From 75f99bcc64c9bae0d01aaae651b057052ca895ab Mon Sep 17 00:00:00 2001 From: Jan Nieuwenhuizen Date: Sun, 6 Feb 2005 11:45:52 +0000 Subject: [PATCH] (Text encoding): Clarify. --- ChangeLog | 2 ++ Documentation/user/changing-defaults.itely | 13 +++++++------ 2 files changed, 9 insertions(+), 6 deletions(-) diff --git a/ChangeLog b/ChangeLog index 577eb76e8c..61546679d3 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,5 +1,7 @@ 2005-02-06 Jan Nieuwenhuizen + * Documentation/user/changing-defaults.itely (Text encoding): Clarify. + * ly/titling-init.ly: Do not also print intstrument in header on first page. Do not print page number on first and only page. diff --git a/Documentation/user/changing-defaults.itely b/Documentation/user/changing-defaults.itely index 4d3b32b9ce..400fbf6428 100644 --- a/Documentation/user/changing-defaults.itely +++ b/Documentation/user/changing-defaults.itely @@ -1552,12 +1552,13 @@ Syntax errors for markup mode are confusing. @node Text encoding @subsection Text encoding -LilyPond uses the Pango library to format multi-lingual texts. This -means that any text, be it title, lyric text, or musical instruction -contaning non-ASCII characters should be entered as Unicode. Such -files should be edited using a Unicode aware editor, and saved as UTF8 -encoded. Most popular modern editors have UTF8 support, for example, -vim, Emacs, jEdit, and GEdit do. +LilyPond uses the Pango library to format multi-lingual texts, and +does not perform any input-encoding conversions. This means that any +text, be it title, lyric text, or musical instruction containing +non-ASCII characters, must be utf-8. Easiest to enter such texts is +by using a Unicode-aware editor, and save using utf-8 encoding. Most +popular modern editors have utf-8 support, for example, vim, Emacs, +jEdit, and GEdit do. Depending on the fonts installed, the following fragment shows Hebrew and Cyrillic lyrics, -- 2.39.5