Just in case you don’t like to see all of this in wysiwyg mode don’t forget that you don’t have to. So you want to protect all the angle brackets and text between them. So for example, if you had an Excel file that contained things like this:Īnd then you opened this file in Studio you would see something that looked just like the Excel spreadsheet but what you would probably prefer is what it can be changed into as shown below: Now let me say that again in English… Studio can look in the content of the text that is extracted for translation and then pick out the bits you don’t want to see and convert them to tags. Studio uses a concept when creating custom XML files of parsing the file again based on the document structure type of an XML parser rule and replacing patterns you create in the parsed text with tags. This crops up quite a bit on ProZ so I thought it might be better to document it once and for all so I have something else to refer to in addition to the Studio help.
CHANGE ROOT PATH DOCUMENTS SDL TRADOS STUDIO HOW TO
But I digress… because this time I want to cover how to handle a similar problem when you find HTML or XML tagged content in an Excel file. In the last article I wrote I documented a method sometimes used by people to handle tagged content in a Word file… funnily enough I came across a Word file containing the XML components of an IDML file today and I guess it must have been prepared in a very similar way judging by the enormous number of tags using the tw4win style to hide them when opened by any SDL Trados version! Proof for me that this practice is sadly alive and well. By taggy files I mean “embedded xml or html content” that is written into an Excel file alongside translatable text.
0 kommentar(er)
