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 they must be escaped or the paths quoted), quote marks (can screw with poorly implemented quoting of spaces), null characters, newlines (technically valid in filenames, but many scripts forget this and they tend to break), backslashes (also valid, but tend to confuse people escaping them). It's also valid but unpleasant when filenames begin with a dash or semicolon because these make it hard to use filenames as arguments.
Besides those ASCII issues, non ASCII localized path and filenames are pretty much a non-issue. On Mon, Apr 13, 2020 at 12:31 PM David Haslam <dfh...@protonmail.com> wrote: > 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. >
_______________________________________________ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page