aboutsummaryrefslogtreecommitdiff
path: root/test/command/ascii.md
AgeCommit message (Collapse)AuthorFilesLines
2018-11-05CommonMark writer: respect --ascii (#5043)quasicomputational1-0/+36
2018-11-04XML: toHtml5Entities: prefer shorter entities...John MacFarlane1-2/+2
when there are several choices for a particular character.
2018-11-01Implement --ascii for Markdown writer.John MacFarlane1-0/+8
2018-11-01HTML writer: use character entities references when possible for HTML5.John MacFarlane1-1/+1
2018-10-18Groff escaping changes.John MacFarlane1-2/+2
- `--ascii` is now turned on automatically for man output, for portability. All man output will be escaped to ASCII. - In T.P.Writers.Groff, `escapeChar`, `escapeString`, and `escapeCode` now take a boolean parameter that selects ascii-only output. This is used by the Ms writer for `--ascii`, instead of doing an extra pass after writing the document. - In ms output without `--ascii`, unicode is used whenever possible (e.g. for double quotes). - A few escapes are changed: e.g. `\[rs]` instead of `\\` for backslash, and `\ga]` instead of `` \` `` for backtick.
2018-09-30Implement `--ascii` (`writerPreferAscii`) in writers, not App.John MacFarlane1-0/+45
Now the `write*` functions for Docbook, HTML, ICML, JATS, Man, Ms, OPML are sensitive to `writerPreferAscii`. Previously the to-ascii translation was done in Text.Pandoc.App, and thus not available to those using the writer functions directly. In addition, the LaTeX writer is now sensitive to `writerPreferAscii` and to `--ascii`. 100% ASCII output can't be guaranteed, but the writer will use commands like `\"{a}` and `\l` whenever possible, to avoid emiting a non-ASCII character. A new unexported module, Text.Pandoc.Groff, has been added to store functions used in the different groff-based writers.