From: Peter Dimov (pdimov_at_[hidden])
Date: 2019-09-17 13:16:58
Rainer Deyke wrote:
> Or the user could be running a non-UTF-8 locale, but accessing a
> filesystem created by somebody who was using UTF-8 - in which case any
> filenames should be in UTF-8, even if the user's locale disagrees.
> It is because of this last possibility that I recommend treating all
> command-line arguments as UTF-8 on Unix systems, even if running a
> non-UTF-8 locale, for all cases where treating them as binary blobs is
> impractical. Unix filenames are binary blobs, but the de-facto standard
> for interpreting these binary blobs as text is to use UTF-8. [...]
How does any of this affect the library? It just gives you whatever you
passed as `argv`, without needing to interpret it.
Windows is a different story.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk