mirror of
https://github.com/facebook/sapling.git
synced 2024-10-10 16:57:49 +03:00
044fa1649f
When a topic provides a callable method for its text, most likely this text will be generated from different parts, so it does not make sense to apply gettext on the whole result, rather the method should provide translation by itself. This is the case with the extensions topic, which triggers a double gettext call, making the ASCII codec fail when it encounters 8 bit characters, and prevents the documentation from being built. |
||
|---|---|---|
| .. | ||
| ja | ||
| gendoc.py | ||
| hg.1.txt | ||
| hgignore.5.txt | ||
| hgrc.5.txt | ||
| Makefile | ||
| README | ||
Mercurial's documentation is currently kept in ASCIIDOC format, which is a simple plain text format that's easy to read and edit. It's also convertible to a variety of other formats including standard UNIX man page format and HTML. To do this, you'll need to install ASCIIDOC: http://www.methods.co.nz/asciidoc/ To generate the man page: asciidoc -d manpage -b docbook hg.1.txt xmlto man hg.1.xml To display: groff -mandoc -Tascii hg.1 | more To create the html page (without stylesheets): asciidoc -b html4 hg.1.txt (older asciidoc may want html instead of html4 above)