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 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.......
Hello! I hope someone has the answer to this. I have been able to print an entry from my termbase into a PDF file, using the "print this entry" command and saving it as PDF. I am doing it this way because each entry has images, and the export options don't work well with images. However, when I'm done populating all of the termbase, I would like to print it out as a whole in PDF. It would be too time consuming to do it one by one. I'm doing a research paper and I would like for it to have a good presentation. Any tips on how can I achieve this? I have SDL Multiterm 2019. Thank you!
Use "Word Dictionary export" from Termbase Management instead. This will export the complete TB to RTF format, which you can print or simply convert to PDF in Word.
Not always a straightforward thing to do, but you have three options I'm aware of:
Of them all I think Publishing MultiTerm should be the best option.
Paul said:The RTF coding in this option is a bit of black art and it's so old I don't know anyone who knows how it works to be able to configure it anymore!
I think there are no configuration options for this export. You can chose sorting and apply a predefined filter, but that's particularly all. However, the exported file can easily be postprocessed in Word, using search and replace (formats and paragraph marks, in particular). I have done this some few times for a customer to achieve better (desired) formatting. Not really a big deal.
it is configurable and certainly desirable. If you had a large termbase and wanted a different content/layout then you certainly wouldn’t want to do this in Word!
Paul said:it is configurable and certainly desirable. If you had a large termbase and wanted a different content/layout then you certainly wouldn’t want to do this in Word!
Of course not, but please enlighten me, where can I configure the Word export. I fail to see more options than sorting and filtering in MT...
BTW, I just tried to export a simple TB to rtf with MT2021b and the result is an empty file...
as I said... it’s a black art!
copy the files and when you edit it to I’ll see you have more options. I’m out at the moment so if you’re still stuck I’ll explain later.
OK, I see - when I copy the Word export definition, I can edit it with some more options. Tricky, but I understand now.
Hello Jerzy, thank you for your reply. When I export the termbase using that option, it only exports a few fields for some reason: only those that are at entry level and one of the target languages equivalent. Also, it doesn't export the image (it exports only the image name). Furthermore, my termbase is multilingual and it only exports one target language, and not all three included. Any thoughts?
Hello Paul, thank you for taking the time to reply. I have verified all of your options:
1. It doesn't export the image (only the image name) and it certainly looks like a file that only black arts can handle. There is a lot of history info throughout the term record (my name as the person who modified it and dates and times) that would make editing and formatting it a hassle. 2. It looks pretty cool, but 1250 euros is out of budget. I see there is a trial version, I might check it towards the end of the project.3. Unfortunately, doesn't support Multiterm 2019.I am enclosing an image of my PDF experiment. It looks pretty good for presenting in the kind of work I'm doing. I'd love for an option to do all the termbase like this. I hope you have more thoughts!
Hello Jerzy. My term record has a lot of fields and editing in Word would be a very time consuming task. I already exported one and it looks awful. I hope another option will come up!
Jerzy, where do I find info on what is a Word export definition and how to edit it? Thank you!
I'm not sure if it will export the images, but you can indeed configure the export, when you copy the export definition in MT Termbase management instead of simply processing it. Then edit the copy of the export definition, which you can then configure.
I had a quick test with the free appstore plugin using this:
But this won't meet your needs either as you only get this:
On the RTF export:
Andrea Herrera said: It doesn't export the image (only the image name) and it certainly looks like a file that only black arts can handle. There is a lot of history info throughout the term record (my name as the person who modified it and dates and times) that would make editing and formatting it a hassle.
It might be possible to correct this, but it is very tricky. Adding the media image just gives me this as opposed to the image itself:
And you'd need to be able to understand how to use RTF coding to improve this format. This might be helpful in terms of getting your formatting right if you have the time and energy to figure it out, and then you'd only have to add the images which would be a lot less work than you have right now:
For a long time I've had an idea to create plugin or an app to do a better job of this but there has never been enough demand for me to raise this to a higher level in the priority list. I might try and see whether we can do something after we've got Trados 2021 out of the way (SDLCOM-2036). Probably too late for you unfortunately but I think it'd be good to have a better export option for something like in the future.
Andrea Herrera said:3. Unfortunately, doesn't support Multiterm 2019.
I don't think the version of MultiTerm is relevant really. So I just changed the requirements for the app and now you should be able to download and test it. Perhaps you can use this in some way to at least get out the main details?
Thank you, Paul. So in the first part of your exercise, you have encountered the same issues I had: not only not getting all of the fields exported, but getting just two languages exported from a multilingual termbase. I see RTF looks pretty scary, as in every thing we don't know. Once you read carefully the coding, you kind of start making sense of the language. I will try to look further into this.It would be late for me, yes, but sounds like a super idea. I really think it could be a huge plus to Studio to be able to consider terminology also as a standalone product, which does already, but as we can see in my case, it could be enhanced. This is, printing out a termbase into a really good looking dictionary format, specially if you have more information (like in my case). I have worked in companies that have glossaries and style guides available to the entire company to check out and use. This could be a way of translation departments sharing everything they have already worked on in a very user-friendly format. More so, appealing to terminologists, as myself, to use this tool for purely terminology purposes. Maybe you could consider including a Bibliography manager section...it would be super helpful...