Le samedi 28 juillet 2007 à 18:24 -0500, Karl Berry a écrit : > Hi John, > > @documentencoding UTF-8 > as > <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=UTF-8"> > > That is what is supposed to happen. And when I run a test document with > @documentencoding UTF-8, that's what I get in the --html output, modulo > capitalization: > > $ makeinfo --html -o - utf8.tex > ... > <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> > > (With the makeinfo from CVS.) > > I guess you're not seeing that? How does your document start?
Sorry to bother you with this; makeinfo from current CVS is OK, but GUB (Grand Unified Binaries, the home-made build system used to build LilyPond) uses texinfo 4.8. In fact, makeinfo 4.8 is enough for LilyPond, and the sources include a verbatim copy of texinfo.tex (which I regularly update from CVS). Including texinfo.tex in our sources may seem unnecessary or even overkill, but LilyPond has so many dependencies (including CVS snapshots of some packages or patched packages) that we find it a good idea to costless remove one dependency for the user. I played with different makeinfo versions (4.8 and from CVS) and once noticed "charset=UTF-8" was missing in HTML output with makeinfo 4.8. As far as I have tested, it seems that adding "--enable-encoding" flag make all makeinfo versions >=4.8 add "charset=UTF-8", so you can forget all about this story :-) Sorry again for the noise John
