Feature Requests item #3477099, was opened at 2012-01-21 14:04
Message generated for change (Comment added) made by martinfleurke
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=520350&aid=3477099&group_id=68187
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: OmegaT Application
Group: 2.5
Status: Open
Resolution: Fixed
Priority: 5
Private: No
Submitted By: Martin Fleurke (martinfleurke)
Assigned to: Martin Fleurke (martinfleurke)
Summary: Add patterns for text that should be removed and validate
Initial Comment:
In some circumstances you have text in the source segment that should be removed when translating. E.g. some comments or some other context that aids translation.
It would be great if you could specify a regular expression for those texts, so that the editor can color it in e.g. red and tag validation will find it if it is not removed.
----------------------------------------------------------------------
>Comment By: Martin Fleurke (martinfleurke)
Date: 2012-01-30 11:47
Message:
This FR is about tag validation, but can be useful for context and
comments.
If you want something that removes the 'context' and/or comments from the
source and still uses the context for multiple translations, and/or shows
the comments as comments in the comments-pane, then such feature must be
implemented at the file filters level (and thus for each filter
separately). The file filters are responsible for detemining the context
and comments.
Note that adding such feature would cause you to retranslate many segements
again (see the new 'disable auto-propagation function'). Note also that you
still would have to retranslate for every minor change, if it is about
context (not if it is about a comment).
You can make a new Feature Request for that
----------------------------------------------------------------------
Comment By: Guido Leenders (guido_leenders)
Date: 2012-01-30 05:44
Message:
I would like to add two observations. I was trying out this great new
functionality. Since providing context for translators is a major problem
for us. We generate the source text from a repository that describes
applications (tables, functions, columns, etc).
Observation 1: it would be great if the message would be shown in the notes
window instead inline. Of course, some formats allow comments/notes to be
present, but if you have to resort to a format that does not allow
providing hints, it would be great when the hint would be shown
accordingly.
Observation 2: the version in trunk works such that the whole segment,
including [CONTEXT: ...] must be translated. Effectively allowing one word
such as 'View' to be replaced by two translations: one for the verb, one
for the database object.
Combining these two observation, I think this change is great for providing
context, since it allows multiple translations in one go.
But I think is does not easily allow comments. Since a change in the
comment, how small the semantical impact even, requires the translator to
reconsider his previous translation.
I can imagine adding even an extra pattern "Comment Fragments" in the tag
validation window. They should be removed from the translation. Add do not
require an exact match in project_save.tmx, but only an exact match after
removal. Their contents is shown in Notes window.
What is your opinion?
----------------------------------------------------------------------
Comment By: Didier Briel (didierbr)
Date: 2012-01-26 02:52
Message:
Fixed in SVN (/trunk).
Didier
----------------------------------------------------------------------
Comment By: Martin Fleurke (martinfleurke)
Date: 2012-01-25 13:58
Message:
In the tag validation options dialog you can add some regular expression.
tet in target segments that matches is rendered red and shown in tag
validator. Text in source segement that matches is shown in italic.
----------------------------------------------------------------------
Comment By: Martin Fleurke (martinfleurke)
Date: 2012-01-25 13:57
Message:
@didier: yes. This is about patterns that are helpful comments to the
translator (that are not in the 'comments' pane), or maybe notes that the
translator himself adds (for QA) which have not been added to the notes
pane.
My use case is: we add "[CONTEXT: translate thus such and so]" to text in
source files, like "ambigue word" -> "[CONTEXT: translate thus such and
so]ambihue word". Most source files (like html) don't support comments, so
we put them inline and force the translator to remove them when
translating, using this feature.
----------------------------------------------------------------------
Comment By: Didier Briel (didierbr)
Date: 2012-01-21 14:24
Message:
Is that a different case than having a pattern for text that would be
effectively removed, including in the source text, so that the translator
would not even see it?
Didier
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=520350&aid=3477099&group_id=68187
|