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.

Forum.zip

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!

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:

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.

Still getting warnings even after changing the encoding.

Pre-Scanning Failed to identify the file type.. It is about the "Unexpected XML declaration must be the first node in the document, and no white space characters are allowed to appear before it. Line 1, position 4."

The file looks OK - and no white spaces in it.

Is this the XML corruption that you talked about?

BR

Fouad

It seems that the difference between the first version that we managed to work with and the current version is the additional "maxlength" option in the each string (I've run beyond compare between both files). This option was not in the first file and the settings that you sent me worked perfectly.

<GIS_PLEASE_WAIT string="Please wait" maxlength="20" g="0" w="0" r="0" a="1" />
<GIS_NOTICE string="Notice" maxlength="15" g="0" w="0" r="0" a="1" />

Can you please advise?

BR

Fouad