Comment tokens always consider the original submission language of a comment and do not take the translated value. Additionally to that, the comment body field is optional and may not be present.
1. Load the translated comment appropriate for the token's context.
2. Only attempt to use the comment body field if its present.
Postponed on
🐛
Not all node, taxonomy entity tokens are multilingual aware
Needs work
Add tests.
None.
None.
Postponed
10.1 ✨
(Drupal 8 Multilingual Initiative) is the tag used by the multilingual initiative to mark core issues (and some contributed module issues). For versions other than Drupal 8, use the i18n (Internationalization) tag on issues which involve or affect multilingual / multinational support. That is preferred over Translation.
The change is currently missing an automated test that fails when run with the original code, and succeeds when the bug has been fixed.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
This was a bugsmash triage target a few days ago. mstrlen suggested either postponing this on the traits being introduced in 🐛 Not all node, taxonomy entity tokens are multilingual aware Needs work or splitting the creation of the traits to a new issue. Since the traits are already in the patch of the other issue I am choosing the first option, postponing.