[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: anglosaxian

From: Mats Bengtsson
Subject: Re: anglosaxian
Date: Tue, 02 Mar 2004 17:21:24 +0100
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040113

That's quick feedback! I changed the formulation yesterday
and get this feedback within 24 hours.

I have changed the formulation and talk about US-ASCII instead.



David Bobroff wrote:
Starting at line 200 the file lilypond-book.itely says:

LilyPond does not use the LaTeX font handling scheme for lyrics and text
markups, so if you use non-anglosaxian characters in your lilypond-book
documents, include @address@hidden@}} in the file
header but do not include @address@hidden@}}. Character
sets other than latin1 are not supported directly but may be handled by
explicitly specifying the @code{font-name} property in LilyPond and
using the corresponding LaTeX packages. Please consult the mailing list
for more details.

Firstly, "non-anglosaxian" should be "non-Anglo-Saxon."  But, and
perhaps more to the point, Anglo-Saxon includes such charaters as 'eth',
'thorn' and 'aesc' (the ligature 'ae').  All of these characters exist
above character code 127 making them non-US-ASCII.  These characters are
all part of [T1], or [latin1] or iso-8859-1.   Does "non-anglosaxian"
need to be changed to "non-US-ASCII" instead?


Lilypond-devel mailing list

        Mats Bengtsson
        Signal Processing
        Signals, Sensors and Systems
        Royal Institute of Technology
        SE-100 44  STOCKHOLM
        Phone: (+46) 8 790 8463                         
        Fax:   (+46) 8 790 7260
        Email: address@hidden

reply via email to

[Prev in Thread] Current Thread [Next in Thread]