Some of these cookies are essential to the operation of the site,
while others help to improve your experience by providing insights into how the site is being used.
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.
Guarantee a unified, consistent and high-quality translation with terminology software by the industry leaders.
SDL MultiTerm 2019 allows translators to create one central location to store and manage multilingual terminology, and with SDL MultiTerm Extract 2019 you can automatically create term lists from your existing documentation to save time.
PerfectIt helps deliver error-free documents. It improves consistency, ensures quality and helps to enforce style guides. It’s a powerful tool for pro users, and comes with the assurance of a 30-day money back guarantee.