On Wed, 26 Dec 2007 09:56:57 +0200, Alessandro Cattelan <[EMAIL PROTECTED]> wrote: ... > translators, really need is a method to translate effectively using TM > and glossaries just like we do in the professional world. OmegaT would > have it all: a glossary extracted from SunGloss can easily be converted > for the tool and the OmegaT TM engine works very well... but then, > obviously, we need a TM that matches the content to be translated.
Maybe I'm missing something, but how can the Sun's glossary/TMX or whatever be helpful without meta-information? No amount of toolchain change is going to address this by itself. Maybe *I'm* not making myself intelligible? I'm talking about having things assigned to the strings like a "term variant", "type of use (menu/option/...)", "keep short" etc. Currently such info often has to be deduced from string ID, or lucky probe in the UI, even from sources digging. --- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
