> # > # Translators, if you are not familiar with the PO format, gettext > # documentation is worth reading, especially sections dedicated to > # this format, e.g. by running: > # info -n '(gettext)PO Files' > # info -n '(gettext)Header Entry' > # > # Some information specific to po-debconf are available at > # /usr/share/doc/po-debconf/README-trans > # or http://www.debian.org/intl/l10n/po-debconf/README-trans > # > # Developers do not need to manually edit POT or PO files. > # > #, fuzzy > msgid "" > msgstr "" > "Project-Id-Version: PACKAGE VERSION\n" > "Report-Msgid-Bugs-To: \n" > "POT-Creation-Date: 2004-10-23 11:32+0200\n" > "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" > "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" > "Language-Team: LANGUAGE <LL@li.org>\n" > "MIME-Version: 1.0\n" > "Content-Type: text/plain; charset=CHARSET\n" > "Content-Transfer-Encoding: 8bit\n" Better. But in the future, please ask translators, or yourself, to fill these fields in, with the appropriate information..:-) A PO file header should NOT be fuzzy....it iusually indicates a lack of filling the header. PS: using "msgfmt -c -o /dev/null <file>" will warn you about such errors and I recommend all translators to use this before sending a new file or an update.
Attachment:
signature.asc
Description: Digital signature