improve template files for translators
The standard gettext library used to extract strings from PHP code generates a number of generic strings in resulting .po files.
This is visible from header of any .pot file in
Obviously, translators would benefit a lot from having real information instead of generic strings.
Therefore the requirement to include post-processing of .pot files in the building process.
More specifically, the
Submitted by fw_crocodile
This is visible from header of any .pot file in
i18n/templates directory:# SOME DESCRIPTIVE TITLE.
# Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER
# This file is distributed under the same license as the PACKAGE package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSIONn"
"Report-Msgid-Bugs-To: n"
"POT-Creation-Date: 2007-03-27 00:28+0200n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONEn"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>n"
"Language-Team: LANGUAGE <LL@li.org>n"
"MIME-Version: 1.0n"
"Content-Type: text/plain; charset=CHARSETn"
"Content-Transfer-Encoding: 8bitn"
"Plural-Forms: nplurals=INTEGER; plural=EXPRESSION;n"
Obviously, translators would benefit a lot from having real information instead of generic strings.
Therefore the requirement to include post-processing of .pot files in the building process.
More specifically, the
scripts/build.php would have to scan the directory scripts/reference/i18n/templates, and to update every .pot file found there, before packaging the full set of reference files.Submitted by fw_crocodile