In our translation process, we use Subversion to exchange TMX files between translator and a person aware of the industry-specific words. Not all words are contained in a glossary, nor do all translator grasp the meaning as easy. Also, sometimes we have error in the source document.
For all these reasons, the translator and other persons working on a translation project need to communicate. In the past we used Word files for this. In the Word file the translator put the segment number (which of course changes as the source changes) and their questions/remarks. Other people replied on this. This was cumbersome: Word files have a very coarse level of granularity when exchanged through SVN since it is a binary format where simultaneous changes from multiple people can not be processed easily.
Therefore we switched to the Note feature (<note>). That works great. However, in a project with 7.000 segments, only a few dozen have a note. We used to search for a specific agreed upon string to find the next note from the user interface. Or just looked directly into the tmx.
However, for new translators it is easier just to press a key or choose a menu option to go to the next segment to be translated with a note. Dito for previous note.
Each person working on the project can then just browse quickly through the notes to find the ones applicable for him. Change where necessary. And send back answer through Subversion. Which answers get merged quite nicely into the work of others.
If the functionality is ok as a good addition, I want to offer the patch attached for inclusion in OmegaT trunk.
Patch for this functionality.
Implemented in SVN (/trunk).
Didier
Note that, to find segments with notes, you don't have to "search for a specific agreed upon string".
In the Search window, just check Notes (uncheck Source and Translation), and search for an empty string in Exact mode, or for a dot ('.') in Regular expression mode.
Didier
Closing...
This feature was implemented in the released version 2.5.1 update 1 of OmegaT.