Re: [Lilypond-auto] Issue 3929 in lilypond: ps2pdf produces ugly output if a single glyph gets accessed with different glyph names

[lilypond]

Comment #2 on issue 3929 by address@hidden: ps2pdf produces ugly output if a  
single glyph gets accessed with different glyph names
http://code.google.com/p/lilypond/issues/detail?id=3929

Maybe send them as a "counterexample" the same example without overriding  
the underlying font.  This will print fine, and the glyphs will be selected  
_totally_ in the same manner.

Personally, I think using the same glyph for omikron and o is a bad idea in  
type design anyway, but it turns out that it confuses GhostScript as well,  
so maybe the Libertine people should at least duplicate the glyph code  
rather than pointing at the same code twice since presumably it is in their  
interest to have their font not look like garbage when printed using  
GhostScript.

--
You received this message because this project is configured to send all  
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings