rust/src/doc
Steve Klabnik a55c508db6 Guide: variable bindings.
Whew! Who knew there was so much to say about variables.

We probably want to move the guessing game to the rust-lang org, rather than
just having it on my GitHub. Or, I could put the code inline. I think it'd be
neat to have it as a project, so people can pull it down with Cargo. Until we
make that decision, I'll just leave this here.
2014-07-01 20:27:37 -04:00
..
po/ja Update repo location 2014-06-16 18:16:36 -07:00
complement-bugreport.md Update repo location 2014-06-16 18:16:36 -07:00
complement-design-faq.md Update repo location 2014-06-16 18:16:36 -07:00
complement-lang-faq.md Update repo location 2014-06-16 18:16:36 -07:00
complement-project-faq.md doc: Modernize FAQs just slightly 2014-02-08 00:38:00 -08:00
favicon.inc core: rename strbuf::StrBuf to string::String 2014-05-24 21:48:10 -07:00
footer.inc rustdoc: Submit examples to play.rust-lang.org 2014-06-06 20:00:16 -07:00
full-toc.inc doc: add webfonts and tweak the styles accordingly 2014-04-19 21:25:35 +09:00
guide-container.md librustc: Remove the fallback to int from typechecking. 2014-06-24 17:18:48 -07:00
guide-ffi.md Rename all raw pointers as necessary 2014-06-28 11:53:58 -07:00
guide-lifetimes.md librustc: Remove the fallback to int from typechecking. 2014-06-24 17:18:48 -07:00
guide-macros.md looks like a cut-n-paste error in unused code 2014-06-27 22:11:11 -07:00
guide-pointers.md librustc: Remove the fallback to int from typechecking. 2014-06-24 17:18:48 -07:00
guide-runtime.md Rename all raw pointers as necessary 2014-06-28 11:53:58 -07:00
guide-tasks.md sync: Move underneath libstd 2014-06-11 10:00:43 -07:00
guide-testing.md librustc: Remove the fallback to int from typechecking. 2014-06-24 17:18:48 -07:00
guide-unsafe.md librustc: Remove the fallback to int for integers and f64 for 2014-06-29 11:47:58 -07:00
guide.md Guide: variable bindings. 2014-07-01 20:27:37 -04:00
index.md Remove the cheat sheet. 2014-06-24 17:22:39 -07:00
intro.md librustc: Remove the fallback to int for integers and f64 for 2014-06-29 11:47:58 -07:00
not_found.md Change static.rust-lang.org to doc.rust-lang.org 2014-05-21 19:55:39 -07:00
po4a.conf Update po4a.conf and regenerate .po files. 2014-02-03 08:23:34 +09:00
README.md Add the patch number to version strings. Closes #13289 2014-05-12 19:52:29 -07:00
rust.css doc: Fix margins around tables of contents 2014-06-19 16:14:49 -07:00
rust.md librustc: Remove the fallback to int for integers and f64 for 2014-06-29 11:47:58 -07:00
rustdoc.md Allow external html in rustdoc for crates. 2014-06-30 00:03:34 -07:00
tutorial.md librustc: Remove the fallback to int for integers and f64 for 2014-06-29 11:47:58 -07:00
version_info.html.template Update repo location 2014-06-16 18:16:36 -07:00

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-dir 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-pre" \
    -M UTF-8 -L UTF-8 \
    src/doc/po4a.conf

(the version number must be changed if it is not 0.11.0-pre 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.