Re: [OmTdev] Custom file format filters

[Didier B. <d....@fr...>]

-----Original Message-----
>From: ome...@li...
[mailto:ome...@li...]On Behalf Of Ian
Trudel
>Sent: Monday, May 19, 2008 5:09 PM
>To: Mailing list for OmegaT developers.
>Subject: Re: [OmTdev] Custom file format filters

>>>I should have shared a sample with you...
>>>
>>>
>>>     <message>
>>>         <source>Hello world!</source>
>>>         <translation type="unfinished"></translation>
>>>     </message>
[snip]
>The target text is the <translation> tag, which might or might not
>have text and can have (or not) a defined type. I believe that type
>can be unfinished, obsolete, done, etc. Once a text is translated,
>it's supposed to change the type for "done". Basically, the question
>is about pre- and/or post-processing on specific attributes during
>edition.

OmegaT has nothing related.
Of course, the attribute itself could be made translatable, but I don't
supposed that's what you would want.

>>>Besides, sometimes information identifying sections should be display
>>>but still unmodifiable. Is it possible with OmegaT framework?
>>
>> It isn't possible currently to display non-translatable text.
>
>This would be a nice feature in any case.

Yes.
Like a lot of things :)

>As far as I understand the plugin system, it is not dynamic
>whatsoever. Is it correct?

Not exactly. What you have used is not a plugin system.
We do have one for filters, but it's not used actually, for a number of
reasons.
One of them is that, if you know how to make a filter, you might as well
compile OmegaT.

We have also a prototype of a generic XML filter, but it wasn't totally
finished, so we cannot integrate it in its current form.

>Anyone thought to use such framework as
>JPF? http://jpf.sourceforge.net/ -- Would it be interesting anyway?

While it might be useful, it wouldn't help much providing OmegaT's core
concepts it doesn't have, such as bilingual documents.

Didier