Re: [Zope3-dev] Re: translation of zope3
Philipp von Weitershausen wrote: Christophe Combelles wrote: Is translations.launchpad.net the regular and recommended way of translating zope3 ? Yes. I'm not sure they're synchronizing frequently with the repository. You bring a good point to my attention. Now that each package is its own project with a separate release cycle, we should split up the translations and maintain them for each package. Mostly 'zope.app.*' packages (with a few exceptions such as zope.formlib) will have translations. Given that the extraction tool left source markers in the translation files, I think this task could be automated. Would be a fun project for somebody :) I've already thought about it and I think the following steps should be performed: 1. Move all Python modules from zope.app.locales to zope.i18nmessageid (or maybe to zope.i18n?). 2. Write a tool for splitting up translations. I think the tool will be useful not only for the case and it would be cool if the tool could extract, split and merge translations. 3. Split up the existing translations. 4. Remove zope.app.locales altogether. If nobody objects I can perform the steps above. Open questions: - What about translations.launchpad.net? Is there are way to create templates for all translated packages in the zope3 project? - When the next release? :-) -- Dmitry Vasiliev dima at hlabs.spb.ru http://hlabs.spb.ru ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Porting zope.testing to python2.5
Jim Fulton [EMAIL PROTECTED] wrote: You should also check that they run under Python 2.3. The tests are running successfully in Python2.3 also. Then go ahead and merge. Jim I have merged the changes to the zope.testing trunk. Regards Nikhil N ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Re: AW: deprecate ++etc++site/default?
On 21.06.2007, at 22:57, Bernd Dorn wrote: On 20.06.2007, at 08:01, Christian Zagrodnick wrote: Note that adding a subitem called 'default' won't be allowed: site_manager['default'] = object() Traceback (most recent call last): ... Your -1 goes was for this part, was it not? yes, i want to be able to add a subitem called default same here ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/batlogg.lists% 40lovelysystems.com -- Sparse is better than dense. -- The Zen of Python, by Tim Peters Jodok Batlogg, Lovely Systems Schmelzhütterstraße 26a, 6850 Dornbirn, Austria phone: +43 5572 908060, fax: +43 5572 908060-77 smime.p7s Description: S/MIME cryptographic signature ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Re: AW: deprecate ++etc++site/default?
On Jun 21, 2007, at 5:22 PM, Jodok Batlogg wrote: On 21.06.2007, at 22:57, Bernd Dorn wrote: On 20.06.2007, at 08:01, Christian Zagrodnick wrote: Note that adding a subitem called 'default' won't be allowed: site_manager['default'] = object() Traceback (most recent call last): ... Your -1 goes was for this part, was it not? yes, i want to be able to add a subitem called default same here same here (pretty much for legacy reasons) Gary ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com