Support of context

Coming from this discussion and from my experience with gettext

Is your feature request related to a problem? Please describe. Some times a same message can be translated differently depending on context, so catalog should contains as many as entries as needed

Describe the solution you’d like A way to handle hierarchical structure of message id or abstraction around context option / attribute

Describe alternatives you’ve considered I tried id with prefixed message but it could lead to translation error.

[tricoder42]

Hey @JSteunou, unfortunatelly, context isn’t supported at the moment. @FredyC also come across msgctx while improving po file support, but we agreed we won’t include it at the moment.

Possible workaround is either to use message ID context.id with default message or add context to default message ((context) message). In upcoming release, there’s gonna be support for message descriptions, so you can communicate with translator what kind of message is it.

I believe we could support message context even without breaking the app completely. We could join message descriptor into single ID during compile if app uses context. For that we need to figure out how to transform IDs in production code, similar to #139.

I’ll leave it open for now, but considering possible workarounds, it has a little priority. I’m open to suggestions!

[tricoder42]

@FredyC Ops, I missed that. Here it is: https://lingui.js.org/ref/macro.html#description