Note: this export may include core translation domains if they are used by the module's files. However, only the wordings used by the module are to be included in the exported file.
ShopNotificationsError is explicitly stated in the example.
These two texts are contradictory. In fact, while translating, the core wordings (Shop and Admin) are not shown for translation. But when exporting the files, the spec expects them to be exported.
The real behavior is that modules always ignore core domains (Shop and Admin).
Considerations
I think the current behavior is correct. Modules may use existing core translations (Shop and Admin). But I cannot imagine a use case when it would be legitimate that a module translation overrides or extends wordings of domains other than Modules.
Proposed correction
I think in Export Installed module translations the note cited above should be removed.
Also the example should be corrected to:
It looks like the specs are contradictory in regards to the translation of modules:
In Installed module translations is written:
In Export Installed module translations is written:
ShopNotificationsError
is explicitly stated in the example.These two texts are contradictory. In fact, while translating, the core wordings (
Shop
andAdmin
) are not shown for translation. But when exporting the files, the spec expects them to be exported. The real behavior is that modules always ignore core domains (Shop
andAdmin
).Considerations I think the current behavior is correct. Modules may use existing core translations (
Shop
andAdmin
). But I cannot imagine a use case when it would be legitimate that a module translation overrides or extends wordings of domains other thanModules
.Proposed correction I think in Export Installed module translations the note cited above should be removed. Also the example should be corrected to: