SDL Trados Studio
SDL Trados GroupShare
SDL Trados Business Manager
SDL Trados Live
SDL Speech to Text
SDL Managed Translation - Enterprise
Translation Management Connectors
SDL LiveContent S1000D
SDL Contenta S1000D
SDL Tridion Docs
SDL Tridion Sites
SDL Content Assistant
SDL Machine Translation Cloud
SDL Machine Translation Connectors
SDL Machine Translation Edge
Tridion Docs Developers
SDL User Experience
Language Products - GCS Internal Community
SDL Community Internal Group
SDL Access Customer Portal
SDL Professional Services
SDL Training & Certification
Language Technology Partner Group
SDL Academic Partners
SDL Approved Trainers
SDL Enterprise Technology Partners
ETUG (European Trados User Group) Public Information
Machine Translation User Group
Nordic SDL Tridion Docs User Group
SDL Tridion UK Meetup
SDL Tridion User Group New England
SDL Tridion West Coast User Group
SDL WorldServer User Group
Tridion Docs Europe & APAC User Group
Tridion User Group Benelux
Tridion User Group Ohio Valley
SDL MultiTerm Ideas
SDL Passolo Ideas
SDL Trados GroupShare Ideas
SDL Trados Studio Ideas
SDL Machine Translation Cloud Ideas
SDL Machine Translation Edge Ideas
SDL Language Cloud TMS Ideas
SDL Language Cloud Terminology Ideas
SDL Language Cloud Online Editor Ideas
SDL Managed Translation - Enterprise Ideas
SDL TMS Ideas
SDL WorldServer Ideas
SDL Tridion Docs Ideas
SDL Tridion Sites Ideas
SDL LiveContent S1000D Ideas
SDL Contenta S1000D
SDL XPP Ideas
Events & Webinars
To SDL Documentation
To SDL Support
What's New in SDL
Detecting language please wait for.......
Is there a location on this community site where I can ask terminology-related questions?
It is a very interesting topic. Since it has been a question for me too somehow, I have just done a small test as below.- Creating one entry with 3 terms in French (one-to-three)- Creating three entries for each pair (one-to-one)
As the screenshot shows, there is no big different on BWB.
However in Studio, it looks different as below.
Either way, the term recognition could work correctly. So I think there is no big difference in those two styles so far, but some considerations as I wrote below.When I tried to create the three entries in one-to-one style, I was prompted by a warning by WorldServer as: This term has previously been proposed: associate(Approved)Because of this warning, I can assume WorldServer is expecting terms are created in one-to-multi style.
Another consideration is, when you work with Excel files for the terms by exporting and importing.If you are collecting new terms in your local Excel file, and you import it to WorldServer sometimes, we should carefully determine which style is the best.If you export one-to-multi style in "Delimited File: Simple Format", it will be a CSV as below, that means you need to create your Excel in a same manner.
For one-to-one style, it will be:
So I think one-to-one style might be handy for us, when we need to think about import/export.
Of course, there are some other considerations like in case of using attributes, TD Groups, etc.
Thank you for your very thorough analysis. You are absolutely correct that there are issues with the export functionality. I tested the one-to-many scenario, exporting as a Delimited file and a CSV file. The Delimited format did not export any of the translations. The CSV format exported only the first translation; omitting the other two translations.
Nevertheless, as you point out, there is an issue with the one-to-one scenario during input, where WorldServer is indicating that multiple entries for the source term exist -- message: "This term has previously been proposed: associate(Approved)". Therefore, the best format I think is the one-to-many scenario as:
This will solve the input part of this issue however, I still need to research the best method to export so that all translations for a source term are exported correctly.