| Страниц в теме: [1 2] > | Glossary keeps getting emptied? Автор темы: Mercer
|
|---|
I'm having a problem with the glossaries in Wordfast Classic 6.03t.
When I try to import/select a glossary, at first things seems ok. But when I click on "reorganize", the top status bar of the window says :
Number of lines found and sorted : 0
The size of the glossary, as indicated by Wordfast, then drops to "1 Kbyte". And if I try to open the file in Finder, it's effectively blank.
I understand Wordfast creates new files when a glossary is i... See more I'm having a problem with the glossaries in Wordfast Classic 6.03t.
When I try to import/select a glossary, at first things seems ok. But when I click on "reorganize", the top status bar of the window says :
Number of lines found and sorted : 0
The size of the glossary, as indicated by Wordfast, then drops to "1 Kbyte". And if I try to open the file in Finder, it's effectively blank.
I understand Wordfast creates new files when a glossary is imported, but the only one of them who seems to have any real information is the backup it makes of the original file.
These same glossaries work fine in Wordfast Pro. I searched a lot and wasn't able to find an answer to this, but I'm new to Wordfast in general.
I'm on OS X 10.8 and using Word 2011. Anyone knows what I'm doing wrong here? ▲ Collapse
| | | | | Format of glossary | Aug 15, 2012 |
Was the glossary you tried to open in Classic exported from Pro? If so, which format did you choose in Pro: tab delimited or TBX? What does the file you try to open in Classic as a glossary look like in a text editor (eg. TextEdit), prior to opening it in Classic?
| | | | | Thanks for responding. | Aug 15, 2012 |
Dominique Pivard wrote:
Was the glossary you tried to open in Classic exported from Pro? If so, which format did you choose in Pro: tab delimited or TBX?
I've tried to export from Pro to Classic as tab delimited files and it had the same problem. The TBX exports from Pro refused to import.
I've also tried the the sample glossary from the Wordfast's beginner tutorial but got the same result. Even the sample glossary file that Classic can make when creating a new one does it.
What does the file you try to open in Classic as a glossary look like in a text editor (eg. TextEdit), prior to opening it in Classic?
Before import, the files tabulated text file (term in source language, tab, term in target language). I've tried to save them in this format from Textedit, Excel and Word, but always get the same problem.
Here's an example, using a glossary with 4 entries, of the files I get before and after importing. (There's a tab between source and target, but it gets lost when posting).
Before import (1 file)
File : sampleglo.txt
authorization screen écran d'accueil
Belgium Belgique
browser navigateur
closed-loop heat recycler recycleur thermique en circuit fermé
After import (3 files)
File : sampleglo.txt
(blank)
File : sampleglo.idg
0 560d 0
File : sampleglo.bak
authorization screen écran d'accueil
Belgium Belgique
browser navigateur
closed-loop heat recycler recycleur thermique en circuit fermé
Am I doing something wrong or could this be a bug because of something in my configuration? I installed Classic according to the instructions for Word 2011 (adding it manually), and there are no other versions of Word on the computer.
| | | | Samuel Murray 
Нидерланды
Local time: 10:34
Член ProZ.com c 2006
английский => африкаанс
+ ...
| Can't use WFP glossaries in WFC | Aug 15, 2012 |
Mercer wrote:
The size of the glossary, as indicated by Wordfast, then drops to "1 Kbyte". And if I try to open the file in Finder, it's effectively blank. ... These same glossaries work fine in Wordfast Pro.
Speaking from experience: Before using a glossary from WFP in WFC, first open the glossary in MS Word and resave it as "Unicode" (or UTF16 or UTF16 LE). WFP writes glossaries as UTF8, but WFC wants them to be in UTF16LE, and if you feed it a UTF8 glossary file, it will simply eat it.
| | |
|
|
|
| Glossary got empty :/ | Aug 15, 2012 |
I've just got a similar problem with Wf Pro 3.1 and Wf Classic 6.03t)... :/
I exported my Wf Pro glossary into a tab-limited format. I opened it and reorganised in Wf Classic. Everything seemed smooth and well until then (apart from some strange signs instead of a few Polish letters in the Pro version exported).
The Pro export file was "glossary 1", my usual one was "glossary 2".
Once in the Wf Classic data editor, I've opened the glossary 2 and wanted to merged i... See more I've just got a similar problem with Wf Pro 3.1 and Wf Classic 6.03t)... :/
I exported my Wf Pro glossary into a tab-limited format. I opened it and reorganised in Wf Classic. Everything seemed smooth and well until then (apart from some strange signs instead of a few Polish letters in the Pro version exported).
The Pro export file was "glossary 1", my usual one was "glossary 2".
Once in the Wf Classic data editor, I've opened the glossary 2 and wanted to merged it with the glossary 1. And at present... I have no glossary 1 - its content and the previous version have disappeared, its first line has been modified, and there are no terms inside the file.
Unfortunately, I do not back up my glossaries every day. I guess I'll have to change the frequency of my back-ups now... ▲ Collapse
| | | | | Thanks for the help, but still no luck | Aug 15, 2012 |
Samuel Murray wrote:
Speaking from experience: Before using a glossary from WFP in WFC, first open the glossary in MS Word and resave it as "Unicode" (or UTF16 or UTF16 LE). WFP writes glossaries as UTF8, but WFC wants them to be in UTF16LE, and if you feed it a UTF8 glossary file, it will simply eat it.
I can't seem to find how to save as Unicode UTF16 or UTF LE in Word, so I did it in TextWrangler. I've tried the various UTF 16 options and the problem remains...
I'm trying all this with the demo version of Classic, but from what I read I don't think that's the cause. I'll try to find computer where I know there's a working full version of Classic installed to see what happens, but that might not be before a few weeks.
| | | | Samuel Murray
Нидерланды
Local time: 10:34
Член ProZ.com c 2006
английский => африкаанс
+ ...
| Am I invisible? | Aug 15, 2012 |
Mercer wrote:
Am I doing something wrong or could this be a bug because of something in my configuration? I installed Classic according to the instructions for Word 2011 (adding it manually), and there are no other versions of Word on the computer.
Speaking from experience: Before using a glossary from WFP in WFC, first open the glossary in MS Word and resave it as "Unicode" (or UTF16 or UTF16 LE). WFP writes glossaries as UTF8, but WFC wants them to be in UTF16LE, and if you feed it a UTF8 glossary file, it will simply eat it.
| | | | | Sorry, it's my messages that are delayed. | Aug 15, 2012 |
Samuel Murray wrote:
Am I invisible?
Sorry, it's my responses which are getting delayed (since I'm a new user, a moderator has to approve my posts before they show). I've tried to save in the various UTF 16 options TextWrangler offers, but that didn't seem to work either... but thanks for the answer.
[Edited at 2012-08-15 18:58 GMT]
[Edited at 2012-08-15 19:09 GMT]
| | |
|
|
|
If your question is addressed to me: No, you are not invisible. People tend to seek solutions after experiencing problems, not before.
In my post, I just wanted to describe my experience (hoping the Wf staff would consider this issue). I have not read this topic before the problem appeared. I've lost my glossary, so no solution to that.
FYI, I always open two glossaries in MS Word and do the "copy&paste". For once I wanted to make it in an easier way and I've been punished by ... See more If your question is addressed to me: No, you are not invisible. People tend to seek solutions after experiencing problems, not before.
In my post, I just wanted to describe my experience (hoping the Wf staff would consider this issue). I have not read this topic before the problem appeared. I've lost my glossary, so no solution to that.
FYI, I always open two glossaries in MS Word and do the "copy&paste". For once I wanted to make it in an easier way and I've been punished by Wf. :/ ▲ Collapse
| | | | Samuel Murray
Нидерланды
Local time: 10:34
Член ProZ.com c 2006
английский => африкаанс
+ ...
Marcelina Haftka wrote:
If your question is addressed to me...
No, I did not quote you, so my reply is not a reply to you.
| | | |
To give an update, it seems like my problem is resolved for now.
I downgraded Wordfast to an older version, and that problem disappeared. Since I saw other people complaining about a similar problem on the mailing lists, I'm guessing there might be a bug on 6.03t on mac with the setup I had (Word 2011, OSX 10.8).
Thanks Dominique, Marcelina, and Samuel for having taken the time to help, I'm pretty happy this finally works.
| | | | | Which older version? | Aug 18, 2012 |
Mercer wrote:
I downgraded Wordfast to an older version, and that problem disappeared.
For the record: which older version solved your problem?
| | |
|
|
|
| Version is 6.01g | Aug 18, 2012 |
Dominique Pivard wrote:
For the record: which older version solved your problem?
It's 6.01g, which seems to date from last year. (There are probably downsides to using an older version, and looks like I might be having different problems now, but the problem I had with the glossaries is gone.)
| | | | SafeTex
Франция
Local time: 10:34
французский => английский
+ ...
| Wordfast Data Editor | Aug 18, 2012 |
Mercer wrote:
I'm having a problem with the glossaries in Wordfast Classic 6.03t.
When I try to import/select a glossary, at first things seems ok. But when I click on "reorganize", the top status bar of the window says :
Number of lines found and sorted : 0
The size of the glossary, as indicated by Wordfast, then drops to "1 Kbyte". And if I try to open the file in Finder, it's effectively blank.
I understand Wordfast creates new files when a glossary is imported, but the only one of them who seems to have any real information is the backup it makes of the original file.
These same glossaries work fine in Wordfast Pro. I searched a lot and wasn't able to find an answer to this, but I'm new to Wordfast in general.
I'm on OS X 10.8 and using Word 2011. Anyone knows what I'm doing wrong here?
Hello
Go to data editor and check all the options, especially 'sort' and 'filters'. You may find that something is wrongly set there causing this behaviour
Good hunting
SafeTex
| | | |
SafeTex wrote:
Go to data editor and check all the options, especially 'sort' and 'filters'. You may find that something is wrongly set there causing this behaviour
Good hunting
SafeTex
Thanks, I'll look at that and update if I find something.
| | | | | Страниц в теме: [1 2] > | To report site rules violations or get help, contact a site moderator: You can also contact site staff by submitting a support request » Glossary keeps getting emptied? | 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 » |
| | Protemos translation business management system | Create your account in minutes, and start working! 3-month trial for agencies, and free for freelancers!
The system lets you keep client/vendor database, with contacts and rates, manage projects and assign jobs to vendors, issue invoices, track payments, store and manage project files, generate business reports on turnover profit per client/manager etc.
More info » |
|
| | | | X Sign in to your ProZ.com account... | | | | | |
Login to reply/comment 
Translation news related to Wordfast
