|
From: Andrzej S. <privat@...> - 2004-07-18 18:54:25
|
Ave, > At present (version 1.4.0), OmegaT only supports a single glossary format: its > own .tab format. [...] I see. Perhaps it is a good situation - it is easier to write standalone converters to/from various other formats than chase the moving target with the whole application. > It's a long time now since I imported a Multiterm glossary, but a glossary > exported as a txt file from the version of Multiterm I had (Multiterm '95 > Plus) was a tab-delimited list, no more complicated than that. It's possible > that the format of text files exported form Multiterm has since changed. I can't remember Multiterm 95, but in versions 5.x and 6.x the glossary export format is different, somewhat SGML-like; a single entry looks like this: ** <English>apple <Deutsch>Apfel <comment>a kind of fruit ... Individual enties are separated by the "**" lines. (How such entries are imported into MultiTerm depends on glossary structure, which is defined in MultiTerm and not included in the .txt file.) As one can see, converting such a file to DSV text or vice versa is pretty straightforward. Still, the mention is Help is a bit misleading... > Multiterm's *internal* format is a different matter altogether. OmegaT can't > handle that. Of course. :-) Best regards, -- Andrzej Sawula |