Translation Workflow/fr: Difference between revisions

    From KDE UserBase Wiki
    (Created page with ";Immersif : Écrire des communiqués aussi séduisants et compréhensifs que la technologie dont ils traitent.")
    (Created page with ";Sensé : Utilisez des exemples réels et des conseils authentiques, afin de véhiculer un message personnel et pertinent.")
    Line 26: Line 26:
    : Écrire des communiqués aussi séduisants et compréhensifs que la technologie dont ils traitent.
    : Écrire des communiqués aussi séduisants et compréhensifs que la technologie dont ils traitent.


    ;Meaningful
    ;Sensé
    : Use real examples and genuine recommendations to make the message personal and relevant.
    : Utilisez des exemples réels et des conseils authentiques, afin de véhiculer un message personnel et pertinent.


    ===Know Your Skills===
    ===Know Your Skills===

    Revision as of 09:44, 1 August 2012

    La plupart des informations sur cette page sont dépassées. Les pages de guide existent pour toutes les tâches contributives, y compris les traductions, qu'elles soient en ligne ou hors-ligne, et peuvent être consultées à partir de la page Tâches et outils.

    Warning

    En éditant des pages déjà marquées pour la traduction, vous verrez des marqueurs de section du type < !--T:1-- >. En fait, chaque paragraphe est une section. Vous ne devez pas modifier les marqueurs, à moins que vous ne supprimiez complètement une section. Dans ce cas, vous devez simplement retirer l'ancien marqueur. Quand vous ajoutez des sections, vous n'avez pas à y ajouter de nouveau marqueur – ils seront automatiquement ajoutés lorsque vos modifications seront approuvées. Si vous voulez déplacer une section, déplacez aussi les marqueurs avec. C'est le seul cas où vous devez toucher au marqueurs - le système s'occupera du reste.


    Méthodes communes à toutes les langues

    Information

    Cette section est nouvelle, et sera contrôlée par des traducteurs expérimentés.


    Le style KDE

    Les qualités attendues de KDE sont l'utilité, l'ambition et l'authenticité. Nos communiqués s'efforcent d'être :

    Efficaces
    Mettre en avant l'efficacité — en supprimant des étapes et réduisant le travail, nous réduisons les coûts.
    Sans effort
    Communiquer avec des termes simples. Soyez concis, intuitif, expressif et fluide.
    Utiles
    Répondre aux besoins réels et ouvrir de nouvelles opportunités.
    Immersif
    Écrire des communiqués aussi séduisants et compréhensifs que la technologie dont ils traitent.
    Sensé
    Utilisez des exemples réels et des conseils authentiques, afin de véhiculer un message personnel et pertinent.

    Know Your Skills

    KDE relies on volunteer translators to help make useful KDE information available around the world. As volunteers, you are not required to have any formal language training, but we do ask that you know your fluency and get the support you need to finish a translation if you run into tricky language issues or content that lies outside your translation capabilities.

    Because many of the articles on KDE wiki are technical in nature, it also helps to be familiar with—and even fluent in—KDE products. You will need to be able to distinguish between common terms and technical terms in context and determine when user interface or workflow elements that are mentioned in the articles need to be translated.


    General guidelines

    Expressions, jargon, and humor
    As you translate, you may encounter expressions, puns, or jargon that are specific to the original language and may be difficult to translate effectively.
    In such cases, translate the concept or point the article is trying to convey and not the exact words.
    Take care to ensure you capture the overall message, and don't worry about losing the humor or the colloquialism.
    Proper names
    Company names and product names should never be translated. Proper company names and product names should always remain in English, no matter what language you are translating for.
    People's names should remain in English for Latin-based languages, but you may transliterate them for non-Latinbased alphabets.
    Terminology
    For help with translating tricky constructions or technical terms, consult the translation-sharing site to: TAUS.
    Simply enter your desired text and then choose which language to translate it from and to. Not all terms are included for all languages, but this can be a helpful tool for completing accurate translations.
    Titles of works
    When you run across the title of a book, program, feature, distro, or other public work, check to see if that title has already been officially translated for your language (by the publisher or distributor), and if so, use that translation.
    If you cannot find a translation for that particular title in your language, do your best to translate it as accurately as possible.
    Units of measurement
    Convert units of measure to make them relevant for the intended language or region. For example, some English-speaking countries use the unit of inch, but other countries may prefer centimeter unit.
    User interface terms
    Translate user interface terms as appropriate for your language.


    See here for more information:

    1. http://translate.sourceforge.net/wiki/guide/start

    2. Glossary: http://translate.sourceforge.net/wiki/guide/glossary

    3. Another Glossary: http://www.glossary.com/category.php?q=Computer

    Guidelines specific to a Language

    We propose to have Team Leaders for each language. As we get leaders appointed, they will take charge of a page of guidelines for their specific language, where they will be named. They will have final say on any question relating to their language. The guidelines will be linked from Language-specific guideline pages.

    Keeping up to date with developments

    I propose that the Discussion page attached to this page should be used for orderly debate about issues noted, particularly issues where existing markup is causing problems. Old threads, long since resolved will be cleaned out, and once decisions are made I will update the relevant help pages. I would ask you to put a Watch on Talk:Translation_Workflow.

    Getting a Better Understanding of the Process

    For a fuller description of the Translate extension, read the description on the developers' website

    Tip

    Monitor the status of your language statistics by monitoring the page Special:LanguageStats if you have your own language set as the interface language of UserBase.

    Language-specific guideline pages

    Tip

    Mediawiki is not yet good at supporting RTL languages. Currently, the workaround is to add < div dir="rtl" > at the start of your translation (i.e. in the first message) and < /div > after the final category statement


    Catalan
    Chinese
    Danish
    French
    Galician
    German
    Italian
    Romanian
    Russian
    Spanish
    Ukrainian