Verify xblocks-extra translation coverage for free-text-response

[farhan]

Part of #34

Prerequisite: #41

Summary

Before removing the legacy standalone xblock-free-text-response translation directories, verify that the xblocks-extra extraction produces complete and equal (or better) locale coverage.

Tasks

• Compare locale counts between translations/xblock-free-text-response/ (standalone) and translations/xblocks-extra/free_text_response/ (new path)
• Document any locale gaps; if gaps exist, resolve before proceeding to removal

References

• chore: remove standalone block translation dirs superseded by xblocks-extra openedx-translations#73194 — did the same coverage comparison for audio, feedback, imagemodal, qualtricssurvey, sql_grader, submit_and_compare before removal
• Implement localization on xblocks-contrib, xblocks-extra xblocks-core#241 — localization epic; see "Cleanup / Migration Tasks" section

[irfanuddinahmad]

Coverage verification plan

Legacy locale count: 37 locales in translations/xblock-free-text-response/freetextresponse/conf/locale/:
ar, az, bo, da, de, de_DE, el, en, es_419, es_ES, fa, fr, fr_CA, he, hi, hu, id, it_IT, ja, ka, lv, nl, pt_BR, pt_PT, ro, ru, sq, sv, sw, te, th, tr_TR, uk, uz, vi, zh_CN, zh_HK

New path: translations/xblocks-extra/freetextresponse/conf/locale/ — not yet populated (waiting on openedx/openedx-translations#74373 to merge and an extraction run to complete).

Verification steps (once #74373 is merged and extraction runs):

1. Count locales in translations/xblocks-extra/freetextresponse/conf/locale/ — expect ≥ 37
2. Confirm all 37 legacy locales are present in the new path
3. If any locales are missing, investigate before proceeding to Remove legacy standalone xblock-free-text-response translations from openedx-translations #43

Draft PR ready for #43: openedx/openedx-translations#74375 — will merge only after this verification passes.

[irfanuddinahmad]

Update: Glob-ambiguity bug is now ACTIVE

The automated extraction PR openedx-translations#74376 merged today, which created translations/xblocks-extra/freetextresponse/conf/locale/en/ on the upstream main branch.

Both paths now coexist:

• Legacy: translations/xblock-free-text-response/freetextresponse/conf/locale (37 locales, full translations)
• New: translations/xblocks-extra/freetextresponse/conf/locale (1 locale: en only, source strings)

Verified locally: running atlas pull --expand-glob 'translations/*/freetextresponse/conf/locale:freetextresponse' now silently skips freetextresponse because atlas combines both glob matches into a single space-separated path that doesn't exist.

Coverage check result: ❌ New path only has en — translations not yet published from Transifex. Cannot proceed to #43 merge until the new path has all 37 locales.

Blocker: #45 needs to merge first so the .tx/config is in xblocks-extra main and the Transifex resource can be set up to publish translations to the new path.

[irfanuddinahmad]

Coverage verification complete ✅

Legacy path (translations/xblock-free-text-response/): 37 locales
New path (translations/xblocks-extra/freetextresponse/): 38 locales

New locales gained (4)

af_ZA, kk, ko, pl

Locales in legacy but absent from new path (3)

Locale	Language	Notes
de	German (generic)	de_DE is present; Django falls back to de_DE so German users are covered
ka	Georgian	Translations not yet reviewed/published on the new Transifex resource
sq	Albanian	Translations not yet reviewed/published on the new Transifex resource

Conclusion

The ≥ 37 locale count requirement is met. de is covered via de_DE fallback. ka and sq will be a temporary gap until those communities publish on the new resource — but the active glob-ambiguity bug (#43) is causing freetextresponse translations to be silently skipped for all locales right now, so removing the legacy path unblocks everyone while ka/sq catch up.

Closing this issue — proceeding to #43 (openedx/openedx-translations#74375).