diff options
Diffstat (limited to 'files/pt-br/mozilla/localization')
7 files changed, 0 insertions, 865 deletions
diff --git a/files/pt-br/mozilla/localization/guia_rápido/index.html b/files/pt-br/mozilla/localization/guia_rápido/index.html deleted file mode 100644 index 917e513127..0000000000 --- a/files/pt-br/mozilla/localization/guia_rápido/index.html +++ /dev/null @@ -1,33 +0,0 @@ ---- -title: Localização Guia Rápido -slug: Mozilla/Localization/Guia_rápido -tags: - - Guide - - Localization - - Mozilla - - Translation -translation_of: Mozilla/Localization/Quick_start_guide ---- -<p><span id="result_box" lang="pt"><span class="hps">Bem-vindo ao</span> <span class="hps">Mozilla</span> <span class="hps">localização</span></span> (Abreviado como L10n em Inglês)!</p> -<p><span id="result_box" lang="pt"><span class="hps">Se você está aqui</span> <span class="hps">para iniciar</span> <span class="hps">a sua própria</span> <span class="hps">localização</span> <span class="hps">no projeto</span> <span class="hps">Mozilla</span> <span class="hps">ou</span> <span class="hps">para se juntar aos</span> <span class="hps">esforços de uma</span> <span class="hps">localização</span> <span class="hps">existente</span><span>, você veio</span> <span class="hps">ao lugar certo</span><span>.</span></span> <span id="result_box" lang="pt"><span class="hps">Este manual</span> <span class="hps">contém todas as</span> <span class="hps">informações básicas</span><span>, técnicas</span> <span class="hps">que você precisa para</span> <span class="hps">se envolver</span> <span class="hps">no programa</span> <span class="hps">l10n</span> <span class="hps">Mozilla.</span> <span class="hps alt-edited">Vamos guiá-lo</span> <span class="hps">através dos</span> <span class="hps">passos para começar</span><span>, a partir da</span> <span class="hps">configuração do ambiente</span> <span class="hps">inicial para</span> <span class="hps">testar e</span> <span class="hps">lançar</span> <span class="hps">sua própria</span> <span class="hps">localização</span><span>.</span> <span class="hps">Ao longo do caminho</span><span>, você vai aprender</span> <span class="hps">sobre a variedade de</span> <span class="hps">projetos que você pode</span> <span class="hps">contribuir e</span> <span class="hps">as ferramentas utilizadas para</span> <span class="hps">localizá-los</span><span>.</span></span></p> -<p><span class="short_text" id="result_box" lang="pt"><span class="hps">Quando chegarmos</span> <span class="hps">a exemplos específicos</span></span>, <span class="short_text" id="result_box" lang="pt"><span class="hps">vamos</span> <span class="hps">levá-los</span> <span class="hps">ao projeto</span> <span class="hps">Firefox</span></span>, como o projeto é mais amplamente localizado na Mozilla. <span id="result_box" lang="pt"><span class="hps">Como você está perto do</span> <span class="hps">final deste guia</span><span>, você</span> <span class="hps">deve ser capaz de</span> <span class="hps">fazer uma mudança</span> <span class="hps">para</span> <span class="hps">o Firefox</span> <span class="hps">em</span> <span class="hps">sua configuração</span> <span class="hps">local e</span><span>, em seguida,</span> <span class="hps">ver a mudança</span> <span class="hps">na interface do</span> <span class="hps">Firefox</span></span>. <span id="result_box" lang="pt"><span class="hps">Quando terminar</span> <span class="hps">este guia</span><span>, você terá</span> <span class="hps">todas as ferramentas necessárias</span> <span class="hps">para</span> <span class="hps">começar a contribuir</span><span>!</span></span></p> -<p><span id="result_box" lang="pt"><span class="hps">Lembre-se,</span> <span class="hps">este guia irá</span> <span class="hps">instruí-lo</span></span> apenas sobre os aspectos técnicos da Mozilla L10n. Visite a página do <a class="link-https" href="https://wiki.mozilla.org/L10n:Localization_Process" title="https://wiki.mozilla.org/L10n:Overview">Processo L10n</a> para aprender sobre o processo inteiro.</p> -<div style="width: 25%; background-color: #4AA02C; float: left; display: block; margin: 1.5%; border: 1px solid #C4C295; text-align: center; padding: 2.5%; padding-top: 0px;"> - <h2 id="Configuração_Inicial"><a href="/en-US/docs/Mozilla/Localization/Quick_start_guide/Initial_setup?redirectlocale=en-US&redirectslug=Localization_Quick_Start_Guide%2FInitial_setup" title="en/Localization_Quick_Start_Guide/Initial_setup">Configuração Inicial</a></h2> - Tecnologia de preparação para o trabalho de localização.</div> -<div style="width: 25%; background-color: #A2BFF4; float: left; display: block; margin: 1.5%; border: 1px solid #C4C295; text-align: center; padding: 2.5%; padding-top: 0px;"> - <h2 id="Fase_da_tradução"><a href="/en-US/docs/Mozilla/Localization/Quick_start_guide/Translation_phase" title="en/Localization_Quick_Start_Guide/Translation_phase">Fase da tradução</a></h2> - <span class="short_text" id="result_box" lang="pt"><span class="hps">Localização das</span> <span class="hps">ferramentas</span> e <span class="hps">tutoriais para</span> <span class="hps">tradução</span><span>.</span></span></div> -<div style="width: 25%; background-color: orange; float: left; display: block; margin: 1.5%; border: 1px solid #C4C295; text-align: center; padding: 2.5%; padding-top: 0px;"> - <h2 id="Fase_da_garantia_de_qualidade"><a href="/en-US/docs/Mozilla/Localization/Quick_start_guide/QA_phase" title="en/Localization_Quick_Start_Guide/QA_phase">Fase da <span class="short_text" id="result_box" lang="pt"><span class="hps">garantia de qualidade</span></span></a></h2> - Testando os tutoriais de localização.</div> -<div style="width: 92%; background-color: #C0C0C0; float: left; display: block; margin: 1.5%; border: 1px solid #C4C295; text-align: center; padding: 2.5%; padding-top: 0px;"> - <h2 id="Fase_de_liberação"><a href="/en-US/docs/Mozilla/Localization/Quick_start_guide/Release_phase" title="en/Localization_Quick_Start_Guide/Release_phase">Fase de liberação</a></h2> - <span class="short_text" id="result_box" lang="pt"><span class="hps">Passos para</span> <span class="hps">enviar seu</span> <span class="hps">trabalho de localização</span><span>.</span></span></div> -<div style="background-color: white; border: 3px solid; display: block; padding: 20px; margin-top: 20px;"> - <span id="result_box" lang="pt"><span class="hps">Estas</span> <span class="hps">quatro etapas</span> <span class="hps">compõem</span> <span class="hps">o lado</span> <span class="hps">técnico</span> <span class="hps">do programa</span> <span class="hps">de localização</span></span>. Para saber mais sobre as etapas, clique nos links acima. Para um melhor aproveitamento, nós sugerimos que siga passo a passo começando por <a href="/en-US/docs/Mozilla/Localization/Quick_start_guide/Initial_setup?redirectlocale=en-US&redirectslug=Localization_Quick_Start_Guide%2FInitial_setup">Configuração Inicial</a>.</div> -<p> </p> -<div class="note"> - <span id="result_box" lang="pt"><span class="hps">Nota: Este</span> <span class="hps">guia foi escrito para</span> <span class="hps">dois tipos de</span> <span class="hps">contribuintes</span><span>: Os que</span> querem <span class="hps">iniciar uma nova</span> <span class="hps">localização e</span> <span class="hps">aqueles que se integram</span> <span class="hps">a uma</span> <span class="hps">localização</span> <span class="hps">existente.</span></span> <span id="result_box" lang="pt"><span class="hps">É</span> <span class="hps">importante saber</span> <span class="hps">qual tipo de informação</span> <span class="hps">se aplica a</span> <span class="hps">qual tipo de</span> <span class="hps">contribuinte</span><span>.</span></span><span style="display: none;"> </span> <span id="result_box" lang="pt"><span class="hps">Para</span> <span class="hps">ajudá-lo a</span> <span class="hps">filtrar</span> <span class="hps">a informação</span> <span class="hps">mais aplicável</span><span>,</span> <span class="hps">note que</span> <span class="hps">todas as informações</span> <span class="hps">que são exclusivas para</span> <span class="hps">quem está começando</span> <span class="hps">uma nova</span> <span class="hps">localização</span> <span class="hps">será</span> <span class="hps">em fonte</span> <span class="hps"><span style="color: #ffa500;">laranja</span>.</span> <span class="hps">Toda a informação</span> <span class="hps">que é exclusiva para</span> <span class="hps">aqueles que se integram</span> <span class="hps">a uma</span> <span class="hps">localização</span> <span class="hps">existente será</span> <span class="hps">em fonte</span> <span class="hps"><span style="color: #0000ff;">azul</span>.</span></span></div> -<p class="note"> </p> -<p>{{ Next("Localization_Quick_Start_Guide/Initial_setup") }}</p> diff --git a/files/pt-br/mozilla/localization/guia_rápido/initial_setup/index.html b/files/pt-br/mozilla/localization/guia_rápido/initial_setup/index.html deleted file mode 100644 index ec02a3c67c..0000000000 --- a/files/pt-br/mozilla/localization/guia_rápido/initial_setup/index.html +++ /dev/null @@ -1,96 +0,0 @@ ---- -title: Configuração inicial -slug: Mozilla/Localization/Guia_rápido/Initial_setup -translation_of: Mozilla/Localization/Quick_start_guide/Initial_setup ---- -<div class="wiki-right-present wiki-left-closed wiki-left-none" id="wiki-column-container"> -<div class="column-container column-container-reverse"> -<div class="column-strip wiki-column" id="wiki-right"> -<div class="toc toggleable" style="width: auto;"> </div> - -<div class="toc toggleable" style="width: auto;"> </div> - -<div class="toc toggleable" id="toc" style="width: auto;"><span style="line-height: 1.5; background-color: rgb(255, 255, 255);">Você também precisa descobrir se já existe para a sua região um trabalho de localização. Aqui nós falaremos sobre as contas que precisa, bem como as ferramentas e suas configurações que você precisa antes de contribuir.</span></div> -</div> - -<div class="column-main wiki-column text-content" id="wiki-content" style="width: 959px;"> -<article id="wikiArticle"> -<h3 id="New_or_existing" style="line-height: 24px; font-size: 1.71428571428571rem;">New or existing</h3> - -<p>Before anything else, you need to know if you will be creating a new localization or joining an existing one. This will determine what information is most applicable to you throughout the rest of this guide.</p> - -<p>Here's what you do:</p> - -<p>Look through the existing <a class="external link-https external-icon" href="https://wiki.mozilla.org/L10n:Teams" title="https://wiki.mozilla.org/L10n:Teams">localization community directory</a> to see if one already exists for your locale.</p> - -<ol start="1" style="list-style-type: lower-alpha;"> - <li><span style="color: rgb(0, 0, 205);">If a community already exists, reach out to them and ask how you can help.</span></li> - <li><span style="color: rgb(255, 140, 0);">If a community doesn't exist, send an <a class="external link-https external-icon" href="https://groups.google.com/forum/?fromgroups#!forum/mozilla.dev.l10n.new-locales" title="https://groups.google.com/forum/?fromgroups#!forum/mozilla.dev.l10n.new-locales">email to the new-locales newsgroup</a> for additional guidance</span><span style="color: rgb(255, 140, 0);">.</span></li> -</ol> - -<h3 id="Accounts" style="line-height: 24px; font-size: 1.71428571428571rem;">Accounts</h3> - -<p>There are a handful of accounts that you need to be aware as you begin. They're not required for you to begin contributing, but will be required when you are preparing to produce an official release. For now, simply be aware that these will become important as your efforts progress. These accounts will store your code, contributions, and help you produce an official localization.</p> - -<dl> - <dt style="margin-left: 40px;">hg (Mercurial)</dt> - <dd>Mercurial is the revision control environment that houses the main Mozilla source code as well as localized code for each official Mozilla localization. You will need this for localizing Mozilla applications. For anyone to gain access to hg repos, you must visit the <a class="external external-icon" href="http://www.mozilla.org/hacking/committer/" title="http://www.mozilla.org/hacking/committer/">Mozilla Commiter page</a> and follow the process outlined there. <a class="external external-icon" href="https://bugzilla.mozilla.org/show_bug.cgi?id=741305" title="https://bugzilla.mozilla.org/show_bug.cgi?id=741305">Here is an example bug</a> that illustrates the process well. Use <a class="external link-https external-icon" href="https://bugzilla.mozilla.org/enter_bug.cgi?product=mozilla.org&component=Repository%20Account%20Requests&rep_platform=All&op_sys=All&cc=l10n%40mozilla.com&short_desc=l10n%20hg%20account%20for%20John%20Doe%20(ab-CD)" title="https://bugzilla.mozilla.org/enter_bug.cgi?product=mozilla.org&component=Repository%20Account%20Requests&rep_platform=All&op_sys=All&cc=l10n%40mozilla.com&short_desc=l10n%20hg%20account%20for%20John%20Doe%20(ab-CD)">this bug template</a>when filing your hg account registration bug. Add a request about creating your locale's repository to the <a class="external external-icon" href="http://groups.google.com/group/mozilla.dev.l10n.new-locales/topics" title="http://groups.google.com/group/mozilla.dev.l10n.new-locales/topics">new locales newsgroup</a>.</dd> - <dt style="margin-left: 40px;">SVN</dt> - <dd style="margin-left: 40px;">SVN is a revision control environment that Mozilla uses to house Mozilla source websites and their localizations for each official Mozilla localization. See <a class="external link-https external-icon" href="https://wiki.mozilla.org/SVN#SVN_account_for_localizers" title="https://wiki.mozilla.org/SVN#SVN_account_for_localizers">this wiki page</a> about how to gain access to SVN. Add a request about creating your locale's repository to the<a class="external external-icon" href="http://groups.google.com/group/mozilla.dev.l10n.new-locales/topics" title="http://groups.google.com/group/mozilla.dev.l10n.new-locales/topics">new locales newsgroup</a>.</dd> -</dl> - -<dl> - <dt style="margin-left: 40px;">Web-based L10n tools</dt> - <dd style="margin-left: 40px;">We'll talk about these in a little bit. For now, just be aware that should you choose to use them, you may need to create a personal account.</dd> - <dt style="margin-left: 40px;">Mozilla LDAP</dt> - <dd style="margin-left: 40px;">You will need a Mozilla LDAP account once you're ready to have your localization registered on the main Mozilla repositories. Add a request about creating your LDAP account to the<a class="external external-icon" href="http://groups.google.com/group/mozilla.dev.l10n.new-locales/topics" title="http://groups.google.com/group/mozilla.dev.l10n.new-locales/topics"> new locales newsgroup</a>.</dd> - <dt style="margin-left: 40px;">Locale-specific Bugzilla component</dt> - <dd style="margin-left: 40px;">Having a Bugzilla component specific to your locale will help us to track your localization's progress from first steps to official release. It will also notify us when you're having problems unique to your localization team's work. Add a request about creating your locale's Bugzilla component to the <a class="external external-icon" href="http://groups.google.com/group/mozilla.dev.l10n.new-locales/topics" title="http://groups.google.com/group/mozilla.dev.l10n.new-locales/topics">new locales newsgroup</a>.</dd> -</dl> - -<h3 id="Local_environment_tools" style="line-height: 24px; font-size: 1.71428571428571rem;">Local environment tools</h3> - -<p>Similar to accounts, there is a number of environment tools that you should install on your personal computer. These tools will help you to store your contributions, build Mozilla applications and language packs, and test your work. Install and configure them in the following order.</p> - -<div class="note"> -<p>If you're using a Windows machine, you'll need to set up a Unix shell first. <a href="https://www.cygwin.com/">Cygwin</a> is the most popular, but there are others you can find using a quick internet search.</p> -</div> - -<dl> - <dt style="margin-left: 40px;">Perl</dt> - <dd style="margin-left: 40px;">Perl is a programming language that will help you create Mozilla application builds and language packs. You can find the source files and install instructions <a class="external external-icon" href="http://www.perl.org/" title="http://www.perl.org/">here</a>.</dd> - <dt style="margin-left: 40px;">Python</dt> - <dd style="margin-left: 40px;">Python is a programming language in which many of our L10n testing scripts are written. You can find the source files and install instructions <a class="external external-icon" href="http://python.org/" title="http://python.org/">here</a>.</dd> - <dt style="margin-left: 40px;">A solid, Unicode-based, text editor</dt> - <dd style="margin-left: 40px;">Here are some suggestions: - <ul> - <li style="margin-left: 40px;">Windows: <a class="external external-icon" href="http://notepad-plus.sourceforge.net/uk/site.htm" title="http://notepad-plus.sourceforge.net/uk/site.htm">Notepad++</a> or <a class="external external-icon" href="http://www.flos-freeware.ch/notepad2.html" title="http://www.flos-freeware.ch/notepad2.html">Notepad2</a></li> - <li style="margin-left: 40px;">GNU/Linux: <a class="external external-icon" href="http://en.wikipedia.org/wiki/Vim_%28text_editor%29" title="http://en.wikipedia.org/wiki/Vim_(text_editor)">vim</a>, <a class="external external-icon" href="http://projects.gnome.org/gedit/" title="http://projects.gnome.org/gedit/">gedit</a> or <a class="external external-icon" href="http://www.kate-editor.org/kate" title="http://www.kate-editor.org/kate">Kate</a></li> - <li style="margin-left: 40px;">Mac OS X: <a class="external external-icon" href="http://www.barebones.com/products/TextWrangler/" title="http://www.barebones.com/products/TextWrangler/">TextWrangler</a></li> - </ul> - </dd> - <dt style="margin-left: 40px;">GNU make</dt> - <dd style="margin-left: 40px;"><span class="external external-icon">Make is a tool which controls the generation of executables. You can find version</span> 3.79.1 or higher <a class="external external-icon" href="http://www.gnu.org/software/make/" title="http://www.gnu.org/software/make/">here</a>. Unfortunately, other varieties of <code>make</code> won't do.</dd> - <dt style="margin-left: 40px;">autoconf 2.13</dt> - <dd style="margin-left: 40px;">autoconf is a utility that is vital to manually creating Mozilla application builds and language packs. We use version 2.13 and higher for these builds. You can find the source files and install instructions <a class="external external-icon" href="http://www.gnu.org/software/autoconf/" title="http://www.gnu.org/software/autoconf/">here</a>.</dd> - <dt style="margin-left: 40px;">wget</dt> - <dd style="margin-left: 40px;">wget is a command-line utility that allows you to retrieve files using internet protocols. We use it for retrieving files from repositories. You can find the source files and install instructions <a class="external external-icon" href="http://www.gnu.org/s/wget/" title="http://www.gnu.org/s/wget/">here</a>.</dd> - <dt style="margin-left: 40px;">compare-locales</dt> - <dd style="margin-left: 40px;">compare-locales is a Python script that helps you check your work without needing to run Firefox or another application. Install intructions are located <a href="https://developer.mozilla.org/en/Compare-locales" title="https://developer.mozilla.org/en/Compare-locales">here</a>.</dd> - <dt style="margin-left: 40px;">L10n checks</dt> - <dd style="margin-left: 40px;">L10n checks is another Python script that helps you check your work without running an application. Install instructions are located <a href="https://developer.mozilla.org/en/L10n_Checks" title="https://developer.mozilla.org/en/L10n_Checks">here</a>.</dd> - <dt style="margin-left: 40px;">Hg (Mercurial)</dt> - <dd style="margin-left: 40px;">As noted above, we use Mercurial for maintaining Mozilla source code and localized code. Not only will you need a localization repository to store your localizations, but you need to have it installed and configured on your personal computer as well. You can find everything you need to know about installing and configuring Mercurial for your localization work <a href="https://developer.mozilla.org/en/Localizing_with_Mercurial#Install_Mercurial" title="https://developer.mozilla.org/en/L10n_on_Mercurial#Install_Mercurial">here</a>.</dd> - <dt style="margin-left: 40px;">Locale Switcher or Quick Locale Switcher</dt> - <dd style="margin-left: 40px;">Both Locale Switcher and Quick Locale Switcher are add-ons for Mozilla applications. Either one is necessary to enable you to see your work within a Mozilla application. You can install either by searching for them in Firefox's add-ons manager or following <a class="external link-https external-icon" href="https://addons.mozilla.org/en-US/firefox/addon/locale-switcher/" title="https://addons.mozilla.org/en-US/firefox/addon/locale-switcher/">these</a> <a class="external link-https external-icon" href="https://addons.mozilla.org/en-US/firefox/addon/quick-locale-switcher/" title="https://addons.mozilla.org/en-US/firefox/addon/quick-locale-switcher/">links</a>.</dd> -</dl> - -<h2 id="End_of_initial_setup" style="line-height: 30px; font-size: 2.14285714285714rem;">End of initial setup</h2> - -<p>Now that you've finished your initial setup, it's time for the best part: translating!</p> -</article> -</div> -</div> -</div> - -<p> </p> diff --git a/files/pt-br/mozilla/localization/index.html b/files/pt-br/mozilla/localization/index.html deleted file mode 100644 index ca4e66d3ec..0000000000 --- a/files/pt-br/mozilla/localization/index.html +++ /dev/null @@ -1,25 +0,0 @@ ---- -title: Localização na Mozilla -slug: Mozilla/Localization -tags: - - Landing - - Localization - - Localização - - Mozilla - - Tradução - - Translation - - l10n -translation_of: Mozilla/Localization ---- -<p><span class="seoSummary"><strong>Localização</strong> (L10n) é o processo de tradução de interfaces do usuário de softwares de um idioma para outro e sua adaptação a uma cultura estrangeira. Esses recursos são para qualquer pessoa com interesse nos aspectos técnicos envolvidos na localização. Eles são para desenvolvedores e todos os contribuidores.</span></p> - -<h2 id="Veja_também">Veja também</h2> - -<dl> - <dt><a href="/en-US/docs/Project:MDN/Localizing" title="/en-US/docs/Project:MDN/Localizing">Localizando o MDN</a></dt> - <dd>Este recurso abrange a localização da documentação aqui no MDN.</dd> - <dt><a href="/en-US/Apps/Build/Localization">Localização de aplicativos</a></dt> - <dd>Este conjunto de documentos aplica-se mais especificamente à localização de aplicativos, incluindo aplicativos do Firefox OS.</dd> - <dt><a href="/en-US/docs/Web/API/L10n">L10n</a></dt> - <dd>Documentos de referência para a API L10n que a Mozilla usa para localizar o Firefox OS.</dd> -</dl> diff --git a/files/pt-br/mozilla/localization/localization_and_plurals/index.html b/files/pt-br/mozilla/localization/localization_and_plurals/index.html deleted file mode 100644 index 859adb7a4d..0000000000 --- a/files/pt-br/mozilla/localization/localization_and_plurals/index.html +++ /dev/null @@ -1,371 +0,0 @@ ---- -title: Localização e Plurais -slug: Mozilla/Localization/Localization_and_Plurals -tags: - - Internacionalização - - Internationalization - - Localization - - Localização -translation_of: Mozilla/Localization/Localization_and_Plurals ---- -<p>Você provavelmente está aqui porque está localizando um arquivo .properties e ele tem um link para essa página. Essa página ajuda a explicar como localizar essas strings de forma que a forma de plural correta seja mostrada para o usuário. Por exemplo, "1 página" vs "2 páginas".</p> - -<p>Se você está aqui para tornar seu código (ex.: extensões) localizável para formas de plural, você pode pular direto para <a href="#Developing_with_PluralForm">Desenvolvendo com PluralForm</a>, mas se você provavelmente precisa localizar as strings iniciais para seu código, então seria bom também ler pelo menos a seção Uso.</p> - -<p> </p> - -<h2 id="Usage" name="Usage">Uso</h2> - -<p>Aqui estão alguns termos usados nesta página para ajudar a manter as coisas claras:</p> - -<ul> - <li><strong>regra de plural</strong>: Para um idioma dado, há uma regra gramatical sobre como alterar palavras dependendo do número qualificando a palavra. Idiomas diferentes podem ter regras diferentes.</li> - <li><strong>forma de plural</strong>: Para uma regra de plural em particular, pode haver múltiplas formas de uma palavra, tal como "página" e "páginas". Neste caso, há 2 formas, mas outros idiomas podem ter 1 ou muito mais.</li> -</ul> - -<p>Se você está aqui para <code>pluralRule</code> no arquivo <code>chrome/global/intl.properties</code>, você precisa descobrir qual <em>regra de plural</em> deve ser escolhida para sua localização. Essa regra de plural é usada para determinar quantas <em>formas de plural</em> são necessárias para cada palavra que precisa ser localizada com plurais em mente.</p> - -<p>Para todos os demais arquivos de propriedades que possuem link para essa página, você terá que fornecer formas de plural suficiente da palavra desejada e separá-las com ponto e vírgula (;). Se você não sabe quantas formas de plural você precisa, verifique o número de <code>pluralRule</code> em <code>chrome/global/intl.properties</code> e procure pela entrada correspondente à entrada na lista de regras de plural a seguir.</p> - -<h2 id="List_of_Plural_Rules" name="List_of_Plural_Rules">Lista de Regras de Plural</h2> - -<p>Essa seção contém uma lista de regras de plural ordenada por seu número de regras de plural. Cada entrada indica quantas formas de plural são necessárias ao localizar uma palavra. Para cada entrada, há uma lista de famílias e idiomas naquelas famílias para lhe ajudar a descobrir se esta é a regra que você deveria escolher para <code>pluralRule</code>. Adicionalmente, há uma breve descrição de cada forma de plural seguida por alguns exemplos de números que caem naquela forma em particular.</p> - -<p>Para a regra de plural dada, a ordem na qual as formas de plural são listadas está na mesma ordem que você localizar uma palavra, separadas por caractere de ponto e vírgula. Por exemplo, o inglês usa a regra de plural 1, e localizar <code>plurals</code> exigiria uma string de "plural;plurais" na qual a primeira palavra é a forma singular e a segunda é a forma plural geral.</p> - -<h3 id="Plural_rule_.230_.281_form.29" name="Plural_rule_.230_.281_form.29">Regra de plural #<em><strong>0</strong></em> (1 forma)</h3> - -<p><strong>Famílias</strong>: asiática (chinês, japonês, coreano), persa, turca/altaica (turco), tailandês, laociana<br> - <strong>tudo</strong>: <small>0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, …</small></p> - -<h3 id="Plural_rule_.231_.282_forms.29" name="Plural_rule_.231_.282_forms.29">Regra de plural #<em><strong>1</strong></em> (2 formas)</h3> - -<p><strong>Famílias</strong>: germânica (dinamarquês, holandês, inglês, faroês, frísio, alemão, norueguês, sueco), fino-úgricas (estoniando, finlandês, húngaro), língua isolada (basco), latina/grega (grego), semítica (hebráico), românica (italiano, português, espanhol, catalão), vietnamita<br> - <strong>é 1</strong>: <small>1</small><br> - <strong>todo resto</strong>: <small>0, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, …</small></p> - -<h3 id="Plural_rule_.232_.282_forms.29" name="Plural_rule_.232_.282_forms.29">Regra de plural #<em><strong>2</strong></em> (2 formas)</h3> - -<p><strong>Família</strong>: Românica (francês, português brasileiro)<br> - <strong>é 0 ou 1</strong>: <small>0, 1</small><br> - <strong>todo resto</strong>: <small>2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, …</small></p> - -<h3 id="Plural_rule_.233_.283_forms.29" name="Plural_rule_.233_.283_forms.29">Regra de plural #<em><strong>3</strong></em> (3 formas)</h3> - -<p><strong>Famílias</strong>: báltica (letã)<br> - <strong>é 0</strong>: <small>0</small><br> - <strong>termina em 1, excluindo 11</strong>: <small>1, 21, 31, 41, 51, 61, 71, 81, 91, 101, 121, 131, 141, 151, 161, 171, 181, 191, 201, 221, 231, 241, 251, 261, 271, 281, 291, …</small><br> - <strong>todo resto</strong>: <small>2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 22, 23, 24, 25, 26, 27, 28, 29, 30, 32, 33, 34, 35, 36, 37, 38, 39, 40, 42, 43, 44, 45, 46, 47, 48, 49, 50, 52, 53, 54, 55, …</small></p> - -<h3 id="Plural_rule_.234_.283_forms.29" name="Plural_rule_.234_.283_forms.29">Regra de plural #<em><strong>4</strong></em> (4 formas)</h3> - -<p><strong>Famílias</strong>: céltica (gaélico escocês)<br> - <strong>é 1 ou 11</strong>: <small>1, 11</small><br> - <strong>é 2 ou 12</strong>: <small>2, 12</small><br> - <strong>é 3-10 ou 13-19</strong>: <small>3, 4, 5, 6, 7, 8, 9, 10, 13, 14, 15, 16, 17, 18, 19</small><br> - <strong>todo resto</strong>: <small>0, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, …</small></p> - -<h3 id="Plural_rule_.235_.283_forms.29" name="Plural_rule_.235_.283_forms.29">Regra de plural #<em><strong>5</strong></em> (3 formas)</h3> - -<p><strong>Families</strong>: Romanic (Romanian)<br> - <strong>is 1</strong>: <small>1</small><br> - <strong>is 0 or ends in 01-19, excluding 1</strong>: <small>0, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 101, 102, 103, 104, 105, 106, 107, 108, 109, 110, 111, 112, 113, 114, 115, 116, 117, 118, 119, 201, 202, 203, 204, 205, 206, 207, 208, 209, 210, 211, 212, …</small><br> - <strong>everything else</strong>: <small>20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64, 65, 66, 67, 68, 69, …</small></p> - -<h3 id="Plural_rule_.236_.283_forms.29" name="Plural_rule_.236_.283_forms.29">Regra de plural #<em><strong>6</strong></em> (3 formas)</h3> - -<p><strong>Families</strong>: Baltic (Lithuanian)<br> - <strong>ends in 1, excluding 11</strong>: <small>1, 21, 31, 41, 51, 61, 71, 81, 91, 101, 121, 131, 141, 151, 161, 171, 181, 191, 201, 221, 231, 241, 251, 261, 271, 281, 291, …</small><br> - <strong>ends in 0 or ends in 11-19</strong>: <small>0, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 30, 40, 50, 60, 70, 80, 90, 100, 110, 111, 112, 113, 114, 115, 116, 117, 118, 119, 120, 130, 140, 150, 160, 170, 180, 190, 200, 210, 211, 212, 213, 214, 215, 216, 217, 218, 219, 220, …</small><br> - <strong>everything else</strong>: <small>2, 3, 4, 5, 6, 7, 8, 9, 22, 23, 24, 25, 26, 27, 28, 29, 32, 33, 34, 35, 36, 37, 38, 39, 42, 43, 44, 45, 46, 47, 48, 49, 52, 53, 54, 55, 56, 57, 58, 59, 62, 63, 64, 65, 66, 67, 68, 69, 72, 73, …</small></p> - -<h3 id="Plural_rule_.237_.283_forms.29" name="Plural_rule_.237_.283_forms.29">Regra de plural #<em><strong>7</strong></em> (3 formas)</h3> - -<p><strong>Families</strong>: Slavic (Belarusian, Bosnian, Croatian, Serbian, Russian, Ukrainian)<br> - <strong>ends in 1, excluding 11</strong>: <small>1, 21, 31, 41, 51, 61, 71, 81, 91, 101, 121, 131, 141, 151, 161, 171, 181, 191, 201, 221, 231, 241, 251, 261, 271, 281, 291, …</small><br> - <strong>ends in 2-4, excluding 12-14</strong>: <small>2, 3, 4, 22, 23, 24, 32, 33, 34, 42, 43, 44, 52, 53, 54, 62, 63, 64, 72, 73, 74, 82, 83, 84, 92, 93, 94, 102, 103, 104, 122, 123, 124, 132, 133, 134, 142, 143, 144, 152, 153, 154, 162, 163, 164, 172, 173, 174, 182, 183, …</small><br> - <strong>everything else</strong>: <small>0, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 25, 26, 27, 28, 29, 30, 35, 36, 37, 38, 39, 40, 45, 46, 47, 48, 49, 50, 55, 56, 57, 58, 59, 60, 65, 66, 67, 68, 69, 70, 75, 76, 77, …</small></p> - -<h3 id="Plural_rule_.238_.283_forms.29" name="Plural_rule_.238_.283_forms.29">Regra de plural #<em><strong>8</strong></em> (3 formas)</h3> - -<p><strong>Families</strong>: Slavic (Slovak, Czech)<br> - <strong>is 1</strong>: <small>1</small><br> - <strong>is 2-4</strong>: <small>2, 3, 4</small><br> - <strong>everything else</strong>: <small>0, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, …</small></p> - -<h3 id="Plural_rule_.239_.283_forms.29" name="Plural_rule_.239_.283_forms.29">Regra de plural #<em><strong>9</strong></em> (3 formas)</h3> - -<p><strong>Families</strong>: Slavic (Polish)<br> - <strong>is 1</strong>: <small>1</small><br> - <strong>ends in 2-4, excluding 12-14</strong>: <small>2, 3, 4, 22, 23, 24, 32, 33, 34, 42, 43, 44, 52, 53, 54, 62, 63, 64, 72, 73, 74, 82, 83, 84, 92, 93, 94, 102, 103, 104, 122, 123, 124, 132, 133, 134, 142, 143, 144, 152, 153, 154, 162, 163, 164, 172, 173, 174, 182, 183, …</small><br> - <strong>everything else</strong>: <small>0, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 25, 26, 27, 28, 29, 30, 31, 35, 36, 37, 38, 39, 40, 41, 45, 46, 47, 48, 49, 50, 51, 55, 56, 57, 58, 59, 60, 61, 65, 66, 67, 68, …</small></p> - -<h3 id="Plural_rule_.2310_.284_forms.29" name="Plural_rule_.2310_.284_forms.29">Regra de plural #<em><strong>10</strong></em> (4 formas)</h3> - -<p><strong>Families</strong>: Slavic (Slovenian, Sorbian)<br> - <strong>ends in 01</strong>: <small>1, 101, 201, …</small><br> - <strong>ends in 02</strong>: <small>2, 102, 202, …</small><br> - <strong>ends in 03-04</strong>: <small>3, 4, 103, 104, 203, 204, …</small><br> - <strong>everything else</strong>: <small>0, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, …</small></p> - -<h3 id="Plural_rule_.2311_.285_forms.29" name="Plural_rule_.2311_.285_forms.29">Regra de plural #<em><strong>11</strong></em> (5 formas)</h3> - -<p><strong>Families</strong>: Celtic (Irish Gaelic)<br> - <strong>is 1</strong>: <small>1</small><br> - <strong>is 2</strong>: <small>2</small><br> - <strong>is 3-6</strong>: <small>3, 4, 5, 6</small><br> - <strong>is 7-10</strong>: <small>7, 8, 9, 10</small><br> - <strong>everything else</strong>: <small>0, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, …</small></p> - -<h3 id="Plural_rule_.2312_.284_forms.29" name="Plural_rule_.2312_.284_forms.29">Regra de plural #<em><strong>12</strong></em> (6 formas)</h3> - -<p><strong>Families</strong>: Semitic (Arabic)<br> - <strong>is 1</strong>: <small>1</small><br> - <strong>is 2</strong>: <small>2</small><br> - <strong>ends in 03-10</strong>: <small>3, 4, 5, 6, 7, 8, 9, 10, 103, 104, 105, 106, 107, 108, 109, 110, 2</small><small>03, 204, 205, 206, 207, 208, 209, 210, </small><small>…</small><br> - <strong>everything else but is 0 and ends in 00-02, excluding 0-2</strong>: <small>11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, … </small><br> - <strong>ends in 00-02, excluding 0-2</strong>: <small>100, 101, 102, 200, 201, 202, …</small><br> - <strong>is 0</strong>: <small>0</small></p> - -<h3 id="Plural_rule_.2313_.284_forms.29" name="Plural_rule_.2313_.284_forms.29">Regra de plural #<em><strong>13</strong></em> (4 formas)</h3> - -<p><strong>Families</strong>: Semitic (Maltese)<br> - <strong>is 1</strong>: <small>1</small><br> - <strong>is 0 or ends in 01-10, excluding 1</strong>: <small>0, 2, 3, 4, 5, 6, 7, 8, 9, 10, 101, 102, 103, 104, 105, 106, 107, 108, 109, 110, 201, 202, 203, 204, 205, 206, 207, 208, 209, 210, …</small><br> - <strong>ends in 11-19</strong>: <small>11, 12, 13, 14, 15, 16, 17, 18, 19, 111, 112, 113, 114, 115, 116, 117, 118, 119, 211, 212, 213, 214, 215, 216, 217, 218, 219, …</small><br> - <strong>everything else</strong>: <small>20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64, 65, 66, 67, 68, 69, …</small></p> - -<h3 id="Plural_rule_.2314_.283_forms.29" name="Plural_rule_.2314_.283_forms.29">Regra de plural #<em><strong>14</strong></em> (3 formas)</h3> - -<p><strong>Families</strong>: Slavic (Macedonian)<br> - <strong>ends in 1</strong>: <small>1, 11, 21, 31, 41, 51, 61, 71, 81, 91, 101, 111, 121, 131, 141, 151, 161, 171, 181, 191, 201, 211, 221, 231, 241, 251, 261, 271, 281, 291, …</small><br> - <strong>ends in 2</strong>: <small>2, 12, 22, 32, 42, 52, 62, 72, 82, 92, 102, 112, 122, 132, 142, 152, 162, 172, 182, 192, 202, 212, 222, 232, 242, 252, 262, 272, 282, 292, …</small><br> - <strong>everything else</strong>: <small>0, 3, 4, 5, 6, 7, 8, 9, 10, 13, 14, 15, 16, 17, 18, 19, 20, 23, 24, 25, 26, 27, 28, 29, 30, 33, 34, 35, 36, 37, 38, 39, 40, 43, 44, 45, 46, 47, 48, 49, 50, 53, 54, 55, 56, 57, 58, 59, 60, 63, …</small></p> - -<h3 id="Plural_rule_.2315_.283_forms.29" name="Plural_rule_.2315_.283_forms.29">Regra de plural #<em><strong>15</strong></em> (2 formas)</h3> - -<p><strong>Families</strong>: Icelandic<br> - <strong>ends in 1, excluding 11</strong>: <small>1, 21, 31, 41, 51, 61, 71, 81, 91, 101, 121, 131, 141, 151, 161, 171, 181, 191, 201, 221, 231, 241, 251, 261, 271, 281, 291, …</small><br> - <strong>everything else</strong>: <small>0, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 22, 23, 24, 25, 26, 27, 28, 29, 30, 32, 33, 34, 35, 36, 37, 38, 39, 40, 42, 43, 44, 45, 46, 47, 48, 49, 50, 52, 53, 54, …</small></p> - -<h3 id="Plural_rule_.2316_.283_forms.29" name="Plural_rule_.2316_.283_forms.29">Regra de plural #<em><strong>16</strong></em> (6 formas)</h3> - -<p><strong>Families</strong>: Celtic (Breton)<br> - <strong>is 1</strong>: <small>1</small><br> - <strong>ends in 1, excluding 1, 11, 71, 91</strong>: <small>21, 31, 41, 51, 61, 81, 101, 121, 131, 141, 151, 161, 181, 201, 221, 231, 241, 251, 261, 281, ...</small><br> - <strong>ends in 2, excluding 12, 72, 92</strong>: <small>2, 22, 32, 42, 52, 62, 82, 102, 122, 132, 142, 152, 162, 182, 202, 222, 232, 242, 252, 262, 282, ...</small><br> - <strong>ends in 3, 4 or 9 excluding 13, 14, 19, 73, 74, 79, 93, 94, 99</strong>: <small>3, 4, 9, 23, 24, 29, 33, 34, 39, 43, 44, 49, 53, 54, 59, ...</small><br> - <strong>ends in 1000000</strong>: <small>1000000: 1000000, 2000000, 3000000, 4000000, 5000000, 6000000, 7000000, 8000000, 9000000, 10000000, ...</small><br> - <strong>everything else</strong>: <small>0, 5, 6, 7, 8, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 25, 26, 27, 28, 30, 35, 36, 37, 38, 40, ...</small></p> - -<h2 id="Examples" name="Examples">Examples</h2> - -<p>The following are some examples for various languages and a brief thought processes.</p> - -<h3 id="French" name="French">French</h3> - -<p>Some French speaking places treat 0 as plural while others treat it as singular. The only other singular is 1 while everything else is plural. So pick either plural rule #1 or #2.</p> - -<p><code>pluralRule=2<br> - seconds=seconde;secondes<br> - minutes=minute;minutes<br> - hours=heure;heures<br> - days=jour;jours </code></p> - -<p>Like many other times when localizing words, gender agreement might force you to rearrange words in a way that the gender is always the same. (seconde vs jour)</p> - -<h3 id="Chinese" name="Chinese">Chinese</h3> - -<p>A word doesn't change if there is a different number in front of it, so all numbers use the same plural form. With just one plural form, it has to be plural rule #0. For each word to localize, it's just like localizing a single word with no semi-colons needed.</p> - -<p><code>pluralRule=0<br> - seconds=秒<br> - minutes=分<br> - hours=時<br> - days=日 </code></p> - -<h3 id="Polish" name="Polish">Polish</h3> - -<p>There's a singular form for 1, a plural form for 2-4, and another for 5-21 at which point 22 is the same as 2. Plural rule #7 has a "ends in 2-4, not 12-14" but the singular form includes everything ending in 1 except 11. Plural rule #9 has the correct singular form for only 1.</p> - -<p><code>pluralRule=9<br> - seconds=sekunda;sekundy;sekund<br> - minutes=minuta;minuty;minut<br> - hours=godzina;godziny;godzin<br> - days=dzień;dni;dni </code></p> - -<p>Even though the last 2 plural forms of "day" are the same, both are still needed because there needs to be 3 plural forms for each word.</p> - -<h3 id="Sorbian" name="Sorbian">Sorbian</h3> - -<p>There are 4 plural forms: nominative singular, nominative dual, nominative plural, genitive plural. These match up with plural rule #10.</p> - -<p><code>pluralRule=10<br> - seconds=sekunda;sekundźe;sekundy;sekundow<br> - minutes=mjeńšina;mjeńšinje;mjeńšiny;mjeńšin<br> - hours=hodźina;hodźinje;hodźiny;hodźin<br> - days=dźeń;dnjej;dny;dnjow </code></p> - -<h2 id="Testing_Extension" name="Testing_Extension">Testing Extension</h2> - -<p>To help make sure you pick the right plural rule and provide enough plural forms for strings, you should use the pluralForm Checker extension. After installing the extension, it should be available from the Tools menu.</p> - -<p>To use it, list off the property files and properties that you want to check and click the button. The extension will load each property and display the plural forms in a table. Selecting a table entry will populate the bottom box with sample uses of the word for some numbers.</p> - -<p><img alt="Image:pluralForm-checker.0.3.png" class="internal" src="/@api/deki/files/804/=PluralForm-checker.0.3.png"></p> - -<p><a class="external" href="http://ed.agadak.net/firefox/pluralForm-checker.xpi">Install pluralForm Checker v0.3 extension</a></p> - -<h3 id="Extension_input" name="Extension_input">Extension input</h3> - -<p>It would be good to keep this list updated with all the words that need plural forms. People using the extension can then copy/paste this input.</p> - -<p><code><small><a class="external" rel="freelink">chrome://mozapps/locale/downloads/do...tes,hours,days</a><br> - <a class="external" rel="freelink">chrome://mozapps/locale/downloads/do...dsTitlePercent</a><br> - <a class="external" rel="freelink">chrome://browser/locale/browser.prop...ausedDownloads</a> </small></code></p> - -<h3 id="Version_history" name="Version_history">Version history</h3> - -<p>0.1: Initial version with pluralRule check, properties input loading, table generation, sample output display<br> - 0.2: Use PluralForm.numForms() to get the number of forms instead of figuring out locally to better support future rules - <strong>Requires build from 2007/01/27 or later</strong><br> - 0.3: Generate a list of what numbers fall into which plural form to minimize the sample output to at most 3 of each form</p> - -<h2 id="Developing_with_PluralForm" name="Developing_with_PluralForm">Developing with PluralForm</h2> - -<p>The functionality for getting the correct plural forms is provided by a JavaScript Module, <code>PluralForm.jsm</code>. This module provides a couple methods for localizing to the browser's current locale as well as getting methods to localize to a desired plural rule. The latter ability of specifying a plural rule is useful for extensions because the extension doesn't necessarily have to be localized to the browser's locale.</p> - -<h3 id="Loading_PluralForm.jsm" name="Loading_PluralForm.jsm">Loading <code>PluralForm.jsm</code></h3> - -<p>Loading the PluralForm module from JavaScript is simple with <a href="/en/Components.utils.import" title="en/Components.utils.import">Components.utils.import</a>. Just put the following line somewhere that will be evaluated before you want to use PluralForm. At the top of your JavaScript file is fine.</p> - -<pre>Components.utils.import("resource://gre/modules/PluralForm.jsm");</pre> - -<h3 id="Methods:_get" name="Methods:_get">Methods: <code>get</code></h3> - -<p>These methods make use of the browser's current locale specified by <code><a class="external" rel="freelink">chrome://global/locale/intl.properties</a></code>'s <code>pluralRule</code> value.</p> - -<pre>/** - * Get the correct plural form of a word based on the number - * - * @param aNum - * The number to decide which plural form to use - * @param aWords - * A semi-colon (;) separated string of words to pick the plural form - * @return The appropriate plural form of the word - */ -string pluralForm -get(int aNum, string aWords)</pre> - -<p>Here is an example of using this method:</p> - -<pre>// Load PluralForm and for this example, assume English -Components.utils.import("resource://gre/modules/PluralForm.jsm"); - -// PluralForm.get expects a semi-colon separated list of words -let downloads = "download;downloads"; -// Pretend this number came from somewhere else -let num = 10; - -// Display the correct plural form for 10 downloads: "You have 10 downloads.") -print("You have " + num + " " + PluralForm.get(num, downloads) + "."); - -// Try again with a different value: "You have 1 download." -num = 1; -print("You have " + num + " " + PluralForm.get(num, downloads) + ".")</pre> - -<p>The above example works, but is still difficult to localize because we're concatenating strings assuming a particular grammatical structure. The following would be better:</p> - -<pre>Components.utils.import("resource://gre/modules/PluralForm.jsm"); - -let downloads = "You have one download.;You have #1 downloads."; -let num = 10; - -// For English, this would display "You have 10 downloads." -print(PluralForm.get(num, downloads).replace("#1", num);</pre> - -<p>Notice in the above example that the code can be written to support placeholders or not use placeholders in some forms of the string. Additionally, the localizer has control over where the placeholder is in relation to the rest of the text.</p> - -<p>Of course, the strings to be localized will be placed in a separate file such as yourextension.properties instead of being hardcoded in the JavaScript code file.</p> - -<p>The following 3 file snippets show how to use PluralForm with your <code>.xul</code>, <code>.properties</code>, <code>.js</code> files.</p> - -<p><code>downloads.xul</code>:</p> - -<pre><stringbundleset> - <stringbundle id="strings" src="chrome://downloads.properties"/> -</stringbundleset></pre> - -<p><code>downloads.properties</code>:</p> - -<pre># LOCALIZATION NOTE (downloadsTitleFiles): Semi-colon list of plural forms. -# See: http://developer.mozilla.org/en/docs/Localization_and_Plurals -# #1 number of files -# example: 111 files - Downloads -downloadsTitleFiles=#1 file - Downloads;#1 files - Downloads - -# LOCALIZATION NOTE (timePair): #1 time number; #2 time unit -# example: 1 second; 11 seconds -timePair=#1 #2 -seconds=second;seconds -minutes=minute;minutes -hours=hour;hours -</pre> - -<p><code>downloads.js</code>:</p> - -<pre>Components.utils.import("resource://gre/modules/PluralForm.jsm"); -let getStr = function(string) document.getElementById("strings").getString(string); - -// Get the correct plural form for the title -let numDownloads = 3; -let title = PluralForm.get(numDownloads, getStr("downloadsTitleFiles")); -// Put in the correct number of downloads -print(title.replace("#1", numDownloads)); - -// Get the correct plural form of seconds -let timeLeft = 55; -let seconds = PluralForm.get(timeLeft, getStr("seconds")); -// Print the localized string for "55 seconds" -print(getStr("timePair").replace("#1", timeLeft).replace("#2", seconds));</pre> - -<h3 id="Method:_makeGetter" name="Method:_makeGetter">Method: <code>makeGetter</code></h3> - -<p>If you're writing an extension, you'll want to use <code>makeGetter</code> instead of <code>PluralForm.get()</code> or <code>PluralForm.numForms()</code> because someone installing the extension on a different locale will be using the strings provided by your default extension locale. For example, your extension localized for English with plural rule #1, which expects 2 plural forms, is installed on a localized version of Firefox with plural rule #4, which expects 3 forms.</p> - -<pre>/** - * Create a pair of plural form functions for the given plural rule number. - * - * @param aRuleNum - * The plural rule number to create functions - * @return A pair: [function that gets the right plural form, - * function that returns the number of plural forms] - */ -[string pluralForm get(int aNum, string aWords), int numForms numForms()] -makeGetter(int aRuleNum)</pre> - -<p>Here is an example usage of <code>makeGetter</code>:</p> - -<pre>Components.utils.import("resource://gre/modules/PluralForm.jsm"); - -// Let's get Irish (plural rule #11) -let [get, numForms] = PluralForm.makeGetter(11); - -// Make up some values to use with "get" -let dummyText = "form 1;form 2;form 3;form 4;form 5"; -let dummyNum = 10; - -// In the case of Irish, the value 10 uses plural form #4, so "form 4" is printed -print(get(dummyNum, dummyText));</pre> - -<p>In this example, the Irish plural rule was hardcoded, but this could be a value specified in the .properties file. So for your extension, specify a pluralRule value in the .properties and call <code>PluralForm.makeGetter(pluralRuleFromProperties)</code> making sure to save the 2 returned functions. (You can use <a href="/en/JavaScript/New_in_JavaScript/1.7#Destructuring_assignment" title="en/New_in_JavaScript_1.7#Destructuring_assignment">destructured assignment</a> in JavaScript 1.7 to keep things clean.) The returned functions act just like <code>PluralForm.get()</code> and <code>PluralForm.numForms()</code> except for the specified plural rule instead of the default plural rule.</p> - -<h2 id="Credits" name="Credits">Credits</h2> - -<p>Plural Form code first implemented for {{ Bug(394516) }} - <em>Figure out a remaining-time rounding scheme for minutes -> hours/days</em><br> - Plural rules and families derived from <a class="external" href="http://www.gnu.org/software/gettext/manual/html_node/gettext_150.html#Plural-forms">GNU <code>gettext</code> documentation</a>.</p> - -<p> </p> - -<p> </p> - -<p>{{ languages( { "es": "es/Localización_y_Plurales", "fr": "fr/Localisation_et_pluriels", "ja": "ja/Localization_and_Plurals", "pl": "pl/Lokalizacja_i_liczba_mnoga" } ) }}</p> diff --git a/files/pt-br/mozilla/localization/localizing_with_pontoon/index.html b/files/pt-br/mozilla/localization/localizing_with_pontoon/index.html deleted file mode 100644 index efe8ef99b2..0000000000 --- a/files/pt-br/mozilla/localization/localizing_with_pontoon/index.html +++ /dev/null @@ -1,135 +0,0 @@ ---- -title: Traduzindo com o Pontoon -slug: Mozilla/Localization/Localizing_with_Pontoon -tags: - - Tradução -translation_of: Mozilla/Localization/Localizing_with_Pontoon ---- -<p>O <a href="https://pontoon.mozilla.org" title="https://pontoon.mozilla.org">Pontoon</a> é uma ferramenta de tradução (l10n) baseado na web do tipo O-Que-Você-Ver-É-O-Que-Você-Tem (WYSIWYG), usada para traduzir conteúdo web. Na Mozilla, usamos o Pontoon para traduzir os sites da Mozilla e a interface de aplicativo do Firefox OS, conhecida como Gaia. O Pontoon é uma ferramenta muito simples e intuitiva que requer pouca ou nenhuma habilidade técnica para usar no trabalho de tradução. Aqui discutiremos como usar o Pontoon para traduzir projetos, do primeiro acesso até a finalização de suas contribuições. Ao longo do caminho, apontaremos alguns belos recursos que o tornarão mais eficiente e farão suas contribuições de tradução mais fáceis.</p> - -<div class="note"> -<p><strong>Você é um desenvolvedor?</strong> Leia sobre <a href="/en-US/docs/Implementing_Pontoon_Mozilla">implementando Pontoon no seu site</a> ou aprenda como se envolver no <a href="https://github.com/mozilla/pontoon">GitHub</a>.</p> -</div> - -<h2 id="Primeiros_passos">Primeiros passos</h2> - -<p>A <a href="https://pontoon.mozilla.org" title="https://pontoon.mozilla.org">página inicial do Pontoon</a> é muito fácil de usar. Para começar a traduzir o projeto, clique no ícone Persona e entre. Em seguida, simplesmente selecione o projeto que você quer trabalhar e seu idioma nos menus suspensos. O Pontoon abrirá automaticamente esse idioma do projeto para você iniciar. Note que para nossos propósitos aqui, usaremos o site do<a href="https://affiliates.mozilla.org/"> Firefox Afiliados</a> para demonstrar a funcionalidade e fluxo de trabalho do Pontoon. E aí está, aberto dentro do Pontoon:</p> - -<p><em><img alt="Navegador do aplicativo e espaço de trabalho" src="https://mdn.mozillademos.org/files/8323/affiliates.png" style="height: 558px;"></em></p> - -<h3 id="Barra_de_ferramentas_principal">Barra de ferramentas principal</h3> - -<p>Como você pode ver, a maior parte da interface é composta pelo site que está sendo traduzido. Somente a barra de ferramentas no topo pertence ao Pontoon, contendo os seguintes itens (da esquerda para a direita):</p> - -<p><img alt="Barra de ferramentas principal" src="https://mdn.mozillademos.org/files/8325/toolbar.png"></p> - -<h4 id="Lista_de_strings">Lista de strings</h4> - -<p>Abre uma barra lateral com uma lista da todas as strings para traduzir.</p> - -<h4 id="Seletor_de_projeto_(Affiliates)">Seletor de projeto (Affiliates)</h4> - -<p>Alterna entre os projetos para traduzir.</p> - -<h4 id="Seletor_de_recursos_(Homepage)">Seletor de recursos (Homepage)</h4> - -<p>Alterna entre os recursos do projeto para traduzir, como sub-páginas ou arquivos de tradução. Oculta se não há recursos disponíveis para o projeto.</p> - -<dl> -</dl> - -<h4 id="Seletor_de_idioma_(Slovenian)">Seletor de idioma (Slovenian)</h4> - -<p>Alterna entre os idiomas para traduzir.</p> - -<h4 id="Go">Go</h4> - -<p>Abre a seleção de projeto-recurso-idioma.</p> - -<h4 id="Indicador_de_progresso">Indicador de progresso</h4> - -<p>Exibe seu progresso no recurso sendo traduzido. Mais detalhes estão disponíveis na janela de contexto.</p> - -<dl> -</dl> - -<h4 id="Menu_do_usuário">Menu do usuário</h4> - -<p>Permite tarefas específicas do usuário, como enviar para o repositório, baixar arquivos e sair.</p> - -<h4 id="Menu_de_informações">Menu de informações</h4> - -<p>Cede informações importantes, como a linha do tempo antecipada do projeto e uma lista de atalhos do teclado.</p> - -<dl> -</dl> - -<p>Tudo bem, que tal traduzirmos algo agora?<span id="cke_bm_608E" style="display: none;"> </span></p> - -<dl> -</dl> - -<h2 id="Traduzir_strings">Traduzir strings</h2> - -<p>Quando usando o Pontoon para tradução, você tem algumas opções para traduzir suas strings. Você pode traduzir em contexto, fora do contexto, ou uma combinação dos dois. Começaremos olhando na tradução em contexto.</p> - -<h3 id="Em_contexto">Em contexto</h3> - -<p>O modo de tradução em contexto do Pontoon é o que se coloca acima dos outros. Ele abre uma nova página (ou aplicativo) e ativa a edição em tempo real daquela página. Aqui está como você traduz sua primeira string:</p> - -<p><img alt="Tradução em contexto" src="https://mdn.mozillademos.org/files/8331/in-context.png"></p> - -<ol> - <li>Passe com o seu mouse sobre o texto que você quer.</li> - <li>Um botão de edição aparece sobre aquele texto. Clique nele para ativar o modo de tradução.</li> - <li>Substitua o texto original com sua tradução dentro do seu idioma.</li> - <li>Clique no botão de salvar para guardar sua tradução.</li> -</ol> - -<div> -<h3 id="Fora_de_contexto">Fora de contexto</h3> - -<p>Algumas strings são impossíveis de traduzir em contexto, por exemplo, os conteúdos da etiqueta <title> nos sites e strings com regionalismos ou formas plurais diferentes. Clicando no ícone de hambúrguer na barra de ferramentas principal, uma lista de todas as strings e traduções disponíveis abrirá na barra lateral. Você também pode usar a barra lateral para tradução fora de contexto:</p> -</div> - -<p><img alt="Tradução fora de contexto: list" src="https://mdn.mozillademos.org/files/8337/out-of-context-1.png"> <img alt="Tradução fora de contexto: traduzir" src="https://mdn.mozillademos.org/files/8335/out-of-context-2.png"></p> - -<ol> - <li>Clique na string que gostaria de traduzir.</li> - <li>O painel de tradução com a string original e seus detalhes (por exemplo, comentários) será aberto.</li> - <li>Traduza a string na área de tradução abaixo.</li> - <li>Clique no botão de salvar para guardar sua tradução.</li> -</ol> - -<p>Conforme você traduz strings fora de contexto, as traduções também aparecerão no site, se elas também puderem ser traduzidas em contexto.</p> - -<h3 id="Ajudantes_de_tradução">Ajudantes de tradução</h3> - -<p>Como você pode ver, sugestões do histórico, traduções memorizadas, máquina de tradução e outros idiomas também estão disponíveis no painel de tradução fora de contexto. Chamamos tudo isso de ajudantes de tradução e aqui está como cada um deles lhe ajudarão conforme você traduz strings:</p> - -<p><img alt="Ajudantes de tradução: Histórico" src="https://mdn.mozillademos.org/files/8339/helpers-history.png"> <img alt="Ajudantes de tradução: Maquinário" src="https://mdn.mozillademos.org/files/8341/helpers-machinery.png"> <img alt="Ajudantes de tradução: Outros idiomas" src="https://mdn.mozillademos.org/files/8343/helpers-locales.png"> <img alt="Ajudantes de tradução: Pesquisar" src="https://mdn.mozillademos.org/files/8345/helpers-menu.png"></p> - -<h4 id="Histórico">Histórico</h4> - -<p>Exibe traduções sugeridas anteriormente, incluindo de outros usuários.</p> - -<h4 id="Maquinário">Maquinário</h4> - -<p>Exibe combinações de vários serviços: memória de tradução interna, <a href="http://transvision.mozfr.org/">Mozilla Transvision</a>, <a href="https://amagama-live.translatehouse.org/">open source translation memory</a>, <a href="https://www.microsoft.com/Language/pt-BR/Default.aspx">Portal de idiomas da Microsoft</a> e a <a href="http://www.bing.com/translator">máquina de tradução</a>.</p> - -<h4 id="Outros_idiomas">Outros idiomas</h4> - -<p>Exibe traduções compatíveis de outros idiomas.</p> - -<h4 id="Pesquisar">Pesquisar</h4> - -<p>Quase igual ao maquinário, mas Almost like machinery, mas pega a palavra-chave fornecida como parâmetro de entrada em vez da string original.</p> - -<p>Clicando em uma sugestão, ela é copiada para dentro da área de tradução.</p> - -<dl> -</dl> - -<h2 id="Publicando_sua_tradução">Publicando sua tradução</h2> - -<p>Suponhamos que agora você quer publicar seu trabalho de tradução para enviar a um repositório. O Pontoon lhe permite fazer isso também! Na verdade, ele faz isso para você sincronizando automaticamente com os repositórios em bases horárias. Você pode agora dar tapinhas nas suas costas, fazer uma dancinha, ir dormir ou outra coisa para comemorar seu trabalho!</p> diff --git a/files/pt-br/mozilla/localization/localizing_with_verbatim/index.html b/files/pt-br/mozilla/localization/localizing_with_verbatim/index.html deleted file mode 100644 index e5fe258987..0000000000 --- a/files/pt-br/mozilla/localization/localizing_with_verbatim/index.html +++ /dev/null @@ -1,158 +0,0 @@ ---- -title: Localizando com o Verbatim -slug: Mozilla/Localization/Localizing_with_Verbatim -translation_of: Mozilla/Localization/Localizing_with_Pontoon ---- -<p><span class="seoSummary">Verbatim is a web-based tool (specifically a Mozilla-hosted Pootle instance) for localizing Mozilla web content. It can be used to localize a variety of Mozilla projects and is capable of supporting any language. This guide will walk you through localizing a common Mozilla web project.</span> The tutorial here will give you a solid foundation for using Verbatim to localize any Mozilla web project you hope to add to your localization community's efforts. We'll discuss what specific projects Verbatim is currently being used for, how to get started with Verbatim, and the tasks that are commonly accomplished through using Verbatim.</p> - -<h2 id="Getting_started_with_Verbatim">Getting started with Verbatim</h2> - -<p>Being that it is web-based, localizers must be online to use Verbatim. There are essentially two ways to get started with Verbatim: start a new localization or join an existing localization community's efforts. Either way, you will need to follow these steps to start working on a Verbatim project.</p> - -<table style="width: 100%; border-style: solid; border-color: rgb(0,0,0);"> - <thead> - <tr style="text-align: center;"> - <th scope="col" style="text-align: center;"><strong>Start a new localization on Verbatim</strong></th> - <th scope="col" style="text-align: center;"><strong>Join an existing localization on Verbatim</strong></th> - </tr> - </thead> - <tbody> - <tr> - <td> - <ol> - <li>Point your browser to <a class="external" href="http://localize.mozilla.org/">http://localize.mozilla.org</a>. This is where Verbatim is hosted.</li> - </ol> - </td> - <td> - <ol> - <li>Point your browser to <a class="external" href="http://localize.mozilla.org/">http://localize.mozilla.org</a>. This is where Verbatim is hosted.</li> - </ol> - </td> - </tr> - <tr> - <td> - <ol start="2"> - <li>If you have a Mozilla LDAP account, simply sign in using your LDAP credentials. If not, register for an account and sign in once you've completed registration. The links for both are located in the upper right-hand corner of the page.</li> - </ol> - </td> - <td> - <ol start="2"> - <li>If you have a Mozilla LDAP account, simply sign in using your LDAP credentials. If not, register for an account and sign in once you've completed registration. The links for both are located in the upper right-hand corner of the page.</li> - </ol> - </td> - </tr> - <tr> - <td> - <ol start="3"> - <li>File a <a class="link-https" href="https://bugzilla.mozilla.org/enter_bug.cgi?alias=&assigned_to=nobody%40mozilla.org&blocked=&bug_file_loc=https%3A%2F%2Flocalize.mozilla.org%2F&bug_severity=normal&bug_status=NEW&cf_blocking_191=---&cf_blocking_192=---&cf_status_191=---&cf_status_192=---&cf_status_firefox10=---&cf_status_firefox11=---&cf_status_firefox8=---&cf_status_firefox9=---&cf_tracking_firefox10=---&cf_tracking_firefox11=---&cf_tracking_firefox8=---&cf_tracking_firefox9=---&comment=I%20would%20like%20to%20request%20that%20you%20add%20the%20%5Binsert%20your%20locale%20code%20here%5D%20as%20a%20new%20localization%20in%20Verbatim.%0D%0A%0D%0A%5BAdd%20any%20other%20comments%20you%20may%20have%20here.%5D&component=Verbatim&contenttypeentry=&contenttypemethod=autodetect&contenttypeselection=text%2Fplain&data=&defined_groups=1&dependson=&description=&flag_type-4=X&flag_type-607=X&form_name=enter_bug&keywords=&maketemplate=Remember%20values%20as%20bookmarkable%20template&op_sys=All&priority=--&product=Webtools&qa_contact=verbatim%40webtools.bugs&rep_platform=All&requestee_type-325=&requestee_type-4=&requestee_type-607=&short_desc=Request%20for%20new%20localization%20on%20Verbatim&status_whiteboard=&target_milestone=---&version=Trunk" title="https://bugzilla.mozilla.org/enter_bug.cgi?alias=&assigned_to=nobody%40mozilla.org&blocked=&bug_file_loc=https%3A%2F%2Flocalize.mozilla.org%2F&bug_severity=normal&bug_status=NEW&cf_blocking_191=---&cf_blocking_192=---&cf_status_191=---&cf_status_192=---&cf_status_firefox10=---&cf_status_firefox11=---&cf_status_firefox8=---&cf_status_firefox9=---&cf_tracking_firefox10=---&cf_tracking_firefox11=---&cf_tracking_firefox8=---&cf_tracking_firefox9=---&comment=I%20would%20like%20to%20request%20that%20you%20add%20the%20%5Binsert%20your%20locale%20code%20here%5D%20as%20a%20new%20localization%20in%20Verbatim.%0D%0A%0D%0A%5BAdd%20any%20other%20comments%20you%20may%20have%20here.%5D&component=Verbatim&contenttypeentry=&contenttypemethod=autodetect&contenttypeselection=text%2Fplain&data=&defined_groups=1&dependson=&description=&flag_type-4=X&flag_type-607=X&form_name=enter_bug&keywords=&maketemplate=Remember%20values%20as%20bookmarkable%20template&op_sys=All&priority=--&product=Webtools&qa_contact=verbatim%40webtools.bugs&rep_platform=All&requestee_type-325=&requestee_type-4=&requestee_type-607=&short_desc=Request%20for%20new%20localization%20on%20Verbatim&status_whiteboard=&target_milestone=---&version=Trunk">bug</a> using this prefilled bugzilla template. Add your locale code and language name to the description field, as well as any other information you'd like to share. See the following example.</li> - </ol> - - <div class="note"><strong>Example</strong>: I would like to request that you add the <em><strong>en-US</strong></em> as a new localization in Verbatim. The langauge is <em><strong>English</strong></em>. Also, I like cookies. Lots and lots of cookies. I can easily be motivated by any and all baked goods.</div> - </td> - <td> - <ol start="3"> - <li><a class="link-https" href="https://wiki.mozilla.org/Category:L10n_Teams" title="https://wiki.mozilla.org/Category:L10n_Teams">Contact the community</a> to find out which projects they need you to concentrate your efforts on. See the following example for what you could include in your email to the community leaders.</li> - </ol> - - <div class="note"><strong>Example</strong>: I would like to join your localization efforts on Verbatim for this locale. Where would be the best place for me to begin? Also, I would like to buy you a drink to encourage you to let me join the team!</div> - </td> - </tr> - </tbody> -</table> - -<p>Now that you're registered and logged in, we'll outline the general translation workflow, using the <a class="link-https" href="https://localize.mozilla.org/projects/mdn" title="https://localize.mozilla.org/projects/mdn/">MDN project page</a> as our example.</p> - -<h2 id="Translating">Translating</h2> - -<p>First thing's first, you need to find untranslated source strings to translate.</p> - -<ol> - <li>Navigate to the <a class="link-https" href="https://localize.mozilla.org/projects/mdn" title="https://localize.mozilla.org/projects/mdn/">MDN project page</a>.</li> - <li>Select your language from the <strong>Overview</strong> tab.</li> - <li>Now click on the the <strong>Translate</strong> tab. This tab will display the directories for the MDN user interface.</li> - <li>Select the <strong>LC Messages</strong> directory. This is where the project's <code>.po</code> files containing translatable strings are located. You will now see an overview of each <code>.po</code> file.</li> - <li>In the summary column, the number of words untranslated will be shown as a link. Click on that link to be taken directly to the first string that needs to be translated.</li> -</ol> - -<p>Now you're ready to contribute translations and you won't believe how easy it is. Check it out, you can contribute translations in two simple steps:</p> - -<ol> - <li>Simply type your translation in the box to below the English string</li> - <li>Select <strong>Suggest</strong>. If you have approval permission, select <strong>Submit</strong>. You will then be taken to the next string that needs translating.</li> - <li>Hooray! You're translating! Repeat steps one and two for the remainder of the untranslated strings.</li> -</ol> - -<div class="note"><strong>Note</strong>: If you come across a string that already has a suggested translation, you can still suggest your own translation if you feel it is more accurate.</div> - -<h3 id="Some_extra_cool_features_on_Verbatim">Some extra cool features on Verbatim</h3> - -<p>Here are a few additional items about the Verbatim interface that you should be aware of. Some of these can be seen in the screen shot below.</p> - -<p><a href="/@api/deki/files/5930/=Translate_Tab.png" title="Translate Tab.png"><img alt="Translate Tab.png" class="internal default" src="/@api/deki/files/5930/=Translate_Tab.png" style="width: 1113px; height: 221px;"></a></p> - -<ul> - <li>You can copy the English string over to the translation box by clicking the <strong>Copy</strong> icon.</li> - <li>You can use machine translation by clicking on the <strong>Google Translate</strong> icon.</li> - <li>You can move forward and back through the strings by clicking the <strong>Next</strong> and <strong>Previous</strong> buttons.</li> - <li>You can navigate directly to a particular string by clicking it's string number on the far left.</li> - <li>You can mark a translation as <strong>Fuzzy</strong> if you think there could be a better way to say something. This will mark it so it can be found and updated later. Remember that only submitted strings will be commited to the localization's repository, not fuzzy strings. If strings remain marked as fuzzy, the source string will appear in your localized version instead of a translated string.</li> - <li>You can add notes about a particular string in the <strong>Translator Comments</strong> section.</li> - <li>When translating a string with both singular and plural forms you will see two boxes on the right hand side. The box for the singular form is labeled <strong>Plural Form 0</strong> and the box for the plural form is labeled <strong>Plural Form 1</strong>.</li> -</ul> - -<h2 id="Additional_tasks">Additional tasks</h2> - -<p>If you are a localizer with approval priviledges, here are a few more tasks that you should be aware of.</p> - -<h3 id="Review_suggested_translations">Review suggested translations</h3> - -<ol start="1"> - <li>Click on the <strong>Review</strong> tab. It will show how many strings are waiting for review for each <code>.po</code> file.<a href="/@api/deki/files/5931/=Review_Tab1.png" title="Review Tab1.png"><img align="right" alt="Review Tab1.png" class="internal rwrap" src="/@api/deki/files/5931/=Review_Tab1.png?size=webview" style="width: 274px; height: 145px;"></a></li> - <li>Select <span style="font-weight: bold;">Review</span><strong> suggestions</strong> to start approving suggestions. It will take you to the first string that needs to be reviewed.</li> - <li>You can accept the suggestion by clicking the green checkmark or reject the suggestion by clicking the red X (see the screen shot from the previous section).</li> -</ol> - -<p>It is important to note that <em>only</em> submitted strings will appear in your localized pages. Neither suggestions nor fuzzy strings will appear. Before commiting your final localized product, make sure all strings have been submitted.</p> - -<h3 id="Using_VCS_on_Verbatim">Using VCS on Verbatim</h3> - -<p>VCS (<strong>V</strong>ersion <strong>C</strong>ontrol <strong>S</strong>ystem) is the repository system we use to update the project's strings as well as push your translated content onto the web. The difference between the two tasks is simply a matter of which link to click.</p> - -<p><img align="right" alt="VCS.png" class="internal rwrap" src="/@api/deki/files/5925/=VCS.png" style="">To push your strings onto the web and see your changes, simply select the <strong>Commit to VCS</strong> link underneath each file name. It usually takes about an hour before you can see your changes on the project site.</p> - -<p>To update your <code>.po</code> files with new untranslated strings, simple select the <strong>Update from VCS</strong> link underneath each file name.</p> - -<p> </p> - -<div class="note"><br> -<strong>Note</strong>: Some projects are automatically updated nightly while others require you to manually update them to receive new source content. Be sure to pay close attention to this, as it can alter your workflow.</div> - -<h2 id="Translating_Verbatim_files_with_an_external_application">Translating Verbatim files with an external application</h2> - -<p>While in the <strong>Translate</strong> tab, you have the option to export the <code>.po </code>and <code>.xliff</code> files and translate the strings with an external application (i.e., a text editor or translation memory tool).</p> - -<ol> - <li>To download the <code>.po</code> file, select the <strong>Download</strong> link found underneath each file name. To download the .<code>xliff</code> file, select the <strong>Download XLIFF</strong> link.</li> - <li>Proceed to translate the strings using your selected tool.</li> -</ol> - -<p>Once you've finished your translations, you'll need to upload your file to Verbatim. You can do this from the <strong>Translate</strong> tab.</p> - -<ol> - <li>Navigate to the bottom of the files list to the <strong>Upload File</strong> section.</li> - <li>Click on the <strong>Browse</strong> button and select the file you wish to upload.</li> - <li>Select an upload setting from the options provided.</li> - <li>Once your upload setting has been selected, click <strong>Upload</strong>.</li> -</ol> - -<div class="warning"> -<p class="warning"><strong>Important</strong>: There have been some problems in the past with community members updating their source strings while others are in the process of localizing the previous updated files. This can cause community members to overlook new source strings, producing untranslated strings in a localized project. Be sure to coordinate these manual updates within your community to avoid this problem.</p> -</div> - -<h2 id="You're_ready_to_go!">You're ready to go!</h2> - -<p>Whew! You've arrived at the end! Time to take what you've learned and put it to good use spreading Mozilla to everyone in your region. Have fun and <a class="link-mailto" href="mailto:l10n-drivers@mozilla.com" title="l10n-drivers@mozilla.com">let us know</a> if you run into any difficulties. We'll be happy to help in any way we can.</p> - -<p> </p> - -<p><a href="/en/Localization_Quick_Start_Guide:_Translation" title="Localization Quick Start Guide: Translation">Back: Quick Start Guide</a></p> diff --git a/files/pt-br/mozilla/localization/writing_localizable_code/index.html b/files/pt-br/mozilla/localization/writing_localizable_code/index.html deleted file mode 100644 index f403bdbb1c..0000000000 --- a/files/pt-br/mozilla/localization/writing_localizable_code/index.html +++ /dev/null @@ -1,47 +0,0 @@ ---- -title: Escrevendo código localizável -slug: Mozilla/Localization/Writing_localizable_code -tags: - - Internacionalização - - Localização -translation_of: Mozilla/Localization/Writing_localizable_code ---- -<div>Essa página lhe fala sobre as melhores práticas e diretrizes ao lidar com código de UI relacionado a localização. Ela é destinada a desenvolvedores do Mozilla e de extensões.</div> - -<p>Para mais detalhes técnicos, por favor veja também <a href="/pt-BR/docs/XUL_Tutorial/Localization" title="XUL_Tutorial/Localization">UL_Tutorial:Localization</a>.</p> - -<h2 id="About_Localizers" name="About_Localizers">Sobre localizadores</h2> - -<p>Algumas notas sobre localizadores para desenvolvedores que raramente lidam ocm eles:</p> - -<ul> - <li>localizadores gostam de ferramentas, e eles não gostam de editores,</li> - <li>ferramentas de localização geralmente são baseadas em pares de chave-valor,</li> - <li>pelo menos alguns localizadores possuem talentos com foco em habilidades linguísticas e não conhecedores de programação, ou alté mesmo compilação de aplicativos.</li> -</ul> - -<h2 id="Guidelines" name="Guidelines">Diretrizes</h2> - -<p>Portanto, há algunas diretrizes que você deve seguir para facilitar a localização de seu código:</p> - -<dl> - <dt>Escolha bons nomes de chaves</dt> - <dd>Os nomes escolhidos para suas chaves (independentemente de ser um DTD ou um arquivo de propriedade) devem ser descritivos. Pensem neles como sendo nomes longos de variáveis. Se você alterar as semânticas de uma string localizada, altere a chave. Isso provavelmente será um bom nome de chave, e ajudará as ferramentas a compreender que a alteração que você fez é diferente de uma mera correção de ortografia.</dd> - <dt>Tente não presumir a gramática em strings compostas</dt> - <dd>A separação de frases em várias chaves muitas vezes, inadvertidamente, pressupõe uma gramática, uma estrutura de oração e essas strings compostas são muitas vezes muito difíceis de traduzir. Quando uma string composta é necessária, tente dar aos tradutores "espaço para se mover". Um exemplo de uma string composta bem utilizada é a configuração do Firefox para páginas visitadas: o tradutor pode (implicitamente) posicionar o campo de texto como ele bem entender.</dd> - <dt>Não use macros de pré-processador</dt> - <dd>O uso de <code>#if #else #endif</code> ou <code>#expand</code> é fortemente desencorajado. Há algumas exceções a esta regra, mas, em geral, o arquivo localizado deve estar em conformidade com padrões e não devem exigir ferramentas de compilação para serem transformadas. Se você deseja adicionar processamento de compilação a arquivos localizados, certifique-se de solicitar feedback do <a href="/User:AxelHecht" title="User:AxelHecht">l10n@</a>. Na maioria dos casos, você também pode colocar o processamento em código de conteúdo e referência diferentes pares de valor-chave em <code>l10n</code>.</dd> - <dt>Use uma boa estrutura de diretórios de fontes</dt> - <dd>Certifique-se de colocar os arquivos localizáveis no lugar correto. A adição de diretórios de topo de nível é um meio termo entre a propriendade do módulo no repositório no <code>cvsroot</code> e a facilidade de localização.</dd> - <dt>Use uma boa estrutura de diretório de chrome</dt> - <dd>Para um módulo <code>mod</code> em particular, um caminho alvo <code>jar:ab-CD.jar!/locale/ab-CD/mod/foo.dtd</code> foi amplamente testado e é um bom lugar para seus arquivos referenciados como <code><a class="external" rel="freelink">chrome://mod/locale/foo.dtd</a></code>. Usar uma estrutura de diretórios como essa facilita o processo de localização sem o código fonte e é especialmente recomendada para autores de extensão. <a href="pt-BR/docs/Developer_Guide/Intrucoes_Build/Manifestos_JAR" title="JAR_Manifests">Manifestos de JAR</a> podem facilitar isso.</dd> -</dl> - -<h2 id="l10n_impact" name="l10n_impact">Impacto de l10n</h2> - -<p>Em árvores congeladas, há a regra de não verificar alterações de <em>l10n-impact</em>. Então, o que isso significa? <em>l10n-impact</em> é</p> - -<ul> - <li>qualquer alteração a <code>mozilla/@mod@/locales</code>; Localizadores descobrem se eles têm que se atualizar sobre alterações ao fazer consultas de bonsai, assim como todo mundo faz. Nenhuma alteração significa que esse resultado de consulta é vazio.</li> - <li>qualquer uso alterado ou novo de strings localizadas existentes; Qualquer coisa que dispara um ciclo de QA em 40+ localizações é <em>l10n-impact</em>.</li> -</ul> |