I wish the #W3C#CSSWG will finish #Ruby so the PITA Chromium-based browsers will finally implement proper Ruby support.
It works well with Firefox, but looks messy with Chromium-based browsers.
Also, anyone following CSS-Ruby are probably aware that there is a serious conflict between CSS-Ruby and HTML-Ruby. There are HTML-Ruby elements deprecated by #HTML5 Working Group, but is important under CSS-Ruby.
The CSS-Ruby should be the one followed, not the deprecation made in HTML5.
I hope someone in @w3c@webi18n can do something about it. It has been like 7 years already?
We seemed to have reached a new level in the #aipocolypse where no English speaking users are using chatbots to open support issues.
Nearly 3 weeks in to this support request and I finally got a hint that this might be the case. Although looking back maybe I should have noticed it sooner.
Either way I don't know how exactly to proceed so I've been asking around for native French (I think) speakers to help. If that's you, please let me know!
No one cares about issues like #email address internationalization (EAI) or international domain-name (IDN) support until their email client or service fails to deliver an important message. #i18n
📣Find out what other W3C Groups or areas are up to:
• @w3cdevs developers relations
• @wai Web Accessibility Initiative #a11y
• @webi18n Internationalization of the Web #i18n
• @tag Technical Architecture of the Web
• @ab W3C Advisory Board #FediFollows
To speakers of underrepresented languages: If your language isn't available in Mastodon's posting window and you'd like me to add it, please let me know.