Anything wrong with importing glossary to Termstar?
Thread poster: ranran
ranran
English to Chinese
May 14, 2008

I tried to import a two-column glossary (SL is English and TL is Chinese) into termstar. As a result, both the source language and target language can’t be separated. I mean, in the right page of termstar, both the English and Chinese terms are in the “ENU”part, and nothing appears in the target part. Wondering what’s wrong with this.

[Subject edited by staff or moderator 2008-05-15 03:30]


Direct link Reply with quote
 

Selcuk Akyuz  Identity Verified
Turkey
Local time: 09:55
Member (2006)
English to Turkish
+ ...
more info please May 15, 2008

What was the format of the glossary file?

Direct link Reply with quote
 
ranran
English to Chinese
TOPIC STARTER
txt.file May 15, 2008

it's txt. file. The file works well when i import it in DVX.

Direct link Reply with quote
 
ranran
English to Chinese
TOPIC STARTER
Detailed description May 16, 2008

Left page:
"Battle of tours" "都尔之战" >>

Right page:
ENG:
Term: "Battle of tours" "都尔之战" (ENU-no edit!)
Gender
Subject:
Defination:

( below the "ENG" part is supposeed to be the Target terms, but nothing appears)

In the import wiard>define the import file layout, i choose the first one-"table layout with unique field separation" ; then in the following "field separation" slot, i tried both symboles: " and >>. But still not working. (by the way, same problem occures when i import the .xls file glossary) Is it because we can't import glossary with two language information; because when i import a glossary containing English language only, it worked well, althoug i need type the target term later.


Direct link Reply with quote
 
ranran
English to Chinese
TOPIC STARTER
one solution May 16, 2008

found a solution-to edit it manually, although it is a little time-consuming. Still i can't import the glossary with both SL and TL.

[Edited at 2008-05-16 16:42]


Direct link Reply with quote
 
FarkasAndras
Local time: 08:55
English to Hungarian
+ ...
just a guess May 19, 2008

I don't know termstar so this is just a stab in the dark:
you say the import file is a txt, so I presume it is a comma or tab separated txt. It seems probable that there is a problem with the separator, ie Termstar expects a particular separator character, like a TAB between S term and T term, which is not there.

MS Word search and replace can solve this once you figure out the exact problem (^t stands for TAB)


Direct link Reply with quote
 


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

Moderator(s) of this forum
Maya Gorgoshidze[Call to this topic]

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

Anything wrong with importing glossary to Termstar?

Advanced search






SDL MultiTerm 2017
Guarantee a unified, consistent and high-quality translation with terminology software by the industry leaders.

SDL MultiTerm 2017 allows translators to create one central location to store and manage multilingual terminology, and with SDL MultiTerm Extract 2017 you can automatically create term lists from your existing documentation to save time.

More info »
LSP.expert
You’re a freelance translator? LSP.expert helps you manage your daily translation jobs. It’s easy, fast and secure.

How about you start tracking translation jobs and sending invoices in minutes? You can also manage your clients and generate reports about your business activities. So you always keep a clear view on your planning, AND you get a free 30 day trial period!

More info »



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