Hi Oleg, --On Donnerstag, 13. September 2001 13:45 +0400 Oleg Broytmann <phd@phd.pp.ru> wrote:
On Thu, Sep 13, 2001 at 11:38:42AM +0200, Tino Wildenhain wrote:
Certainly it is possible. Oracle, for example, allows to create multilingual multiencoding databases. But it is not so simple.
Maybe its possible to define the splitter per field?
The problem is not in the Splitter itself - the problem is in locale data. Locale data is the accumulated result of long research. Many people collected the data (how to represent national symbols, how to sort them, which are printable, which are alphas, etc), organized it and put into locales. If you are going to get rid of locale - where you will get this information? You need it for every language/encoding you are going to support.
Specifically by defining the locale per field. The problem however raises, if you have multiple representations of the same document and have to serve them according to existence and language preference of the reader. Even harder, if one document has more then one language in it! The way to go is unicode of course, but how do we proceed? Any ideas? I think this must be solveable. Regards Tino
Oleg. ---- Oleg Broytmann http://www.zope.org/Members/phd/ phd@phd.pp.ru Programmers don't die, they just GOSUB without RETURN.
_______________________________________________ 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 )