trikonf 2013 - standards and interoperability

Post on 20-May-2015

618 Views

Category:

Technology

1 Downloads

Preview:

Click to see full reader

DESCRIPTION

Presentation about Standards and Interoperability in the translation industry. Focus on authoring, content management, translation and publishing standards. Special focus on DITA and TMX.

TRANSCRIPT

2014

www.tracom.de • @stefangentz • facebook.com/stefan.gentz

by Stefan Gentz, tracom.de • @StefanGentzTriKonf 2013 • 20 Oct 2013 • Freiburg, Germany • #trikonf13

STANDARDS

&INTEROPERABILITY

www.tracom.de • @stefangentz • facebook.com/stefan.gentz

twitter: @stefangentz

facebook: fb.com/stefan.gentz

LinkedIn: linkedin.com/in/stefangentz

Stefan Gentz

@stefangentz at #trikonf13: Your voice matters!

Let's make this event trending!

STANDARDS

ARE NOT NEW

STANDARDS

TODAY

»STANDARDS ARETHE DISTILLED WISDOM

OF PEOPLE WITH EXPERTISE IN THEIR SUBJECT MATTER AND WHO KNOW THE NEEDS OF THE ORGANIZATIONS

THEY REPRESENT – PEOPLE SUCH AS MANUFACTURERS, SELLERS, BUYERS,

CUSTOMERS, TRADE ASSOCIATIONS, USERS OR REGULATORS.«

British Standards / BSI, »What is a Standard«?

»STANDARDS ARE KNOWLEDGE. THEY ARE POWERFUL TOOLS THAT CAN

HELP DRIVE INNOVATION AND INCREASE PRODUCTIVITY.

THEY CAN MAKE ORGANIZATIONS MORE SUCCESSFUL AND PEOPLE’S EVERYDAY LIVES

EASIER, SAFER AND HEALTHIER.«

British Standards / BSI, »What is a Standard«?

STANDARDSLET’S HAVE A LOOK AT

CONTENT TODAY

WE HAVE STANDARDS FOR:

CONTENT AUTHORING

CONTENT MANAGEMENT

CONTENT TRANSLATION

CONTENT DELIVERY

AUTHORING

STANDARDS

CONTENT AUTHORING STANDARDS

• ISO/IEC 26300:2006 (OPEN OFFICE)• ISO/IEC 29500-1:2008 (DOCX)• OASIS DITA• OASIS DOCBOOK• W3C (X)HTML

CONTENT

MANAGEMENT

STANDARDS

CMISCONTENT MANAGEMENT

INTEROPERABILITY SERVICES

DERCOM COTICOMMON TRANSLATION INTERFACE

FIRST DRAFT PUBLISHED AT TCWORLD / TEKOM 2013/11

WWW.DERCOM.DE

ACOLADA GMBH | SCHEMA GMBH | DOCUFY GMBHEMPOLIS INFORMATION MANAGEMENT GMBH | GDS AG

NOXUM GMBH | OVIDIUS GMBH

TRANSLATION

STANDARDS

A FEW CONTENT L9N/L10N STANDARDS:

• OASIS XLIFF• TMX (STANDARD?!?)• ISO 30042:2008 – TBX (TERM)• SRX (STANDARD?!?)• XML:TM (dead)• W3C ITS

CONTENT

DELIVERY

STANDARDS

A FEW CONTENT DELIVERY STANDARDS:

• ISO 32000 (PDF/X)• XSLT / XSLFO• (X)HTML + CSS• IDPF ePub• MOBI

CONTENT CURATION

DELIVERY

TRAN

SLATIONAU

THO

RIN

G

MANAGEMENT

SO, WE’RE

COVERED!

THE STANDARDS

FORMULAR FOR

WOR(L)D PEACE

ALL IS FINE!ALL IS FINE!

@stefangentz at #trikonf: “ The Forumlar for Wor(l)d Peace! #Standards for Everything: Content, Content Mgmgt, Translation, Publishing”

Did you tweet?

THANK YOU

FOR YOUR

ATTENTION!

twitter: @stefangentz

facebook: fb.com/stefan.gentz

LinkedIn: linkedin.com/in/stefangentz

Stefan Gentz

ONE MORE THING …

2013

DIRTY

www.tracom.de • @stefangentz • facebook.com/stefan.gentz

by Stefan Gentz, tracom.de • @StefanGentzTriKonf 2013 • 20 Oct 2013 • Freiburg, Germany • #trikonf13

TRUTHLITTLE

STANDARDS&INTEROPERABILITYABOUT

THE

HELLO CONTENT AUTHORS!

STANDARDS ARE GOOD.

BUT HUMANS CAN

MESS UP EVERYTHING!

Adobe InDesign CS6

ISO/IEC 15930-7 (PDF/X-4)

ISO/IEC 29500-1:2008 (DOCX)

THE SAME RESULT IN ISO/IEC 29500-1:2008

SDL Trados Studio

A TRANSLATION EDITOR

DITA 1.2 Sample

A DITA 1.2 SAMPLE

OmegaT 3.0.4 TMX Export

TMX 1.4 (OmegaT)

SDL Trados 2007 TMX Export

TMX 1.4 (TRADOS 2007)

SDL Trados 2011 TMX Export

TMX 1.4 (TRADOS 2011)

memoQ 6.5 TMX export

TMX 1.4 (memoQ 6.5)

across Language Server TMX export

TMX 1.4 (across.net)

XLIFF SUPPORT IN CAT TOOLS Results of the survey, January 2012

Lucía Morado Vázquez David Filip

XLIFF SUPPORT IN CAT TOOLS

http://www.localisation.ie/resources/XLIFFSotAReport_20120210.pdf

9

3.3.1 Minimal XLIFF elements and attributes In the minimal XLIFF elements we found the elements that a XLIFF document should contain to be

considered as valid. Along with the elements, we decided also to include in this analysis the

compulsory attributes of this set of elements, which, following the same criteria, would be needed

to have a valid XLIFF document. It should be noted that all 7 tools support the elements, which means that there is a common

denominator among all of them. And regarding attributes, with the exception of “datatype” in

Virtaal, the rest of the attributes are supported by all 7 tools.

Tool Name

Elements Attributes

body

file

sour

ce

tran

s-un

it

xliff

data

type

id

orig

inal

sour

ce-

lang

uage

targ

et-

lang

uage

Okapi Framework Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes

MultiTrans Prism (5.0) Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes

SDL Trados Studio 2011 Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes

Swordfish III (3.0-6) Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes

Transifex N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A

Translator Workspace XLIFF Editor Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes

Virtaal 0.7.0 Yes Yes Yes Yes Yes No Yes Yes Yes Yes

XTM 6.0 Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes

Table 4. Minimal XLIFF elements and attributes support We also asked two questions regarding two specific aspects of XLIFF support: the possibility of

handling more than one file element and whether the tool prevents or not the creation of duplicated

trans-unit IDs. In “Table 5. Multiplicity of file element and duplicated trans-unit IDs” you can see how

all the answers, with the exception of Virtaal 0.7.0, were affirmative.

Tool Name It handles more than one file element It prevents the creation of duplicated trans-units IDs

Okapi Framework Yes

Yes

MultiTrans Prism (5.0) Yes

Yes

SDL Trados Studio 2011 Yes

Yes

Swordfish III (3.0-6) Yes

Yes

Transifex Yes

Yes

Translator Workspace XLIFF Editor Yes Yes

Virtaal 0.7.0 No

N/A

XTM 6.0 Yes

Yes Table 5. Multiplicity of file element and duplicated trans-unit IDs

XLIFF SUPPORT IN CAT TOOLS

http://www.localisation.ie/resources/XLIFFSotAReport_20120210.pdf

STANDARDS ARE GOOD.

BUT SOFTWARE CAN

MESS UP EVERYTHING!

CHALLENGES

• CONTROLLED AUTHORING• BETTER STANDARDS INTEGRATION

IN SOFTWARE TOOLS• DATA EXCHANGE AND

INTEROPERABILITY BEYOND »STANDARD FRAMEWORKS«

STANDARDS ARE GOOD.

BUT WE’RE JUST AT THE

BEGINNING.

DITA, XLIFF, TMX, TBX ETC. ARE JUST »FRAMEWORKS«. THEY CAN WRAP AROUND OTHER STANDARDS OR NON-STANDARDS. THEY ARE NO GUARANTEE FOR ANYTHING THAT THEY “CARRY”.

THINK OF A MOBILE PHONE COMPANY:

WHILE BUILD ON TONS OF STANDARDS, THEY ARE STILL JUST CARRIERS.

BUT YOU MAKE THE PHONE CALL.IT’S YOUR CONTENT.

DON’T BLAME THE STANDARDS IF YOUR CONTENT IS JUST SHIT.

» Standards are like a Trojan horse: They come as a present but can carry a bomb!«

REMBER OUR LITTLE

FORMULAR FOR

WOR(L)D PEACE?

ALL IS FINE?ALL IS FINE?

FINAL QUOTE:

@stefangentz at #LocWorld: “ Humans eat Standards for lunch”

Let's make this event trending!

THANK YOU

FOR YOUR

ATTENTION!

twitter: @stefangentz

facebook: facebook.com/stefan.gentz

LinkedIn: linkedin.com/in/stefangentz

Stefan Gentz

top related