Ok, I can reproduce this bug. This seems to be a problem when you are using uText as property type. The bug does not occur with normal string property and does not occur with standard unicode attributes. I am trying to investigate the reason later today...should not be too hard to fix that. -aj --On Montag, 6. Januar 2003 06:58 +0200 Heimo Laukkanen <huima@fountainpark.org> wrote:
Andreas Jung wrote:
I have never seen this problem since casefolding is on by default(!) and there is no code that modifies the original object. Please provide a reasonable description how to reproduce this problem with a standard Zope installation.
Ok. Here is how to do it.
I have a Zope 2.6.
Create new folder for test textindextest with public interface ( index_html )
Go to index_html, add to properties content uText field. Add content: Test Content'
Create ZCatalag there - with name Catalog, add TextIndexNG index with name content, indexing content attribute.
Find objects to catalog with name index_html
Go back to index_html and check properties: Test Content is changed to test content
-huima
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
--------------------------------------------------------------------- - Andreas Jung http://www.andreas-jung.com - - EMail: andreas at andreas-jung.com - - "Life is too short to (re)write parsers" - ---------------------------------------------------------------------