Import .mdb into Termbase, can't get it right...
Thread poster: Montes

Montes  Identity Verified
Netherlands
Local time: 10:53
Member (2009)
English to Dutch
+ ...
Oct 2, 2009

I've got a bilingual 3-field table that looks like:
That is Id, Dutch and English.

Index NL ENG
1 aan to
2 aan te sturen to control
3 aanbevolen recommended

I use convert to create the .XML that looks like:


-
-
1
aan
to

-
2
aan te sturen
to control

-
3
aanbevolen
recommended


The fault must ly in TB-definition because the log says:
'Can't find a table'...

Original Entry Number Action Entry Number in Termbase
-1 Does not conform to the target termbase definition.
Reason: Kan de uitvoertabel I_1 niet vinden.
Source: MtServer.MtTermbase.1

-1 Does not conform to the target termbase definition.
Reason: Kan de uitvoertabel I_1 niet vinden.
Source: MtServer.MtTermbase.1

What should the import definition look like to fit the 3-field table above?
I'm stuck.


Direct link Reply with quote
 

Vito Smolej
Germany
Local time: 10:53
Member (2004)
English to Slovenian
+ ...
Eliminate the first column Oct 2, 2009

Eszes wrote:

I've got a bilingual 3-field table that looks like:
That is Id, Dutch and English.

Index NL ENG
1 aan to
2 aan te sturen to control
3 aanbevolen recommended
....
What should the import definition look like to fit the 3-field table above?
I'm stuck.


The first column is superfluous (I mean, what's the intention behind it?) and causes all the trouble. Next, I have a gut feeling the ENG in the header row should better read EN.

Regards

Vito






[Edited at 2009-10-02 18:20 GMT]


Direct link Reply with quote
 

Montes  Identity Verified
Netherlands
Local time: 10:53
Member (2009)
English to Dutch
+ ...
TOPIC STARTER
Thanks for the reply Oct 3, 2009

I tried leaving the index field out, but then importing was rejected immediately. The name Eng is just the header in the table; in the importdefinition they are named correctly.

Again my question. What should the import definition look like to import the 3 fields?


Direct link Reply with quote
 

Astrid Elke Witte  Identity Verified
Germany
Local time: 10:53
Member (2002)
German to English
+ ...
Did you read the documentation that comes with the software? Oct 3, 2009

I paste it below:

"Preparing Microsoft Excel files for Conversion
SDL MultiTerm directly supports Microsoft Excel 2002/3.

Users of later versions and Excel (XP) must prepare their files for conversion as follows:

Save the terminology data as a comma separated values file (TXT) or an XLS file.

Convert the file using SDL MultiTerm Convert.

Users of Microsoft Excel 97 and Microsoft Excel 2000 must prepare their files for conversion as follows:

Save the terminology data as a tab-delimited file (TXT) from within Microsoft Excel 97.

Open the TXT file in a Unicode text editor, and save it as UTF-8.

Convert the file using SDL MultiTerm Convert.

Your Microsoft Excel file (XLS) must comply with the following preconditions:

All data must be located on the first sheet in the book.

The first row or line in the file must contain the information from the header field of each column.

No empty columns should appear between the columns that contain data. If the file contains an empty column between columns that contain data, the conversion process will stop at the empty column. Be sure to remove any empty columns of this kind before you run the conversion.

If you plan to import the terminology data into an existing termbase rather than creating a new termbase, make sure that the header field of each column has the same label as the corresponding field in the SDL MultiTerm termbase. For example, you might have a text field with the label 'Definition' in your SDL MultiTerm, and the corresponding column might be called 'Def' in your input file. Rename the 'Def' column to 'Definition' before you run the conversion."


Vito is right, your first column is invalid, because it does not concern a language. The index fields have to be languages. Furthermore, they have to be matched up with languages, during the conversion process, when you reach the step "Specify Column Header".


Direct link Reply with quote
 

Grzegorz Gryc  Identity Verified
Local time: 10:53
French to Polish
+ ...
Welcome in the Multiterm hell... column headers... Oct 3, 2009

VitoSmolej wrote:

Eszes wrote:

I've got a bilingual 3-field table that looks like:
That is Id, Dutch and English.

Index NL ENG
1 aan to
2 aan te sturen to control
3 aanbevolen recommended
....
What should the import definition look like to fit the 3-field table above?
I'm stuck.


The first column is superfluous (I mean, what's the intention behind it?) and causes all the trouble.

Not all but you may be right

Next, I have a gut feeling the ENG in the header row should better read EN.

In fact, the problem is the Multiterm guys rewrite the column headers in the XML/DB structure instead of map 'em.
Simply, it's impossible to make it work properly with their assumptions.

I assume you use the English GUI version as I do (I never tested the French, Spanish etc.).
I assume you use the default bilingual glossaries setup.
In your table, replace NL by Dutch, ENG by English (attention, case sensitive).
It should work.

The column header names must match exacty your MT database setup.
If it's different, use your settings.

Cheers
GG

[Edited at 2009-10-03 12:43 GMT]


Direct link Reply with quote
 

Montes  Identity Verified
Netherlands
Local time: 10:53
Member (2009)
English to Dutch
+ ...
TOPIC STARTER
Great relieve! Oct 3, 2009

Thank you GG!
Both your assumptions where right. I changed the field names to English and Dutch and it processed >2000 entries like a charm...

Me happy!


Direct link Reply with quote
 


To report site rules violations or get help, contact a site moderator:


You can also contact site staff by submitting a support request »

Import .mdb into Termbase, can't get it right...

Advanced search







Wordfast Pro
Translation Memory Software for Any Platform

Exclusive discount for ProZ.com users! Save over 13% when purchasing Wordfast Pro through ProZ.com. Wordfast is the world's #1 provider of platform-independent Translation Memory software. Consistently ranked the most user-friendly and highest value

More info »
CafeTran Espresso
You've never met a CAT tool this clever!

Translate faster & easier, using a sophisticated CAT tool built by a translator / developer. Accept jobs from clients who use SDL Trados, MemoQ, Wordfast & major CAT tools. Download and start using CafeTran Espresso -- for free

More info »



Forums
  • All of ProZ.com
  • Term search
  • Jobs
  • Forums
  • Multiple search