On 03/01/13 16:52, intrigeri wrote:
> Hi,
>
> sajolida@??? wrote (03 Jan 2013 15:07:36 GMT) :
>> To copy and run it you need to do: [...]
>
> I've subscribed to the ITP bug, and will notice the list once it's
> available in Debian.
>
>> Running it on all our PO files
>
> I assume this was on the website source and perhaps on the PO files
> for custom programs that we have in Git. Or did this include our other
> custom bundled packages too?
>
>> and filtering unique messages returns the following set of messages:
>
>> invalid-content-transfer-encoding ENCODING => 8bit
>> syntax-error-in-po-file line 113
>
> For the website source, I believe we don't care about all error
> messages but these two ones, because I think the tools that currently
> process the website PO files simply don't care about other headers.
I have a doubt regarding the invalid-content-transfer-encoding error
which is triggered by lines such as "Content-Transfer-Encoding:
ENCODING" instead of "Content-Transfer-Encoding: 8bit". That said, 65 of
our PO files have that, so I wonder whether we should correct them all
or ignore that message as well.
>> Then if we think it's worth using i18nspector I can add it to
>> `/contribute/l10n_tricks` and help documenting the
>> interesting messages.
>
> I think it would be good to have our website clean wrt. these two
> kinds of errors.
>
> What about adding a script to l10n_tricks that would e.g. be called
> `check_po [LANGUAGE]' and run i18nspector on all PO files (restricted
> to the given language if specified), filtering out all errors we have
> decided we don't care about (starting with all you've listed by the
> two ones I'd rather not ignore, and adding to the list when needed in
> the future)?
>
> (I mean, that's probably low-priority, so if someone gets excited,
> excellent, else that's no big deal :)
Done, see a61b2f6..6080819.
> Aside of the website, we might want to be stricter about our other PO
> files, which are going to be processed by a large set of different
> tools, whom expectations I have no idea of; given we hardly test e.g.
> tails-persistence-setup in every supported language, i18nspector might
> help e.g. detect buggy PO files that could prevent the program to be
> translated at all. Perhaps a i18nspector pass could be added:
>
> * to the release process of each of our custom bundled programs,
> possibly as part of debian/rules for full automation
> * to the ISO build process, to catch errors in the PO files for our
> custom scripts
Those are things I don't know how to do. Shall I create a ticket as a
place to keep them?
