Re: Fwd: convert text encodings (was: Old LilyPond versions)

[Mats Bengtsson]

Please note that convert-ly automatically will convert
latin1 to UTF-8 if the input file is older than version 2.5.13.
It will not handle any embedded TeX commands, but my guess is that in
many of the cases, the embedded TeX commands will have
to be replaced by some appropriate \markup command or other
construct in LilyPond, not by a single UTF-8 encoded character
string.

  /Mats

Quoting fiëé visuëlle <address@hidden>:

> Am 2008-04-08 um 20:28 schrieb Graham Percival:
> > You're talking about the old LaTeX accents -> utf-8 ?
> >
> > Manual conversion is necessary with current convert-ly.  I can
> > think of three ways to automate it.  They're all kind-of hackish,
> > but they'd work in theory.  It just needs somebody to translate
> > that theory into practice.
>
> Conversion of "LaTeX encoding" to any other encoding, esp. UTF-8 is  easy.
> I've a little script ready for such - but it converts whole files, I
> don't know if it will affect LilyPond commands.
>
> Here:
> http://www.fiee.net/texnique/?menu=0-2-2&lang=en
> you can download the "mab2bib" archive, it includes "utf2latex.py".
>
> Just rename that to "latex2utf.py" (or any other encodings, like
> "latin12utf" or "macroman2utf", it analyzes its filename when called).
>
> It should work with all encodings that Python knows of. Normally
> LaTeX is not one of them, so the also included "latex.py" must reside
>  in the same directory.
>
> Have fun!
>
>
> Greetlings from Lake Constance
> ---
> fiëé visuëlle
> Henning Hraban Ramm
> http://www.fiee.net
> http://angerweit.tikon.ch/lieder/
> https://www.cacert.org (I'm an assurer)
>
> _______________________________________________
> lilypond-user mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/lilypond-user