CafeTran

IK: In tab-delimited files where such alternatives are currently used.

I was afraid of that. So the idea is to get rid of one file format, and to achieve that, you want to keep that format, but handle it in CT like the most suitable format. More waste of time.

H.

Besides, if you use a tab dell as a TMX file, and convert it back to tab dell for no good reason, I suppose you'll miss important information/metadata, like creationdate, creationid. Unless you'll add that to the tab dell as well. Anything to keep on coding...

H.

IK: The TMX support is unaffected by this improvement.

That's good to know. But I still think it's a futile exercise. There's no good reason for using tab dells.

H.

- The size and state of the Dashboard panels is maintained when you close the project.

- Added support for .mqxlz files. These are zipped .mqxliff files which previously needed to be unzipped and zipped back after the translation. Now, these actions can be performed directly in CafeTran.

Thanks, both things are most helpful, in my very humble opinion.

Holiday greetings from the very south of Europe.

>> I plan to let CT maintain the concise structure of the alternatives/synonyms in one entry in a future update.

Looking forward to this.

There are two reasons why I'm still using tab-d glossaries.

1. "Concise structure of the alternatives/synonyms in one entry" is now supported only for text glossaries.

For my language pair (English/Japanese), alternatives are musts because there can be so many alternatives on both the s/t sides, and if I were to do this with a TMX file, I'd have to spend much more time (because it currently accepts one entry per TU), especially when I want to add additional information.

I'd appreciate it if CT supports some kind of tabular listing of alternatives, also for TMX files.

2. Additional fields

When TMX files are converted into text files (for safekeeping purposes, in my case) (by saving TMX as .txt file), additional fields are lost. This is the other reason.

There seems to be one or more people who assume, without scrutiny, I'm a hard-boiled text glossary lover. Funny.

Masato: For my language pair (English/Japanese), alternatives are musts

I suppose that goes for any language. And when you use the Automated workflow, they do show up in the tabbed pane, and probably in the Match Box (which I don't use), as repeatedly mentioned by me and a certain Igor:

...and if I were to do this with a TMX file, I'd have to spend much more time (because it currently accepts one entry per TU), especially when I want to add additional information.

I doubt that. If you add a term on-the-go, it's a matter of a few clicks, arguably faster than adding them to a tab del. Even if you use a script.

When TMX files are converted into text files (for safekeeping purposes, in my case) (by saving TMX as .txt file), additional fields are lost.

Yes, and very important ones. I already mentioned (above) creationid an creationdate (the latter being very important for my workflow), but CT also stores your settings of a TMX file in the file itself, like priority, Newer Duplicates Only, Match Case, you name it.

type="x-segments">false</prop><prop type="x-terms">true</prop><prop type="x-processing_tags">false</prop><prop type="x-read_only">false</prop><prop type="x-stop_autoassembling">false</prop><prop type="x-pretranslate_only">false</prop><prop type="x-terms_consistency_check">false</prop><prop type="x-priority">0</prop><prop type="x-integration">0</prop><prop type="x-case_match">false</prop><prop type="x-duplicates"

All that useful information will get lost if you convert a TMX file back to a tab del, unless Igor adds them to the tab dells as well, which exactly is why I'm so @#$&ing angry. Years have been spent to make a tab del act like a TMX file, and it cannot be done. For CT, there's only one format suitable for terms (fragments, words), and that format happens to be TMX.

H.

On a lighter note, but still on topic, our Count of Hastings, now using the samsung of CAT tools, defends the lack of being able to add new fields for terms in that tool:

Read all about it...

H.