Hello, On Mon, Mar 17, 2008 at 11:21 AM, Mathias Bauer <[EMAIL PROTECTED]> wrote: > > Julen wrote: > > > On Mon, Mar 10, 2008 at 4:13 PM, Mathias Bauer <[EMAIL PROTECTED]> wrote: > >> Hi Julen, > >> > >> > >> Julen wrote: > >> > >> > TMX is just a format for exchanging purposes and it can be a source to > >> > feed a TM data-base. It's like exporting our document to another > >> > format (but something more ;). So, don't confuse TMX (a specific > >> > format) with TM (a general approach). > >> > Although TMX format can store customized properties for a translation > >> > unit, the format itself doesn't include structural information about a > >> > document, e.g. odt. It's just plain text, translation units ready to > >> > be used. For more information about this format you can see the > >> > specification online[1] > >> > >> Hm, it seems that we should clarify what the purpose of the extension > >> should be: > >> > >> (1) providing an interface to translate odt files > >> (2) using OOo as a translation tool based on tmx files > >> > >> First I assumed it was the first, now to me it sounds as if you are > >> targetting the latter. For the first use case we surely would need to > >> maintain structural information by matching translated and original > >> content inside of the extension. For the latter of course that wouldn't > >> be necessary and tmx defines the model of the extension. > >> > >> Can you give me a hint which of the two use cases it the one you want to > >> support? > > > > You're right, I want to support the second use case. > > Sorry for the misunderstanding. > > Thanks for clarification. After giving this some thinking I would like > to find out how that could basically work. > > OOo would need a TMX->Text filter for import and export. The filter > would use the Text API of OOo so that it basically could be imported > into any OOo application. The structure of the text seems to be simple > enough so that no special Writer features are required.
Yes. > The extension should create a UI with two windows containing the > original and the translated text. I think this can be done on top of the document, with no need of separate windows. To see an example of what I mean, search "wordfast" on the web for images[1] (you also have an entry at Wikipedia[2]). > If I see what e.e. OmegaT offers, I assume that we should also plan to > add some more fancy features that can be added incrementally. > > Is that correct? Yes, the features of this tool can be extended far beyond the initial idea and could be the starting point for more projects. Kindly yours, Julen. [1] http://www.geocities.com/wordfast/linux/linux1.jpg [2] http://en.wikipedia.org/wiki/Wordfast --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
