Hi Jesse Good 

Unknown said:

1. Is it documented anywhere?

Only internally.  I don't know why this didn't go in the release notes.

Unknown said:

2. What files types currently have this behavior?

I'm sharing exactly what we have written up internally:

======================

Requirements for translating empty target segments

I. Filters for bilingual files (XLIFF, GDF, Bilingual Excel, etc.)
The content from the target segment, whether it is empty or not, will always be written as it is in the target file, regardless of segment pair status and the contents of the source segment.

II. Filters for non-bilingual files
For this type of filters there are 2 different situations, according to the segment pair status:

1. Segment pair is not confirmed
This case represents all the segment pair statuses except Translated, Translation Approved and Signed-Off.

Outcome: the source text is copied into the target file.

2. Segment pair is confirmed
This case represents the segment pair statuses Translated, Translation Approved and Signed-Off.

Outcome: the source text is not copied into the target file, leaving the text empty.

Notes:
Other segment properties such as lock status or match percentage must not affect the rules above.

Out-of-segment content is not subject to these rules.

Filters which USE this processor as described are these:

• Microsoft PowerPoint 2007-2016
• Microsoft Word 2007-2016
• Microsoft Excel 2007-2016
• HTML 4
• HTML 5Json

======================

So if you are getting the same behaviour with other filetypes can you share some examples with me?  I just spoke to the filter manager and there have been no changes in this area so it would be good to validate them and understand what's happenning.

Thank you

Hi Paul

Great answer!

I also get this behavior with XML files, here is a simple XML file if you would like to test it out.
Just throw this in any project, set the status to "translated" and then generate the target translation.

<?xml version="1.0" encoding="utf-8"?>
<IllustTrans>
<Content>hello</Content>
</IllustTrans>

Thanks Jesse Good , I see what you mean. I knocked up an InDesign and Framemaker file and these also behave the same way. So I have gone back to the development team and will confirm the outcome when I know. In some ways it makes sense to have consistent behaviour like this across all monolingual filetypes... but let's see what the team thinks.