[Zope-dev] release of lovely.remotetask?

2009-02-11 Thread Christian Zagrodnick
Hi, I'd like to create a new release of lovely.remotetask. Could somebody give me (zagy) the pypi rights? Thanks, -- Christian Zagrodnick · c...@gocept.com gocept gmbh co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 4 · fax +49 345 1229889 1

Re: [Zope-dev] z3c.form 2.0

2009-02-11 Thread Stephan Richter
On Tuesday 10 February 2009, Wolfgang Schnerring wrote: I'd like to introduce this to z3c.form as well (see attached patch). Would it be alright with you for me to commit this to trunk (to then go into the release)? Add a test and you can check it in. :-) Regards, Stephan -- Stephan Richter

Re: [Zope-dev] Where should I update the translation messages?

2009-02-11 Thread Dan Korostelev
2009/2/11 Takeshi Yamamoto t...@mac.com: Hello, I would like to update Japanese translation messages of ZMI of Zope 3. I used to do it with launchpad.net but it seems to be gone. Where should I update the translation messages? Thank you. Translations currently belong to the zope.app.locales

Re: [Zope-dev] z3c.form 2.0

2009-02-11 Thread Dan Korostelev
2009/2/11 Stephan Richter srich...@cosmos.phy.tufts.edu: On Tuesday 10 February 2009, Wolfgang Schnerring wrote: I'd like to introduce this to z3c.form as well (see attached patch). Would it be alright with you for me to commit this to trunk (to then go into the release)? Add a test and you

Re: [Zope-dev] z3c.form 2.0

2009-02-11 Thread Dan Korostelev
2009/2/10 Stephan Richter srich...@cosmos.phy.tufts.edu: On Tuesday 10 February 2009, Laurent Mignon wrote: With the replacement of zope.app.component import with zope.site, it's no more possible to use z3c.form with Zope2 / Plone :-( Thanks for getting our attention on this. I consider this

Re: [Zope-dev] Translations for zope packages.

2009-02-11 Thread Dan Korostelev
2009/2/10 Paul Winkler sli...@gmail.com: On Tue, Feb 10, 2009 at 01:54:54PM +0100, Martijn Faassen wrote: In my mind, the Zope framework should offer facilities to support translating applications. These applications can be composed out of more than a single package, and we want to support the

[Zope-dev] Zope Tests: 7 OK, 1 Failed

2009-02-11 Thread Zope Tests Summarizer
Summary of messages to the zope-tests list. Period Tue Feb 10 12:00:00 2009 UTC to Wed Feb 11 12:00:00 2009 UTC. There were 8 messages: 8 from Zope Tests. Test failures - Subject: FAILED (failures=1) : Zope-trunk-alltests Python-2.5.4 : Linux From: Zope Tests Date: Tue Feb 10

Re: [Zope-dev] Translations for zope packages.

2009-02-11 Thread Dan Korostelev
2009/2/10 Martijn Faassen faas...@startifact.com: +1 also to have a way to *see* the translations as a single whole, with the possibility to define a message id that is used by many packages. I'm not sure about the last thing. Message objects are bound to one translation domain, so the

Re: [Zope-dev] Where should I update the translation messages?

2009-02-11 Thread Takeshi Yamamoto
Thank you, Dan. I have sent you an updated Japanese po file just few minutes ago. Can I get a commit right for the next time? Regards. Takeshi Yamamoto On Feb 11, 2009, at 8:20 PM, Dan Korostelev wrote: 2009/2/11 Takeshi Yamamoto t...@mac.com: Hello, I would like to update Japanese

Re: [Zope-dev] Where should I update the translation messages?

2009-02-11 Thread Dan Korostelev
2009/2/11 Takeshi Yamamoto t...@mac.com: Thank you, Dan. I have sent you an updated Japanese po file just few minutes ago. Can I get a commit right for the next time? Regards. Takeshi Yamamoto Done. Thanks for contribution. BTW, we expect a way of translating messages to change soon, so

Re: [Zope-dev] z3c.form 2.0

2009-02-11 Thread Laurent Mignon
Stephan Richter wrote: On Wednesday 11 February 2009, Dan Korostelev wrote: Thanks for getting our attention on this. I consider this a show-stopper for 2.0. Dan, let's think about something creative that allows us to use the new and old way, maybe through a special import statement like that:

Re: [Zope-dev] z3c.form 2.0

2009-02-11 Thread Dan Korostelev
2009/2/11 Laurent Mignon laurent.mig...@softwareag.com: Stephan Richter wrote: On Wednesday 11 February 2009, Dan Korostelev wrote: Thanks for getting our attention on this. I consider this a show-stopper for 2.0. Dan, let's think about something creative that allows us to use the new and old

Re: [Zope-dev] z3c.form 2.0

2009-02-11 Thread Adam GROSZER
Hello, Tuesday, February 10, 2009, 2:19:48 AM, you wrote: ObjectWidget/ObjectMultiWidget - ??? I didn't checked that out, so it would be nice if its author reviewied it and wrote here about its status. SR Adam? I'll note that we use that code heavily at Keas, so at least for that SR limited

Re: [Zope-dev] z3c.form 2.0

2009-02-11 Thread Dan Korostelev
2009/2/11 Stephan Richter srich...@cosmos.phy.tufts.edu: On Wednesday 11 February 2009, Dan Korostelev wrote: Yeah. So one solution, as I said before is to release zope.sitecompat egg that provides a zope.site module, but doesn't implement a site implementation, but instead imports things from

Re: [Zope-dev] z3c.form 2.0

2009-02-11 Thread Tres Seaver
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dan Korostelev wrote: 2009/2/10 Stephan Richter srich...@cosmos.phy.tufts.edu: On Tuesday 10 February 2009, Laurent Mignon wrote: With the replacement of zope.app.component import with zope.site, it's no more possible to use z3c.form with Zope2 /

Re: [Zope-dev] z3c.form 2.0

2009-02-11 Thread Wolfgang Schnerring
Hello, On Tuesday 10 February 2009, Wolfgang Schnerring wrote: I'd like to introduce this to z3c.form as well (see attached patch). Would it be alright with you for me to commit this to trunk (to then go into the release)? * Stephan Richter srich...@cosmos.phy.tufts.edu [2009-02-11 03:19]:

Re: [Zope-dev] z3c.form 2.0

2009-02-11 Thread Laurent Mignon
Tres Seaver wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dan Korostelev wrote: 2009/2/10 Stephan Richter srich...@cosmos.phy.tufts.edu: On Tuesday 10 February 2009, Laurent Mignon wrote: With the replacement of zope.app.component import with zope.site, it's no more possible to use