[Zope-dev] NotFound
Hi Is there a reason why zope.publisher.interfaces.NotFound is not locatable? class NotFound(LookupError, TraversalException): implements(INotFound) def __init__(self, ob, name, request=None): self.ob = ob self.name = name Why should a NotFound error instance not be locatable by default since it provides a location? Regards Roger Ineichen _ END OF MESSAGE ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: AW: AW: Re: AW: Re: AW: Re: New i18n locale extraction concept
On Sat, May 10, 2008 at 6:22 PM, Wichert Akkerman <[EMAIL PROTECTED]> wrote: > zcml is a pretty simple format though: xml with only human readable text > in title and description attributes (and perhaps a few others) and the > translation domain specified in a i18n_domain attribute. It should be > quite trivial to extract that data without having to pull all of zope > in. If you determine beforehand which strings are translatable (end up as msgid objects) it should be trivial to extract these. You will have to update i18ndude to add new zcml tags though. -- Martijn Pieters ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: AW: AW: Re: AW: Re: AW: Re: New i18n locale extraction concept
Previously Martijn Pieters wrote: > On Sat, May 10, 2008 at 3:40 PM, Hanno Schlichting <[EMAIL PROTECTED]> wrote: > > Currently i18ndude doesn't extract any messages from ZCML. It is used for > > extraction of all messages for the Plone project which happens to use lots > > of ZCML. But none of the messages defined in ZCML are actually used in any > > user visible part of the whole application. > > > > So even if you are a Zope project, I think there's very good reasons not to > > require ZCML extraction. > > Although the ZMI may not count as a 'user visible' part, Generic Setup > profile titles do show up there, which are defined in ZCML and should > be translatable. > > Also, these days it is possible to register content views (such as the > default view for a folder) through ZCML, using a menu directive for > the title. Again these titles should be translatable. zcml is a pretty simple format though: xml with only human readable text in title and description attributes (and perhaps a few others) and the translation domain specified in a i18n_domain attribute. It should be quite trivial to extract that data without having to pull all of zope in. Wichert. -- Wichert Akkerman <[EMAIL PROTECTED]>It is simple to make things. http://www.wiggy.net/ It is hard to make things simple. ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: AW: AW: Re: AW: Re: AW: Re: New i18n locale extraction concept
On Sat, May 10, 2008 at 3:40 PM, Hanno Schlichting <[EMAIL PROTECTED]> wrote: > Currently i18ndude doesn't extract any messages from ZCML. It is used for > extraction of all messages for the Plone project which happens to use lots > of ZCML. But none of the messages defined in ZCML are actually used in any > user visible part of the whole application. > > So even if you are a Zope project, I think there's very good reasons not to > require ZCML extraction. Although the ZMI may not count as a 'user visible' part, Generic Setup profile titles do show up there, which are defined in ZCML and should be translatable. Also, these days it is possible to register content views (such as the default view for a folder) through ZCML, using a menu directive for the title. Again these titles should be translatable. -- Martijn Pieters ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: AW: AW: Re: AW: Re: AW: Re: New i18n locale extraction concept
Hi. Roger Ineichen wrote: Anyway, Since zcml is a default part of zope locale extraction it make no sense to me to not using a working setup for locale extraction. Grok? Does Grok not use zcml extraction? If not, we could probably change the z3c.recipe and disable the default zcml extractor. Currently i18ndude doesn't extract any messages from ZCML. It is used for extraction of all messages for the Plone project which happens to use lots of ZCML. But none of the messages defined in ZCML are actually used in any user visible part of the whole application. So even if you are a Zope project, I think there's very good reasons not to require ZCML extraction. Hanno ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Zope Tests: 5 OK
Summary of messages to the zope-tests list. Period Fri May 9 11:00:00 2008 UTC to Sat May 10 11:00:00 2008 UTC. There were 5 messages: 5 from Zope Tests. Tests passed OK --- Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Tests Date: Fri May 9 21:02:22 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-May/009525.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Tests Date: Fri May 9 21:03:52 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-May/009526.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Tests Date: Fri May 9 21:05:23 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-May/009527.html Subject: OK : Zope-2.11 Python-2.4.4 : Linux From: Zope Tests Date: Fri May 9 21:06:53 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-May/009528.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Tests Date: Fri May 9 21:08:23 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-May/009529.html ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Common-Criteria certification cancelled
On Sat, May 10, 2008 at 10:10:21AM +0200, Lennart Regebro wrote: > On Thu, May 8, 2008 at 11:55 AM, Christian Theune <[EMAIL PROTECTED]> wrote: > > Hi everyone, > > > > I have to give an unfortunate update about the Common Criteria (CC) > > certification. > > > > The CC project began in 2003 to certify Zope 3's security architecture under > > the conditions of the Common Criteria framework. > > > > We started out as a community effort which turned out not to be a viable > > solution due to the lack of interest of volunteers and the complexity of the > > problem space. > > > > gocept restarted the efforts in 2006 and provided a security target document > > which was given to review and moving pretty good actually. There were very > > concrete and viable plans for 2008 to finally get the certification wrapped > > up > > by end of may. > > > > Unfortunately the project had to be cancelled due to the lack of interest of > > the sponsoring organisation which went through a major merger. Due to that > > we're stopping all activities on the certification. If interest in this > > should > > come back at some point, we'd be happy to be part of a renewed effort. > > Too bad. I think those kinds of certifications aren't of much real > use, but it positions you as a serious enterprise player, so it looks > good. I found it very useful to think about security in a structured way. The CC functional catalog isn't that bad. I think the overall approach of CC is actually pretty good. However, certifying a framework isn't directly thought of in CC so we had our problems with terminology clashes etc as CC wants to certify a specific application instead. Christian -- gocept gmbh & co. kg - forsterstrasse 29 - 06112 halle (saale) - germany www.gocept.com - [EMAIL PROTECTED] - phone +49 345 122 9889 7 - fax +49 345 122 9889 1 - zope and plone consulting and development ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Common-Criteria certification cancelled
On Thu, May 8, 2008 at 11:55 AM, Christian Theune <[EMAIL PROTECTED]> wrote: > Hi everyone, > > I have to give an unfortunate update about the Common Criteria (CC) > certification. > > The CC project began in 2003 to certify Zope 3's security architecture under > the conditions of the Common Criteria framework. > > We started out as a community effort which turned out not to be a viable > solution due to the lack of interest of volunteers and the complexity of the > problem space. > > gocept restarted the efforts in 2006 and provided a security target document > which was given to review and moving pretty good actually. There were very > concrete and viable plans for 2008 to finally get the certification wrapped up > by end of may. > > Unfortunately the project had to be cancelled due to the lack of interest of > the sponsoring organisation which went through a major merger. Due to that > we're stopping all activities on the certification. If interest in this should > come back at some point, we'd be happy to be part of a renewed effort. Too bad. I think those kinds of certifications aren't of much real use, but it positions you as a serious enterprise player, so it looks good. -- Lennart Regebro: Zope and Plone consulting. http://www.colliberty.com/ +33 661 58 14 64 ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
