Fix stuff lost when merging xpdf303

restore the implementation of -binary
restore the fix that level2sep and level3sep must write cmyk instead of rgb
restore the conversion of bitmaps with all gray to mono8
fixed the CMYK misspelling in Stream.
Change nnnnnn to number

This way people won't expect it to be six fixed digits
Bug #46708
glib: add poppler_fonts_iter_get_substitute_name
glib: show substitute font name in demo
glib: add copy button to selections demo
pdftocairo: allow one of -scale-to-[xy] = -1 to mean the aspect ratio is to be preserved

based on pdftoppm patch 38ace7db5de0b2b247fd520e48a8f26e5d28c9d7
pdftocairo: document that -scale-to will preserve aspect ratio

based on pdftpppm patch 7ec31b8dc40ec8a3534fbb89964aa011aeb81f5e
Update copyrights
0.19.0 news file
Increase versions
Update poppler copyright
Fix pdftops -passfonts regression

This patch fixes pdftops -passfonts by using the new psFontPassthrough variable
consistently and removing the old psSubstFonts and its setter and getter in
GlobalParams.

Bug 46744
pdffonts: list the encoding of each font

Bug 46888
regtest: Add --pretty-diff option to create-report command

It includes a pretty-diff link to make a bit easier to check differences
in test results. For images it creates a html with javascript that
toggles actual and expected image, using the same code than WebKit
layout test results. For text files it uses HtmlDiff class from python
difflib. It's an option disabled by default because pretty diff for text
files is very slow.
regtest: Ignore backends with no results when creating html report
glib demo: fix typo
Improve CJK suport in PSOutputDev

1. Adapt bug fix for bug 11413 to the postscript device
2. A small bug fix when locateFont doesn't find a suitable font and
returns a null pointer

to 1.:
Adapting the implementation of the bug fix for splash and cairo to the
postscript device was quite easy. But my first proofs of the output with
ghostscript 8.71 shows some regressions where the CJK chars have a
smaller height than the default square of the font. But the "48" in the
output of bug-poppler11413.pdf which is set in a "normal" font but
rotated was at the right position. Then I stepped to ghostscript 9.04,
and now the CJK chars were shown correctly, but the 48 was positioned
wrong. But because of these different tests I think that it is still a
problem in ghostscript when using a mix of CJK fonts and "normal" fonts.
BTW, also Acrobat X distiller has problems with the position of the "48"!

to 2.:
On my first tests with PDF which uses non embedded CJK fonts on Windows
I got crashes. Reason for it was that GlobalParamWin returns Helvetica,
which is not a CID font, but locateFont accepts here only CID fonts and
therefore returns a NULL pointer. I first fixed that and then decided to
return as default MS Mincho if a CID font is expected.
CJK substitute implementation on WIndows platforms.

When You install ghostscript on WIndows You're able to switch on CJK
support. This will create a  cidfmap file in the gs-lib directory. The
ps file which creates it (mkcidfm.ps) runs over the windows font
directory and tries to create a suitable substitution table for missing
CJK fonts. The cidfmap file is more or less PDF like, so it's quite easy
to parse it with our parser and create a substitution table in
GlobalParamsWin and use that table. But I expect it in the poppler data
dir instead of searching for ghostscript installation. If it is not
there, it always returns the default CID font of point 2.
You can either copy it from the gs lib directory or create it with the
ghostscript tool calling

gswin32c -q -dBATCH -sFONTDIR=<windows font directory>
-sCIDFMAP=<popper data dir>/cidfmap mkcidfm.ps
Do not crash on malformed files with 0 bits in the color map of an image
Fix mismatch in some functions declarations