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.

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.