Barry Warsaw writes: > It's true that the bulk of the translation work project-wide will be for > Postorius and Hyperkitty. Both of those are Django projects, and I'm sure > Django has i18n support, although I really don't know much about those > details.
The OP is already aware of Django's I18N, so I think we're off to a good start there. > To the extent that all subprojects can share infrastructure, great, > but that shouldn't come as a sacrifice for Django's natural i18n > workflow. Aurelien and Florian should probably describe how they > want it to work for those two projects. Agreed. I think the main Django I18N frameworks end up producing potfiles, so the translators should not have too much new infrastructure to learn. Steve _______________________________________________ Mailman-Developers mailing list Mailman-Developers@python.org https://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
