I manage the Spanish translation using -po files, one per array (pgv_lang, factarray, countries, etc.) These are the scripts I use:
pgvxgettext traverses the source code and extracts translation keys generating what amounts to a skeleton po template file containing source cross references that are useful during translation. This process is fragile and will both fail to detect some references and match at spurious places. This problem cannot be solved without chamges to the PGV source code.
pgv2po takes a set of translation files and creates a .po file that can be msgmerge'd with the template file to add source cross references.
po2pgv takes a .po file, a source language file and produces a target language file as a copy of the source language file with all strings replaced by those in the .po file
lanza.pgv2po and lanza.po2pgv are sample shell scripts that use the above building blocks.
Log in to post a comment.