Hi Chris,
I don't think you understand what I'm saying. There are no language
specific pages. You don't "force pages into their respective tongues".
It's the other way around. A page should have "versions" in every tongue.
And it definately isn't machine translation... Don't know where you got that
impression (aside from the fact that you build a GMS). And like I said, the
response has been very good. Our clients love the fact that they don't have
to build two sites and they know what's missing because pages haven't been
approved. They also love the fact that when they change the site's
architecture in one language, the change is automatic in every language.
That is so important in multilingual productions. Site architecture MUST be
the same in every language. It is *very* practical and has cut content dev
time significantly.
a.
PS. Let's chat off-list about your system. I may have a few clients that
could use your services in conjunction with ours.
André Milton
www.mlore.com
-----Original Message-----
From: Christian Johnson [mailto:cjohnson@;idiominc.com]
Reading this peaks my interest. What do you mean by "force"? Why would you
want to force pages into their respective tongues? How are you translating
it...machine translation? When brute force translations occur, the data is
not going to be current, product specs are going to be off, linguistically
it will not flow, etc.
As to my knowledge, no CMS on the market can actively manage multi-lingual
content. As the doc moves through the workflow it hits a stone wall...then
the manual process take over. Very time consuming, very expensive and the
sites never seem to be in sync.
Chris Johnson
--
http://cms-list.org/
trim your replies for good karma.
