[poppler] Fwd: [Bug 690722] Problem with the font embedding logic

[Derek B. Noonburg]

On 2009 Aug 20, luigi scarso wrote:
> On Thu, Aug 20, 2009 at 5:27 PM, Martin Schröder<martin at oneiros.de> wrote:
>> 2009/8/20 luigi scarso <luigi.scarso at gmail.com>:
>>> Please see
>>> http://bugs.ghostscript.com/show_bug.cgi?id=690722
>>>
>>> Ken will be fix it .
>>
>> Thanks.
>> Still - is the error message from xpdf (which pdftex/luatex issue)
>> correct and is it of any use?
>>
>> Best
>>   Martin
>>
> 
> At pag 3 of AdobeTech#5411 there is
> the following text:
> 
> "codespacetange" definition , without exception, shall
>  always be used:
> 1 begincodespacerange
> <0000><FFFF>
> endcodespacerange
> 
> See also
> PDF 1.7 spec, at pag 472 sec 5.9.2 says:
> "Additional guidance regarding the CMAP defined in this entry is provided
> in Adobe Technical Note #5411, ToUnicode Mapping File Tutorial"
> 
> For what I understand: xpdf makes the only right thing to do.
> And pdf is ok.
> The other applications/viewer can do something else and wrong, and
> maybe until  tomorrow
> they go  unnoticed -- but this is not what we want for luatex & pdftex
> , I presume .


I actually fixed that a while back in Xpdf -- the next release will
parse that CMap without any errors.

When I looked at the PDF / CMap specs, it was unclear whether the
one-byte characters were allowed there or not.  Since it was pretty easy
to accept one-byte characters, and since it doesn't really hurt
anything, and since Acrobat seems to do it too, I decided to change my
CMap parser.

- Derek