documentation/locale/sources/contributing.pot

# SOME DESCRIPTIVE TITLE.
# Copyright (C) Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 14.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2021-05-18 07:12+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"

#: ../../content/contributing.rst:4
msgid "Contributing"
msgstr ""

#: ../../content/contributing/documentation.rst:4
msgid "Contributing to the documentation"
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:4
msgid "Content guidelines"
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:6
msgid "To give the community the best documentation possible, we listed here a few guidelines, tips and tricks that will make your content shine at its brightest! While we encourage you to adopt your own writing style, some rules still apply to give the reader more clarity and comprehension."
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:11
msgid "We strongly recommend contributors to carefully read the other documents in this *Contribution* section of the documentation. Good knowledge of the ins and outs of **RST writing** is required to write and submit your contribution. Note that it also affects your writing style itself."
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:15
msgid ":doc:`introduction_guide`"
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:16
#: ../../content/contributing/documentation/introduction_guide.rst:34
msgid ":doc:`rst_cheat_sheet`"
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:17
#: ../../content/contributing/documentation/introduction_guide.rst:35
msgid ":doc:`rst_guidelines`"
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:22
msgid "Writing style"
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:24
msgid "**Writing for documentation** isn't the same as writing for a blog or another medium. Readers are more likely to skim read until they've found the information they are looking for. Keep in mind that the user documentation is a place to inform and describe, not to convince and promote."
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:31
msgid "Consistency"
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:33
msgid "*Consistency is key to everything.*"
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:35
msgid "Make sure that your writing style remains **consistent**. If you modify an existing text, try to match the existing tone and presentation, or rewrite it to match your own style."
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:41
msgid "Grammatical tenses"
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:43
msgid "In English, descriptions and instructions require the use of a **Present Tense**, while a *future tense* is appropriate only when a specific event is to happen ulteriorly. This logic might be different in other languages."
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:0
msgid "Good example (present):"
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:0
msgid "*Screenshots are automatically resized to fit the content block's width.*"
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:0
msgid "Bad example (future):"
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:0
msgid "*When you take a screenshot, remember that it will be automatically resized to fit the content block's width.*"
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:56
msgid "Paragraphing"
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:58
msgid "A paragraph comprises several sentences that are linked by a shared idea. They usually are two to six lines long."
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:61
msgid "In English, a new idea implies a new paragraph, rather than having a *line break* as it is common to do in some other languages. *Line breaks* are useful for layout purposes but shouldn't be used as a grammatical way of separating ideas."
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:66
msgid ":ref:`RST cheat sheet: Break the line but not the paragraph <contributing/line-break>`"
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:71
msgid "Titles and headings"
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:73
msgid "To write good titles and headings:"
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:75
msgid "**Be concise.**"
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:76
msgid "**Avoid sentences**, questions, and titles starting with \"how to.\""
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:77
msgid "**Don't use pronouns** in your titles, especially 2nd person (*your*)"
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:78
msgid "Use **sentence case**. This means you capitalize only:"
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:80
msgid "the first word of the title or heading"
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:81
msgid "the first word after a colon"
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:82
msgid "proper nouns (brands, product and service names, etc.)"
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:83
msgid "app features, as written in the apps"
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:86
msgid "Do not capitalize common nouns when they are not referred to as features. This is more likely to happen in headings rather than in titles."
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:90
msgid "Examples"
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:90
msgid "Explanations"
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:0
msgid "**Titles**"
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:0
msgid "(h1)"
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:92
msgid "*Quotation Templates*"
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:92
msgid "\"Quotation Templates\" is a feature in Odoo."
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:94
msgid "*Lead Mining*"
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:94
msgid "\"Lead Mining\" is a feature in Odoo."
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:96
msgid "*Resupply from another Warehouse*"
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:96
msgid "\"Warehouse\" is capitalized as we refer to the feature in the app rather than to a real warehouse."
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:99
msgid "*Synchronize Google Calendar with Odoo*"
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:99
msgid "\"Google Calendar\" is a product and \"Odoo\" is a brand."
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:0
msgid "**Headings**"
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:0
msgid "(h2, h3, etc.)"
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:102
msgid "*Confirm the quotation*"
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:102
msgid "\"The quotation\" is a common noun not referring to a feature in Odoo."
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:105
msgid "*Test environment*"
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:105
msgid "\"Environment\" is a common noun."
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:107
msgid "*Add a new Payment Acquirer*"
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:107
msgid "\"Payment Acquirers\" is a feature in Odoo."
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:109
msgid "*Generate SEPA Direct Debit XML files to submit payments*"
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:109
msgid "\"SEPA Direct Debit\" and \"XML\" are considered as proper nouns."
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:116
msgid "Document's structure"
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:118
msgid "Use different **headings levels** to organize your text by sections and sub-sections. Your headings are also displayed in a dynamic *navigation bar* on the side."
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:0
msgid "**H1: Page title**"
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:0
msgid "Your *page title* gives your reader a quick and clear understanding of what your content is about. It is also referenced in the section's *table of contents*."
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:126
msgid "The *content* in this section describes the upcoming content from a **business point of view**, and shouldn't put the emphasis on Odoo, as this is documentation and not marketing."
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:130
msgid "Start first with a **lead paragraph**, which helps the reader make sure that they've found the right page, then explain the **business aspects of this topic** in the following paragraphs."
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:0
msgid "**H2: Section title (configuration)**"
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:0
msgid "This first H2 section is about the configuration of the feature, or the prerequisites to achieve a specific goal. To add a path, make sure you use the ``:menuselection:`` specialized directive (see link below)."
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:0
msgid "Example:"
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:0
msgid "To do so, go to ``:menuselection:`App name --> Menu --> Sub-menu```, and enable the XYZ feature."
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:0
msgid "**H2: Section title (main sections)**"
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:0
msgid "Create as many main sections as you have actions or features to distinguish. The title can start with a verb, but try to avoid using \"Create ...\"."
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:0
msgid "**H3: Subsection**"
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:0
msgid "Subsections are perfect for assessing very specific points. The title can be in the form of a question, if appropriate."
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:151
msgid "**H2: Next Section**"
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:155
msgid ":ref:`RST cheat sheet: headings <contributing/headings>`"
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:156
msgid ":ref:`RST cheat sheet: specialized directives <contributing/specialized-directives>`"
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:161
msgid "Images"
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:163
msgid "Adding a few images to illustrate your text helps the readers to understand and memorize your content. However, avoid adding too many images: it isn't necessary to illustrate all steps and features, and it may overload your page."
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:168
msgid "Don't forget to :ref:`compress your PNG files with pngquant <contributing/pngquant>`."
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:173
msgid "Screenshots"
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:175
msgid "Screenshots are automatically resized to fit the content block's width. This implies that screenshots can't be too wide, else they would appear very small on-screen. Therefore, we recommend to avoid to take screenshots of a full screen display of the app, unless it is relevant to do so."
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:179
msgid "A few tips to improve your screenshots:"
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:181
msgid "**Zoom** in your browser. We recommend a 110% zoom for better results."
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:182
msgid "**Resize** your browser's width, either by *resizing the window* itself or by opening the *browser's developer tools* (press the ``F12`` key) and resizing the width."
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:184
msgid "**Select** the relevant area, rather than keeping the full window."
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:185
msgid "If necessary, you can **edit** the screenshot to remove unnecessary fields and to narrow even more Odoo's display."
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:193
msgid "Resizing the window's width is the most important step to do as Odoo's responsive design automatically resizes all fields to match the window's width."
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:199
msgid "Media files"
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:201
msgid "A **media filename**:"
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:203
msgid "is written in **lower-case letters**"
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:204
msgid "is **relevant** to the media's content. (E.g., :file:`screenshot-tips.gif`.)"
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:205
msgid "separates its words with a **hyphen** ``-`` (E.g., :file:`awesome-filename.png`.)"
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:207
msgid "Each document has its own folder in which the media files are located. The folder's name must be the same as the document's filename."
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:210
msgid "For example, the document :file:`doc_filename.rst` refers to two images that are placed in the folder ``doc_filename``."
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:222
msgid "Previously, image filenames would mostly be named with numbers (e.g., :file:`feature01.png`) and placed in a single ``media`` folder. While it is advised not to name your *new* images in that fashion, it is also essential **not to rename unchanged files**, as doing this would double the weight of renamed image files on the repository. They will eventually all be replaced as the content referencing those images is updated."
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:231
msgid "ALT tags"
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:233
msgid "An **ALT tag** is a *text alternative* to an image. This text is displayed if the browser fails to render the image. It is also helpful for users who are visually impaired. Finally, it helps search engines, such as Google, to understand what the image is about and index it correctly, which improves the :abbr:`SEO (Search Engine Optimization)` significantly."
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:238
msgid "Good ALT tags are:"
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:240
msgid "**Short** (one line maximum)"
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:241
msgid "**Not a repetition** of a previous sentence or title"
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:242
msgid "A **good description** of the action happening on the image"
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:243
msgid "Easily **understandable** if read aloud"
msgstr ""

#: ../../content/contributing/documentation/content_guidelines.rst:246
msgid ":ref:`RST cheat sheet: image directive <contributing/image>`"
msgstr ""

#: ../../content/contributing/documentation/introduction_guide.rst:4
msgid "Introduction guide"
msgstr ""

#: ../../content/contributing/documentation/introduction_guide.rst:6
msgid "**First of all, thank you for landing here and helping us improve the user documentation of Odoo!**"
msgstr ""

#: ../../content/contributing/documentation/introduction_guide.rst:8
msgid "This introductory guide will help you acquire the tools and knowledge you need to write documentation, whether you plan to make a minor content change or document an application from scratch."
msgstr ""

#: ../../content/contributing/documentation/introduction_guide.rst:15
msgid "reStructuredText"
msgstr ""

#: ../../content/contributing/documentation/introduction_guide.rst:17
msgid "Our documentation is written in **reStructuredText** (RST), a `lightweight markup language <https://en.wikipedia.org/wiki/Lightweight_markup_language>`_ consisting of normal text augmented with markup which allows including headings, images, notes, and so on. This might seem a bit abstract but there is no need to worry. :abbr:`RST (reStructuredText)` is not hard to learn, especially if you intend to make only small changes to the content."
msgstr ""

#: ../../content/contributing/documentation/introduction_guide.rst:23
msgid "If you need to learn about a specific markup, head over to :doc:`our cheat sheet for RST <rst_cheat_sheet>` which contains all the information that you should ever need for the user documentation of Odoo."
msgstr ""

#: ../../content/contributing/documentation/introduction_guide.rst:28
msgid "We kindly ask you to observe a set of :doc:`content <content_guidelines>` and :doc:`RST <rst_guidelines>` guidelines as you write documentation. This ensures that you stay consistent with the rest of the documentation and facilitates the approval of your content changes as they are reviewed by a redactor at Odoo."
msgstr ""

#: ../../content/contributing/documentation/introduction_guide.rst:36
msgid ":doc:`content_guidelines`"
msgstr ""

#: ../../content/contributing/documentation/introduction_guide.rst:41
msgid "Getting started"
msgstr ""

#: ../../content/contributing/documentation/introduction_guide.rst:43
msgid "As our documentation is maintained on GitHub, you will need a free GitHub account. Click `here <https://github.com/join>`_ to create one."
msgstr ""

#: ../../content/contributing/documentation/introduction_guide.rst:46
msgid "Now, depending on whether you want to update existing content, or rather work on new content and make file changes, you have two courses of action:"
msgstr ""

#: ../../content/contributing/documentation/introduction_guide.rst:49
msgid "**For small changes** in ``.rst`` files only, i.e. addition/edition of paragraphs or typos, **we suggest that you use the GitHub interface**. This is the easiest and fasted way to submit your request for changes for the documentation and is suitable for non-technical people. Read :ref:`contributing/github-interface` to learn how to use this method."
msgstr ""

#: ../../content/contributing/documentation/introduction_guide.rst:53
msgid "**For more complex cases**, it is necessary to **use Git and work from a local copy of the documentation**. This method seems intimidating but only requires basic knowledge of Git. See :ref:`contributing/canonical-git-workflow` for more information on this method."
msgstr ""

#: ../../content/contributing/documentation/introduction_guide.rst:60
msgid "Use the GitHub interface"
msgstr ""

#: ../../content/contributing/documentation/introduction_guide.rst:62
msgid "Verify that you are browsing the documentation in the version that you intend to change. The version can be selected from the dropdown in the top menu."
msgstr ""

#: ../../content/contributing/documentation/introduction_guide.rst:67
msgid "Head over to the page that you want to change and click on the **Edit on GitHub** button in the bottom of the left menu."
msgstr ""

#: ../../content/contributing/documentation/introduction_guide.rst:72
msgid "If you do not have edit rights on the repository (`odoo/documentation <https://github.com/odoo/documentation>`_), you need to fork it by clicking on the appropriate button. In other terms, you create a copy of the entire repository on your own account. If you do have the edit rights, skip this step."
msgstr ""

#: ../../content/contributing/documentation/introduction_guide.rst:79
msgid "Make the appropriate changes while taking care of following the :doc:`guidelines <rst_guidelines>`."
msgstr ""

#: ../../content/contributing/documentation/introduction_guide.rst:82
msgid "Click on the **Preview changes** button to review your contribution in a more human-readable format. Be aware that the preview is not able to handle all markups correctly. Notes and tips, for instance, are not correctly rendered. The version of your content published to the website will be, however."
msgstr ""

#: ../../content/contributing/documentation/introduction_guide.rst:87
msgid "Go to the bottom of the page to create a commit (:dfn:`what packs your changes together and labels them with a commit message`) of your changes."
msgstr ""

#: ../../content/contributing/documentation/introduction_guide.rst:0
msgid "In first text box, describe your changes. For instance, \"Fix a typo\" and \"Add documentation for invoicing of sales orders\" are two clear commit messages."
msgstr ""

#: ../../content/contributing/documentation/introduction_guide.rst:0
msgid "In the second text box, justify *why* you made these changes, if you feel that it is not obvious."
msgstr ""

#: ../../content/contributing/documentation/introduction_guide.rst:94
msgid "Select the option \"Create a new branch for this commit and start a pull request.\" if you have the choice (if you have partial or full edit writes on the repository). If not, skip this step."
msgstr ""

#: ../../content/contributing/documentation/introduction_guide.rst:97
msgid "Click on the green button. It is either labelled \"Commit changes\" or \"Propose file change\"."
msgstr ""

#: ../../content/contributing/documentation/introduction_guide.rst:101
msgid "In the dropdown for the selection of the base branch (i.e., the version of the documentation that your changes concern), make sure to select the same version as in the first step of this guide and click on the **Create pull request** button."
msgstr ""

#: ../../content/contributing/documentation/introduction_guide.rst:107
msgid "Double-check your :abbr:`PR (Pull Request)` and, when ready, click again on the **Create pull request** button to submit your changes for review by a content writer at Odoo."
msgstr ""

#: ../../content/contributing/documentation/introduction_guide.rst:112
#: ../../content/contributing/documentation/introduction_guide.rst:390
msgid "You're done! If your changes are approved straight away they will appear in the documentation the very next day. It may also be the case that the reviewer has a question or a remark, so make sure to check your notifications or your emails, depending on your account settings."
msgstr ""

#: ../../content/contributing/documentation/introduction_guide.rst:119
msgid "Use the canonical Git workflow"
msgstr ""

#: ../../content/contributing/documentation/introduction_guide.rst:124
msgid "Prepare your machine"
msgstr ""

#: ../../content/contributing/documentation/introduction_guide.rst:129
msgid "Install Git"
msgstr ""

#: ../../content/contributing/documentation/introduction_guide.rst:131
msgid "We use `Git <https://en.wikipedia.org/wiki/Git>`_ to manage the files of the user documentation. It is a tool that allows to track the history of changes made to a file and, more importantly, to work on different versions of those files at the same time. It means that you do not need to worry about overwriting someone else’s pending work when you start editing the documentation."
msgstr ""

#: ../../content/contributing/documentation/introduction_guide.rst:136
msgid "You must then configure Git to identify yourself as the author of your future contribution. Enter the same email address as the one you used to register on GitHub."
msgstr ""

#: ../../content/contributing/documentation/introduction_guide.rst:139
msgid "Download and install **Git** on your machine."
msgstr ""

#: ../../content/contributing/documentation/introduction_guide.rst:140
msgid "Verify that `the installation folder of Git is included in your system's PATH variable <win-add-to-path_>`_."
msgstr ""

#: ../../content/contributing/documentation/introduction_guide.rst:142
#: ../../content/contributing/documentation/introduction_guide.rst:167
#: ../../content/contributing/documentation/introduction_guide.rst:314
#: ../../content/contributing/documentation/introduction_guide.rst:331
#: ../../content/contributing/documentation/introduction_guide.rst:362
msgid "Execute the following commands in a terminal:"
msgstr ""

#: ../../content/contributing/documentation/introduction_guide.rst:152
msgid "Fetch the sources"
msgstr ""

#: ../../content/contributing/documentation/introduction_guide.rst:154
msgid "As stated earlier, our documentation (in all its versions) is maintained on GitHub at `github.com/odoo/documentation <https://github.com/odoo/documentation>`_. A modification is made by the mean of a :abbr:`PR (Pull Request)` (:dfn:`proposal of content changes`) to allow for a review of the changes before updating the sources of the documentation."
msgstr ""

#: ../../content/contributing/documentation/introduction_guide.rst:159
msgid "Prior to submitting a modification, you need to make a copy of the sources and download that copy on your machine."
msgstr ""

#: ../../content/contributing/documentation/introduction_guide.rst:162
msgid "Go to `github.com/odoo/documentation <https://github.com/odoo/documentation>`_ and click on the **Fork** button in the top right corner."
msgstr ""

#: ../../content/contributing/documentation/introduction_guide.rst:175
msgid "If you do not have edit rights on the repository owned by Odoo, replace \"odoo\" with your Github username in the URL of the command above. If you do have edit rights, it is not necessary to fork the repository."
msgstr ""

#: ../../content/contributing/documentation/introduction_guide.rst:179
msgid "In order to ease the collaboration between writers coming from many different systems and teams, execute the following group of commands that correspond to your :abbr:`OS (Operating System)` in a terminal."
msgstr ""

#: ../../content/contributing/documentation/introduction_guide.rst:183
msgid "Windows:"
msgstr ""

#: ../../content/contributing/documentation/introduction_guide.rst:191
msgid "Linux or Mac OS:"
msgstr ""

#: ../../content/contributing/documentation/introduction_guide.rst:202
msgid "Python"
msgstr ""

#: ../../content/contributing/documentation/introduction_guide.rst:204
msgid "Because the documentation is written in :abbr:`RST (reStructuredText)`, it needs to be built (:dfn:`converted to HTML`) in order to display nicely. This is done by the documentation generator which takes the original :abbr:`RST (reStructuredText)` files as input, transforms the markups in a human-readable format, and outputs HTML files to be read in your web browser."
msgstr ""

#: ../../content/contributing/documentation/introduction_guide.rst:209
msgid "The documentation generator that we use is called `Sphinx <http://www.sphinx-doc.org/en/master/>`_. and is written in `Python <https://en.wikipedia.org/wiki/Python_(programming_language)>`_. You have to install Python in order to use Sphinx. For the record, Sphinx is the program and Python the programming language, but you do not need to know much more about them so don't panic!"
msgstr ""

#: ../../content/contributing/documentation/introduction_guide.rst:214
msgid "Python comes with its own package manager: `pip <https://en.wikipedia.org/wiki/Pip_(package_manager)>`_. It allows installing Python dependencies in a single command."
msgstr ""

#: ../../content/contributing/documentation/introduction_guide.rst:218
msgid "Download and install the recommended release (`see README file <https://github.com/odoo/documentation/tree/14.0/README.md>`_) of **Python 3** on your machine."
msgstr ""

#: ../../content/contributing/documentation/introduction_guide.rst:220
msgid "Make sure to have **pip** installed on your machine (on Windows, you can install pip alongside Python)."
msgstr ""

#: ../../content/contributing/documentation/introduction_guide.rst:222
msgid "Execute the following commands in a terminal to verify that both installations finished successfully:"
msgstr ""

#: ../../content/contributing/documentation/introduction_guide.rst:230
msgid "Execute the following commands in a terminal to install the Python dependencies of the documentation:"
msgstr ""

#: ../../content/contributing/documentation/introduction_guide.rst:239
msgid "Depending on your :abbr:`OS (Operating System)`, you may need to run the commands ``python`` and ``pip`` instead of ``python3`` and ``pip3``"
msgstr ""

#: ../../content/contributing/documentation/introduction_guide.rst:245
msgid "Make"
msgstr ""

#: ../../content/contributing/documentation/introduction_guide.rst:247
msgid "`Make <https://en.wikipedia.org/wiki/Make_(software)>`_ is a tool that packs a bunch of command-lines into one to be easier to remember and to type. In our case, it is used to execute complex Sphinx build commands by using a single and simpler one instead."
msgstr ""

#: ../../content/contributing/documentation/introduction_guide.rst:251
msgid "Download and install **Make** on your machine."
msgstr ""

#: ../../content/contributing/documentation/introduction_guide.rst:252
msgid "Verify that `the installation folder of Make is included in your system's PATH variable <win-add-to-path_>`_."
msgstr ""

#: ../../content/contributing/documentation/introduction_guide.rst:258
msgid "pngquant"
msgstr ""

#: ../../content/contributing/documentation/introduction_guide.rst:260
msgid "`pngquant <https://pngquant.org/>`_ is a tool that we use to compress PNG images so that the documentation does not end up weighting several Gigabytes in a few year span."
msgstr ""

#: ../../content/contributing/documentation/introduction_guide.rst:263
msgid "Download and install **pngquant** on your machine."
msgstr ""

#: ../../content/contributing/documentation/introduction_guide.rst:264
msgid "Verify that `the installation folder of pngquant is included in your system's PATH variable <win-add-to-path_>`_."
msgstr ""

#: ../../content/contributing/documentation/introduction_guide.rst:270
msgid "Prepare your version"
msgstr ""

#: ../../content/contributing/documentation/introduction_guide.rst:272
msgid "Now that your machine is all set up, it is time to do the same for your version of the documentation files. As it would not be convenient to have several people working on the version 14.0 in parallel (conflicts of content would occur all the time), and in order to be able to create a :abbr:`PR (Pull Request)`, you must `create a new branch <https://www.atlassian.com/git/tutorials/using-branches>`_ starting from the branch 14.0. In other words, you copy the entirety of this version’s files and give it another name. For this example, we will go with ``14.0-my_contribution``."
msgstr ""

#: ../../content/contributing/documentation/introduction_guide.rst:280
msgid "Execute the following commands in a terminal to..."
msgstr ""

#: ../../content/contributing/documentation/introduction_guide.rst:282
msgid "Navigate to the documentation folder:"
msgstr ""

#: ../../content/contributing/documentation/introduction_guide.rst:288
msgid "Switch to the version 14.0:"
msgstr ""

#: ../../content/contributing/documentation/introduction_guide.rst:294
msgid "Create your own branch which will be a copy of 14.0:"
msgstr ""

#: ../../content/contributing/documentation/introduction_guide.rst:303
msgid "Perform your changes"
msgstr ""

#: ../../content/contributing/documentation/introduction_guide.rst:305
msgid "You can now perform any change you want to the documentation files. These changes must be compliant with :abbr:`RST (reStructuredText)` syntax (see :doc:`rst_cheat_sheet`) and with our :doc:`guidelines <rst_guidelines>`."
msgstr ""

#: ../../content/contributing/documentation/introduction_guide.rst:310
msgid "If your changes include the addition of a new image, for instance :file:`my_image.png`, proceed as follows:"
msgstr ""

#: ../../content/contributing/documentation/introduction_guide.rst:313
msgid "Make sure that the image is in ``.png`` format."
msgstr ""

#: ../../content/contributing/documentation/introduction_guide.rst:321
msgid "Delete :file:`my_image.png`."
msgstr ""

#: ../../content/contributing/documentation/introduction_guide.rst:322
msgid "Rename :file:`my_image-fs8.png` to :file:`my_image.png`."
msgstr ""

#: ../../content/contributing/documentation/introduction_guide.rst:327
msgid "Preview your changes"
msgstr ""

#: ../../content/contributing/documentation/introduction_guide.rst:329
msgid "To preview your changes in a generated documentation, proceed as follows:"
msgstr ""

#: ../../content/contributing/documentation/introduction_guide.rst:340
msgid "You can omit the :command:`make clean` command when no recent change has been made to the hierarchy of documentation files."
msgstr ""

#: ../../content/contributing/documentation/introduction_guide.rst:343
msgid "Fix any error or warning shown in the logs of the build."
msgstr ""

#: ../../content/contributing/documentation/introduction_guide.rst:344
msgid "Open the file :file:`documentation/_build/html/index.html` with your default web browser."
msgstr ""

#: ../../content/contributing/documentation/introduction_guide.rst:347
msgid "These steps have for only purpose to show you the final results of your changes. They have no impact on the documentation source files."
msgstr ""

#: ../../content/contributing/documentation/introduction_guide.rst:353
msgid "Submit your changes"
msgstr ""

#: ../../content/contributing/documentation/introduction_guide.rst:356
msgid "We expect you to have basic knowledge of Git, which should be enough to cover the basic flow of a one-time contribution. If you plan on submitting several contributions, work on older versions of the documentation or perform any other advanced action, we recommend you to be confident with Git. Help yourself with `this manual of Git <https://www.atlassian.com/git>`_ and `this interactive tutorial <https://learngitbranching.js.org/>`_."
msgstr ""

#: ../../content/contributing/documentation/introduction_guide.rst:370
msgid "Go to `github.com/odoo/documentation/pulls <https://github.com/odoo/documentation/pulls>`_ and click on the **New pull request** button."
msgstr ""

#: ../../content/contributing/documentation/introduction_guide.rst:375
msgid "If you forked the base repository in the section :ref:`contributing/fetch-sources`, click on the link **compare across forks** If not, skip this step."
msgstr ""

#: ../../content/contributing/documentation/introduction_guide.rst:380
msgid "In the dropdown for the selection of the base branch (i.e., the version of the documentation that your changes concern), make sure to select the version that your changes target (here **14.0**)."
msgstr ""

#: ../../content/contributing/documentation/introduction_guide.rst:385
msgid "Double-check your :abbr:`PR (Pull Request)` and, when ready, click again on the **Create pull request** button to submit your changes for review by a redactor at Odoo."
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:4
msgid "RST cheat sheet"
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:9
msgid "Headings"
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:12
msgid "For each formatting line (e.g., ``===``), write as many symbols (``=``) as there are characters in the header."
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:16
msgid "The symbols used for the formatting are, in fact, not important. Only the order in which they are written matters, as it determines the size of the decorated heading. This means that you may encounter different heading formatting and in a different order, in which case you should follow the formatting in place in the document. In any other case, use the formatting shown below."
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:19
msgid "Heading size"
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:19
msgid "Formatting"
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:19
msgid "Min/Max number of occurrences"
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:21
msgid "H1"
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:0
#: ../../content/contributing/documentation/rst_cheat_sheet.rst:0
#: ../../content/contributing/documentation/rst_cheat_sheet.rst:0
msgid "``=======``"
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:0
#: ../../content/contributing/documentation/rst_cheat_sheet.rst:0
#: ../../content/contributing/documentation/rst_cheat_sheet.rst:0
#: ../../content/contributing/documentation/rst_cheat_sheet.rst:0
#: ../../content/contributing/documentation/rst_cheat_sheet.rst:0
#: ../../content/contributing/documentation/rst_cheat_sheet.rst:0
msgid "``Heading``"
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:21
msgid "1/1"
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:25
msgid "H2"
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:25
#: ../../content/contributing/documentation/rst_cheat_sheet.rst:28
#: ../../content/contributing/documentation/rst_cheat_sheet.rst:31
#: ../../content/contributing/documentation/rst_cheat_sheet.rst:34
#: ../../content/contributing/documentation/rst_cheat_sheet.rst:37
msgid "0/∞"
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:28
msgid "H3"
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:0
msgid "``-------``"
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:31
msgid "H4"
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:0
msgid "``~~~~~~~``"
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:34
msgid "H5"
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:0
msgid "``*******``"
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:37
msgid "H6"
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:0
msgid "``^^^^^^^``"
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:44
msgid "Markup"
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:49
msgid "Inline markup"
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:51
msgid "Use the following markups to emphasize your text to your liking:"
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:54
msgid "\\*\\*Text\\*\\*"
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:54
msgid "**Text**"
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:56
msgid "\\*Text\\*"
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:56
msgid "*Text*"
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:58
msgid "\\`\\`Text\\`\\`"
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:58
msgid "``Text``"
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:62
msgid ":ref:`contributing/specialized-directives`"
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:67
msgid "Bulleted list"
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:83
msgid "Numbered list"
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:98
msgid "Nested lists"
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:110
msgid "Hyperlinks"
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:115
msgid "Hyperlink references"
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:117
msgid "Hyperlink references are links to a URL with a custom label. They follow this syntax: ```label <URL>`_``"
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:121
msgid "The URL can be a relative path to a file within the documentation."
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:124
#: ../../content/contributing/documentation/rst_cheat_sheet.rst:145
#: ../../content/contributing/documentation/rst_cheat_sheet.rst:191
#: ../../content/contributing/documentation/rst_cheat_sheet.rst:231
#: ../../content/contributing/documentation/rst_cheat_sheet.rst:262
#: ../../content/contributing/documentation/rst_cheat_sheet.rst:287
#: ../../content/contributing/documentation/rst_cheat_sheet.rst:312
#: ../../content/contributing/documentation/rst_guidelines.rst:18
msgid "Example"
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:126
msgid "This excerpt of :abbr:`RST (reStructuredText)`: ``For instance, `this is a hyperlink reference <https://odoo.com>`_.`` is rendered as follows in HTML: “For instance, `this is a hyperlink reference <https://odoo.com>`_.”"
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:133
msgid "External hyperlink targets"
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:135
msgid "External hyperlink targets allow creating shortcuts for hyperlink references."
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:136
msgid "The definition syntax is as follows: ``.. _target: URL``"
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:137
msgid "There are two ways to reference them, depending on the use case:"
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:139
msgid "``target_`` creates a hyperlink with the target name as label and the URL as reference. Note that the ``_`` moved after the target!"
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:141
msgid "```label <target_>`_`` does exactly what you expect: the label replaces the name of the target, and the target is replaced by the URL."
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:148
#: ../../content/contributing/documentation/rst_cheat_sheet.rst:194
#: ../../content/contributing/documentation/rst_cheat_sheet.rst:234
#: ../../content/contributing/documentation/rst_cheat_sheet.rst:265
#: ../../content/contributing/documentation/rst_cheat_sheet.rst:290
#: ../../content/contributing/documentation/rst_cheat_sheet.rst:315
#: ../../content/contributing/documentation/rst_cheat_sheet.rst:351
#: ../../content/contributing/documentation/rst_cheat_sheet.rst:372
#: ../../content/contributing/documentation/rst_cheat_sheet.rst:391
#: ../../content/contributing/documentation/rst_cheat_sheet.rst:412
#: ../../content/contributing/documentation/rst_cheat_sheet.rst:431
#: ../../content/contributing/documentation/rst_cheat_sheet.rst:452
#: ../../content/contributing/documentation/rst_cheat_sheet.rst:476
msgid "RST"
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:158
#: ../../content/contributing/documentation/rst_cheat_sheet.rst:210
#: ../../content/contributing/documentation/rst_cheat_sheet.rst:242
#: ../../content/contributing/documentation/rst_cheat_sheet.rst:273
#: ../../content/contributing/documentation/rst_cheat_sheet.rst:298
#: ../../content/contributing/documentation/rst_cheat_sheet.rst:329
#: ../../content/contributing/documentation/rst_cheat_sheet.rst:360
#: ../../content/contributing/documentation/rst_cheat_sheet.rst:380
#: ../../content/contributing/documentation/rst_cheat_sheet.rst:400
#: ../../content/contributing/documentation/rst_cheat_sheet.rst:420
#: ../../content/contributing/documentation/rst_cheat_sheet.rst:440
#: ../../content/contributing/documentation/rst_cheat_sheet.rst:460
#: ../../content/contributing/documentation/rst_cheat_sheet.rst:485
msgid "Render"
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:160
msgid "A `proof-of-concept <https://en.wikipedia.org/wiki/Proof_of_concept>`_ is a simplified version, a prototype of what is expected to agree on the main lines of expected changes. `PoC <https://en.wikipedia.org/wiki/Proof_of_concept>`_ is a common abbreviation."
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:167
msgid "Internal hyperlink targets"
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:169
msgid "Internal hyperlink targets follow the same syntax as external hyperlink targets but without any URL. Indeed, they are internal. They allow referencing a specific part of a document by using the target as an anchor. When the user clicks on the reference, the documentation scrolls to the part of the page containing the target."
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:175
msgid "Targets can be referenced from other files than the ones in which they are defined."
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:177
msgid "The definition syntax is: ``.. _target:``"
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:178
msgid "There are two ways to reference them, both using the ``ref`` directive:"
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:180
msgid "``:ref:`target``` creates a hyperlink to the anchor with the heading defined below as label."
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:181
msgid "``:ref:`label <target>``` creates a hyperlink to the anchor with the given label."
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:183
msgid "See :ref:`contributing/relative-links` to learn how to write proper relative links for internal references."
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:187
msgid "Notice that there is no ``_`` at the end, as it is done with :ref:`hyperlink targets <contributing/hyperlink-references>`."
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:212
msgid "This can easily be done by creating a new product, see `How to create a product? <https://example.com/product>`_ for additional help."
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:215
msgid "**How to create a product?**"
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:217
msgid "As explained at the `start of the page <https://example.com/scroll-to-start-of-page>`_, ..."
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:222
msgid "Implicit hyperlink targets"
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:226
msgid "Implicit hyperlink targets are a special kind of internal hyperlink targets: they are automatically generated by section titles, footnotes, etc. Consequently, they don’t have a definition syntax."
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:228
msgid "They can be referenced the same first way as external hyperlink targets by using the name of the section title as URL."
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:244
msgid "This can easily be done by creating a new user, see `How to create a new user? <https://example.com/how-to-create-a-user>`_ for additional help. ..."
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:250
msgid "The ``doc`` directive"
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:253
msgid "The ``doc`` directive allows referencing a documentation page wherever it is in the file tree through a relative file path."
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:254
msgid "As usual, there are two ways to use the directive:"
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:256
msgid "``:doc:`path_to_doc_page``` creates a hyperlink reference to the documentation page with the title of the page as label."
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:258
msgid "``:doc:`label <path_to_doc_page>``` creates a hyperlink reference to the documentation page with the given label."
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:275
msgid "Please refer to `this documentation <https://example.com/doc/accounting/invoices.html>`_ and to `Send a pro-forma invoice <https://example.com/doc/sales/proforma.html>`_."
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:281
msgid "The ``download`` directive"
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:283
msgid "The ``download`` directive allows referencing files (that are not necessarily :abbr:`RST (reStructuredText)` documents) within the source tree to be downloaded."
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:300
msgid "Download this `module structure template <https://example.com/doc/odoosh/extras/my_module.zip>`_ to start building your module in no time."
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:306
msgid "The ``image`` directive"
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:308
msgid "The ``image`` directive allows inserting images in a document. It comes with a set of optional parameter directives that can individually be omitted if considered redundant."
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:343
msgid "Admonitions (alert blocks)"
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:348
msgid "Seealso"
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:363
msgid "`Customer invoices <https://example.com/doc/accounting/invoices.html>`_"
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:364
msgid "`Pro-forma invoices <https://example.com/doc/sales/proforma.html#activate-the-feature>`_"
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:369
msgid "Note"
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:383
msgid "Use this to get the attention of the reader about additional information."
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:388
msgid "Tip"
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:403
msgid "Use this to inform the reader about a useful trick that requires an action."
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:409
msgid "Important"
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:423
msgid "Use this to notify the reader about an important information."
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:428
msgid "Warning"
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:443
msgid "Use this to require the reader to proceed with caution with what is described in the warning."
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:449
msgid "Danger"
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:463
msgid "Use this to alarm the reader about a serious threat."
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:468
msgid "Formatting tips"
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:473
msgid "Break the line but not the paragraph"
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:488
msgid "First super long line that you break in two… here is rendered as a single line."
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:489
msgid "Second line that follows a line break."
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:494
msgid "Add comments"
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:496
msgid "If you made a particular choice of writing or formatting that a future writer should be able to understand and take into account, consider writing a comment. Comments are blocks of text that do not count as a part of the documentation and that are used to pass a message to writers of the source code. They consist of a line starting with two dots and a space, followed by the comment."
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:501
msgid "``.. For instance, this line will not be rendered in the documentation.``"
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:506
msgid "Use tables"
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:508
msgid "Make use of `this convenient table generator <https://www.tablesgenerator.com/text_tables>`_ to build your tables. Then, copy-paste the generated formatting into your document."
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:514
msgid "Spice up your writing with specialized directives"
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:516
msgid "Use these additional directives to fine-tune your content:"
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:519
msgid "**Directive**"
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:519
msgid "**Purpose**"
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:519
msgid "**Example**"
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:521
msgid "**RST**"
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:521
msgid "**HTML**"
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:523
msgid "``abbr``"
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:523
msgid "Self-defining abbreviations"
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:523
msgid "``:abbr:`SO (Sales Order)```"
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:523
msgid ":abbr:`SO (Sales Order)`"
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:525
msgid "``command``"
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:525
msgid "Highlight a command"
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:525
msgid "``:command:`python example.py```"
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:525
msgid ":command:`python example.py`"
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:527
msgid "``dfn``"
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:527
msgid "Define a term"
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:527
msgid "``:dfn:`a definition for a new term```"
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:527
msgid ":dfn:`a definition for a new term`"
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:529
msgid "``file``"
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:529
msgid "Indicate a file path"
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:529
msgid "``:file:`~/odoo/odoo-bin```"
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:529
msgid ":file:`~/odoo/odoo-bin`"
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:531
msgid "``menuselection``"
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:531
msgid "Guide a user through a sequence of menus"
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:531
msgid "``:menuselection:`Sales --> Configuration --> Settings```"
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:531
msgid ":menuselection:`Sales --> Configuration --> Settings`"
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:537
msgid "Escape markup symbols (Advanced)"
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:539
msgid "Markup symbols escaped with backslashes (``\\``) are rendered normally. For instance, ``this \\*\\*line of text\\*\\* with \\*markup\\* symbols`` is rendered as “this \\*\\*line of text\\*\\* with \\*markup\\* symbols”."
msgstr ""

#: ../../content/contributing/documentation/rst_cheat_sheet.rst:543
msgid "When it comes to backticks (`````), which are used in many case such as :ref:`hyperlink references <contributing/hyperlink-references>`, using backslashes for escaping is no longer an option because the outer backticks interpret enclosed backslashes and thus prevent them from escaping inner backticks. For instance, ```\\`this formatting\\```` produces an ``[UNKNOWN NODE title_reference]`` error. Instead, `````this formatting````` should be used to produce the following result: ```this formatting```."
msgstr ""

#: ../../content/contributing/documentation/rst_guidelines.rst:4
msgid "RST guidelines"
msgstr ""

#: ../../content/contributing/documentation/rst_guidelines.rst:9
msgid "Use relative links for internal URLs"
msgstr ""

#: ../../content/contributing/documentation/rst_guidelines.rst:11
msgid "If you need to reference an internal documentation page or a file that is not sitting in the same directory as your current page, always make use of *relative file paths* rather than *absolute file paths*. An absolute file path indicates the location of the target from the root of its file tree. A relative file path makes use of smart notations (such as ``../`` git that redirects to the parent folder) to indicate the location of the target *relative* to that of the source document."
msgstr ""

#: ../../content/contributing/documentation/rst_guidelines.rst:20
msgid "Given the following source file tree:"
msgstr ""

#: ../../content/contributing/documentation/rst_guidelines.rst:35
msgid "A reference to the rendered :file:`prices.html` and :file:`variants.html` could be made from :file:`import.rst` as follows:"
msgstr ""

#: ../../content/contributing/documentation/rst_guidelines.rst:38
msgid "Absolute:"
msgstr ""

#: ../../content/contributing/documentation/rst_guidelines.rst:40
msgid "``https://odoo.com/documentation/14.0/applications/sales/sales/products_prices/prices.html``"
msgstr ""

#: ../../content/contributing/documentation/rst_guidelines.rst:41
msgid "``https://odoo.com/documentation/14.0/applications/sales/sales/products_prices/products/variants.html``"
msgstr ""

#: ../../content/contributing/documentation/rst_guidelines.rst:43
msgid "Relative:"
msgstr ""

#: ../../content/contributing/documentation/rst_guidelines.rst:45
msgid "``../prices.html``"
msgstr ""

#: ../../content/contributing/documentation/rst_guidelines.rst:46
msgid "``variants.html``"
msgstr ""

#: ../../content/contributing/documentation/rst_guidelines.rst:48
msgid "The relative links are clearly superior in terms of readability and stability: the references survive version updates, folder name changes and file tree restructurations."
msgstr ""

#: ../../content/contributing/documentation/rst_guidelines.rst:54
msgid "Start a new line before the 100th character"
msgstr ""

#: ../../content/contributing/documentation/rst_guidelines.rst:56
msgid "In RST, it is possible to break a line without forcing a line break on the rendered HTML. Make use of this feature to write **lines of maximum 100 characters**. A line break in a sentence results in an additional whitespace in HTML. That means that you do not need to leave a trailing whitespace at the end of a line to separate words."
msgstr ""

#: ../../content/contributing/documentation/rst_guidelines.rst:62
msgid "You can safely break a line around the separators (``-->``) of ``menuselection`` directives and anywhere in a hyperlink reference. For the ``doc``, ``ref`` and ``download`` directives, this is only true for the label part of the reference."
msgstr ""

#: ../../content/contributing/documentation/rst_guidelines.rst:67
msgid "Example: Line breaks within directive and inline markup"
msgstr ""

#: ../../content/contributing/documentation/rst_guidelines.rst:76
msgid "Be consistent with indentation"
msgstr ""

#: ../../content/contributing/documentation/rst_guidelines.rst:78
msgid "Use only spaces (never tabs)."
msgstr ""

#: ../../content/contributing/documentation/rst_guidelines.rst:80
msgid "Use as many spaces at the beginning of an indented line as needed to align it with the first character of the directive in the line above. This usually implies 3 spaces but you only need 2 for bulleted lists."
msgstr ""

#: ../../content/contributing/documentation/rst_guidelines.rst:85
msgid "Example: The first ``:`` is below the ``i`` (3 spaces)"
msgstr ""

#: ../../content/contributing/documentation/rst_guidelines.rst:94
msgid "Example: The ``:titlesonly:`` and page references start below the ``t`` (3 spaces)"
msgstr ""

#: ../../content/contributing/documentation/rst_guidelines.rst:105
msgid "Example: Continuation lines resume below the ``I``’s of “Invoice” (2 spaces)"
msgstr ""

#: ../../content/contributing/documentation/rst_guidelines.rst:115
msgid "Use the menuselection directive"
msgstr ""

#: ../../content/contributing/documentation/rst_guidelines.rst:117
msgid "Although chaining characters ``‣`` and menu names works fine to indicate a user which menus to click, it is best to use the ``menuselection`` directive (see :ref:`contributing/specialized-directives`) for the same result. Indeed, it renders the menus chain consistently with the rest of the documentation and would automatically adapt to the new graphic chart if we were to switch to a new one. This directive is used inline as follows: ``:menuselection:`Settings --> Products --> Variants```."
msgstr ""

#: ../../content/contributing/documentation/rst_guidelines.rst:127
msgid "Write resilient code"
msgstr ""

#: ../../content/contributing/documentation/rst_guidelines.rst:129
msgid "Prefer the use of ``#.`` in numbered lists instead of ``1.``, ``2.``, etc. This removes the risk of breaking the numbering when adding new elements to the list and is easier to maintain."
msgstr ""

#: ../../content/contributing/documentation/rst_guidelines.rst:131
msgid "Avoid using implicit hyperlink targets and prefer internal hyperlink targets instead. Referencing the implicit target ``How to print quotations?`` is more prone to break than a reference to the explicit target ``_print_quotation`` which never appears in the rendered HTML and is thus even less likely to be modified."
msgstr ""

#: ../../content/contributing/documentation/rst_guidelines.rst:139
msgid "Prefix hyperlink targets with application names"
msgstr ""

#: ../../content/contributing/documentation/rst_guidelines.rst:141
msgid "As hyperlink targets are visible from the entire documentation when referenced with the ``ref`` directive, it is recommended to prefix the target name with that of the related application. For instance, naming a target ``_amazon/form`` instead of ``_form`` avoids unwanted behaviors and makes the purpose of the target clear."
msgstr ""

#: ../../content/contributing/documentation/rst_guidelines.rst:149
msgid "Don’t break hyperlink targets"
msgstr ""

#: ../../content/contributing/documentation/rst_guidelines.rst:151
msgid "When refactoring (improving without adding new content) section headings or hyperlink targets, take care not to break any hyperlink reference to these targets or update them accordingly."
msgstr ""

#: ../../content/contributing/documentation/rst_guidelines.rst:157
msgid "Use single-underscore suffixes for hyperlink references"
msgstr ""

#: ../../content/contributing/documentation/rst_guidelines.rst:162
msgid "Although using a double-underscore suffix works most of the time for classic hyperlink references, it is not recommended as double-underscores normally indicate an anonymous hyperlink reference. This is a special kind of hyperlink reference that makes use of nameless hyperlink targets consisting only of two underscore."
msgstr ""

#: ../../content/contributing/documentation/rst_guidelines.rst:164
msgid "tl;dr: Double-underscore suffixes work until they don’t and are bad practice, use single-underscore suffixes instead."
msgstr ""