Selcuk Akyuz wrote:
Igor Kmitowski wrote:
The pipe character in TMX memories is used for the stemming (prefix matching) feature whereas in simple tab delimited glossaries it used to separate multiple target meanings.
Clear information, thanks! My glossary structure is Source Term TAB Target Term TAB Additional fields (all separated with tabs). No pipe characters, but I don't know how does CT consider my additional fields.
CafeTran assumes that all fields in a text file are separated by the same character (for example TAB). Are they?
Sure, they are. I am good with csv files thanks to UniCSVed.
Well, but as I have stated above in my third message, Glossary file displays additional fields provided that you do not have duplicate source terms (with identical or different translations). I want to see the additional fields for duplicate terms and therefore Glossary is not so useful for me.
You can keep the duplicate entries when converting from a tab delimited glossary to a TMX memory. Just check Keep all duplicates box in Memory | New Memory | Filter when you create the new TMX memory for the conversion.
Thanks, it worked. No data loss now!
CT may freeze when you load huge TMX or glossary files into RAM memory assigned to CafeTran. You can increase this value. See Edit | Options | Memory tab | Java memory size (MB). Remember not to go over the actual RAM memory on your system.
I have 2GB only and 1GB is assigned to Java. I assume it will not be a good idea to increase it to 2GB. Other programs may freeze.
When you see search results in the Memory tab, click the segment number and go to Edit Tu menu to see notes for this translation unit
Scroll down the list with the mouse to find the term, click on the number, click on "Edit Tu", select "Edit note" to display it, then click on X (or press Esc three times) to close the window. IMO, it is time consuming and excessive use of mouse for a program. (Generally speaking, after testing CT for 3 days, I feel many operations in CT requires use of mouse)
I still did not test the External DB function, I have to make some research before using H2, MySQL, Oracle 10g, HSQLDB 2.0 or Derby (Java DB). Use of a term list with any of these databases may be better (for speed and hopefully for GUI).
But as for the other features I tested for terminology management (Glossary, Dictionary, Memory for Terms), sorry but I am really lost in them. IMO, Dictionary is useless because there is no on-the-fly search. Memory for Terms requires too much mouse and keyboard use. Most promising one is Glossary but it needs some improvements that I have discussed in this thread. By the way I loved docking and undocking of tabs
Kind regards,
Selcuk
[Edited at 2012-01-18 03:38 GMT]