Re: generating Info encoded in UTF-8 only
Eli Zaretskii <[email protected]>
| Newsgroups | gmane.comp.tex.texinfo.bugs |
|---|---|
| Message-ID | <[email protected]> |
> Date: Fri, 14 Aug 2026 14:03:05 +0200 > From: Patrice Dumas <[email protected]> > Cc: [email protected] > > On Fri, Aug 14, 2026 at 02:07:10PM +0300, Eli Zaretskii wrote: > > > Date: Fri, 14 Aug 2026 10:11:46 +0200 > > > From: Patrice Dumas <[email protected]> > > > > > > Hello, > > > > > > I propose to generate Info encoded in UTF-8 only from texi2any. > > > > I'm not sure I understand what are the alternatives. Can you spell > > them out? > > The alternative would be, as of today > * to use the @documentencoding > * to take into account OUTPUT_ENCODING_NAME to override the output > encoding > > > I also don't think I understand fully what you mean by "generate Info > > encoded in UTF-8". Surely, the encoding of the Info file depends on > > @documentencoding, doesn't it? Or what am I missing? > > Right now, this is the case, but my proposal is to generate the Info > file encoded in UTF-8 irrespective of the @documentencoding or > OUTPUT_ENCODING_NAME. So it becomes impossible to control the encoding of the Info file by any specification in the Texinfo source? Why is that a good idea? I don't understand why the current situation, where we use @documentencoding, is a problem.