Pavlos Martopoulos

I don't have time to test, but have you tried the following Xpath?

/map/data[not(@translate)]/@value

It makes sure that the data element does not contain the translate attribute.

Jesse Good

Thanks for the XPATH, but it doesn't work.

I've tried to set the following to 'not translatable', it works on XMLSpy, but doesn't do the job in Studio

I think it has to do with rules' order. 

BTW, in your post you mentioned wrong guy Please mention NLG GmbH instead.

Hi Pavlos, I noticed in the schreenshot that you used "/map/data[(@translate)]/@value", not "/map/data[not(@translate)]/@value". Does this help? With best regards, Nico.

Hi Pavlos, I noticed in the schreenshot that you used "/map/data[(@translate)]/@value", not "/map/data[not(@translate)]/@value". Does this help? With best regards, Nico.

Nico van de Water

Nope, it doesn't work

NLG GmbH

I see... Even with //*[@translate='no'], that will be ignored because of /map/data/@value.

Here is one more shot:

//data[not(@translate='no')]/@value

According to this post, the not function should work, so I'm not sure why it isn't working.

Jesse Good

Thanks for the XPATH, this exports only the relevant text for translation.

Please note this is only a sample of the 650 files, so I wouldn't prefer writing custom XPATHs for every each element/attribute.

My question is still not answered (despite your efforts ): why these rules don't work?

NLG GmbH

I can get this which is what I think you're after using a custom XML filetype:

Or... using the dita filetype you used (except v3 as I'm using 2021):

Just use these rules:

//map/data[not(@translate='no')]/@value
//map/@title
//topicref[not(@locktitle='no')]/@navtitle
//*

NLG GmbH said:

My question is still not answered (despite your efforts ): why these rules don't work?

You said this earlier:

NLG GmbH said:

• 'value' of 'map/data' elements when are not followed by 'translate=no'

And your very first rule says translate all the value attributes when they are in map/data.  Complete contradiction.

Generally you don't seem to have applied your requirements in a logical way... look more like guess work.

Thanks, now it works.

Paul Filkin: as you may guessed, I provided only the relevant rules for the ditamap files. For this project we have > 600 dita/ditamap files with ~500 XPaths, so something may have mixed.