rust/src/doc
bors da796ededa auto merge of #16635 : steveklabnik/rust/ordering_comment, r=huonw
This way people won't try to copy/paste it in.

This is provided as an alternate solution to #16003. What do you think, @treeman?
2014-08-21 21:25:56 +00:00
..
complement-bugreport.md
complement-design-faq.md doc: grammar fixes 2014-08-20 01:31:07 +02:00
complement-lang-faq.md
complement-project-faq.md
favicon.inc
footer.inc
full-toc.inc
guide-container.md
guide-ffi.md Fix FFI guide 2014-08-21 12:58:42 -04:00
guide-lifetimes.md
guide-macros.md
guide-pointers.md Make variable mutable to allow mutable reference 2014-08-19 15:41:12 -05:00
guide-runtime.md guide-runtime.md: remove redundant verb 2014-08-12 07:39:53 +02:00
guide-strings.md
guide-tasks.md doc: small tasks guide improvements 2014-08-20 01:34:41 +02:00
guide-testing.md guide-testing.md: add auxiliary verb 2014-08-12 07:39:56 +02:00
guide-unsafe.md doc: grammar fixes 2014-08-20 01:31:07 +02:00
guide.md auto merge of #16635 : steveklabnik/rust/ordering_comment, r=huonw 2014-08-21 21:25:56 +00:00
index.md
intro.md
not_found.md
po4a.conf
README.md Changed the sample command in the Rustdoc readme to use --output instead of the outdated --output-dir and 2014-08-17 14:01:26 -07:00
rust.css
rust.md manual: fix link 2014-08-20 21:02:23 -04:00
rustdoc.md
tutorial.md libsyntax: Remove the use foo = bar syntax from the language in favor 2014-08-18 09:19:10 -07:00
version_info.html.template

Dependencies

Pandoc, a universal document converter, is required to generate docs as HTML from Rust's source code.

po4a is required for generating translated docs from the master (English) docs.

GNU gettext is required for managing the translation data.

Building

To generate all the docs, just run make docs from the root of the repository. This will convert the distributed Markdown docs to HTML and generate HTML doc for the 'std' and 'extra' libraries.

To generate HTML documentation from one source file/crate, do something like:

rustdoc --output html-doc/ --output-format html ../src/libstd/path.rs

(This, of course, requires a working build of the rustdoc tool.)

Additional notes

To generate an HTML version of a doc from Markdown manually, you can do something like:

pandoc --from=markdown --to=html5 --number-sections -o rust.html rust.md

(rust.md being the Rust Reference Manual.)

The syntax for pandoc flavored markdown can be found at: http://johnmacfarlane.net/pandoc/README.html#pandocs-markdown

A nice quick reference (for non-pandoc markdown) is at: http://kramdown.rubyforge.org/quickref.html

Notes for translators

Notice: The procedure described below is a work in progress. We are working on translation system but the procedure contains some manual operations for now.

To start the translation for a new language, see po4a.conf at first.

To generate .pot and .po files, do something like:

po4a --copyright-holder="The Rust Project Developers" \
    --package-name="Rust" \
    --package-version="0.11.0" \
    -M UTF-8 -L UTF-8 \
    src/doc/po4a.conf

(the version number must be changed if it is not 0.11.0 now.)

Now you can translate documents with .po files, commonly used with gettext. If you are not familiar with gettext-based translation, please read the online manual linked from http://www.gnu.org/software/gettext/ . We use UTF-8 as the file encoding of .po files.

When you want to make a commit, do the command below before staging your change:

for f in src/doc/po/**/*.po; do
    msgattrib --translated $f -o $f.strip
    if [ -e $f.strip ]; then
       mv $f.strip $f
    else
       rm $f
    fi
done

This removes untranslated entries from .po files to save disk space.