RE: translating xml documents in a cms

Hi Mattias,

Re: your question of how to handle translation of XML docs in a CMS, there
are usually two ways of solving this. Most typically, translators do not
directly work in the CMS -- this is usually an issue of translation tools
and scalability, although some companies do have in-house translators.

Translators usually rely on Translation Memory tools, which require that the
content that needs to be translated is exported. This helps in leveraging
from previous translations, and also facilitiates (for the translator)
dealing with the typically small, but frequent incremental changes posted to
a web site. Most of this happens in a XML-related standard, TMX. Also, if
you investigate XLIFF, you'll find standards that support the translation
process for XML.

There are a number of plug-in apps available, Globalization Management
Systems, that integrate with a CMS to automate the process of recognizing
small incremental changes, notifying and routing into workflow for
translation, leveraging against translation memory, and redelivering into
the appropriate directories. Among those companies are GlobalSight, Idiom,
SDL, and a few others.

There a number of inticracies when dealing with translation -- these really
are just the most basic highlights...

- Thomas

-----Original Message-----
From: cms-list-admin-/[email protected] [mailto:[email protected]]On
Behalf Of cms-list-request-/[email protected]
Sent: Wednesday, August 13, 2003 12:00 PM
To: cms-list-/[email protected]
Subject: cms-list digest, Vol 1 #599 - 3 msgs


Send cms-list mailing list submissions to
	cms-list-/[email protected]

To subscribe or unsubscribe via the World Wide Web, visit
	http://cms-list.org/mailman/listinfo/cms-list
or, via email, send a message with subject or body 'help' to
	cms-list-request-/[email protected]

You can reach the person managing the list at
	cms-list-admin-/[email protected]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of cms-list digest..."


Max digest size has been increased to 80k per digest. This should result in
fewer digest messages on heavy traffic days (though the digest will be
larger). Feedback on the change is welcome at listmom-/[email protected]
----

Today's Topics:

   1. translating xml documents in a cms (Mattias Konradsson)
   2. RE: translating xml documents in a cms ([email protected])
   3. R: cms-list digest, Vol 1 #598 - 3 msgs (Simone Marotta)

--__--__--

Message: 1
From: "Mattias Konradsson" <[email protected]>
To: <cms-list-/[email protected]>
Date: Wed, 13 Aug 2003 06:18:52 +0200
Subject: [cms-list] translating xml documents in a cms

I'm working on a xmlbased cms that should support multiple languages , I'm
wrestling with how to best handle the process of translating xml documents
between different languages. The idea is that there should be a translator
role with a specifik interface, this translator has right to translate from
one language to another.

First I simply envisioned a split screen interface where he'd see the
original document and start translating it to another language, then I
realized
things are a bit more complicated than that, the xml document actually
contains tags that control the functionality of the page, say that shows a
forum-thread, journal entry or whatever.

If the translator is fluent with xml and the meaning of these tasks
everything is fine, but optimally you'd want the translator only to have to
know
how to translate between the languages and not being able to meddle with
those other tags, but how to accomplish that? you can't simply restrict him
from changing the tag structure either because of things like paragraph tags
that is different between translations, you could make up a template of some
sort I guess that defines what the translatable sections of a document is
but that doesn't seem like a simple task both from a technical and interface
standpoint.

Anyone wrestled with the same problem, thoughts, ideas? Should one keep it
simple and allow the translator to edit the documents in their entirety?

mvh
---
Mattias Konradsson


--__--__--

Message: 2
From: [email protected]
To: cms-list-/[email protected]
Subject: RE: [cms-list] translating xml documents in a cms
Date: Wed, 13 Aug 2003 09:18:44 +0200

xopus (http://www.xopus.com) looks like the ideal tool for this situation.
Have a look at their website, or even better, contact them directly.  They
are very helpfull.

Jan

-----Original Message-----
From: Mattias Konradsson [mailto:[email protected]]
Sent: Wednesday, August 13, 2003 6:19 AM
To: cms-list-/[email protected]
Subject: [cms-list] translating xml documents in a cms


I'm working on a xmlbased cms that should support multiple languages , I'm
wrestling with how to best handle the process of translating xml documents
between different languages. The idea is that there should be a translator
role with a specifik interface, this translator has right to translate from
one language to another.

First I simply envisioned a split screen interface where he'd see the
original document and start translating it to another language, then I
realized
things are a bit more complicated than that, the xml document actually
contains tags that control the functionality of the page, say that shows a
forum-thread, journal entry or whatever.

If the translator is fluent with xml and the meaning of these tasks
everything is fine, but optimally you'd want the translator only to have to
know
how to translate between the languages and not being able to meddle with
those other tags, but how to accomplish that? you can't simply restrict him
from changing the tag structure either because of things like paragraph tags
that is different between translations, you could make up a template of some
sort I guess that defines what the translatable sections of a document is
but that doesn't seem like a simple task both from a technical and interface
standpoint.

Anyone wrestled with the same problem, thoughts, ideas? Should one keep it
simple and allow the translator to edit the documents in their entirety?

mvh
---
Mattias Konradsson

--
http://cms-list.org/
more signal, less noise.


-----Disclaimer-----

This message may contain confidential information intended solely for the
use of the named addressee. If you are not the intended recipient, you
should not read, use, disclose or reproduce the content of this message. If
you have received this message by mistake, please notify the sender
immediately. Any views or opinions presented in this message are solely
those of the author and do not necessarily represent those of AXA Belgium,
AXA Bank Belgium, AXA Tech Belgium GIE - ESV or any other entity of the AXA
Group, unless otherwise stated by the sender and duly authorized by the said
companies.

---------------------



--- StripMime Report -- processed MIME parts ---
multipart/alternative
  text/plain (text body -- kept)
  text/html
---

--__--__--

Message: 3
From: "Simone Marotta" <[email protected]>
To: <cms-list-/[email protected]>
Date: Wed, 13 Aug 2003 10:34:23 +0200
Subject: [cms-list] R: cms-list digest, Vol 1 #598 - 3 msgs

Ben, I think Darrel is right, u need a budget.
Watch this site: www.steptwo.com.au it's fantastic and helpful, in my
opinion.
Specifically, look for white papers about how to make a tender and how to
evaluate a CMS solution.
Let me know what do you think about it.
Simone.

> -----Messaggio originale-----
> Da: cms-list-admin-/[email protected] [mailto:[email protected]]Per
> conto di cms-list-request-/[email protected]
> Inviato: martedì 12 agosto 2003 21.00
> A: cms-list-/[email protected]
> Oggetto: cms-list digest, Vol 1 #598 - 3 msgs
>
>
> Send cms-list mailing list submissions to
> 	cms-list-/[email protected]
>
> To subscribe or unsubscribe via the World Wide Web, visit
> 	http://cms-list.org/mailman/listinfo/cms-list
> or, via email, send a message with subject or body 'help' to
> 	cms-list-request-/[email protected]
>
> You can reach the person managing the list at
> 	cms-list-admin-/[email protected]
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of cms-list digest..."
>
>
> Max digest size has been increased to 80k per digest. This should
> result in fewer digest messages on heavy traffic days (though the
> digest will be larger). Feedback on the change is welcome at
> listmom-/[email protected]
> ----
>
> Today's Topics:
>
>    1. RE: What to look for in a CMS. (Ben Brown)
>    2. RE: RE: Storing data as XML ? (Michael Bardeggia)
>    3. RE: What to look for in a CMS. (Austin, Darrel)
>
> -- __--__--
>
> Message: 1
> From: "Ben Brown" <b.brown-vg8CL7zJelEGl2Yqhw0eblpr/1R2p/[email protected]>
> To: <cms-list-/[email protected]>
> Subject: RE: [cms-list] What to look for in a CMS.
> Date: Mon, 11 Aug 2003 11:44:48 +0100
>
> Also, a cheeky question.what sort of prices should I be expecting? I
> know this will vary tremendously, but a ball park figure to report to
> "the people who decide" would be good.
>
> We are looking for supply (+ license) and some training of the CMS and a
> few templates designed to get us started.
>
> We have the spec and cost for the hosting server.
>
> TIA
>
>
> Ben
>
> -----Original Message-----
> From: cms-list-admin-/[email protected] [mailto:[email protected]]
> On Behalf Of Webb, KerryA
> Sent: 11 August 2003 00:51
> To: cms-list-/[email protected]
> Subject: RE: [cms-list] What to look for in a CMS.
>
>
> Ben wrote:
>
> >
> > I am currently working on redeveloping our website.
> >
> > Due to time and knowledge restrictions were are using
> > external companies to supply and set up our CMS.
> >
> > Several companies will be coming to demonstrate their CMS products in
> > the next two weeks, and I was just after anything I should be watching
> > out for etc.
> >
> > Any questions or points for me to put to them would be appreciated.
> >
>
> Apart from what others have suggested:
>
> Migration - ease of transferring your current website to the new system,
> and
> (looking to the future) ease of migrating from the new system to a later
> one, possibly achieved by your new system using a non-proprietary
> DTD/schema.
>
> Archiving - government agencies typically have more stringent
> requirements
> for archiving their Web resources.
>
> Good luck
>
> Kerry
>
> --
> Kerry Webb
> ACT Information Management
> (02) 62070239
>
> --
> http://cms-list.org/
> more signal, less noise.
>
> --
> http://cms-list.org/
> more signal, less noise.
>
>
> --- StripMime Report -- processed MIME parts ---
> multipart/alternative
>   text/plain (text body -- kept)
>   text/html
> ---
>
> -- __--__--
>
> Message: 2
> Reply-To: <[email protected]>
> From: "Michael Bardeggia" <[email protected]>
> To: "'Tjeerd Brenninkmeijer'" <[email protected]>,
> 	"CMS List" <cms-list-/[email protected]>
> Subject: RE: [cms-list] RE: Storing data as XML ?
> Date: Tue, 12 Aug 2003 10:29:24 -0400
> Organization: FeedStream Inc.
>
> Hello Tjeerd,
>
> How much does X-Hive-DB cost?  I can't find that info from the website.
>
> Regards,
>
> Mike Bardeggia
> [email protected]
> http://www.feedstream.com
>
>
>
> -- __--__--
>
> Message: 3
> From: "Austin, Darrel" <[email protected]>
> To: cms-list-/[email protected]
> Subject: RE: [cms-list] What to look for in a CMS.
> Date: Tue, 12 Aug 2003 09:36:23 -0500
>
> > Also, a cheeky question.what sort of prices should I be expecting?
>
> I'd put forward a semi-educated guess of something between $3,000 and
> $3,000,000
>
> The best way to go about this is come up with a budget. Include hardware,
> the CMS software, installation, set up, training, maintenance, upgrades,
> integration, content migration, and support.
>
> Once you have the budget, you can then find the CMS products that
> fit within
> it.
>
> -Darrel
>
>
>
> -- __--__--
>
> --
> http://cms-list.org/
>
> End of cms-list Digest



--__--__--

--
http://cms-list.org/

End of cms-list Digest

--
http://cms-list.org/
more signal, less noise.