How to translate plugin if it uses shared domain

The best way to handle this is to NOT share text domains between plugins.

If you want to go against the general recommendation of one text domain per plugin, then you can expect friction.

If for some reason you MUST share the text domain, then I suggest you configure the “primary” plugin to see the source strings in the secondary plugin (by adding its source file paths in the Advanced config). Then use only the primary plugin to manage the template and the translation files.

It’s a plugin of external developer, so only option to add source path can be suitable. Thanks, the suggestion was really helpful