Many solutions. The easiest would be using the bilingual Excel file type, confirming all segments and updating the TM. This way each corresponding pair of cells will be a TU in TM.

You can also store the file as tab delimited text, use Olifant to create a new TMX, place the txt there, store and use this for creating a TM.

Otherwise you can also separate the columns in two Excel files and align these.

Jerzy Czopik

The easiest may be the Glossary Converter... can go directly to an SDLTM with a drag and drop.

Hi MARIA-TERESA ALVAREZ-BENITO

Since Jerzy already pointed to two ways, I will point out another one...

Using the Glossary Converter, a free app from the SDL Appstore, you select "Sdl TM" as output format, drop the file on it and the job is done:

Select target format:

Select the direction of the TM:

Job done:

It really is that simple. Jerzy's solutions work just as well, but Olifant is the most tricky of the three mentioned here I would say.

Daniel

Paul & Daniel: thanks for pointing this out

Somehow I prefer not so automated solutions, but this is certainly an error. The Olifant is indeed quite tricky. The good about Olifant: you can edit the TMX. But TBH you can edit the Excel upfront, so GC is certainly the best here.

Hi. "The easiest would be using the bilingual Excel file type, confirming all segments and updating the TM. This way each corresponding pair of cells will be a TU in TM."

Can you tell me the steps? I don't know how to do that.

The Glossary Converter does not work. Here is what it says:

El archivo de la plantilla debe ser una base terminológica sdltb o un archivo de definición xdt.

Source: GlossaryConverter
en Sdl.MultiTerm.Tools.GlossaryConverter.Helpers.FieldResolver.TryToResolveFromTemplate(List`1 fields)
en Sdl.MultiTerm.Tools.GlossaryConverter.Helpers.FieldResolver.TryToResolveFields(List`1 fields, IFilter filter)
en Sdl.MultiTerm.Tools.GlossaryConverter.Helpers.FieldResolver.ResolveFields(List`1& fields, IFilter filter)
en Sdl.MultiTerm.Tools.GlossaryConverter.Filters.ExcelReader.GetFields(IFilter filter)
en Sdl.MultiTerm.Tools.GlossaryConverter.Core.FieldReader.Read(List`1 inputFilters, List`1 inputPaths)
en Sdl.MultiTerm.Tools.GlossaryConverter.Workflow.Converter.Convert(List`1 inputFilters, List`1 inputPaths, IFilter outputFilter)
en Sdl.MultiTerm.Tools.GlossaryConverter.Workflow.FileHandler.HandleMultipleFiles(List`1 files)
en Sdl.MultiTerm.Tools.GlossaryConverter.Workflow.FileHandler.ProcessFiles(List`1 files)
Program version 6.0.7588.22667

Windows version: Windows 10, Build 18363, 64 bit (Spanish (Spain, International Sort))

.net versions:
Client 4.8.03752
Full 4.8.03752
Client 4.0.0.0

Libre/OpenOffice version:

MultiTerm version: MultiTerm 15.0.0.0

22/01/2021 19:06 Could not find LibreOffice.CalcDocument\CurVer in registry
22/01/2021 19:06 Could not find opendocument.CalcDocument\CurVer in registry

<Settings version="3">
<AlwaysShowFieldsDialog>false</AlwaysShowFieldsDialog>
<CheckForUpdates>true</CheckForUpdates>
<PlaySound>false</PlaySound>
<FastExcelMode>true</FastExcelMode>
<ExcelTags>true</ExcelTags>
<ExcelRawMode>false</ExcelRawMode>
<DefineTermbaseOutputFormat>true</DefineTermbaseOutputFormat>
<MergeFiles>false</MergeFiles>
<UseTermbaseTemplate>true</UseTermbaseTemplate>
<UseMasterTermbase>false</UseMasterTermbase>
<MergeLanguages>false</MergeLanguages>
<MergeSubLanguages>false</MergeSubLanguages>
<MergeEntryNumber>false</MergeEntryNumber>
<MasterTermbase></MasterTermbase>
<MergeField></MergeField>
<TermbaseTemplate>C:\Users\Maite\Desktop\TM TEST.xlsx</TermbaseTemplate>
<Synonyms>
<Type>OneLine</Type>
<Column></Column>
<Repeat>false</Repeat>
<Separator>|</Separator>
</Synonyms>
<DefaultGlossaryFormat>Translation Memory eXchange</DefaultGlossaryFormat>
<UiLocale>es</UiLocale>
<UiTheme>Default</UiTheme>
<SettingsTab>0</SettingsTab>
<EmptyOutput>false</EmptyOutput>
<IgnoreUnknownFields>false</IgnoreUnknownFields>
<CreateEmptyFields>false</CreateEmptyFields>
<WriteDocType>false</WriteDocType>
<LargeFileExcelMode>false</LargeFileExcelMode>
<MultiFieldMode>ignore</MultiFieldMode>
<CreationUser>glossaryconverter</CreationUser>
<TbCopyright></TbCopyright>
<TbDescription></TbDescription>
<UseContentFilter>false</UseContentFilter>
<RegexContentFilter>false</RegexContentFilter>
<ContentFilterText></ContentFilterText>
<Tbx>
<Dialect>Core</Dialect>
<ResolveNote>false</ResolveNote>
<MappingFile></MappingFile>
<UseMappingFile>false</UseMappingFile>
</Tbx>
</Settings>

dentro: C:\Users\Maite\Desktop\tm test.xlsx
fuera: C:\Users\Maite\Desktop\tm test.tmx

Inicio de conversión: 22/01/2021 19:06:12
**** Hubo un error al crear el archivo de salida.
System.Exception: El archivo de la plantilla debe ser una base terminológica sdltb o un archivo de definición xdt.
en Sdl.MultiTerm.Tools.GlossaryConverter.Helpers.FieldResolver.TryToResolveFromTemplate(List`1 fields)
en Sdl.MultiTerm.Tools.GlossaryConverter.Helpers.FieldResolver.TryToResolveFields(List`1 fields, IFilter filter)
en Sdl.MultiTerm.Tools.GlossaryConverter.Helpers.FieldResolver.ResolveFields(List`1& fields, IFilter filter)
en Sdl.MultiTerm.Tools.GlossaryConverter.Filters.ExcelReader.GetFields(IFilter filter)
en Sdl.MultiTerm.Tools.GlossaryConverter.Core.FieldReader.Read(List`1 inputFilters, List`1 inputPaths)
en Sdl.MultiTerm.Tools.GlossaryConverter.Workflow.Converter.Convert(List`1 inputFilters, List`1 inputPaths, IFilter outputFilter)
en Sdl.MultiTerm.Tools.GlossaryConverter.Workflow.FileHandler.HandleMultipleFiles(List`1 files)
en Sdl.MultiTerm.Tools.GlossaryConverter.Workflow.FileHandler.ProcessFiles(List`1 files)

I downloaded Glossary Converter, but I don’t see anything like the second screenshot, certainly no SDLTM output option. What went wrong?

Paul Danaher 

Go to Settings and chose Default Output:

Thank you, Jerzy!

this has not worked in my case: simple 2 column Excel file, that I have tried to convert both into TM and TB, but I have always get an error. I find upsetting that Trados does not have a reliable glossary converter.