On Mon, Jan 13, 2014 at 02:25:37PM +0100, Taco Hoekwater wrote:
On 01/12/2014 11:51 PM, Khaled Hosny wrote:
On Sat, Jan 11, 2014 at 04:30:19PM +0100, Cron Daemon wrote:
------------------------------------------------------------------------ r4742 | luigi | 2014-01-11 12:26:06 +0100 (Sat, 11 Jan 2014) | 1 line Changed paths: M /trunk/source/texk/web2c/luatexdir/luafontloader/fontforge/fontforge/parsettfatt.c
unwanted side effects: font loading takes way longer due to linear checks and it makes no sense to do that for a bugged font; this can better be doen at the lua end if needed at all (hans)
Then you are better dropping glyph name guessing code completely because it is known to produce duplicate glyph names, having generic "glyphXXXX" names is better than having more than one glyph with the same name (the fonts are not bugged, but the original was).
Luatex is now back to how it behaved earlier (buggy, but with known workarounds) with a ticket that explains what happens and also why it is not patched right now:
Since the part after the period is irrelevant (text extracting tools guessing code point from glyph name strip everything starting from the first period found), we can just generate a unique prefix each time regardless of the feature tag. Regards, Khaled