On 7/1/2014 1:40 PM, Fabian Greffrath wrote:
Am Dienstag, den 01.07.2014, 08:08 +0900 schrieb Norbert Preining:or adding another fake glyph fi/f_i,Yes, please. This sounds like the best compromise: It retains backward and forward compatibility, should be trivial to implement and should be safe for future changes that poppler (or any other rendering framework) introduce.
I have no clue what this will solve. Say that the original input stream has this:
effe = e f i e and the feature processor turns that into <glyph representing e> <glyph representing fi> <glyph representing e> which in the pdf stream can become <1><2><1> with 1 pointing glyph representing e and 2 representing fi.The pdf file has then this mapping with fi being named f_i and not fi (why should it) and also carries a tounicode which maps the <1> to unicode e and <2> to unicodes f followed by i. The reference to ff never ends up in the subsetted file.
Just fix poppler, because it it has this problem with f_i it definitely has more such problems.
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------