Tikal extraction ignores -nocopy option with -seg option
Issue #571
resolved
When running tikal -x with the -seg option, the -nocopy option is ignored, and targets contain the source text.
Comments (3)
-
reporter -
The issue you reported (source text gets copied into target even if
-nocopy
is set) is a valid issue: By default the segmenter copies the source and, clearly, it should not if-nocopy
is there. I'm fixing it right now.Now, the issue of the CAT tool not liking empty/absent targets is another issue. From an XLIFF viewpoint it is perfectly valid to have an XLIFF file with a source (segmented or not) with an empty target or no target. The CAT tool is apparently not supporting XLIFF very well.
-
- changed status to resolved
The -nocopy option in Tikal is now respected when extracting using the -seg option. This resolves issue
#571.→ <<cset b88359f6ba1b>>
- Log in to comment
Now I am not sure if it is an issue at all. I have created a script that removed all the contents of the target units, and now my CAT tool complains that xliff is not pretranslated (target slot missing). Can somebody explain me why segmented units have to be pretranslated?