Hi,
sajolida@??? wrote (13 Jan 2013 21:50:50 GMT) :
> 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.
Let's ignore it as well. I guess you'll want to add it to check_po.sh?
>> What about adding a script to l10n_tricks that would e.g. be called
>> `check_po [LANGUAGE]' [...]
> Done, see a61b2f6..6080819.
Awesome. I've pushed some (untested) minor improvements on top of
that. Tell me I suck if I broke anything -- sorry.
>> 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
I did that:
de100f0 -- Add step to check PO files with i18nspector to the bundled
Debian packages release process.
For automation at build time, we have to wait until Tails is based on
Wheezy and i18nspector is in wheezy-backports, else it would be too
painful to maintain pbuilder chroots with i18nspector available.
I'm not sure it's worth a ticket (if we had a better task manager, and
a way to set things to a very low priority, I would create it, but
well...)
>> * 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.
Hmm, with a tiny bit of guidance, you sure do know how to do the
latter :) It's basically the same as check_po.sh, modulo:
* PO files are to be found in
config/chroot_local-includes/usr/share/locale/
* the call to check_po.sh or i18nspector should be added to
auto/build, e.g. right after the call to ./refresh-translations
Want to give it a try?
Cheers,
--
intrigeri
| GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc
| OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc
