# i18n Published articles for i18n. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Babel in Khan Academy's i18n Toolchain DevFeed: [Babel in Khan Academy's i18n Toolchain]() Original publisher: [Read original article]() Author: Khan Academy Published: 2015-06-22T22:00:00Z Content type: article Language: en Sources: [Khan Academy]() Topics: [Babel](), [Internationalization (i18n)](), [ECMAScript](), [React](), [Test-driven development]() Tags: [api](), [architecture](), [argument](), [arguments](), [ast](), [babel](), [build-system](), [callback](), [class](), [classes](), [destructuring](), [engineering](), [es6](), [eslint](), [exports](), [foreach](), [frontend](), [function](), [functions](), [i18n](), [jsx](), [news](), [web-frontend]() ### AI overview Khan Academy's Babel migration preserved its custom i18n workflow by adding a Babel plugin that turns `<$_>` and `<$i18nDoNotTranslate>` JSX tags into function calls. Matching jstransform required retaining generated line numbers and exact whitespace in translation strings; the team compared Gettext `.pot` files from both build paths and used fixtures to isolate whitespace differences. Migration testing also caught two transformer issues: class output still contained `let` until `es6.blockScoping` was added to the whitelist, and Babel's function-name transformation could make a `setInterval` method call itself by shadowing the global. The article reports that Babel maintainers fixed the issues and describes the plugin as a relatively straightforward way to preserve the existing build workflow. ### Source excerpt By Kevin Barabash We've been using ES6 (along with JSX) for sometime at Khan Academy. Right now, we're ... Read more ## postmarketOS in 2026-08: Conferences DevFeed: [postmarketOS in 2026-08: Conferences]() Original publisher: [Read original article]() Published: 2026-09-06T00:00:00Z Content type: news Language: en Sources: [postmarketOS]() Topics: [Developer Events](), [Test automation](), [Mobile Testing](), [Internationalization (i18n)]() Tags: [2026](), [alpine](), [automated-testing](), [conferences](), [defcon](), [gdb](), [i18n](), [infrastructure](), [libc](), [linux](), [matrix](), [nura](), [organizational](), [os](), [postmarketos]() ### AI overview Conference activity was the month's main theme: postmarketOS had stands at FrOSCon, FOSSY and DEFCON, and its own conference schedule went live, though the event was already fully booked. Video recordings or streams were being explored without a guarantee. Project updates include faster GitLab hosting after repositories moved to SSDs, a production debuginfod server for postmarketOS and Alpine, and working collation in the musl locale overhaul. A newly accepted proposal aims to release an immutable postmarketOS version and improve automated hardware testing. A merged policy permits case-by-case support for bootstrap software associated with proprietary tools such as Steam, with safeguards including explicit user choice and disclosure, maintenance by at least two community members, and documentation. Other updates cover generic postmarketOS kernels for x86_64, Fairphone 5 rear camera support, and apkmr for testing merge requests. ### Source excerpt Conferences has been the main theme of this month. We had stands at FrOSCon (photo, next to our friends from Phosh), FOSSY (pictured above) as well as DEFCON and the following postmarketOS / Linux Mobile related talks were given: Automated testing of a phone operating system (Luca at FrOSCon) Push-Benachrichtigungen. Dezentral und OpenSource (Daniel G. at FrOSCon) Random Cool Things from postmarketOS (a linux-based mobile OS) (Ranny at DEFCON) Controlling our devices: linux on mobile (Ranny at DEFCON) Besides that we have of course been very busy planning our own conference and are happy to announce that the schedule is now live! For those who did not get a ticket, the event is completely booked now but we are trying to do video recordings and/or live streams so you can watch the talks at home (no promises for that though since this is our first event). If all goes well, we might even follow up with another one next year. For those who will be there, make sure to join the Matrix chat / IRC channel. Organizational OSUOSL, who maintain gitlab.postmarketos.org, have reacted to slowdowns we have observed across the site and made it significantly faster by moving git repositories to SSDs. Thanks, Lance! Paul has joined the infrastructure team. NLnet and NGI Zero Core related news A production debuginfod server for postmarketOS and Alpine was set up, "allowing developers to automatically fetch debug symbols during crash analysis with tools like coredumpctl and gdb" (!9468, sync-debuginfod, milestone 34) An update was posted by Rich on the collation + i18n support in musl libc project: "I'm pleased to announce a big step in the #musl locale overhaul project: collation is working! This is the result of a long project to design data structures and logic that would admit honoring the full Unicode Collation Algorithm rules, including equivalence under normalization, and keep the size of collation weight tables for the entirety of Unicode under control." And last but not least, ## postmarketOS August 2026 Update: Conferences, Infrastructure, and Software Projects DevFeed: [postmarketOS August 2026 Update: Conferences, Infrastructure, and Software Projects]() Original publisher: [Read original article]() Published: 2026-09-06T00:00:00Z Content type: news Language: en Sources: [postmarketOS]() Topics: [Linux](), [Mobile](), [Software Testing](), [Operating system](), [GitLab](), [Internationalization (i18n)](), [gdb]() Tags: [2026](), [conferences](), [gdb](), [git](), [gitlab](), [i18n](), [infrastructure](), [linux](), [mobile](), [opensource](), [postmarketos](), [testing]() ### AI overview The August 2026 postmarketOS update covers conference appearances and a newly scheduled project conference, infrastructure improvements including faster Git repositories and a new debuginfod server, progress on musl libc collation and internationalization support, and an accepted proposal for an immutable postmarketOS release with improved automated hardware testing. ### Source excerpt Conferences has been the main theme of this month. We had stands at FrOSCon (photo, next to our friends from Phosh), FOSSY (pictured above) as well as DEFCON and the following postmarketOS / Linux Mobile related talks were given: Automated testing of a phone operating system (Luca at FrOSCon) Push-Benachrichtigungen. Dezentral und OpenSource (Daniel G. at FrOSCon) Random Cool Things from postmarketOS (a linux-based mobile OS) (Ranny at DEFCON) Controlling our devices: linux on mobile (Ranny at DEFCON) Besides that we have of course been very busy planning our own conference and are happy to announce that the schedule is now live! For those who did not get a ticket, the event is completely booked now but we are trying to do video recordings and/or live streams so you can watch the talks at home (no promises for that though since this is our first event). If all goes well, we might even follow up with another one next year. For those who will be there, make sure to join the Matrix chat / IRC channel. Organizational OSUOSL, who maintain gitlab.postmarketos.org, have reacted to slowdowns we have observed across the site and made it significantly faster by moving git repositories to SSDs. Thanks, Lance! Paul has joined the infrastructure team. NLnet and NGI Zero Core related news A production debuginfod server for postmarketOS and Alpine was set up, "allowing developers to automatically fetch debug symbols during crash analysis with tools like coredumpctl and gdb" (!9468, sync-debuginfod, milestone 34) An update was posted by Rich on the collation + i18n support in musl libc project: "I'm pleased to announce a big step in the #musl locale overhaul project: collation is working! This is the result of a long project to design data structures and logic that would admit honoring the full Unicode Collation Algorithm rules, including equivalence under normalization, and keep the size of collation weight tables for the entirety of Unicode under control." And last but not least, ## Implement RTL and bidirectional text support in web layouts DevFeed: [Implement RTL and bidirectional text support in web layouts]() Original publisher: [Read original article]() Author: Joost de Valk Published: 2026-07-09T00:00:00Z Content type: tutorial Language: en Sources: [The Website Specification]() Topics: [User interface design](), [Responsive Design](), [Media Queries](), [Icon font]() Tags: [bidi](), [css](), [flexbox](), [html](), [i18n](), [layout](), [locale](), [recommended](), [rtl]() ### AI overview The article explains how to support right-to-left scripts and bidirectional text in web interfaces. It recommends setting language and direction separately, using CSS logical properties, mirroring directional icons, and applying `dir="auto"` or `` to handle user-generated and embedded text. ### Source excerpt Sites that serve Arabic, Hebrew, Persian, or Urdu must set dir="rtl" and use CSS logical properties so layouts mirror correctly without hard-coded left and right. ## hreflang for language and regional URLs DevFeed: [hreflang for language and regional URLs]() Original publisher: [Read original article]() Author: Joost de Valk Published: 2026-07-09T00:00:00Z Content type: tutorial Language: en Sources: [The Website Specification]() Topics: [search-engines](), [Microformats]() Tags: [http](), [https](), [i18n](), [recommended]() ### AI overview The article explains how hreflang signals equivalent language and regional URLs to search engines. It covers BCP 47 tags, reciprocal and self-referential alternate links, x-default, and choosing a single delivery method across HTML, HTTP headers, or XML sitemaps. It also identifies common implementation mistakes and explains that hreflang helps search engines serve a better-matched URL but does not affect ranking on its own. ### Source excerpt hreflang tells search engines which language or regional version of a page to show to which user. It uses BCP 47 codes and must be reciprocal across all alternates. ## translate attribute for untranslatable content DevFeed: [translate attribute for untranslatable content]() Original publisher: [Read original article]() Author: Joost de Valk Published: 2026-06-18T00:00:00Z Content type: tutorial Language: en Sources: [The Website Specification]() Topics: [Internationalization (i18n)](), [alt text](), [Localization (l10n)]() Tags: [alt-text](), [astro](), [chrome](), [code](), [edge](), [firefox](), [i18n](), [language](), [optional](), [safari](), [translation]() ### AI overview The global HTML `translate` attribute tells machine translation systems whether to translate an element and its translatable attributes. The article explains how `translate="no"` can protect brand names, code, identifiers, and other text that should remain unchanged, and contrasts the attribute with `lang`. ### Source excerpt The translate attribute marks content that automatic translation systems must leave alone -- brand names, code, and identifiers. Use translate="no" so Google Translate and the browser's built-in translation don't mangle terms that have no localised form. ## Locale-aware content DevFeed: [Locale-aware content]() Original publisher: [Read original article]() Author: Joost de Valk Published: 2026-05-29T18:54:03Z Content type: tutorial Language: en Sources: [The Website Specification]() Topics: [Internationalization (i18n)](), [Localization (l10n)]() Tags: [apis](), [english](), [i18n](), [javascript](), [locale](), [recommended]() ### AI overview Locale-aware content adapts dates, numbers, currency, units, sorting, and other presentation details to a user's conventions. The article explains how to resolve one locale per request, format consistently with JavaScript Intl APIs and server-side ICU libraries, negotiate locale preferences, and avoid common formatting mistakes. ### Source excerpt Dates, numbers, currency, and units should be formatted in the user's locale. Use Intl APIs in the browser and the same locale data server-side so output matches expectations. ## Avoid automatic IP-based language redirects DevFeed: [Avoid automatic IP-based language redirects]() Original publisher: [Read original article]() Author: Joost de Valk Published: 2026-05-29T18:54:03Z Content type: tutorial Language: en Sources: [The Website Specification]() Topics: [Redirection](), [Search engine optimization (SEO)]() Tags: [avoid](), [i18n]() ### AI overview Automatic IP or Accept-Language redirects can trap visitors in the wrong locale, prevent search engines from reaching translated pages, and break shared links. The article recommends letting users choose, keeping localized URLs stable, and using a non-blocking suggestion when appropriate. It also provides checks for verifying locale behavior. ### Source excerpt Automatically redirecting visitors to a locale based on IP geolocation or Accept-Language is an anti-pattern. It traps users in the wrong language, breaks search crawlers, and breaks shared links. Let users choose. ## Internationalised Domain Names (IDN) DevFeed: [Internationalised Domain Names (IDN)]() Original publisher: [Read original article]() Author: Joost de Valk Published: 2026-05-29T18:54:03Z Content type: tutorial Language: en Sources: [The Website Specification]() Topics: [Domain Name System (DNS)](), [DNS security]() Tags: [attacks](), [canonical](), [case-folding](), [dns](), [encoding](), [i18n](), [optional](), [spoofing]() ### AI overview Internationalised domain names allow non-ASCII characters in hostnames. They are encoded as Punycode for DNS and shown in Unicode by browsers, subject to display policies designed to reduce homograph attacks. The article explains implementation practices for registration, certificates, hostname input, normalization, storage, and browser testing. ### Source excerpt IDNs let domain names contain non-ASCII characters. They are encoded as Punycode on the wire and rendered as Unicode in the browser, subject to anti-spoofing rules. ## lang attribute on inline content DevFeed: [lang attribute on inline content]() Original publisher: [Read original article]() Author: Joost de Valk Published: 2026-05-29T18:54:03Z Content type: tutorial Language: en Sources: [The Website Specification]() Topics: [Localization (l10n)](), [Web Content Accessibility Guidelines](), [Internationalization (i18n)]() Tags: [english](), [i18n](), [japanese](), [required](), [wcag]() ### AI overview The `lang` attribute identifies the natural language of an HTML element. This guide explains how to mark passages whose language differs from the surrounding page, use BCP 47 tags, and avoid common mistakes. It says correct declarations help screen readers pronounce text properly and support browser spelling, typography, search, and translation behavior. ### Source excerpt Mark passages, phrases, and inline elements that differ from the document language with a lang attribute. WCAG 3.1.2 requires it so assistive tech can switch pronunciation. ## Plural rules and grammatical number DevFeed: [Plural rules and grammatical number]() Original publisher: [Read original article]() Author: Joost de Valk Published: 2026-05-29T18:54:03Z Content type: tutorial Language: en Sources: [The Website Specification]() Topics: [structure](), [Groovy]() Tags: [categories](), [code](), [costs](), [developers](), [go](), [how-to](), [i18n](), [implement](), [language](), [languages](), [like](), [number](), [plural](), [recommended](), [review](), [rules](), [strings](), [translation](), [type]() ### AI overview The article explains how CLDR plural categories vary across languages and recommends using Intl.PluralRules to select localized message forms instead of hard-coded English singular/plural logic. It also covers ordinal rules, localized number formatting, and translation formats that let translators supply the needed forms. ### Source excerpt Most languages don't pluralise like English. Use CLDR plural categories -- zero, one, two, few, many, other -- via Intl.PluralRules instead of hard-coded 'item' vs 'items' logic. ## Language switcher DevFeed: [Language switcher]() Original publisher: [Read original article]() Author: Joost de Valk Published: 2026-05-29T18:54:03Z Content type: tutorial Language: en Sources: [The Website Specification]() Topics: [Localization (l10n)](), [CSS]() Tags: [i18n](), [recommended](), [screen-readers](), [ui]() ### AI overview A language switcher should label each locale in its own language, use per-link lang and hreflang attributes, avoid using flags to represent languages, and preserve the user's chosen page and explicit locale URL. The article also recommends making the control discoverable, indicating the current locale, and testing it with a screen reader. ### Source excerpt List each locale in its own language ('Deutsch', '日本語', 'العربية') and mark it with the right lang attribute. Don't use flags -- flags are countries, not languages. ## Writing modes and CJK line breaking DevFeed: [Writing modes and CJK line breaking]() Original publisher: [Read original article]() Author: Joost de Valk Published: 2026-05-29T18:54:03Z Content type: tutorial Language: en Sources: [The Website Specification]() Topics: [User interface design](), [Dark Mode]() Tags: [accessibility](), [css](), [flexbox](), [grid](), [i18n](), [japanese](), [korean](), [optional](), [signage]() ### AI overview This tutorial explains how CSS writing-mode, text-orientation, line-break, and word-break support vertical layouts and script-appropriate wrapping for CJK and Thai text. It also covers language metadata, logical CSS properties, and common readability pitfalls. ### Source excerpt Vertical text (Japanese, Traditional Chinese, Mongolian) needs CSS writing-mode. Chinese, Japanese, Korean, and Thai also need explicit line-break and word-break rules so wrapping respects script-specific conventions. ## Localised page metadata DevFeed: [Localised page metadata]() Original publisher: [Read original article]() Author: Joost de Valk Published: 2026-05-29T18:54:03Z Content type: tutorial Language: en Sources: [The Website Specification]() Topics: [Open Graph protocol](), [alt text](), [Microformats](), [RDF (Resource Description Framework)]() Tags: [english](), [i18n](), [recommended](), [structured-data](), [translation]() ### AI overview A tutorial on localizing website metadata alongside page content. It covers translating titles, descriptions, Open Graph and Twitter Card fields, JSON-LD properties, image alt text, and PWA manifest names, plus setting locale attributes and checking rendered results across search and social previews. ### Source excerpt Translate every visible string in the head and in structured data -- title, meta description, Open Graph fields, JSON-LD names and descriptions, image alt text -- not just the body. A localised body with English metadata is a half-translation. ## hreflang in XML sitemaps DevFeed: [hreflang in XML sitemaps]() Original publisher: [Read original article]() Author: Joost de Valk Published: 2026-05-29T18:54:03Z Content type: tutorial Language: en Sources: [The Website Specification]() Topics: [Internationalization (i18n)](), [SVG]() Tags: [google-search](), [html](), [i18n](), [implement](), [language-en](), [locale](), [optional](), [sitemaps](), [xml]() ### AI overview Sitemaps can declare language and regional page alternates with the XML xhtml:link element, providing the same search-engine signal as inline hreflang tags. The article explains how to structure reciprocal alternate links, choose a delivery method, and verify the resulting clusters. ### Source excerpt Declare language and regional alternates inside the XML sitemap with xhtml:link instead of in the HTML head. Easier to maintain at scale and keeps localisation metadata separate from content. ## International URL structure DevFeed: [International URL structure]() Original publisher: [Read original article]() Author: Joost de Valk Published: 2026-05-29T18:54:03Z Content type: tutorial Language: en Sources: [The Website Specification]() Topics: [Internationalization (i18n)](), [Search engine optimization (SEO)]() Tags: [cctld](), [i18n](), [implement](), [locale](), [recommended](), [scope](), [url]() ### AI overview For multilingual or multi-regional sites, choose one URL pattern--ccTLD, subdomain, or subdirectory--and use it consistently. The guide compares their operational and locality tradeoffs, recommends pairing canonical URLs with hreflang, and advises setting locale from the URL rather than silently negotiating from the Accept-Language header. ### Source excerpt Pick a single URL pattern for multilingual or multi-regional content -- country-code top-level domain, subdomain, or subdirectory -- and stick with it. Optionally localise the slugs too. ## Finally, Mercari Japan in English! Our Road to Cross-Platform i18n DevFeed: [Finally, Mercari Japan in English! Our Road to Cross-Platform i18n]() Original publisher: [Read original article]() Author: Andy Hall Published: 2025-12-08T10:00:40Z Content type: article Language: en Sources: [Mercari Engineering]() Topics: [Internationalization (i18n)](), [cross-platform](), [Website](), [Android](), [iOS](), [App](), [Back end](), [Code]() Tags: [android](), [app](), [backend](), [code](), [cross-platform](), [i18n](), [ios](), [ui]() ### AI overview Mercari describes shipping English UI support for its main marketplace app across iOS, Android, and the web. The post explains how earlier engineering work using internationalization libraries and patterns prepared the codebase, why the release was delayed, and how internal English locale overrides reduced the urgency to ship the feature. ### Source excerpt This post is for Day 8 of Merpay & Mercoin Advent Calendar 2025. For more than a decade, Mercari's Marketplace has been a Japanese service - sometimes to the annoyance of our many, many employees who don't speak Japanese. But as of late November, we've finally shipped English UI support for our main flea market [...] ## Docusaurus 3.9 DevFeed: [Docusaurus 3.9]() Original publisher: [Read original article]() Author: Sébastien Lorber Published: 2025-09-25T00:00:00Z Content type: release Language: en Sources: [Docusaurus Blog]() Topics: [releases](), [Node.js](), [Algolia](), [Artificial Intelligence](), [Internationalization (i18n)](), [layout]() Tags: [ai](), [algolia](), [bug-fixes](), [i18n](), [layout](), [node-js](), [release](), [releases](), [upgrade]() ### AI overview Docusaurus 3.9 drops support for Node.js 18, raising the minimum required version to Node.js 20. It adds Algolia DocSearch v4 with AskAI, improves internationalization support, adds Mermaid ELK layout support, and includes other improvements and bug fixes. ### Source excerpt We are happy to announce Docusaurus 3.9. ## ScreenshotWhale Generates App Store Screenshots with a Layer-Based Editor and Automatic Localization DevFeed: [ScreenshotWhale Generates App Store Screenshots with a Layer-Based Editor and Automatic Localization]() Original publisher: [Read original article]() Author: Jorge Castillo Published: 2025-09-16T16:36:22Z Content type: article Language: en Sources: [Effective Android]() Topics: [App](), [Artificial Intelligence](), [Vibe coding](), [Figma](), [Internationalization (i18n)](), [Cloud](), [User Experience]() Tags: [ai](), [android](), [app](), [app-store](), [building](), [cloud](), [code](), [coding](), [editor](), [export](), [figma](), [i18n](), [ios](), [languages](), [phones](), [templates]() ### AI overview The article introduces ScreenshotWhale, a cloud-based service for creating app store screenshots. It offers a Figma-style layer-based editor, templates, support for Android and iOS device formats, and automatic internationalization during export. The product is in its initial stages and is presented as seeking user feedback. ### Source excerpt Some words for the people who joined the newsletter these days. ## Launching ScreenshotWhale.com 🐋 DevFeed: [Launching ScreenshotWhale.com 🐋]() Original publisher: [Read original article]() Author: Jorge Castillo Published: 2025-09-13T15:03:52Z Content type: release Language: en Sources: [Effective Android]() Topics: [App](), [Android](), [iOS](), [Internationalization (i18n)](), [export](), [Cloud]() Tags: [android](), [app](), [cloud](), [editor](), [export](), [i18n](), [image](), [ios](), [layer](), [screenshots](), [templates]() ### AI overview ScreenshotWhale has launched as a cloud-based tool for creating app screenshots. It includes an online editor, templates, multilingual export, support for iOS and Android form factors, a mirror feature, app store layout settings, and layered editing. ### Source excerpt The wait is over, screenshotwhale is live today 🎉 ## Bluesky Likes Web Components DevFeed: [Bluesky Likes Web Components]() Original publisher: [Read original article]() Author: Lea Verou Published: 2025-06-17T00:00:00Z Content type: article Language: en Sources: [Lea Verou's blog]() Topics: [Web Components](), [API](), [Bluesky](), [Web]() Tags: [a11y](), [api](), [api-design](), [article](), [blog](), [bluesky](), [components](), [i18n](), [launch](), [open-source](), [web-components](), [web-standards]() ### AI overview The author presents web components for displaying Bluesky post likes and discusses the practical challenges of building accessible, localizable components that consume public API data. The article highlights Bluesky's open API, which allows unauthenticated access to public data without an API key. ### Source excerpt Just want the components? Here you go: Demo Repo NPM A love letter to the Bluesky API I'm old enough to remember the golden Web 2.0 era, when many of today's big social media platforms grew up. A simpler time, when the Web was much more extroverted. It was common for websites to embed data from others (the peak of mashups), and prominently feature widgets from various platforms to showcase a post's likes or shares. Especially Twitter was so ubiquitous that the number of Twitter shares was my primary metric for how much people were interested in a blog post I wrote. Then, websites started progressively becoming walled gardens, guarding their data with more fervor than Gollum guarding the Precious. Features disappeared or got locked behind API keys, ridiculous rate limits, expensive paywalls, and other restrictions. Don't get me wrong, I get it. A lot of it was reactionary, a response to abuse -- the usual reason we can't have nice things. And even when it was to stimulate profit -- it is understandable that they want to monetize their platforms. People gotta eat. I was recently reading this interesting article by Salma Alam-Naylor. The article makes some great points, but it was something else that caught my eye: the widget of Bluesky likes at the bottom. Salma's Bluesky likes widget that inspired these I mentioned it to my trusty apprentice Dmitry who discovered the API was actually much simpler than what we've come to expect. Later, it turned out Salma has even written an entire post on how to implement the same thing on your own site. The openness of the API was so refreshing. Not only can you read public data without being authenticated, you don't even need an API key! Major nostalgia vibes. It seemed the perfect candidate for a web component that you can just drop in to a page, give it a post URL, and it will display the likes for that post. I just had to make it, and of course use it right here. Web Components that use API data have been historically awkward. Let ## postmarketOS in 2025-03: OP6 & MSM89x7 Camera, Generic SM7150, COSMIC, Musl Collation + I18n DevFeed: [postmarketOS in 2025-03: OP6 & MSM89x7 Camera, Generic SM7150, COSMIC, Musl Collation + I18n]() Original publisher: [Read original article]() Published: 2025-04-09T00:00:00Z Content type: news Language: en Sources: [postmarketOS]() Topics: [Linux](), [Mobile](), [Internationalization (i18n)](), [Continuous integration](), [gitlab-ci](), [Matrix](), [Self-hosted](), [ASUS](), [Pinebook-Pro](), [Pinephone](), [Pinephone-Pro]() Tags: [2025](), [asus](), [devices](), [gitlab](), [gitlab-ci](), [i18n](), [linux](), [matrix](), [mobile](), [pinebook-pro](), [pinephone](), [pinephone-pro](), [postmarketos](), [self-hosted]() ### AI overview A postmarketOS monthly update covering device support, an accepted grant for musl libc collation and internationalization, community contributions, a self-hosted Matrix/IRC bridge, reliable GitLab CI, and GNOME 48 changes for mobile. ### Source excerpt The calendar has turned another page, and it's finally time for our eagerly awaited monthly update! We're thrilled to share what our community has been building and improving since last month. Before we get to that, let's talk about the most recent Linux After Dark episode: It seems when the four hosts do a distro challenge, they do it properly. They didn't just try postmarketOS on one or two devices, but on all of these: ASUS Transformer Pad 3G, Linx 7 tablet (Generic X86_64), Motorola Moto G 2015, PinePhone Pro, PinePhone, Pinebook Pro and Acer R11/ASUS C200/Lenovo Duet 3 (Chromebooks). The resulting episode is not only very entertaining, but also gives many insights into first use experiences! Organizational We have applied for an NGI0 grant for Collation + i18n support in musl libc and it has been accepted! Collation allows set ordering based on locales, and follows a certain set of established rules and standards. Internationalization provides basic functionality in the language of choice for the user like dates, times, numbers, and monetary symbols. The implementation will be done by main author and maintainer of musl libc Rich and will benefit postmarketOS, Alpine Linux and all other users of musl libc. Thanks Rich, Pablo and NLNet! knuxify is our newest Trusted Contributor! They work a lot on the postmarketOS wiki, are mainlining the Broadcom Kona series chipsets, co-maintaining the Exynos 4 close to mainline kernel fork and more. Read their TC page for more information. Thanks knuxify! We wrote detailed blog posts on finances and priorities for 2025. Thanks Pablo and Oliver! Our Matrix/IRC bridge is now self-hosted. Thanks Luca, Ferass, Oliver! GitLab CI with our custom runner now works reliably (#101). Thanks Oliver! GNOME 48 GNOME 48 is now in Alpine edge and it brings massive performance improvements with dynamic triple buffering and more, new fonts, notification stacking and many other great changes! Shortly afterwards, GNOME Shell on Mobile has been re ## postmarketOS in 2025-03: OP6 & MSM89x7 Camera, Generic SM7150, COSMIC, Musl Collation + I18n DevFeed: [postmarketOS in 2025-03: OP6 & MSM89x7 Camera, Generic SM7150, COSMIC, Musl Collation + I18n]() Original publisher: [Read original article]() Published: 2025-04-09T00:00:00Z Content type: news Language: en Sources: [postmarketOS]() Topics: [Internationalization (i18n)](), [CI/CD]() Tags: [2025](), [camera](), [cosmic](), [i18n](), [musl](), [nura](), [postmarketos]() ### AI overview The March 2025 update reports initial camera support merged for the OnePlus 6 and several MSM89x7 phones, plus a new generic Qualcomm SM7150 package that replaces device-specific packages and boots through a second-stage bootloader and systemd-boot. COSMIC is available in Alpine and postmarketOS, with prebuilt edge images for generic x86_64 and ThinkPad X13s; GNOME 48 brings dynamic triple buffering and mobile shell window placement and input improvements. Other practical changes include Firefox per-site user-agent spoofing and user-overridable preferences, pmbootstrap support for setting the FDE passphrase through an environment variable, and initramfs support for multi-device btrfs. The project also secured funding for musl collation and internationalization support. The source is a broad monthly changelog, so these highlights do not cover every change. ### Source excerpt The calendar has turned another page, and it's finally time for our eagerly awaited monthly update! We're thrilled to share what our community has been building and improving since last month. Before we get to that, let's talk about the most recent Linux After Dark episode: It seems when the four hosts do a distro challenge, they do it properly. They didn't just try postmarketOS on one or two devices, but on all of these: ASUS Transformer Pad 3G, Linx 7 tablet (Generic X86_64), Motorola Moto G 2015, PinePhone Pro, PinePhone, Pinebook Pro and Acer R11/ASUS C200/Lenovo Duet 3 (Chromebooks). The resulting episode is not only very entertaining, but also gives many insights into first use experiences! Organizational We have applied for an NGI0 grant for Collation + i18n support in musl libc and it has been accepted! Collation allows set ordering based on locales, and follows a certain set of established rules and standards. Internationalization provides basic functionality in the language of choice for the user like dates, times, numbers, and monetary symbols. The implementation will be done by main author and maintainer of musl libc Rich and will benefit postmarketOS, Alpine Linux and all other users of musl libc. Thanks Rich, Pablo and NLNet! knuxify is our newest Trusted Contributor! They work a lot on the postmarketOS wiki, are mainlining the Broadcom Kona series chipsets, co-maintaining the Exynos 4 close to mainline kernel fork and more. Read their TC page for more information. Thanks knuxify! We wrote detailed blog posts on finances and priorities for 2025. Thanks Pablo and Oliver! Our Matrix/IRC bridge is now self-hosted. Thanks Luca, Ferass, Oliver! GitLab CI with our custom runner now works reliably (#101). Thanks Oliver! GNOME 48 GNOME 48 is now in Alpine edge and it brings massive performance improvements with dynamic triple buffering and more, new fonts, notification stacking and many other great changes! Shortly afterwards, GNOME Shell on Mobile has been re ## How to Let Google Know of Other Languages in Your Django Site DevFeed: [How to Let Google Know of Other Languages in Your Django Site]() Original publisher: [Read original article]() Author: Haki Benita Published: 2019-05-06T21:00:00Z Content type: tutorial Language: en Sources: [Haki Benita]() Topics: [Django](), [Internationalization (i18n)](), [Code](), [Google]() Tags: [articles](), [code](), [django](), [google](), [how-to](), [i18n](), [language](), [seo](), [translation]() ### AI overview A tutorial on configuring a multilingual Django site and adding hreflang links so Google and other search engines can identify localized versions of pages. It covers Django internationalization setup, localized URLs, absolute URLs, query parameters and hashes, and limitations when translating non-localized URLs. ### Source excerpt If you have a public facing Django site in multiple languages, you probably want to let Google and other search engines know about it. [Next page]()