• State Suggested Answer
  • Replies 5 replies
  • Answers 2 answers
  • Subscribers 432 subscribers
  • Views 4317 views
  • Users 0 members are here
Options
Related

Verification error : Sequence contains more than one matching element

Cristi Necula

Hello everyone, 

I have spent quite some time on trying to figure this out on my own yet I could not reach a solution. 

I have received a TBX file from a client out of which I have created a multiterm Termbase. The provided TBX contains allowed and forbidden terms. I have set these up as a pick list in order to use the verification check in studio for a translated file. 

Screenshot of Trados Studio showing Descriptive Fields with a picklist for 'State concept' including 'allowed', 'prohibited', and 'not decided'.

If I run the verification check as normal I run into no issues. By as normal I mean with the following settings in studio:

Screenshot of Trados Studio verification criteria settings with options for checking non-usage of target terms and forbidden terms.

As soon as I change the setting to include the distinction between allowed and prohibited i cannot run the verification check anymore.

Like so : 

Screenshot highlighting the 'Select forbidden values' setting in Trados Studio with 'prohibited' checked under verification criteria.

This is the error i receive in studio when verifying my file with the above setting (stack trace included in case needed) : 

Error message in Trados Studio stating 'Sequence contains more than one matching element' with a stack trace of system details.

I have found this article about the issues : https://gateway.rws.com/csm?id=kb_article_view&sysparm_article=KB0030918 but it does not really give me a path to solving it as I cannot find duplicate terms and I am making sure I do not ignore sublanguages when creating the termbase. 

Any help with this would be greatly appreciated. I have tried this in both Studio 2019 and Studio 2015 

I would be able to provide the files in question but on a public forum. 

Regards,
Cristian 

Generated Image Alt-Text
[edited by: Trados AI at 7:38 PM (GMT 0) on 28 Feb 2024]
emoji
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents
  • 0

    Perhaps ths article makes the resolution a little clearer... same one, just a different layout:

    https://gateway.rws.com/csm?id=kb_article_view&sysparm_article=KB0039916

    Can you share a screenshot of your Termbase Management View here:

    Screenshot of Trados Studio's Termbase Management View showing a list of languages with a sub-language added to an existing main language.

    I deliberately addeda sub-language to an existing main language.

    If you definitley don't believe you have done any of the things noted in the article you can share your termbase with me and I'll be happy to see if I can find a problem - pfilkin@sdl.com

    Paul Filkin | RWS Group

    ________________________
    Design your own training!
    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

    emoji


    Generated Image Alt-Text
    [edited by: Trados AI at 7:38 PM (GMT 0) on 28 Feb 2024]
  • 0 in reply to Paul

    Hi Paul,

    Thank you very much for taking a look at this.

    Here is the requested screenshot.

    Regarding the point in the article I can confirm as follows:

    • your termbase has more than one sub-language for a main language. For example English (United Kingdom) and English (United States). Not applicable

    • the XML file you import into the termbase contains for example English (United Kingdom) and English (United States) entries that each have same terms. The distinction from en-GB to en-US is made via a descriptive field in the TBX I was provided with,  while the actual languages of the TBX are only 2   and . Therefore I do not think this applies. I have not actually added this descriptive field in the termbase as I do not think it is relevant for the purpose of my test.

    • on page Step 3 - Validation Settings of the SDL MultiTerm Desktop/Administrator Import Wizard, the Ignore sub-languages option is ticked/enabled/active. Not applicable

    • it was not considered to create a custom import definition to import converted (via SDL MultiTerm Convert) terminology into the existing  Termbase and avoid the import of existing/duplicate terms. Not applicable

    Let me know what you think and thank you once again.

Reply
  • 0 in reply to Paul

    Hi Paul,

    Thank you very much for taking a look at this.

    Here is the requested screenshot.

    Regarding the point in the article I can confirm as follows:

    • your termbase has more than one sub-language for a main language. For example English (United Kingdom) and English (United States). Not applicable

    • the XML file you import into the termbase contains for example English (United Kingdom) and English (United States) entries that each have same terms. The distinction from en-GB to en-US is made via a descriptive field in the TBX I was provided with,  while the actual languages of the TBX are only 2   and . Therefore I do not think this applies. I have not actually added this descriptive field in the termbase as I do not think it is relevant for the purpose of my test.

    • on page Step 3 - Validation Settings of the SDL MultiTerm Desktop/Administrator Import Wizard, the Ignore sub-languages option is ticked/enabled/active. Not applicable

    • it was not considered to create a custom import definition to import converted (via SDL MultiTerm Convert) terminology into the existing  Termbase and avoid the import of existing/duplicate terms. Not applicable

    Let me know what you think and thank you once again.

Children