LGTM
For the future, I would like to prefer Identity-H encoding rather than 3 custom encodings. If I understand correctly, All glyphs can be used with Identity-H encoding. No other encoding is necessary. For current LilyPond and Ghostscript, when using CID-keyed font, Identity-H encoding PDF is generated. If you use the same CID-keyed font in many intermediate PDFs, you can unify them into one font in the final PDF no matter what glyphs you use. Unfortunately, non-CID-keyed fonts can not use Identity-H encoding. XeTeX and LuaTeX seem to convert non-CID-Keyed font to CID-keyed font on the fly, and embed it to PDF, use Identity-H encoding. https://codereview.appspot.com/325630043/ _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
