On Fri 26 Jan 2018 at 10:14:22 (+0100), Michael Lange wrote:
> Hi,
> 
> On Thu, 25 Jan 2018 20:31:36 -0600
> David Wright <deb...@lionunicorn.co.uk> wrote:
> 
> > But the main difference between the old and new versions (upgraded
> > today) is that the new version spews error messages from the
> > configuration files, 152 of them in all.
> > 
> > Here are the first few. (The program stammers.)
> > 
> > Config Error: Unknown config file command
> > 'unicodeMap' (/usr/share/xpdf/xpdfrc-arabic:2) Config Error: Some work
> > needs to be done to suppport this option in the Poppler version of xpdf
[…]
> > 
> > This is a days-old installation of stretch 9.3 with ~/.xpdfrc hidden.
> > (Talking of which, they do seem to have fixed many of the interactive
> > commands (I use zoom, turn & continuous) that were missing throughout
> > jessie.)
> 
> I get these same error messages here even when I open an empty xdpf
> window, so they seem not to be related to the document.
> Of course I cannot tell about the document you have, I have been speaking
> only about the document the OP mentioned which works now with both xpdf
> and qpdfview here.

It's a very similar situation to the bank document cited earlier:

Old:
$ pdffonts chase-2015-09.pdf
name                                 type              encoding         emb sub 
uni object ID
------------------------------------ ----------------- ---------------- --- --- 
--- ---------
Helvetica                            Type 1            WinAnsi          no  no  
no      37  0
Helvetica-Bold                       Type 1            WinAnsi          no  no  
no      12  0
$ 

New:
$ pdffonts chase-2015-10.pdf
name                                 type              encoding         emb sub 
uni object ID
------------------------------------ ----------------- ---------------- --- --- 
--- ---------
[none]                               Type 3            Custom           yes no  
yes     43  0
[none]                               Type 3            Custom           yes no  
yes     37  0
Helvetica-Bold                       Type 1            WinAnsi          no  no  
no      36  0
[none]                               Type 3            Custom           yes no  
yes     44  0
$ 

With a newer PC running stretch, I can page through the documents
a little faster. Page 1 of the bill always has blank items, and
by items I mean any information connected to my account.
Page 2 is similar, though most of it is "fine print", and that
displays correctly. Page 3 has most of the account items (only
a few fit on page 1) and these are usually blank. Page 4 is
usually almost entirely unused.

Whether page 3 displays correctly seems to be essentially
unpredictable, it comes and goes. Also, the box round the totals,
which has to be placed according to the number of items, sometimes
appears at completely the wrong X,Y position on the page. So it
seems that it's not just the embedded custom-encoded fonts causing
a problem, but the whole page-rendering process.

Cheers,
David.

Reply via email to