Before answering the question I want to clarify that Passolo supports 3 different comment fields.

• Comments that are imported from the source file
• Comments that are created by project managers in the source string list
• Comments that are created by translators in the translation list (1 comment filed per target language)

Where have you inserted your comments?

Thanks for the quick answer, Mr Herrmann,
The first 2 kinds, because "real" translation (i.e. in P2) has not taken place yet.

1. There are comments already in the source file
2. And I as project manager (I guess) am trying to add further comments in Passolo to the sources of P1, to help the translators to interpret the GUI strings correctly. 
   I was hoping that these would propagate through to the sources of P2 (i.e. 2nd LPU in the cascade), and even into the target files of P1, but they don't.

Excerpt from a PO file.  Source file comments are prefixed with #.

#. Title for dashboard config
#. Name of route to dashboard config
msgid "Dashboard configuration"
msgstr "Dashboard configuration"

I tested it, and it works, at least with my latest 2018 version. Comments that you are inserting as a project manager into the source list will be inherited into the comment field of the cascaded project. Can you please check if your comment is a project manager or a translator comment.

I double click in the comments cell of a string in the sources in P1.  Passolo prefixes a "C".
I guess this is a proj mgr comment, as I can make one comment per source string, not one per language.

Here's what I do in screenshots:

Initial state in P1

Add comment to a source string in P1

Save and close P1, open P2
Select and create/update source strings in P2

Look for commented string in sources of P2.  The source-file comment has come over OK, but the Passolo comment I added has been lost.

I need to re-test the issue with Passolo 2016. According to the release notes https://gateway.sdl.com/apex/communityknowledge?articleName=CUs-Passolo-2016 this issue was already fixed in Passolo 2016 CU3. In Passolo 2018 I can't reproduce it.

Ok, I re-tested the issue with Passolo 2016 16.0.412.0 (see above) and can confirm that it is working properly. Project manager comments must be inserted into the source list of the base project, the translation list of the base project must be updated. Then the cascaded project must be opened and updated. Now the project manager comments will be available in the cascaded project.

Maybe one additional side note: when translated target PO files are created, Passolo doesn't store the project manager comments into the translated PO file. On the other side translator comments inserted with Passolo will be stored into the translated PO file into the translator comment field (#) without any additional character.

Thanks.

I confirm that "project manager comments" made in Passolo in the sources of P1 are now propagating through to the target string lists of P2.

Achim Herrmann said:

Project manager comments must be inserted into the source list of the base project, the translation list of the base project must be updated.

Looking back at my screenshots I think my mistake was to save P1 without updating the source string lists.

Thanks again.
Peter.

Thanks.

I confirm that "project manager comments" made in Passolo in the sources of P1 are now propagating through to the target string lists of P2.

Achim Herrmann said:

Project manager comments must be inserted into the source list of the base project, the translation list of the base project must be updated.

Looking back at my screenshots I think my mistake was to save P1 without updating the source string lists.

Thanks again.
Peter.