This site uses cookies.
Some of these cookies are essential to the operation of the site,
while others help to improve your experience by providing insights into how the site is being used.
For more information, please see the ProZ.com privacy policy.
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]
Subject:
Comment:
The contents of this post will automatically be included in the ticket generated. Please add any additional comments or explanation (optional)
Selcuk Akyuz Türkiye Local time: 06:54 English to Turkish + ...
more info please
May 15, 2008
What was the format of the glossary file?
Subject:
Comment:
The contents of this post will automatically be included in the ticket generated. Please add any additional comments or explanation (optional)
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 symbole... See more
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. ▲ Collapse
Subject:
Comment:
The contents of this post will automatically be included in the ticket generated. Please add any additional comments or explanation (optional)
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]
Subject:
Comment:
The contents of this post will automatically be included in the ticket generated. Please add any additional comments or explanation (optional)
FarkasAndras Local time: 05:54 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)
Subject:
Comment:
The contents of this post will automatically be included in the ticket generated. Please add any additional comments or explanation (optional)
Translate faster & easier, using a sophisticated CAT tool built by a translator / developer.
Accept jobs from clients who use Trados, MemoQ, Wordfast & major CAT tools.
Download and start using CafeTran Espresso -- for free
Create customer quotes and invoices from within Trados Studio
Trados Business Manager Lite helps to simplify and speed up some of the daily tasks, such as invoicing and reporting, associated with running your freelance translation business.