Re: Text encoding

[Ed Baskerville]

Well, I'd like to have a usable--though not feature-rich--preview 
version out within a couple weeks. Since 2.4 is still the current 
"stable" version, I might as well support it--it's a matter of changing 
a single constant in a method call to output in Latin1 instead of 
UTF-8.

Correct me if I'm wrong, but I'm assuming that the silence means that 
everything I said was accurate: in 2.5+, we have UTF-8 only, and 
\encoding and \encoded-simple are no longer supported.

--Ed

On Apr 24, 2005, at 3:12 PM, Han-Wen Nienhuys wrote:

> Op zo, 24-04-2005 te 12:06 -0700, schreef Ed Baskerville:
> > Hi all,
> >
> > I have a few questions/clarifications about text encoding in LilyPond.
> > These are are covered to some extent in the list archives and in the
> > docs, but I wanted to check with the list to get the most accurate
> > information from the horses' mouths...
> >
> > (1) This is what I'm getting from the lilypond-user and lilypond-devel
> > archives: LilyPond 2.4.x and earlier use ISO Latin1 as the native
> > encoding, and 2.5+ are using UTF-8. Therefore, a LilyPond previewer
> > ideally should detect the version of LilyPond being used and output 
> > the
> > right encoding accordingly. Is this accurate?
> >
> > (2) Aside from one allusion in section 10.2.2 (perhaps out of date?)
> > the \encoding command has been expunged from the 2.5 documentation, 
> > and
> > the section entitled "Text encoding" makes it sound like UTF-8 is the
> > only way to go. Does that mean that \encoding is no longer supported?
> > What about \encoded-simple?
>
> forget about supporting 2.4. By the time you get you'll get the first
> version of your tool out, we'll probably be well on our way into
> 2.7 :-)
>
> > (3) Is TeX encoding gone too?
>
> yup
>
> --
> Han-Wen Nienhuys - address@hidden
> LilyPond Software Design - http://www.lilypond-design.com