My module creates and manages some config_entities programmatically (ie. not through an EntityForm) in response to associated content entities being saved.
In order to handle multi-language content entities, I see two options:
- create one config entity and add translations for it
- create a unique config entity for each translation
The first seems cleaner - however, I don't see how to actually transparently manage translations for config entities. Translating an entity with the
config_translation module appears to create a new entry in the
config table with
collection = language.xx, but I don't see how to access a translated entity explicitly (rather than it being automatically mapped by the site's interface language). Is this even possible?