Re: Intent to remove: Ability to specify the Raanana macOS system font by its Hebrew name in CSS

On Wed, Jan 18, 2017 at 9:38 AM, Jonathan Kew wrote: > Note that the current CSS Fonts 3 spec explicitly says that UAs are required > to recognize localized font names: > > "Some font formats allow fonts to carry multiple localizations of the family > name. User agents must

Re: Intent to remove: Ability to specify the Raanana macOS system font by its Hebrew name in CSS

Forgot the bug link: https://bugzilla.mozilla.org/show_bug.cgi?id=1331859 On Wed, Jan 18, 2017 at 11:38 AM, Jonathan Kew wrote: > As you've noted, Chrome does not actually support this, so there is not full > interoperability in this area; but if we decide to remove this

Re: Intent to remove: Ability to specify the Raanana macOS system font by its Hebrew name in CSS

On 18/01/2017 07:04, Henri Sivonen wrote: I'm in the process of rewriting our encoding converter infrastructure in Rust. For a new implementation, it makes sense to support only the Web-exposed encodings, that is, the encodings specified in the Encoding Standard. Currently, Firefox supports

Re: Intent to remove: Ability to specify the Raanana macOS system font by its Hebrew name in CSS

* Including a special-case check for the name Raanana when enumerating > the system fonts > My preference as well, though I'm not convinced it's worth doing. The Wikipedia page for the city of Ra'anana [0] marks up the city's Hebrew name as: רַעֲנָנָה‎ The Hebrew version [1] doesn't specify

Intent to remove: Ability to specify the Raanana macOS system font by its Hebrew name in CSS

I'm in the process of rewriting our encoding converter infrastructure in Rust. For a new implementation, it makes sense to support only the Web-exposed encodings, that is, the encodings specified in the Encoding Standard. Currently, Firefox supports decoding non-Encoding Standard encodings in one