rust/src/doc
Jakub Bukaj f71b852d38 rollup merge of #19103: huonw/literal-suffixes
Futureproof Rust for fancier suffixed literals. The Rust compiler tokenises a literal followed immediately (no whitespace) by an identifier as a single token: (for example) the text sequences `"foo"bar`, `1baz` and `1u1024` are now a single token rather than the pairs `"foo"` `bar`, `1` `baz` and `1u` `1024` respectively.

The compiler rejects all such suffixes in the parser, except for the 12 numeric suffixes we have now.

I'm fairly sure this will affect very few programs, since it's not currently legal to have `<literal><identifier>` in a Rust program, except in a macro invocation. Any macro invocation relying on this behaviour can simply separate the two tokens with whitespace: `foo!("bar"baz)` becomes `foo!("bar" baz)`.

This implements [RFC 463](https://github.com/rust-lang/rfcs/blob/master/text/0463-future-proof-literal-suffixes.md), and so closes https://github.com/rust-lang/rust/issues/19088.
2014-11-19 22:41:05 +01:00
..
complement-bugreport.md Rename rust_fail to rust_panic 2014-10-30 05:09:50 +05:30
complement-design-faq.md doc: small grammar fix 2014-11-15 23:17:36 +00:00
complement-lang-faq.md Rename fail! to panic! 2014-10-29 11:43:07 -04:00
complement-project-faq.md
favicon.inc
footer.inc
full-toc.inc
guide-container.md
guide-crates.md build the crates guide 2014-10-23 07:40:29 -04:00
guide-error-handling.md Error handling guide 2014-11-18 19:30:05 -05:00
guide-ffi.md Rename fail! to panic! 2014-10-29 11:43:07 -04:00
guide-lifetimes.md Switch to purely namespaced enums 2014-11-17 07:35:51 -08:00
guide-macros.md Switch to purely namespaced enums 2014-11-17 07:35:51 -08:00
guide-plugin.md Use PascalCase for token variants 2014-10-28 15:55:37 +11:00
guide-pointers.md Switch to purely namespaced enums 2014-11-17 07:35:51 -08:00
guide-strings.md Fixed several typos 2014-11-15 15:00:47 -08:00
guide-tasks.md Remove lots of numeric traits from the preludes 2014-11-13 03:46:03 +11:00
guide-testing.md Fix fallout from coercion removal 2014-11-17 22:41:33 +13:00
guide-unsafe.md Update infrastructure for fail -> panic 2014-10-29 16:06:13 -04:00
guide.md rollup merge of #18968: danluu/guide_play 2014-11-19 22:37:18 +01:00
index.md New guide: error handling 2014-11-18 12:56:55 -05:00
intro.md Prepend should be append in the 30 minute intro 2014-11-07 14:59:42 -05:00
not_found.md cleaned up ids, added direct rust doc search 2014-11-02 08:06:32 -08:00
po4a.conf New guide: error handling 2014-11-18 12:56:55 -05:00
README.md
reference.md rollup merge of #19103: huonw/literal-suffixes 2014-11-19 22:41:05 +01:00
rust.css doc: enable OpenType kerning and ligatures 2014-11-01 00:16:48 +01:00
rust.md
rustdoc.md auto merge of #18381 : pelmers/rust/patch-1, r=alexcrichton 2014-10-31 00:22:19 +00:00
tutorial.md
version_info.html.template

Rust documentations

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

(reference.md being the Rust Reference Manual.)

The syntax for pandoc flavored markdown can be found at:

A nice quick reference (for non-pandoc markdown) is at:

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

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