Updated man page and README.
Pandoc no longer respects locale, even when compiled by GHC 6.12.
This commit is contained in:
parent
d6dd5fff7b
commit
fb201a5b46
2 changed files with 3 additions and 6 deletions
4
README
4
README
|
@ -116,9 +116,7 @@ Character encodings
|
|||
-------------------
|
||||
|
||||
All input is assumed to be in the UTF-8 encoding, and all output
|
||||
is in UTF-8 (unless your version of pandoc was compiled using
|
||||
GHC 6.12 or higher, in which case the local encoding will be used).
|
||||
If your local character encoding is not UTF-8 and you use
|
||||
is in UTF-8. If your local character encoding is not UTF-8 and you use
|
||||
accented or foreign characters, you should pipe the input and output
|
||||
through [`iconv`]. For example,
|
||||
|
||||
|
|
|
@ -53,9 +53,8 @@ markdown: the differences are described in the *README* file in
|
|||
the user documentation. If standard markdown syntax is desired, the
|
||||
`--strict` option may be used.
|
||||
|
||||
Pandoc uses the UTF-8 character encoding for both input and output
|
||||
(unless compiled with GHC 6.12 or higher, in which case it uses
|
||||
the local encoding). If your local character encoding is not UTF-8, you
|
||||
Pandoc uses the UTF-8 character encoding for both input and output.
|
||||
If your local character encoding is not UTF-8, you
|
||||
should pipe input and output through `iconv`:
|
||||
|
||||
iconv -t utf-8 input.txt | pandoc | iconv -f utf-8
|
||||
|
|
Loading…
Reference in a new issue