Shirley Yeng 

I see what you mean.

In your source file you have where its marked as locked

In the SDLXLIFF format post translation 
We see no target translation applied and the segment is still in a locked state

But when looking at the file generated the locked status is now false with translation (despite what your screen shots show)

Subsequently your original source which has locked=false

now has a different state

What I am not sure about is why are both 

<source>图鉴1·圣诞</source>

<source>图鉴2·圣诞</source>

coming through as segment 5 as noted below

When its clear these are 2 different segments in the source 

I will dig deeper and update this post accordingly

Lyds

Thank you Lyds

Hi Shirley Yeng , In case of Memsource XLIFF files with empty „target” elements (<target />), the segment numbers are not assigned correctly. This issue was logged for Development as CRQ-37160, to fix in a future version of Studio. The incorrect locked segments also seem to be related to the missing „target” elements. If I unlock the locked segments in the Editor, copy source to target, and then lock them again, the locked segments are correctly written into the target file.

Hi Edith,

I also raised a new fault regarding Memsource XLIFF files
Issue during generating target translations - 2. Trados Studio - Trados Studio - RWS Community
Can you help me check this as well?

Hi Shirley Yeng , can you please double-check if you referenced the correct thread? In the one you mentioned the source is a bilingual Excel file.

Hi Edith,

Yes, it's a bilingual Excel file.

The issue is
When I generate the target translation Trados will add extra spaces at the beginning of the cells, even though there is no exception in sdlxliff.