[FFmpeg-devel] [PATCH] configure's to_lower and to_upper fix on *bsd

Rich Felker dalias
Tue Feb 12 05:32:23 CET 2008

On Tue, Feb 12, 2008 at 12:39:53AM +0100, Reimar D?ffinger wrote:
> Hello,
> On Mon, Feb 11, 2008 at 06:28:34PM -0500, Rich Felker wrote:
> > On Tue, Feb 12, 2008 at 12:18:04AM +0100, Diego Biurrun wrote:
> > > I'm tempted to set
> > > 
> > > LC_ALL=C
> > > 
> > > in the beginning of configure similar to what MPlayer's configure does.
> > 
> > I wonder if this could have any ill effects when the build path or any
> > library/include paths contains non-ascii characters.
> Hm. Why should it matter? Shouldn't (in theory at least) everything
> treat the file name as 0-terminated binary data?

There is no specification of this; it's only historical practice and
it makes it rather impossible to have multiple locales with different
charset coexisting peacefully on a system. A much smarter approach to
system implementation would be to always use a Unicode-based internal
filename encoding, and translate locale-specific encodings to that.
Even better would be to only support UTF-8, of couse. :)

Surely on Windows, the locale matters to accessing the filesystem..

> In general the locale
> does not guarantee that the filename are in a specific encoding, if
> nothing else you might have mounted a disk from a different PC for
> recovery, having a look at someone else's home or whatever...

Indeed this is the way most systems work, but it's broken for an
application to expect that it can override the locale with no ill

> What I do know though is that on my 32 bit system ICC does not
> run at all because out of laziness I still have de_DE as locale but the
> locale data for that is not installed - no idea why it is so essential
> to ICC though...



More information about the ffmpeg-devel mailing list