Fóruns técnicos » Localization »
Translation database: what to expect?
Tópico cartaz: Heinrich Pesch
Heinrich Pesch
Heinrich Pesch  Identity Verified
Finlândia
Local time: 05:43
Membro (2003)
finlandês para alemão
+ ...
Aug 26, 2007

Last week I started to use a database along with my translation. The software strings were translated in Excel and I converted the source and target into Termbase for SDLX.
Now Termbase displays only single words for suggestions:

EN/DE
and/und
for/für
on/auf
patient/patient
etc.

I would have expect, that the database would show up as complete strings, as entered in the columns, like:

consider patient name for transfer/..... See more
Last week I started to use a database along with my translation. The software strings were translated in Excel and I converted the source and target into Termbase for SDLX.
Now Termbase displays only single words for suggestions:

EN/DE
and/und
for/für
on/auf
patient/patient
etc.

I would have expect, that the database would show up as complete strings, as entered in the columns, like:

consider patient name for transfer/....

I mean, what's the point of a database, if it does not recognise complete strings?

The same happens in Transit Termstar.

Is this normal or what do you think?

REgards
Heinrich



[Bearbeitet am 2007-08-26 01:47] ▲ Collapse
 
Roberta Anderson
Roberta Anderson  Identity Verified
Itália
Local time: 04:43
Membro (2001)
inglês para italiano
+ ...
check delimeters - space instead of tab? Aug 26, 2007

Hi Heinrich

no, this is not normal... the first thing that came to mind is the delimeter used in the conversion from Excel to text file, and the delimiter selected when importing the text file in SDLX Termbase. If at some point it has been set to space instead of tab, then I think you would get what you are describing.

Try saving your Excel file as tab delimited txt file, then when you import it in the newly created termbase, ensure that you also select Tab as delimiter... See more
Hi Heinrich

no, this is not normal... the first thing that came to mind is the delimeter used in the conversion from Excel to text file, and the delimiter selected when importing the text file in SDLX Termbase. If at some point it has been set to space instead of tab, then I think you would get what you are describing.

Try saving your Excel file as tab delimited txt file, then when you import it in the newly created termbase, ensure that you also select Tab as delimiter - you should then get your full strings.

Hope this helps
Roberta ▲ Collapse
 
Heinrich Pesch
Heinrich Pesch  Identity Verified
Finlândia
Local time: 05:43
Membro (2003)
finlandês para alemão
+ ...
CRIADOR(A) DO TÓPICO
Tab was selected by default Aug 26, 2007

I imported the file again and now it seems to work. I wonder what was wrong.
Thanks, Roberta, for the hint.
Regards
Heinrich
 


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

Moderador(es) deste fórum
Maya Gorgoshidze[Call to this topic]
Mahmoud Akbari[Call to this topic]

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

Translation database: what to expect?






TM-Town
Manage your TMs and Terms ... and boost your translation business

Are you ready for something fresh in the industry? TM-Town is a unique new site for you -- the freelance translator -- to store, manage and share translation memories (TMs) and glossaries...and potentially meet new clients on the basis of your prior work.

More info »
Trados Studio 2022 Freelance
The leading translation software used by over 270,000 translators.

Designed with your feedback in mind, Trados Studio 2022 delivers an unrivalled, powerful desktop and cloud solution, empowering you to work in the most efficient and cost-effective way.

More info »