> > workaraound: re-encode files in UTF-8 but that's not exactly > > satisfying in the long term. It will take ages before > > we enforce UTF-8 on all Debian l10n teams (why would > > we?) > > Because it's the standard? :)
No more no less than anything less. Even though I perfectly agree that it sets up a common ground, having software that only supports UTF-8 encoding is too much restriction. gettext is designed for being able to hadle various encodings and gettext-aware software should handle these encodings gracefully..:) > > expected fix: have the Tookit *ignore* invalid files and Pootle > > continue the import/indexing > > Or we could have an option: ignore invalid files, OR display an > interactive error. That would definitely be the best. I currently have to dig into the bunch of PO files to find the culprit. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Translate-pootle mailing list Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle
