From 46c1de5bf7ec3eea686534d215fb49ef079a43b4 Mon Sep 17 00:00:00 2001 From: Joshua Daniel Franklin Date: Mon, 3 Feb 2003 00:30:45 +0000 Subject: * cygwinenv.sgml: Add section for 'CYGWIN codepage:[ansi|oem]' --- winsup/doc/cygwinenv.sgml | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) (limited to 'winsup/doc/cygwinenv.sgml') diff --git a/winsup/doc/cygwinenv.sgml b/winsup/doc/cygwinenv.sgml index c8c00f914..c78299e5e 100644 --- a/winsup/doc/cygwinenv.sgml +++ b/winsup/doc/cygwinenv.sgml @@ -50,6 +50,23 @@ case" error. + + +codepage:[ansi|oem] - 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. + + (no)envcache - If set, environment variable conversions (between Win32 and POSIX) are cached. Note that this is may -- cgit v1.2.3