From 140d836e9cd54fb67b969fd82ef7ed19ba574d40 Mon Sep 17 00:00:00 2001 From: Luca Falavigna Date: Sat, 26 Apr 2014 15:11:58 +0200 Subject: Imported Upstream version 2.3.1 --- .../params/man.output.encoding.xml | 53 ++++++++++++++++++++++ 1 file changed, 53 insertions(+) create mode 100644 src/engine/SCons/Tool/docbook/docbook-xsl-1.76.1/params/man.output.encoding.xml (limited to 'src/engine/SCons/Tool/docbook/docbook-xsl-1.76.1/params/man.output.encoding.xml') diff --git a/src/engine/SCons/Tool/docbook/docbook-xsl-1.76.1/params/man.output.encoding.xml b/src/engine/SCons/Tool/docbook/docbook-xsl-1.76.1/params/man.output.encoding.xml new file mode 100644 index 0000000..7154bc8 --- /dev/null +++ b/src/engine/SCons/Tool/docbook/docbook-xsl-1.76.1/params/man.output.encoding.xml @@ -0,0 +1,53 @@ + + +man.output.encoding +string + + +man.output.encoding +Encoding used for man-page output + + + + +UTF-8 + + + +Description + +This parameter specifies the encoding to use for files generated +by the manpages stylesheet. Not all processors support specification +of this parameter. + + + If the value of the man.charmap.enabled + parameter is non-zero (the default), keeping the + man.output.encoding parameter at its default + value (UTF-8) or setting it to + UTF-16 does not cause your + man pages to be output in raw UTF-8 or UTF-16 -- because + any Unicode characters for which matches are found in the enabled + character map will be replaced with roff escape sequences before the + final man-page files are generated. + + So if you want to generate "real" UTF-8 man pages, without any + character substitution being performed on your content, you need to + set man.charmap.enabled to zero (which will + completely disable character-map processing). + + You may also need to set + man.charmap.enabled to zero if you want to + output man pages in an encoding other than UTF-8 + or UTF-16. Character-map processing is based on + Unicode character values and may not work with other output + encodings. + + + + -- cgit v1.2.3