Hello Peter,
The codepoint you are referring to is from the ancient Cypriot script.
The code block for this script was added to Unicode Standard in April
2003 (according to http://en.wikipedia.org/wiki/Cypriot_syllabary).
I see no reason why you shouldn't set a score in an ancient script - ca
> Not all unicode characters are being correctly realised in my score.
> Something like \mark \markup { \char ##x03EE } will work but this
> throws an error:
>
> \mark \markup { \char ##x1080B }
>
> [...]
>
> Thanks. Is there a solution to the problem? It's happening in
> about 30% of the unicod
Thanks. Is there a solution to the problem? It's happening in about 30%
of the unicode.
On 05/05/2013 11:15 PM, Nick Payne wrote:
On 06/05/13 00:46, Peter O'Doherty wrote:
\mark \markup { \char ##x1080B }
error:
programming error: FT_Get_Glyph_Name () error: invalid argument
continuing, cro
On 06/05/13 00:46, Peter O'Doherty wrote:
\mark \markup { \char ##x1080B }
error:
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+1001080B, file
/home/peter/lilypo
Hi,
Not all unicode characters are being correctly realised in my score.
Something like \mark \markup { \char ##x03EE } will work but this throws
an error:
\mark \markup { \char ##x1080B }
error:
programming error: FT_Get_Glyph_Name () error: invalid argument
continuing, cross fingers
progr
