X-Git-Url: https://git.stg.codes/stg.git/blobdiff_plain/bfec9cc7ab5a396f7662090b208691ec59a69f1b..2f1753cc3e240fa497a87873ed19fe3f11e22331:/doc/help/xslt/params/man.output.encoding.xml diff --git a/doc/help/xslt/params/man.output.encoding.xml b/doc/help/xslt/params/man.output.encoding.xml deleted file mode 100644 index 7154bc87..00000000 --- a/doc/help/xslt/params/man.output.encoding.xml +++ /dev/null @@ -1,53 +0,0 @@ - - -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. - - - -