https://codereview.appspot.com/339090043/diff/80001/ps/encodingdefs.ps File ps/encodingdefs.ps (right):
https://codereview.appspot.com/339090043/diff/80001/ps/encodingdefs.ps#newcode721 ps/encodingdefs.ps:721: /.notdef /.notdef /.notdef /.notdef /.notdef Yes, the encoding vector should contain exactly 256 elements. https://codereview.appspot.com/339090043/diff/80001/ps/encodingdefs.ps#newcode860 ps/encodingdefs.ps:860: /nine {<7c> show} def The order in /LilyOtherEncoding doesn't matter. It's this very encoding vector that maps glyph names to glyph indices. https://codereview.appspot.com/339090043/diff/80001/ps/encodingdefs.ps#newcode863 ps/encodingdefs.ps:863: % 0x78 I think the hex numbers in the comment lines refer to the glyph order in the font – 0x00 indicates the first glyph in the Type 1 font, 0x0a the elenventh. https://codereview.appspot.com/339090043/ _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
