rust/src/doc
Steve Klabnik 6c5bf9f2a4 Re-do the 30 minute intro
This was originally on my blog, so it's incredibly informal. Let's make
it better.
2014-10-03 11:22:44 -04:00
..
complement-bugreport.md Update repo location 2014-06-16 18:16:36 -07:00
complement-design-faq.md doc: grammar fixes 2014-08-20 01:31:07 +02:00
complement-lang-faq.md doc: Fix spelling errors. 2014-09-01 20:52:38 -04:00
complement-project-faq.md doc: Make sure all doc titles say 'Rust'. #12466 2014-08-01 17:32:24 -07:00
favicon.inc webfonts: serve Source Code Pro locally 2014-07-08 20:31:26 +02: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 Remove container guide. 2014-09-13 15:06:00 -04:00
guide-ffi.md Use a space after colons per the Rust coding style: 2014-09-12 09:10:03 +02:00
guide-lifetimes.md Remove incorrect example 2014-07-31 11:50:24 -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 note about ref patterns in pointer guide 2014-08-30 16:15:46 -04:00
guide-runtime.md guide-runtime.md: remove redundant verb 2014-08-12 07:39:53 +02:00
guide-strings.md Add section about Str trait 2014-09-09 18:48:30 -04:00
guide-tasks.md rollup merge of #17292 : thestinger/tasks 2014-09-17 08:49:28 -07:00
guide-testing.md guide-testing.md: add auxiliary verb 2014-08-12 07:39:56 +02:00
guide-unsafe.md Update docs to include Sized trait, which is needed 2014-09-15 18:52:20 -04:00
guide.md auto merge of #17366 : ohazi/rust/master, r=steveklabnik 2014-09-23 20:20:41 +00:00
index.md manual -> reference & formatting 2014-09-22 17:54:09 -04:00
intro.md Re-do the 30 minute intro 2014-10-03 11:22:44 -04:00
not_found.md manual -> reference & formatting 2014-09-22 17:54:09 -04:00
po4a.conf Replace the Tutorial with the Guide. 2014-09-11 16:21:32 -04:00
README.md manual -> reference & formatting 2014-09-22 17:54:09 -04:00
reference.md clean up some references to 'owned' 2014-09-22 17:54:10 -04:00
rust.css Fix API docs css reversing elements that it shouldn't 2014-08-01 04:01:29 -04:00
rust.md manual -> reference & formatting 2014-09-22 17:54:09 -04:00
rustdoc.md Fix example in docs on documentation 2014-07-02 10:53:30 +02:00
tutorial.md only deprecate the guide rather than 🔥 🔥 🔥 2014-09-11 16:21:32 -04: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 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 reference.html reference.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.