I have used Latin1 character encoding for the last 15 years for handling
text in English, French, Spanish, and German. My (Unix) e-mail
client uses Latin1 (ISO-8859-1). I use a Latin1 text editor for LilyPond
and thus avoid the cursed false-single-quote problem, and I do not want to
incur the hazards of unicode character-encoding.
If LilyPond can't give me Latin1 characters (é à ç ö etc.) then I will
handwrite them in on the printout, but it would be look cleaner if
LilyPond could handle Latin1 text characters, as is the case with every
other piece of software I use.
I'm running LilyPond 2.6.0 under Windows.
The file ...\usr\share\lilypond\2.6.0\ly\paper-defaults.ly
sanctions Latin1 in the statement
inputencoding = #"latin1"
and later under
#(define text-font defaults... ...)
The file ...\usr\share\lilypond\2.6.0\scm\encoding.scm,
in the long definition
(define-public latin1-coding-vector... ...),
laboriously lists all 256 Latin1 characters, with .notdef for the
control characters and with a full list of the Western European
accented characters (agrave, aacute, acircumflex, etc.).
The clear implication is that the coding for LilyPond to recognize
Latin1 characters is there. But something somewhere is blocking
their recognition (à, é, etc. in markup are just ignored).
What can I change in which file to get LilyPond to accept Latin1
characters?
Or what trick, however laborious, will enable me to use Latin1 characters
in markup? I only need them occasionally in titles.
There is considerable coding to enable Latin1 in the .ly and .scm files in
the LilyPond distribution; how can this coding be made to actually
function?
Thank you for your help.
-- Tom
***********************************************************************
On Thu, 1 Sep 2005, Mats Bengtsson wrote:
address@hidden wrote:
The only unicode characters I ever need are in fact, on rare occasions,
some Latin-1 character (à é è ç ö ü etc.) in a song title.
The ASCII editor I use accepts these characters, but then LilyPond \markup
just skips them.
I would rather not switch to a utf-8 editor.
What editor do you use, then, an what character encoding does it use
when savinf the files? Most text editors nowadays can be configured
to save the file using UTF-8.
Is there any way to
incorporate Latin-1 (or unicode) characters into an ASCII LilyPond file,
using HTML notation or some other trick? It wouldn't have to be
"convenient" if it would just work. I have used only LP's built-in roman
and sans fonts; would using an external TTF (TrueType) font give me access
to Latin-1 characters that LilyPond would recognize?
It doesn't matter what font you use. In fact, the text font used in
Lilypond are not built into the program but taken from what you already
have on your machine.
/Mats
_______________________________________________
lilypond-user mailing list
address@hidden
http://lists.gnu.org/mailman/listinfo/lilypond-user