The translation is temporarily closed for contributions due to maintenance, please come back later.

Translation

Put one translator per line, in the form NAME <EMAIL>, YEAR1, YEAR2
_
English
translator-credits
235/1000 · 18
Context English Portuguese (Brazil) State
_ translator-credits Edson Brandi, ebrandi@FreeBSD.org, 2018
Lucas Andrade, slucasandrade@protonmail.ch, 2018
Mauro Risonho de Paula Assumpção, mauro.risonho@gmail.com, 2018
André Franciosi, andre@franciosi.org, 2018
Danilo G. Baio, dbaio@FreeBSD.org, 2018
Practical rc.d scripting in BSD Scripts rc.d práticos no BSD
<email>yar@FreeBSD.org</email> <email>yar@FreeBSD.org</email>
<personname><firstname>Yar</firstname><surname>Tikhiy</surname></personname><affiliation> <_:address-1/> </affiliation> <personname><firstname>Yar</firstname><surname>Tikhiy</surname></personname><affiliation> <_:address-1/> </affiliation>
<year>2005</year> <year>2006</year> <year>2012</year> <holder>The FreeBSD Project</holder> <year>2005</year> <year>2006</year> <year>2012</year> <holder>The FreeBSD Project</holder>
FreeBSD is a registered trademark of the FreeBSD Foundation. FreeBSD is a registered trademark of the FreeBSD Foundation.
NetBSD is a registered trademark of the NetBSD Foundation. NetBSD is a registered trademark of the NetBSD Foundation.
Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this document, and the FreeBSD Project was aware of the trademark claim, the designations have been followed by the <quote>™</quote> or the <quote>®</quote> symbol. Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this document, and the FreeBSD Project was aware of the trademark claim, the designations have been followed by the <quote>™</quote> or the <quote>®</quote> symbol.
$FreeBSD: head/en_US.ISO8859-1/articles/rc-scripting/article.xml 44709 2014-04-29 21:39:27Z wblock $ $FreeBSD: head/pt_BR.ISO8859-1/articles/rc-scripting/pt_BR.po 52247 2018-09-12 00:52:17Z ebrandi $
Beginners may find it difficult to relate the facts from the formal documentation on the BSD <filename>rc.d</filename> framework with the practical tasks of <filename>rc.d</filename> scripting. In this article, we consider a few typical cases of increasing complexity, show <filename>rc.d</filename> features suited for each case, and discuss how they work. Such an examination should provide reference points for further study of the design and efficient application of <filename>rc.d</filename>. Os iniciantes podem achar difícil relacionar os fatos da documentação formal do framework <filename>rc.d</filename> do BSD com as tarefas práticas do script <filename>rc.d</filename>. Neste artigo, consideramos alguns casos típicos de complexidade crescente, vamos mostrar os recursos do <filename>rc.d</filename> adequados para cada caso e vamos discutir como eles funcionam. Esse exame deve fornecer pontos de referência para um estudo mais aprofundado do design e da aplicação eficiente do <filename>rc.d</filename>.
Introduction Introdução
The historical BSD had a monolithic startup script, <filename>/etc/rc</filename>. It was invoked by <citerefentry><refentrytitle>init</refentrytitle><manvolnum>8</manvolnum></citerefentry> at system boot time and performed all userland tasks required for multi-user operation: checking and mounting file systems, setting up the network, starting daemons, and so on. The precise list of tasks was not the same in every system; admins needed to customize it. With few exceptions, <filename>/etc/rc</filename> had to be modified, and true hackers liked it. Historicamente o BSD tinha um script de inicialização monolítico, o <filename>/etc/rc</filename>. Ele era chamado pelo <citerefentry><refentrytitle>init</refentrytitle><manvolnum> 8</manvolnum></citerefentry> no momento da inicialização do sistema e executava todas as tarefas necessárias para a operação multi-usuário: verificação e montagem do sistemas de arquivos, configuração de rede, iniciava daemons e assim por diante. A lista precisa de tarefas não era a mesma em todos os sistemas; os administradores precisavam personalizá-lo. Com poucas exceções, o <filename>/etc/rc</filename> teve que ser modificado, e os verdadeiros hackers gostaram disso.
The real problem with the monolithic approach was that it provided no control over the individual components started from <filename>/etc/rc</filename>. For instance, <filename>/etc/rc</filename> could not restart a single daemon. The system admin had to find the daemon process by hand, kill it, wait until it actually exited, then browse through <filename>/etc/rc</filename> for the flags, and finally type the full command line to start the daemon again. The task would become even more difficult and prone to errors if the service to restart consisted of more than one daemon or demanded additional actions. In a few words, the single script failed to fulfil what scripts are for: to make the system admin's life easier. O problema real com a abordagem monolítica era que ela não fornecia nenhum controle sobre os componentes individuais iniciados a partir do <filename>/etc/rc</filename>. Por exemplo, o <filename>/etc/rc</filename> não podia reiniciar um único daemon. O administrador do sistema tinha que encontrar o processo daemon manualmente, matá-lo, esperar até que ele realmente finalizasse, então procurar pelas flags no <filename>/etc/rc</filename>, e finalmente digitar a linha de comando completa para iniciar o daemon novamente. A tarefa se tornaria ainda mais difícil e propensa a erros se o serviço de reinicialização consistisse em mais de um daemon ou exigisse ações adicionais. Em poucas palavras, o único script não cumpriu o objetivo dos scripts: tornar a vida do administrador do sistema mais fácil.
Later there was an attempt to split out some parts of <filename>/etc/rc</filename> for the sake of starting the most important subsystems separately. The notorious example was <filename>/etc/netstart</filename> to bring up networking. It did allow for accessing the network from single-user mode, but it did not integrate well into the automatic startup process because parts of its code needed to interleave with actions essentially unrelated to networking. That was why <filename>/etc/netstart</filename> mutated into <filename>/etc/rc.network</filename>. The latter was no longer an ordinary script; it comprised of large, tangled <citerefentry><refentrytitle>sh</refentrytitle><manvolnum>1</manvolnum></citerefentry> functions called from <filename>/etc/rc</filename> at different stages of system startup. However, as the startup tasks grew diverse and sophisticated, the <quote>quasi-modular</quote> approach became even more of a drag than the monolithic <filename>/etc/rc</filename> had been. Mais tarde, houve uma tentativa de dividir algumas partes do <filename>/etc/rc</filename> para iniciar os subsistemas mais importantes separadamente. O exemplo notório foi o <filename>/etc/netstart</filename> para configurar a rede. Ele permitia acessar a rede a partir do modo single-user, mas não se integrou bem ao processo de inicialização automática porque partes de seu código precisavam intercalar com ações essencialmente não relacionadas à rede. Foi por isso que o <filename>/etc/netstart</filename> mudou para <filename>/etc/rc.network</filename>. Este último não era mais um script comum; ele era composto por um emaranhado de funções <citerefentry><refentrytitle>sh</refentrytitle><manvolnum>1</manvolnum></citerefentry> chamadas pelo <filename>/etc/rc</filename> em diferentes estágios da inicialização do sistema. No entanto, a medida que as tarefas de inicialização cresciam variadas e sofisticadas, a abordagem <quote>quase modular</quote> tornou-se ainda mais engessada do que o monolítico <filename>/etc/rc</filename>.
Without a clean and well-designed framework, the startup scripts had to bend over backwards to satisfy the needs of rapidly developing BSD-based operating systems. It became obvious at last that more steps are necessary on the way to a fine-grained and extensible <filename>rc</filename> system. Thus BSD <filename>rc.d</filename> was born. Its acknowledged fathers were Luke Mewburn and the NetBSD community. Later it was imported into FreeBSD. Its name refers to the location of system scripts for individual services, which is in <filename>/etc/rc.d</filename>. Soon we will learn about more components of the <filename>rc.d</filename> system and see how the individual scripts are invoked. Sem um framework limpo e bem projetado, os scripts de inicialização tiveram que se curvar para satisfazer as necessidades de desenvolvimento rápido dos sistemas operacionais baseados no BSD. Tornou-se óbvio, finalmente, que mais passos eram necessários no caminho para construção de um sistema <filename>rc</filename> extensível e customizável. Assim nasceu o BSD <filename>rc.d</filename>. Seus pais reconhecidos foram o Luke Mewburn e a comunidade do NetBSD. Mais tarde ele foi importado para o FreeBSD. Seu nome se refere à localização dos scripts do sistema para serviços individuais, que é o <filename>/etc/rc.d</filename>. Em breve, vamos aprender sobre mais componentes do sistema <filename>rc.d</filename> e vamos ver como os scripts individuais são invocados.
The basic ideas behind BSD <filename>rc.d</filename> are <emphasis>fine modularity</emphasis> and <emphasis>code reuse</emphasis>. <emphasis>Fine modularity</emphasis> means that each basic <quote>service</quote> such as a system daemon or primitive startup task gets its own <citerefentry><refentrytitle>sh</refentrytitle><manvolnum>1</manvolnum></citerefentry> script able to start the service, stop it, reload it, check its status. A particular action is chosen by the command-line argument to the script. The <filename>/etc/rc</filename> script still drives system startup, but now it merely invokes the smaller scripts one by one with the <option>start</option> argument. It is easy to perform shutdown tasks as well by running the same set of scripts with the <option>stop</option> argument, which is done by <filename>/etc/rc.shutdown</filename>. Note how closely this follows the Unix way of having a set of small specialized tools, each fulfilling its task as well as possible. <emphasis>Code reuse</emphasis> means that common operations are implemented as <citerefentry><refentrytitle>sh</refentrytitle><manvolnum>1</manvolnum></citerefentry> functions and collected in <filename>/etc/rc.subr</filename>. Now a typical script can be just a few lines' worth of <citerefentry><refentrytitle>sh</refentrytitle><manvolnum>1</manvolnum></citerefentry> code. Finally, an important part of the <filename>rc.d</filename> framework is <citerefentry><refentrytitle>rcorder</refentrytitle><manvolnum>8</manvolnum></citerefentry>, which helps <filename>/etc/rc</filename> to run the small scripts orderly with respect to dependencies between them. It can help <filename>/etc/rc.shutdown</filename>, too, because the proper order for the shutdown sequence is opposite to that of startup. As idéias básicas por trás do BSD <filename>rc.d</filename> são <emphasis>modularidade fina</emphasis> e <emphasis>reutilização de código</emphasis>. <emphasis>Modularidade fina</emphasis> significa que cada <quote>serviço básico</quote>, como um daemon do sistema ou uma tarefa de inicialização primitiva, obtém seu próprio script <citerefentry><refentrytitle>sh</refentrytitle> <manvolnum></manvolnum></citerefentry> capaz de iniciar o serviço, pará-lo, recarregá-lo e verificar seu status. Uma ação específica é escolhida pelo argumento da linha de comando para o script. O script <filename>/etc/rc</filename> ainda comanda a inicialização do sistema, mas agora ele simplesmente invoca os scripts menores um por um com o argumento <option>start</option>. É fácil executar tarefas de desligamento executando o mesmo conjunto de scripts com o argumento <option>stop</option>, o que é feito pelo <filename>/etc/rc.shutdown</filename>. Observe como isso segue de perto o modo Unix de ter um conjunto de pequenas ferramentas especializadas, cada uma cumprindo sua tarefa da melhor forma possível. <emphasis>Reutilização de código</emphasis> significa que operações comuns são implementadas como funções <citerefentry><refentrytitle>sh</refentrytitle><manvolnum>1</manvolnum></citerefentry> e coletadas em <filename>/etc/rc.subr </filename>. Agora, um script típico pode conter apenas algumas linhas de código <citerefentry><refentrytitle>sh</refentrytitle><manvolnum>1</manvolnum> </citerefentry>. Finalmente, uma parte importante do framework do <filename>rc.d</filename> é <citerefentry> <refentrytitle>rcorder</refentrytitle> <manvolnum>8</manvolnum> </citerefentry>, o qual ajuda o <filename>/etc/rc</filename> a executar os pequenos scripts ordenadamente em relação às dependências entre eles. Ele também pode ajudar o <filename>/etc/rc.shutdown</filename>, porque a ordem apropriada para a sequência de encerramento é oposta à da inicialização.

Showing only subset of the strings as there were too many matches.

Component Translation Difference to current string
The following strings have the same context and source.
Translated FreeBSD Doc/articles_serial-uart Edson Brandi, ebrandi@FreeBSD.org, 2018
Lucas Andrade, slucasandrade@protonmail.ch, 2018 Mauro Risonho de Paula Assumpção, mauro.risonho@gmail.com, 2018 André Franciosi, andre@franciosi.org, 2018 Danilo G. Baio, dbaio@FreeBSD.org, 2018
Translated FreeBSD Doc/articles_committers-guide Edson Brandi, ebrandi@FreeBSD.org, 2018 Lucas Andrade, slucasandrade@protonmail.ch, 2018 Mauro Risonho de Paula Assumpção, mauro.risonho@gmail.com, 2018 André Franciosi, andre@franciosi.orgAndré Franciosi, andre@franciosi.org, 2018
Edson Brandi, ebrandi@FreeBSD.org, 2018
Silvio Ap Silva, contato@kanazuchi.com, 2018
Danilo G. Baio, dbaio@FreeBSD.org, 2018-2020
Translated FreeBSD Doc/articles_explaining-bsd Edson Brandi, ebrandi@FreeBSD.org, 2018
Lucas Andrade, slucasandrade@protonmail.ch, 2018 Mauro Risonho de Paula Assumpção, mauro.risonho@gmail.com, 2018 André Franciosi, andre@franciosi.org, 2018 Danilo G. Baio, dbaio@FreeBSD.orgRafael Mentz Aquino, rafael@lk6.com.br, 2018
Translated FreeBSD Doc/articles_building-products Edson Brandi, ebrandi@FreeBSD.org, 2018 Lucas Andrade, slucasandrade@protonmail.ch, 2018 Mauro Risonho de Paula Assumpção, mauro.risonho@gmail.com, 2018 André Franciosi, andre@franciosi.org, 2018 Danilo G. Baio, dbaio@FreeBSD.org, 2018translator-credits
Translated FreeBSD Doc/articles_contributing Edson Brandi, ebrandi@FreeBSD.org, 2018 Lucas Andrade, slucasandrade@protonmail.ch, 2018 Mauro Risonho de Paula Assumpção, mauro.risonho@gmail.com, 2018 André Franciosi, andre@franciosi.org, 2018 Danilo G. Baio, dbaioAlexandre Vasconcelos, alex.vasconcelos@gmail.com, 2018
Edson Brandi, ebrandi@FreeBSD.org, 2018
Translated FreeBSD Doc/articles_contributors Edson Brandi, ebrandi@FreeBSD.org, 2018 Lucas Andrade, slucasandrade@protonmail.ch, 2018 Mauro Risonho de Paula Assumpção, mauro.risonhoGabriel Rizzo, gabriel96.gsr@gmail.com, 2018
André Franciosi, andre@franciosi.org, 2018
Danilo G. Baio, dbaio@FreeBSD.org, 2018-2020
Edson Brandi, ebrandi@FreeBSD.org, 2018
Lucas Andrade, slucasandrade@protonmail.ch, 2018
Translated FreeBSD Doc/articles_freebsd-questions Edson Brandi, ebrandi@FreeBSD.org, 2018 Lucas Andrade, slucasandrade@protonmail.ch, 2018 Mauro Risonho de Paula Assumpção, mauro.risonho@gmail.com, 2018 André Franciosi, andre@franciosi.org, 2018 Danilo G. Baio, dbaio@FreeBSD.org, 2018
Translated FreeBSD Doc/articles_geom-class Edson Brandi, ebrandi@FreeBSD.org, 2018
Lucas Andrade, slucasandrade@protonmail.ch, 2018 Mauro Risonho de Paula Assumpção, mauro.risonho@gmail.com, 2018 André Franciosi, andre@franciosi.org, 2018 Danilo G. Baio, dbaio@FreeBSD.org, 2018
Translated FreeBSD Doc/articles_ipsec-must Edson Brandi, ebrandi@FreeBSD.org, 2018
Lucas Andrade, slucasandrade@protonmail.ch, 2018 Mauro Risonho de Paula Assumpção, mauro.risonho@gmail.com, 2018 André Franciosi, andre@franciosi.org, 2018 Danilo G. Baio, dbaio@FreeBSD.org, 2018
Translated FreeBSD Doc/articles_mailing-list-faq Edson Brandi, ebrandi@FreeBSD.org, 2018 Lucas Andrade, slucasandrade@protonmail.ch, 2018 Mauro Risonho de Paula Assumpção, mauro.risonho@gmail.com, 2018 André Franciosi, andre@franciosi.org, 2018 Danilo G. Baio, dbaio@FreeBSD.orgAlexandre Vasconcelos, alex.vasconcelos@gmail.com, 2018
Edson Brandi, ebrandi@FreeBSD.org, 2018
Mauro Risonho de Paula Assumpção, mauro.risonho@gmail.com, 2018
Translated FreeBSD Doc/articles_gjournal-desktop Edson Brandi, ebrandi@FreeBSD.org, 2018
Lucas Andrade, slucasandrade@protonmail.ch, 2018 Mauro Risonho de Paula Assumpção, mauro.risonho@gmail.com, 2018 André Franciosi, andre@franciosi.org, 2018 Danilo G. Baio, dbaio@FreeBSD.org, 2018
Translated FreeBSD Doc/articles_ldap-auth Edson Brandi, ebrandi@FreeBSD.org, 2018
Lucas Andrade, slucasandrade@protonmail.ch, 2018 Mauro Risonho de Paula Assumpção, mauro.risonho@gmail.com, 2018 André Franciosi, andre@franciosi.orgKanazuchi, contato@kanazuchi.com, 2018
Danilo G. Baio, dbaio@FreeBSD.org, 2018
Translated FreeBSD Doc/articles_pgpkeys Edson Brandi, ebrandi@FreeBSD.org, 2018 Lucas Andrade, slucasandrade@protonmail.ch, 2018 Mauro Risonho de Paula Assumpção, mauro.risonho@gmail.com, 2018 André Franciosi, andre@franciosi.org, 2018 Danilo G. Baio, dbaioDanilo G. Baio, dbaio@FreeBSD.org, 2018
Edson Brandi, ebrandi@FreeBSD.org, 2018
Translated FreeBSD Doc/articles_leap-seconds Edson Brandi, ebrandi@FreeBSD.org, 2018 Lucas Andrade, slucasandrade@protonmail.ch, 2018 Mauro Risonho de Paula Assumpção, mauro.risonho@gmail.com, 2018 André Franciosi, andre@franciosiNilton José Rizzo, rizzo@rizzo.eng.br, 2018
Edson Brandi, ebrandi@FreeBSD.org, 2018
Danilo G. Baio, dbaio@FreeBSD.org, 2018
Translated FreeBSD Doc/articles_linux-users Edson Brandi, ebrandi@FreeBSD.org, 2018 Lucas Andrade, slucasandrade@protonmail.ch, 2018 Mauro Risonho de Paula Assumpção, mauro.risonho@gmail.com, 2018 André Franciosi, andre@franciosiNilton José Rizzo, rizzo@rizzo.eng.br, 2018
Edson Brandi, ebrandi@FreeBSD.org, 2018
Danilo G. Baio, dbaio@FreeBSD.org, 2018
Translated FreeBSD Doc/articles_linux-emulation Edson Brandi, ebrandi@FreeBSD.org, 2018
Lucas Andrade, slucasandrade@protonmail.ch, 2018 Mauro Risonho de Paula Assumpção, mauro.risonho@gmail.com, 2018 André Franciosi, andre@franciosi.orgKanazuchi, contato@kanazuchi.com, 2018
Danilo G. Baio, dbaio@FreeBSD.org, 2018
Translated FreeBSD Doc/articles_freebsd-releng Edson Brandi, ebrandi@FreeBSD.org, 2018
Lucas Andrade, slucasandrade@protonmail.ch, 2018
Mauro Risonho de Paula Assumpção, mauro.risonho@gmail.com, 2018 André Franciosi, andre@franciosi.orgAndré Franciosi, andre@franciosi.org, 2018
Vinícius Zavam, egypcio@googlemail.com, 2018
Silvio Ap Silva, contato@kanazuchi.com, 2018
Danilo G. Baio, dbaio@FreeBSD.org, 201820
Translated FreeBSD Doc/articles_port-mentor-guidelines Edson Brandi, ebrandi@FreeBSD.org, 2018
Lucas Andrade, slucasandrade@protonmail.ch, 2018 Mauro Risonho de Paula Assumpção, mauro.risonho@gmail.com, 2018
André Franciosi, andre@franciosi.org, 2018 Danilo G. Baio, dbaio@FreeBSD.org, 2018
Translated FreeBSD Doc/articles_vinum Edson Brandi, ebrandi@FreeBSD.org, 2018
Danilo G. Baio, dbaio@FreeBSD.org, 2018
Lucas Andrade, slucasandrade@protonmail.ch, 2018 Mauro Risonho de Paula Assumpção, mauro.risonho@gmail.com, 2018 André Franciosi, andre@franciosi.org, 2018 Danilo G. Baio, dbaio@FreeBSD.org, 2018
Translated FreeBSD Doc/articles_cups Edson Brandi, ebrandi@FreeBSD.org, 2018 Lucas Andrade, slucasandrade@protonmail.ch, 2018 Mauro Risonho de Paula Assumpção, mauro.risonho@gmail.com, 2018 André Franciosi, andre@franciosiWendell Borges, perlporter@gmail.com, 2018
Edson Brandi, ebrandi@FreeBSD.org, 2018
Danilo G. Baio, dbaio@FreeBSD.org, 2018

Loading…

User avatar dbaio

Translation changed

FreeBSD Doc / articles_rc-scripting — Portuguese (Brazil)

translator-credits
translator-creditsEdson Brandi, ebrandi@FreeBSD.org, 2018
Lucas Andrade, slucasandrade@protonmail.ch, 2018
Mauro Risonho de Paula Assumpção, mauro.risonho@gmail.com, 2018
André Franciosi, andre@franciosi.org, 2018
Danilo G. Baio, dbaio@FreeBSD.org, 2018
a year ago
User avatar dbaio

Translation changed

FreeBSD Doc / articles_rc-scripting — Portuguese (Brazil)

translator-credits
Edson Brandi, ebrandi@FreeBSD.org, 2018translator-credits
a year ago
User avatar dbaio

Translation changed

FreeBSD Doc / articles_rc-scripting — Portuguese (Brazil)

translator-credits
Rafael Mentz Aquino, rafael@lk6.com.br, 2018 Edson Brandi, ebrandi@FreeBSD.org, 2018 Danilo G. Baio, dbaioEdson Brandi, ebrandi@FreeBSD.org, 2018
a year ago
User avatar dbaio

Translation changed

FreeBSD Doc / articles_rc-scripting — Portuguese (Brazil)

translator-credits
Edson Brandi, ebrandiRafael Mentz Aquino, rafael@lk6.com.br, 2018
Edson Brandi, ebrandi@FreeBSD.org, 2018
Danilo G. Baio, dbaio@FreeBSD.org, 2018
a year ago
User avatar dbaio

Translation reverted

FreeBSD Doc / articles_rc-scripting — Portuguese (Brazil)

translator-credits
Rafael Mentz Aquino, rafael@lk6.com.br, 2018 Edson Brandi, ebrandi@FreeBSD.org, 2018 Danilo G. Baio, dbaioEdson Brandi, ebrandi@FreeBSD.org, 2018
a year ago
User avatar dbaio

Translation reverted

FreeBSD Doc / articles_rc-scripting — Portuguese (Brazil)

translator-credits
translator-creditsRafael Mentz Aquino, rafael@lk6.com.br, 2018
Edson Brandi, ebrandi@FreeBSD.org, 2018
Danilo G. Baio, dbaio@FreeBSD.org, 2018
a year ago
User avatar ebrandi

Translation changed

FreeBSD Doc / articles_rc-scripting — Portuguese (Brazil)

translator-credits
translator-credits
a year ago
User avatar ebrandi

Translation changed

FreeBSD Doc / articles_rc-scripting — Portuguese (Brazil)

translator-credits
translator-credits
a year ago
User avatar ebrandi

Translation changed

FreeBSD Doc / articles_rc-scripting — Portuguese (Brazil)

translator-credits
Edson Brandi, ebrandi@FreeBSD.org, 2018 Lucas Andrade, slucasandrade@protonmail.ch, 2018 Mauro Risonho de Paula Assumpção, mauro.risonho@gmail.com, 2018 André Franciosi, andre@franciosi.org, 2018 Danilo G. Baio, dbaio@FreeBSD.org, 2018translator-credits
a year ago
User avatar ebrandi

New contributor

FreeBSD Doc / articles_rc-scripting — Portuguese (Brazil)

New contributor a year ago
Browse all component changes

Things to check

Mismatching line breaks

Number of new lines in translation does not match source

Reset

Glossary

English Portuguese (Brazil)
No related strings found in the glossary.

Source information

Context
_
Source string comment
Put one translator per line, in the form NAME <EMAIL>, YEAR1, YEAR2
Flags
max-length:1000
String age
a year ago
Source string age
a year ago
Translation file
articles/pt_BR/rc-scripting.po, string 1