Menu ▾ ▴

#1240 Compatibility with MED format

4.0
closed-fixed
Alex Buloichik
None
5
2016-09-06
2016-04-26
Didier Briel
No

The MED format is a project package defined by the Directorate-General for Translation:
http://dragoman.org/med/

As the OmegaT project format and the MED format share similarities, some interoperability should be possible.
Although the current specifications are med-029, the development is based on the medo1 template, as it is currently more stable. Once MED specification become stable enough, it should be easy to adapt mapping. Until this is done, caution should be used in production, as the format may change.
In the Project menu, there are two new entries:

Open MED Project. It is only available if no project is open.
This loads the following elements from a MED (.zip) project into a new project:

  • The source language from <name>/dossier/workflow/translation{slang}
  • The target language from <name>/dossier/workflow/translation{tlang}
  • All source files from <name>/doc/main/<slang>/* are placed in /source
  • All TMX files from <name>/doc/support/<slang>/tm/*.tmx are placed in /tm/auto. That way, if the package is produced by OmegaT, all translations would be retrieved.
  • All glossaries from <name>/doc/support/<slang>/term/* are placed in /glossary, including if present the writeable glossary (glossary/glossary.txt).

The MED package (<name.zip>) is stored in /omegat/med/<name.zip>.</name.zip>

Create MED Project. It is only available if an OmegaT project is open.
This stores the following elements in a MED (.zip) project:

  • The source and target language of the project in the text file translation
    o <name>/dossier/workflow/translation{slang}
    o <name>/dossier/workflow/translation{tlang}
  • Any source document from /source in <name>/doc/main/<slang>/*
  • Any target document from /target in <name>/doc/main/<tlang>/*
  • The translation memory (in TMX format) from the root of the project in <name>/doc/support/<slang>/tm/<name>-level2.tmx
  • The writeable glossary of the project form glossary/glossary.txt in <name>/doc/support/<slang>/term/glossary.txt
  • The statistics of the project from /omegat/project_stats.txt in <name>/dossier/post/project_stats.txt

If the OmegaT project was originally created from a MED project, all stored information not modified by OmegaT should be copied “as is” to the new MED project.

The way the mapping is done, it is possible to achieve a minimal but usable roundtrip by creating a MED package and loading it in another instance of OmegaT with all translations and the writeable glossary preserved.

Didier

Discussion

  • Didier Briel

    Didier Briel - 2016-04-26

    Implemented in SVN (/trunk).

    Didier

     

    Last edit: Didier Briel 2016-04-26

  • Didier Briel

    Didier Briel - 2016-09-06
    • status: open-fixed --> closed-fixed
     

  • Didier Briel

    Didier Briel - 2016-09-06

    Implemented in the released version 4.0 of OmegaT.

    Didier

     

  • Didier Briel

    Didier Briel - 2016-09-06
    • Description has changed:

    Diff:

    --- old
+++ new
@@ -2,7 +2,7 @@
 http://dragoman.org/med/

 As the OmegaT project format and the MED format share similarities, some interoperability should be possible.
-Although the current specifications are `med-029`, the development is based on the `medo1` template, as it is currently be more stable. Once MED specification become stable enough, it should be easy to adapt mapping. Until this is done, caution should be used in production, as the format may change. 
+Although the current specifications are `med-029`, the development is based on the `medo1` template, as it is currently more stable. Once MED specification become stable enough, it should be easy to adapt mapping. Until this is done, caution should be used in production, as the format may change. 
 In the Project menu, there are two new entries:

 Open MED Project. It is only available if no project is open.
     

Log in to post a comment.

MongoDB Logo MongoDB