With the word-space override you suggest (below), that means that your
comment of a few weeks ago that it _might_ be desirable to redefine
\char #<unicode-number>
to produce a utf-8 byte string is true: this would in fact be useful for
people who need, infrequently, to insert various odd special characters in
their Lilypond text, such as an em-dash, a capital Greek delta, or a
1/2-sign, or who need to print titles in languages, such as Portuguese or
Romanian, that have, in addition to the usual panoply of European
characters, just a few oddball characters. Even for a text editor that
can _save_ in utf-8, _inputting_ the required character directly
presumably requires a character map, and at this point I don't know that
any really extensive character maps exist.
I realize that implementing a new \char is not trivial, since the utf-8
coding algorithm is such a mess.
-- Tom
On Thu, 5 Jan 2006, Han-Wen Nienhuys wrote:
> [EMAIL PROTECTED] wrote:
> > The problem I've had with that is that when I define
> >
> > eaigu = "<the utf-8 double byte for é>"
> >
> > and then (later) say
> >
> > \markup "sym" \eaigu "trique"
> >
> > what I get in the PDF file is
> >
> > sym é trique
> >
> > because Lilypond inserts a space between any two markup components.
>
> try
>
> \override #'(word-space . 0) { sym \eaigu trique }
>
> --
> Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
_______________________________________________
lilypond-user mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/lilypond-user
