Revision as of 10:03, 20 April 2018 by ChristianW (talk | contribs) (Created page with "Plusieurs problèmes ont été identifiés et discutés; les solutions sont proposées dans les sections suivantes :")

Modifier le marquage

Other languages:
English • ‎español • ‎français • ‎polski • ‎suomi • ‎中文(中国大陆)‎

Outils disponibles

  • Typographical guidelines standardizes markup for use in translation, either to official manuals (DocBook) or to other languages. Please refer to this frequently, as markup will be refined to match translators' needs.

Etape 1 du travail

Corriger l'ancien marquage

  • Vérifiez que chaque titre de section ou de sous-section est suivi d'une ligne vide.
  • Many pages have multiple indents set. This was included in earlier mediawiki documentation, but is not longer acceptable as it causes problems for exporting to other formats, so please re-arrange, using single indents only. Bullets can continue to be used nested.
  • Les smiley ASCII génèrent des problèmes et doivent être supprimés. Ils peuvent être remplacés par des icônes Oxygen en petite taille (11pixels ?). Mais on en trouve beaucoup plus sur Wikimedia Commons - ajouter ici des précisions.
  • Internal links in the form [[Translation Workflow]] should be edited to the complete form, showing link, then visible text such as [[Special:myLanguage/Translation_Workflow|Translation Workflow]]
  • Many styles have been used to display input text, including <code>, <pre> and tables and boxes. Text intended to be input by the user should use the Input template, {{Input|1=input text (can be multi-line or single)}}. You can still use <code> for very short input, if you don't want the text to appear on a separate line.
  • Output from terminal and error messages have been similarly marked with a variety of methods. These should be replaced with the Output template, {{Output|1=terminal output}}
  • Every page should end with a Category statement. These must be standardized categories. A current list of categories can be found on any of the translators' pages linked from this language page
  • Make sure that there are no unbalanced brackets in any section. If you find unbalanced brackets then add the missing bracket(s) — possibly in a comment like this:
    <!--(--> a)
  • There should be a blank line between bullets in lists. See the sections on lists beginning with Bulleted Lists.
  • Tables should be split in a similar manner, so that there is a blank line between each row. The first and last items will need to have curly braces balanced.

Etape 2 - Guide du nouveau marquage

Liens de marquage pour les traductions

  • A stand-alone link, such as the application-names in Applications/Internet, should use the form [[Special:myLanguage/Ark|<translate>Ark </translate>]]
  • Where the link is within a sentence the whole of the link should be kept within the translatable message.

Balises spéciales

  • Identify all keyboard key-names, and tag, e.g. <keycap>Enter</keycap>
  • Include concurrent keypresses in the <keycap> tag, e.g. Ctrl + Alt + F1. Note that the separator is (space)+(space)
  • Treat menu sequences in a similar manner, using the <menuchoice> tag, e.g.System Settings -> Account Details -> Social Desktop. Note that the separator is (space)->(space)
NEVER add translate section tags (the ones that look like < !--T:18-- >). The software will do any handling of tags that is required, and manually changing them will break the system.

Type gras

  • Identify program names and mark them as bold type, e.g. Klipper
  • Identify labels and names that cannot be changed by the user, and mark them as bold type.
  • Remove any bold type marking that were previously entered, but do not match this guideline. (See below for emphasizing a word or phrase.)
  • Window captions and Icon labels are also marked as bold type.


  • Italics can be used to give emphasis as you might in non-technical writing
  • Use italics on the first appearance of an unfamiliar word or phrase, and if possible link it to #Glossary or a dictionary entry.
  • When referencing other (external) works, titles are italicized.

Gras et italliques combinés

  • This should only be used in the context of an example where the user has to substitute text, e.g. "Your new addressbook records are in /home/user/share/contacts"
Définitions simplifiées - les programmes sont lancés par les utilisateurs, les composants sont utilisés par les programmes

Sujets posant des problèmes de traduction

Plusieurs problèmes ont été identifiés et discutés; les solutions sont proposées dans les sections suivantes :

These are usually noticed after the first markup, and it may be necessary to re-arrange spacing and/or structure to avoid the problems.

Presque la fin

  • In the summary field at the bottom, enter that you are doing a markup edit.
  • Use Preview and read through the whole of your work. If you are satisfied, save the page.
  • Use this page to request release - you can add the URL of the page you have edited. Pasting your link there tells us that you believe the page to be ready for translators to work with. We will scan it, and if satisfied we will enable it for translation.

This page was last edited on 18 August 2019, at 22:45. Content is available under Creative Commons License SA 4.0 unless otherwise noted.