Re: makeinfo with utf-8 support
> [EMAIL PROTECTED]: > > Le jeudi 04 janvier 2007 à 00:33 +0100, Karl Hammar a écrit : > > > Hmm, when building I get: > > > > > > out/lilypond.nexi:62: warning: unrecognized encoding name `utf-8'. > ... > > > Does anybody know where the makeinfo with utf-8 support is, a patch ? > > > > AFAIK Texinfo does no character encoding conversion for the Info and > > HTML output, so the LilyPond devels have decided to use the modern > > character set UTF-8, not Latin1. This will really become a problem for > > the PDF (outputted by Texinfo/TeX) when we decide to make PDF of Lily > > docs translation. > > > > Well, you can safely ignore these warnings. > > > > See also > > http://lists.gnu.org/archive/html/lilypond-devel/2007-01/msg00047.html > > Tried cvs version [1] of texinfo/makeinfo > > $ makeinfo --version > makeinfo (GNU texinfo) 4.8.90 > > But the warning persist. Well, never mind. > > Regards > /Karl > > [1] http://savannah.gnu.org/cvs/?group=texinfo This is fixed in latest texinfo cvs: Karl Berry: > I just added UTF-8 to the list of encoding names recognized by makeinfo > (from CVS). It just passes through the bytes as they are received, > which hopefully will be better than nothing. I can't undertake to > actually parse UTF-8 at this point (I added it to the TODO file :). > > Thanks, > Karl Regards /Karl ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: makeinfo with utf-8 support
[EMAIL PROTECTED]: > > Tried cvs version [1] of texinfo/makeinfo > > > > $ makeinfo --version > > makeinfo (GNU texinfo) 4.8.90 > > > > But the warning persist. Well, never mind. > > Please report this to bug-texinfo, together with a small example (if > possible). Done. Regards /Karl ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: makeinfo with utf-8 support
> Tried cvs version [1] of texinfo/makeinfo > > $ makeinfo --version > makeinfo (GNU texinfo) 4.8.90 > > But the warning persist. Well, never mind. Please report this to bug-texinfo, together with a small example (if possible). Werner ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: makeinfo with utf-8 support
[EMAIL PROTECTED]: > Le jeudi 04 janvier 2007 à 00:33 +0100, Karl Hammar a écrit : > > Hmm, when building I get: > > > > out/lilypond.nexi:62: warning: unrecognized encoding name `utf-8'. ... > > Does anybody know where the makeinfo with utf-8 support is, a patch ? > > AFAIK Texinfo does no character encoding conversion for the Info and > HTML output, so the LilyPond devels have decided to use the modern > character set UTF-8, not Latin1. This will really become a problem for > the PDF (outputted by Texinfo/TeX) when we decide to make PDF of Lily > docs translation. > > Well, you can safely ignore these warnings. > > See also > http://lists.gnu.org/archive/html/lilypond-devel/2007-01/msg00047.html Tried cvs version [1] of texinfo/makeinfo $ makeinfo --version makeinfo (GNU texinfo) 4.8.90 But the warning persist. Well, never mind. Regards /Karl [1] http://savannah.gnu.org/cvs/?group=texinfo ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: makeinfo with utf-8 support
Le jeudi 04 janvier 2007 à 00:33 +0100, Karl Hammar a écrit : > Hmm, when building I get: > > out/lilypond.nexi:62: warning: unrecognized encoding name `utf-8'. > out/lilypond-internals.nexi:10: warning: unrecognized encoding name `utf-8'. > out/music-glossary.nexi:6: warning: unrecognized encoding name `utf-8'. > out/INSTALL.texi:6: warning: unrecognized encoding name `utf-8'. > out/README.texi:6: warning: unrecognized encoding name `utf-8'. > > I've got: > > $ makeinfo --version > makeinfo (GNU texinfo) 4.8 > > The latest texinfo at http://ftp.gnu.org/gnu/texinfo/ seems to be too old. > Does anybody know where the makeinfo with utf-8 support is, a patch ? AFAIK Texinfo does no character encoding conversion for the Info and HTML output, so the LilyPond devels have decided to use the modern character set UTF-8, not Latin1. This will really become a problem for the PDF (outputted by Texinfo/TeX) when we decide to make PDF of Lily docs translation. Well, you can safely ignore these warnings. See also http://lists.gnu.org/archive/html/lilypond-devel/2007-01/msg00047.html Greetings -- John Mandereau <[EMAIL PROTECTED]> ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
makeinfo with utf-8 support
Hmm, when building I get: out/lilypond.nexi:62: warning: unrecognized encoding name `utf-8'. out/lilypond-internals.nexi:10: warning: unrecognized encoding name `utf-8'. out/music-glossary.nexi:6: warning: unrecognized encoding name `utf-8'. out/INSTALL.texi:6: warning: unrecognized encoding name `utf-8'. out/README.texi:6: warning: unrecognized encoding name `utf-8'. I've got: $ makeinfo --version makeinfo (GNU texinfo) 4.8 The latest texinfo at http://ftp.gnu.org/gnu/texinfo/ seems to be too old. Does anybody know where the makeinfo with utf-8 support is, a patch ? Regards /Karl ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
