diff options
Diffstat (limited to 'files/pt-pt/mozilla/localization')
11 files changed, 1723 insertions, 0 deletions
diff --git a/files/pt-pt/mozilla/localization/aplicação_tradução_com_mercurial/index.html b/files/pt-pt/mozilla/localization/aplicação_tradução_com_mercurial/index.html new file mode 100644 index 0000000000..ef44aa26fa --- /dev/null +++ b/files/pt-pt/mozilla/localization/aplicação_tradução_com_mercurial/index.html @@ -0,0 +1,282 @@ +--- +title: Tradução da Aplicação com Mercurial +slug: Mozilla/Localization/aplicação_tradução_com_mercurial +translation_of: Mozilla/Localization/Application_Translation_with_Mercurial +--- +<h4 id="draft">{{draft}}</h4> + +<h2 id="Verifique_qual_o_idioma_que_está_disponível_para_tradução">Verifique qual o idioma que está disponível para tradução</h2> + +<ol> + <li>Find out on which branch localization is done for your locale: Read <a href="https://l10n.mozilla.org/teams/">your localization team's page</a> by clicking on the team with your <a href="https://en.wikipedia.org/wiki/Language_code">language code</a> (e.g. "de" for German). The localization lead for your language knows the branch. The <strong>default localization branch</strong> is <strong>aurora</strong>.</li> + <li>Next check what is still untranslated by going to <a href="https://l10n.mozilla.org/teams/">Localization status page</a> and click on the page for your language.</li> + <li>In the section "Applications & Sign-offs", you will find different products and branches which are currently in translation. + <ul> + <li>gaia-* denotes branches of <a href="http://www.mozilla.org/en-US/firefox/os/">Firefox OS</a>, the operating system for mobile devices.</li> + <li>Firefox and fx-* denote branches of <a href="http://www.mozilla.org/firefox">Firefox for Desktop</a>, the browser for desktops and notebooks running, Windows, Mac OS or Linux.</li> + <li>Fennec and fennec-* denote branches of <a href="http://www.mozilla.org/en-US/firefox/fx/">Firefox for Mobile</a>, the Firefox browser for the Android operating system.</li> + <li>Thunderbird and tb-* denote branches of <a href="http://www.mozilla.org/thunderbird">Thunderbird</a>, the mail client, newsgroup and feed reader and chat client. The localization of the <a href="https://www.mozilla.org/en-US/projects/calendar/">Lightning calendar add-on </a>also takes place on these branches.</li> + <li>SeaMonkey and sea-* denote branches of <a href="http://www.seamonkey-project.org/">SeaMonkey</a>, the suite consisting of browser, mail and chat client and more.</li> + <li>Lightning and cal-* denote branches of Lightning, the calendar add-on for Thunderbird. The localization of Lightning now happens on Thunderbird's tb-* branches, the cal-* branches have been retired.<span id="cke_bm_478E" style="display: none;"> </span></li> + </ul> + </li> + <li>In this example, we assume Firefox for Desktop shall be localized and that the localization branch is aurora. Scroll to the <strong>fx_aurora</strong> text.</li> + <li>Read the text next to it. + <ul> + <li>If it is '<strong>Translated</strong>', the branch has already been translated. Either translate a different product now or contact the person responsible for localization from the team's page (see above) so he can notify you by mail when the next strings for translation become available.</li> + <li>If it is a red text consisting of a <strong>number</strong> and the word '<strong>missing</strong>', then there are untranslated texts and you can move on with this guide.<br> + </li> + </ul> + </li> +</ol> + +<h2 id="Ferramentas_Necessárias">Ferramentas Necessárias</h2> + +<h4 id="Pré-requisitos_de_criação">Pré-requisitos de criação</h4> + +<p>First, get the required programs to compile Mozilla applications like Firefox and Thunderbird from <a href="/pt-PT/docs/Guia_do_desenvolvedor/Instruções_de_compilação">Instruções de Compilação</a>. This is only necessary once.</p> + +<div class="warning"> +<p>MozillaBuild deve estar instalado num caminho de ficheiro absoluto sem espaços em branco, senão este será interrompido..</p> +</div> + +<h4 id="Programa_de_comparação_de_ficheiro">Programa de comparação de ficheiro</h4> + +<p>For the translation, it is recommend to use file comparison program to compare the English file (containing the new texts) with the file of your locale (which is still missing the new strings). This example uses <a href="http://winmerge.org/">WinMerge</a>: Download and install it. A comparison of alternatives (e.g. for Linux and Mac OS) is available on <a href="https://en.wikipedia.org/wiki/Comparison_of_file_comparison_tools">Wikipedia</a>.</p> + +<h4 id="Editor_de_ficheiro_e_texto">Editor de ficheiro e texto</h4> + +<p>For editing individual files a text editor can be a better choice than a file comparion program, e.g. because the file is new and everything has to be translated, the file is too customized to compare it to the English one, or special functionality is required (e.g. bookmarking untranslated lines). Use a text editor you are comfortable with. This example uses <a href="http://notepad-plus-plus.org/">Notepad++</a>.</p> + +<h4 id="Ferramenta_de_monitorização_do_progresso">Ferramenta de monitorização do progresso</h4> + +<p>To track which strings and files already have been translated and later also to see which new strings have already been tested in the product as being a good translation for the functionality behind the translated strings and that the translated texts fit into the available, the translation progress should be tracked. This can be done in a text editor or word processor or any other tool in which you can attach different kind of states to the individual texts to translate. The Firefox extension <a href="https://addons.mozilla.org/firefox/addon/scrapbook/">Scrapbook</a> is used in this guide. Install it into your default Firefox profile (you will have more than one profile when following this guide).</p> + +<h2 id="Obter_os_Textos_atuais_em_inglês_e_o_seu_idioma">Obter os Textos atuais em inglês e o seu idioma</h2> + +<h4 id="Obter_os_textos_em_inglês_com_o_código_fonte">Obter os textos em inglês com o código fonte</h4> + +<p>Get the source code by downloading the following file:</p> + +<ul> + <li><strong>Firefox Desktop</strong> or <strong>Firefox for Android</strong>: Download the <strong>mozilla-<branch>.hg</strong> file (e.g. mozilla-aurora.hg) from <a href="https://ftp.mozilla.org/pub/mozilla.org/firefox/bundles/">https://ftp.mozilla.org/pub/mozilla.org/firefox/bundles/</a> The file is not small, but after initially downloading it, you only need to download the latest changes in the future.</li> + <li><strong>Thunderbird</strong>, <strong>Lightning</strong> or <strong>SeaMonkey</strong>: Download the <strong>comm-<branch>.hg</strong> file (e.g. comm-aurora.hg) from <a href="http://ftp.mozilla.org/pub/mozilla.org/thunderbird/bundles/">https://ftp.mozilla.org/pub/mozilla.org/thunderbird/bundles/</a></li> +</ul> + +<p>In the next step, we will unpack the source code:</p> + +<ol> + <li>Open an input shell, e.g. by pressing the Windows key and R on the keyboard <img alt="Screenshot of Windows key + R key" src="https://mdn.mozillademos.org/files/7211/windows%20key%20plus%20r.png" style="height: 30px; width: 82px;"> or by calling the "<code>Run...</code>" command from the Windows "Start" button, and then typing <code><strong>cmd</strong></code> and pressing the Enter key.</li> + <li>Launch the installed MozillaBuild toolset by launching it with its path, e.g. <code>C:\Mozilla\Coding\Buildtools\MozillaBuild\start-shell-msvc2010.bat</code> You can autocomplete the file path after typing a few characters and then pressing the Tabulator key.<br> + If you launch the start-shell-l10n.bat, compiling features will be disabled. You can create translation patches, but creating language packs for the application, binary repacks of the application (changing the localization of the program), and compiling the application likely won't work.</li> + <li>You are now in the Mozilla development environment which emulates a Linux environment. Now go to the directory where you want to put the source code. It's highly recommended to put it onto the fastest hard drive in the device. File paths here work starting with a slash (/) followed by the drive letter, and then the directory structure like on Windows, but using slashes (/) instead of backslashes (\). So let's go to C:\Mozilla by typing<br> + <code>cd /c/Mozilla/</code></li> + <li>Create a new directory for the source code:<br> + <code>mkdir mozilla-aurora</code></li> + <li>Initialize the new directory as new repository:<br> + <code>hg init mozilla-aurora</code></li> + <li>Go into the new directory:<br> + <code>cd mozilla-aurora</code></li> + <li>Unpack the source code:<br> + <code>hg unbundle /path/to/the/downloaded/mozilla-aurora.hg</code><br> + This can take some time, mostly depending on the performance of the hard drive.</li> + <li>Extract the files:<br> + <code>hg update</code></li> +</ol> + +<h4 id="Obter_os_textos_para_a_sua_localização">Obter os textos para a sua localização</h4> + +<ol> + <li>Go back to the parent folder of <code>mozilla-aurora</code>:<br> + <code>cd ..</code></li> + <li>Find the localization repository for your branch and language on <a href="http://hg.mozilla.org/">http://hg.mozilla.org/</a> E.g. for aurora and German (language code 'de'), it is <code>http://hg.mozilla.org/releases/l10n/mozilla-aurora/de/</code> Copy that url to the clipboard.</li> + <li>Copy the repository to your computer by running the following command:<br> + <code>hg clone http://hg.mozilla.org/releases/l10n/mozilla-aurora/de/ de-mozilla-aurora</code><br> + This should proceed pretty fast.<br> + On Windows, you can paste the url by calling the Paste command from the window menu in the upper left corner of the window.</li> +</ol> + +<h2 id="Configurar_as_suas_definições_de_utilizador_do_Mercurial">Configurar as suas definições de utilizador do Mercurial</h2> + +<p>Still in the command prompt, go to your home directory in the file system, e.g. for a Windows user, it looks like C:\Users\MyName , depending on your Windows version:</p> + +<p><code>cd /c/Users/MyName</code></p> + +<p>Now list all the files here:</p> + +<p><code>ls -a</code></p> + +<p>If there is no file called <code>.hgrc</code> , create it with</p> + +<p><code>> .hgrc</code></p> + +<p>This file stores your general Mercurial settings (Mercurial is the tool which manages the source code and its history of changes).</p> + +<p>Now go in the file system to the file and open it in your favorite text editor. Windows users can use e.g. <a href="http://notepad-plus-plus.org/">Notepad++</a>.</p> + +<p>Paste the following content into the file:</p> + +<pre>[ui] +username = Firstname Lastname <mynick@example.com> +merge = internal:merge + +[alias] +qexport = export -g -r qtip +qexportall = diff -r qparent + +[defaults] +commit = -v +diff = -p -U 8 +qdiff = -p -U 8 +qnew = -U + +[diff] +git = 1 +showfunc = 1 +unified = 8 + +[extensions] +hgext.mq = +progress = + +[hooks] + +</pre> + +<p>Put in your name and email address which later will be public on the internet after your translation patch got accepted and uploaded. Save the file and close it.</p> + +<h2 id="Ativar_filas_do_Mercurial_(correções_revertíveis)">Ativar filas do Mercurial (correções revertíveis)</h2> + +<p>Some time will pass between the moment in which you start the localization, finish it, test it, improve it, upload it for review and get review (maybe not approved on first try). Other localizers will likely have done changes to the translation, either adding new texts, removing obsolete ones or improving the current texts. This can cause conflicts between the changes you created and theirs. For this reason, updating patches kann be necessary so Mercurial is still able to find the lines in the files which it has to replace or where it has to add them. <a href="/en-US/docs/Mercurial_Queues">Mercurial queues</a> allow to revert changes and also pull changes and reapply your local changes.</p> + +<p>Go back to the localization directory:</p> + +<p><code>cd /c/Mozilla/de-mozilla-aurora</code></p> + +<p>Initiate Mercurial queues:</p> + +<p><code>hg qinit</code></p> + +<h2 id="Conhecer_o_estilo_de_tradução">Conhecer o estilo de tradução</h2> + +<p>For having good chances that the translation suggestions get accepted, they should match the translation style of the texts in the application already translated. In general, the labels in the applications should have the same style like the operating system, e.g. use the same order of subject, verb and objects; decline verbs or not like the operating system does.</p> + +<p>The following resources can help figuring out the translation style and translate according to them:</p> + +<ul> + <li><a href="https://l10n.mozilla.org/teams/">Check your localization team's page</a> by clicking on the team with your <a href="https://en.wikipedia.org/wiki/Language_code">language code</a> (e.g. "de" for German) for a style guide (e.g. <a href="https://wiki.mozilla.org/L10n:Teams:de/Leitfaden_%C3%9Cbersetzung">style guide</a> for German).</li> + <li><a href="http://transvision.mozfr.org/">Transvision</a> offers searching for texts and text ids ("entities" or "keys"), allowing to quickly find translations for already translated texts.</li> + <li><a href="http://www.microsoft.com/language/de-de/default.aspx">Microsoft's terminology search</a> allows fast lookups of localized technical terms.</li> +</ul> + +<h2 id="Escolher_o_que_traduzir">Escolher o que traduzir</h2> + +<p>Go to the <a href="https://l10n.mozilla.org/teams/">Localization status page</a> and click on the '<number> missing' label of the Firefox branch on which you want to translate, e.g. <strong>fx_aurora</strong>. The page which opens has a bar holding information about how many texts (strings) have already been translated, how many there are in English and your locale and have the same text, and how many are missing in your local. The interesting part follows below as list of missing texts.</p> + +<p><img alt="unchanged localization report" src="https://mdn.mozillademos.org/files/7303/mozilla%20-%20localization%20report%20-%20new.png" style="height: 396px; width: 483px;"></p> + +<p>The first line shows the locale for which the texts are being translated (in this example: de - German). With the second line start the file paths of the files which require changes. The file paths follow the directory structure of the locale repository downloaded for translation. In this example, the file aboutDialog can be found in the folder browser/chrome/browser/. The text striked through are texts which have been removed in the English version and can also be removed from the locale being worked on. In this example we will translate the one new text with the id <strong>privatebrowsingpage.howToStart4</strong> in the file <strong>aboutPrivateBrowsing.dtd</strong>.</p> + +<p>Tips for finding files with usually easily translateable texts:</p> + +<ul> + <li>Look for files in browser/chrome/browser/</li> + <li>Look for a file with only a few changes</li> + <li>Suggestions + <ul> + <li>Files starting with <strong>about</strong>...</li> + <li>Files in the <strong>preferences</strong> directory (browser/chrome/browser/preferences/)</li> + <li>The <strong>browser.dtd</strong> and <strong>browser.properties</strong> files if there aren't too many new strings.</li> + </ul> + </li> +</ul> + +<h2 id="Monotorizar_o_progresso_de_tradução">Monotorizar o progresso de tradução</h2> + +<p>If you translate more than a few strings, you usually want to keep track of what has already been translated (and later if the text has been tested in the product as fitting into the available area and suiting the functionality it describes). This guide achieves this with the Firefox extension <a href="https://addons.mozilla.org/firefox/addon/scrapbook/">Scrapbook</a>.</p> + +<ol> + <li>You installed Scrapbook earlier, now open it in Firefox either by calling it from the Firefox menu bar (press the Alt key to show it if necessary) using "View" > "Sidebar" > "Scrapbook" or by clicking its toolbar button which you likely have to add by toolbar customization if you didn't do this before.</li> + <li>Drag the tab with the localization error showing missing and obsolete strings to the sidebar.</li> + <li>After Scrapbook has saved the web page to your local disk, click with the right mouse button on the page in the sidebar and choose "Properties" from the context menu which gets opened. Rename it something meaningful, e.g. "Firefox <version number> translation".</li> + <li>After you saved the dialog, click with the left mouse button on the page in the sidebar to open the locally saved copy.</li> +</ol> + +<h2 id="Abrir_ficheiros_em_inglês_e_o_idioma_de_destino_lado-a-lado">Abrir ficheiros em inglês e o idioma de destino lado-a-lado</h2> + +<p>The localization report shows the IDs of added or removed texts, but the English text itself is still unknown. We get this by comparing the English version of the file with the one of the locale we are translating in. To do so,</p> + +<ol> + <li>Launch WinMerge.</li> + <li>From its "File" menu, choose "Save project".</li> + <li>For the file path of the left directory, go to the downloaded <code>mozilla-aurora</code> source code and then into its <strong><code>browser/locales/en-US/</code></strong> folder. In this example, the absolute file path is <code>C:\Mozilla\mozilla-aurora\browser\locales\en-US</code>.</li> + <li>Enable read-only mode for the left directory.</li> + <li>For the file path of the right directory, go to the downloaded translation directory <code>de-mozilla-aurora</code> and then into its <code>browser</code> folder. In this example, the absolute file path is <code>C:\Mozilla\de-mozilla-aurora\browser</code>.</li> + <li>Save this comparison as project so you can easily relaunch this comparision without selecting the directories again. A good name is e.g. <code>translation-mozilla-aurora-browser.winmerge</code></li> + <li>Open the comparison you just saved.</li> +</ol> + +<h2 id="A_tradução">A tradução</h2> + +<ol> + <li> + <p>Bring the console with Mercurial to the front.</p> + </li> + <li> + <p class="brush: bash">Start tracking changes you make against the localization repository by telling it that with the <strong><code>qnew</code></strong> subcommand to save these changes as patch in a mercurial queue. This patch needs a name, choose something meaning full like "<code>Firefox-<version number>-more-details</code>". In this example, <code>Firefox-29-aboutPrivateBrowsing</code> will be used.<br> + <code>hg qnew Firefox-29-aboutPrivateBrowsing</code></p> + </li> + <li>Switch back to WinMerge and navigate to <code>browser/chrome/browser/</code> and open the <code>aboutPrivateBrowsing.dtd</code> file. You will see something like this:<br> + <img alt="single file comparision in WinMerge without changes by the user" src="https://mdn.mozillademos.org/files/7305/mozilla%20-%20compare%20-%20unchanged.png"><br> + On the left, you see an overview of the comparison of the English and the non-English file. Gray parts indicate blocks of texts which can't be found in that file, dark yellow represents changed lines and light yellow the parts of text in it which is different.</li> + <li>Below the license header which should never changed, the texts are organized in the following format:<br> + <code><!ENTITY stringid "Text which will be shown in Firefox"></code></li> + <li>As you can see there is a bigger block of text not recognized. This is due to the texts which have in the English versionmoved from below the string with the id <code>privatebrowsingpage.howToStart3</code> to a position above it. Cut and paste these strings in the localized file so their position corresponds to the on in the English file.</li> + <li>Press the F5 key or click the reload button in WinMerge's toolbar to re-compare the files.</li> + <li>Now copy the empty lines below <code>privatebrowsingpage.learnMore</code> and the line <code><!-- TO BE REMOVED POST-AUSTRALIS --></code> to the localized file. This text is a comment (which in .dtd files always can be found between <code><!--</code> and <code>--></code>). There is no need to translate this text.</li> + <li>Now we copy the two missing lines from the English file and insert them in the localized file:<br> + <code><!-- LOCALIZATION NOTE (privatebrowsingpage.howToStart4): please leave &newPrivateWindow.label; intact in the translation --><br> + <!ENTITY privatebrowsingpage.howToStart4 "To start Private Browsing, you can also select &newPrivateWindow.label; from the menu."></code><br> + The first line is a comment providing information on the localization of the text in the following line. <code>&newPrivateWindow.label;</code> has to be left unchanged so it can be replaced with the text of the string id <code>&newPrivateWindow.label;</code> whis is stored elsewhere<code>.</code></li> + <li><strong>Translation time</strong>: Translate the text. Afterwars, the line should look somehow like this:<br> + <code><!ENTITY privatebrowsingpage.howToStart4 "Der private Modus kann auch über den Menü-Eintrag &newPrivateWindow.label; gestartet werden."></code></li> + <li>Save the file.</li> +</ol> + +<h2 id="Exportar_as_alterações_como_correção">Exportar as alterações como correção</h2> + +<p>A patch is a file containing recorded changes to a repository. It can be used to apply these changes to a copy of the repository yet without these changes.</p> + +<ol> + <li>Tell Mercurial to store the changes in the Mercurial queue with the <code>qref</code> command. We also create a commit message which will describe the changes in the patch and later get used when the patched gets checked in ('added') to the official repository with the localized files. For the commit message, we have to use the <code>-m</code> command line flag,<br> + <code>hg qref -m "Firefox 29: Localize missing string in aboutPrivateBrowsing.dtd"</code><br> + You can change the commit message in the Mercurial queue every time by calling <code>hg qref</code> again.</li> + <li>Now export the patch to the file system using the <code>qexport</code> command which is defined in the <code>.hgrc</code> file (see above):<br> + <code>hg qexport > ../firefox-29-aboutPrivateBrowsing-v1.patch</code><br> + This creates a patch file called <code>firefox-29-aboutPrivateBrowsing-v1.patch</code> containing the changes in the parent directory of <code>de-mozilla-aurora</code> (in this example: <code>C:\Mozilla\</code>).</li> +</ol> + +<h2 id="Correção_ortográfica_e_alterar_a_correção_(patch)">Correção ortográfica e alterar a correção (patch)</h2> + +<p>Now proof-read the patch. This detects often more than 90 percent of the possible reasons for the reviewer to not accept the patch. If you find that changes have to be done, edit the real aboutPrivateBrowsing.dtd file from the localization repository, save it and follow the steps from Exporting the changes as patch (see above).</p> + +<h2 id="Validar_a_tradução_no_produto">Validar a tradução no produto</h2> + +<p>This guide hasn't yet a section about the validation of the translation. Please follow the instructions from the <a href="https://developer.mozilla.org/en-US/docs/Mozilla/Localization/Quick_start_guide/QA_phase">QA phase section of the Localization quick start guide</a>.</p> + +<h2 id="Submeter_a_correção_(patch)_para_revisão">Submeter a correção (patch) para revisão</h2> + +<p>Now the patch has to be shared so the people currently trusted to change the official translation can review the suggested changes.</p> + +<ol> + <li>File a <a href="https://bugzilla.mozilla.org/enter_bug.cgi?product=Mozilla%20Localizations">bug ("ticket") in the Mozilla Localization product</a> and choose as component the localization for which you have translated.</li> + <li>Choose a meaningful bug summary which will be shown for searches etc. like in this example "Firefox 29: aboutPrivateBrowsing.dtd"</li> + <li>Fill any important and additional information into the description field.</li> + <li>Click the 'Add attachment' button.</li> + <li>Select the exported patch file with the file picker. The checkbox for 'patch' should get automatically checked.</li> + <li>Add a meaningful name for the attachment, e.g. aboutPrivateBrowsing.dtd, patch, v1</li> + <li>Go to the review 'Flags' category and set the one for <strong>review</strong> to <strong>?</strong>, meaning that you request review for the patch.</li> + <li>In the text field next to it, add the mail address of the person leading the translation of the locale. This information can be found on the <a href="https://l10n.mozilla.org/teams/">page of the localization team</a>.</li> + <li>Submit the bug report.</li> + <li>Now you have to wait for the review of that person. This can happen on the same day, on the next weekend or later, but should happen in the timeframe given for the localization of aurora. If the person requests changes, follow the instructions under <strong>Proof-reading and altering the patch</strong>. If the reviewer accepts the changes, the patch will get uploaded and your translation will officially be added to Firefox.</li> +</ol> diff --git a/files/pt-pt/mozilla/localization/guia_iniciação_rápida/configuracao_inicial/index.html b/files/pt-pt/mozilla/localization/guia_iniciação_rápida/configuracao_inicial/index.html new file mode 100644 index 0000000000..abde7e440f --- /dev/null +++ b/files/pt-pt/mozilla/localization/guia_iniciação_rápida/configuracao_inicial/index.html @@ -0,0 +1,81 @@ +--- +title: Configuração Inciail +slug: Mozilla/Localization/Guia_iniciação_rápida/Configuracao_inicial +translation_of: Mozilla/Localization/Quick_start_guide/Initial_setup +--- +<p>Como um pré-requisito para contribuir com o programa de L10n, precisa de ter acesso aos códigos, ferramentas e um ambiente local adequadamente configurado (ou seja, o seu computador pessoal). Também precisa de determinar se já existe um esforço de localização para o seu idioma. Aqui, nós irmos ver as contas de que precisa, bem como as ferramentas e as suas configurações que precisa de configurar antes de contribuir.</p> + +<h3 id="Nova_ou_existente">Nova ou existente</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>Veja o que faz:</p> + +<p>Look through the existing <a class="link-https" 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: #0000cd;">If a community already exists, reach out to them and ask how you can help.</span></li> + <li><span style="color: #ff8c00;">If a community doesn't exist, send an <a class="link-https" 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: #ff8c00;">.</span></li> +</ol> + +<h3 id="Contas">Contas</h3> + +<p>There are a handful of accounts that you need to be aware of 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 style="">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. Hg commit access is <u>not</u> necessary to begin localizing. After you have some experience with hg, you may want to get commit access. At that point, you must visit the <a class="external" href="http://www.mozilla.org/hacking/committer/" title="http://www.mozilla.org/hacking/committer/">Mozilla Committer page</a> and follow the process outlined there. <a 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="link-https" 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. <span>Add a request about creating your locale's repository to the <a class="external" 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>.</span></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="link-https" 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. The <a href="https://developer.mozilla.org/en-US/docs/SVN_guide_for_localizers" title="https://developer.mozilla.org/en-US/docs/SVN_guide_for_localizers">SVN for Localizers guide</a> will help you learn the most important SVN commands for l10n. <span>Add a request about creating your locale's repository to the <a class="external" 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>.</span></dd> +</dl> + +<dl> + <dt style="margin-left: 40px;">Ferramentas de L10n baseadas na Web</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" 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;">Componente de Bugzilla específico do local</dt> + <dd style="margin-left: 40px;"><span>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 </span><a class="external" href="http://groups.google.com/group/mozilla.dev.l10n.new-locales/topics" title="http://groups.google.com/group/mozilla.dev.l10n.new-locales/topics"><span>new locales newsgroup</span></a><span>.</span></dd> +</dl> + +<h3 id="Ferramentas_de_ambiente_locais">Ferramentas de ambiente locais</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.</p> + +<dl> + <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="/en/Localizing_with_Mercurial#Install_Mercurial" title="https://developer.mozilla.org/en/L10n_on_Mercurial#Install_Mercurial">here</a>.</dd> +</dl> + +<dl> + <dt style="margin-left: 40px;">comparar-idiomas</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="/en/Compare-locales" title="https://developer.mozilla.org/en/Compare-locales">here</a>.</dd> + <dt style="margin-left: 40px;">Verificações de L10n</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="/en/L10n_Checks" title="https://developer.mozilla.org/en/L10n_Checks">here</a>.</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" 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" href="http://www.gnu.org/s/wget/" title="http://www.gnu.org/s/wget/">here</a>.</dd> + <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" 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" href="http://python.org/" title="http://python.org/">here</a>.</dd> + <dt style="margin-left: 40px;">Locale Switcher ou Quick Locale Switcher</dt> + <dd style="margin-left: 40px;">Ambos o Locale Switcher e o Quick Locale Switcher são extras para as aplicações da Mozilla. 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="link-https" 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="link-https" 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> + <dt style="margin-left: 40px;">Um editor de texto sólido, baseado em Unicode</dt> + <dd style="margin-left: 40px;">Here are some suggestions: + <ul> + <li style="margin-left: 40px;">Windows: <a class="external" href="http://notepad-plus.sourceforge.net/uk/site.htm" rel="external nofollow" title="http://notepad-plus.sourceforge.net/uk/site.htm">Notepad++</a> or <a class="external" href="http://www.flos-freeware.ch/notepad2.html" rel="external nofollow" title="http://www.flos-freeware.ch/notepad2.html">Notepad2</a></li> + <li style="margin-left: 40px;">GNU/Linux: <a class="external" href="http://en.wikipedia.org/wiki/Vim_%28text_editor%29" rel="external nofollow" title="http://en.wikipedia.org/wiki/Vim_(text_editor)">vim</a>, <a class="external" href="http://projects.gnome.org/gedit/" rel="external nofollow" title="http://projects.gnome.org/gedit/">gedit</a> or <a class="external" href="http://www.kate-editor.org/kate" rel="external nofollow" title="http://www.kate-editor.org/kate">Kate</a></li> + <li style="margin-left: 40px;">Mac OS X: <a class="external" href="http://www.barebones.com/products/TextWrangler/" rel="external nofollow" 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">Make is a tool which controls the generation of executables. You can find version</span> 3.79.1 or higher <a class="external" 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> +</dl> + +<h2 id="Fim_da_configuração_inicial">Fim da configuração inicial</h2> + +<p>Agora que concluiu a configuração inicial, é hora da melhor parte: traduzir!</p> + +<p>{{ PreviousNext("Localization_Quick_Start_Guide", "Localization_Quick_Start_Guide/Translation_phase") }}</p> diff --git a/files/pt-pt/mozilla/localization/guia_iniciação_rápida/fase_da_traducao/index.html b/files/pt-pt/mozilla/localization/guia_iniciação_rápida/fase_da_traducao/index.html new file mode 100644 index 0000000000..cdb31df82a --- /dev/null +++ b/files/pt-pt/mozilla/localization/guia_iniciação_rápida/fase_da_traducao/index.html @@ -0,0 +1,120 @@ +--- +title: Fase da Tradução +slug: Mozilla/Localization/Guia_iniciação_rápida/Fase_da_Traducao +tags: + - Localização + - 'Localização: Ferramentas' + - Tradução +translation_of: Mozilla/Localization/Quick_start_guide/Translation_phase +--- +<p>Parabéns por completar a configuração inicial! Como recompensa pelos seus esforços, você começa a pensar no motivo pelo qual veio até aqui: localizar projetos da Mozilla.</p> + +<p>É onde o aspeto técnico do processo começa a dividir-se. Na Mozilla, nós localizamos muitos projetos diferentes que podem ser categorizados em três grupos diferentes. Cada grupo de projetos emprega um tipo diferente de ferramenta l10n para, você adivinhou, localizar os projetos. As ferramentas do l10n destinam-se a ajudá-lo a manter o seu conteúdo localizado de lançamento a lançamento e aproveitar os materiais já localizados quando localiza novo conteúdo.</p> + +<p>Aqui, nos iremo identificar esses grupos de projetos e as ferramentas de l10n associadas com os mesmo. Ao longo do caminho, nós iremos direcioná-lo para os tutoriais técnicos básicos sobre a localização desse grupo específico de projetos. Cabe a si, e à sua comunidade determinar qual a ferramenta de l10n corresponderá melhor às suas necessidades. À medida que ganha mais experiência, talvez queira localizar independentemente das ferramentas de l10n desenvolvidas pela Mozilla, que nós também discutiremos aqui.</p> + +<h2 id="Projetos">Projetos</h2> + +<p>Os projetos da Mozilla e os ritmos de trabalho de l10n são divididos nestes grupos: aplicações da Mozilla, sites da Web da Mozilla, e Extras. Em baixo, irá encontrar a lista de todos os projetos da Mozilla, as suas ferramentas de l10n associadas, e hiperligações para tutoriais descrevendo os seus ritmos de trabalho.</p> + +<h3 id="Aplicações_da_Mozilla">Aplicações da Mozilla</h3> + +<p>So you're interested in localizing Mozilla applications. Each l10n tool follows a different workflow for localizing Mozilla application projects. We've linked a brief tutorial to each l10n tool name below. Follow the tutorials to help you decide which l10n tool fits your specific needs.</p> + +<p>These are the l10n tools we use to localize Mozilla applications:</p> + +<dl> + <dt style="margin-left: 40px;"><a class="external" href="http://translate.sourceforge.net/wiki/guide/mozilla" title="http://translate.sourceforge.net/wiki/guide/mozilla">Pootle</a></dt> + <dd style="margin-left: 40px;">A user-friendly web portal built on the Translate Toolkit API. This tool includes workspaces for translating strings, reviewing string submissions, and project dashboards. See the <a class="external" href="http://pootle.locamotion.org/" title="http://pootle.locamotion.org/">instance of Pootle used to localize Mozilla applications</a>.</dd> +</dl> + +<dl> + <dt style="margin-left: 40px;"><a href="/en/Localizing_with_Koala" title="https://developer.mozilla.org/en/Localizing_with_Koala">Koala</a></dt> + <dd style="margin-left: 40px;">A l10n add-on for the offline, stand-alone Komodo Edit text editor.</dd> + <dt style="margin-left: 40px;"><a class="external" href="/en/Localizing_with_Mozilla_Translator" title="https://developer.mozilla.org/en/Localizing_with_Mozilla_Translator">Mozilla Translator</a></dt> + <dd style="margin-left: 40px;">Am offline, stand-alone, Java-based l10n tool that helps you translate and integrates with your repositories. Visit the <a class="external" href="http://kenai.com/projects/moztrans/downloads" title="http://kenai.com/projects/moztrans/downloads">Mozilla Translator (MT) download page</a> to get your own MT client. Version 5.26 is the latest version.</dd> + <dt style="margin-left: 40px;">Virtaal</dt> + <dd style="margin-left: 40px;">An offline, stand-alone version of Pootle that is also built on the Translate Toolkit API.</dd> +</dl> + +<p>These are the Mozilla application projects that are localized using the l10n tools above:</p> + +<dl> + <dt style="margin-left: 40px;">Firefox</dt> + <dd style="margin-left: 40px;">The award-winning Firefox® Web browser has security, speed and new features that will change the way you use the Web. <span style="color: #daa520;">See the <a class="external" href="http://zaf.svn.sourceforge.net/viewvc/zaf/trunk/po/fftb/firefox.phaselist" title="http://zaf.svn.sourceforge.net/viewvc/zaf/trunk/po/fftb/firefox.phaselist">list of the most critical strings for localizing in Firefox</a></span><span style="color: #daa520;">, as well as <a class="external" href="http://zaf.svn.sourceforge.net/viewvc/zaf/trunk/po/fftb/phases" title="http://zaf.svn.sourceforge.net/viewvc/zaf/trunk/po/fftb/phases">a guide to understanding how they're organized</a></span><span style="color: #daa520;">.</span></dd> + <dt style="margin-left: 40px;">Thunderbird</dt> + <dd style="margin-left: 40px;">Enjoy safe, fast and easy email, Mozilla-style. The Thunderbird® email client includes intelligent spam filters, powerful search and customizable views.</dd> + <dt style="margin-left: 40px;">Seamonkey</dt> + <dd style="margin-left: 40px;">SeaMonkey® is the all-in-one application formerly known as the "Mozilla Application Suite", containing a web browser, a mail and newsgroups client, an HTML editor, web development tools, and an IRC chat client.</dd> + <dt style="margin-left: 40px;">Firefox Mobile</dt> + <dd style="margin-left: 40px;">By adding Firefox® to your mobile phone, you can access rich Web content and enjoy your favorite Firefox features wherever you go.</dd> + <dt style="margin-left: 40px;">Lightning</dt> + <dd style="margin-left: 40px;">Lightning is a popular calendaring, scheduling and task management extension.</dd> +</dl> + +<p><span style="color: #0000ff;">If your locale has an hg repository hosted on the Mozilla servers, you can track your localization's current progress by visiting the </span><a class="link-https" href="https://l10n.mozilla.org/teams/" title="https://l10n.mozilla.org/teams/"><span style="color: #0000ff;">l10n dashboards</span></a><span style="color: #0000ff;">.</span></p> + +<div class="note"> +<p><strong>Nota:</strong> <span style="color: #ff8c00;">se estiver a iniciar uma nova localização e decidir utilizar uma ferramenta off-line para localizar aplicações da Mozilla, terá que familiarizar-se com a utilização de Mercurial (hg). Visite o tutorial <a href="https://developer.mozilla.org/pt-PT/docs/Mozilla/Localization/Localizar_com_Mercurial" title="https://developer.mozilla.org/en-US/docs/Localizing_with_Mercurial"><span style="color: #ff8c00;">sobre como utilizar "hg" nos seus esforços de localização aqui</span></a><span style="color: #ff8c00;">. </span></span></p> +</div> + +<h3 id="Sites_da_Web_da_Mozilla">Sites da Web da Mozilla</h3> + +<p>So you're interested in localizing Mozilla websites. Each l10n tool follows a different workflow for localizing Mozilla web projects. We've linked a brief tutorial to each l10n tool name below. Follow the tutorials to help you decide which l10n tool fits your specific needs.</p> + +<p>These are the l10n tools we use to localize Mozilla web projects:</p> + +<dl> + <dt style="margin-left: 40px;"><a href="/en-US/docs/Localizing_with_Pontoon" title="/en-US/docs/Localizing_with_Pontoon">Pontoon</a></dt> + <dd style="margin-left: 40px;">A web-based, What-You-See-Is-What-You-Get (WYSIWYG) l10n tool that allows you to localize Mozilla websites within the site itself. Visit <a class="external" href="https://pontoon.mozilla.org" title="http://horv.at/pontoon/">Pontoon</a> here. Please note the Pontoon is not available for all web projects yet.</dd> +</dl> + +<p>These are the Mozilla web projects that are localized using the l10n tools above:</p> + +<dl> + <dt style="margin-left: 40px;">mozilla.org</dt> + <dd style="margin-left: 40px;">Every user's first Mozilla experience.</dd> + <dt style="margin-left: 40px;">addons.mozilla.org (AMO)</dt> + <dd style="margin-left: 40px;">A portal for all users interested in finding add-ons for their local Mozilla applications. Read the <a class="link-https" href="https://addons.mozilla.org/en-US/localizers/" title="https://addons.mozilla.org/en-US/localizers/">guidelines on localizing AMO</a>, straight from the AMO team.</dd> + <dt style="margin-left: 40px;">developer.mozilla.org (MDN)</dt> + <dd style="margin-left: 40px;">Where you are now! Help localize the MDN user interface for everyone in your region.</dd> + <dt style="margin-left: 40px;">support.mozilla.com (SUMO)</dt> + <dd style="margin-left: 40px;">A portal for anyone who needs technical support for their Mozilla applications. Help localize the SUMO user interface for everyone in your region.</dd> + <dt style="margin-left: 40px;">Mozilla Engagement Campaigns</dt> + <dd style="margin-left: 40px;">Individual campaigns created by Mozilla to attract new contributors.</dd> + <dt style="margin-left: 40px;">hacks.mozilla.org</dt> + <dd style="margin-left: 40px;">For everyone interested in the leading-edge stuff that people are doing with Mozilla Firefox and the open web.</dd> + <dt style="margin-left: 40px;">In-product pages</dt> + <dd style="margin-left: 40px;">A set of pages used to interact with and give information to the end-user as part of their first experience with their Mozilla applications.</dd> +</dl> + +<p><span style="color: #ff8c00;">Se está a criar a sua própria localização, existem vários sites da Web da Mozilla que precisam de ser localizados antes que os seus esforços se tornem numa localização lançada oficialmente. Consulte a</span><span style="color: #ff8c00;"> <a class="link-https" href="https://wiki.mozilla.org/L10n:Web_parts#Firefox_in-product_pages" title="https://wiki.mozilla.org/L10n:Web_parts#Firefox_in-product_pages">lista de sites da Web localizados da Mozilla</a>. </span></p> + +<p>Também deveria ler <a class="link-https" href="https://wiki.mozilla.org/L10n:Web_parts" title="https://wiki.mozilla.org/L10n:Web_parts">mais informação sobre a localização de projetos da web da Mozilla</a>.</p> + +<dl> + <dt> </dt> +</dl> + +<h3 id="Extras_(Add-ons)">Extras (Add-ons)</h3> + +<p>l10n for add-ons is handled by at least two other organizations/services called Babelzilla and Adofex. They both have created comprehensive programs and l10n tools for localizing any and all third-party add-ons for Mozilla applications. Visit their websites to learn how to get involved.</p> + +<ul> + <li><a class="external" href="http://babelzilla.org" title="http://babelzilla.org">Babelzilla</a></li> + <li><a class="external" href="http://adofex.clear.com.ua/" title="http://adofex.clear.com.ua/">Adofex</a></li> +</ul> + +<h2 id="Ferramenta_de_localização_independente">Ferramenta de localização independente</h2> + +<p>Are you a command-line master? Do you prefer Unicode text editors to any other applications on Earth? Do you have a pet CAT (computer-assisted translation) tool, like OmegaT? Then you may not be interested in using any of the tools listed above for your localizations. If that is the case, then this section is for you!</p> + +<p>For localizers who prefer localizing without a specialized tool the workflows for localizing Mozilla applications and Mozilla websites are essentially the same.<a href="/en/Localizing_without_a_specialized_tool" title="https://developer.mozilla.org/en/Localizing_without_a_specialized_tool"> This tutorial</a> should provide you with all of the technical information you need to secure and maintain your tool independence.</p> + +<h2 id="Produtibilidade">Produtibilidade</h2> + +<p>Productization is an essential part of localizing Mozilla products. This is where you research and select the search plugins, content and protocol handlers, bookmarks, and links to recommended sites on the in-product pages that your locale's users will find in their Mozilla products.</p> + +<p><a href="https://developer.mozilla.org/en-US/docs/Productization_guide" title="https://developer.mozilla.org/en/Productization_patches">This tutorial will walk you through performing these productization tasks</a>, creating productization patches, and submitting them for review.</p> + +<p>{{ PreviousNext("Localization_Quick_Start_Guide/Initial_setup", "Localization_Quick_Start_Guide/QA_phase") }}</p> diff --git a/files/pt-pt/mozilla/localization/guia_iniciação_rápida/fase_de_lancamento/index.html b/files/pt-pt/mozilla/localization/guia_iniciação_rápida/fase_de_lancamento/index.html new file mode 100644 index 0000000000..310ec4344e --- /dev/null +++ b/files/pt-pt/mozilla/localization/guia_iniciação_rápida/fase_de_lancamento/index.html @@ -0,0 +1,177 @@ +--- +title: Fase de Lançamento +slug: Mozilla/Localization/Guia_iniciação_rápida/Fase_de_lancamento +translation_of: Mozilla/Localization/Quick_start_guide/Release_phase +--- +<p>Você conseguiu! Configurou os seus ambientes locais e remotos, selecionou as suas ferramentas e projetos de L10n, efetuou algumas traduções e até mesmo alguns testes! Agora está pronto para a fase final: ser parte de um lançamento oficial da L10n. Aqui, nós continuaremos a ser fiéis à intenção original deste guia e apresentaremos apenas a informação técnica necessária para se tornar num lançamento oficial. Nós vamos concentrar-nos principalmente em obter a configuração do seu repositório de lançamento e comandos do Mercurial que precisa de saber para utilizar este repositório.</p> + +<p>Para obter mais informação sobre a parte de lançamento do processo L10n, visite o site da <a class="link-https" href="https://wiki.mozilla.org/L10n:Becoming_an_Official_Localization" title="https://wiki.mozilla.org/L10n:Becoming_an_Official_Localization">wiki da Mozilla a</a>qui.</p> + +<h2 id="O_seu_repositório_oficial_de_lançamentos">O seu repositório oficial de lançamentos</h2> + +<p>Now that your locale has been registered, the localization files will live on Mozilla Mercurial server at <code>hg.mozilla.org</code>. Depending on which branch you work on, the URL of your repository might look like this:</p> + +<pre>http://hg.mozilla.org/releases/l10n-central/x-testing +</pre> + +<p>If you followed the <a href="Localizing_with_Koala" rel="internal" title="en/Localizing with Koala">Koala</a> or <a href="Localizing_without_a_specialized_tool" rel="internal" title="en/Localizing without a specialized tool">plain text</a> approach, you probably already have a local clone of the repository. Otherwise, in order to be able to make any changes to the localization files, you will need to clone the repository on your local machine and work in the <em>local clone</em>.</p> + +<p>There are two different protocols you can use to connet with your Mercurial repository: HTTP and SSH. Be advised that there's an important distinction between them. You can <code>pull</code> using both, but you can only <code>push</code> through SSH. Consequently, if you already have a local clone that you pulled using HTTP, you'll need to modify a config file to tell Mercurial to push through SSH. Let's go over configuring your connection protocols.</p> + +<h3 class="editable" id="Configuração">Configuração</h3> + +<p>Before you try pushing, you need to tell SSH which username you wish to use for connecting with hg.mozilla.org. This should be your Mozilla LDAP account name.</p> + +<ol> + <li>Add the following lines to your <code>~/.ssh/config</code> file, replacing <a class="link-mailto" href="mailto:user@host.domain" rel="external" title="mailto:user@host.domain">user@host.domain</a> with your Mozilla LDAP account name:</li> +</ol> + +<pre class="eval">Host hg.mozilla.org +User <a class="link-mailto" href="mailto:user@host.domain" rel="external" title="mailto:user@host.domain">user@host.domain</a></pre> + +<ol start="2" style="list-style-type: decimal;"> + <li>If you have already cloned the remote repository using the HTTP protocol using this command:<code> $ hg clone <strong>http</strong>://hg.mozilla.org/releases/l10n-central/x-testing</code> then you will need to edit the <code>.hg/hgrc</code> file (inside the <code>x-testing</code> local clone) to tell Mercurial to push using SSH. Your <code>.hg/hgrc</code> file shoud look like this (add the emphasized line):</li> +</ol> + +<pre class="eval">[paths] +default = hg.mozilla.org/releases/l10n-central/x-testing +<strong>default-push = <a class="external" href="ssh://hg.mozilla.org/releases/l10n-central/x-testing" rel="external" title="ssh://hg.mozilla.org/releases/l10n-central/x-testing">ssh://hg.mozilla.org/releases/l10n-central/x-testing</a></strong> +</pre> + +<ol start="3" style="list-style-type: decimal;"> + <li>If you haven't already cloned the remote repository, enter this command: <code>hg clone <strong>ssh</strong>://hg.mozilla.org/releases/l10n-central/x-testing</code></li> +</ol> + +<p style="margin-left: 40px;">Mercurial will let you know that it's cloning the repository:</p> + +<pre style="margin-left: 40px;">destination directory: x-testing +requesting all changes +adding changesets +adding manifests +adding file changes +added 4 changesets with 242 changes to 239 files +updating to branch default +239 files updated, 0 files merged, 0 files removed, 0 files unresolved +</pre> + +<p>The default <code>push</code> URL is the same as the default <code>pull</code> URL (i.e., <code><a class="external" href="ssh://hg.mozilla.org/releases/l10n-central/x-testing" rel="external" title="ssh://hg.mozilla.org/releases/l10n-central/x-testing">ssh://hg.mozilla.org/releases/l10n-central/x-testing</a></code>).</p> + +<p>You should now be able to <code>push</code> to the remote repository!</p> + +<h3 class="editable" id="Commit_outgoing_and_push">Commit, outgoing, and push</h3> + +<p>You should try to <code>commit</code> your work regularly as you progress through the localization files. Keep in mind that the <code>hg commit</code> command will save your changes locally (in the local clone). With the <code>hg push</code> command you can send the changesets to the remote server. Here's how that's done:</p> + +<ol> + <li>Run this command to see recent commits in your local clone: <code>$ hg log -l 3</code></li> +</ol> + +<p style="margin-left: 40px;">You should a list of the most recent commits, similar to this one:</p> + +<pre style="margin-left: 40px;">changeset: 0:7c543e8f3a6a +tag: tip +user: Your Name <email@example.com> +date: Mon Nov 23 18:08:25 2009 +0100 +summary: Added search bar strings +</pre> + +<ol start="2" style="list-style-type: decimal;"> + <li>Now run the <code>hg outgoing</code> command to compare the local repository on your machine with the remote repository on hg.mozilla.org.</li> +</ol> + +<p style="margin-left: 40px;">The <code>hg outgoing</code> command compares the two repositories and lists all changesets that are present locally, but not in the remote repository. These changesets will need to be pushed to the remote repository. The output will look something like this:</p> + +<pre style="margin-left: 40px;">comparing with ssh://hg.mozilla.org/releases/l10n-central/x-testing +searching for changes + +changeset: 0:7c543e8f3a6a +tag: tip +user: Your Name <email@example.com> +date: Mon Nov 23 18:08:25 2009 +0100 +summary: Added search bar strings +</pre> + +<ol start="3" style="list-style-type: decimal;"> + <li>Make sure this output is accurate before continuing.</li> + <li>Once you've made sure the outgoing output is accurate, push this changeset to hg.mozilla.org by running the <code>hg push</code> command.</li> +</ol> + +<p style="margin-left: 40px;">Mercurial will connect to the remote repository, authenticate through SSH and send the changesets. The output should look something like this:</p> + +<pre style="margin-left: 40px;">pushing to ssh://hg.mozilla.org/releases/l10n-central/x-testing +searching for changes +adding changesets +adding manifests +adding file changes +added 1 changesets with 2 changes to 2 files +</pre> + +<p>Congratulations! Your changeset has been successfully pushed to hg.mozilla.org! You can now visit <span style="font-family: monospace;">http</span><code>://hg.mozilla.org/releases/l10n-central/x-testing</code> in your browser to see the new changeset in the remote repository.</p> + +<h3 class="editable" id="Resolução_de_problemas_de_SSH">Resolução de problemas de SSH</h3> + +<p>If pushing fails, make sure your <code>~/.ssh/config </code>has the correct <code>User</code> set under the <code>hg.mozilla.org</code> host. This should be your Mozilla LDAP account name. Next, try issuing the following command: <code>$ ssh hg.mozilla.org</code></p> + +<p>If SSH is working fine, you should see the following message:</p> + +<pre>No interactive shells allowed here! +Connection to hg.mozilla.org closed. +</pre> + +<p>If you don't see this message, try running the same command in a more verbose mode (with the debugging information): <code>$ ssh -vvv hg.mozilla.org</code></p> + +<p>This should tell you why your connection is not succeeding. If you can't figure it out on your own, copy the output of the above command, paste it on <a class="external" href="http://pastebin.mozilla.org/" rel="external" title="http://pastebin.mozilla.org/">http://pastebin.mozilla.org</a> and ask in #l10n on the irc.mozilla.org server.</p> + +<h2 id="Revisões_técnicas_e_assinadas">Revisões técnicas e assinadas</h2> + +<p>You've done some localization work and your ready for it to be released. The merge date for migrating from one product release channel to the next is rapidly approaching. You need to make sure that your work can effectively be compiled into a build for the next release channel. Do you know whether to ask for technical review of your work or a sign-off review? Do you know what what exactly is reviewed in each process? Technical and sign-off reviews apply to different localizations in different ways. Here's the basic difference between the two.</p> + +<table style="width: 100%;"> + <thead> + <tr> + <th scope="col" style="text-align: center;"><strong>Revisão Técnica</strong></th> + <th scope="col" style="text-align: center;"><strong>Revisão Assinada</strong></th> + </tr> + </thead> + <tbody> + <tr> + <td> + <ul> + <li>Performed as a QA measure on a revision pushed to a new locale's L10n aurora repo in Mercurial.</li> + <li>Very comprehensive. Covers the entire product.</li> + <li>Focus is on technical accuracy and completion of L10n work; not translation quality.</li> + <li>Only performed on the first revision a new locale wants to have released to the public.</li> + <li>Must be approved prior to migrating your revision from one release channel to the next (e.g., Aurora to Beta).</li> + </ul> + </td> + <td> + <ul> + <li>Performed as a QA measure for maintaining a localization from release-to-release.</li> + <li>Only new L10n work is evaluated. This is done by generating a diff between the new release revision being considered and the previously approved release revision.</li> + <li>Focus is still on technical accuracy and completion of L10n work; not translation quality.</li> + <li>Release revisions are evaluated, not entire L10n repos.</li> + <li>Sign-offs do not need to be approved before revision merge between release channels, although it is recommended.</li> + </ul> + </td> + </tr> + </tbody> +</table> + +<p>There is a specific process to follow in Bugzilla for requesting these reviews:<a href="/@api/deki/files/6034/=technical_review.png" title="technical review.png"><img alt="technical review.png" class="internal rwrap" src="/@api/deki/files/6034/=technical_review.png?size=webview" style="float: right; height: 189px; width: 350px;"></a></p> + +<ol> + <li>File a bug requesting the review.</li> + <li>Attach your files to the bug. Once attached, open the attachment details.</li> + <li>In the attachment details, select the <strong>?</strong> from the dropdown menu next to the <span style="color: #daa520;">review flag</span> or the <span style="color: #0000ff;">appropriate approval flags</span> (see image). This will display a text box to assign the review to someone.</li> + <li>Enter <strong>:Pike</strong> as the <strong>Requestee</strong>.</li> +</ol> + +<p>We will perform a technical review of your work and provide you with feedback. We're happy to work with you to make sure that your work is fully functional.</p> + +<p>For more detailed information about reviews for new localizations and sign-offs for maintenance releases, visit the <a href="/en/Localization_technical_reviews" title="https://developer.mozilla.org/en/Localization_technical_reviews">technical review</a> and <a href="/en/Localization_sign-off_reviews" title="https://developer.mozilla.org/en/Localization_sign-off_reviews">sign-off review</a> pages.</p> + +<h2 id="Tah_dah!">Tah dah!</h2> + +<p>Mais uma vez, parabéns! Chegou ao final! Sinta-se à vontade para voltar a este tutorial sempre que necessário. Nós estamos felizes em o ter como um novo colaborador da Mozilla L10n e nós esperamos trabalhar de perto consigo.</p> + +<p>{{ Previous("Localization_Quick_Start_Guide/QA_phase") }}</p> diff --git a/files/pt-pt/mozilla/localization/guia_iniciação_rápida/fase_pr/index.html b/files/pt-pt/mozilla/localization/guia_iniciação_rápida/fase_pr/index.html new file mode 100644 index 0000000000..48e5d343d5 --- /dev/null +++ b/files/pt-pt/mozilla/localization/guia_iniciação_rápida/fase_pr/index.html @@ -0,0 +1,212 @@ +--- +title: Fase de PR +slug: Mozilla/Localization/Guia_iniciação_rápida/Fase_PR +tags: + - Localização +translation_of: Mozilla/Localization/Quick_start_guide/QA_phase +--- +<p>Depois de todo o trabalho duro de localização, nós temos a certeza de que não quer ver apenas o seu trabalho, mas quer ter a certeza de que está preciso! Se não tem muita experiência com código, pode até preocupar-se que tenha efetuado algo de errado (Ups!). Nós agora vamos orientá-lo na realização de alguns testes de garantia de qualidade no seu trabalho para garantir que esteja no caminho certo.</p> + +<p>If you're localizing Mozilla websites, your work will display soon after you've committed it without needing a language pack. Since such is the case, this part of the guide may not be entirely applicable to you. Feel free to skip ahead to the next section by clicking on the <strong>Next</strong> link at the bottom of the page.</p> + +<p>In order to see your work on Firefox (or another Mozilla application), you'll need to have a built language pack to install on your local instance.</p> + +<h2 id="Criações_automatizadas_e_manual">Criações automatizadas e manual</h2> + +<p>With the click of a button, some L10n tools (like Narro and Koala) automatically create language pack builds for you. If you're using one of these tools, feel free to skip ahead to the <a href="/en/Localization_Quick_Start_Guide:_QA#Seeing_your_work" title="https://developer.mozilla.org/en/Localization_Quick_Start_Guide:_Part_3#Seeing_your_work">Seeing your work</a> section. If you're not using one of these tools, let's walk you through building your own language pack manually.</p> + +<div class="note"><strong>Nota</strong>: Remember all of those pre-requisite tools we asked you to install in the <a href="/en/Localization_Quick_Start_Guide#Local_environment_tools" title="https://developer.mozilla.org/en/Localization_Quick_Start_Guide#Local_environment_tools">initial setup</a>? Here's where you'll need almost all of them. If you haven't installed them yet, <em>now</em> is the time to do it.</div> + +<h3 id="Instruções_preliminares">Instruções preliminares</h3> + +<p>We will be using the following file directories for this example:</p> + +<pre style="margin-left: 40px;">your working directory <em>(root)/</em> + mozilla-aurora <em>(en-US source, pulled from <a class="external" href="http://hg.mozilla.org/releases/mozilla-aurora" rel="external" title="http://hg.mozilla.org/releases/mozilla-aurora">http://hg.mozilla.org/releases/mozilla-aurora</a></em> <em>)</em>/ + l10n-central <em>(directory for L10n directories, one per L10n; often referred to as "l10n base")/</em> + your-locale-code <em>(a directory with your L10n files, in this example we'll use x-testing)</em> + +<strong>Example</strong>: <code>root/mozilla-aurora</code> & <code>root/l10n-central/x-testing</code> +</pre> + +<p>Additionally, you will need to copy and translate the <code>toolkit/defines.inc</code> file directly from en-US before you can build. This is due to a bug in the build logic.</p> + +<p>Please either follow the above structure closely or adjust the commands below according to your custom setup.</p> + +<p>To copy this file to the appropriate directory, do the following:</p> + +<ol> + <li>Navigate to your working directory from your command-line terminal (i.e., where you created the folder structure described above).</li> + <li>Enter the following commands:</li> +</ol> + +<pre style="margin-left: 40px;">mkdir -p l10n-central/x-testing/toolkit/ + +cp mozilla-aurora/toolkit/locales/en-US/defines.inc l10n-central/x-testing/toolkit/defines.inc +</pre> + +<p>Tah-dah! Copied!</p> + +<p>Finally, you will need a file called <code>.mozconfig</code> to proceed with manual builds. This file contains the necessary build instructions.</p> + +<p>To create and configure this file, follow these instructions:</p> + +<div class="warning"> +<p>Until the fix for <a href="https://bugzil.la/1063880">bug 1063880</a> lands on mozilla-aurora and mozilla-beta when building language packs against those two trees you should:</p> + +<ol> + <li> + <p>remove <code>ac_add_options --disable-compile-environment</code> from <code>.mozconfig</code> in step 3</p> + </li> + <li> + <p>use <code>./mach build config</code> after step 4</p> + </li> +</ol> +</div> + +<ol> + <li>Update the Mozilla source code:</li> +</ol> + +<p style="margin-left: 40px;"><code>$ cd mozilla-aurora<br> + $ hg pull -u</code></p> + +<ol start="2" style="list-style-type: decimal;"> + <li>Enter the following command to create the <code>.mozconfig</code> file: <code>$ nano -w .mozconfig</code></li> + <li>Enter the following lines in your <code>.mozconfig</code> file:</li> +</ol> + +<pre style="margin-left: 40px;">mk_add_options MOZ_OBJDIR=@TOPSRCDIR@/../firefox-build +ac_add_options --disable-compile-environment +ac_add_options --with-l10n-base=../l10n-central # path relative to MOZ_OBJDIR +ac_add_options --enable-application=[<em>browser or mail</em>] +</pre> + +<p style="margin-left: 40px;">You will need to specify which application you're localizing in the fourth line (e.g., for Firefox, that's <code>browser</code>, Thunderbird would be <code>mail</code>).</p> + +<ol start="4" style="list-style-type: decimal;"> + <li>Enter the following command to perform the configuration: <code>$ ./mach configure</code></li> + <li>Once your command-line finishes spitting out the config command's output, navigate to the newly created directory:<code> $ cd ../firefox-build/browser/locales</code></li> +</ol> + +<p>Now you're ready to build! At this point you can choose between two build options. You can either:</p> + +<ul> + <li><a href="/en/Creating_a_Language_Pack#Creating_a_langpack" title="https://developer.mozilla.org/en/Creating_a_Language_Pack#Creating_a_langpack">Create a langpack</a>, which is installed <em>on top of</em> your Mozilla application, or</li> + <li><a href="/en/Creating_a_Language_Pack#L10n_binary_repack" title="https://developer.mozilla.org/en/Creating_a_Language_Pack#L10n_binary_repack">Repack the application's binary</a> (aka, a L10n repack), which allows you to install <em>next</em> to your existing Mozilla application installation and use separately.</li> +</ul> + +<p>Visit the links above to learn how to make these testing builds.</p> + +<h2 id="Testar_a_sua_L10n_e_ver_o_seu_trabalho">Testar a sua L10n e ver o seu trabalho</h2> + +<p>Now that you have your langpack or L10n repack, let's discuss seeing your work and testing it in the application.</p> + +<p>Testing the langpack will put you one step closer to having your localization added to the L10n releases. Follow the steps below to test your localization:</p> + +<ol> + <li>Install Aurora in your preferred language.</li> + <li>Install the <code>.xpi</code> langpack you just created (or exported).</li> + <li>Set your language using the Quick Locale Switcher or Locale Switcher add-ons by navigating to Tools->Language->Your localization's language code.</li> + <li>Restart your browser and start testing!</li> +</ol> + +<p>Now you should be able to see all of your work up to this point. Click <a class="link-https" href="https://wiki.mozilla.org/MozillaQualityAssurance:l10n_checklist" title="https://wiki.mozilla.org/MozillaQualityAssurance:l10n_checklist">here</a> for guidelines on how to test your localization.</p> + +<h2 id="Não_perca_o_seu_trabalho!">Não perca o seu trabalho!</h2> + +<p>Your work is <em>SO</em> important! We would really hate to see you lose any of it. After you test your localization, you should send it to a remote repository, which will serve as a backup for your work and will let others follow your progress. We're going to go through the process below.</p> + +<p>The official localization teams use repositories at <a class="external" href="http://hg.mozilla.org/" rel="external" title="http://hg.mozilla.org/">hg.mozilla.org</a>. Before a team becomes official, we like to get the localizers comfortable with the Hg commands that allow for cloning, pulling, committing, and pushing work to an experimental repository. We use a web service called <a class="external" href="http://www.bitbucket.org/" rel="external" title="http://www.bitbucket.org/">Bit Bucket</a> to start the learning process.</p> + +<div class="note"><strong>Nota</strong>: You must have Mercurial configured before you begin. That step is back on the initial setup page. If you haven't done that yet, don't worry, we'll wait for you!</div> + +<h3 class="note" id="Envio_(Pushing)_para_o_seu_repositório">Envio (Pushing) para o seu repositório</h3> + +<p>There are a couple of things you should take note of before you push to your repository:</p> + +<ul> + <li>Make sure that your files have been encoded in Unicode without BOM (byte order mark).</li> + <li>Remember that here you are pushing an entire directory, not a <code>.zip</code> archive file or an <code>.xpi</code> lang pack.</li> +</ul> + +<p>The instructions below will help you learn how to use your Hg repository.</p> + +<ol> + <li><span style="color: #daa520;">After your new repository is created by the l10n-drivers</span>, please visit the URL for your repo. We'll use x-testing here for our example. You can do this by entering the following URL into your browser: <code><a class="external" href="http://hg.mozilla.org/l10n-central/x-testing" rel="freelink">http://hg.mozilla.org/l10n-central/x-testing</a></code></li> + <li>Now, navigate to your locale's directory on your local machine.</li> +</ol> + +<p style="margin-left: 40px;">If you're using Koala, this should be located at <code>/path/to/your/koala.project/locale/3.6/x-testing</code>, otherwise, it should be located at <code>/path/to/your/working_dir/l10n_base/x-testing</code>.</p> + +<p style="margin-left: 40px;">In this directory, you should have an hg repository. You might have created it yourself by running <code>hg init</code> or <code>hg clone</code> or you might have had it created by Koala when you were setting up a new localization project. Also at this point, you shouldn't have any uncommitted changes (i.e., running the <code>hg status </code>command should show nothing). Let's see what the last revision in this repository is.</p> + +<ol start="3" style="list-style-type: decimal;"> + <li>Enter the following command: <code>$ hg log -l 1</code></li> +</ol> + +<p style="margin-left: 40px;">You should see an output similar to the one below:</p> + +<pre style="margin-left: 40px;">changeset: 0:7c543e8f3a6a +tag: tip +user: Your Name <email@example.com> +date: Mon Nov 23 18:08:25 2009 +0100 +summary: Added search bar strings +</pre> + +<ol start="4" style="list-style-type: decimal;"> + <li>Now compare the local repository on your machine with the remote Hg repository by entering this command: <code>$ hg outgoing <a class="external" href="http://hg.mozilla.org/l10n-central/x-testing" rel="freelink">http://hg.mozilla.org/l10n-central/x-testing</a></code></li> +</ol> + +<p style="margin-left: 40px;">The <code>hg outgoing</code> command compares the two repositories and lists all changesets that are present locally, but not in the remote repository. These changesets will need to be "pushed" to the remote repository. You can expect to see output like this:</p> + +<pre style="margin-left: 40px;">comparing with http://hg.mozilla.org/l10n-central/x-testing +searching for changes + +changeset: 0:7c543e8f3a6a +tag: tip +user: Your Name <email@example.com> +date: Mon Nov 23 18:08:25 2009 +0100 +summary: Added search bar strings +</pre> + +<ol start="5" style="list-style-type: decimal;"> + <li>Let's now push this changeset. Enter the following command:<code> hg push <a class="external" href="http://hg.mozilla.org/l10n-central/x-testing" rel="freelink">http://hg.mozilla.org/l10n-central/x-testing</a></code></li> + <li>Mercurial will connect to your repo and ask you to provide your account information (i.e., the username and the password).</li> +</ol> + +<pre style="margin-left: 40px;">real URL is http://hg.mozilla.org/l10n-central/x-testing +pushing to http://hg.mozilla.org/l10n-central/x-testing +searching for changes +http authorization required +realm: hg.mozilla.org HTTP +user: your_id +password: +</pre> + +<p style="margin-left: 40px;">After you enter your account information, the changeset will be pushed.</p> + +<pre style="margin-left: 40px;">adding changesets +adding manifests +adding file changes +added 1 changesets with 2 changes to 2 files +bb/acl: your_id is allowed. accepted payload. +quota: 979.7 KB in use, 150.0 MB available (0.64% used) +</pre> + +<p>Your changeset has been successfully pushed to your repository!</p> + +<p>As you begin to move through your translations, you should <code>commit</code> the changes locally and <code>push</code> your work to this experimental repository. For instance, if you have finished translating all the <code>.dtd</code> and <code>.properties</code> files in your <code>x-testing/browser/chrome/browser/</code> directory, then you should run these commands:</p> + +<pre>$ hg status +$ hg commit -m "Translated browser/chrome/browser/" +$ hg outgoing +$ hg push http://hg.mozilla.org/l10n-central/x-testing</pre> + +<p>Note that due to the distributed nature of Hg, <code>hg commit</code> saves the changes locally (i.e., in your computer's Hg repository). You can see the history of commits with <code>hg log</code>. After doing <code>hg commit</code>, you still need to send the changes to the remote repository. This is where <code>hg push</code> comes in. This sends your commits to the remote repository.</p> + +<p>Now you're ready to proceed to the release phase!</p> + +<p> </p> + +<p>{{ PreviousNext("Localization_Quick_Start_Guide/Translation_phase", "Localization_Quick_Start_Guide/Release_phase") }}</p> diff --git a/files/pt-pt/mozilla/localization/guia_iniciação_rápida/index.html b/files/pt-pt/mozilla/localization/guia_iniciação_rápida/index.html new file mode 100644 index 0000000000..7135cec329 --- /dev/null +++ b/files/pt-pt/mozilla/localization/guia_iniciação_rápida/index.html @@ -0,0 +1,41 @@ +--- +title: Guia de Iniciação Rápida da Localização +slug: Mozilla/Localization/Guia_iniciação_rápida +tags: + - Guía + - Tradução +translation_of: Mozilla/Localization/Quick_start_guide +--- +<p>Bem-vindo à localização da Mozilla (abreviado em inglês L10n)!</p> + +<p>Se está aqui para iniciar a sua própria localização no projeto Mozilla ou para se juntar aos esforços de uma localização existente, veio ao lugar certo. Este guia é preenchido com todas as informações técnicas básicas que precisa para se envolver no programa Mozilla l10n. Nós iremos guiá-lo através dos passos para começar, desde a configuração inicial do ambiente até ao teste e lançamento da sua própria localização. Ao longo do caminho, irá aprender sobre a variedade de projetos para os quais pode contribuir e as ferramentas utilizadas para localizá-los.</p> + +<p>Quando alcamçamos exemplos específicos, nós iremos removê-los do projeto Firefox, já que é o projeto mais amplamente localizado dentro da Mozilla. Ao aproximar-se do final deste guia, poderá fazer uma alteração no Firefox na sua configuração local e, depois ver essa alteração na interface do Firefox. Para encerrar, quando terminar este guia, terá todas as ferramentas necessárias para começar a contribuir!</p> + +<p>Lembre-se, este guia irá instruí-lo apenas sobre os aspetos técnicos de L10n da Mozilla. 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 de L10n</a> para saber mais sobre todo o processo.</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="https://developer.mozilla.org/pt-PT/docs/Mozilla/Localization/Guia_inicia%C3%A7%C3%A3o_r%C3%A1pida/Configuracao_inicial" title="en/Localization_Quick_Start_Guide/Initial_setup">Configuração Inicial</a></h2> +Preparação da tecnologia antes de localizar.</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="https://developer.mozilla.org/pt-PT/docs/Mozilla/Localization/Guia_inicia%C3%A7%C3%A3o_r%C3%A1pida/Fase_da_Traducao" title="en/Localization_Quick_Start_Guide/Translation_phase">Fase da tradução</a></h2> +Tutoriais das ferramentas de L10n para tradução.</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_de_PR"><a href="/pt-PT/docs/Mozilla/Localization/Guia_inicia%C3%A7%C3%A3o_r%C3%A1pida/Fase_PR" title="en/Localization_Quick_Start_Guide/QA_phase">Fase de PR</a></h2> +Tutoriais de teste de L10n.</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_Lançamento"><a href="https://developer.mozilla.org/pt-PT/docs/Mozilla/Localization/Guia_inicia%C3%A7%C3%A3o_r%C3%A1pida/Fase_de_lancamento" title="en/Localization_Quick_Start_Guide/Release_phase">Fase de Lançamento</a></h2> +Passos para submeter o seu trabalho de tradução.</div> + +<div style="background-color: white; border: 3px solid; display: block; padding: 20px; margin-top: 20px;">Esses quatro estágios formam o lado técnico do programa de l10n. Para saber mais sobre qualquer um deles, clique em quaisquer das hiperligações acima. Para obter uma visão geral, nós sugerimos que comece com a bolha verde e mova de um estágio para outro.</div> + +<p> </p> + +<div class="note"><strong>Nota</strong>: este guia foi escrito para dois tipos de colaboradores: os que iniciam uma nova localização e os que se juntam a uma localização existente. É importante saber que informação se aplica ao tipo de colaborador. Para ajudá-lo a filtrar a informação mais aplicável, note que toda a informação que é única das que iniciam uma nova localização estarão com <span style="color: #daa520;">letra em cor de laranja</span>. Toda a informação que é única para aqueles que se juntam a uma localização existente estará em <span style="color: #0000ff;">letra azul</span>.</div> + +<p class="note"> </p> + +<p>{{ Next("Localization_Quick_Start_Guide/Initial_setup") }}</p> diff --git a/files/pt-pt/mozilla/localization/index.html b/files/pt-pt/mozilla/localization/index.html new file mode 100644 index 0000000000..049ddf8e95 --- /dev/null +++ b/files/pt-pt/mozilla/localization/index.html @@ -0,0 +1,23 @@ +--- +title: Localização na Mozilla +slug: Mozilla/Localization +tags: + - Landing + - Localização + - Mozilla + - Tradução + - l10n +translation_of: Mozilla/Localization +--- +<p><span class="seoSummary"><strong>Localização</strong> (L10n) é o processo de tradução das interfaces do utilizador do software de um idioma para outro e a adaptação para o ajustar a uma cultura estrangeira. Estes recursos são para qualquer um com interesse nos aspetos técnicos involvidos na localização.</span> Estes são para os responsáveis pelo desenvolvimento e todos os colaboradores.</p> + +<h2 id="Consultar_também">Consultar também</h2> + +<dl> + <dt><a href="/pt-PT/docs/MDN/Contribute/Localize" title="/en-US/docs/Project:MDN/Localizing">Localizar MDN</a></dt> + <dd>Este recurso abrange a localização da documentação aqui na MDN.</dd> + <dt><a href="/pt-PT/docs/Archive/B2G_OS/Firefox_OS_apps/Localiza%C3%A7%C3%A3o">Localização de aplicação</a></dt> + <dd>Este conjunto de documentos aplica-se mais especificamente à localização de aplicações, incluindo as aplicações do Firefox OS.</dd> + <dt><a href="/en-US/docs/Web/API/L10n">L10n</a></dt> + <dd>Documentos de referência para a API de L10n que a Mozilla utilzia para localizar o sistema operativo Firefox.</dd> +</dl> diff --git a/files/pt-pt/mozilla/localization/index/index.html b/files/pt-pt/mozilla/localization/index/index.html new file mode 100644 index 0000000000..3b35d9f58b --- /dev/null +++ b/files/pt-pt/mozilla/localization/index/index.html @@ -0,0 +1,9 @@ +--- +title: Índex +slug: Mozilla/Localization/Index +tags: + - Localização + - Tradução +translation_of: Mozilla/Localization/Index +--- +<p>{{Index("/pt-PT/docs/Mozilla/Localization")}}</p> diff --git a/files/pt-pt/mozilla/localization/localizacao_e_plurais/index.html b/files/pt-pt/mozilla/localization/localizacao_e_plurais/index.html new file mode 100644 index 0000000000..207f94128f --- /dev/null +++ b/files/pt-pt/mozilla/localization/localizacao_e_plurais/index.html @@ -0,0 +1,384 @@ +--- +title: Tradução e Plurais +slug: Mozilla/Localization/Localizacao_e_Plurais +tags: + - Internacionalização + - Localização + - Tradução +translation_of: Mozilla/Localization/Localization_and_Plurals +--- +<p>Provavelmente está aqui porque está a traduzir um ficheiro .properties e este tinha uma hiperligação para esta página. Esta página é para ajudar a explicar como localizar essas entradas de carateres para que a forma correta do plural seja mostrada ao utilizador. Por exemplo, "1 página" vs. "2 páginas".</p> + +<p>Se está aqui para criar o seu código (por exemplo, extensões) localizável para as formas de plural, pode ir diretamente para <a href="#Developing_with_PluralForm">Programar com <em>PluralForm</em></a>. Também poderá ter que localizar as entradas iniciais para o seu código, por isso também seria bom que lê-se pelo menos a secção 'Utilização'.</p> + +<h2 id="Utilização">Utilização</h2> + +<p>Aqui tem alguns termos utilizados nesta página para o ajudar a manter as coisas simples:</p> + +<ul> + <li><strong>regra de plural</strong>: para um determinado idioma, existe uma regra gramatical sobre como alterar as palavras, dependendo do número que qualifica a palavra. Idiomas diferentes podem ter regras diferentes.</li> + <li><strong>forma de plural</strong>: para uma regra de plural específica, pode haver várias formas de uma palavra, como "página" e "páginas". Neste caso, existem 2 formulários, mas outros idiomas podem ter 1 ou mais.</li> +</ul> + +<p>If you're here for <code>pluralRule</code> in the <code>chrome/global/intl.properties</code> file, you'll need to figure out what <em>plural rule</em> to choose for your localization. This plural rule is used to determine how many <em>plural forms</em> are needed for each word that needs to be localized, with plurals in mind.</p> + +<p>For all other properties files that link to this page, you'll need to provide enough plural forms of the desired word, and separate them with semi-colons (;). If you don't know how many plural forms you need, check the <code>pluralRule</code> number in <code>chrome/global/intl.properties</code>, and look up the corresponding entry in the following list of plural rules.</p> + +<h2 id="Lista_das_Regras_de_Plural">Lista das Regras de Plural</h2> + +<p>Esta secção contém uma lista de regras plurais ordenadas pelo seu número de regra 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 nessas famílias, para ajudá-lo a descobrir se é a regra que deve escolher para <code>pluralRule</code>. Além disso, há uma breve descrição de cada forma de plural, seguida por alguns números de amostra que se enquadram nessa forma específica.</p> + +<p>For a given plural rule, the order in which the plural forms are listed is the same order you need to localize a word, separated by semi-colons. For example, English uses plural rule 1, and localizing <code>plurals</code> would require a string of "plural;plurals" where the first word is the singular form and the second is the general plural form.</p> + +<h3 id="Regra_de_plural_0_1_forma">Regra de plural #<em><strong>0</strong></em> (1 forma)</h3> + +<p><strong>Famílias</strong>: Asiáticas (chinês, japonês, coreano), persa, turco/altaico (turco), Thai, Lao<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="Regra_de_plural_1_2_formas">Regra de plural #<em><strong>1</strong></em> (2 formas)</h3> + +<p><strong>Famílias</strong>: Germânico (dinarmaquês, holandês, inglês, Faroese, Frisian, alemão, norueguês, sueco ), Finno-Ugric (Estonian, Finnish, Hungarian), Language isolate (Basque), Latin/Greek (Greek), Semitic (Hebrew), Românico (italiano, português, espanhol, catalão), e vietnamita<br> + <strong>é 1</strong>: <small>1</small><br> + <strong>tudo o 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="Regra_de_plural_2_2_formas">Regra de plural #<em><strong>2</strong></em> (2 formas)</h3> + +<p><strong>Famílias</strong>: Românico (francês, português (Brasil)), Lingala<br> + <strong>é 0 ou 1</strong>: <small>0, 1</small><br> + <strong>tudo o 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="Regra_de_plural_3_3_formas">Regra de plural #<strong><em>3</em></strong> (3 formas)</h3> + +<p><strong>Famílias</strong>: Baltic (Latvian, Latgalian)<br> + <strong>termina em 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>tudo o resto</strong>: <small>2, 3, 4, 5, 6, 7, 8, 9, 11, 12, 13, 14, 15, 16, 17, 18, 19, 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, …</small></p> + +<h3 id="Regra_de_plural_4_4_formas">Regra de plural #<em><strong>4</strong></em> (4 formas)</h3> + +<p><strong>Famílias</strong>: Celtic (Scottish Gaelic)<br> + <strong>é 1 ou 11</strong>: <small>1, 11</small><br> + <strong>é 2 ou 12</strong>: <small>2, 12</small><br> + <strong>is 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>tudo o 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="Regra_de_plural_5_3_formas">Regra de plural #<em><strong>5</strong></em> (3 formas)</h3> + +<p><strong>Famílias</strong>: Romanic (Romanian)<br> + <strong>é 1</strong>: <small>1</small><br> + <strong>é 0 ou termina em 01-19, excluindo 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>tudo o resto</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="Regra_de_plural_6_3_formas">Regra de plural #<em><strong>6</strong></em> (3 formas)</h3> + +<p><strong>Famílias</strong>: Baltic (Lithuanian)<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>termina em 0 ou termina em 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>tudo o resto</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="Regra_de_plural_7_3_formas">Regra de plural #<em><strong>7</strong></em> (3 formas)</h3> + +<p><strong>Famílias</strong>: Belarusian, Russian, Ukrainian<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>termina em 2-4, excluindo 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>tudo o resto</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, …, 112, 113, ..., 212, 213, ...</small></p> + +<h3 id="Regra_de_plural_8_3_formas">Regra de plural #<em><strong>8</strong></em> (3 formas)</h3> + +<p><strong>Famílias</strong>: Eslavo (eslovaco, checo)<br> + <strong>é 1</strong>: <small>1</small><br> + <strong>é 2-4</strong>: <small>2, 3, 4</small><br> + <strong>tudo o resto</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="Regra_de_plural_9_3_formas">Regra de plural #<em><strong>9</strong></em> (3 formas)</h3> + +<p><strong>Famílias</strong>: Eslavo (polaco)<br> + <strong>é 1</strong>: <small>1</small><br> + <strong>termina em 2-4, excluindo 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>tudo o resto</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_10_4_forms">Plural rule #<em><strong>10</strong></em> (4 forms)</h3> + +<p><strong>Famílias</strong>: Eslavo (esloveno, sérbio)<br> + <strong>termina em 01</strong>: <small>1, 101, 201, …</small><br> + <strong>termina em 02</strong>: <small>2, 102, 202, …</small><br> + <strong>termina em 03-04</strong>: <small>3, 4, 103, 104, 203, 204, …</small><br> + <strong>tudo o resto</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_11_5_forms">Plural rule #<em><strong>11</strong></em> (5 forms)</h3> + +<p><strong>Famílias</strong>: Celtic (Irish Gaelic)<br> + <strong>é 1</strong>: <small>1</small><br> + <strong>é 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>tudo o resto</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_12_6_forms">Plural rule #<em><strong>12</strong></em> (6 forms)</h3> + +<p><strong>Famílias</strong>: Semitic (Arabic)<br> + <strong>é 1</strong>: <small>1</small><br> + <strong>é 2</strong>: <small>2</small><br> + <strong>termina em 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>tudo o resto but é 0 and termina em 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>termina em 00-02, excluding 0-2</strong>: <small>100, 101, 102, 200, 201, 202, …</small><br> + <strong>é 0</strong>: <small>0</small></p> + +<h3 id="Plural_rule_13_4_forms">Plural rule #<em><strong>13</strong></em> (4 forms)</h3> + +<p><strong>Famílias</strong>: Semitic (Maltese)<br> + <strong>é 1</strong>: <small>1</small><br> + <strong>é 0 ou termina em 01-10, excluindo 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>termina em 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>tudo o resto</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_14_3_forms">Plural rule #<em><strong>14</strong></em> (3 forms)</h3> + +<p><strong>Famílias</strong>: unused<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>tudo o resto</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_15_2_forms">Plural rule #<em><strong>15</strong></em> (2 forms)</h3> + +<p><strong>Famílias</strong>: Icelandic, Macedonian<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>tudo o resto</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_16_5_forms">Plural rule #<em><strong>16</strong></em> (5 forms)</h3> + +<p><strong>Famílias</strong>: Celtic (Breton)<br> + <strong>termina em 1, excluindo 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, excluindo 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 excluindo 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>termina em 1000000</strong>: <small>1000000: 1000000, 2000000, 3000000, 4000000, 5000000, 6000000, 7000000, 8000000, 9000000, 10000000, ...</small><br> + <strong>tudo o resto</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> + +<h3 id="Plural_rule_17_2_forms">Plural rule #17 (2 forms)</h3> + +<p><strong>Famílias</strong>: Ecuador indigenous languages (Shuar)<br> + <strong>é 0</strong>: <small>0</small><br> + <strong>tudo o resto</strong>: <small>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, 50, 51, …</small></p> + +<h3 id="Plural_rule_18_6_forms">Plural rule #18 (6 forms)</h3> + +<p><strong>Famílias</strong>: Welsh<br> + <strong>é 0</strong>: <small>0</small><br> + <strong>é 1</strong>: <small>1</small><br> + <strong>é 2</strong>: <small>2</small><br> + <strong>is 3</strong>: <small>3</small><br> + <strong>é 6</strong>: <small>6</small><br> + <strong>tudo o resto</strong>: <small>4, 5, 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_19_3_forms">Plural rule #<em><strong>19</strong></em> (3 forms)</h3> + +<p><strong>Famílias</strong>: Slavic (bósnio, croata, sérvio)<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>termina em 2-4, excluindo 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>tudo o resto</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, …, 112, 113, ..., 212, 213, ...</small></p> + +<h2 id="Exemplos">Exemplos</h2> + +<p>A seguir tem alguns exemplos para vários idiomas e um breve processo de reflexão.</p> + +<h3 id="Francês">Francês</h3> + +<p>Some French speaking places treat 0 as plural while others treat it as singular. The only other singular é 1 while tudo o resto 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="Chinês">Chinês</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="Polaco">Polaco</h3> + +<p>There's a singular form fou 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 "termina em 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="Sérbio">Sérbio</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="Extensão_de_Teste">Extensão de Teste</h2> + +<p>Para ajudar a ter a certeza de que escolhe a regra de plural correta e fornecer formas de plural suficientes para as sequências de carateres, deveria utilizar a extensão "pluralForm Checker". Depois de instalar a extensão, esta deverá estar disponível no menu de "Ferramentas".</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="https://ed.agadak.net/firefox/pluralForm-checker.xpi">Instalar a extensão Checker v0.3 de <em>pluralForm</em></a></p> + +<h3 id="Entrada_de_extensão">Entrada de extensão</h3> + +<p>Seria bom manter esta lista atualizada com todas as palavras que precisam de formas plurais. As pessoas que utilizam a extensão podem copiar/colar esta entrada.</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="Histórico_de_versão">Histórico de versão</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="Programar_com_PluralForm">Programar com <em>PluralForm</em></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="Carregar_PluralForm.jsm">Carregar <code>PluralForm.jsm</code></h3> + +<p>Loading the PluralForm module from JavaScript is simple with <a href="/en-US/docs/Mozilla/Tech/XPCOM/Language_Bindings/Components.utils.import" title="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="Métodos_get">Métodos: <em><code>get</code></em></h3> + +<p>Estes métodos utilizam o idioma atual do navegador especificado pelo valor <code><a class="external" rel="freelink">chrome://global/locale/intl.properties</a></code>'s <code>pluralRule</code>.</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>Aqui tem um exemplo de utilização deste método:</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 fou 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: https://developer.mozilla.org/en-US/docs/Mozilla/Localization/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="Método_makeGetter">Método: <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>. This is 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>Aqui tem um exemplo de utilização de <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-US/docs/Web/JavaScript/Reference/Operators/Destructuring_assignment" title="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="Créditos">Créditos</h2> + +<p>Inicialmente, o código da "Forma de Plural" foi implementado por {{ Bug(394516) }} - <em>Figure out a remaining-time rounding scheme for minutes -> hours/days</em><br> + As regras de plural e as familias derivadas da <a class="external" href="https://www.gnu.org/software/gettext/manual/html_node/gettext_150.html#Plural-forms">documentação <code>gettext</code> da GNU</a>.</p> diff --git a/files/pt-pt/mozilla/localization/localizar_com_mercurial/index.html b/files/pt-pt/mozilla/localization/localizar_com_mercurial/index.html new file mode 100644 index 0000000000..de4a09643f --- /dev/null +++ b/files/pt-pt/mozilla/localization/localizar_com_mercurial/index.html @@ -0,0 +1,256 @@ +--- +title: Localizar com Mercurial +slug: Mozilla/Localization/Localizar_com_Mercurial +tags: + - Documentação de criação + - Internacionalização + - Localização + - Tradução +translation_of: Mozilla/Localization/Localizing_with_Mercurial +--- +<p>In Mozilla, we use the the <a href="../../../../en/Mercurial_basics" rel="internal">Mercurial</a> version control system (Hg) to manage our source code and localizations. Mercurial allows localizers to work locally (on their machines) and then <code style="font-size: 14px;">push</code> (an Hg term) changes to a remote repository, which usually is hosted on the Mozilla servers (<a class="external" href="http://hg.mozilla.org/" title="http://hg.mozilla.org/">hg.mozilla.org</a>). Localizing current versions of Firefox, Thunderbird and SeaMonkey includes working with Mercurial. If the documentation is incomplete or you have questions, please drop by the <a href="irc://irc.mozilla.org/l10n" title="irc://irc.mozilla.org/l10n">#l10n</a> or <a href="irc://irc.mozilla.org/hg" title="irc://irc.mozilla.org/hg">#hg</a> channels on irc.mozilla.org. The <a class="internal" href="/en/Mercurial_FAQ" title="En/Mercurial FAQ">Mercurial FAQ</a> are also worth a read, should you run into trouble.</p> + +<p>For the eager and quick, below you'll find instructions on installing and configuring Mercurial, instructions on receiving an Hg account commit priviledges, as well as a few tasks you can complete without account priviledges.</p> + +<h2 id="Instalar_Mercurial">Instalar Mercurial</h2> + +<p>Follow the instructions below to install Mercurial on your system. Once you've installed Mercurial, we'll walk through the steps to <a href="/en/Mercurial_FAQ#Configuration" title="en/Mercurial FAQ#Configuration">configure</a> it.</p> + +<h3 id="Mercurial_no_Linux">Mercurial no Linux</h3> + +<p>You can easily install Mercurial from the command line by issuing one of the following commands. Choose the appropriate command for your distribution and make sure to run <em>as root</em>.</p> + +<pre># Debian/ubuntu +$ apt-get install mercurial + +# Fedora +$ yum install mercurial + +# Gentoo +$ emerge mercurial + +# Arch Linux +$ pacman -S mercurial + +# OpenSolaris +$ pkg install SUNWmercurial +</pre> + +<p>Se preferir uma interface gráfica, pode <a href="http://javaforge.com/project/HGE" title="http://javaforge.com/project/HGE">transferir e instalar o MercurialEclips e aqui</a>.</p> + +<h4 id="Este_funcionou">Este funcionou?</h4> + +<p>Open a Terminal window and enter <code>hg --version</code>. If you see a message about the version of Mercurial (e.g. <code>Mercurial Distributed SCM (version 1.3.1)</code>), you have installed Mercurial successfully!</p> + +<h4 id="Mais_detalhes">Mais detalhes</h4> + +<p>For more details on installing Hg on Linux systems, refer to the <a class="external" href="http://mercurial.selenic.com/downloads/" title="http://mercurial.selenic.com/downloads/">instructions on Mercurial's Download page</a>.</p> + +<h3 id="Mercurial_no_Windows">Mercurial no Windows</h3> + +<p>With Windows, you have a couple of install options:</p> + +<ul> + <li>For a <strong>command line interface</strong>, download and install {{ interwiki("wikimo", "MozillaBuild") }} package. This will not only install Hg, but also all the tools required to build Mozilla products on Windows. Trust us, you'll want this eventually.</li> + <li><a href="/@api/deki/files/3863/=TortoiseHg.png" title="TortoiseHg.png"><img alt="TortoiseHg.png" class="internal rwrap" src="/@api/deki/files/3863/=TortoiseHg.png?size=thumb" style="float: right; height: 115px; width: 160px;"></a>For a <strong>graphical interface</strong>, you may want to <a class="external" href="http://tortoisehg.bitbucket.org/" title="http://tortoisehg.bitbucket.org/">install TortoiseHg</a>, which integrates with your Windows Explorer shell. It also installs the command line utility.</li> +</ul> + +<p><a href="/@api/deki/files/3861/=Mercurial_Installer.png" title="Mercurial Installer.png"><img alt="Mercurial Installer.png" class="internal rwrap" src="/@api/deki/files/3861/=Mercurial_Installer.png?size=thumb" style="float: right; height: 125px; width: 160px;"></a>Part of the command line Hg install for Windows involves making sure the <code>hg </code>executable is in the system's <code>%PATH%</code> variable (TortoiseHg doesn't need this step). Use the <code>add_path.exe</code> utility found in <code>C:\mozilla-build\hg</code> to do this.</p> + +<pre>PS C:\Users\your_id> cd C:\mozilla-build\hg +PS C:\mozilla-build\hg> .\add_path.exe /result . +</pre> + +<p>Note the dot ("<code>.</code>") at the end of the second command, which means <em>the current directory</em>. If the utility modified your <code>%PATH%</code> successfully, a dialog will open saying, "<code><em>%PATH%</em></code><em> has been updated correctly</em>."</p> + +<p>Alternatively, you can edit the <code>%PATH%</code> variable manually. In order to do so, right-click on your computer icon, choose <code>Properties > Advanced > Environmental Variables</code>, select <code>PATH </code>and click <code>Edit</code>. If you don't see <code>PATH</code> among the options, you'll have to click <code>Add</code> and edit it within the <strong>Add</strong> dialog. See the screenshot for an example.<a href="/@api/deki/files/3862/=PATH.jpg" title="PATH.jpg"><img alt="PATH.jpg" class="internal rwrap" src="/@api/deki/files/3862/=PATH.jpg?size=thumb" style="float: right; height: 71px; width: 160px;"></a></p> + +<h4 id="Este_funcionou_2">Este funcionou?</h4> + +<ol> + <li>Go to <code>Start > Run...</code></li> + <li>Type <code>cmd.exe </code>and click <code>OK</code>. A new shell window should appear. </li> + <li>Type <code>hg --version</code> in the new shell window. If you see a message about the version of Mercurial (e.g. <code>Mercurial Distributed SCM (version 1.3.1)</code>), you have installed Mercurial successfully!</li> +</ol> + +<h4 id="Mais_detalhes_2" style="font-size: 14px;">Mais detalhes</h4> + +<p>For more details on installing Hg on Windows, refer to the <a class="external" href="http://mercurial.selenic.com/downloads/" title="http://mercurial.selenic.com/downloads/">instructions on Mercurial's Download page</a>.</p> + +<h3 id="Mercurial_no_Mac_OSX">Mercurial no Mac OSX</h3> + +<p>Installing Hg on Mac OSX is super easy. You can install Mercurial via <a class="external" href="http://www.macports.org/" title="http://www.macports.org/">MacPorts</a> through the Terminal, like so:</p> + +<p><code>$ sudo port install mercurial</code></p> + +<p>You can also install it by downloading the dmg package from the <a href="http://mercurial.selenic.com/wiki/Download#Mac_OS_X" title="http://mercurial.selenic.com/wiki/Download#Mac_OS_X">Hg download page</a>. It has an install dialog that will walk you through the process.</p> + +<p>If you prefer a graphical interface, you can <a href="http://javaforge.com/project/HGE" title="http://javaforge.com/project/HGE">download and install MercurialEclipse here</a>.</p> + +<h4 id="Este_funcionou_3">Este funcionou?</h4> + +<p>Open a Terminal window and type <code>hg --version</code>. If you see a message about the version of Mercurial (e.g. <code>Mercurial Distributed SCM (version 1.3.1)</code>), you have installed Mercurial successfully!</p> + +<h4 id="Mais_detalhes_3" style="font-size: 14px;">Mais detalhes</h4> + +<p>For more details on installing Hg on Mac OSX, refer to the <a class="external" href="http://mercurial.selenic.com/downloads/" title="http://mercurial.selenic.com/downloads/">instructions on Mercurial's Download page</a>.</p> + +<h2 id="Configurar_o_Mercurial">Configurar o Mercurial</h2> + +<p>Once you've installed Mercurial, you'll need to configure it before you can use it successfully.</p> + +<p>Your Mercurial configuration is contained within a config file which you must create yourself. Your config file is called either <code style="font-size: 14px; color: rgb(51, 51, 51);">~/.hgrc</code> (UNIX systems) or <code style="font-size: 14px; color: rgb(51, 51, 51);">Mercurial.ini</code> (Windows), depending on your operating system.</p> + +<p>Your config file should have the following settings:</p> + +<pre class="eval">[ui] +username = Your Real Name <<a class="link-mailto" href="mailto:user@example.com" rel="external" title="mailto:user@example.com">user@example.com</a>> +merge = internal:merge + +[defaults] +commit = -v + +[diff] +git = 1 +showfunc = 1 +unified = 8</pre> + +<p>To configure Hg, follow these steps:</p> + +<ol> + <li>Create a new file in your favorite text editor.</li> + <li>Copy the settings above and paste them into your new file.</li> + <li>Save the file as either <code>.hgrc</code> (UNIX systems) or <code>Mercurial.ini</code> (Windows) and save it in either <code>$HOME/</code> or <code>C:\mozilla-build\hg\</code> or <code>C:\Program Files\Mercurial\</code>.</li> +</ol> + +<p>Now that you've installed and configured Mercurial, here are a few tasks you can do without Hg commit access priviledges.</p> + +<h2 id="Clonar_e_atualizar_os_repositórios">Clonar e atualizar os repositórios</h2> + +<p>There are a couple of repostiories that contain en-US source files that most locales will want to deal with.</p> + +<ul> + <li><a class="external" href="https://hg.mozilla.org/mozilla-central/" title="https://hg.mozilla.org/mozilla-central/">mozilla-central</a> contains the files for Firefox Nightly.</li> + <li><a class="external" href="https://hg.mozilla.org/comm-central/" title="https://hg.mozilla.org/comm-central">comm-central</a> contains the files for SeaMonkey and Thunderbird which are not already part of Firefox.</li> + <li><a href="https://hg.mozilla.org/l10n-central/" title="https://hg.mozilla.org/l10n-central/">l10n-central</a> contains all of the L10n repos for Firefox Nightly.</li> +</ul> + +<div class="note"> +<p>When you get the comm-central repository, this will include the mozilla-central repository as well. You can therefore use the one set up for developing Firefox, SeaMonkey and Thunderbird without having to pull mozilla-central a second time.</p> +</div> + +<p>Here's how to get (or clone) your en-US source files for the first time:</p> + +<ul> + <li>Run the following command in the command line to get the source en-US files for Firefox:</li> +</ul> + +<pre class="eval">hg clone https://hg.mozilla.org/mozilla-central/ +</pre> + +<p>This will create a clone of the mozilla-central repository in the directory mozilla-central.</p> + +<ul> + <li>Run the following commands in the command line to get the source en-US files for any combination of Firefox, SeaMonkey, Thunderbird:</li> +</ul> + +<pre>hg clone https://hg.mozilla.org/comm-central/ +cd comm-central +python client.py checkout +</pre> + +<p>The first command will create a clone of the comm-central repository. The second command will move you into that directory. The third command will do a clone of mozilla-central, and pull some other hg repositories. The other directories are required for SeaMonkey and Thunderbird.</p> + +<ul> + <li>Cloning your localization repository for the first time is just as easy. For example, to clone your Firefox Nightly L10n repo, run the following command, replacing ab-CD with your locale code:</li> +</ul> + +<pre class="eval" style="font-size: 14px;">hg clone https://hg.mozilla.org/l10n-central/ab-CD/</pre> + +<h3 id="Atualizar_os_seus_repositórios_locais">Atualizar os seus repositórios locais</h3> + +<ul> + <li>To update your working copy of mozilla-central, go to your local mozilla-central directory and run:</li> +</ul> + +<pre class="eval">hg pull -u +</pre> + +<p>This will both get new changesets from mozilla-central and apply those changes in your working copy.</p> + +<ul> + <li>To update your working copy of comm-central, go to your comm-central directory and run:</li> +</ul> + +<pre>python client.py checkout</pre> + +<p>This will both get new changesets from comm-central, mozilla-central and the other appropriate locations and apply those changes in your working copy.</p> + +<ul> + <li>To update your local L10n repo after your first clone, run this command from your local L10n directory:</li> +</ul> + +<pre style="font-size: 14px;">hg pull -u</pre> + +<h2 id="Criar_correções_(patches)_de_L10n">Criar correções (patches) de L10n</h2> + +<p>Another thing you can do with Hg without needing account priviledges is creating L10n patches of your work for someone else to commit to your remote L10n repo on the Mozilla servers. Doing this ensures that your dashboards are always accurate, as they look at your remote repo.</p> + +<p>Here's how to create a L10n patch with Hg and the <a href="http://mercurial.selenic.com/wiki/MqExtension" title="http://mercurial.selenic.com/wiki/MqExtension">Mq extension</a>:</p> + +<ol> + <li>Enable Mq by adding <code>hg.ext = </code> to your Mercurial config file (<code>~/.hgrc</code> on Unix-like systems or <code>Mercurial.ini</code> on Windows) under the <code>[extensions]</code> section.</li> + <li>Open your command line tool and navigate to your L10n directory.</li> + <li>Inside your L10n directory, init your repo with Mq by running <code>hg init --mq</code>.</li> + <li>To create a new patch, run <code>hg qnew -m "Your commit message" patch-name.patch</code>. The commit message should take the form of "Bug 123456 - Change this thing to work better by doing something; r=reviewers" if you are to fix a bug.</li> + <li>Make your change.</li> + <li>Once you finish making your change, run <code>hg qrefresh</code> to commit your changes to the patch.</li> + <li>Navigate to your <code><repository>/.hg/patches</code> to find your <code>.patch</code>.</li> + <li>You may repeat from step 4 to create another patch. Your patches will be incremental, i.e. new patches are created based on old patches. If you want to commit all the patches to the repository and cleanup the patch queue, run <code>hg qfinish</code>.</li> +</ol> + +<p>Please refer to <a href="http://mercurial.selenic.com/wiki/MqTutorial" title="http://mercurial.selenic.com/wiki/MqTutorial">MqTutorial</a> and <a href="http://mercurial.selenic.com/wiki/MqExtension" title="http://mercurial.selenic.com/wiki/MqExtension">Mq documentation</a> for further uses of Mq extension to manage patches.</p> + +<h2 id="Privilégios_da_Conta_Mercurial">Privilégios da Conta Mercurial</h2> + +<p>Eventually, you or your team leader will need Hg account priviledges. Let's face it, it's just more convenient to commit and push your work to the remote repo yourself, rather than creating patches and asking someone else to push them for you.</p> + +<p>To get write access to the l10n hg repositories on the Mozilla server,<a class="external" href="http://www.mozilla.org/hacking/commit-access-policy/" title="http://www.mozilla.org/hacking/commit-access-policy/"> there's a bit of paper work to be done</a>. The localization team owner needs to <a class="link-https" 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)">file a bug requesting an hg account</a>. This bug will request level 1 L10n priviledges. You need to follow the instructions regarding the <a class="external" href="http://www.mozilla.org/hacking/committer/" title="http://www.mozilla.org/hacking/committer/">contributor form</a>. Write access to the hg repositories requires a ''voucher'', which, for the owner, will be done based on the review by Mozilla. For peers of a localization, the owner can vouch (once she or he is registered).</p> + +<h2 id="Pull_your_locale" name="Pull_your_locale">Enviar alterações para a Mozilla</h2> + +<p>Now that you have Hg account privileges, you can send your work to Mozilla all by yourself. Here are the steps to send your L10n work using Mercurial:</p> + +<ol> + <li>Since your L10n work takes place in your own local repository, you should ensure that there are no changes made to the remote repository before committing your work. To do this, <a href="https://developer.mozilla.org/en-US/docs/Localizing_with_Mercurial#Updating_your_local_repos" title="https://developer.mozilla.org/en-US/docs/Localizing_with_Mercurial#Updating_your_local_repos">update your locale, as per the section above</a>.</li> + <li>After finishing a change or set of changes and checking you have updated to the latest, you should commit by entering this command:</li> +</ol> + +<pre class="eval">hg commit -m "your message identifying the change (bug 555)"</pre> + +<p>Committing won’t send your changes to Mozilla’s repository, but prepares them for it. The next step will send your changes to your remote repo via <code>push</code>.</p> + +<ol start="3"> + <li>To push to mozilla-hosted repositories, you have to have committer access, and you must edit the file <code><em>(your-local-hg-root AKA the directory you pulled your locale into)</em>/.hg/hgrc</code> (note, this is <strong>NOT</strong> your <code>~/.hgrc</code>) to add these lines (replacing ab-CD with your locale code):</li> +</ol> + +<pre class="eval">[paths] +default = https://hg.mozilla.org/l10n-central/ab-CD/ +default-push = ssh://hg.mozilla.org/l10n-central/ab-CD/ +</pre> + +<ol start="4"> + <li>You’ll also need to tell ssh which account to use for your pushes, too, by editing <code>~/.ssh/config</code> and adding these lines, where <code style="font-size: 14px; color: rgb(51, 51, 51);">user@host.domain</code> is your account:</li> +</ol> + +<pre>Host hg.mozilla.org +User user@host.domain +</pre> + +<ol start="5"> + <li>Now you can push your work to the repository (and check the result on the dashboard) by entering this command from your local directory:</li> +</ol> + +<pre class="eval">hg push</pre> + +<p id="A_.mozconfig">And tah dah! You're done! Congratulations on finishing the tutorial. Take a break and grab a snack, you deserve it</p> diff --git a/files/pt-pt/mozilla/localization/localização_com_pontoon/index.html b/files/pt-pt/mozilla/localization/localização_com_pontoon/index.html new file mode 100644 index 0000000000..05fa58b1d6 --- /dev/null +++ b/files/pt-pt/mozilla/localization/localização_com_pontoon/index.html @@ -0,0 +1,138 @@ +--- +title: Traduzir com Pontoon +slug: Mozilla/Localization/Localização_com_Pontoon +tags: + - Localização + - Tradução +translation_of: Mozilla/Localization/Localizing_with_Pontoon +--- +<p><a href="https://pontoon.mozilla.org/pt-PT/" title="https://pontoon.mozilla.org">Pontoon</a> é uma ferramenta de localização (l10n), O-Que-Vê-É-O-Que-Obtém (WYSIWYG) baseada na Web. Na Mozilla, nós utilizamos o Pontoon para localizar todos os produtos e sites da Web da Mozilla, desde o Firefox até Mozilla.org. Pontoon é uma ferramenta muito simples e intuitiva que requer poucos conhecimentos técnicos para utilizar no ritmo de trabalho de l10n. Aqui, nós iremos discutir como utilizar o Pontoon para localizar projetos, desde o primeiro início de sessão até concluir as suas contribuições. Ao longo do caminho, nós iremos sugerir algumas funcionalidades que irão tornar mais eficiente e facilitar as suas contribuições no seu l10n.</p> + +<div class="note"> +<p><strong>É um programador?</strong> Leia sobre a <a href="/pt-PT/docs/Mozilla/Implementacao_do_Pontoon_num_projeto_da_Mozilla">implementação do Pontoon no seu projet</a>o ou saiba como participar no <a href="https://github.com/mozilla/pontoon">GitHub</a>.</p> +</div> + +<h2 id="Primeiros_passos">Primeiros passos</h2> + +<p><a href="https://pontoon.mozilla.org" title="https://pontoon.mozilla.org">Pontoon's home page</a> is very easy to use. To begin localizing the project, click on the Persona icon and sign in. Next, simply select the project you want to work on and your locale from the dropdown menus. Pontoon will automatically open that locale's project for you to get started. Note that for our purposes here, we'll be using <a href="https://affiliates.mozilla.org/">Firefox Affiliates</a> website to demo Pontoon's functionality and workflow. And there it is, opened inside Pontoon:</p> + +<p><em><img alt="Browser app and workspace" 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>As you can see, most of the interface is taken by the website being translated. Only the toolbar on top belongs to Pontoon, containing the following items (from left to right):</p> + +<p><img alt="Main toolbar" src="https://mdn.mozillademos.org/files/8325/toolbar.png"></p> + +<h4 id="Lista_de_textos">Lista de textos</h4> + +<p>Opens a sidebar with a list of all strings to localize.</p> + +<h4 id="Seletor_de_projeto_(Afiliados)"><span id="cke_bm_939S" style="display: none;"> </span>Seletor de projeto (Afiliados)</h4> + +<p>Switches between projects to localize.</p> + +<h4 id="Seletor_de_recursos_(Página_Inicial)"><span id="cke_bm_940S" style="display: none;"> </span>Seletor de recursos (Página Inicial)</h4> + +<p>Switches between project resources to localize, like subpages or localization files. Hidden if no resources available for project.</p> + +<h4 id="sect1"><span id="cke_bm_941S" style="display: none;"> </span></h4> + +<dl> +</dl> + +<h4 id="Seletor_de_idioma_(Esloveno)">Seletor de idioma (Esloveno)</h4> + +<p>Switches between languages to localize.</p> + +<h4 id="Ir">Ir</h4> + +<p>Opens project-resource-locale selection.</p> + +<h4 id="Indicado_do_progresso">Indicado do progresso</h4> + +<p>Displays your progress on the resource being localized. More details are available in the popup.</p> + +<dl> +</dl> + +<h4 id="Menu_do_utilizador"><span id="cke_bm_943S" style="display: none;"> </span>Menu do utilizador</h4> + +<p>Allows for user-specific tasks, like commiting to repository, downloading files and signing out.</p> + +<h4 id="Menu_da_informação">Menu da informação</h4> + +<p>Gives important information, like the anticipated project timeline and a list of keyboard shortcuts.</p> + +<dl> +</dl> + +<p>Alright, how about we do some translating now?<span id="cke_bm_608E" style="display: none;"> </span></p> + +<dl> +</dl> + +<h2 id="Traduzir_texto">Traduzir texto</h2> + +<p>When using Pontoon for localization, you have a couple of options to translate your strings. You can translate in-context, out-of-context, or a combination of the two. We'll start with looking at in-context translation.</p> + +<h3 id="In-context">In-context</h3> + +<p>Pontoon's in-context translation mode is what puts it above others. It opens a web page (or web app) and enables real-time editing of that page. Here's how you translate your first string:</p> + +<p><img alt="In-context localization" src="https://mdn.mozillademos.org/files/8331/in-context.png"></p> + +<ol> + <li>Hover over the text you want to translate with your mouse.</li> + <li>An edit button appears over that text. Click on it to enable the translate mode.</li> + <li>Replace the original text with its translation into your language.</li> + <li>Click the save button to save your translation.</li> +</ol> + +<div> +<h3 id="Out-of-context">Out-of-context</h3> + +<p>Some strings are impossible to translate in-context, e.g. the contents of the <title> tag in websites and strings with placeables or different plural forms. By clicking on the hamburger icon in the main toolbar, a list of all strings and available translations will open in the sidebar. You can also use the sidebar for out-of-context localization:</p> + +<p><img alt="Out-of-context localization: list" src="https://mdn.mozillademos.org/files/8337/out-of-context-1.png"> <img alt="Out-of-context localization: translate" src="https://mdn.mozillademos.org/files/8335/out-of-context-2.png"></p> + +<ol> + <li>Click on the string you'd like to translate.</li> + <li>Translation panel with original string and its details (e.g. comments) opens.</li> + <li>Translate the string in the translation area below.</li> + <li>Click the save button to save your translation.</li> +</ol> + +<p>As you translate strings out-of-context, translations will also appear in website, if they could also be translated in-context.</p> + +<h3 id="Ajudas_de_tradução">Ajudas de tradução</h3> +</div> + +<p>As you can see, suggestions from history, translation memory, machine translation and other locales are also available in the out-of-context translation panel. We call all of these translation helpers and here's how each of them will help you as you translate strings:</p> + +<p><img alt="Translation helpers: History" src="https://mdn.mozillademos.org/files/8339/helpers-history.png"> <img alt="Translation helpers: Machinery" src="https://mdn.mozillademos.org/files/8341/helpers-machinery.png"> <img alt="Translation helpers: Other locales" src="https://mdn.mozillademos.org/files/8343/helpers-locales.png"> <img alt="Translation helpers: Search" src="https://mdn.mozillademos.org/files/8345/helpers-menu.png"></p> + +<h4 id="Histórico">Histórico</h4> + +<p>Displays previously suggested translations, including from other users.</p> + +<h4 id="Máquina">Máquina</h4> + +<p>Displays matches from various services: internal translation memory, <a href="http://transvision.mozfr.org/">Mozilla Transvision</a>, <a href="https://amagama-live.translatehouse.org/">open source translation memory</a>, <a href="http://www.microsoft.com/Language/">Microsoft terminology</a> and <a href="http://www.bing.com/translator">machine translation</a>.</p> + +<h4 id="Outros_idiomas">Outros idiomas</h4> + +<p>Displays matching translations from other locales.</p> + +<h4 id="Pesquisar">Pesquisar</h4> + +<p>Almost like machinery, but takes provided keyword as input parameter instead of the original string.</p> + +<p>By clicking a suggestion, it gets copied into translation area.</p> + +<dl> +</dl> + +<h2 id="Publicar_a_sua_localização">Publicar a sua localização</h2> + +<p>Suppose you now want to publish your l10n work by committing it to a repo. Pontoon lets you do that too! Actually, it does that for you by automatically syncing with repositories on hourly basis. You can now pat yourself on the back, do a little dance, go to sleep or do something else to celebrate your work!</p> |