Jan N 

Select Include with Text instead. Does it work?

Thank you but that doesn't change anything, works (or rather does not work) the same

Jan N 

The problem is that Trados Studio sees this placeholder at the start of the sentence and assumes (incorrectly in this case) that it's not needed in there as it's at the start anyway.  I'm not sure if this is intended behaviour or a bug, but I do think it should respect the "include" option - Patrik Mazanek fyi/comment?  If you view "All Content" instead of "All Segments" you'll see it and can move it in manually if needed:

One solution to this is to use tag pairs instead... lookahead for the opening and lookbehind for the closing.  For example:

That will get you this:

Not perfect but at least you have it automatically in segment and the content is locked.  Maybe that helps?

 Dear Paul ,

Thank you very much for looking into this. I'm aware about using the "All content" option, but it's not really convenient when preparing multiple languages, and it requires additional manual work either by us, or by our linguists.

The other option - lookahead/lookbehind - is very interesting. We probably won't use it in this scenario, but I was looking for a way to create the locked content for quite some time now, so finally I know how to do that - thank you very much! It's always great to learn something new.

As for the original issue - I think this is kind of a bug, as the option "Include" should simply work, that's why the option is there. But it might be somehow related to the formatting of the source document. If you select all text in Word and change the font to Courier New (for example), the "Include" option suddenly works well. I find it very interesting. We found two other ways how to make it work - which makes me think it has something to do with the formatting:

1. If we remove emojis from the paragraph, the "Include" option starts working

2. If we just type Starry Mice so it uses the same font and colour as the rest of the text, the "Include" option starts working correctly as well

This all seems to be as an issue somehow connected to the formatting of the source DOCX file. But in either case, I still think that the option "Include" should work by default regardless of formatting or other things.

Thank you again for your help with this one. If you come around anything more related to that, please let me know, as I'm curious ;)

With kind regards,

Jan

 Dear Paul ,

Thank you very much for looking into this. I'm aware about using the "All content" option, but it's not really convenient when preparing multiple languages, and it requires additional manual work either by us, or by our linguists.

The other option - lookahead/lookbehind - is very interesting. We probably won't use it in this scenario, but I was looking for a way to create the locked content for quite some time now, so finally I know how to do that - thank you very much! It's always great to learn something new.

As for the original issue - I think this is kind of a bug, as the option "Include" should simply work, that's why the option is there. But it might be somehow related to the formatting of the source document. If you select all text in Word and change the font to Courier New (for example), the "Include" option suddenly works well. I find it very interesting. We found two other ways how to make it work - which makes me think it has something to do with the formatting:

1. If we remove emojis from the paragraph, the "Include" option starts working

2. If we just type Starry Mice so it uses the same font and colour as the rest of the text, the "Include" option starts working correctly as well

This all seems to be as an issue somehow connected to the formatting of the source DOCX file. But in either case, I still think that the option "Include" should work by default regardless of formatting or other things.

Thank you again for your help with this one. If you come around anything more related to that, please let me know, as I'm curious ;)

With kind regards,

Jan