Details
-
Bug
-
Resolution: Fixed
-
None
-
Critical
-
In addition to changing the default instance level value to disabled for the "runtimeOptions.editor.frontend.reviewTask.useSourceForReference" config, also the customer specific overwrites for this config will be set to disabled.
-
Revoke the default value for the "runtimeOptions.editor.frontend.reviewTask.useSourceForReference" config back to disabled.
-
Empty show more show less
Description
Change of default
Some weeks ago we changed the config
runtimeOptions.editor.frontend.reviewTask.useSourceForReference
to activated by default, because we thought, also for review tasks by default it makes sense, that the tag situation in the source text is the "source of truth".
This turned out to be a major problem, because in Trados internal tags of type "locked" are not copies of the source in the target. Yet they do refer to different trans-units (although those trans-units are clones of each other).
That it works like this in Trados can be found out only by reverse engineering (inspecting files, when users run into errors) because there is no sdlxliff spec out there.
Because of this reason we need to change back the default of
runtimeOptions.editor.frontend.reviewTask.useSourceForReference
back to deactivated, although the behavior of Trados is not like the xliff format is intended to work.
This again proofs, that the "shit in shit out"-principle should be followed regarding internal tags in files coming from other CAT tools, where the target is already filled. Also for those files the translator (that works outside of translate5) should be the expert regarding tags and if he produces tag errors, he maybe knows why and if they should be fixed, they should be fixed in the other CAT tool. Also this is the reason, why "disabled" makes sense as default setting for
runtimeOptions.editor.frontend.reviewTask.useSourceForReference
Still for files, where the config had been changed before import, changing it back to disabled, running the tag check afterwards and then correcting the tag errors does not solve the problem. File is still corrupt in Trados.
Therefore also
https://jira.translate5.net/browse/TRANSLATE-3420
is implemented, that will solve the problem for those files.
Adding to config description
Current description of the config is
runtimeOptions.editor.frontend.reviewTask.useSourceForReference
Use Source text as reference source for tags for review task
If enabled 'Source text' field is used as reference for checking and copying tags, otherwise 'Target text at time of import' is used. This is only for review tasks, so tasks where directly the bilingual files have been imported to translate5 and even for those tasks only for segments, that had already content in the target of the imported bilingual segments
Please add to it:
_For sdlxliff files it is important, that this config is disabled. If you enable it, the sdlxliff files exported from translate5 may be corrupt in Trados. Please see
for reasons why.
_
Attachments
Issue Links
- relates to
-
TRANSLATE-3420 SDLxliff corrupt after export, if imported untranslated into translate5 and containing internal tags of type locked
- Done