#i18n

Reusable components like Dropdown Menus and Toasts with accessibility, internationalization and themes built-in are just a few aspects that make the new webUI shine ✨ Animations, gifs and transitions are automatically disabled when prefers-reduced-motion is set. Yes, everything you've asked for, like web push + proper PWA, and much more is coming. I'm a man of my word. Just look at https://loops.video 🤠 #pixelfed #webUI #accessibility #i18n #redesign

17 July is the one day of the year when the calendar #emoji is correct! The word emoji combines the Japanese e (絵, picture) + moji (文字, character) and dates back to the late 80s. Its similarity to the English "emotion" is just a coincidence. Nowadays, emoji are standardised by the Unicode Consortium, a Californian non-profit that has its roots in facilitating a universal digital representation of the world's writing systems. #Unicode doesn't specify exactly how emoji should look – so they're different on Android and Apple devices, for example – but it lists their names. The first major character set used in computing was #ASCII, the American Standard Code for Information Interchange, published in 1963. Using 7 bits, it could represent 128 characters — more than enough for a to z, A to Z, 0 to 9 and common punctuation marks, but certainly indicative of a North American worldview. Later "extended" versions of ASCII doubled this to 256 possibilities, allowing for dozens of accented letters, characters like æ and ß, and symbols like © and ¾. And double-byte character sets like Shift JIS meant that Chinese, Korean and Japanese could be represented in full. But multiple standards existed, and it became just a bit too common to see ����. The answer was Unicode: a single, multi-byte character encoding standard for everyone. Plus emoji! #language #i18n

@yayfee@mastodon.ml @rf@mastodon.ml терпеть не могу те русские раскладки клавиатур, которые подсовывают запятую вместо точки на нумпаде #клавиатура #i18n #l10n

Quantum’s Lang package is evolving in 3.1.0.

What used to be single file-based translations is now an adapter-based, multi-provider translation system.

Built-in providers now include:

• File translations
• DeepL
• Google Translate

The code is already available on GitHub as part of #533: https://github.com/quantum-php/framework/tree/master/src/Lang

This is an early announcement before the 3.1.0 release.

#PHP #QuantumPHP #OpenSource #i18n

@hongminhee@hollo.social @liaizon@social.wake.st @Edent@mastodon.social @north@xn--8r9a.com @Profpatsch@mastodon.xyz (1/3) Report back from #FediForum last week. Held a good session on #GloballyInclusive handles. Just a few attendees, but one knew the technical issues deeply and was well connected to ActivityPub design. Session notes will likely appear at https://fediforum.org/topics/#topic-internationalization in a few weeks. For now, here is a summary: #i18n #GloballyInclusiveFediverse #Fediverse #Multilingual

Zalgo Text in Fediverse handles? #FediForum #FediForum2026 #i18n

Terence @Edent@mastodon.social, Jason @north@xn--8r9a.com, Hong @hongminhee@hollo.social, I appreciate your steps in #i18n for #FediVerse. Do you plan to attend #FediForum next week (28-30 April, 15-20h UTC)? I will propose a session on "#Globally-inclusive Fediverse handles". If you were present, it would improve the session. I think Philip Patsch @Profpatsch@mastodon.xyz will demo too. https://fediforum.org/2026-04/ #UniversalAcceptance #Multilingual

How do you know early when #Haikuos is preparing for a new release? It's when I start asking people to have a look at our #i18n / #translation tool and help complete translations for various languages. For beta releases, our policy is to include only languages where the translation is at least 60% complete. This time we need help to reach this in Belarusian, Croatian, Bulgarian, and Slovenian. Lithuanian and Slovak are above 60% but may need some help too.