> > So - if you don't want the possibility to write é instead of \'e,
> > we can junk it - I'll do it, and make a system to include it when
> > we need it ("\mudelainput8bit" and "ly2dvi -8", or similar).
>
> I don't get a very warm feeling from this option, myself. But as
> long as it *breaks* \'e, i think you should junk it.
There should be no need for the extra option once we fix the
cause of the problem, namely the font selection commands
defined in lilyponddefs.tex
I'll take a look at it during the weekend.
> > Jan Arne, once we have the correct LaTeX font commands, you should add
> > \usepackage[latin1]{inputenc}
> > in the generated file header so we can use the full latin1 character
> > set and write e.g. "Un peu plus lent et élégant" directly in the .ly
> > file. The Latin1 character set is already supported in Lilypond.
>
> Isn't that some of what is done by
> \usepackage[T1]{fontenc}
> in cooperation with e.g.
> \usepackage[norsk]{babel}?
No, babel sets hyphenation patterns, changes the name of strings such as
"Figure", "References" a.s.o. and for some languages redefines e.g. '"a'
to give a 'ä' (however the norsk version doesn't do any such changes).
Babel does not bother about 8-bit characters.
As far as I can understand from the documentation, the inputencoding is
just was it sounds like, namely translating from the character codes
to the symbol to be produced. 'latin1' corresponds to the standard used
on UNIX machines PCs running Windows, 'applemac' understands the
character codes used on a Macintosh a.s.o.
I have been taught to always use the commands
\usepackage[latin1]{inputenc}
\usepackage[T1]{fontenc}
together, but when I try it right now, it seems to work as soon as I
use at least one of the two packages are used. This must be since the
ordering of the special characters is the same in the TeX fonts as in
latin1 and will certainly not work on a Macintosh or other machine
with its own character table.
Note that some of our earlier mails could be confusing to people
who don't have a mail reader that understands MIME, since our
8-bit examples look strange in the "quoted-printable" encoding.
/Mats
