Re: [Zope-dev] Re: What catalog/index to use ...
Hi! Please note that former Zope versions already include a dedicated unicode-aware splitter that is already usable with the old TextIndex and maybe with ZCTextIndex. TextIndexNG resolves all these issues by doing the complete internal processing by converting the data into unicode. Every single processing step only handles unicode data. Most older browsers should be able to handle at least UTF-8 as character set. This is sufficient for most cases. The problem seems to be that ZCTextIndex indeed does not do the splitting right if German Umlauts are used. There is no option for Unicode-aware splitter. Instead of a Vocabulary it uses a Lexicon, which just offers two options: HTML aware splitter and Whitespace splitter. I haven't tested the whitespace splitter yet, but the HTML aware splitter did not do the Umlaut thing right without the patch, i.e. it used umlauts as splitting characters ... So there is a bug ... Joachim ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: What catalog/index to use ...
The problem seems to be that ZCTextIndex indeed does not do the splitting right if German Umlauts are used. There is no option for Unicode-aware splitter. Instead of a Vocabulary it uses a Lexicon, which just offers two options: HTML aware splitter and Whitespace splitter. I haven't tested the whitespace splitter yet, but the HTML aware splitter did not do the Umlaut thing right without the patch, i.e. it used umlauts as splitting characters ... That's just what the default ZMI interface for ZCTextIndex offers. It's easy to add your own splitter by writing a few lines of Python code. RTSL. --Guido van Rossum (home page: http://www.python.org/~guido/) ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: What catalog/index to use ...
Guido van Rossum wrote: The problem seems to be that ZCTextIndex indeed does not do the splitting right if German Umlauts are used. There is no option for Unicode-aware splitter. Instead of a Vocabulary it uses a Lexicon, which just offers two options: HTML aware splitter and Whitespace splitter. I haven't tested the whitespace splitter yet, but the HTML aware splitter did not do the Umlaut thing right without the patch, i.e. it used umlauts as splitting characters ... That's just what the default ZMI interface for ZCTextIndex offers. It's easy to add your own splitter by writing a few lines of Python code. RTSL. of course everyone can write his own Splitter... one for german, one for french, etc.pp. but what is the problem with the patch? is pythons-regexp (?L) not just intended for this simple way of localizing software? and think of the european market: no one will buy Zope, if it is not working with your native language out of the box. and that's what the patch for... cheers, maik -- Maik Jablonski __o www.zfl.uni-bielefeld.de _ \_Deutsche Zope User Group Bielefeld, Germany (_)/(_) www.dzug.org ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: What catalog/index to use ...
The problem seems to be that ZCTextIndex indeed does not do the splitting right if German Umlauts are used. There is no option for Unicode-aware splitter. Instead of a Vocabulary it uses a Lexicon, which just offers two options: HTML aware splitter and Whitespace splitter. I haven't tested the whitespace splitter yet, but the HTML aware splitter did not do the Umlaut thing right without the patch, i.e. it used umlauts as splitting characters ... That's just what the default ZMI interface for ZCTextIndex offers. It's easy to add your own splitter by writing a few lines of Python code. RTSL. of course everyone can write his own Splitter... one for german, one for french, etc.pp. but what is the problem with the patch? is pythons-regexp (?L) not just intended for this simple way of localizing software? and think of the european market: no one will buy Zope, if it is not working with your native language out of the box. and that's what the patch for... I must've missed the start of this thread (I only just signed up for this list). I didn't see any patch -- I thought it was just a gripe about ZCTextIndex. Of course patches are welcome -- where can I find this particular patch? --Guido van Rossum (home page: http://www.python.org/~guido/) ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Simplifying the zdaemon package
I think all these things are reasonable things to do... Guido van Rossum wrote: The zdaemon package contains a bunch of dead wood, or decoys, as Jim would call it, that I'd like to remove. AFAICT, Heartbeat.py is not used anywhere. At least not in the Zope sources -- maybe there are outside users??? And ZDaemonLogging.py is a very thin layer on top of zLOG -- can I get rid of it too? The SignalHandler.py class is not used by zdaemon itself; perhaps it can be moved into the Signals package? --Guido van Rossum (home page: http://www.python.org/~guido/) ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope ) -- Chris McDonoughZope Corporation http://www.zope.org http://www.zope.com Killing hundreds of birds with thousands of stones ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Non Bloating Page Counter
kt == kapil thangavelu [EMAIL PROTECTED] writes: e.g. BerkeleyStorage or OracleStorage. kt is there a useable undoable storage? I think you meant useable non-undoable storage, right? If so, then I believe that ZODB 3.2 will have a such a useable storage. We've had some recent discussions with Sleepycat about some of the worst problems with the BerkeleyDB storages, and I think we now have some good strategies for greatly improving their utility. In the ZODB cvs tree there are now two completely rewritten implementations of the Full and Minimal storages. Full storage, as its name implies supports undo and versions. It reference counts objects and does mark-and-sweep garbage collection, but you need to pack in order to get rid of old object revisions or unreferenced objects. An interesting byproduct of the rewrite is that Full now supports something called autopacking -- essentially a background thread that can be configured to pack the database, say as of 4 hours ago, once per hour (these parameters are of course configurable). Autopacking usually only eliminates old object revisions (with reference counting), but it can be configured to occasionally do a classic pack, which would also do a mark-and-sweep of the entire object space to get rid of unreferenced cycles. For example, you could tell autopack to do one of those once per day. Minimal storage does not support undo or versions because it keeps only the most current object revision. The current implementation of Minimal isn't quite complete because while it performs reference counting garbage collection, it doesn't yet do mark-and-sweep to collect unreferenced object cycles. I'll be adding this probably next week, with pack and autopack interfaces. One downside to the rewrite is that the table schemas aren't compatible with the older versions of these storages, so if you have data in an existing Berkeley storage, you'll need to use something like copyTransactionsFrom() to move them to the new storages. I plan on making a beta release of the new storages sometime early next week. They will be included in the ZODB 3.2 release, which will like get alpha'd soon, with hopefully a final release by the end of the year. If you want to take an early look, check out the ZODB3 cvs tree. What's there passes all the tests. Cheers, -Barry ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Simplifying the zdaemon package
I think all these things are reasonable things to do... Guido van Rossum wrote: The zdaemon package contains a bunch of dead wood, or decoys, as Jim would call it, that I'd like to remove. AFAICT, Heartbeat.py is not used anywhere. At least not in the Zope sources -- maybe there are outside users??? And ZDaemonLogging.py is a very thin layer on top of zLOG -- can I get rid of it too? Done. Also lost a silly main program hiding in zdaemon/__init__.py. The SignalHandler.py class is not used by zdaemon itself; perhaps it can be moved into the Signals package? Will do. --Guido van Rossum (home page: http://www.python.org/~guido/) ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: What catalog/index to use ...
I must've missed the start of this thread (I only just signed up for this list). I didn't see any patch -- I thought it was just a gripe about ZCTextIndex. Of course patches are welcome -- where can I find this particular patch? Hi Guido! I don't know where you would expect a patch to be found, but in this particular case the Zope Collector is a good place to look: http://collector.zope.org/Zope/597 Use the collector, Luke! ;-) Joachim P.S.: I guess most of the people on the zope-dev list have some clue on how to write their own splitters, but the message of my gripe was that something worked o.k. (for the dumb end user) with the old TextIndex and doesn't with the thing that is advertised on the Add form as the replacement, and that just isn't cool. ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: What catalog/index to use ...
I don't know where you would expect a patch to be found, but in this particular case the Zope Collector is a good place to look: http://collector.zope.org/Zope/597 Use the collector, Luke! ;-) Um, that's not a patch. Can you attach a context or unified diff to the collector item? Joachim P.S.: I guess most of the people on the zope-dev list have some clue on how to write their own splitters, but the message of my gripe was that something worked o.k. (for the dumb end user) with the old TextIndex and doesn't with the thing that is advertised on the Add form as the replacement, and that just isn't cool. Indeed. --Guido van Rossum (home page: http://www.python.org/~guido/) ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Simplifying the zdaemon package
The SignalHandler.py class is not used by zdaemon itself; perhaps it can be moved into the Signals package? Will do. Done. --Guido van Rossum (home page: http://www.python.org/~guido/) ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: user roles authentication
This is how the HTTP 1/1 specification requires it to be.
Your browser follows this spec.
Dieter,
I understand the HTTP spec... but ZOPE does not work that way.
I can use methods which require roles above where I logged in. The
methods used for returning the roles themselves do not correlate with ZOPE's
own actions. Therefore ZOPE has an internal inconsistency regarding user
authentication with basic HTTP authorization.
Apparently, you are using a user folder that uses basic authentication.
There are user folders around that can (be configured to) use
Cookie authentication. You can also use CookieCrumber for that.
yes, I've used one or two - but I'm concerned with remedying the default
ZOPE authentication mechanism, which is broken
dtml-call REQUEST.set('roles',['Anonymous',])
dtml-if AUTHENTICATED_USER
dtml-call REQUEST.set('roles',AUTHENTICATED_USER.getRoles())
/dtml-if
Paul,
thanks, but your suggestion isn't applicable since the result of
AUTHENTICATED_USER.getRoles() is wrong.
Grant K Rauscher
GeeKieR Enterprises
http://www.geekier.com/
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://lists.zope.org/mailman/listinfo/zope-announce
http://lists.zope.org/mailman/listinfo/zope )
