@Nobuto > Does this report handles the problem that when SHIFT_JIS encoded font- names are specified, evince(poppler) cannot show the characters?
No, its seems misunderstanding too. This bug covers below "troble": - Workaround/mitigation/fixing for Evince's "square character bug" (yes, strictly speaking, its libpoppler's bug). - That caused by fontconfig settings. Evince(libpoppler) could not handles properly "secondoly" fonts. - It has same root problem of https://bugs.freedesktop.org/show_bug.cgi?id=36474 . But another approach(workarounding). This "trouble" caused by these situations(In PDF property): a) PDF designate "non-existent fonts" in your sytstem. b) PDF designate "Shift_JIS(amd other encodings) encoded FontName". That makes corruption in FontName strings, that cause a) as a result(Broken FontName could not match system's font lists). And, If you reproduce this "trouble", you could see these two behavior: 1) Evince could not show characters ("square character bug"), its evince/libpoppler bug. 2) Evince shows the FontName as "Times New Roman". This is evince's bug. The key factor of that, these are brother, but not same bug. - "Situation a" cause 1. - "Situation b" cause 1 and 2. So, I'll report 2) as a yet another bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/759882 Title: In some Japanese PDF files(in evince) could not display Kanji characters -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
