Hello,
I have a problem with translating some hard-coded content in MFE (Micro Frontend).
One solution I’ve thought of is creating custom IDs and default messages, and then trying to translate them that way or does anyone have any better ideas or suggestions for this kind of issue?
Thank You! 
Would it be possible to make an upstream pull request to make these translatable strings?
I think that all of these title, previewDescription, and description values can be changed to message IDs instead of hard-coded strings.
e.g.
export const ProblemTypes = StrictDict({
[ProblemTypeKeys.SINGLESELECT]: {
- title: 'Single select',
+ titleMessage: 'authoring.problemEditor.types.singleSelect.title',
preview: singleSelect,
- previewDescription: 'Learners must select the correct answer from a list of possible options.',
+ previewDescriptionMessage: 'authoring.problemEditor.types.singleSelect.previewDescription',
- description: 'Enter your single select answers below and select which choices are correct. Learners must choose one correct answer.',
+ descriptionMessage: 'authoring.problemEditor.types.singleSelect.description',
...
Then, they can be rendered like this:
<FormattedMessage id={data.previewDescriptionMessage} />
As long as the messages are defined in the messages.ts files, it will work fine.
@braden thank you for your suggestion! We’ve already completed this.
I noticed that Open edX translation WG is showing 100% translated and reviewed in Spanish, but it doesn’t seem like everything is fully done.
@braden I’m still looking into a solution for this. Do you have any comments or thoughts
Can you please link to the PR? I want to make sure it’s fixed on master, and I hadn’t seen it.
I agree you should be able to do that but I’ve never actually used our translations tooling so I’m not sure how to achieve it, sorry.
I am working on the same part in the advanced list, facing a few issues related to JSX. Once I have resolved and tested this, I will submit a pull request. Additionally, I have another pull request on my list that I will also handle.
We tried your solution, but it’s not working as expected. It also prints id also I don’t have much expertise in React.js, so I might be missing something.
After applying your solution, another issue has appeared: we are unable to edit the problem or add any types using options like single set, dropdown, etc.
@braden or @sarina Can you please connect us with a person who has experience in this area? We would like to reach out to them on Slack to troubleshoot and fix this issue together.
@Yagnesh I think the best thing to do would open your pull request as a draft, and get feedback on it.
