po4a/po4a-doc — Portuguese @ Hosted Weblate: master documents ---+---->-------->---------+ (doc authoring) |

Translation

Source change

English type: verbatim

Portuguese

Needs editing

Skip

	English	Portuguese	Actions
	SYNOPSIS	SINOPSE
	B<po4a> [I<options>] I<config_file>	B<po4a> [I<options>] I<config_file>
	po4a (PO for anything) eases the maintenance of documentation translation using the classical gettext tools. The main feature of po4a is that it decouples the translation of content from its document structure. Please refer to the page L<po4a(7)> for a gentle introduction to this project.	po4a (PO for anything) facilita a manutenção de tradução da documentação a usar as ferramentas clássicas do gettext. A característica principal do po4a é que ele dissocia a tradução do conteúdo da estrutura documental. Consulte a página L<po4a(7)> para uma introdução suave a este projeto.
	Upon execution, B<po4a> parses all documentation files specified in its configuration file. It updates the PO files (containing the translation) to reflect any change to the documentation, and produce a translated documentation by injecting the content's translation (found in the PO files) into the structure of the original master document.	Quando executa o programa B<po4a> com os documentos mestre e os ficheiros PO, ele produz os documentos traduzidos a injetar a tradução do conteúdo (encontrada nos ficheiros PO) na estrutura do documento mestre original.
	At first, the PO files only contain the strings to translate from the original documentation. This file format allows the translators to manually provide a translation for each paragraph extracted by B<po4a>. If the documentation is modified after translation, B<po4a> marks the corresponding translations as "fuzzy" in the PO file to request a manual review by the translators. The translators can also provide so-called "addendum", that are extra content stating for example who did the translation and how to report bugs.
	master documents ---+---->-------->---------+ (doc authoring) \| \| V (po4a executions) >-----+--> translated \| \| \| documents existing PO files -->--> updated PO files >-+ \| ^ \| \| \| V \| +----------<---------<-------+ ^ (manual translation process) \| \| addendum -->--------------------------------------+	documentos mestres -+----->-------->---------+ (autoria de docs) \| \| V (execuções do po4a) >----+--> traduções \| \| \| ficheiros PO ------->-----> ficheiros PO -->--+ \| existentes atualizados \| ^ \| \| \| V ^ +----------<---------<--------+ \| (processo de tradução manual) \| \| adendo ---->--------------------------------------+
	The workflow of B<po4a> is asynchronous, as suited to open-source projects. The documentation writers author the master documents at their own pace. The translators review and update the translations in the PO files. The maintainers rerun B<po4a> on need, to reflect any change to the original documentation to the PO files, and to produce updated documentation translations, by injecting the latest translation into the latest document structure.
	By default, a given translated document is produced when at least 80% of its content is translated. The untranslated text is kept in the original language. The produced documentation thus mixes languages if the translation is not complete. You can change the 80% threshold with the I<--keep> option described below. Note however that discarding translations as soon as they are not 100% may be discouraging for the translators whose work will almost never be shown to the users, while showing "translations" that are too incomplete may be troubling for the end users.	Por predefeinição, os documentos traduzidos são produzidos quando pelo menos 80% do conteúdo deles é traduzido (consulte a opção I<--keep> abaixo). Descartar traduções assim que elas não forem 100% pode ser desanimador para os tradutores, enquanto mostrar "tradução" muito incompletas pode ser preocupante para os utilizadores finais.
	Storing the translated documentation files in the version control system is probably a bad idea, since they are automatically generated. The precious files are the PO files, that contain the hard work of your fellow translators. Also, some people find it easier to interact with the translators through an online platform such as S<weblate>, but this is naturally fully optional.
	Quick start tutorial
	Let's assume you maintain a program named B<foo> which has a man page F<man/foo.1> written in English (the bridge language in most open-source projects, but B<po4a> can be used from or to any language). Some times ago, someone provided a German translation named F<man/foo.de.1> and disappeared. This is a problem because you just got a bug report saying that your documentation contains a gravely misleading information that must be fixed in all languages, but you don't speak German so you can only modify the original, not the translation. Now, another contributor wants to contribute a translation to Japanese, a language that you don't master either.

Loading…

None

String updated in the repository

English

Portuguese 642 characters edited Current translation Needs editing

a year ago

None

Source string changed

English 18 characters edited

a year ago

Browse all string changes

Things to check

Mismatching line breaks

Number of new lines in translation does not match source

Reset

Glossary

English	Portuguese
po4a		po4a Glossary
Software name

String information

Source string description

type: verbatim

Flags

no-wrap

Source string location

po4a:9

String age

a year ago

Last updated

11 months ago

Source string age

a year ago

Translation file

po/pod/pt.po, string 42