After a longer period of time, I am pleased to announce the release of
TextIndexNG 1.05 beta1
TextIndexNG is a pluggable index for the ZCatalog that enhances the
fulltext
indexing capabilities of Zope by providing the following features:
* support for document converters (HTML, PDF, WinWord, PowerPoint,
Postscript). Custom converters can be easily added
* stemmer support for 12 languages
* optional support for right truncation
* similarity search (soundex, metaphone support) (for english)
* NEAR search
* phrase search
* pluggable query parsers (two parsers included)
* stop words support
* new test tab for interactive testing
* faster than Zopes old TextIndex
* full unicode support (new)
* normalization support (new)
* new similarity algorithm: double metaphone (new)
* new TXNGSplitter
* new vocabulary browser
Changes:
* added full wildcard support for CLLexicon and StandardLexicon
* rewrote Stemmer module (now fully unicode compliant)
* unittests code cleanup
* query evaluation refactored
* Parser API changed to return a parse tree instead of a Python
expression
* new parse tree evaluator added
* PyQueryParser: now accepts a minus sign as prefix of a word to
indicate
NOT. Searching for "foo -bar" will be recognized as "foo AND NOT
bar". In
addition the syntax for "ANDNOT" has been changed to "AND NOT".
* stopword handling through registry
* added double metaphone algorithm for similarity search
* Splitter handling changed: The new TXNGSplitter has been added. It
supports both strings and unicode strings and supercedes the
functionalities of all other existing splitters for Zope.
TXNGSplitter is
the only splitter that will be used by TextIndexNG. The "index
numbers"
options has been removed both from the splitter and the ZMI. In
addition
the splitter now accepts an optional set of characters that are
recognized to be valid inside words. This allows you to index
common
words like "C++" or "python-22.lib" when you specify "+.-" as
valid word
characters.
* Python C extensions compile now under Windows (Binary distribution
will
be available for Windows)
* normalizer support added
* full unicode support
* the add form for TextIndexNG now uses the registries to obtain
informations about registered componenents instead of hardcoded
values.
* fixed problem with changed API of the Interface packages (backport
from
Zope 3 to Zope 2.6)
* added vocabulary browser
* lots of code cleanup
* bug fixes...
* add statistics tab to ZMI
* fixed serious bug in TXNGSplitter due to missing encoding
parameter
* minor ZMI adjustments
* using converters no longer raises an exception when a converter
could not
be found for the mime-type of a document
Requirements:
* Zope 2.5 or Zope CVS trunk checkout
Documentation:
* http://www.zope.org/Members/ajung/TextIndexNG/wiki
Download:
* http://www.zope.org/Members/ajung/TextIndexNG/ or
* http://sourceforge.net/project/showfiles.php?group_id=50052
---------------------------------------------------------------------
- Andreas Jung http://www.andreas-jung.com -
- EMail: andreas at andreas-jung.com -
- "Life is too short to (re)write parsers" -
---------------------------------------------------------------------
I am pleased to announce the first beta release of ZODB3, formerly
known as StandaloneZODB. ZODB is an object database for Python that
provides transactional persistence while requiring few, if any,
changes to application logic.
You can get a source release from http://www.zope.org/Products/StandaloneZODB
Windows users will need a compiler to build C extensions. I'd be
happy to accept a binary installer for Windows, if a user is willing
to contribute it.
The components you get with the ZODB3 release are as follows:
- Core ZODB, including the persistence machinery
- Standard storages such as FileStorage
- Supporting modules such as ExtensionClass
- The persistent BTrees modules
- ZEO
- Experimental Berkeley storages
- Some documentation <wink>
The beta release contains roughly the same version of ZODB that will
be included in Zope 2.6. The two releases are not directly
coordinated, so there may be some subtle differences.
Many people have contributed to ZODB3. Special thanks to Toby
Dickenson for the new ZODB Connection cache. Many people at Zope
Corp. have contributed code and tested unreleased versions.
The NEWS.txt file contains a list of the major changes since the
StandaloneZODB 1.0 release in February. You can also find this list
at http://www.zope.org/Products/StandaloneZODB/NEWS
Jeremy
Announcing PersistentTranslationService 0.1:
This first alpha release of PersistentTranslationService allows you to
have fully functional internationalization from Page Templates using the
standardized i18n tags.
PersistentTranslationService is configurable and can redirect different
i18n domains to different message catalogs.
PersistentTranslationService currently uses Localizer as its message
catalog backend, and Zope 2.7's implementation of i18n tags. It needs a
Unicode-aware Zope (Zope-2_6-branch from CVS is recommended).
See http://www.zope.org/Members/efge/PersistentTranslationService for
more information.
Florent
--
Florent Guillaume, Nuxeo (Paris, France)
+33 1 40 33 79 87 http://nuxeo.com mailto:fg@nuxeo.com
* Do you want to know if your ZEO client cache is configured properly?
* Are you using ZEO but you didn't know it had a client cache?
* Do you want to contribute towards a better ZEO client cache design?
If you answered yes at least once, read on!
Jeremy is working on a new ZEO 2 release; the first beta was released
two weeks ago. For that release I have written cache instrumentation
code that lets you review the effectiveness of the ZEO client cache.
There's also a version of the instrumented cache for ZEO 1. I don't
plan to work on it more before the ZEO 2 release (unless I receive bug
reports). All code is available *now* from the ZODB3 CVS tree:
http://cvs.zope.org/ZODB3/.
In addition to adding instrumentation, some bugs affecting performance
but not correctness of the cache have been fixed in the instrumented
cache code. The instrumentation is controlled by an environment
variable so you can leave the new cache code in place after turning
off the instrumentation.
I'm inviting everyone who is running ZEO seriously to install the
cache instrumentation code, run it for a while, and send me the
resulting trace file. (The trace files contain no privacy-sensitive
data, so you don't have to worry about revealing anything about your
site.) The trace files will be used as input to a simulation of a new
cache design. The only way to validate a cache design is to run
experiments, and trace files are the most reliable way to run such
experiments. The more trace files I receive the better. The larger
they are the better (traces of several days of uninterrupted service
are ideal). I've got the disk space to burn.
I should mention that I'm confident that the instrumentated cache
works correctly: we've been collecting traces without problems at a
Zope Corp customer site since last Wednesday.
To enable the cache instrumentation, you need to replace a single file
in the ZEO package used by the Zope application, set an environment
variable, and restart the Zope application. The file you need to
replace is named ClientCache.py. Here are the URLs:
For ZEO 1: http://cvs.zope.org/ZODB3/ZEO1/ClientCache.py?rev=HEAD
For ZEO 2: http://cvs.zope.org/ZODB3/ZEO/ClientCache.py?rev=HEAD
Make sure to get the file for the ZEO version you are using!
Details about enabling the tracing can be found here:
http://cvs.zope.org/ZODB3/ZEO/README.txt?rev=HEAD
If you want to play with the statistics or simulation programs
yourself, get stats.py and simul.py from the ZEO directory:
http://cvs.zope.org/ZODB3/ZEO/
These work with trace files produced by either version of the
instrumented cache code.
Once you have one or more trace files for me, the best way to get it
to me is probably to place a gzipped copy on an FTP or HTTP server
from which I can download it and mail me the URL. As I said, these
trace files contain no sensitive data. If you still prefer a
different approach, email me and we'll figure something out.
--Guido van Rossum (home page: http://www.python.org/~guido/)
Hi all !
IngeniWeb, french leader of Zope hosting and consulting, is proud
to announce the release of version 1.0 of its MonZope bundle.
MonZope is a win32 bundle for the end-user, including Zope 2.5.1,
IngeniSite P.E. (End-User oriented CMS System) and
MonZope.com a free redirection system.
With this toolset, you can host a Zope personal website
on your own ADSL/Cable internet line. Full documentation is provided.
Everything is Free. French version only for now.
Visit and download package on www.monzope.com
Cheers,
--
Olivier DECKMYN
INGENIWEB (TM) - SARL 50000 Euros - RC B 438 725 632
2 cours du 14 Juillet - 78300 Poissy France - +331 300 601 41
web : www.ingeniweb.com - « les Services Web Ingénieux »
PGP : http://www.ingeniweb.com/keys/olivier.deckmyn
This is to announce the release of Pound v0.10.
New in this release:
- added required/disallowed headers matching in groups
- configurable cyphers/strength for SSL
- retry request on discovering dead back-end
- configurable logging facility
- added configure script
- fixed bug in multiple requests per connection (GROUP matching)
- (re)fixed missing '~' in URL matching
- fixed bug in reading certificate/private-key file
What is Pound (from the Web page)
- a reverse-proxy: it passes requests from client browsers to one or more
back-end servers.
- a load balancer: it will distribute the requests from the client browsers
among several back-end servers, while keeping session information.
- an SSL wrapper: Pound will decrypt HTTPS requests from client browsers and
pass them as plain HTTP to the back-end browsers.
- an HTTP/HTTPS sanitizer: Pound will verify requests for correctness and
accept only well-formed ones.
- an HTTP/1.1 to 1.0 proxy.
- a fail-over-server: should a back-end server fail, Pound will take note of
the fact and stop passing requests to it until it recovers.
- a request redirector - it will pass client requests to separate groups of
servers, based on required URL and the presence or absence of headers
(pattern matching)
Pound was specifically developed to serve as a front-end for multiple
instances of Zope running on top of a common ZEO storage, but can be used
with any other web server. A patch for the Python source of z2.py is
available as part of the distribution to allow using Pound's SSL capabilities.
Pound is currently in use in several mdeium to large volume sites and seems
to be holding up quite well. The speed is well superior to other, equivalent
solutions, the configuration is much simpler and the necessary resources
(CPU, RAM, disk) are much, much lower.
For further information, download, etc. please see http://www.apsis.ch/pound
The software is at version 0.10 (beta quality). Further testing (especially
under heavy loads), improvements and suggestions are welcome.
Pound is distributed under the GPL.
Enjoy and let me know how it works for you.
--
Robert Segall
Apsis GmbH
Postfach, Uetikon am See, CH-8707
Tel: +41-1-920 4904
Tired of trying to get all the right bits for Plone installed or want any
easy way to install Plone 1.0 Alpha 4 and try it out? Check out the Windows
Installer, in one simple installer (for Windows only) you will have a
working Plone with all the goodies including PIL, Reportlab, External Editor
and the Zope Controller (customised for Plone).
More information: http://www.agmweb.ca/plone
--
Andy McKay
Agmweb Consulting
http://www.agmweb.ca
http://www.zope.org/Members/fredz/html-helper-mode
Here you can find a modified version of html-helper-mode.el (3.0.4jolly)
for emacs who supports dtml tags :
- Auto-indentation (with a little help :))
- Shortcuts / Completion
- Tag regions
I'd be pleased to receive feedback
Fredz.