[Scummvm-devel] Using non-ascii characters in our source, and in filenames
Travis Howell
kirben at optusnet.com.au
Sun Mar 19 22:08:02 CET 2006
From: "Max Horn" <max at quendi.de>
> The second issue is much harder to resolve. We could for example demand
> that all our backends provide file system operations that use a
> particular encoding (e.g. UTF-8). But that's probably not realistic
> anyway. Right now, we managed fine, because paths/file names were either
> pure ASCII, or were fixed to a single computer, so which encoding was
> used was totally irrelevant.
> Hence the alternative to requiring a fixed encoding is to ignore the
> matter, and simply let Töff-Töff remain unsupported (at least, not
> supported w/o manual work) on systems that use a different encoding.
Would be best to just ignore the matter, as people on systems using
difference encoding, can easily rename the demo's files. It definately isn't
worth the required back ends changes for ports, just for this one demo.
More information about the Scummvm-devel
mailing list