You don't need to worry about non-ASCII characters on the Linux side of
things. Almost all file systems and tooling on almost all distros will
handle almost any Unicode UTF-8 characters in filenames and paths just
fine. The only thing you need to watch out for typically are spaces (can be
used, but
Y'all:
I cannot speak with respect to any particular software or other distros,
but Debian is just fine with any UTF-8 character in file and directory
names, including special symbols, Greek, Hebrew, Cryllic.
Hope this helps.
Tom Sullivan
i...@beforgiven.info
FAX: 815-301-2835
--
Lateral thoughts
How might a build work or fail if the SWORD path contains any non-ASCII
characters?
This is certainly conceivable for Windows users whose locale is not English.
I cannot speak for Linux users.
Best regards,
David
Sent from ProtonMail Mobile
On Wed, Apr 8, 2020 at 09:17,
So there's a two-fold failure during compile when handling paths with
spaces.
The first is that the build fails when the code is in a path that has
spaces in it. This is because instances of "-I${some_foo}/include" in
autotools are not wrapped with quotation marks.
The second is when you invoke:
