bug-texinfo
[Top][All Lists]
Advanced

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

Re: put invalid encoded file name for another locale in Makefile for DIS


From: Gavin Smith
Subject: Re: put invalid encoded file name for another locale in Makefile for DIST
Date: Fri, 4 Mar 2022 18:23:50 +0000

On Fri, Mar 04, 2022 at 08:34:36AM +0100, Patrice Dumas wrote:
> Hello,
> 
> For some tests I use an include file with name encoded in ISO-8859-1 
> to be included from a manual encoded in ISO-8859-1.  The manual is
> tp/tests/other/manual_include_accented_file_name_latin1.texi, the
> include file is tp/tests/'included_lat'$'\356''n1.texi' as reported
> by ls in my utf8 encoded locale, and included_latîn1.texi in the FR_fr
> locale.
> 
> I have trouble including the included_latîn1.texi file encoded in latin1
> in the Makefile.am EXTRA_DIST variable.  I tried included_lat\3561.texi
> or $(wildcard included_lat*n1.texi) but it does not work.  Does anybody
> knows how to do that, and, if possible, portably?
> 
> (I should probably also use it for the utf8 encoded file name that is
> already in EXTRA_DIST for those who are in a non utf8 locale).

You could try putting the filename in Makefile.am using a text editor
that could insert these bytes, perhaps using an 8-bit locale.

However, this might not be a good idea and could easily cause problems
(for example for the next person who tries to edit that file).
My preference would be to keep Makefile.am a purely UTF-8 or even
ASCII file.  (This would avoid us having to contend with encoding
issues in Automake as well as in Texinfo.)

If we really want to test these inputs, bespoke test scripts could be written
that create the files with ISO-8859-1-encoded names when they are run.



reply via email to

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