DGT-OmegaT 3.4 update 6 published

Now each glossary, which are accessible to groovy layout scripts as entry.origin, have 2 new properties:

• engineType : a string indicating what kind of local or distant method is used to retreive data. Will be "local file" for glossaries which are in the disk, and another string for other kinds of glossaries
• format : indicates which kind of data can be retreived for each entry of the glossary. Default value "3-col" indicates that the glossary contains the 3 usual columns "source, translation, comment". Actually only TBX glossaries will return another value (they will return "TBX V.V Dialect", where "V.V" is the version number (actually supported 2.0 and 3.0), and Dialect is the TBX dialect used by the glossary, if declared.

These 2 properties are totally independant. Some examples:

• TAAS glossaries will return engineType = "TAAS", while format is a kind of TBX because TaaS works by retreiving TBX documents
• Teambase glossaries will return engineType = "Cyclotis" (name of the plugin), while format is actually "3-col" but may change in the future
• All formats contained in a file will return engineType = "local file" and you will have to read format to know about the data.

A new glossary layout script "target-only" is joined to show these properties. But in the future, their real usage will probably not to display them, but to check whenever some extra properties which exist only in some file formats (such as part of speech) are available or not, before trying to display them.

Transtips (glossary markers) now support a tooltip in the editor, exactly as in OmegaT 4 but with the colors.