Manpage translations in Makefiles
The translated manpage generation has moved from scripts to Makefiles. This asists with conditional building as well, no need to regenerate the German pgrep man page if both the original pgrep.1 and man-po/de.po is not changed. My Makefile-fu fails me on producing a cross-product or double iteration for languages and man pages. Until that is solved each man page is explicitly built. No big deal but it doesn't look elegant in the Makefile. Languages will be picked up automatically if they are found in man-po, man-po/top or man-po/ps The README describes the three-step process for translating the files, incase I forget or someone else wants to update them.
This commit is contained in:
19
README
19
README
@@ -43,6 +43,25 @@ PACKAGING
|
||||
For normal packages, ensure that you do not add debugging flags
|
||||
to the CFLAGS variable.
|
||||
|
||||
TRANSLATING MAN PAGES
|
||||
There is a three-step process for translating man pages. Most
|
||||
of the work happens in the man-po directory.
|
||||
|
||||
make -C man-po translate-templates
|
||||
Creates the translation templates (the .pot files) for translators
|
||||
to use as a base. These, along with the tar file, should be sent
|
||||
to the tp-coorindator before release.
|
||||
|
||||
make get-trans
|
||||
rsyncs the latest translated (.po) files for both the programs and
|
||||
man pages.
|
||||
|
||||
make -C man-po translate-mans
|
||||
This is also called in the dist-hook and is where the translation
|
||||
magic happens. Take the original man page, the relevant .po file
|
||||
and produce a translated man page in that language.
|
||||
All of the man pages generated are found in
|
||||
man-po/(LANG)/man(SECTION)/
|
||||
UPSTREAM & BUG REPORTS
|
||||
|
||||
procps-ng <procps@freelists.org>
|
||||
|
Reference in New Issue
Block a user