![]() ![]() One (good) use is to convert our XML file into an HTML file showing us three columns: ID, text and translation – and tell Trados in the file type options to use that. Not only can XSL present XML data in a number of other languages, it also lets you convert one XML file into another, use variables, copy and move elements, and even use control structures such as if. XML and XSL are like HTML and CSS on steroids. But let’s try using only XML this time, shall we? Been there (article in German), it works quite nicely and you automatically have the source text in TagEditor’s source column and any existing translations in the target column. TXT, use Trados text table input filter to read and translate the file and turn it back into an XML document with another RegEx. One way to achieve this is by using a text editor with Regular Expression Search&Replace functionality to turn the whole XML thing into a tab-separated table, save as. File preparationĪpparently, what we need to do before translating the translation elements is to copy the source text, preferably without destroying extant translations. However, telling Trados to parse the translation elements as translatables will lead to English text in TagEditor’s German source column for strings 001 and 003, and you won’t get to see string 002 at all, because it’s empty and nobody would ever need to translate „nothing“, right? And on top of that, you won’t ever get to see the German source text. ![]() Usually, you would want to write your translations into the translation elements. So, we have already translated strings, empty strings and strings that need to be edited. Unfortunately, our virtual client has not marked that string as modified, for example by setting something like a new or modified="yes" attribute on the string or text element. I have inserted three use cases: The string is already accurately translated, the string is untranslated (empty translation tag) and the string is translated but the translation doesn’t match the text (here: the company name has changed). Attention: If the file is saved as ANSI instead of UTF-8, the Umlaut and Ampersands might throw parsing errors and should be replaced with Entities! ![]() Inside, we can see three string tags with their IDs as attributes, each with one text and one translation tag with the actual source and target content. The mandatory „root element“ uistrings encompasses all other tags, it also holds the source and target languages as attributes. The file starts with the XML file declaration including version and encoding. XML NOTEPAD 2011 DEUTSCH CODEBe careful with those tags! Dear Clients: Using CDATA may lead to messed-up code during the translation, please try to use namespaces instead to enclose HTML in XML, then they will be correctly parsed and displayed as immutable tags and the translator is less likely to forget or mangle a tag somewhere. Sometimes, clients will wrap HTML into those tags as Character Data ( ), which means you will get to see every tag in the translation environment as plain text. XML NOTEPAD 2011 DEUTSCH PLUSLet’s first have a look at the file we want to translate with Trados (or the free/open source OmegaT plus Okapi Rainbow combo, or any other CAT tool): If you want to know more, have a look at the XML and XSLT pages over at W3schools. This basically means that while HTML is mainly used to display structured information to the human user, XML’s primary purpose is to contain structured information of any kind for humans and machines alike, and let separate stylesheets worry about how it will be displayed (e.g., as XHTML, PDF, LaTeX, CSV tables, plain text, you name it). Looks similar to HTML, but you get to define the valid structure and tags in your own DTD. XML NOTEPAD 2011 DEUTSCH HOW TOLet’s have a look at how to prepare those files with XSLT!Īlright, you have seen XML already, don’t you? Right. Worse, if the client happily announces that the source of some of the translated strings has changed, things get more than just a bit tricky. But if the file is already partly translated, things get a bit more tricky, since you want to avoid overwriting existing translations. If the target strings are empty, you can easily copy the content over and translate right away. Unfortunately, this means that the source strings will be overwritten with the translation - a bad idea if the source file is already bilingual XML that contains source and target language strings in matched tags. The market leader of Computer Aided Translation (CAT) Tools, SDL’s Trados Studio, allows to translate XML with an „Any XML“ input filter, which includes an assistant that lets you choose which XML tags and attributes will be visible in the editor as „translatables“. More and more translation clients, especially in the Web industry, but also in application I18N/L10N, use the versatile XML standard for translation purposes. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |