en
0.25
0.5
0.75
1.25
1.5
1.75
2
Making the Multilingual Web Work: When Open Standards Meet CMS
Published on Jun 19, 201314351 Views
Multilingual content on the web is no longer a luxury, but instead a requirement for most organizations. Although getting web content translated, prepared, and onto the web is hardly turn-key, a best
Related categories
Chapter list
Making the Multilingual Web work: with Open Standards and CMS 00:00
A few things about me00:00
Our good fortune today . . .00:35
Multilingual Web needs multilingual content00:47
My use cases 00:55
Proprietary solutions vs. open standards-based solutions 01:22
Drupal: Translation Core Module01:42
Translator logs in01:50
Clicks the “Translate” tab02:09
Picks the translation language 02:12
BOOM!02:27
Pros and Cons of using Drupal out of the box translation03:29
Translating Drupal with XLIFF04:05
Fundamental difference the XLIFF Tools module brings04:31
Drupal Admin picks the XLIFF modul04:51
Selects the node type to translate04:56
Exports the nodes to XLIFF05:04
Saves the XLIFF file locally05:09
Post processing is usually necessary05:12
XLIFF sent to LSP05:46
LSP leverages TM and translates the XLIFF06:33
Translate only desired text06:49
XLIFF sent back to content owner 06:59
In some cases, non-content text strings require additional processing 07:16
Drupal admin navigates to the Translate interface07:31
Exports the menu PO file07:38
Saves the PO file locally07:42
This provides a non-XLIFF method to translate the menu text07:44
LSP translates Drupal PO XLIFF, then returns translated XLIFF 08:01
Transform translated XLIFF to PO08:07
Import the translated PO file08:12
The site is translated 08:15
Pros and Cons of using open standards and the XLIFF tools module08:21
Component Content Management System (CCMS)08:48
DITA and CCMS09:18
For example, our datasheets are managed in our CCMS09:57
They are made up of many topics (205 in this example)10:05
Under the covers, topics, maps, images live in the repository10:13
Translating Trisoft DITA using out of the box features 10:34
Pick the “publication”10:40
Assign language(s)10:42
Initiate translation10:44
Generate translation report10:47
Push translation11:04
Next steps11:08
100, 1000, 1000000 DITA files sent to LSP; translated; returned11:43
Pros and Cons of using out of the box12:03
XLIFF and the DITA-XLIFF OT Plugin for CCMS 12:32
Note about the DITA-XLIFF plugin and our integration with Trisoft12:46
We’ve added our “Trisoft Publishing Assistant” custom application13:10
1 XLIFF file (not 100, 1000, 1000000 DITA files) sent; translated; returned13:23
Pros and Cons of using XLIFF plugin13:41
Thank you14:17