Language Tags for Text Fields
B
Becca
We’d love to see support for language tagging in text fields.
Right now, we’re forced to use WYSIWYG fields everywhere there is text because content may be written in either Te Reo Māori or English (or a mixture). This creates several challenges:
* We can’t apply character limits or input validation.
* Editors can paste in poorly formatted content (e.g. from Word), which breaks layout and styling, or they can create lists, headings etc. mid component.
* We lose semantic clarity around which language is being used, which affects accessibility and screen reader support.
Adding language tagging would help with:
* Accessibility: Screen readers can correctly pronounce Te Reo Māori and English when language is tagged.
* Cultural integrity: Ensures Te Reo Māori is treated as a distinct and respected language, not just styled text.
* SEO: Improves search engine indexing and relevance for bilingual content.
* Translation workflows: Makes it easier to identify and manage multilingual content.
* Analytics: Enables tracking of language usage for reporting and planning.
* Styling: Allows for language-specific formatting or layout adjustments.
This would also allow us to move back to simpler, structured fields where appropriate, improving consistency and reducing formatting issues.
Keen to hear if this is on the roadmap or if others are facing similar challenges!
Ana Hoseit
Completely agree with this suggestion from Becca. Also, it would be nice if we had a visual cue when language tags were applied to text in WYSIWYG. Currently we have to install a JSON file. This way our text editors could easily look at a page and see if language tags had been applied to the te reo (visual cue is a light underline under the word). It is too difficult to try and explain to text editors how to install the JSON file – I struggle with it every time I need to reinstall. This was a feature we had in Oracle.