.ly input encodings

[Jan Nieuwenhuizen]

Hi,

It looks like 2.5 is almost feature complete, but we may want to
add friendlier support for input encodings of .ly files.

Are we going to support utf-8 enabled editors only, or should we look
into iconv?

When using iconv, we should devise some kind of encoding marker for
the .ly source to start with, I guess?


Currently, convert-ly has

        if re.search (r"\\encoding", str):
                sys.stderr.write ("Sorry, input files should be UTF8.\n"
                                  + "Please convert by hand.")
                raise FatalConversionError()

which is a bit unfriendly.  This unfriendliness is unnecessary in case
the .ly source does not have 8bit characters, or if \encoding = Tex.

If it does contain 8-bit set characters, chances are \encoding = latin1,
because that's what 2.4 supported.

All these cases could be handled elegantly by convert-ly, either by
recoding or by adding an input encoding marker (eg, latin1) for iconv.


Jan.

-- 
Jan Nieuwenhuizen <address@hidden> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien       | http://www.lilypond.org