bug-texinfo
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: url protection


From: Patrice Dumas
Subject: Re: url protection
Date: Fri, 5 Aug 2022 13:45:07 +0200

On Fri, Aug 05, 2022 at 09:15:06AM +0300, Eli Zaretskii wrote:
> > From: Gavin Smith <gavinsmith0123@gmail.com>
> > Date: Thu, 4 Aug 2022 20:34:01 +0100
> > 
> > On 8/4/22, Eli Zaretskii <eliz@gnu.org> wrote:
> > >
> > > Isn't the main issue here about encoding _file_names_, and the
> > > encoding of HTML is secondary?  I mean file names we produce from
> > > Texinfo sources, for files that are part of the output from texi2any
> > > processing.
> > >
> > Not for creating files, referring to them from within an HTML file.
> 
> So you mean the HTML file will have these file names encoded in UTF-8,
> while the file itself will be created using the locale's encoding?

That's a possibility.

> This should work, but it needs careful programming, because not every
> low-level function that manipulates file names knows the purpose of
> the file name, so it won't necessarily know which encoding to apply
> (assuming that internally we are going to keep file names in UTF-8).

Indeed, there could be some inconsistencies.  In texi2any, the input
file content encoding, input file names encoding, output file content
encoding and output file name encoding can all be set independently,
athugh, in the default case they depend on each other, or on the
locale encoding.

There could be some inconsistencies, but it is still not fully clear
to me what the real cases are.  The objective would be to have good
defaults.  We already have made possible to flexibly set everything,
but it would be much better if the defaults were right (though we will
not be able to please everyone...).

-- 
Pat



reply via email to

[Prev in Thread] Current Thread [Next in Thread]