Re: Problem with non-ASCII characters

[Mats Bengtsson]

I noted that text in the manual after sending the previous response, but
my comment is actually relevant for the tex backend as well, so we should
remove that misleading information from the manual.

My guess is that you didn't manage to save your file in UTF8 encoding,
but it could also be that you don't have the necessary fonts (or at least
that LilyPond/Pango doesn't know about them).

If you run the command
file test.ly
it should say something like:
test.ly: UTF-8 Unicode English text
If it doesn't mention UTF-8 then you failed to persuade Emacs to use
the correct encoding.

You could also try to download and process the example utf-8.ly
from the Regression Tests document (just make sure to remove the
line \include "lilypond-book-preamble.ly" at the top of the file first).

  /Mats


Ari Constancio wrote:

> Hello,
>
> Thanks for replying.
>
> > Why do you use the texstr backend? As far as I know, it's just an old
> > left over from some experiment that never was finished and it's 
> > certainly
> > unsupported.
>
>
> Probably because it says so in the documentation and it's not
> mencioned that it is an unsupported experiment. I referred to the
> stable version (2.8.6) but I checked also the 2.9.18 docs. Here's the
> diff of the web pages involved
> (http://lilypond.org/doc/v2.{8,9}/Documentation/user/lilypond/Text-encoding.html): 
>
>
> --- 2.8-text-enc.txt    2006-09-21 10:06:34.000000000 +0100
> +++ 2.9-text-enc.txt    2006-09-21 10:06:25.000000000 +0100
> @@ -4,7 +4,7 @@
>    Previous: [4]Including LilyPond files, Up: [5]Input files
>      _________________________________________________________________
>
> -    10.1.4 Text encoding
> +    10.1.6 Text encoding
>
>    LilyPond uses the Pango library to format multi-lingual texts, and
>    does not perform any input-encoding conversions. This means that any
> @@ -41,7 +41,7 @@
>
>    [7]input/regression/utf-8.ly
>
> -   This page is for LilyPond-2.8.5 (stable-branch).
> +   This page is for LilyPond-2.9.18 (development-branch).
>
>
>     Report errors to
> @@ -53,13 +53,13 @@
>
> References
>
> -   1. http://lilypond.org/doc/v2.8/Documentation/...
> -   2.http://lilypond.org/doc/v2.8/Documentation/...
> -   3. http://lilypond.org/doc/v2.8/Documentation/...
> -   4. http://lilypond.org/doc/v2.8/Documentation/...
> -   5. http://lilypond.org/doc/v2.8/Documentation/...
> -   6. http://lilypond.org/doc/v2.8/Documentation/...
> -   7. http://lilypond.org/doc/v2.8/Documentation/...
> +   1. http://lilypond.org/doc/v2.9/Documentation/...
> +   2. http://lilypond.org/doc/v2.9/Documentation/...
> +   3. http://lilypond.org/doc/v2.9/Documentation/...
> +   4. http://lilypond.org/doc/v2.9/Documentation/...
> +   5. http://lilypond.org/doc/v2.9/Documentation/...
> +   6. http://lilypond.org/doc/v2.9/Documentation/...
> +   7. http://lilypond.org/doc/v2.9/Documentation/...
>    8. http://post.gmane.org/post.php?group=gmane.comp.gnu.lilypond.bugs
> -   9. 
> http://lilypond.org/doc/v2.8/Documentation/user/lilypond/Text-encoding.html 
>
> +   9. 
> http://lilypond.org/doc/v2.9/Documentation/user/lilypond/Text-encoding.html 
>
>   10. http://lilypond.org/web/about/browser-language
>
> Only the version number changed...
>
> I followed your advice, while upgrading to 2.9.18:
>
> $ lilypond test.ly
>
> GNU LilyPond 2.9.18
> Processing `test.ly'
> Parsing...
> Interpreting music...
> warning: Two simultaneous key-change events, junking this one
> warning: Previous key-change event here
> warning: Two simultaneous key-change events, junking this one
> warning: Previous key-change event here[8][16][17]
> Preprocessing graphical objects...
> programming error: FT_Get_Glyph_Name returns error
> continuing, cross fingers
> programming error: Glyph has no name, but font supports glyph naming.
> Skipping glyph: Century Schoolbook L 3.3818359375
> continuing, cross fingers
> Layout output to `test.ps'...
> Converting to `test.pdf'...
>
> The compilation is apparently successful, but the non-ASCII characters
> do not appear in the final formats (ps,pdf). Could it be a font
> problem?
>
> Thank you again,
> Ari Constancio
>
>
> _______________________________________________
> lilypond-user mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/lilypond-user