Detecting language please wait for.......
I have followed the steps for converting an Excel Glossary using MultiTerm Convert. (I kept receiving error messages using Glossary Converter and the suggested Glossary Converter Beta version also did not function correctly).
When I come to the importing stage, I click on Termbase Management but nothing happens. No Import option appears.
I presume I need this to happen in order to eventually make an Autosuggest dictionary?
Hi Clare Rubin
It looks as though you may have inadvertently closed the Catalog Categories that contain the features you are looking for. Try resetting your window layout:
I think AutoSuggest dictionary is a resource from the past, when Studio was not able to utilize "live" TMs to create partial matches and dig out words for AutoSuggest feature. Now you can start a brand…
Here's my screen.
Have you created an empty termbase using the definition obtained during the convert process? With no open TB in MT there are no options in Termbase Management...
Does not look like proper termbase. Do you understand German?
Sorry, no I don't.
As far as I am aware (I am still very new to this) I created an empty termbase and have a 3.2KB .mtf file ready to go.
Clare Rubin said:I presume I need this to happen in order to eventually make an Autosuggest dictionary?
Also note that you are creating a termbase here. You can use this to get auto-suggestions from your termbase, but this is not an autosuggest dictionary. The latter is created from your Translation Memory if you have an AutoSuggest Creation licence to accompany the Freelance Verion or a Professional licence.
Brilliant. Thank you, Paul. That is exactly what had happened.
In response to the Autosuggest dictionary point, I thought that I was in the last few days (if not day) of my first month (my SDL Language Cloud subscription started on the 14th April) and so I was hoping to use all of my glossaries to create one while I still had free access in my Freelance edition. Despite seeing somewhere that I had 30 days, the option is now greyed out so I must have run out of time. I may well just use the termbase I have finally successfully created instead, as per your suggestion.
Will it create issues if I move it from the SDL Multiterm Termbases folder to a folder on my desktop for ease of access?
Clare Rubin said:I was hoping to use all of my glossaries to create one while I still had free access in my Freelance edition.
Just to clarify... glossaries are not used to create an autosuggest dictionary. This is a feature based on your Translation Memories. Autosuggest can come from many sources... maybe review this "old but still usefu" article:
Today out of the box autosuggest comes from these sources:
So you have "Translation Memory and Automated Translation" which means hits from your translation memory and also concordance searches can feed the autosuggest; and also fragment matches which is a sort of dynamic "autosuggest dictionary". So I would not worry too much if you didn't create any dictionaries while the trial was still active. Dictionaries are static and need to rebuily every now and again to make sure they contain all your latest work. Fragment matching uses your live TM so you have this kind of feature out of the box anyway.
Clare Rubin said:Will it create issues if I move it from the SDL Multiterm Termbases folder to a folder on my desktop for ease of access?
Only if you don't tell Studio where you moved them to. It's no problem to move them wherever you like, but make sure you also remove them in Stdio and then add them back in again from their new location. You'll probably be prompted when Studio can't find them.
I think AutoSuggest dictionary is a resource from the past, when Studio was not able to utilize "live" TMs to create partial matches and dig out words for AutoSuggest feature. Now you can start a brand new project with a brand new empty TM to see Studio starting giving you AutoSuggest hits from this very TM.
This way you are getting all actual hits without a need to do anything, while with an AutoSuggest dictionary you have only a static collection of items extracted from your TM at day X. After a certain period of time the items there are outdated and you would need to create a new ASD again.
From my point of view using an ASD does not help at all - at least not, if you are using all the features available in S2019. To utilize the full power, switch UpLift in your TMs and projects on, switch AutoConcordance on and than change the general settings to this:
Thank you. To clarify, I was attempting to convert the Excel files into a format which would be available as a resource for an Autosuggest dictionary. I got confused between Translation memories and Termbases but at least managed to convert all my excel glossaries into one giant Termbase which I successfully imported into my project shortly before it disappeared into the mist.
Could you tell me how to remove the termbases in Studio, please? I seem to have many SDL-related folders scattered about now.
Sorry this answer was for Paul. Jerzy, many thanks for your reply. I have printed the screen shots out and hope to apply them if I can resolve the other missing project issue.