diff options
Diffstat (limited to 'files/pt-pt/mozilla/localization/guia_iniciação_rápida')
5 files changed, 631 insertions, 0 deletions
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> |