Gwen Gondry

Make sure this is not checked before you create your project:

If you create a small sample file with just this part in it, zip it up and attach to this thread, we can help you more efficiently.

Hi Paul,

Thanks a lot for replying to quickly. The box you mention is indeed NOT checked. 

As suggested, I'm sending you a sample file for your testing. Your thoughts will be greatly appreciated (as always!).

Gwen

CCT import issue_Sample.zip

Gwen Gondry

Looks like this is unlocked content and I also don't see a way to exclude this.  So I would do this... use the Advanced Display Filter to filter on the CCT, copy source to target, set as translated for completeness, and lock:

Then clear the filter and filter on unlocked:

Hi Paul, 

Many thanks for confirming that there is no way to exclude these CCTs. Your workaround is indeed what our PM did.

It would however be a good thing to be able to filter these out during XLIFF conversion, so as to reduce project preparation time and avoid overloading translators with segments to ignore and/or display instructions.

In addition, in order to make sure that our field values get updated, even when we have Perfect matches in locked segments, we need to allow locked segments to update our TMs. 

We're left with 2 options:

1. not copying the CTT source segments into the target column or copying them but not confirming segments, so that these fields don't get thrown into our TMs. But then our project statistics will always be off;
2. copying CTT source segments and confirming segments, but then our TMs will contain ENG>ENG segments.

None of these 2 options is really satisfactory.

Do you think more detailed file type options is something we could suggest SDL developing in the future?

Best,

Gwen

Hi Paul, 

Many thanks for confirming that there is no way to exclude these CCTs. Your workaround is indeed what our PM did.

It would however be a good thing to be able to filter these out during XLIFF conversion, so as to reduce project preparation time and avoid overloading translators with segments to ignore and/or display instructions.

In addition, in order to make sure that our field values get updated, even when we have Perfect matches in locked segments, we need to allow locked segments to update our TMs. 

We're left with 2 options:

1. not copying the CTT source segments into the target column or copying them but not confirming segments, so that these fields don't get thrown into our TMs. But then our project statistics will always be off;
2. copying CTT source segments and confirming segments, but then our TMs will contain ENG>ENG segments.

None of these 2 options is really satisfactory.

Do you think more detailed file type options is something we could suggest SDL developing in the future?

Best,

Gwen

Gwen Gondry

Gwen Gondry said:

Do you think more detailed file type options is something we could suggest SDL developing in the future?

You can ask.. see if you get any support...

http://ideas.sdl.com

Gwen Gondry

Gwen Gondry said:

We're left with 2 options:

1. not copying the CTT source segments into the target column or copying them but not confirming segments, so that these fields don't get thrown into our TMs. But then our project statistics will always be off;
2. copying CTT source segments and confirming segments, but then our TMs will contain ENG>ENG segments.

None of these 2 options is really satisfactory.

Not sure I follow this.  You could do this using the SDLXLIFF Toolkit across an entire project in one go:

1. copy source to target
2. change status to translated (without adding to TM)
3. lock them (so they are excluded from your stats)

Wouldn't that help?