How you work What you share and don't share You receive all what has changed in the distant database Only segments modified after the re-connection are sent to the server You see again segments from your colleagues Note : a column about RMI mode would be similar to the last one (this is a variant of project mode), except that the inter-operability with other CAT tools is not implemented, and would probably be more difficult.ĭGT-OmegaT (includes the plugin) or Patched OmegaT 4.3.2 (plugin is not yet compatible with OmegaT) And there is no way to share dictionnaries. However, contrairly to Git/SVN, you cannot share the full project : if you want to share more than one TMX file, you will have to create as many instances of Cyclotis database as necessairly. This makes conflicts highly unprobable, unless you are in the same segment at the same time. CyclotisĬyclotis makes use of a SQL database in order to ensure an immediate synchronisation when you validate a segment. This means that changes appearing during this interval of time are not visible, and in case you change the same segment, a window will open to require you to solve the conflict immediately. However, the synchronisation occurs only when you do a save (or if you let OmegaT do it regularly, usually every 5 minutes). This has the advantage of preventing you from any manual work except the creation of the project in the server (OmegaT can check out a project, but not do the initial import in the server). In OmegaT 2.6 was introduced the possibility to use Git or Subversion to store a project shared by several users. This is probably an obsolete solution, but we keep it here for comparison. Solutions proposed, for example here, imply a manual copy of this file each time you want to synchronise with your collegues. However, the main file project_save.tmx is not really shareable this way. Since OmegaT automatically reloads a file when it detects a modification, you have no synchronisation problem related to these files. This works well if you want to share files which are not modified by OmegaT : TMX files in the tm/ directory, dictionnaries, some glossaries. In both cases the idea is to give the responsability to the operating system to make abstraction of the fact that your directory is distant. The compared solutions Shared directoryīefore version 2.6 of OmegaT, when users required information about sharing a project, they should have found several solutions based either on a shared directory (Windows CIFS, NFS. So that it is easier to read, we first describe it in a small table, then give more detail in plain text. By objective, we mean that we are open to comments and will be happy to complete the comparaison even if it is not in our advantage. In this article we try to make the more objective comparaison between our solution and already existing ones. If you want to share work between translators inside OmegaT, some other solutions exist.
0 Comments
Leave a Reply. |