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
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 -
The new behaviour of makeinfo regarding UTF-8 encoding
New behavior? Sorry, I'm blanking.
Le jeudi 05 juillet 2007 à 12:16 -0500, Karl Berry a écrit :
By the way, do you use makeinfo with the lilypond manual?
Yes, we build the HTML manual in all languages and the Info manual in
English.
If so, could
you see if version in the 4.9.90 pretest (alpha.gnu.org/gnu/texinfo) has
any
Thanks for the fix. Unfortunately, I'm not at home and have no
computer access to build LilyPond. I'll be back on July 25th.
If testing this bugfix is urgent, I can ask somebody on lilypond-devel to do it.
We use makeinfo to build HTML and Info manuals, so I'll test 4.9.90.
Cheers,
John
much space is often left around the quoted text
Thanks for the report, and sorry for the delayed reply. There's a new
version at ftp://tug.org/tex/texinfo.tex with the patch below, which
fixed it for me.
By the way, do you use makeinfo with the lilypond manual? If so, could
you see if
Dear Texinfo hackers,
We LilyPond translators have found a serious layout problem in LilyPond
PDF manual, with Texinfo 4.9. pdfetex/texinfo.tex seems to be sometimes
confused when formatting text with quotes: much space is often left
around the quoted text, leading to overfull hboxes and a
