search

openedx / frontend-app-authoring

Front-end for the Open edX Studio experience, implemented in React and Paragon.
GNU Affero General Public License v3.0
13 stars 76 forks source link

[editors] Localization issues - strings not marked for translation #1237

Open arbrandes opened 1 year ago

arbrandes commented 1 year ago

Description

(This has a sister issue, https://github.com/openedx/frontend-app-communications/issues/148, and both are being tackled simultaneously via https://github.com/openedx/wg-translations/issues/16.)

As first noted on Slack 2023-08-15 by @sambapete, it seems when previewing the type of problems some strings may not be properly identified for translations.

For instance, in src/editors/data/constants/problem.js, there are no indications that "Specify one or more correct numeric answers, submitted in a response field." would be translated.

There is also no corresponding section in Transifex.

(Side bug: all "Learn more" links point edx.readthedocs.io.)

Solution space

The owning team has been contacted via one of the project's wiki pages.

This repository is also up for inclusion in the Atlas (aka OEP-58) pilot (as is frontend-app-communications) , as opposed to pursuing the usual edx-transifex-bot route.

OmarIthawi commented 11 months ago

Thanks for documenting the issue @arbrandes. The solution would be to use formattedMessage calls:

OmarIthawi commented 9 months ago

This issue has been fixed as far as the Communications MFE is concerned. The solution has been done by adding an atlas pull argument to the Makefile building step:

Some strings may not make it and needs to be marked correctly as formattedMessage like I've mentioned in my previous https://github.com/openedx/frontend-app-course-authoring/issues/1237.

This repository still needs the formattedMessage calls.

cc: @ehuthmacher @arbrandes