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 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
Hello Yael,
The problem is not the settings file it's your xml file itself. The file should be encoded UTF16-LE and it should have a BOM (Byte Order Mark). This file you provided has no BOM and whilst the decl;aration says UTF16 a decent text editor will confirm it's actually UTF8.
Try this one. You also get a warning when you open the file in Studio that gives you a clue the file has ben corrupted somewhere... not a Studio problem:
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
As I said, I added the BOM back and made sure the file was UTF16. This is nothing to do with Studio at all. Many parsers will default to UTF8 if the BOM is missing and this is what happened here. You need a decent text editor to be able to see this and correct it... I use EditPadPro which allows me to see the difference and correct it like this, but I believe NotePad++ can do this too and that one is free.
Your new file:
My corrected file (and your very first sample):
If you are going to work with files like this then I'd recommend you get a decent editor, otherwise it's very easy to corrupt the files yourself, never mind any problems that can occur through doing things like copying files from a MAC to a Windows environment, or emailing them... could be many things that cause this. The best solution is to always make sure the xml files are zipped before moving them around.
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
Translate
