On Mon, 24 Dec 2007 11:29:59 +0200, Jean-Christophe Helary <[EMAIL PROTECTED]> 
wrote:
> On 24 déc. 07, at 17:09, Yury Tarasievich wrote:
>
>> On Mon, 24 Dec 2007 00:52:45 +0200, Jean-Christophe Helary <[EMAIL PROTECTED]
>> > wrote:
>>> On 23 déc. 07, at 19:21, Yury Tarasievich wrote:
>>>
>>>> However, I do care about lack of meta-information which renders many
>>>> actual translation issues hard to resolve. Your scheme does not
>>>> address that matter and actually would postpone its resolvement.
>>>
>>> No, it does not.
>>>
>>> XLIFF is equivalent to SDF in terms of the possible availability of
>>> "context information".
>> ...
>> Etc. etc. Wouldn't it be nice if all things were nice. Aren't you
>> deliberately ignoring such factors as the workflow and manpower?
>
> This is specifically what I am trying to address.
>
> Why has SUN moved from a workflow that ensures the most efficient use
> of previous translations to a workflow that does not ?

Because it's not their priority?
Because at the time this seemed (or actually was) the best available solution?
Because the world-wide populariry of the "OOO translating" caught them unaware?

> How hard would it be to have a few Java programmers improve the
> current OLT filters so that SDF is supported there ?

The OLT itself seems to be sort of "put on ice", as it seems. Or so I gathered 
in Spring, when accessing the possibity to XLIFF-migrate the OOO translation 
I'm taking care of.

> How hard would it be to give translators access to the full source of
> the help files for context ?
>
> Ie, what can be done in practical terms, besides for PO hacks, to
> improve the translators' work and the output quality ?

I.e., to add meta-information, be it Nth extra field of SDF or whatever carrier 
format, which would be an enterprise all by itself. The PO hacks, ugly as they 
are, work, and translations are coming in. The "new way to go", pretty as it 
may seem in theory, has yet to be implemented *and* to prove itself. What about 
*other* translating teams, after all?

---

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to