On Mon, Oct 24, 2022 at 10:26:16PM +0300, Eli Zaretskii wrote: > > Date: Mon, 24 Oct 2022 21:03:38 +0200 > > From: [email protected] > > Cc: [email protected], [email protected] > > > > > I've added debugging printouts and ran the above command. What I see > > > is that encode_file_name doesn't encode the file name at all, so it > > > stays in its UTF-8 encoding, and the 'stat' in locate_include_file > > > cannot find a file by that name. The reason encode_file_name doesn't > > > encode is that reverse_iconv is zero at entry to encode_file_name, and > > > all of input_file_name_encoding, doc_encoding_for_input_file_name, and > > > > input_file_name_encoding should be the string "ISO-8859-1", I checked > > that it is the case for me. > > Btw, input_encoding_name inside encode_file_name is "iso-8859-1" > (lower-case). This comes from @documentencoding, right?
Yes, we tend to lower-case encoding names upon reading and before comparing encoding names, because the lower case encodings are what appears in general in diverse outputs, like HTML, LaTeX... -- Pat
