IK: so I might check them
You see? Tell him he it's too difficult for him, and he'll try again. Predictable.
> "It's too difficult for Igor."
Difficulties apart, it is usually a matter of priorities and time available.
> You can be sure Igor had a close look at it years ago.
That's true. At that time, I abandoned the idea because the possible implementation would work only on Windows PC. The availability of Access drivers on the other operating system seems to have improved so I might check them.
amos: I also support adding this feature
You can be sure Igor had a close look at it years ago. The best thing we can do at the moment, is to state that "It's too difficult for Igor."
CT should at least warn where a Studio package contains a glossary
That's more feasible.
Source terms and target terms in Access databases are matched via the Concept ID. The only columns that are relevant for a CafeTran translation project are I_Source_language and I_Target_language:
Access readers are likely to be available for all supported operating systems.
>Reputed app GlossaryConverter can convert Multiterm files into TBX
Studio has to be installed, so it possibly (very likely) uses Studio's resources.
Masato: It should be technically possible.
I bet it is, but I do think it would be quite difficult, especially for CT because it's cross-platform, whereas SDLTB is MS Access.
It can contain several languages, and lots of attributes. I wouldn't know where to begin to automate that, not even for one language pair.
This would be much appreciated indeed!