When a segment is marked as read-only in the xliff the target segments in translate5 remain empty. If a term matches the source segment it will be underlined red as the corresponding target term is not used.

This should not happen because the target term being missing is not an error in this case.

Added by marcmittag: We have several reasons in translate5, why a segment could be locked. Only the case, when the segment had already been locked in the original translation  system should lead to the blue marking of terms instead of  red marking. Because this means, that with the segment everything is ok, completely independent of what translate5 thinks of it. This should be the case completely indenpendent what content exists in the target segment (or if any).