Advantages of XLIFF

xliff is less vendor dependent

you can use xml tools to handle xliff content

you have better control of what to translate than with .po files

you can have alternative translations

easy round trip

XLIFF is integrated with sidneys marshaller

Requirements:

LinguaPlone

ArchetypeContentTypes

Plone is not a translation tool, but it would handle multilingual content.

Translation Memory: TMX

Translation tools woule keep track of existing translations and if there is a translation already the tool would come up with it and help the translator.

Tools:

* TRADOS big and used a lot

* Microsoft Word supports XMLIFF

* XLIFF editors

Each language would be put into one xliff file. This file is sent to a translation center. The file will be returned and integrated. Copy and Paste / Drag and Drop has been done at this point prior to xliff, now this is not needed any more.

Export as one xliff file or into a zipfile with all objects you choose.

With webdav you can upload xliff again.

[...xliff snipplet is shown on the screen...]

uids are used to identify the content object that is exported or imported.

content can be moved and renamed, because the uid is a reference that will not break.

you have a trans unit in the xliff xml file

the trans unit contains a source and a target

translators get paid by word! they don't necessarily understand the xml so they would translete EVERY occurance of words, so some would translate source AND target, which makes the xliff meaningless for the system. They would also translate markup keywords like class="veebmeister" align="raremal". Those are 'real life' problems with translations. SOme attribtes need to be translated, though.

[...an example of a plone 2.0.5 site translated into 24 languages is shown on the screen...]

Issues and Solutions

lang-code on fileids
the url should be the same...
Folders should be imported FIRST, then the content objects. The objects would be in different locations and can have the SAME id then, only the first folders id differs and decides which language you want to see.

Limi added that this issue is much easier to handle now with plone2.1 and the new LinguaPlone :-)

Webdav:

* NETDRIVE is recommended

Speed:

* It takes time to translate at content

Cataloguing:

* Catalog on import or after import


How in Plone 2.1?

* It should work 'out of the box'

* There is an external method that is implemented in xliff marshaller

* you should look up content objects and have a sort of list of them

* you trigger the external method for exporting the content

* you will get one file per folderish object as well, to handle the content of folderish objects.

* Some browsers unzip the zip right after the download

* You can also use xliff to recreate your content, as a kind of emergency backup ;-)

* the xliff file contains information on which fields should be translated and which language is the target language.

* The xliff file can then be uploaded again

* Now we have two more languages available in the interface :-)

* There is a xliff management entry in the 'translate into' menu. You can export and import through the web using the interface that would come up when you select this option.