Hi,
I have a XML file in the following structure:
<GIS_HELLO_WORLD string="Hello World" maxlength="11" g="1" w="1" r="0" />
<GIS_PLEASE_WAIT string="Please wait" g="0" w="0" r="0" a="1" />
<GIS_NOTICE string="Notice" g="0" w="0" r="0" a="1" />
We need to translate only the text after "string=".
Studio can't handle this type of file and I want to know how can I add or edit a XML file type to be able to show only the relevant text for translation.
Thanks
Fouad
Hi Fouad
Studio has no issues dealing with this type of file - all you need to add is either a rule for the 'string' attribute in the parser rules or an XPath rule to deal with all elements containing the 'string' attribute. Sample file and filetype attached containing an XPath rule to deal with all instances of the attribute 'string'. I added <test> as the root element to the sample file.
I hope this helps.
Thanks
Fas
Fas Aziz | Desktop Life Cycle Service Manager | SDL | Support Operations, Support Lifecycle
Paul Filkin | RWS Group
________________________
Design your own training!
You've done the courses and still need to go a little further, or still not clear?
Tell us what you need in our Community Solutions Hub
This filetype will only work with XML files with the root element <test> - if your root element is not <test> then this filetype will not work for you. Open your XML file in a text editor take note of the root element (outermost element) and then add this to the 'Detection' settings under the XML filter I sent you:
Hope this helps.
Thanks
Fas
Fas Aziz | Desktop Life Cycle Service Manager | SDL | Support Operations, Support Lifecycle
Translate
<?xml version="1.0" encoding="utf-16"?>
<data version="1.0.1" encrypted="0" dataType="StringData">
<dictionary language="enu">
<GIS_HELLO_WORLD string="Hello World" maxlength="11" g="1" w="1" r="0" />
====== GI Android Strings ================================ -->
<GIS_M12A_ENTERPRISE string="M12A Enterprise Holter System" g="0" w="0" r="0" a="1" />
<GIS_CHOOSE_DEVICE string="Choose device" g="0" w="0" r="0" a="1" />
<GIS_DONT_SHOW string="Don\'t show this hint again" g="0" w="0" r="0" a="1" />
<GIS_REQUIRES string="requires at least" g="0" w="0" r="0" a="1" />
<GIS_IS_REQUIRED string="is required" g="0" w="0" r="0" a="1" />
<GIS_CHARACTERS string="Characters" g="0" w="0" r="0" a="1" />
<GIS_ATTENTION string="Attention!" g="0" w="0" r="0" a="1" />
<GIS_CONNECTION_TIMED_OUT string="Connection timed out" g="0" w="0" r="0" a="1" />
<GIS_NO_REPORTS string="There are currently no reports associated with this subject" g="0" w="0" r="0" a="1" />
<GIS_REPORTS string="Reports" g="1" w="1" r="0" a="1" />
<!-- ======================== GI New Strings ================================ -->
<GIS_SAVING string="Saving" maxlength="10" g="1" w="1" r="0" a="1" />
<GIS_HR_TREND string="HR Trend" maxlength="10" g="1" w="0" r="0" />
<GIS_UPDATE_EXPORT string="Enable Update Export" maxlength="25" g="1" w="0" r="0" />
</dictionary>
</data>
Fouad - try the attached filetype settings.
Thanks
Fas
Fas Aziz | Desktop Life Cycle Service Manager | SDL | Support Operations, Support Lifecycle
Might be worth you reviewing this article that may help you do this yourself in the future.
Paul Filkin | RWS Group
________________________
Design your own training!
You've done the courses and still need to go a little further, or still not clear?
Tell us what you need in our Community Solutions Hub
Hi Yael,
There two places you should read that will explain what Fas did.
Why do we need custom xml filetypes
More Regex? No it's time for something completely different.
Both these articles will explain this and more. But in a nutshell Fas just used two simple xpath rules as he explained. First this one set as non translatable:
//*
This basically means don't translate anything. The star is a wildcard meaning select everything. So all he did was ensure that nothing is added for translation at all.
Next he added a rule to extract exactly what you wanted:
//*/@string
This just means extract the text from all attributes named string. So in Studio you see this:
The only other thing he did was to ensure the xml file was recognised by adding the root element of data into the detection box.
Not too tricky!
Paul Filkin | RWS Group
________________________
Design your own training!
You've done the courses and still need to go a little further, or still not clear?
Tell us what you need in our Community Solutions Hub