[fpc-pascal] FPC 3: disabling automatic AnsiString codepage conversionx

Jonas Maebe jonas.maebe at elis.ugent.be
Mon Apr 4 13:10:38 CEST 2016


tobiasgiesen wrote on Mon, 04 Apr 2016:

>> How did you get a codepage 20127 Mac?
>
> The Mac is UTF-8,

This statement makes no sense. There is no "UTF-8" or "non-UTF-8" Mac.  
The Unix environment on OS X can use any OS-supported code page.

> but cwstring or whatever does not realize it.

cwstring simply sets the code page based on how it is defined in your  
environment.

> Terminal has LC_CTYPE=UTF-8.

What about LC_ALL? LC_ALL overrides LC_CTYPE, because that is how the  
meaning of these environment variables is defined by POSIX (see e.g.  
http://pubs.opengroup.org/onlinepubs/7908799/xbd/envvar.html )

> Well I will just set the default codepages manually.

Then you will probably be back in a few months with another message  
complaining how FPC 3.0 supposedly breaks X or Y, because you are  
merely hiding the real issue (e.g. when calling an external program,  
which may then try to interpret your UTF-8 command line arguments as  
plain ASCII).


Jonas



More information about the fpc-pascal mailing list