Comment 14 for bug 759882

Revision history for this message
Nobuto Murata (nobuto) wrote :

> @Nobuto
>
>> It seems to be a bug of parsing the font name.
>
> I want to clarify the this indication. Could you please check your analysis?
>
> (1)
> Evince (in File -> Property) 's property show the "Times New Roman" (like https://wiki.ubuntulinux.jp/Develop/Natty/Evince?action=AttachFile&do=get&target=evince2-mocchi.png) , that is *only* property-dialog issue. In rendering, evince has same logical bug(see 2), but that is not same code.
>
> (2)
> Some PDF (e.g. #8 attached) files have SHIFT_JIS encoded font-name, but that is correct in PDF format. Mitsuya Shibata and me think that is PDF-reader side bug, not PDF itself.

Ah, I might have misunderstood this report. I thought this report handles early-Natty regression that characters like Ryumin which can be shown on Maverick are shown as squares on Natty.

And now my question is,
Does this report handles the problem that when SHIFT_JIS encoded font-names are specified, evince(poppler) cannot show the characters?
You have not mention SHIFT_JIS until comment #11, I'm confused.

BTW, I mentioned parsing problem as that even if GothicBBB is shown in properties window properly, but characters which are specified as GothicBBB shown as squares. I have reported this issue as Bug #769827.

> # So, let's cry with us, "PDF specification is too complex for me!":)

Just for my curiosity, supposing that SHIFT_JIS encoded font-names complies PDF specifications, what software uses SHIFT_JIS encoded font-names as far as you know?
I'd like to know how many PDF files are affected.

Just for your information, "poppler should fall back font properly" issue seems to be reported in upstream as poppler.
https://bugs.freedesktop.org/show_bug.cgi?id=36474