> From: Gavin Smith <[email protected]> > Date: Sun, 20 Feb 2022 14:48:39 +0000 > Cc: Patrice Dumas <[email protected]>, [email protected], > [email protected] > > > what if the argument of -I is in some non-UTF-8 encoding, and the > > source uses @include with a non-ASCII file name encoded according > > top @documentencoding, which is UTF-8? You need to construct a > > complete file name from 2 parts that are encoded differently. > > The byte sequences are just concatenated and used as the path to the file, > even if it's not validly encoded. This shouldn't cause a problem.
It will cause problems if the file names are encoded in something other than UTF-8. Users on GNU/Linux can do that quite easily.
