| 08:31 | <hsivonen> | While looking into yesterday's topic, I learned that CSS text-transform in Firefox supports Irish, but CLDR/ICU does not. (Commented on https://unicode-org.atlassian.net/browse/ICU-23349 ) Also, CSS text-transform in Firefox has Turkish-like i behavior for Tatar, Crimean Tatar, and Baskir, which aren't listed in SpecialCasing.txt, which only lists Is there some CLDR/Unicode history here that I should be aware of? For example, are the Turkish-like rules for languages other than Turkish and Azerbaijani considered not establishe and stable enough for SpecialCasing.txt, or is it just a matter of no one having sorted this area out more comprehensively? |
| 08:35 | <hsivonen> | The section 5.18.2 Complications for Case Mapping in the Unicode Standard is silent about Irish. |
| 08:58 | <eemeli> | Also regarding the same conversation from yesterday: I didn't realize until looking into it afterwards that the CSS Furthermore, the MDN entry for |
| 14:42 | <Richard Gibson> |
I think I'd push for only affecting the start of the first word-like segment, and possibly further requiring that segment to itself be first |