As I can see it, synonyms occupy one line each. In multi-synonym termbases, this entails the need for long scrolling to see the terms. Is it possible somehow to replace the new line synonym separator with a space or comma or whatever?
there is no default function for that, I guess.
It is just a matter of changing a delimiter, there could be an option or an easy hack for it.
Out of the box there is no option for this and that would be because the termbase is built on the basic premise there could be multiple fields on a term and so the simply way to handle this is treat each term as a separate object and not as a word or phrase that will never have accompanying data.
I think, if you have any development skills, the solution could be fairly simple as this is only a view at the end of the day. So you could create your own termbase view designed to represent the data as you wish it to be displayed for your particular data structure. I think the code in this app. would contain an example of how the view is achieved and then it's just a matter of using a stylesheet after that:
https://github.com/RWS/Sdl-Community/tree/master/IATETerminologyProvider
I hope that helps you. I imagine Kelly could do this easily enough if he's interested.
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
post a brief sample file
What format?
Exactly, Paul, only a view. I think that this is a typical termbase use by translators (plain two-column, source-target), so it would be a view worthy of being included in the software.
it would be a view worthy of being included in the software.
For that your best bet is to raise an idea:
https://community.rws.com/ideas/trados-portfolio-ideas/i/multiterm-ideas
That way the product managers can pick it up for consideration.
My team, if nobody else does it, could pick this up as a plugin for Trados Studio (for the AppStore) and then anyone who wanted this as an option could install the plugin and use this new view as their preferred one. Perhaps, if you have some ideas around what this should look like (in addition to just wrapping and separating with commas) and anything else you think you would like to see, you could share it here. Screenshots mocked up in powerpoint for example will be fine.
I can't promise we'll get to this quickly but I don't think it's tricky so maybe we can squeeze it in if Kelly doesn't get there before us.
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
Thanks Paul!
Yes, I wanted to do that beforehand but for some reason I had to get reauthorized for that section of the site. Small test termbase attached here:
community.rws.com/.../provide-a-term-wrapping-view-for-term-recognition-window
I hope the Company make a good news soon
Before that, try some bandaid of mine
Check it out at AHK section
The thread Kelly refers to is this one:
Very clever solution.
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
The thread Kelly refers to is this one:
Very clever solution.
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
Paul, amazing, providing the answer before it is asked. This is what support should be like 
Yes, clever solution, but the same thing can be done in a much easier way with glossary preparation in Excel, i.e. simply do not parse synonyms, saving Kelly all that hard and admirable coding! Really impressive what can be done with AHK, indeed, if one knows what to do.
Much easier with Excel ?
Sounds like, you do not need CAT at all
You just use P&P (Pencil and Paper) that is all you needed.
That is much and much easier.
Perhaps I was not clear enough. My starting point for the termbase was Excel, where column one was source text and column two, translations (comma delimited). What I did in order to produce the termbase was replace commas with pipe and run the file in Glossary Converter (checking the option for synonyms). In order to have the same result as one gets with your hack, I could simply not have replaced the comma with the pipe and simply run with Glossary Converter (or replace with pipe, but not enable synonym processing).
Translate
