Verbatim (code) blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 Indented code blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 Fenced code blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 iv Contents Inline formatting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 Emphasis . . . . . . format and every other. Pandoc attempts to preserve the structural elements of a document, but not formatting details such as margin size. And some document elements, such as complex tables, may not fit into

3 2.4. General formatting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 3. Text formatting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 4. Code formatting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . project. This is intentionally not a complete user manual, but lists the subset of functionality and formatting options we would like to use. For further reference and more examples see • Official Asciidoc

5 2.5. General formatting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 3. Text formatting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 4. Code formatting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . project. This is intentionally not a complete user manual, but lists the subset of functionality and formatting options we would like to use. For further reference and more examples see • Official Asciidoc

5 2.5. General formatting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 3. Text formatting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 4. Code formatting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . project. This is intentionally not a complete user manual, but lists the subset of functionality and formatting options we would like to use. For further reference and more examples see • Official Asciidoc

5 2.5. General formatting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 3. Text formatting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 4. Code formatting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . project. This is intentionally not a complete user manual, but lists the subset of functionality and formatting options we would like to use. For further reference and more examples see • Official Asciidoc

5 2.5. General formatting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 3. Text formatting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 4. Code formatting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . project. This is intentionally not a complete user manual, but lists the subset of functionality and formatting options we would like to use. For further reference and more examples see • Official Asciidoc

in turn can make code more bug-prone and harder to read and maintain. The goal of this guide is to manage this complexity by describing in detail the dos and don’ts of writing C++ code. These rules exist keep the code base manageable while still allowing coders to use C++ language features produc- tively. Style, also known as readability, is what we call the conventions that govern our C++ code. The term term Style is a bit of a misnomer, since these conventions cover far more than just source file formatting. Most open-source projects developed by Google conform to the requirements in this guide. Note

. . . . . . . 415 3.2 Starting contributing code to Weblate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417 3.3 Weblate source code . . . . . . . . . . . . . . . . . . . . . . . A source code link is shown in the web-browser configured in the Component configuration by default. Hint: By setting the Editor link, you use your local editor to open the VCS source code file of translated to alert the translator to a potential formatting issue. Various bits of extra info can be shown on this page, most of which coming from the project source code (like context, comments or where the message

. . . . . . . 416 3.2 Starting contributing code to Weblate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 418 3.3 Weblate source code . . . . . . . . . . . . . . . . . . . . . . . A source code link is shown in the web-browser configured in the Component configuration by default. Hint: By setting the Editor link, you use your local editor to open the VCS source code file of translated to alert the translator to a potential formatting issue. Various bits of extra info can be shown on this page, most of which coming from the project source code (like context, comments or where the message

org/hosting/ for more information. Documentation To be found in the docs directory of the source code, or viewed online on https://docs.weblate.org/ Installation Setup instructions: https://docs.weblate progress reporting Contributor docs Contributing to Weblate Starting contributing code to Weblate Weblate source code Debugging Weblate Weblate internals Developing add-ons Weblate frontend Reporting A source code link is shown in the web-browser configured in the Component configuration by default. Hint By setting the Editor link, you use your local editor to open the VCS source code file of translated