Hi, I'm trying to help Mark Ramm with i18n chapter for his book and would like to discuss some i18n issues.
1. I18N command dichotomy. In TurboGears we currently have two approaches to manage i18n data: first, more popular, is admi18n and second, which I contributed, via "tg-admin i18n" command. I think it's beneficial to support both approaches but at the moment they're not 100% compatible and both could benefit from, er, cross-pollination and cross-promotion. May be admi18n maintainer could review command/i18n.py to find problematic things and/or commonalities? I am willing to fix those. I (finally!) wrote basic docs for my command-line i18n tool which are in http://www.turbogears.org/svn/turbogears/trunk/newdocs/docs/admin.html. (I'm not sure that's the right place though and I haven't merged that to trunk). Feedback is welcomed. 2. Kid templates localization Does anyone actually use any of the currently available methods to localize Kid templates' content? Which method do you use and how well it performs? 3. BUG: String collection fails on XML entities, like If Kid files contains such entities both tools (toolbox and cmd-line) chokes with: xml.parsers.expat.ExpatError: undefined entity Any idea how to fix this? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears-trunk -~----------~----~----~----~------~----~------~--~---
