Sophie Brugnon 

Can you share the PO file itself, or at least half a dozen lines or so?  At a guess it might look like this:

sb_maybe.po

Out of the box Trados Studio doesn't expect this where the msgid field contains the reference key (like routes.home.text) and the msgstr field contains the actual French translation.  Trados Studio will always show the reference keys in the source column and the French text in the target column when it sees a file like this.  I think it might be because your file is a software localization files where the developer uses key-based references rather than the actual source language text.  So in Trados Studio you would overwrite the translation... I think!

If the file was structured like this:

sb_probably_should_be.po

Then you'd see the msgid field in the source and the msgstr would hold the target translation, and you'd still be able to see the keys in the DSI column:

Or even better if you use the DSI Viewer app from the appstore: https://appstore.rws.com/Plugin/25

Both formats are valid... and both are a guess... so best to see your actual file to give you better advice if you still need it.

For more flexibility around this you might find the PO filetype app from Supertext to be a better solution as this offers a lot more flexibility around what you extract and where it gets displayed... clearly Supertext do a lot of these files and understand the requirements well: https://appstore.rws.com/Plugin/259

Sophie Brugnon 

Can you share the PO file itself, or at least half a dozen lines or so?  At a guess it might look like this:

sb_maybe.po

Out of the box Trados Studio doesn't expect this where the msgid field contains the reference key (like routes.home.text) and the msgstr field contains the actual French translation.  Trados Studio will always show the reference keys in the source column and the French text in the target column when it sees a file like this.  I think it might be because your file is a software localization files where the developer uses key-based references rather than the actual source language text.  So in Trados Studio you would overwrite the translation... I think!

If the file was structured like this:

sb_probably_should_be.po

Then you'd see the msgid field in the source and the msgstr would hold the target translation, and you'd still be able to see the keys in the DSI column:

Or even better if you use the DSI Viewer app from the appstore: https://appstore.rws.com/Plugin/25

Both formats are valid... and both are a guess... so best to see your actual file to give you better advice if you still need it.

For more flexibility around this you might find the PO filetype app from Supertext to be a better solution as this offers a lot more flexibility around what you extract and where it gets displayed... clearly Supertext do a lot of these files and understand the requirements well: https://appstore.rws.com/Plugin/259