Wrong text transformation on geminate Ls
Categories
(Core :: Layout: Text and Fonts, enhancement)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox116 | --- | fixed |
People
(Reporter: zipus.technologies, Assigned: jfkthame)
References
Details
(Keywords: parity-chrome, parity-safari)
Attachments
(2 files)
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/114.0
Steps to reproduce:
I've noticed an issue with the text-transform:capitalize property in CSS when used on words containing "l·l" in Catalan (see Interpunct - Catalan https://en.wikipedia.org/wiki/Interpunct#Catalan). When this rule is applied to such words, the CSS interpreter incorrectly treats the interpunct as a word boundary and capitalizes the letter after it.
To illustrate, consider the word "cancel·lar". When text-transform:capitalize is applied, it currently results in "Cancel·Lar". However, according to Catalan language rules, it should be "Cancel·lar" instead. The interpunct is not considered a word boundary, and the second 'l' should not be capitalized.
For context, I filled previously the issue to MDN (mdn/content#26968), they reported me to fill a issue to CSSWG (w3c/csswg-drafts#8987) and them to report to BugZilla.
Actual results:
Cancel·Lar
Expected results:
Cancel·lar
Updated•2 years ago
|
Comment 1•2 years ago
|
||
Firefox is not against the spec, since CSS Text says that word boundaries are UA-dependent.
But Blink and WebKit do what would be expected in Catalan, so it would be good if Firefox aligned with them.
| Assignee | ||
Comment 2•2 years ago
|
||
Seems reasonable, yes. So although U+00B7 is classified as punctuation, we'd treat it like a hyphen or apostrophe within a word.
| Assignee | ||
Comment 3•2 years ago
|
||
Updated•2 years ago
|
Comment 6•2 years ago
|
||
In https://github.com/w3c/csswg-drafts/issues/8987#issuecomment-1598820175 @moyogo makes the point, with examples, that this is an issue for other languages besides Catalan, and with other letter combinations. It looks like the proposed code change covers that, but i'm just leaving this here for any future reader.
Comment 7•2 years ago
|
||
| bugherder | ||
Description
•