Rossella Mastropietro

If you share a little snippet of the xml I'm sure this is a fairly simple question to help with.  The attribute they mention will be in the XML file itself so you need to create a non-translatable rule in Studio that uses the presence of that attribute to prevent the text from being exposed for translation.  B ut rather than we guess if you share a bit of the XML that has this attribute we can explain in a better way.

Certainly you will have to create a custom XML for this. 

Hi Paul,

Yes, I suspected that too but I couldn't find that attribute but please see a short paragraph where you can see the pre-translated text:

<p cms:rid="8b14xjjdda90012" cms:tstatus="Released" cms:tmatch="element1" cms:twords="42" cms:tlogicalid="x-svn:///svn/techdoc^/xml/lang/dk/release/F/EN/D010/Fans/TFC_(Bele)/TFC_roof_fans.xml?p=26009" cms:tpos="1.6.1.5" cms:trid="68w0g9t0b0n001t"><?Pub _font TypeSize="90%" Posture="italic"
?>(Erklæringen gælder kun for produktet i den stand, det blev leveret
og installeret i anlægget iht. den medfølgende installationsvejledning.
Forsikringen dækker ikke eftermonterede dele eller efterfølgende indgreb
i produktet)<?Pub /_font?></p>

Thanks a lot,

Rossella

Rossella Mastropietro said:

<p cms:rid="8b14xjjdda90012" cms:tstatus="Released" cms:tmatch="element1"

It's right there, the second attribute: cms:tstatus="Released".

Hi Rossella Mastropietro

Is your client suggesting you add this attribute to the XML?  Do you have control over the creation of the XML from the origin system?

Evzen Polenka

That would seem logical, but it's not what she said:

Rossella Mastropietro said:

using the attribute markfortrans set to no.

Why would you use something else when the instruction was for this?

The example was a translated text... so I assume that untranslated text is marked using different value of the attribute.
That's how CMSs usually work.

And the advise to "exclude elements from translation using the attribute markfortrans set to no" is apparently misleading - the advisor seems to assume that the translator is a programmer which knows how to manipulate XML content AND perhaps also that the translator is using a particular translation tool (probably some their internal tool originally intended to be used?) which uses this particular attribute.

Or, in other words, the advise assumes something (which is simply not true) and based on this assumption advises to do something (which would then be useless because the assumption is wrong) ;-)

Hi Paul,

I believe so but we don't have control over the creation of the XML from the origin system.

Hello Evzen,

Thanks for joining the conversation. Yes- I found that instruction misleading too because I COULD see cms:tstatus="Released" - what I COULD NOT was the attribute they were referring to and I thought the client should be the one inserting that attribute and us, the agency, just create the filter.

If I would be you, I would just identify which attribute/value to use for extracting only the untranslated strings and use it in a custom XML file type... then translate and done.

I see, so I think in this file it's cms:tstatus="In_Translation"

If I create that filter, will the report give me the word count only for those strings with this attribute, correct?

I see, so I think in this file it's cms:tstatus="In_Translation"

If I create that filter, will the report give me the word count only for those strings with this attribute, correct?

Yes... assuming you do everything correctly ;-)
You can always check the content in Editor, or use the Preview while creating the file type.