To be on the safe side, you will need to define a new filetype for your XML.
The process is roughly as follows:
1. Exclude all untranslatable sections from display in the Editor (i.e. also from the analysis)
2. Define all translatable content between the respective XML tags as translatable (i.e. include it in the analysis)
3. Use the following regular expression to display embedded HTML code as tags: </?[a-z][a-z0-9]*[^><]*>
The contents of this post will automatically be included in the ticket generated. Please add any additional comments or explanation (optional)
To do this you need to only parse the translatable text into Studio. This is because it is the text in the editor that will be counted. To do this, if you are seeing code snippets in the editor, you need to create a custom filetype.
This is not always too tricky... depends on the xml file you have... but there are some examples below that might shed some light on this topic for you if you are unfamilar with this process.
Kilgray's memoQ is the world's fastest developing integrated localization & translation environment rendering you more productive and efficient.
With our advanced file filters, unlimited language and advanced file support, memoQ translator pro has been designed for translators and reviewers who work on their own, with other translators or in team-based translation projects.
Manage your TMs and Terms ... and boost your translation business
Are you ready for something fresh in the industry? TM-Town is a unique new site for you -- the freelance translator -- to store, manage and share translation memories (TMs) and glossaries...and potentially meet new clients on the basis of your prior work.