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. Julen. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
