Yes, it can. The Text Parser rule must contain a back reference for both, the ID and the comment.

Then the imported list will also import the comments

To exclude strings with “{Locked” in the comment from translation you can manually define a filter

After applying the filter you can select all displayed entries and mark them as read-only. This usually takes just a minute.

A more automated way can be achieved by implemented a system macro that automatically parses the comment after the file is imported and then is setting the read-only flag if the comment contains the “{Locked” string.

Hello Achim

Thank you very much for the detailed reply that indeed helped me get the comments displayed in Passolo.


When I used Find All command I was able to find all the strings that contained "{Locked" in the comments. But I have issues with getting filter to filter the strings that contain "{Locked" in the comments.
It just doesn't filter.

This issue was observed on Demo Passolo 2018 18.0.90.0, but with Passolo 2015 Team it works flawlesly. 

Thank you again for the help.

Simon

Sorry, my mistake. Instead of using

instr(.Comment, "{Locked") > 0

you have to use

instr(.ParserComment, "{Locked") > 0

With .Comment you access the manually inserted comment while the comment that is automatically imported from the source file is stored in .ParserComment

Sorry, my mistake. Instead of using

instr(.Comment, "{Locked") > 0

you have to use

instr(.ParserComment, "{Locked") > 0

With .Comment you access the manually inserted comment while the comment that is automatically imported from the source file is stored in .ParserComment

Aha, I see.

I saw the .ParserComment  in the editor but just didn't look at the remaining options in the filter dialog.

Interestingly, Passolo 2015 worked well  with instr(.Comment, "{Locked") > 0.

FYI, I just check the same on my Demo Passolo 2018 and somehow dosn't want to show only the strings with "{Locked" in the ParserComment.

Maybe it has something to do with the fact that it is a Demo version?

Anyway, your advice was very helpfull and to the point.

Thank you again.

Simon

You are right. Back in 2015 there was just one comment property named .Comment. The .ParserComment property was introduced in 2016 to allow a better differentiation between imported comments and project manager comments.

And your observation regarding the demo version is right too. In the demo version all automation features like the command line interface and the COM object model where these filter properties are used are disabled.

If you like to do a more deep dive testing please contact your SDL sales representative to get a time limited full version of the product.