Page MenuHomePhabricator

Summary does not use language direction
Closed, ResolvedPublic


Autogenerated strings for the summary should have embedded direction marks, at least in the cases where it is possible to set them. When they are autogenerated in a specific language the direction should be set for the string, and if the string is user supplied it should be possible to default to the sites content language. Otherwise it could in some cases be possible to detect, and fallback to, the user language.

Version: unspecified
Severity: enhancement



Related Objects

Event Timeline

bzimport raised the priority of this task from to Lowest.Nov 22 2014, 12:48 AM
bzimport set Reference to bz38488.
bzimport added a subscriber: Unknown Object (MLST).

[Removing RESOLVED LATER as discussed in . Reopening and setting priority to "Lowest" as discussed on IRC.
For future reference, please use either RESOLVED WONTFIX (for issues that will not be fixed), or simply set lowest priority. Thanks a lot!]

This could be quite simple if the browsers reads first char of its own text content and sets direction on that, that is if lang="auto" is set. If so the first content should be the user provided value, and then the direction can be set depending on the characters used in the value. This must although be checked against the generated html-structure and how the individual browsers react on getting its tested content after other tagged content.