Feature request - Tag string as translated

[svatas]

As I used OmegaT+ frequently in the last week, I noticed some
"missing" features. It is common to create a translation from original
files but many strings (segments in OT+ terminology) are the same in
original and translated version.

There is no possibility how to tag some string as translated. This
will helps a lot as we can decide, which string is or not translated.
I have many strings which have the same string for original and
translation and I do not "touch" them. In this version of OmegaT+ the
only possibility to "translate" some string is to change something in
it. Then it is skipped when using "Goto unext untranslated" and
statistic is updated as well.

Is there any possibility to implement tag "Translated/Untranslated
string/segment"? Am I missing something and this is implemented now?

Svatopluk Vit

[laseray]

Hi Svatopluk,

On Jul 7, 4:21 am, svatas <svatopluk....@gmail.com> wrote:
> Is there any possibility to implement tag "Translated/Untranslated
> string/segment"? Am I missing something and this is implemented now?

That functionality does not exist yet. The feature to color/style
segments according to translated, untranslated, and so forth was only
added in the most recent version. This kind of feature is sort of
towards helping translators see the state of a particular segment.
What you are suggesting may be an additional feature added to that
perhaps.

To implement this there will be some issues with storing the state of
the segment (as translated, but not really translated) between uses of
a project. It seems simple, but actually problems will arise when the
original documents are changed/updated. If the documents all remained
static and unchanging then it would be straightforward, but in
practice this is not what users will end up doing a percentage of the
time. Plus, you will have to mark each segment manually (as
translated, but still original). Doable, but possibly tedious.

Anyway, there are a number of potential issues to sort out for that
specific feature.

In the meantime, if you want to work around this issue then you can
(tediously) add a text marker to each segment that will remain as
original so you can jump over them when trying to go to the next
untranslated segment. For instance, add an uppercase word at the
beginning of the segment, like "DONE" or whatever. Finish the
translation, generate the documents, and then in a text editor/
wordprocessor remove the markers with Find/Replace (replace with
nothing to remove it) that most applications have.

Please file the feature request on the project through SourceForge so
that it can be tracked and dealt with later.

Regards,

Raymond