Correct `lang=` HTML tag attribute should be used for target language text on Web UI
Description
Environment
Attachments
- 31 May 2018, 01:04 am
- 31 May 2018, 01:04 am
Activity
Former user 20 April 2018 at 00:23
We are closing all the old issues to have more clarity in our backlog for Zanata project. Feel free to re-open or leave a comment if you require our attention on your Jira.
Carlos Munoz 30 November 2015 at 22:43
We could remove the lang attribute from the html in the new editor for the time being. (per @Sean Flanigan's suggestion)
We have to keep in mind that the UI is in itself multilingual as we could have as many as 3 languages in the UI at a time.
Sean Flanigan 30 November 2015 at 05:17
There could be up to three different languages in different elements in the editor, all at once. There's the language Zanata itself (or in this case, the editor) is using, there's the source (TextFlow) language, and of course the target translation language (TextFlowTarget). We need to set the correct lang for all three cases.
Until we sort that out, it might help to remove the lang=en attribute, and perhaps the browser will be able to auto-detect the right lang at least in some cases.
Former user 30 November 2015 at 00:32
This should be trivially easy to add while migrating the text flows to use React, so I will add the lang attribute as part of the migration.
Details
Details
Assignee
Reporter
Sprint
Fix versions
Affects versions
Priority
unspecified
In the Alpha (webapp) version, a global
<html ... lang="en">attribute is present, making all the text being treated as English text in the browser. Since browsers (like my Chrome) may choose fonts and sometimes OpenType features likeloclby this attribute, many text end up being rendered oddly or even wrongly.In the original version, there is not even a
langattribute, so I doubt if I should treat this as a bug in it too.