Standards for releasing software

Posted Oct 11, 2010 22:26 UTC (Mon) by man_ls (guest, #15091)
In reply to: Standards for releasing software by dwheeler
Parent article: Jaeger: systemd - and #osc2010

Very nice, thanks. I miss a similar standard for Python -- library management is a mess, setup.py sucks a bit, and internationalization has to be done manually.

Standards for releasing software

Posted Oct 12, 2010 14:09 UTC (Tue) by mpr22 (subscriber, #60784) [Link] (2 responses)

If you didn't think about i18n from day one when writing your program, it's always going to involve a lot of unpleasant drudgework to add it. Only static (or tersely technical, such that it doesn't matter if it looks like "computerspeak") communication to the user can reasonably be localized via the likes of gettext(); for everything else, you need code.

Standards for releasing software

Posted Oct 12, 2010 14:57 UTC (Tue) by man_ls (guest, #15091) [Link] (1 responses)

Sorry, I didn't explain myself. The actual process was more or less painless; using gettext is not so hard. But installing the translation files was a real pain -- there is no actual mechanism in Python. You have to find the target directory using gettext.bindtextdomain('yourpackage') and then copy the .mo files manually, keeping the right directory structure. Not pretty.

Standards for releasing software

Posted Oct 14, 2010 9:40 UTC (Thu) by mpr22 (subscriber, #60784) [Link]

OK, that makes sense. (Eww.)