[poppler] Fontname vs FontName WAS Filename vs FileName

[Jonathan Kew]

On 2 Dec 2009, at 23:34, Albert Astals Cid wrote:

> A Dijous, 3 de desembre de 2009, Martin Schröder va escriure:
>> 2009/12/2 Albert Astals Cid <aacid at kde.org>:
>>> PDF on KDE bug 217013 has a dictionary with a key named Filename  
>>> instead
>>> FileName, so when converting to PS it crashes.
>>
>> Do you mean http://www.tramontana.com.au/bug_files/okular.PDF ?
> Yes
>
>> Do you FontName & Fontname (obj 9)?
> Yes, sorry i suck :D
>
>>
>>> The question is should each time we look for the FileName key look  
>>> for
>>> the Filename one if it fails? Or even more broad should we turn
>>> dictionary searches case insensitive? Or do not try to make it work?
>>
>> I wanted to complain, but since AR9 accepts the file, so should you
>> (maybe issuing a warning). Follow the robustness principle, but case
>> by case - i.e. I wouldn't turn key searches case insensitive.
>
> Any other opinion

AFAICT from a quick look, the PDF specification does not allow this;  
it explicitly says that PDF is case-sensitive, and it only documents  
the key FontName, not Fontname. So I think it should be ignored (which  
I guess means the font concerned can't be used). Obviously, crashing  
is bad and should be avoided, but when it comes to interpreting the  
contents of the PDF, follow the specification, not the bugs of a  
particular implementation.

JK