po4a/po4a-doc — Polish @ Hosted Weblate: [type: man] man/foo.1 $lang:man/translated/foo.$lang.1

Translation

Source change

English type: verbatim

Polish

Needs editing

Skip

	English	Polish	Actions
	It is time to convert your documentation to B<po4a> to solve your documentation maintenance nightmares. You want to update the doc when needed, you want to ease the work of your fellow translators, and you want to ensure that your users never see any outdated and thus misleading documentation.
	The conversion includes two steps: setup the po4a infrastructure, and convert the previous German translation to salvage the previous work. This latter part is done using S<po4a-gettextize>, as follows. As detailed in the documentation of L<po4a-gettextize(1)>, this process rarely fully automatic, but once it's done, the B<de.po> file containing the German translation can be integrated in your po4a workflow.
	po4a-gettextize --format man --master foo.1 --localized foo.de.1 --po de.po	$ po4a-gettextize -f <format> -m <master.doc> -p <tłumaczenie.pot>
	Let's now configure po4a. With the appropriate file layout, your configuration file could be as simple as this:
	[po_directory] man/po4a/	[po_directory] man/po4a/po/
	[type: man] man/foo.1 $lang:man/translated/foo.$lang.1	[type: man] man/foo.1 $lang:man/translated/$lang/foo.1 \ add_$lang:?man/po4a/add_$lang/$lang.add opt:"-k 80"
	It specifies that all PO files (containing the work of the translators) are in the F<man/po4a/> directory, and that you have only one master file, F<man/foo.1>. If you had several master files, you would have several lines similar to the second one. Each such line also specify where to write the corresponding translation files. Here, the German translation of F<man/foo.1> is in F<man/translated/foo.de.1>.
	The last thing we need to complete the configuration of B<po4a> is a POT file containing the template material that should be used to start a new translation. Simply create an empty file with the S<.pot> extension in the specified S<po_directory> (e.g. F<man/po4a/foo.pot>), and B<po4a> will fill it with the expected content.
	Here is a recap of the files in this setup:	Graficzna reprezentacja tego procesu:
	├── man/ │ ├── foo.1 <- The original man page, in English │ ├── po4a/ │ │ ├── de.po <- The German PO translation, from gettextization │ │ └── foo.pot <- The POT template of future translations (empty at first) │ └── translated/ <- Directory where the translations will be created └── po4a.cfg <- The configuration file
	Once setup, executing B<po4a> will parse your documentation, update the POT template file, use it to update the PO translation files, and use them to update the documentation translation files. All in one command:

Loading…

None

String updated in the repository

English

Polish 123 characters edited Current translation Needs editing

a year ago

None

Source string changed

English 67 characters edited

a year ago

Browse all string changes

Things to check

Double space

Translation contains double space

Fix string

Reset

Mismatching line breaks

Number of new lines in translation does not match source

Reset

Glossary

English	Polish
foo		po4a Glossary
foo is an english word that means nothing, it's only good to hold the place. See https://en.wikipedia.org/wiki/Foobar

String information

Source string description

type: verbatim

Flags

no-wrap

Source string location

po4a:20

String age

a year ago

Last updated

11 months ago

Source string age

a year ago

Translation file

po/pod/pl.po, string 53