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.
Thanks
/Mats
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 @[EMAIL PROTECTED]@}} in the file header but do not include @[EMAIL PROTECTED]@}}. 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?
-David
_______________________________________________ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel
-- ============================================= Mats Bengtsson Signal Processing Signals, Sensors and Systems Royal Institute of Technology SE-100 44 STOCKHOLM Sweden Phone: (+46) 8 790 8463 Fax: (+46) 8 790 7260 Email: [EMAIL PROTECTED] WWW: http://www.s3.kth.se/~mabe =============================================
_______________________________________________ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel
