Last modified: 2014-08-28 00:17:31 UTC
Use ABC notation in Score, title not support Chinese (If T is Chinese): <score lang="ABC"> X:1 T:测试 M:6/8 L:1/8 R:jig K:G GFG BAB | gfg gab | GFG BAB | d2A AFD | GFG BAB | gfg gab | age edB |1 dBA AFD :|2 dBA ABd |: efe edB | dBA ABd | efe edB | gdB ABd | efe edB | d2d def | gfe edB |1 dBA ABd :|2 dBA AFD |] </score> Retun error: Unable to compile LilyPond input file: Processing `.../file.ly' Parsing... Interpreting music... [8][16] Preprocessing graphical objects... Interpreting music... MIDI output to `file.midi'... programming error: FT_Get_Glyph_Name () error: invalid argument continuing, cross fingers programming error: Glyph has no name, but font supports glyph naming. Skipping glyph U+10004E24, file /usr/share/lilypond/2.14.2/fonts/otf/CenturySchL-Bold.otf continuing, cross fingers programming error: FT_Get_Glyph_Name () error: invalid argument continuing, cross fingers programming error: Glyph has no name, but font supports glyph naming. Skipping glyph U+100053EA, file /usr/share/lilypond/2.14.2/fonts/otf/CenturySchL-Bold.otf continuing, cross fingers programming error: FT_Get_Glyph_Name () error: invalid argument continuing, cross fingers programming error: Glyph has no name, but font supports glyph naming. Skipping glyph U+10008001, file /usr/share/lilypond/2.14.2/fonts/otf/CenturySchL-Bold.otf continuing, cross fingers programming error: FT_Get_Glyph_Name () error: invalid argument continuing, cross fingers programming error: Glyph has no name, but font supports glyph naming. Skipping glyph U+1000864E, file /usr/share/lilypond/2.14.2/fonts/otf/CenturySchL-Bold.otf continuing, cross fingers Finding the ideal number of pages... Fitting music on 1 page... Drawing systems... Layout output to `file.eps'... Converting to PNG...GS exited with status: 9
This may require upstream development as this is the lilypond parts itself Might need an upstream bug for extended character set support
I cannot find a corresponding issue upstream in http://code.google.com/p/lilypond/issues/list and existing tickets imply that unicode is supported. Hence not sure whether to upstream or not.
