This is a bug in 1.5.2. There is a bug report here:
https://bugs.scribus.net/view.php?id=14117The way this showed up for me is that many 3-digit pages numbers are
printed with one or two missing characters (never the first digit) represented by a box.
The missing digits vary from one PDF export to the next, but in patterns such as
no 8s print as the second digit.
It is supposed to be fixed in 1.5.3.
The method of closing and reopening the file, which Bri_Huang said
worked for him, gives worse results for me! - none of the 3 digits print!
Somebody posted on another thread that the workaround is to print to a separate
PDF printer instead of using Scribus's own PDF export. This didn't work for me on the
first try using PDF995; in this case Scribus went into a loop of trying to export some
piece of data, and I had to cancel; then the PDF printed the first page and an errror message.
Scribus refused to print successfully to PDF995.
I was successful when I used Foxit PDF printer instead. All the page numbers
are fine. Hallelujah. So, all print-to-PDF programs are not the same to Scribus.
BUT this is still not a perfect solution: the flaw only showed up when I concatenated
all of the chapter PDFs, and then it appeared that Foxit's 8.5x11 page is not quite
the same size as Scribus's 8.5x11 page, but showing up on the screen a few pixels
smaller. I don't know what will happen when this concatenated PDF is printed on paper.
Following this I spent another hour or so adjusting the page size in Foxit PDF printer
by trial and error, and the page size 8.27" x 11.70" makes the concatenated PDF
pages match up at the same size as the ones I previously had exported (with
no problems, by the way) from Scribus 1.5.2 using the similar files of the previous
five chapters.
The funny thing is that I have converted six files from 1.4.6 to 1.5.2 recently and
in the first five the page numbers printed correctly. This file is bigger and has more
graphics. It may be a matter of switching over to 1.5.3. I haven't been able to make
1.5.5 work on my old Windows 7 machine because of a .dll that I can't find.
However, it appears that I do have a workaround now.
jack