File HOWTO of Package gnome-patch-translation

Overview Repositories Revisions Requests Users Attributes Meta

File HOWTO of Package gnome-patch-translation (Revision 6f8ae2b85c69e1c4e4ae6365de801e17)

Currently displaying revision 6f8ae2b85c69e1c4e4ae6365de801e17 , Show latest

scripts for gnome-patch-translation maintainers
===============================================

HOW TO UPDATE TRANSLATIONS

Scripts for gnome-patch-translation package maintainers are intended to
update package from forge, then update translations from latest package
shapshots and then merge them back to forge.

Note that in difference to all other packages, gnome-patch-translation
provides fuzzy strings from upstream translations not present in the po
file.

These scripts are intended to be started from inside directory
containing unpacked sources of gnome-patch-translation. Please also see
HOWTO in gnome-patch-translation sources.

Run scripts in following order:

./update-step1-update-translations-from-lcn (calls gnome-patch-translation-from-forge):

Collects translations from LCN and updates gnome-patch-translation.tar.bz2.

./update-step2-update-strings-from-packages (calls gnome-patch-translation-collect):

Collects strings in patches.

You need following special tools: osc svn

Note: These tools work on packages already submitted and accepted into
defined repository. If you want to use more fresh copy of your package,
you can use a simple trick: When package is checked out (during
update-step2-update-strings-from-packages) and before the source is
unpacked, pause tool running by Ctrl+S. Then replace the source
directory with a directory you want to use in an another terminal.
Return back, press Ctrl+Q and the tool will continue with sources you
need.

./update-step3-upload-strings-to-lcn (calls gnome-patch-translation-to-forge):

Picks updated translations and fuzzy files and puts them back to forge.

After successful call please call

./update-step1-update-translations-from-lcn

once again.

If gnome-patch-translation-to-forge fails due to third party commits
during gnome-patch-translation-collect run, run script:

./update-solve-upload-conflict

Then you can continue with

./update-step3-upload-strings-to-lcn

gnome-patch-translation-from-forge:

You can optionally repeat its run to merge new strings to the package.
If you will not do it, next changelog checker will consider files as
changes and you will have to check manually, which changes were provided
by translators.

After using tools, submit updated packages!

DETAILS

Tools perform following steps for you:

1) Collect all files created by COMPENDIUM_UPDATE_MODE=1
gnome-patch-translation-update in all included packages. They are picked
by calling %prep phase of rpmbuild.

2) Use upper mentioned files to update
gnome-patch-translation-files.tar.bz2

3) Prepare this package (it is enough to unpack archives and call
"sh gnome-patch-translation-merge").

4a) If there is not yet any translation for particular language, pick
fuzzy po file from gnome-patch-translation-merged from build directory
and send it to translator for translation.

4b) If there is already a translation for particular language, pick
updated file from /usr/share/gnome-patch-translation (resp.
gnome-patch-translation-merged) and send it to translator for update.

5) Put your new translation into gnome-patch-translation.tar.bz2

Places

File HOWTO of Package gnome-patch-translation (Revision 6f8ae2b85c69e1c4e4ae6365de801e17)

Places