• State Verified Answer
  • Replies 2 replies
  • Subscribers 63 subscribers
  • Views 3510 views
  • Users 0 members are here
Options

XML Parser: specifying translation element

Russell Keeley

Hello,

I'm having a bit of a struggle getting my head round the XPath-but-not-quite-XPath used when configuring a custom XML parser. Specifically, I am trying to use the translation element to have Passolo read/write the translation from a different element to the source.

 

The screenshot below should hopefully illustrate my problem. From what I've read in the help files, the settings I am using should work. However, they don't so clearly I'm doing something wrong. Can anyone help?

 

Thanks,

 

Russell

 

Trados Studio custom XML parser configuration window with an XML Data Element dialog box open showing 'source' as Element name and 'translation@attribute:language=German' as Translation element.

 

 

Generated Image Alt-Text
[edited by: Trados AI at 5:07 AM (GMT 0) on 5 Mar 2024]
emoji
Rate translation
×
Suggest better translation
×
Parents
  • 0

    A few days ago I published an answer to another XML problem using a knowledge base article that I once created back in 2009 on the XML file parser. It contains some tips and I enhanced the article with more modern tips. So please first of all look into https://community.sdl.com/product-groups/translationproductivity/sdl_passolo/f/142/t/16929

    Unfortunately the literal language names that are used in your file are not supported by Passolo. Instead of the literal language names it must be one of these encodings:

    Trados Studio dialog box showing XML Language Element with options for Language Coding, including ISO and Windows Language ID codes.

    Then it would work but your rule must contain 2 different language codes. 

    Trados Studio XML Rule Configuration sample with Tree View, Definitions tab, and XML Language Element dialog box open.

    The data element then just needs source as the Data Element and translation as the Translation Element.

    Trados Studio XML Data Element configuration dialog box with options for Element Name, Translation Element, and Meta Data.

    So the problem that will remain is the unsupported language name.
    emoji


    Generated Image Alt-Text
    [edited by: Trados AI at 5:07 AM (GMT 0) on 5 Mar 2024]
Reply
  • 0

    A few days ago I published an answer to another XML problem using a knowledge base article that I once created back in 2009 on the XML file parser. It contains some tips and I enhanced the article with more modern tips. So please first of all look into https://community.sdl.com/product-groups/translationproductivity/sdl_passolo/f/142/t/16929

    Unfortunately the literal language names that are used in your file are not supported by Passolo. Instead of the literal language names it must be one of these encodings:

    Trados Studio dialog box showing XML Language Element with options for Language Coding, including ISO and Windows Language ID codes.

    Then it would work but your rule must contain 2 different language codes. 

    Trados Studio XML Rule Configuration sample with Tree View, Definitions tab, and XML Language Element dialog box open.

    The data element then just needs source as the Data Element and translation as the Translation Element.

    Trados Studio XML Data Element configuration dialog box with options for Element Name, Translation Element, and Meta Data.

    So the problem that will remain is the unsupported language name.
    emoji


    Generated Image Alt-Text
    [edited by: Trados AI at 5:07 AM (GMT 0) on 5 Mar 2024]
Children