this post was submitted on 02 Oct 2024
13 points (100.0% liked)

Firefox

7 readers
22 users here now

The latest news and developments on Firefox and Mozilla, a global non-profit that strives to promote openness, innovation and opportunity on the web.

You can subscribe to this community from any Kbin or Lemmy instance:

Related

Rules

While we are not an official Mozilla community, we have adopted the Mozilla Community Participation Guidelines as far as it can be applied to a bin.

Rules

  1. Always be civil and respectful
    Don't be toxic, hostile, or a troll, especially towards Mozilla employees. This includes gratuitous use of profanity.

  2. Don't be a bigot
    No form of bigotry will be tolerated.

  3. Don't post security compromising suggestions
    If you do, include an obvious and clear warning.

  4. Don't post conspiracy theories
    Especially ones about nefarious intentions or funding. If you're concerned: Ask. Please don’t fuel conspiracy thinking here. Don’t try to spread FUD, especially against reliable privacy-enhancing software. Extraordinary claims require extraordinary evidence. Show credible sources.

  5. Don't accuse others of shilling
    Send honest concerns to the moderators and/or admins, and we will investigate.

  6. Do not remove your help posts after they receive replies
    Half the point of asking questions in a public sub is so that everyone can benefit from the answers—which is impossible if you go deleting everything behind yourself once you've gotten yours.

founded 1 year ago
MODERATORS
yoasif@fedia.io
13
Yet another reason why you should use #Firefox (c.im)
submitted 1 month ago by youronlyone@c.im to c/firefox@fedia.io
2 comments fedilink hide all child comments
 

Yet another reason why you should use #Firefox

You can use: #BestViewedInFirefox

  • :lang(\*-Hang)
  • :lang("*-Latn)
  • :lang("zh", "ja", ko")
  • :lang(PT, DE, HE)

If you care about multilingual and multi-script support.

#language #lang #HTML #CSS #WebDev #BrowserWars

you are viewing a single comment's thread
view the rest of the comments
[–] lil5@fosstodon.org 2 points 1 month ago (1 children)

@youronlyone@c.im assuming what you’re showing to me is a Firefox only css, should we just use

html[lang=“jp”] h1 {}

[–] youronlyone@c.im 1 points 1 month ago

@lil5@fosstodon.org

It's not "Firefox-only" per se, it's CSS. Firefox is fast when it comes to implementing updates that benefits multilingual and Asian support, and Chromium is either slow, implements a small part only, or just ignores it completely.

(aside: Another good example is Ruby annotation. Firefox's implementation of Ruby is up-to-date while Chromium's stuck in 2010.

And this is very very annoying, you have to design for Chromium when it comes to Ruby annotations; or use JavaScript to serve different Ruby codes per browser. Chromium is practically the "modern IE6".)

It's the same with :lang().

In Chromium, you still have to do it like this:

:lang(en-GB), :lang(en-US), :lang(en-AU), :lang(en-NZ), :lang(en-PH) { }

In Firefox you can do it this way:

:lang(en-GB, en-US, en-AU, en-NZ, en-PH) { }

or

:lang("en-GB", "en-US", "en-AU", "en-NZ", "en-PH") { }

Another example, in Chromium:

:lang(ceb-Tglg), :lang(pam-Tglg), :lang(fil-Tglg) { }

:lang(ceb-Hano), :lang(pam-Hano), :lang(fil-Hano) { }

In Firefox:

:lang(\*-Tglg) { }  
:lang(\*-Hano) { }

or

:lang("*-Tglg) { }  
:lang("*-Hano) { }

^_~