[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Lilypond-auto] Issue 2889 in lilypond: Bad unicode char value in error
From: |
lilypond |
Subject: |
[Lilypond-auto] Issue 2889 in lilypond: Bad unicode char value in error message |
Date: |
Wed, 10 Oct 2012 20:49:28 +0000 |
Status: Accepted
Owner: ----
Labels: Type-Defect
New issue 2889 by address@hidden: Bad unicode char value in error
message
http://code.google.com/p/lilypond/issues/detail?id=2889
Reported by Nick Payne:
http://lists.gnu.org/archive/html/bug-lilypond/2012-10/msg00076.html
See below. Trying to use the unicode character value for a two-em dash
gives an error message where the char value has been incremented by
0x10000000:
%======================
\version "2.17.0"
\relative c' {
c1^\markup { \char ##x2E3A }
}
%======================
Processing `/home/nick/lilypond/examples/test.ly'
Parsing...
Interpreting music...
Preprocessing graphical objects...
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+10002E3A, file /home/nick/.fonts/CenturySchL-Roma.otf
continuing, cross fingers
- [Lilypond-auto] Issue 2889 in lilypond: Bad unicode char value in error message,
lilypond <=
- Re: [Lilypond-auto] Issue 2889 in lilypond: Bad unicode char value in error message, lilypond, 2012/10/10
- Re: [Lilypond-auto] Issue 2889 in lilypond: Bad unicode char value in error message, lilypond, 2012/10/10
- Re: [Lilypond-auto] Issue 2889 in lilypond: Bad unicode char value in error message, lilypond, 2012/10/10
- Re: [Lilypond-auto] Issue 2889 in lilypond: Bad unicode char value in error message, lilypond, 2012/10/10
- Re: [Lilypond-auto] Issue 2889 in lilypond: Bad unicode char value in error message, lilypond, 2012/10/10
- Re: [Lilypond-auto] Issue 2889 in lilypond: Bad unicode char value in error message, lilypond, 2012/10/14
- Re: [Lilypond-auto] Issue 2889 in lilypond: Bad unicode char value in error message, lilypond, 2012/10/15
- Re: [Lilypond-auto] Issue 2889 in lilypond: Bad unicode char value in error message, lilypond, 2012/10/15
- Re: [Lilypond-auto] Issue 2889 in lilypond: Bad unicode char value in error message, lilypond, 2012/10/15
- Re: [Lilypond-auto] Issue 2889 in lilypond: Bad unicode char value in error message, lilypond, 2012/10/15