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. 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 statistics of the project from /omegat/project_stats.txt in /dossier/post/project_stats.txt The writeable glossary of the project form glossary/glossary.txt in /doc/support//term/glossary.txt The translation memory (in TMX format) from the root of the project in /doc/support//tm/-level2.tmx Any target document from /target in /doc/main//* Any source document from /source in /doc/main//* The source and target language of the project in the text file translation This stores the following elements in a MED (.zip) project: It is only available if an OmegaT project is open. The MED package () is stored in /omegat/med/.Ĭreate MED Project. All glossaries from /doc/support//term/* are placed in /glossary, including if present the writeable glossary ( glossary/glossary.txt). That way, if the package is produced by OmegaT, all translations would be retrieved. Some of these cookies are essential to the operation of the site, while others help to improve your experience by providing insights into how the site is being used. All TMX files from /doc/support//tm/*.tmx are placed in /tm/auto. Details on OmegaT including translator reviews, system requirements, price information, file formats and more. All source files from /doc/main//* are placed in /source The source language from /dossier/workflow/translation This loads the following elements from a MED (.zip) project into a new project: It is only available if no project is open. In the Project menu, there are two new entries: Until this is done, caution should be used in production, as the format may change. You can translate the resulting XML file, but once you get the file back into FM, you will have to re-apply all the formatting and put the original figures. Once MED specification become stable enough, it should be easy to adapt mapping. The MED format is a project package defined by the Directorate-General for Translation:Īs the OmegaT project format and the MED format share similarities, some interoperability should be possible.Īlthough the current specifications are med-029, the development is based on the medo1 template, as it is currently more stable.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |