PlaneteCasio
/
libc
1
0
Fork 0
Code Issues 6 Pull Requests Releases Wiki Activity

* setup2.sgml (setup-locale-problems): Fix an incomplete sentence.

This commit is contained in:
Corinna Vinschen 2009-03-31 11:17:08 +00:00
parent 7ccfe2c70e
commit 83fb2c849c
2 changed files with 8 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
winsup/doc/ChangeLog
View File

@ -1,3 +1,7 @@
2009-03-31 Corinna Vinschen <corinna@vinschen.de>
* setup2.sgml (setup-locale-problems): Fix an incomplete sentence.
2009-03-31 Corinna Vinschen <corinna@vinschen.de>
* faq-using.xml (faq.using.unicode): Modernize.

7
winsup/doc/setup2.sgml
View File

@ -280,9 +280,10 @@ of <envar>LC_ALL</envar>, <envar>LC_CTYPE</envar>, or <envar>LANG</envar>,
is to use the current Windows ANSI codepage.</para>
<para>As long as the environment only contains ASCII characters, this is
no problem. But if it does, 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 <envar>PATH</envar>.</para>
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
<envar>PATH</envar>.</para>
<note><para>Per POSIX, the name of an environment variable should only
consist of valid ASCII characters, and only of uppercase letters, digits, and