The discussion revolves around missing translations for certain strings in the Discourse platform, particularly related to the Math plugin and other features like Footnote, Post Language button, and automated topic actions. duy initially noticed that the Discourse Math plugin wasn’t available for translation on Crowdin. Moin clarified that the Math plugin is part of the core project and should be included in the translation process, but the configuration was missing. A fix was proposed in a pull request by david, which was quickly merged. duy later identified additional strings not available for translation, including those for Footnote, Post Language, split topics, and autoclosed topics. david and Moin explained that some strings are hardcoded or part of post content, meaning translations only apply to new posts. keegan confirmed a hardcoded string for the Post Language button was fixed. The team acknowledged the issues and provided solutions, with updates being implemented to improve translation availability.
If it is important for you, you can change the text there without waiting for the translation. Customize text in Discourse works for texts that haven’t been translated like discourse_math.composer.insert_math too
Yes. This is like a post you create; the content does not change because a translation is updated. Also, the post is created in the default language of the forum. So here on Meta, new small action posts about posts being split will still be in English.
It’s a little like the “Continuing the discussion from %{postLink}:” text that is added when you reply as a new topic. The text is part of the post. It’s not dynamic.