The bug was fixed three weeks ago (branch-1-0), it is
time for a release I guess. Well, only the strip(),
no try/except clause yet.
By the way, Localizer bugs/patches should be sent to
the Localizer mailing list or to the SourceForge tracker
of the LLEU project.
Romain Slootmaekers wrote:
Joachim Werner wrote:
Just a very short comment:
As Paul said in the Paris meeting and as Joachim W. has
stated in a previous mail, one thing we can work on is in
a common way to get translations from message catalogs, from
Python code and DTML and ZPT templates.
First bug, the module 'Products/PluginIndexes/tests/testFieldIndex.py'
contains the methods 'checkEmpty', 'checkPopulated', 'checkZero',
'checkNone' and 'checkRange'; they should be named 'testEmpty',
'testPopulated', etc.. otherwise the tests doesn't run.
Last bug, The file
(I think) there's a very small bug in 'App/special_dtml.py'. In Zope
2.4.1, the line 231 is:
if bind_to in ('container', 'client'):
I think it should be:
if bind_to in ('container', 'context'):
The problem shows when subclassing DTMLFile and trying to change the
The version 0.2 of the product Localizer has been released. It helps
to internationalize/localize python products and build multilingual
web sites. The new version fixes some bugs and includes some small
new features. A little documentation is included. Download from:
P.S.: Shane, have you developed Symlinks any further? I think they could be
extremely useful. I tried out the initial release and liked it, except for
the fact that the symlinks looked EXACTLY like real ones, so they can be
very irritating ...
I'm not sure what to do with symlinks.
The undo form shows interesting info about transactions, for example their
modification times. It's easy to know the last time an object was modified
But, is there an easy way to get the name of the user that made the last
modification of an object?
I've working a little in a new CalendarTag, you can download it
(version 2.0 alpha 1) from http://sourceforge.net/projects/lleu
Be careful, its usage is somewhat different and will probably
break the pages that use the old CalendarTag. It's not for
production environments, it's mainly
Download mxDateTime 0.1 from
This product makes easier to use the mxDateTime python module
from Zope. It allows to use it from Python Products and external
methods using for example::
I used mxDateTime about two years ago, when I worked with Bobo, the
move to Zope brought lots of advantages, the only thing I missed was
The discussion about DateTime comes to the mailing lists between time
to time, you can look what has already been said about it
Of course, we already can use mxDateTime in our own products. But
there is a problem, both modules have the same name, if you write
"import DateTime" you get the Zope's DateTime module.
A solution is to rename the mxDateTime module directory from
DateTime to, for example, mxDateTime,
IMHO the long term solution would be to use the mxDateTime 
module instead of the DateTime module that currently uses Zope.
I am playing around with the DateTime module in order to adapt it
In article [EMAIL PROTECTED],
Jimmie Houchin [EMAIL PROTECTED] wrote:
The GPL would protect DC from predatory competitors. It would also allow
for Zope's adoption in certain environments. I also believe some people
And prevent it in others.
would relicense their products to the
On Tue, 14 Nov 2000 09:48:20 +0100 (MET), [EMAIL PROTECTED] (Juan
David Ibáñez Palomar) wrote:
it's illegal to distribute GPL code together
with [ZPL] code
I dont see this as an issue for Zope (taken as a whole). There is no
problem with other developers releasing GPL products
Has any open source license issue actually come to court yet?
How many people really care about this compared to the number of people
who just want to get on, develop and use software in an open source
community fashion and don't want to get involved in religious flame
Regaurding licensing, twhile I wouldn't want to snuff out freedom of speech,
I would say that we have already had the "Licensing Wars" about 18 months
ago, and things are settled and non negotiable at this point. Arguing only
creates tension in the community, which does more damage
Mail list logo