* setup2.sgml (setup-locale-problems): Fix an incomplete sentence.
This commit is contained in:
parent
7ccfe2c70e
commit
83fb2c849c
|
@ -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.
|
||||
|
|
|
@ -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
|
||||
|
|
Loading…
Reference in New Issue