i18n again

[Petr Stehlik <pstehlik@xxxxxxxxxx>]

Hi all,

I have been googling for half of Sunday but haven't found a good answer
to my question. I decided to create different HTML files for different
languages since there is no framework for automatic text nodes
translation (*). So I searched for a way of handling different HTML
'skins' and found this:

http://mail-archive.objectweb.org/xmlc/2000-08/msg00011.html

As you can see this proposal is almost 4 years old. No idea if it ever
got implemented. Haven't found it documented anywhere. Does David or
somebody else know if this (or a similar method) is available in current
XMLC 2.2/Enhydra 5.1?

(*) re: automatic text nodes translation:

Eric Bartley wrote in January 17th, 2001 about an idea based on MD5
hashmap of the text nodes - sounds very similar to my idea I talked
about in January this year. Unfortunately the MHonArc on ObjectWeb broke
the old links Google knows so the following URL points to Google's
cache:

http://216.239.59.104/search?q=cache:Ju3BN6993U4J:xmlc.enhydra.org/project/mailingLists/xmlc/msg00546.html+Enhydra+i18n+md5&hl=cs&ie=UTF-8&inlang=pl

Again no sign if this was ever discussed further.

I am certain the i18n issues have been solved by many Enhydra/XMLC users
privately but there doesn't seem to be a ready-to-use solution for i18n
newcomers included in stock XMLC/Enhydra. Or am I wrong? Please tell me.

Thanks.

Petr