# SOME DESCRIPTIVE TITLE. # Copyright (C) 2015, OpenStack contributors # This file is distributed under the same license as the I18n Contributor Guide package. # FIRST AUTHOR , YEAR. # #, fuzzy msgid "" msgstr "" "Project-Id-Version: I18n Contributor Guide 1.0.0\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2017-05-17 04:53+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #: ../about.rst:3 msgid "About this guide" msgstr "" #: ../about.rst:5 msgid "" "This page describes the conventions and tips on writing this guide itself." msgstr "" #: ../about.rst:7 msgid "" "The guide is written in reStructuredText (RST) markup syntax with Sphinx " "extensions. Most conventions follow `those of the openstack-manuals project " "`__." msgstr "" #: ../about.rst:12 msgid "The followings are useful links when writing documents in RST." msgstr "" #: ../about.rst:14 msgid "" "`Sphinx documentation `__" msgstr "" #: ../about.rst:15 msgid "" "`Quick reStructuredText `__" msgstr "" #: ../about.rst:18 msgid "Titles" msgstr "" #: ../about.rst:20 msgid "The convention for heading levels is as follows::" msgstr "" #: ../bug_report.rst:5 msgid "Reporting translation bugs" msgstr "" #: ../bug_report.rst:7 msgid "This page describes how end users can report translation bugs." msgstr "" #: ../bug_report.rst:9 msgid "" "Finding and reporting translation bugs is an important step towards better " "quality of translations in OpenStack." msgstr "" #: ../bug_report.rst:12 msgid "" "When you are using OpenStack (including the dashboard, API or CLI) or are " "reading translated documentations, if you find something wrong, something " "you cannot understand, something you cannot agree, or something to be " "improved, please consider reporting it." msgstr "" #: ../bug_report.rst:18 msgid "Where can I report a bug?" msgstr "" #: ../bug_report.rst:20 msgid "" "OpenStack I18n team uses `Launchpad `_ for the bug tracking." msgstr "" #: ../bug_report.rst:24 msgid "Translation bugs in all languages can be reported here." msgstr "" #: ../bug_report.rst:27 msgid "How can I report a bug?" msgstr "" #: ../bug_report.rst:29 msgid "" "If you visit `openstack-i18n launchpad `_, we can find **Report a bug** at the right-upper corner. Click to " "report a bug." msgstr "" #: ../bug_report.rst:32 msgid "You can report a bug in your language (or English)." msgstr "" #: ../bug_report.rst:34 msgid "It is highly recommended to include the following information." msgstr "" #: ../bug_report.rst:36 msgid "Where you find a bug you are reporting?" msgstr "" #: ../bug_report.rst:38 msgid "For documentations, URL and a detail place would be great." msgstr "" #: ../bug_report.rst:39 msgid "For the dashboard, panel or form name." msgstr "" #: ../bug_report.rst:41 msgid "What is wrong? What should be improved?" msgstr "" #: ../bug_report.rst:42 msgid "" "**Make sure to include your English language name in a bug summary**. It is " "also suggested to write a bug summary in English. For example:" msgstr "" #: ../bug_report.rst:50 msgid "(optional) Put your language name as bug tag." msgstr "" #: ../bug_report.rst:53 msgid "Who can help you?" msgstr "" #: ../bug_report.rst:55 msgid "Everyone in the OpenStack community is glad to help you." msgstr "" #: ../bug_report.rst:57 msgid "" "`Language translation team `_: you can ask in your language :-)" msgstr "" #: ../bug_report.rst:58 msgid "OpenStack I18n team: See :ref:`label-i18n-team-contact`" msgstr "" #: ../check_translation.rst:3 msgid "How to check translations" msgstr "" #: ../check_translation.rst:5 msgid "" "It is important to check your translations by using a real situation where " "your translation is used. This page describes how to check your translations." msgstr "" #: ../check_translation.rst:9 msgid "Documentation" msgstr "" #: ../check_translation.rst:12 msgid "Using docs.openstack.org" msgstr "" #: ../check_translation.rst:14 msgid "" "Translated documents are available at the OpenStack Documentation site. It " "is updated daily. Most contents are linked from either of:" msgstr "" #: ../check_translation.rst:17 msgid "" "http://docs.openstack.org/ contains released documents. Follow \"More " "Releases and Languages\" in http://docs.openstack.org/." msgstr "" #: ../check_translation.rst:19 msgid "" "http://docs.openstack.org/draft/draft-index.html contains draft (unreleased) " "documents." msgstr "" #: ../check_translation.rst:22 msgid "" "To build a translated document, you need to update the file ``doc-tools-" "check-languages.conf`` in each repository, and add an entry to ``BOOKS`` " "like ``[\"ja\"]=\"install-guide\"``. Also, to build as a draft, you need to " "add an entry to ``DRAFTS``." msgstr "" #: ../check_translation.rst:27 msgid "" "For a document in a stable branch, such as the installation guide for " "Liberty, you need to update the file ``doc-tools-check-languages.conf`` in " "the target stable branch directly. You must add an entry to ``DRAFTS``, " "which is used as a special flag for a stable branch." msgstr "" #: ../check_translation.rst:33 msgid "" "You can check a generated document for a specified branch on http://docs." "openstack.org///. For example, the link of " "Ubuntu Installation Guide for Liberty is http://docs.openstack.org/liberty/" "ja/install-guide-ubuntu/." msgstr "" #: ../check_translation.rst:38 msgid "" "To add a link to a generated document, you need to update the file ``www/" "/index.html`` in the ``master`` branch of the ``openstack-manuals`` " "repository. Note that the web pages are published from ``master`` branch, " "which contains the pages for all releases, such as Liberty. Therefore, you " "don't need to update the file ``www//index.html`` in the stable branch." msgstr "" #: ../check_translation.rst:47 msgid "Application developer documentation" msgstr "" #: ../check_translation.rst:49 msgid "" "We can translate the application developer documentations, such as API " "Guide, as ``api-site`` resources in Zanata." msgstr "" #: ../check_translation.rst:53 msgid "OpenStack developer documentation" msgstr "" #: ../check_translation.rst:55 msgid "" "Currently, we do not support translations for OpenStack developer documents: " "http://docs.openstack.org/developer/" msgstr "" #: ../check_translation.rst:59 msgid "OpenStack Dashboard" msgstr "" #: ../check_translation.rst:62 msgid "Translation check site" msgstr "" #: ../check_translation.rst:64 msgid "" "The Infrastructure and I18n teams are preparing the translation check site " "to check dashboard translations. It is under preparation." msgstr "" #: ../check_translation.rst:69 msgid "Currently there is no solid plan when the check site is provided." msgstr "" #: ../check_translation.rst:72 msgid "Running DevStack" msgstr "" #: ../check_translation.rst:74 msgid "" "Another convenient way is to check dashboard translations is to run DevStack " "in your local environment. To run DevStack, you need to prepare ``local." "conf`` file, but no worries. Several ``local.conf`` files are shared on the " "Internet and a minimum example is shown below. From our experience, you need " "a machine with two or four CPU cores, 8 GB memory and 20 GB disk to run " "DevStack comfortably. If you enable just major OpenStack projects, the " "machine requirement would be much smaller like 2~4GB memory." msgstr "" #: ../check_translation.rst:92 msgid "" "Replace ``$BRANCH`` with an appropriate branch such as ``master``, ``stable/" "newton`` or ``stable/mitaka``." msgstr "" #: ../check_translation.rst:95 msgid "" "The following is an example of ``local.conf`` for Newton release which runs " "core components (keystone, nova, glance, neutron, cinder), horizon, swift " "and heat. The components which the main horizon code supports are chosen." msgstr "" #: ../check_translation.rst:103 msgid "Import latest translations" msgstr "" #: ../check_translation.rst:105 msgid "" "Translations are being imported into a project repository daily, so in most " "cases you do not need to pull translations from Zanata manually. What you " "need is to pull the latest horizon code." msgstr "" #: ../check_translation.rst:109 msgid "If you have a machine running DevStack, there are two ways." msgstr "" #: ../check_translation.rst:111 msgid "" "One way is to update the horizon code only. The following shell script " "fetches the latest horizon code, compiles translation message catalogs and " "reloads the apache httpd server. Replace ``$BRANCH`` with an appropriate " "branch such as ``master``, ``stable/newton`` or ``stable/mitaka``." msgstr "" #: ../check_translation.rst:120 msgid "" "The other way is to rerun DevStack. Ensure to include ``RECLONE=True`` in " "your ``local.conf`` before running ``stack.sh`` again so that DevStack " "retrieve the latest codes of horizon and other projects." msgstr "" #: ../check_translation.rst:133 msgid "CLI (command line interface)" msgstr "" #: ../check_translation.rst:135 ../check_translation.rst:140 msgid "TBD" msgstr "" #: ../check_translation.rst:138 msgid "Server projects" msgstr "" #: ../contributing.rst:3 msgid "Contributing" msgstr "" #: ../contributing.rst:5 msgid "The I18n team welcomes any kinds of contribution." msgstr "" #: ../contributing.rst:7 ../contributing.rst:12 msgid "Translations" msgstr "" #: ../contributing.rst:8 ../contributing.rst:37 msgid "Translation tools" msgstr "" #: ../contributing.rst:9 ../contributing.rst:28 msgid "Fixing I18n bugs" msgstr "" #: ../contributing.rst:14 msgid "" "To help with translation, :doc:`become an official translator " "` and join your language team. Then go to `translation " "website`_ to start translation. You can find prioritized translation jobs as " "I18n team at the top of the page." msgstr "" #: ../contributing.rst:18 msgid "" ":doc:`Your language team ` may have useful information to help " "our translation efforts including translation guidelines, priorities, " "communication tools and so on. It is worth visited. You can find your " "language team page at https://wiki.openstack.org/wiki/I18nTeam/team. If you " "have questions, you can contact your coordinators." msgstr "" #: ../contributing.rst:25 msgid "To report translation errors, see :doc:`bug_report`." msgstr "" #: ../contributing.rst:30 msgid "" "If you want to help fix I18n bugs of OpenStack, we can find them in the " "following places:" msgstr "" #: ../contributing.rst:33 msgid "`openstack-i18n in Launchpad`_" msgstr "" #: ../contributing.rst:34 msgid "`Horizon I18n bugs`_" msgstr "" #: ../contributing.rst:39 msgid "" "Go to the `translation tools`_ page to understand the tools and scripts " "which support our translation platform." msgstr "" #: ../contributing.rst:42 msgid "" "If you want to help to report bugs, add more wishlists, and improve them, " "you can report and fix bugs at `openstack-i18n in Launchpad`_. Mark bugs " "with a tag \"tools\"." msgstr "" #: ../glossary.rst:3 msgid "Glossary Management" msgstr "" #: ../glossary.rst:5 msgid "" "Zanata provides suggestions for translation based on a glossary of your " "language. The glossary is maintained in the i18n repository." msgstr "" #: ../glossary.rst:9 msgid "Glossary of your language" msgstr "" #: ../glossary.rst:11 msgid "" "A glossary file of your language is found at ``i18n/locale//" "LC_MESSAGES/i18n.po`` in the i18n repository. The file is a usual PO file." msgstr "" #: ../glossary.rst:15 msgid "" "When you want to update a glossary of your language, edit a corresponding " "glossary file using your favorite editor and propose a change to the Gerrit " "review system." msgstr "" #: ../glossary.rst:19 msgid "" "Once your change is merged, the updated glossary will be uploaded to Zanata. " "Note that the upload to Zanata is a **manual** process now. Only the Zanata " "administrator (usually the I18n PTL and some limited folks) can upload a " "glossary. If your glossary is not uploaded, contact the I18n team or the PTL " "via the i18n mailing list." msgstr "" #: ../glossary.rst:27 msgid "" "Discuss and review glossary changes in your language team before you propose " "changes to the Gerrit review system. Reviewers in the Gerrit review system " "cannot understand your language in most cases, so they can only check syntax " "or conventions." msgstr "" #: ../glossary.rst:33 msgid "Master glossary" msgstr "" #: ../glossary.rst:35 msgid "" "When you add a new entry to the glossary, it is highly recommended to add " "the entry to the master glossary ``i18n/locale/i18n.pot``. By doing this, " "all language teams can share the glossary." msgstr "" #: ../glossary.rst:39 msgid "" "The master glossary is an usual POT file. You can edit it in your favorite " "editor as usual." msgstr "" #: ../glossary.rst:42 msgid "" "After you edit the master glossary, ensure to reflect the change to all " "language glossary files. To do this, run the following command." msgstr "" #: ../glossary.rst:49 msgid "" "Finally, propose a patch including all of the above changes to the Gerrit " "review system." msgstr "" #: ../handling_bugs.rst:3 msgid "Handling translation bugs" msgstr "" #: ../handling_bugs.rst:5 msgid "" "If you are a translator or a person involved in I18n effort, you may be " "interested in triaging and fixing translation bugs :)" msgstr "" #: ../handling_bugs.rst:8 msgid "" "The bug triaging process are following the `general bug triaging process " "`_. If you want to help bug " "triaging tasks, join the `OpenStack I18n bug team `_ first." msgstr "" #: ../handling_bugs.rst:13 msgid "" "Bugs in translated documents or dashboard are mainly classified into the " "following areas:" msgstr "" #: ../handling_bugs.rst:16 msgid "translation bugs" msgstr "" #: ../handling_bugs.rst:17 msgid "bugs in a source project" msgstr "" #: ../handling_bugs.rst:18 msgid "bugs in tool chains" msgstr "" #: ../handling_bugs.rst:21 msgid "Translation bugs" msgstr "" #: ../handling_bugs.rst:23 msgid "" "If a bug reports translation errors of a certain language, it could be " "called **translation bug**. The translation bug should be fixed in the " "translation tool." msgstr "" #: ../handling_bugs.rst:27 msgid "If you are a speaker of this language, you could help" msgstr "" #: ../handling_bugs.rst:29 msgid "tag the bug with a language name" msgstr "" #: ../handling_bugs.rst:30 msgid "confirm the bug or mark it as incomplete" msgstr "" #: ../handling_bugs.rst:31 ../handling_bugs.rst:80 msgid "prioritize the bug" msgstr "" #: ../handling_bugs.rst:33 msgid "If you are a translator of this language, you could help" msgstr "" #: ../handling_bugs.rst:35 msgid "" "assign the bug to you or a member of your language team, and then mark it as " "\"In Progress\"" msgstr "" #: ../handling_bugs.rst:37 msgid "" "fix it by visiting a corresponding resource in Zanata and correcting " "translations." msgstr "" #: ../handling_bugs.rst:42 msgid "" "As a translator, if reported bugs turns out beyond a translation bug, it is " "better to ask I18n team members via the mailing list or the IRC channel. " "They can handle such bugs." msgstr "" #: ../handling_bugs.rst:47 msgid "Bugs in a source project" msgstr "" #: ../handling_bugs.rst:49 msgid "" "The translatable strings are extracted from a source project. So some i18n " "bugs might be caused by bugs in the original strings/source codes of a " "source project which contains these translatable strings. Those kind of bugs " "should be fixed in the source project." msgstr "" #: ../handling_bugs.rst:54 msgid "In most cases, a source project would be one of:" msgstr "" #: ../handling_bugs.rst:56 msgid "`OpenStack manuals `_" msgstr "" #: ../handling_bugs.rst:57 msgid "`Horizon (OpenStack dashboard) `_" msgstr "" #: ../handling_bugs.rst:59 msgid "" "You must determine whether bugs are **translation bugs** or **bugs in a " "source project**. Typical i18n bugs in the source project include:" msgstr "" #: ../handling_bugs.rst:62 msgid "Original string or message is not correct." msgstr "" #: ../handling_bugs.rst:63 msgid "" "Missed translations. Missed translations might be caused by not extracting " "English strings from the source project, or be caused by real missed " "translations. If the translations are missed in two different languages, " "they are probably bugs in the source project. Or else, they are real missed " "translations." msgstr "" #: ../handling_bugs.rst:68 msgid "" "Bugs to report English strings are hard to translate in your language. For " "example, translators cannot control the order of words, or a plural form is " "not supported. Usually, this kind of bugs are in the original strings and " "cannot be fixed just by changing the strings and more work is needed." msgstr "" #: ../handling_bugs.rst:74 msgid "" "If a reported bug turns out to be bugs in a source project, You could help" msgstr "" #: ../handling_bugs.rst:77 msgid "tag it with the project name, for example \"horizon\" or \"docs\"." msgstr "" #: ../handling_bugs.rst:78 msgid "add the source project to \"Also affects project\" of this bug." msgstr "" #: ../handling_bugs.rst:79 msgid "confirm the bug" msgstr "" #: ../handling_bugs.rst:83 msgid "Bugs in tool chains" msgstr "" #: ../handling_bugs.rst:85 msgid "" "If you encounter more complicated things including translation tool chains " "or something others, the most recommended way is to ask it in the I18n " "mailing list ``openstack-i18n@lists.openstack.org``. Of course, you can file " "a bug against a related project directly." msgstr "" #: ../i18n_team_meeting.rst:3 msgid "I18n team meeting" msgstr "" #: ../i18n_team_meeting.rst:5 msgid "" "The I18n team holds weekly meetings on Thursdays at alternating times in " "#openstack-meeting IRC channel. To download ICS file, please visit " "`eavesdrop `_ page." msgstr "" #: ../i18n_team_meeting.rst:10 msgid "Every odd week: 13:00 UTC, Thursday" msgstr "" #: ../i18n_team_meeting.rst:11 msgid "Every even week: 07:00 UTC, Thursday" msgstr "" #: ../i18n_team_meeting.rst:15 msgid "Odd and even values are calculated based on ISO week numbers." msgstr "" #: ../i18n_team_meeting.rst:18 msgid "Meeting agenda" msgstr "" #: ../i18n_team_meeting.rst:20 msgid "" "The meeting agenda is located at `I18nTeamMeeting Wiki `_. You " "can add your topics on the Wiki page." msgstr "" #: ../i18n_team_meeting.rst:24 msgid "Previous meetings" msgstr "" #: ../i18n_team_meeting.rst:26 msgid "" "You can refer to `previous meeting logs with their notes `_." msgstr "" #: ../i18n_team_meeting.rst:30 msgid "IRC meeting commands" msgstr "" #: ../i18n_team_meeting.rst:32 msgid "This is a useful commands for the IRC meeting." msgstr "" #: ../index.rst:3 msgid "OpenStack I18n Guide" msgstr "" #: ../index.rst:9 msgid "" "Internationalization (I18n) is essential to make OpenStack ubiquitous. The " "mission of OpenStack I18n team is to make OpenStack ubiquitously accessible " "to people of all language backgrounds, by enhancing OpenStack software " "internationalization, providing translation, maintaining a translation " "platform and managing translation process for better quality of outcomes." msgstr "" #: ../index.rst:16 msgid "" "This guide provides detailed instructions on the I18n contribution workflow " "and conventions to be considered by all contributors." msgstr "" #: ../index.rst:20 msgid "Contents" msgstr "" #: ../index.rst:43 msgid "Getting in touch" msgstr "" #: ../index.rst:46 msgid "Language translation team" msgstr "" #: ../index.rst:48 msgid "" "Each language team has useful information to help our translation efforts. " "It is worth visited. You can find your language team at https://wiki." "openstack.org/wiki/I18nTeam/team." msgstr "" #: ../index.rst:56 msgid "OpenStack I18n team" msgstr "" #: ../index.rst:58 msgid "" "Mailing List: `openstack-i18n@lists.openstack.org `_" msgstr "" #: ../index.rst:60 msgid "IRC channel: ``#openstack-i18n`` on freenode" msgstr "" #: ../index.rst:61 msgid ":doc:`IRC meeting `" msgstr "" #: ../index.rst:64 msgid "Search in this guide" msgstr "" #: ../index.rst:66 msgid ":ref:`search`" msgstr "" #: ../infra.rst:3 msgid "Translation infrastructure" msgstr "" #: ../infra.rst:5 msgid "" "A series of scripts in OpenStack infrastructure is used to manage " "translation changes in Zanata. Without running the scripts, translation " "changes will not be reflected into OpenStack projects. This page explains " "how the infrastructure scripts runs as Jenkins jobs and monitor the jobs " "status." msgstr "" #: ../infra.rst:11 msgid "Translation jobs" msgstr "" #: ../infra.rst:13 msgid "" "We have two types of Jenkins jobs for translations: syncing Zanata with the " "latest repositories and pushing translations into the repositories. The " "first job is for Zanata-side updates. It enables Zanata to have up-to-date " "texts to be translated by comparing OpenStack project repositories and " "Zanata. On the other hand, the second job is aimed to reflect changes " "related to translations. For example, if you contribute translations in " "Zanata, the translation results need to be pushed to the corresponding " "repositories." msgstr "" #: ../infra.rst:21 msgid "" "To find updates for both Zanata and OpenStack project repositories, Jenkins " "starts to run scripts everyday at **6:00 UTC**." msgstr "" #: ../infra.rst:24 msgid "" "Note that not all translation changes are the target for translation jobs. " "The goal is to have consistent translated programs, UIs, and documentation. " "There's not much sense if only a few lines are translated. The team has " "decided that files that have at least 75 percent of messages translated will " "be in the git repositories." msgstr "" #: ../infra.rst:30 msgid "" "To not have too much churn and last minute string fixes lead to files get " "removed, there is also a lower threshold for releases of **66 percent** of " "messages translated as policy - which is only manually enforced." msgstr "" #: ../infra.rst:35 msgid "" "The OpenStack infra scripts currently download new files that are at least " "**75 percent** translated and if files grow over time but do not get new " "translations (or strings change too much), they will be removed again " "automatically from the project with a lower threshold of currently **40 " "percent**." msgstr "" #: ../infra.rst:42 msgid "Monitoring translation jobs status" msgstr "" #: ../infra.rst:44 msgid "" "`OpenStack Health `__ " "dashboard provides us a convenient way to check the translation job status." msgstr "" #: ../infra.rst:47 msgid "" "`Post jobs - Syncing to Zanata `__" msgstr "" #: ../infra.rst:48 msgid "" "`Periodic jobs: Syncing into repos `__" msgstr "" #: ../infra.rst:51 msgid "Translation infrastructure scripts" msgstr "" #: ../infra.rst:53 msgid "" "Translation infrastructure scripts are stored and managed in `openstack-" "infra/project-config `__ repository." msgstr "" #: ../infra.rst:57 msgid "" "`upstream_translation_update.sh `__" msgstr "" #: ../infra.rst:59 msgid "Implements the first Jenkins job (Syncing to Zanata)." msgstr "" #: ../infra.rst:61 msgid "" "`propose_translation_update.sh `__" msgstr "" #: ../infra.rst:63 msgid "Carries out the second Jenkins job (Syncing into repos)." msgstr "" #: ../infra.rst:65 msgid "" "`common_translation_update.sh `__" msgstr "" #: ../infra.rst:67 msgid "" "Common code used by **propose_translation_update.sh** and " "**upstream_translation_update.sh**" msgstr "" #: ../infra.rst:70 msgid "" "`create-zanata-xml.py `__" msgstr "" #: ../infra.rst:72 msgid "Python script to setup projects for Zanata" msgstr "" #: ../infra.rst:74 msgid "" "`include/build-releasenotes.sh `__" msgstr "" #: ../infra.rst:76 msgid "" "Builds release notes in both the original (English) version and translated " "versions (if any)." msgstr "" #: ../infra.rst:79 msgid "" "Note that the scripts use `zanata-cli `__ to pull and push translation content." msgstr "" #: ../lang_team.rst:3 msgid "Language Team" msgstr "" #: ../lang_team.rst:5 msgid "" "OpenStack I18n team is a team to coordinate all language translations and " "cooperation with the I18n team and the development teams. I18n team usually " "has a working plan." msgstr "" #: ../lang_team.rst:9 msgid "" "Although each language team could follow the I18n team working plan, your " "team may also decide your own work items and priorities as a language team." msgstr "" #: ../lang_team.rst:13 msgid "" "Each language team may have useful information to help our translation " "efforts including translation guidelines, priorities, communication tools " "and so on. It is worth visited. You can find your language team page at " "https://wiki.openstack.org/wiki/I18nTeam/team. If you have questions, you " "can contact your coordinators." msgstr "" #: ../lang_team.rst:20 msgid "" "If you cannot find your local team, you can request to :ref:`create a local " "translation team `." msgstr "" #: ../lang_team.rst:24 msgid "Roles in a Language Team" msgstr "" #: ../lang_team.rst:26 msgid "There are three different roles in a translation team:" msgstr "" #: ../lang_team.rst:29 msgid "A person who can submit translations." msgstr "" #: ../lang_team.rst:29 msgid "Member (translator)" msgstr "" #: ../lang_team.rst:32 msgid "" "A person who can proofread translations and mark them as reviewed (approved) " "or rejected." msgstr "" #: ../lang_team.rst:33 msgid "Reviewer" msgstr "" #: ../lang_team.rst:36 msgid "" "A privileged member in a translation team who can help in team management " "tasks, such as approving new members and reviewing contributions to that " "language. We also have task coordinators for specific tasks." msgstr "" #: ../lang_team.rst:39 msgid "Coordinator" msgstr "" #: ../lang_team.rst:42 msgid "Managing a Language Team" msgstr "" #: ../lang_team.rst:44 msgid "" "This section tries to share best practices on how team coordinators manages " "their language team. Feel free to add useful information!" msgstr "" #: ../lang_team.rst:47 msgid "" "When a new member request is received, a coordinator approves (or rarely " "rejects) the request. At the moment, Zanata provides no way to communicate " "with language team members, so it is better to inform the new member of ways " "usually used in the language team." msgstr "" #: ../lang_team.rst:51 msgid "" "When a translation period towards a new OpenStack release approaches, it is " "recommended to coordinate and prioritize translation efforts." msgstr "" #: ../lang_team.rst:53 msgid "" "Setting up a communication channel among team members is recommended. It " "encourage team communications to discuss various translation related topics." msgstr "" #: ../lang_team.rst:56 msgid "" "It is a good idea to organize glossaries and initiate related discussion." msgstr "" #: ../lang_team.rst:57 msgid "..." msgstr "" #: ../lang_team.rst:59 msgid "" "Of course there is no need that team coordinators do all items. You can " "collaborate your team members and share ideas." msgstr "" #: ../lang_team.rst:65 msgid "Creating a Language Team" msgstr "" #: ../lang_team.rst:67 msgid "" "If you want to create a language team and you want to be a coordinator, " "please follow below steps:" msgstr "" #: ../lang_team.rst:70 msgid "" "Follow :doc:`the step ` to register an ID in the " "translation website." msgstr "" #: ../lang_team.rst:73 msgid "" "Write an email to \"openstack-i18n@lists.openstack.org\" to introduce " "yourself and the language team you want to create, together with your ID on " "Zanata." msgstr "" #: ../lang_team.rst:77 msgid "" "When your request is approved, add an item in \"Local Translation Teams\" in " "the wiki page, create a wiki page under page `I18nTeam `_ (for example, I18nTeam/team/zh_cn) to " "introduce your team, with the following information at least: the contact " "information, the web page, and the work items." msgstr "" #: ../lang_team.rst:84 msgid "" "Then, your locale translation team is created successfully. You can enroll " "more people to join and start your translation work." msgstr "" #: ../lang_team.rst:87 msgid "" "Keep in mind to work with your `local user group `_ and the `OpenStack Ambassadors `_ to raise awareness and gather members :)" msgstr "" #: ../official_translator.rst:3 msgid "Official OpenStack translator" msgstr "" #: ../official_translator.rst:6 msgid "Steps to become a OpenStack translator" msgstr "" #: ../official_translator.rst:8 msgid "" "Translation is another kind of important contribution to OpenStack " "community. If you want to become a official translator, you need to finish " "following steps:" msgstr "" #: ../official_translator.rst:12 msgid "" "Before you start contribution, you'll have to `agree to the contributor " "license agreement `_. (You can preview the full text of `the OpenStack " "Individual Contributor License Agreement `_ first if you want.)" msgstr "" #: ../official_translator.rst:21 msgid "" "If you want to become a translator only, simply speaking, you need to `join " "The OpenStack Foundation `_ (select " "\"Foundation Member\") and `sign the appropriate Individual Contributor " "License Agreement `_." msgstr "" #: ../official_translator.rst:28 msgid "Register a user ID in Zanata" msgstr "" #: ../official_translator.rst:30 msgid "Go to `Zanata server `_" msgstr "" #: ../official_translator.rst:31 msgid "Click \"Log in\" button." msgstr "" #: ../official_translator.rst:32 msgid "" "If you don't have OpenStack ID, `register one `_." msgstr "" #: ../official_translator.rst:34 msgid "" "After you log in with OpenStack ID, you will be requested to fill in your " "profile." msgstr "" #: ../official_translator.rst:39 msgid "" "You are encouraged to register with your business email, which will help " "your company to get the credit. If you don't want to, use your personal " "email will be OK too." msgstr "" #: ../official_translator.rst:43 msgid "Request to join a translation team" msgstr "" #: ../official_translator.rst:45 msgid "Click \"Languages\" on the top, all languages will be listed." msgstr "" #: ../official_translator.rst:46 msgid "" "Click the language you want to translate, the language page will be shown." msgstr "" #: ../official_translator.rst:48 msgid "Click \"...\" on the right, and select \"Request to join team\"." msgstr "" #: ../official_translator.rst:49 msgid "" "Input a short introduction of yourself, including your name, as \"Additional " "information\", then click \"Send message\"." msgstr "" #: ../official_translator.rst:54 msgid "" "Make sure to include a short introduction because it is the only information " "which language coordinators can use to determine your join request is valid " "or not." msgstr "" #: ../official_translator.rst:58 msgid "When your request is approved, you will get an email notification." msgstr "" #: ../official_translator.rst:60 msgid "" "Now you can start your translation. You can actually become an OpenStack " "official translator by contributing translations. You can find :doc:`various " "ways of contributions `." msgstr "" #: ../official_translator.rst:66 msgid "ATC status in I18n project" msgstr "" #: ../official_translator.rst:68 msgid "" "The I18n project is an official OpenStack project, so official translators " "who have contributed in a specific period are regarded as \"ATC\" (Active " "Technical Contributor) and \"APC\" (Active Project Contributor) of the I18n " "project. APC can vote for the I18n PTL (Project Team Lead), and ATC can vote " "for OpenStack TC (Technical Committee). For more detail on ATC, APC and TC, " "see `OpenStack Technical Committee Charter `__." msgstr "" #: ../official_translator.rst:78 msgid "" "As of now, ATC of official translators are treated as extra ATCs as we have " "no way to collect statistics automatically now. The list of extra ATCs is " "maintained by the PTL and is usually updated short before the deadline of " "extra ATCs nomination in each release cycle. The deadline of extra ATCs " "nomination can be checked in the release schedule page at http://releases." "openstack.org/ (for example, http://releases.openstack.org/newton/schedule." "html)." msgstr "" #: ../official_translator.rst:86 msgid "" "Translators who translate and review 300 and more words combinedly in the " "last six months until the deadline of extra ATCs nomination are nominated as " "ATCs, and the ATC status of translators is valid for one year. Translation " "count and review count can be added up. The detail period is determined by " "the PTL in each cycle. For Newton cycle, the six month period was from " "2016-02-01 to 2016-07-31, and this ATC status will expire on July 2017 if " "there will be no additional translation contributions." msgstr "" #: ../official_translator.rst:97 msgid "" "I18n PTL updates the list using Zanata API and translator list. Detail " "statistics data is available at: https://wiki.openstack.org/wiki/I18nTeam/" "ATC_statistics." msgstr "" #: ../official_translator.rst:101 msgid "" "If you have a question, feel free to ask it to the PTL or the i18n list." msgstr "" #: ../official_translator.rst:103 msgid "" "Note that contributors to openstack/i18n repository are acknowledged as ATC " "automatically in the same way as for most OpenStack projects." msgstr "" #: ../release_management.rst:3 msgid "Team activities with release" msgstr "" #: ../release_management.rst:5 msgid "" "This page documents what I18n team concerns and which things are needed to " "do with OpenStack releases. Each OpenStack release has around 6-month cycle " "and the corresponding schedule is available on https://releases.openstack." "org/ (e.g., https://releases.openstack.org/ocata/schedule.html describes " "Ocata release schedule)." msgstr "" #: ../release_management.rst:11 msgid "" "One of main goals in I18n team is to incorporate translated strings into a " "new release so that more global users experience translated version of " "OpenStack. To accomplish this goal, some of team activities need to be " "aligned with a release schedule." msgstr "" #: ../release_management.rst:18 msgid "" "I18n team sets target projects to be translated and prioritizes during " "around the Forum (renamed from the Design Summit). Current translation plan " "and priority are available on `translation dashboard `_." msgstr "" #: ../release_management.rst:25 msgid "The terms in this page follow release schedule pages." msgstr "" #: ../release_management.rst:27 msgid "[Project] Release milestone-3. ``Soft StringFreeze`` is in effect." msgstr "" #: ../release_management.rst:28 msgid "[Translator] Start translations for the release." msgstr "" #: ../release_management.rst:30 msgid "Translate **master** version on Zanata." msgstr "" #: ../release_management.rst:32 msgid "[I18n PTL] Call for translation" msgstr "" #: ../release_management.rst:34 msgid "" "[I18n PTL] Coordinate release and translation import schedule of individual " "projects with PTL or I18n liaison." msgstr "" #: ../release_management.rst:37 msgid "" "[Project] Release RC1 and create a stable branch. ``Hard StringFreeze`` is " "in effect." msgstr "" #: ../release_management.rst:40 msgid "[Zanata admin] Create a stable version such as ``stable-newton``" msgstr "" #: ../release_management.rst:42 msgid "" "The stable version is created from the master version on Zanata once RC1 is " "cut and a stable branch is created in a git repository." msgstr "" #: ../release_management.rst:44 msgid "" "Once a stable version corresponding to a project stable branch is created on " "Zanata, the infra script will push strings automatically." msgstr "" #: ../release_management.rst:47 msgid "" "[Translator] Translate **stable-XXXX** version instead of master version on " "Zanata." msgstr "" #: ../release_management.rst:50 msgid "" "At this stage, the master version on Zanata is still open for translations, " "but it is strongly suggested to work on a stable version." msgstr "" #: ../release_management.rst:53 msgid "" "[Infra] Setup translation jobs such as ``translation-jobs-newton`` to import " "translations for stable branches." msgstr "" #: ../release_management.rst:56 msgid "This should be done after a stable version on Zanata is created." msgstr "" #: ../release_management.rst:58 msgid "" "[Translator] It is suggested to complete translation work by Monday or " "Tuesday of the Final RC week." msgstr "" #: ../release_management.rst:61 msgid "" "[Project] RC2 or RC3 release will be shipped with latest translations. Final " "RC release will happen one week before the official release week." msgstr "" #: ../release_management.rst:64 msgid "[Project] Official release!" msgstr "" #: ../release_management.rst:66 msgid "[Zanata admin] Merge a stable version back into the master version." msgstr "" #: ../release_management.rst:68 msgid "This usually happens within a week after the release." msgstr "" #: ../release_management.rst:69 msgid "" "The stable version is well reviewed, so it makes sense to merge translations " "into the master version on Zanata to avoid translating the same strings " "again." msgstr "" #: ../release_management.rst:73 msgid "" "After the official release, translating master version is welcome for " "upstream translation contribution, but the original strings may be changed " "frequently due to upstream development on the projects." msgstr "" #: ../release_management.rst:77 msgid "" "On the other hand, translating stable version as upstream contribution is " "not encouraged after the translated strings are packaged with releases. The " "stable version will be closed earlier than or around EOL." msgstr "" #: ../release_management.rst:81 msgid "" "If there is a translation bug on a stable version in Zanata, it is highly " "recommended to fix the same translation bug on the corresponding string in " "the master version." msgstr "" #: ../reviewing-translation-import.rst:3 msgid "Reviewing translation imports" msgstr "" #: ../reviewing-translation-import.rst:5 msgid "" "This document explains to reviewers details about the automatic import of " "translations from Zanata." msgstr "" #: ../reviewing-translation-import.rst:8 msgid "" "If you are unfamiliar with translations in OpenStack, read the `Project Team " "Guide on Internationalization and Translation `_ first." msgstr "" #: ../reviewing-translation-import.rst:14 msgid "This document gives additional information." msgstr "" #: ../reviewing-translation-import.rst:18 msgid "How are translations handled?" msgstr "" #: ../reviewing-translation-import.rst:20 msgid "" "Translators translate repositories using the `translation server `_ which runs the Zanata software." msgstr "" #: ../reviewing-translation-import.rst:23 msgid "" "Every day, new translations get imported into the repositories using a " "proposal job. These need to have a review on whether the bot worked " "properly. You can see all open reviews in `Gerrit `_. The subject of these " "patches is always \"Imported Translations from Zanata\"." msgstr "" #: ../reviewing-translation-import.rst:31 msgid "Reviewing" msgstr "" #: ../reviewing-translation-import.rst:33 msgid "If you are reviewing these translations, keep the following in mind:" msgstr "" #: ../reviewing-translation-import.rst:35 msgid "" "The change is done by a bot. If anything looks wrong with it, you need to " "actively reach out to the :ref:`OpenStack I18n team ` " "and point the problem out." msgstr "" #: ../reviewing-translation-import.rst:38 msgid "" "The goal of the review is that the structure of the change is fine, it's not " "that the strings are translated properly. The review of translated strings " "is done by teams using the translation server." msgstr "" #: ../reviewing-translation-import.rst:41 msgid "" "If you notice bad translations in a language, file a bug (see :ref:" "`reporting_translation_bugs`). Then the translation team will update the " "translation. We recommend to still import this change as is and import later " "the fix to not block other valid translations to merge." msgstr "" #: ../reviewing-translation-import.rst:46 msgid "" "Nobody should change translation files (the `.po` files in the `locale` " "directory) besides the bot. The next automatic import will override any " "change again. Therefore, leave a ``-1`` vote on any such changes and point " "developer to this document." msgstr "" #: ../reviewing-translation-import.rst:50 msgid "" "The proposal bot also removes files, it removes files that have very few " "translations in them. Note that no translations will be lost, they are still " "in the translation server." msgstr "" #: ../reviewing-translation-import.rst:53 msgid "" "Most teams have single approval for translation imports instead of two core " "reviewers." msgstr "" #: ../reviewing-translation-import.rst:57 msgid "Setting up translations for a repository" msgstr "" #: ../reviewing-translation-import.rst:59 msgid "" "The Creator's Guide of the Infrastructure Manual explains how to `Enable the " "Translation Infrastructure `_." msgstr "" #: ../translation_stats.rst:3 msgid "Translation Statistics" msgstr "" #: ../translation_stats.rst:5 msgid "There are several ways to know your translation activity." msgstr "" #: ../translation_stats.rst:8 msgid "Zanata" msgstr "" #: ../translation_stats.rst:10 msgid "Zanata provides ways to know your activity on Zanata." msgstr "" #: ../translation_stats.rst:12 msgid "" "`Dashboard `__ page shows your " "recent activity statistics this month and detail activity." msgstr "" #: ../translation_stats.rst:14 msgid "" "`Profile `__ page provides more " "nice statistics view. It shows your statistics in this month and last month." msgstr "" #: ../translation_stats.rst:18 msgid "" "Note that you need to log into Zanata to see your activity in the above " "pages." msgstr "" #: ../translation_stats.rst:21 msgid "Stackalytics" msgstr "" #: ../translation_stats.rst:23 msgid "" "`Stackalytics `__ is a popular web site which " "allows us to know various statistics related to OpenStack. It supports " "translation statistics :)" msgstr "" #: ../translation_stats.rst:27 msgid "" "Visit `Stackalytics `__ and choose " "``Translations`` as ``Metric`` dropdown menu at the upper-right." msgstr "" #: ../translation_stats.rst:31 msgid "FAQ: I cannot find my name in Stackalytics" msgstr "" #: ../translation_stats.rst:33 msgid "" "There are cases where you cannot see your translation statistics in " "Stackalytics even after you translate strings in Zanata." msgstr "" #: ../translation_stats.rst:36 msgid "Here is the check list for such case:" msgstr "" #: ../translation_stats.rst:38 msgid "" "Is your Zanata ID included in the `translator list `__?" msgstr "" #: ../translation_stats.rst:40 msgid "Is your Zanata ID different from your launchpad ID?" msgstr "" #: ../translation_stats.rst:42 msgid "" "If your Zanata ID is not included in the translator list, you need to add " "your Zanata ID to the list. Contact your language coordinator, email the " "i18n mailing list, or submit a patch to add your ID by yourself." msgstr "" #: ../translation_stats.rst:53 msgid "" "If your Zanata ID is different from your launchpad ID, Stackalytics will not " "find your translation statistics. You need to let Stackalytics know your ID " "mappings. To do this, you need to add your user data into ``etc/detault_data." "json`` in `the Stackalytics repository `__. An example is https://review.openstack.org/#/" "c/284638/1/etc/default_data.json." msgstr "" #: ../translation_stats.rst:60 msgid "" "If you are lucky to use a same name for launchpad and Zanata IDs, you do not " "need to do the above. Stackalytics will find your statistics automatically." msgstr "" #: ../translation_tips.rst:3 msgid "Translation tips" msgstr "" #: ../translation_tips.rst:5 msgid "This page collects small tips and tricks around translations." msgstr "" #: ../translation_tips.rst:7 msgid "If you have any, don't hesitate to share it :)" msgstr "" #: ../translation_tips.rst:10 msgid "Where a string is used in source code?" msgstr "" #: ../translation_tips.rst:12 msgid "" "It is important to understand how an original string is used in the source " "code with contextual knowledge for better quality of translations. " "Unfortunately Zanata translation interface does not show where a target " "string is used in a source code correspondingly." msgstr "" #: ../translation_tips.rst:17 msgid "You can find the location in a source code by checking the POT file." msgstr "" #: ../translation_tips.rst:19 msgid "" "The POT file is found under ``http://tarballs.openstack.org/translation-" "source////." "pot``, where:" msgstr "" #: ../translation_tips.rst:23 msgid "```` is Zanata project name," msgstr "" #: ../translation_tips.rst:24 msgid "" "```` is Zanata project version such as ``master`` or " "``stable-mitaka``," msgstr "" #: ../translation_tips.rst:26 msgid "" "```` is a path of a document such as ``nova/locale``, " "``openstack_dashboard/locale`` or ``releasenotes/source/locale``," msgstr "" #: ../translation_tips.rst:28 msgid "```` is a document name in Zanata." msgstr "" #: ../translation_tips.rst:30 msgid "" "The easiest way would be to open http://tarballs.openstack.org/translation-" "source and then follow ````, ```` and " "corresponding links." msgstr "" #: ../translation_tips.rst:34 msgid "" "Open a POT file you find and search a string you are interested in. Then you " "can find an entry like:" msgstr "" #: ../translation_tips.rst:44 msgid "" "Once you find location(s) of a string you would like to check, you can check " "more detail context where the string is used by looking at the code in the " "git repository. Zanata project and git repository are one-to-one " "relationship. If Zanata project name is ````, the " "corresponding git repository location is ``http://git.openstack.org/cgit/" "openstack//``. For example, if you are translating " "``horizon``, the git repository is found at http://git.openstack.org/cgit/" "openstack/horizon/." msgstr "" #: ../translation_tips.rst:56 msgid "" "POT files are no longer stored in git repositories. The change was made at " "the beginning of Newton development cycle [#]_." msgstr "" #: ../translation_tips.rst:59 msgid "http://lists.openstack.org/pipermail/openstack-dev/2016-May/094215.html" msgstr "" #: ../translation_tips.rst:62 msgid "Where a string is used in Dashboard UI?" msgstr "" #: ../translation_tips.rst:64 msgid "" "During translating a dashboard related project, you may want to know \"where " "is this string used in the dashboard?\"." msgstr "" #: ../translation_tips.rst:67 msgid "" "You can estimate where a string is used from a location in a source code. " "(See the previous entry on how to find a location.)" msgstr "" #: ../translation_tips.rst:71 msgid "" "This means \"Aggregates\" menu in \"Admin\" group in the left side menu. In " "Horizon code, the second level corresponds to a dashboard group like " "\"Project\" or \"Admin\" and the third level corresponds to a panel like " "\"Aggregates\" (in this example), \"Instances\" or \"Networks\"." msgstr "" #: ../translation_tips.rst:74 msgid "``dashboards/admin/aggregates/views.py:104``" msgstr "" #: ../translation_tips.rst:77 msgid "" "When a filename is ``workflows.py`` or ``forms.py``, it means it is used in " "a form for creating or editing something." msgstr "" #: ../translation_tips.rst:78 msgid "``dashboards/project/loadbalancers/workflows.py:44``" msgstr "" #: ../translation_tips.rst:81 msgid "" "A template is a skeleton of static HTML files. In this case, the string is " "perhaps used in \"Update\" form in \"Container\" menu." msgstr "" #: ../translation_tips.rst:81 msgid "``dashboards/project/containers/templates/containers/_update.html:21``" msgstr ""