From e7268547cb8eda347875904ce40ced698f751e3e Mon Sep 17 00:00:00 2001
From: joshuadfranklin <joshuadfranklin>
Date: Mon, 3 Feb 2003 00:30:45 +0000
Subject: [PATCH] * cygwinenv.sgml: Add section for 'CYGWIN
 codepage:[ansi|oem]'

---
 winsup/doc/cygwinenv.sgml | 17 +++++++++++++++++
 winsup/doc/dll.sgml       |  7 ++++++-
 winsup/utils/utils.sgml   |  9 +++++++++
 3 files changed, 32 insertions(+), 1 deletion(-)

diff --git a/winsup/doc/cygwinenv.sgml b/winsup/doc/cygwinenv.sgml
index c8c00f9148..c78299e5ee 100644
--- a/winsup/doc/cygwinenv.sgml
+++ b/winsup/doc/cygwinenv.sgml
@@ -50,6 +50,23 @@ case" error.</para>
 </listitem>
 </itemizedlist>
 </listitem>
+
+<listitem>
+<para><FirstTerm>codepage:[ansi|oem]</FirstTerm> - Windows console 
+applications can use different character sets (codepages) for drawing
+characters.  The first setting, called "ansi", is the default.
+This character set contains various forms of latin characters used
+in European languages.  The name originates from the ANSI Latin1
+(ISO 8859-1) standard, used in Windows 1.0, though the character
+sets have since diverged from any standard.  The second setting
+selects an older, DOS-based character set, containing various line
+drawing and special characters.  It is called "oem" since it was
+originally encoded in the firmware of IBM PCs by original
+equipment manufacturers (OEMs).  If you find that some characters 
+(especially non-US or 'graphical' ones) do not display correctly in 
+Cygwin, you can use this option to select an appropriate codepage.
+</listitem>
+
 <listitem>
 <para><FirstTerm>(no)envcache</FirstTerm> - If set, environment variable
 conversions (between Win32 and POSIX) are cached.  Note that this is may
diff --git a/winsup/doc/dll.sgml b/winsup/doc/dll.sgml
index d5d8a2f13c..7bb10829c6 100644
--- a/winsup/doc/dll.sgml
+++ b/winsup/doc/dll.sgml
@@ -32,7 +32,12 @@ information needed to tell the OS how your program interacts with
 
 <sect2 id="dll-build"><title>Building DLLs</title>
 
-<para>OK, let's go through a simple example of how to build a dll.
+<para>This page gives only a few simple examples of gcc's DLL-building 
+capabilities. To begin an exploration of the many additional options,
+see the gcc documentation and website, currently at 
+<ulink URL="http://gcc.gnu.org/">http://gcc.gnu.org/</ulink>
+
+<para>Let's go through a simple example of how to build a dll.
 For this example, we'll use a single file
 <filename>myprog.c</filename> for the program
 (<filename>myprog.exe</filename>) and a single file
diff --git a/winsup/utils/utils.sgml b/winsup/utils/utils.sgml
index e98c2db434..131b0a56d3 100644
--- a/winsup/utils/utils.sgml
+++ b/winsup/utils/utils.sgml
@@ -843,6 +843,9 @@ Options for 'set' Action:
  -m, --multi-string   set type to REG_MULTI_SZ
  -s, --string         set type to REG_SZ
 
+Options for 'set' and 'unset' Actions:
+ -K&lt;c&gt;, --key-separator[=]&lt;c&gt;  set key separator to &lt;c&gt; instead of '\'
+
 Other Options:
  -h, --help     output usage information and exit
  -q, --quiet    no error output, just nonzero return if KEY/VALUE missing
@@ -916,6 +919,12 @@ a regular string.
 The <literal>unset</literal> action removes a value from a key.
 </para>
 
+<para>
+By default, the last "\" or "/" is assumed to be the separator between the
+key and the value.  You can use the <literal>-K</literal> option to provide 
+an alternate key/value separator character.
+</para>
+
 </sect2>
 
 <sect2 id="setfacl"><title>setfacl</title>
-- 
2.11.0