On 26 déc. 07, at 17:08, Yury Tarasievich wrote:
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.
I think you are indeed missing something.
As Ale wrote, such meta-information can be added to the glossaries (in
OmegaT->use the third column) or to TMX files, or to XLIFF files.
TMX files can use the <note> place holder.
XLIFF files can use the <context> place holder.
Besides, glossary or TMX information in OmegaT (or anywhere else) is
suggestions for the translator at best and the context can be provided
by other means.
"Other means" include but is not limited to meta-information. Besides,
it is necessary for the meta-information to be directly available and
processable by the translator to have any practical use.
The focus on meta-information is valid as long as the data is
automatically available to the processes. Currently it is not the
case, or is it ?
Since there are not tools that can automatically process the SDF meta-
information in its current form, focusing on meta-information seem to
me to be counter productive.
Other ways to support the translator is to provide external context to
strings. That can be done by the translator's experience itself
(knowing the data set, having experience in the field etc), or by
providing the data in external viewers: OOo's help viewer, screenshots
etc...
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.
Yes. That is correct. But in most of the cases the translator has
enough common sense and external resources (the l10n community,
experiences users, external context, etc.) to make do for the lack of
meta-information or the lack of automatic access to it.
I fully understand that you want to provide the most error-prone-less
possible workflow by using such meta-information, but in most cases
this meta-information will not be available to the translators in a
practical way. Last but not least, such meta-information is mostly
useful for indetifying UI items, but for the whole rest of the
translation process (terminology management, style management etc) it
is simply useless.
Jean-Christophe Helary
------------------------------------
http://mac4translators.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
