From 83fb2c849c7834d98da00886332a19c20b39ac27 Mon Sep 17 00:00:00 2001 From: Corinna Vinschen Date: Tue, 31 Mar 2009 11:17:08 +0000 Subject: [PATCH] * setup2.sgml (setup-locale-problems): Fix an incomplete sentence. --- winsup/doc/ChangeLog | 4 ++++ winsup/doc/setup2.sgml | 7 ++++--- 2 files changed, 8 insertions(+), 3 deletions(-) diff --git a/winsup/doc/ChangeLog b/winsup/doc/ChangeLog index 830a233c1..dd973d100 100644 --- a/winsup/doc/ChangeLog +++ b/winsup/doc/ChangeLog @@ -1,3 +1,7 @@ +2009-03-31 Corinna Vinschen + + * setup2.sgml (setup-locale-problems): Fix an incomplete sentence. + 2009-03-31 Corinna Vinschen * faq-using.xml (faq.using.unicode): Modernize. diff --git a/winsup/doc/setup2.sgml b/winsup/doc/setup2.sgml index f03725b7f..02737ff2a 100644 --- a/winsup/doc/setup2.sgml +++ b/winsup/doc/setup2.sgml @@ -280,9 +280,10 @@ of LC_ALL, LC_CTYPE, or LANG, is to use the current Windows ANSI codepage. 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 PATH. +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 +PATH. Per POSIX, the name of an environment variable should only consist of valid ASCII characters, and only of uppercase letters, digits, and