What should a 'perfect' XML and XLIF file look like for Trados?
Thread poster: jykim
jykim

Local time: 01:11
German to Korean
+ ...
Oct 9, 2010

Hi everyone!

I have been working for this client for a couple of years and since I was complaining their newest XML-files (it crashes from time to time when opening a segment), the customer asked me what to me a 'perfect' XML- or XLIF (?) -file should look like to work with on Trados. Since I am not a technical Trados specialist, I thought why not asking this very good forum. So, may I ask you, how a 'perfect' XML-/XLIF-file should look like to work on conveniently?

The only things which come into my mind are no additional tags (btw: what's the difference between internal and external tags?), configuration information, right coding, but what else? What are the important things to have a good structured source file and what is the difference between XML and XLIF?

Thanks to everyone!

(-:


Direct link Reply with quote
 

Walter Blaser  Identity Verified
Switzerland
Local time: 01:11
French to German
+ ...
It does not need to be perfect but it must be 'well-formed' Oct 9, 2010

There is no definition of a "perfect XML document", but there is a standard defining which rules must be met in order for an XML document to be considered as "well-formed".

Only a "well-formed" XML document can be opened or processed without any problems by a third-party application.

As to the difference between XML and XLIFF: XML is the basic standard for a markup language and XLIFF is one of the various existing XML flavors. It stands for "XML Localization Interchange File Format " and is a standard for the exchange of localizable data. So, XLIFF is not at all identical to XML, but it is based on the XML standard.

You can find the XML standard here: http://www.w3.org/TR/REC-xml/

Walter


Direct link Reply with quote
 
jykim

Local time: 01:11
German to Korean
+ ...
TOPIC STARTER
Hm, what about... Oct 9, 2010

Thanks, Walter!

Since I am doing pretty much software localization with Trados, I got loads of files containing tags and therefore would really much like to know, whether it is possible to declare special tags within the files as untranslatable and block variables, placeholder or the like... and what about html-tags, links etc. - can they greyed out as well?

Which CAT-Tool would be good alternative to Trados for this?

(-:


Direct link Reply with quote
 

Walter Blaser  Identity Verified
Switzerland
Local time: 01:11
French to German
+ ...
It can all be done in Studio Oct 10, 2010

...would really much like to know, whether it is possible to declare special tags within the files as untranslatable and block variables, placeholder or the like... and what about html-tags, links etc. - can they greyed out as well?


This can all be done by defining an appropriate XML file type definition. Studio 2009 includes a default "Any XML" definition, which can be used as a template to define an XML filetype that does exactly what you want it to do. You can create such a new XML filetype either by importing an existing definition from an .INI or .ANL file, by extracting the information from an XML file or manually by defining yourself the entities and their attributes.

Walter


Direct link Reply with quote
 
jykim

Local time: 01:11
German to Korean
+ ...
TOPIC STARTER
One more question... Oct 10, 2010

Hi Walter,

once again, thanks (-:

How can the information be automatically extracted from the XML-file? Is there a way by simply pushing a button?

And what you're explaining is only for 2009 or does 2007 contain similar functions?

Thanks!


Direct link Reply with quote
 

Walter Blaser  Identity Verified
Switzerland
Local time: 01:11
French to German
+ ...
You can create an XML filetype from a document Oct 10, 2010

jykim wrote:

Hi Walter,

How can the information be automatically extracted from the XML-file? Is there a way by simply pushing a button?


Go to Tools - Options - File Types, click on the "New" button on top right, select XML as file type, click on 'OK'. On the next screen enter a name for the new filetype into the first field and click 'Next'. In the window 'XML Settings Import', select "Define settings based on INI, ANL, XML or ITS rule file' and navigate to the XML document.
The same procedure applies when you want to create a filetype based on an .INI file.

jykim wrote:
And what you're explaining is only for 2009 or does 2007 contain similar functions?


2007 also allows you to edit the entities in a DTD, but it is far less flexible in the configuration possibilities than Studio 2009 is.

Walter


Direct link Reply with quote
 


To report site rules violations or get help, contact a site moderator:


You can also contact site staff by submitting a support request »

What should a 'perfect' XML and XLIF file look like for Trados?

Advanced search







CafeTran Espresso
You've never met a CAT tool this clever!

Translate faster & easier, using a sophisticated CAT tool built by a translator / developer. Accept jobs from clients who use SDL Trados, MemoQ, Wordfast & major CAT tools. Download and start using CafeTran Espresso -- for free

More info »
Wordfast Pro
Translation Memory Software for Any Platform

Exclusive discount for ProZ.com users! Save over 13% when purchasing Wordfast Pro through ProZ.com. Wordfast is the world's #1 provider of platform-independent Translation Memory software. Consistently ranked the most user-friendly and highest value

More info »



Forums
  • All of ProZ.com
  • Term search
  • Jobs
  • Forums
  • Multiple search