Let's go crazy and make sure each error/warning has a lot of detail (or a link to a lot of detail).

There has also been a request to write the report as a PDF.

Just to add, my personal preference would if report was in text format, so it's somewhat machine-readable (and JSON would be even better). Though I can see that in other use cases a PDF would be preferable.

Another request for this was received.

Basic text/HTML reports are in 2.17.x, could add JSON/PDF output formats, and documentation for the errors (maybe links to dcpomatic.com).

Though maybe the existing error texts are OK and better documentation is not such a high priority.

Another +1 for PDFs.

Why PDF? Everyone can print to PDFs nowadays? If this would be intended to be printed on paper to go with a DCP, plain text can be printed just as well.

Admittedly, PDF would just allow for a nicer layout, headline/title, section separations in bold, etc.

I guess people get asked for PDF, so it probably just about makes sense to do it in DCP-o-matic if it's not too difficult (I imagine there's a library somewhere that could be integrated).

Just that PDF is then more complicated to be processed by other tools (e.g. analysis of large collections of DCPs).