Different structure XML to be translated in SDL Studio

Hi,

I have a set of XML files to be translated in SDL Studio.

However, each file has a different structure and a different tags with content for translation.

Example:

File 1 - text for translation:

<original_fullname>Technology Structure</original_fullname>

<original_shortname>Technology Structure</original_shortname>

                <title>News forum</title>

File 2 - text for translation:

<name>New</name>

<name>Turning Technology</name>

<name>Match the following G&amp;amp;M code elements with the parallel elements in the English language.</name>

<questiontext>Match the following code elements.</questiontext>

<generalfeedback>Characters are the …. command.</generalfeedback>

<answertext>Letters</answertext>

And in other files the content for translation is between different tags.

Usually, I was adding the XML as the settings definition to be based on. But now, I have many different XML files as indicated.

Can you please advise how should I prepare the structure and the file type?

It is really urgent !

Thank You & Best Regards

Fouad

Parents
  • Hi Fouad,
    The XML parser considers all elements that are not mentioned in a rule as "translatable (but not in protected content)" and as "structure tag" and all attributes as not translatable. So actually, you don't have to enter any rules at all, if you want to translate all elements in your file, and there are no inline tag (like in your example).
    If you know that a specific element is not to translate, enter a corresponding rule.
    If you want to translate a certain attribute, then enter a corresponding rule as well.
    If there is a couple of inline tag, define them in a rule.

    For the file detection, it seems that a * in "Any of the following root elements" accepts all possible root, in case you have different roots. (I've just tried this)

    Kind regards
    Sébastien

Reply
  • Hi Fouad,
    The XML parser considers all elements that are not mentioned in a rule as "translatable (but not in protected content)" and as "structure tag" and all attributes as not translatable. So actually, you don't have to enter any rules at all, if you want to translate all elements in your file, and there are no inline tag (like in your example).
    If you know that a specific element is not to translate, enter a corresponding rule.
    If you want to translate a certain attribute, then enter a corresponding rule as well.
    If there is a couple of inline tag, define them in a rule.

    For the file detection, it seems that a * in "Any of the following root elements" accepts all possible root, in case you have different roots. (I've just tried this)

    Kind regards
    Sébastien

Children