Export the source lists into a translatoin bundle. Developers can use the free Translation Edition to check and edit the read-only states and to add comments.  

Sorry but IMHO  it's not an option to ask developers to install a localization version just because the translator is not able to export a bunch of strings to be checked somehow ;-) Don't you think so, too? It's as if a graphics designer would ask his/her customers to have a trial version of their software because the don't ge the picture out as jpg...

I don’t agree and cannot understand the comparison made with the graphics designer tool. You don’t just export a rendered “jpg picture”, you expect other users to edit the “picture” which always require some kind of editor tool.

Our customers have implemented the following solutions:

• A number of customers have several licenses and also use them in development for automation and localization engineering, which exactly covers the use case described.
• Customers with just one license use a floating license and share it between development and localization management.
• When just one single license of the Team Edition is available the proposed procedure with the bundles with source lists is secure, easy to use and does not require any additional licenses because it works with the free Translator Editions.
• There might be other clients that don’t want to choose any of these approaches. Using the macro technology and the free SDK these customers can implement any other user defined process.

So. I think it should just be said that EXPORT seems to be for translation only ((since that's what SDL Passolo is all about)).
I tried to see if there was any Export format that would export the source strings *with* the read-only strings are there is not. The Passolo Text format allows source string export, but will not include read-only strings as those are "not to be translated" so there is that.

If you need a quick hack, you can always sort by STATUS and then screenshot the read-only strings, but if you want an editable text file it seems you are out of luck.
The only answer is exporting the source lists into a translation bundle. Unfortunately in this case.

Thank you, Ian for your answer. Yes, I understand that Passolo is made for translation. However, interaction with development is (or should be) an integral part of localization management. And part of that, in my situation (which should not be that unusual ..) is to "talk about" certain types of strings and exchange (information about) them, so it would be great to be able to export a set of strings according to a custom definition that is not related only to translation....

My sixpence anyways... :-)

Thank you, Ian for your answer. Yes, I understand that Passolo is made for translation. However, interaction with development is (or should be) an integral part of localization management. And part of that, in my situation (which should not be that unusual ..) is to "talk about" certain types of strings and exchange (information about) them, so it would be great to be able to export a set of strings according to a custom definition that is not related only to translation....

My sixpence anyways... :-)