diff options
Diffstat (limited to 'winsup/doc/setup2.sgml')
| -rw-r--r-- | winsup/doc/setup2.sgml | 11 |
1 files changed, 7 insertions, 4 deletions
diff --git a/winsup/doc/setup2.sgml b/winsup/doc/setup2.sgml index a1175939b..3ed1f2ad2 100644 --- a/winsup/doc/setup2.sgml +++ b/winsup/doc/setup2.sgml @@ -317,12 +317,15 @@ variable hasn't been set <emphasis>before</emphasis> starting this process, Cygwin has to make an educated guess which charset to use to convert the environment itself. The only reproducible way to do that in the absence of <envar>LC_ALL</envar>, <envar>LC_CTYPE</envar>, or <envar>LANG</envar>, -is to use the current Windows ANSI codepage.</para> +is to use the "C" locale. The default conversion in the "C" locale +used by Cygwin internally is UTF-8. So, in the absence of any +internationalization environment variable, the environment will be converted +to UTF-8.</para> <para>As long as the environment only contains ASCII characters, this is -no problem. But if it contains native characters, and you're planning -to use, say, UTF-8, the environment will result in invalid characters in -the UTF-8 charset. This would be especially a problem in variables like +no problem at all. But if it contains native characters, and you're planning +to use, say, GBK, the environment will result in invalid characters in +the GBK charset. This would be especially a problem in variables like <envar>PATH</envar>.</para> <note><para>Per POSIX, the name of an environment variable should only |