it seems that Chrome is applying Unicode normalization and Firefox isn't, which makes these three sequences display differently: Ấ Ấ Ấ should Firefox be normalizing too? @ManishEarth @behdadesfahbod @zwnj
-
-
the other thorny question is how Unicode NFC and decomposition are supposed to interact with CSS font fallback; unfortunately the spec completely punts on this issue and leaves it up to the UA and to authors: https://www.w3.org/TR/css-fonts-3/#char-handling-issues …
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
Different font fallback strategies? Chrome shapes with HarfBuzz checks for 0 glyph indices and tries fallback, HarfBuzz will try NFC then NFD before giving up. Firefox checks if the font has glyph for a character, if not tries fallback, no normalization.
-
Right, at the moment Prince uses the same strategy as Firefox, but it doesn't always produce good results, so I think we'll switch to the normalization approach. It would be better if the CSS Fonts spec recommended this instead of leaving it open, I think.
- Još 2 druga odgovora
Novi razgovor -
-
-
Weird things in general happening. Here are all 3 sequences in Chrome and Firefox with <span style="font-family:'Abyssinica SIL',AdobeBlank"> (but for each font on our system). ¯\_(ツ)_/¯pic.twitter.com/EVOTZxlKd2
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.
Mozilla Research.
Open Source.
Likes languages.
Repatriate/ABCD.
Formerly physics. he/him