You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Fix _button.text and _button.ariaLabel incorrectly marked as translatable #128
_tutor._button.text and _tutor._button.ariaLabel in both component.schema.json and course.schema.json are marked "translatable": true, but their defaults are Handlebars template references ({{_globals._extensions._tutor.hideFeedback}}). Because the translation export resolves defaults, these fields appear in the CSV as the raw template string rather than an actual translatable value, polluting every export with content that needs to be manually removed before sending to translators.
The genuinely translatable string — hideFeedback in course.schema.json — is already correctly marked "translatable": true. The four _button fields should be "translatable": false.
Search for rows containing {{_globals._extensions._tutor.hideFeedback}}
Expected behaviour
Only genuinely translatable strings should appear in the export. Handlebars template references that resolve at runtime should not be included.
Actual behaviour
_tutor._button.text and _tutor._button.ariaLabel appear twice in the CSV (once from component.schema.json, once from course.schema.json) as the raw string {{_globals._extensions._tutor.hideFeedback}}. These are not translatable values and must be manually removed before the CSV can be sent to translators.
Suggested Fix
The fix in each case is changing "translatable": true to "translatable": false.
Regarding the suggested solution: If someone did change the values away from the default handlebars templates, then the new values wouldn't be translated because their schema wouldn't be marked as translatable.
I personally have never seen an instance of using different variant text for question buttons on a question-by-question basis. I can think of two other solutions:
Modify button text in course.json only (remove per-component variant). Avoids UI bloat in AAT and keeps the model simpler.
Update the export tool to strip out handlebars template references.
Activity
oliverfoster commentedon Mar 26, 2026
Regarding the suggested solution: If someone did change the values away from the default handlebars templates, then the new values wouldn't be translated because their schema wouldn't be marked as translatable.
joe-replin commentedon Mar 26, 2026
I personally have never seen an instance of using different variant text for question buttons on a question-by-question basis. I can think of two other solutions: