# Localization (l10n) Localization (l10n) is the adaptation of a product, application, or document content to meet the language, cultural, and other requirements of a specific target market. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## i18nize-templates: Internationalization After the Fact DevFeed: [i18nize-templates: Internationalization After the Fact]() Original publisher: [Read original article]() Author: Khan Academy Published: 2015-09-28T22:00:00Z Content type: release Language: en Sources: [Khan Academy]() Topics: [Internationalization (i18n)](), [Localization (l10n)](), [Open Source](), [Python](), [Handlebars](), [HTML](), [Library](), [Code](), [JavaScript](), [Babel]() Tags: [babel](), [code](), [engineering](), [html](), [infrastructure](), [javascript](), [language](), [languages](), [library](), [news](), [open-source](), [programming](), [python]() ### AI overview Khan Academy describes retrofitting its English-only codebase for internationalization and localization across several HTML-rendering technologies. It introduces i18nize-templates, an open-source Python module that finds natural-language text in HTML and templates and marks it as i18n-aware. The tool supports raw HTML, jinja2, and Handlebars templates and reportedly reduces template annotation time by over 90%. ### Source excerpt By Craig Silverstein Khan Academy started as a collection of videos, but now has over 100,000 pieces of ... Read more ## How AI-Generated Work Can Shift Complexity to Reviewers DevFeed: [How AI-Generated Work Can Shift Complexity to Reviewers]() Original publisher: [Read original article]() Author: Robin Wieruch Published: 2026-09-01T06:50:46Z Content type: opinion Language: en Sources: [Robin Wieruch]() Topics: [Artificial Intelligence](), [Pull Request](), [Localization (l10n)]() Tags: [agent](), [agentic-coding-team](), [ai](), [ai-code-review-burden](), [ai-engineer](), [ai-slop-pull-requests](), [env-file-security](), [review](), [workslop]() ### AI overview This commentary argues that AI-generated output can create additional work when it appears polished but leaves important decisions unresolved. Using pull requests as examples, it discusses number localization and how architectural choices can surface late in review. ### Source excerpt AI made producing work nearly free, so the job is absorbing complexity before handing work to someone else, with examples from tickets, PRs, and slide decks. ## CodeSOD: The Big Family DevFeed: [CodeSOD: The Big Family]() Original publisher: [Read original article]() Author: Remy Porter Published: 2026-08-27T06:30:00Z Content type: opinion Language: en Sources: [The Daily WTF]() Topics: [PHP](), [Programming](), [Code](), [data](), [SQL](), [Localization (l10n)](), [formatting](), [HTML](), [Parsing]() Tags: [array](), [code](), [codesod](), [fetch](), [formatting](), [html](), [humor](), [php](), [programming](), [sql]() ### AI overview This commentary examines a large, generalized PHP code sample that builds hierarchical output from a presumed database source. It highlights probable SQL injection risk, unused array keys, dynamic localization fields, extensive number formatting and HTML string manipulation, string-based date-time parsing, and repeated code for child and sibling records. ### Source excerpt Some time ago, Charles shared with us some awful PHP, aka the most common sort. Today's code sample is maybe a little too big to sum up, but I'll let Charles take a crack at it. It's so bad that even analyzing and laughing at it feels impossible. But it's so bad, I couldn't not share it. I'm the only one handling all the IT-related tasks at my company, and I don't have anyone here to vent or laugh about this kind of thing with. So, I figured, why not share it here? I'm hoping it'll provide at least a little bit of catharsis or some dark humor. To make sure the confidentiality of the codebase was respected, I took the liberty of generalizing it. You might notice some inconsistencies, but that's just me trying to keep things neutral while protecting the original structure and functionality. Apologies if it looks a bit patchy - the goal was to avoid revealing any specific details or sensitive code. The whole block is north of 400 lines, and it's doing a lot. Or well, maybe it's not, as you'll see. Let's star with the outermost layer. $resm_data = $data_source->fetchData("group=" . $item_id); foreach ($resm_data as $key => $value) { // rest of the code here } We fetch data from a data source, presumably a database, passing our condition as a string, which reeks of probable SQL injection, but I don't know what library they're using. I also note they're using the key/value style of array iteration, but never actually check the key. $option_id = $value->option_id; $resm_details = $detail_source->fetch($option_id); if ($resm_details) { $label = $resm_details->{"label$lang"}; $description = $resm_details->{"description$lang"}; $category = $resm_details->category; Nice little bit of "meta" programming to get their localization working, it'll fetch labelen or labelde as needed. Definitely not a horrible, dangerous way to solve that problem. We use that again to get our currency figured out. That lets us do number formatting. So much number formatting code. if ($category == 0) ## Mistral x HUMAIN DevFeed: [Mistral x HUMAIN]() Original publisher: [Read original article]() Published: 2026-08-24T16:02:41Z Content type: article Language: en Sources: [Mistral AI Blog]() Topics: [AI Strategy](), [AI Infrastructure](), [AI Models](), [Model Development](), [model-deployment](), [Localization (l10n)](), [datacenter](), [Cybersecurity]() Tags: [ai](), [ai-infrastructure](), [ai-platform](), [arabic](), [data](), [data-center](), [deployment](), [enterprise](), [europe](), [financial-services](), [manufacturing](), [model-development](), [public-sector](), [security]() ### AI overview Mistral and HUMAIN announce a strategic collaboration to advance sovereign AI in Saudi Arabia and across the Middle East. The initiative covers AI infrastructure, advanced model development, localized Arabic-capable models, and deployment of AI solutions for regulated industries. ### Source excerpt The most powerful AI platform for enterprises. Customize, fine-tune, and deploy AI assistants, autonomous agents, and multimodal AI with open models. ## Localization strategy: Best practices for global websites DevFeed: [Localization strategy: Best practices for global websites]() Original publisher: [Read original article]() Author: Webflow Team Published: 2026-08-15T00:00:00Z Content type: article Language: en Sources: [Webflow Blog]() Topics: [Localization (l10n)](), [Internationalization (i18n)](), [systems]() Tags: [best-practices](), [global](), [global-expansion](), [how-to](), [strategy]() ### AI overview A practical guide to localization strategy for global websites, covering internationalization, localization, translation, cultural adaptation, audience research, and workflows for entering new markets. ### Source excerpt Learn localization strategy fundamentals, why they're important, and how to optimize your approach to make a memorable first impression in every new market. ## Pay by Bank: How A2A Payments Work for SaaS DevFeed: [Pay by Bank: How A2A Payments Work for SaaS]() Original publisher: [Read original article]() Author: Deepak Jangir Published: 2026-08-06T00:00:00Z Content type: article Language: en Sources: [Dodo Payments Blog]() Topics: [Software as a service](), [Authentication](), [real-time](), [Localization (l10n)]() Tags: [authentication](), [comparison](), [conversion](), [global](), [payments](), [real-time](), [saas]() ### AI overview This guide explains how pay-by-bank, or account-to-account payments, move money directly from a customer's bank account to a SaaS merchant. It covers the payment flow, authentication, near-real-time settlement, cost and dispute trade-offs versus cards, and the regional nature of domestic payment schemes. ### Source excerpt How pay by bank and account-to-account payments work, what they cost compared with cards, and where they fit in a global SaaS checkout. ## Human-Centered Automation for Kubernetes Localization in the AI Era DevFeed: [Human-Centered Automation for Kubernetes Localization in the AI Era]() Original publisher: [Read original article]() Author: The Kubernetes Authors Published: 2026-06-26T22:00:00Z Content type: article Language: en Sources: [Kubernetes Contributors Blog]() Topics: [Localization (l10n)](), [Kubernetes](), [Documentation](), [Maintainers]() Tags: [automation](), [documentation](), [kubernetes](), [maintainers](), [translation]() ### AI overview This article describes a Kubernetes localization mentorship project focused on human-centered automation. Its goal is to help maintainers prioritize review work by improving visibility and reducing repetitive triage, rather than automating translation. The approach addresses ongoing maintenance of localized documentation as English source content changes. ### Source excerpt This year, the Kubernetes localization subproject participated in LFX Mentorship for the first time through the project "CNCF - Kubernetes: SIG Docs Localization: AI-era localization automation" . The work was also tracked in kubernetes/website#54075 . As the mentee on this project, I worked with Kubernetes SIG Docs localization mentors on a practical maintenance question: In an era of rapidly improving AI translation tools, what kind of automation actually helps localization maintainers? Kubernetes documentation is used by readers around the world. Localization helps make the project more accessible to users and contributors by providing content in their native languages. But localization is not only about translating pages once. It is also about maintaining those pages as Kubernetes changes. For this mentorship project, the focus was human-centered automation: tools that improve visibility, reduce repetitive triage, and protect human reviewer attention. The goal was not to automate translation. The goal was to make localization review work easier to prioritize. The maintenance problem behind localization Kubernetes documentation changes continuously. Concepts are clarified, examples are updated, feature states move forward, commands are corrected, and API-related wording changes. When English documentation changes, localized pages may also need updates. For active localization teams, this creates ongoing maintenance work. Reviewers need to understand both the source content and the target language, and they need enough Kubernetes context to decide whether a change affects technical accuracy. Existing signals can help detect possible drift. Some localization teams compare Git history to see whether the English source changed after a localized page was last updated, and Kubernetes website pages may also show lastmod warnings when localized content appears older than the English source. These signals are useful, but they do not always explain what kind of review is n ## Stripe Usage-Based Billing vs Dodo Payments: Honest 2026 Comparison DevFeed: [Stripe Usage-Based Billing vs Dodo Payments: Honest 2026 Comparison]() Original publisher: [Read original article]() Author: Aarthi Poonia Published: 2026-06-04T00:00:00Z Content type: comparison Language: en Sources: [Dodo Payments Blog]() Topics: [stripe](), [Software as a service](), [API](), [Localization (l10n)](), [real-time]() Tags: [2026](), [api](), [comparison](), [comparisons](), [legal](), [merchant-of-record](), [pricing](), [real-time](), [saas](), [usage-based-billing]() ### AI overview This comparison examines Stripe Billing and Dodo Payments for usage-based SaaS and AI products. It contrasts their metering and usage tracking, billing architectures, tax compliance, chargeback handling, payment localization, and developer experience. Stripe Billing is presented as a subscription and billing engine built on Stripe's payment processor, while Dodo Payments is described as a Merchant of Record platform that also provides billing, tax compliance, and chargeback transfer. ### Source excerpt Stripe usage-based billing vs Dodo Payments compared - metering, pricing models, tax handling, chargeback risk, and which one fits your usage-based SaaS or AI business. ## New ways to turn global demand into revenue DevFeed: [New ways to turn global demand into revenue]() Original publisher: [Read original article]() Author: Abhi Tiwari Published: 2026-06-04T00:00:00Z Content type: article Language: en Sources: [Stripe Blog]() Topics: [stripe](), [Localization (l10n)](), [Optimization](), [Artificial Intelligence](), [data](), [Authorization]() Tags: [ai](), [billing](), [checkout](), [compliance](), [conversion](), [cross-border](), [data](), [global](), [optimization](), [payment](), [pricing](), [products](), [revenue](), [stripe](), [tools]() ### AI overview Stripe describes products and capabilities for converting global demand into revenue through localized checkout, local payment methods, local-currency pricing, and cross-border optimization. The article highlights Checkout studio and Adaptive Pricing, including reported effects on conversion, authorization rates, and cross-border revenue. ### Source excerpt At Sessions 2026, Stripe unveiled dozens of products and capabilities to help businesses turn global demand into revenue. See how to go global faster with localized checkout and Adaptive Pricing, smarter fraud tools, multicurrency treasury support, and automated tax compliance. ## Accept Payments in Africa: A Complete Guide for SaaS Companies DevFeed: [Accept Payments in Africa: A Complete Guide for SaaS Companies]() Original publisher: [Read original article]() Author: Ayush Agarwal Published: 2026-04-05T00:00:00Z Content type: tutorial Language: en Sources: [Dodo Payments Blog]() Topics: [Software as a service](), [Localization (l10n)](), [Transactions]() Tags: [africa](), [bank-transfers](), [card](), [compliance](), [digital-wallet](), [global-expansion](), [guide](), [merchant-of-record](), [mobile](), [payments](), [saas](), [transactions]() ### AI overview This guide explains how SaaS and digital product businesses can accept payments across Africa. It emphasizes mobile money, local bank rails, transfers, USSD, and localized payment methods over card-only checkout, and discusses currencies, compliance, and Merchant of Record services. ### Source excerpt How to accept payments across Africa with the right payment methods, currencies, and compliance setup for SaaS and digital product businesses. ## How to Handle Multi-Currency Pricing for Global SaaS DevFeed: [How to Handle Multi-Currency Pricing for Global SaaS]() Original publisher: [Read original article]() Author: Ayush Agarwal Published: 2026-03-31T00:00:00Z Content type: tutorial Language: en Sources: [Dodo Payments Blog]() Topics: [Software as a service](), [Localization (l10n)](), [Shared Responsibility Model]() Tags: [billing](), [conversion](), [global](), [guide](), [how-to](), [payments](), [pricing](), [saas]() ### AI overview A guide for SaaS founders on multi-currency pricing, purchasing power parity pricing, currency localization, and automatic forex management for selling globally. ### Source excerpt A comprehensive guide for SaaS founders on implementing multi-currency pricing, purchasing power parity (PPP), and automatic forex management to drive global growth. ## Xcode 26 Migration, UIScene Rollout, Initializr Localization Bundles, and More DevFeed: [Xcode 26 Migration, UIScene Rollout, Initializr Localization Bundles, and More]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-03-07T00:00:00Z Content type: article Language: en Sources: [CodeName One]() Topics: [Xcode](), [iOS](), [Localization (l10n)](), [Internationalization (i18n)](), [migration](), [Android](), [Documentation]() Tags: [adaptive](), [android](), [developer-guide](), [ios](), [migration](), [tooling](), [updates](), [xcode]() ### AI overview A Codename One update reports a staged Xcode 26 migration, initial UIScene support for testing, and Initializr-generated localization resource bundles. It also covers localization workflow improvements, Android adaptive icons, iOS notification replacement fixes, and UI and resource tooling updates. ### Source excerpt We started the Xcode 26 migration rollout, Initializr now generates localization resource bundles, and there are several useful platform updates you should know about. ## Scaling Localization with AI at Lyft DevFeed: [Scaling Localization with AI at Lyft]() Original publisher: [Read original article]() Author: Stefan Zier Published: 2026-02-19T17:28:41Z Content type: article Language: en Sources: [Lyft Engineering - Medium]() Topics: [Localization (l10n)](), [Artificial Intelligence](), [Large Language Model](), [Latency](), [Prompt Engineering](), [Web]() Tags: [ai](), [architecture](), [artificial-intelligence](), [aws](), [code](), [compliance](), [distributed-systems](), [infrastructure](), [latency](), [llm](), [lyft](), [machine-learning](), [real-time](), [web]() ### AI overview Lyft re-architected its translation pipeline to combine AI with linguist oversight, context injection, evaluation, guardrails, and version-controlled prompts. The batch system reduces translation latency from days to minutes while supporting legal compliance and brand integrity across expanding markets. ### Source excerpt Written by Stefan Zier For years, Lyft's localization infrastructure relied exclusively on human translation. While this model usually ensured excellent quality, it was bound by multi-day turnarounds and costs that scaled linearly with every new language. For the few languages Lyft initially supported (Spanish, Portuguese, and French), these limits were acceptable. However, Lyft's expansion goals quickly outpaced what traditional workflows could support. Lyft's recent Québec launch required compliance with Bill 96 (legislation mandating French-first user experiences) which demanded faster turnaround than multi-day cycles allowed. Simultaneously, the Lyft Urban Solutions ("LUS": Bikes & Scooters) division sought to expand into European markets, requiring six new languages. The business need had changed as we now needed to move faster without sacrificing quality. This post explores how we re-architected Lyft's Translation Pipeline to leverage AI alongside linguist oversight and ultimately unlock new market launches. We will walk through context injection, decoupling content generation from evaluation, implementing guardrails, and treating prompts as version-controlled production code. The new pipeline reduces translation latency from days to minutes while maintaining the fidelity required for legal compliance and brand integrity. Note: We will walk through our batch translation pipeline -- used for 99% of app and web content -- which targets a 30-minute SLA for 95% of translations. We also support real-time translation (e.g., ride chat) which uses a different architecture.* How Translations Reach Hundreds of Services Before diving into the LLM pipeline, it helps to understand how translations flow through Lyft's infrastructure. This 2020 post explains the internationalization architecture initially built to move beyond one language/currency/country. Since then, the platform has grown to serve 11 locales across 150+ services. At its core, the pipeline does two things in ## Making AI work for everyone, everywhere: our approach to localization DevFeed: [Making AI work for everyone, everywhere: our approach to localization]() Original publisher: [Read original article]() Published: 2026-02-06T10:00:00Z Content type: article Language: en Sources: [OpenAI News]() Topics: [Localization (l10n)](), [Artificial Intelligence](), [OpenAI](), [Frontier AI](), [ChatGPT](), [AI Strategy]() Tags: [ai](), [ai-models](), [chatgpt](), [frontier-ai](), [global](), [global-affairs](), [openai](), [platform](), [safety]() ### AI overview OpenAI explains how globally shared frontier AI models can be adapted to local languages, accents, laws, curricula, cultural norms, and values. The article describes localized AI pilots, including ChatGPT for students in Estonia, while emphasizing transparency, consistent behavioral boundaries, and human safety and rights. ### Source excerpt OpenAI shares its approach to AI localization, showing how globally shared frontier models can be adapted to local languages, laws, and cultures without compromising safety. ## H Company's new Holo2 model takes the lead in UI Localization DevFeed: [H Company's new Holo2 model takes the lead in UI Localization]() Original publisher: [Read original article]() Author: Ramzi De Coster; Hamza Benchekroun; Aurélien Lac; Tony Wu; Pierre-Louis Cedoz; Kai Yuan; Mart Bakler; Antoine Bonnet; Aleix Cambray; Ronan Riochet Published: 2026-02-03T17:40:14Z Content type: article Language: en Sources: [Hugging Face - Blog]() Topics: [Localization (l10n)](), [Model Development](), [Benchmark](), [skypilot](), [Kubernetes]() Tags: [agentic](), [benchmark](), [company](), [development](), [hugging-face](), [infrastructure](), [jobs](), [kubernetes](), [model](), [model-development](), [models](), [performance](), [release](), [research](), [scale](), [skypilot](), [training](), [ui]() ### AI overview H Company introduces Holo2-235B-A22B Preview, a research model for localizing UI elements in high-resolution interfaces. Its agentic mode iteratively improves predictions and achieves state-of-the-art results on ScreenSpot-Pro, while SkyPilot supports large-scale training across cloud providers and Kubernetes clusters. ### Source excerpt Two months since releasing our first batch of Holo2 models, H Company is back with our largest UI localization model yet: Holo2-235B-A22B Preview. This model achieves a new State-of-the-Art (SOTA) record of 78.5% on Screenspot-Pro and 79.0% on OSWorld G. Available on Hugging Face, Holo2-235B-A22B Preview is a research release focused on UI element localization. Agentic Localization High-resolution 4K interfaces are challenging for localization models. ## Figma achieves C5 accreditation, strengthening cloud security for customers across the DACH region DevFeed: [Figma achieves C5 accreditation, strengthening cloud security for customers across the DACH region]() Original publisher: [Read original article]() Author: Figma Published: 2026-02-03T14:00:00Z Content type: release Language: en Sources: [Figma Blog]() Topics: [Figma](), [Security & compliance, Cloud security](), [Security](), [Localization (l10n)]() Tags: [cloud-security](), [compliance](), [figma](), [finance](), [germany](), [government](), [government-public-sector](), [switzerland](), [visibility]() ### AI overview Figma announced that it achieved C5 accreditation, a German cloud-computing security and compliance standard. The accreditation applies to Figma's services for customers in Germany, Austria, and Switzerland and provides independent assessment of security, availability, confidentiality, risk management, and operational transparency. ### Source excerpt Figma is giving customers greater confidence in cloud security and compliance. ## Figma expands support for India with local data hosting and new governance tools DevFeed: [Figma expands support for India with local data hosting and new governance tools]() Original publisher: [Read original article]() Author: Figma Published: 2025-12-05T00:00:00Z Content type: news Language: en Sources: [Figma Blog]() Topics: [Figma](), [Localization (l10n)](), [data](), [hosting](), [Security]() Tags: [2026](), [data-protection](), [enterprise](), [figma](), [governance](), [hosting](), [india](), [privacy](), [security]() ### AI overview Figma is expanding support for India with local hosting of Figma file data and new enterprise governance features. Local hosting is planned for Q1 2026, while Governance+ will provide enhanced access controls and help customers strengthen security and compliance. ### Source excerpt Figma introduces new governance features for enterprise customers, with local data residency expected next quarter. ## From Zero to Hero: Localization-Led Generative AI at Udemy DevFeed: [From Zero to Hero: Localization-Led Generative AI at Udemy]() Original publisher: [Read original article]() Author: Nishanth Gandhidoss Published: 2025-09-22T17:47:18Z Content type: article Language: en Sources: [Udemy Engineering]() Topics: [Localization (l10n)](), [Generative AI](), [Large Language Model](), [datasets]() Tags: [ai](), [features](), [generative-ai](), [generative-ai-tools](), [implementation](), [llm](), [llm-applications](), [machine-learning](), [machine-translation](), [retrieval-augmented-gen](), [techniques](), [translation]() ### AI overview Udemy describes how it localized generative AI features, including Skills Mapping and its in-course AI Assistant, to serve learners in multiple languages. The article compares translation management systems, multilingual LLMs, and hybrid strategies, emphasizing trade-offs among implementation speed, language coverage, fluency, cultural nuance, and domain precision. ### Source excerpt By Nishanth Gandhidoss, Senior Staff Data Scientist @ Udemy Why Multilingual Generative AI Matters Generative AI is rapidly changing how people learn and work, but those gains are only realized when the technology speaks the user's language. Over the past year at Udemy, we prioritized breaking the English-only barrier so our Gen AI features, most critically Skills Mapping and the in-course AI Assistant, could deliver value for learners across the globe. Our approach balanced speed, coverage, and quality, allowing us to move quickly without sacrificing fidelity in markets where nuance matters. Below we describe the localization strategy we adopted, why we made those trade-offs, and the operational practices that made the rollout repeatable, scalable, and quick. Localization Strategies When deciding how to localize a Gen AI product, it is helpful to think of options on a spectrum from low to high complexity. The simplest approach provides broad language coverage fast, while the most involved approach optimizes for fluency, cultural nuance, and domain precision. At Udemy, we researched and organized our work around three primary strategies: a translation management system (TMS) for rapid implementation with broader coverage, a multilingual LLM system (MLS) for high-fidelity experiences, and a hybrid approach to balance reach and quality. As each strategy is introduced below, we briefly explain the industry-standard localization techniques they draw on, with examples, so the differences are clear. Translation Management System (TMS) At the simplest end of the spectrum, we have the TMS approach. With a TMS, the user interacts in their own language, but the AI model itself operates in English input/output. The system first detects the user's input language, say, in Spanish, and sends the input through a machine translation (MT) service that converts it into English. The LLM then generates an English response, and that response is translated back into the user's input lang ## Swift Default Value in String Interpolations DevFeed: [Swift Default Value in String Interpolations]() Original publisher: [Read original article]() Author: Keith Harrison Published: 2025-09-07T08:51:46Z Content type: tutorial Language: en Sources: [K. Harrison]() Topics: [Swift](), [SwiftUI](), [Localization (l10n)]() Tags: [auto-layout](), [ios](), [learn](), [objective-c](), [swift](), [swift-6-2](), [wwdc](), [xcode]() ### AI overview Swift 6.2 adds a default value parameter for string interpolation, allowing optional values of any type to use a specified fallback string. The article also notes that this parameter does not currently work with LocalizedStringKey. ### Source excerpt Swift 6.2 makes it easier to interpolate strings with optional values. What's The Problem? In this SwiftUI view I need to create a text string from an optional integer value: struct CounterView: View { let count: Int? var body: some View { Text("The count is \(count)") } } The compiler warns about the optional value: String interpolation produces a debug description for an optional value; did you mean to make this explicit? The compiler suggests either providing a default value or to use String(describing:) to silence the warning. Using the nil-coalescing operator to provide a default value removes the warning but is not ideal. The default value has to match the type of the optional value. That can work when dealing with an optional string. In this example I have an optional Int and there may not be a sensible default value for the nil case. For example, I could use zero: // The count is 0 Text("The count is \(count ?? 0)") The alternative of using the String(describing:) approach is both clumsy and ends up showing the nil value: // The count is nil Text("The count is \(String(describing: count))") What I want is a way to provide a default string regardless of the type of the optional value. Default Value Parameter In Swift 6.2, String interpolation has a new default value parameter that accepts a string regardless of the type of the optional value: // The count is not set Text("The count is \(count, default: "not set")") That's an improvement over outputting nil. Localization One issue is that I've been unable to get this to work with localization. The problem seems to be that LocalizedStringKey doesn't support the default value parameter. So this doesn't work: // Not Supported let key = LocalizedStringKey("The count is: \(count, default: "not set")") Learn More SE-0477 Default Value in String Interpolations Swift Default Value in String Interpolations was originally posted 07 Sep 2025 on useyourloaf.com. Want this direct to your inbox? Sign up and get my free WWDC ## Figma moves closer to its community with Latin American Spanish localization DevFeed: [Figma moves closer to its community with Latin American Spanish localization]() Original publisher: [Read original article]() Author: Figma Published: 2025-07-02T00:00:00Z Content type: article Language: en Sources: [Figma Blog]() Topics: [Figma](), [Localization (l10n)](), [coding-community]() Tags: [collaboration](), [community](), [design](), [development](), [digital-experiences](), [figma](), [product](), [support]() ### AI overview Figma has launched Latin American Spanish localization for its product and support experiences, expanding its presence across Latin America. The article highlights regional customer adoption, collaboration among design, product, and engineering teams, and Figma's broader localization efforts. ### Source excerpt Latin American Spanish becomes Figma's latest language for product and support localization. ## Figma launches Brazilian Portuguese localization, expanding global reach DevFeed: [Figma launches Brazilian Portuguese localization, expanding global reach]() Original publisher: [Read original article]() Author: Figma Published: 2025-05-07T00:00:00Z Content type: article Language: en Sources: [Figma Blog]() Topics: [Figma](), [Localization (l10n)](), [User Interfaces]() Tags: [brazil](), [community](), [customers](), [design](), [figma](), [global](), [product-development](), [prototyping](), [workflows]() ### AI overview Figma launches full Brazilian Portuguese localization, including translated and culturally adapted user interfaces and dedicated Portuguese-language support. The article presents the launch as part of Figma's effort to expand global reach and make design more accessible, highlighting its growing customer and community base in Brazil. ### Source excerpt Brazilian Portuguese becomes the fourth language for localization, with Latin American Spanish expected later this year. ## Figma localizes product and support for Korean market DevFeed: [Figma localizes product and support for Korean market]() Original publisher: [Read original article]() Author: Figma Published: 2025-04-15T00:00:00Z Content type: article Language: en Sources: [Figma Blog]() Topics: [Figma](), [Localization (l10n)](), [User Interfaces](), [Internet]() Tags: [community](), [company](), [customers](), [design](), [developers](), [development](), [digital-products](), [figma](), [global](), [internet](), [platform](), [product](), [productivity](), [products](), [support](), [technology](), [user-interfaces](), [work]() ### AI overview Figma has launched an open beta for Korean localization, translating its product and adapting its user interfaces and support for Korean users. The article describes this as Figma's third product localization and highlights adoption, community activity, and customer feedback in South Korea. ### Source excerpt Figma launches Korean localization open beta, with more languages expected to follow this year. ## Figma localizes product and support for Spanish market DevFeed: [Figma localizes product and support for Spanish market]() Original publisher: [Read original article]() Author: Figma Published: 2025-03-27T00:00:00Z Content type: article Language: en Sources: [Figma Blog]() Topics: [Figma](), [Localization (l10n)](), [User Interfaces]() Tags: [collaboration](), [core](), [developers](), [figma](), [global](), [product](), [product-design](), [revenue]() ### AI overview Figma has localized its product and support experience for the Spanish market, adding Spanish as its second localized language after Japanese. ### Source excerpt Figma adds Spanish as its second localized language, after Japanese, with more languages expected later this year. ## macOS Keyboard Shortcut Localization DevFeed: [macOS Keyboard Shortcut Localization]() Original publisher: [Read original article]() Author: Conrad Irwin Published: 2024-11-08T00:00:00Z Content type: article Language: en Sources: [Zed Industries - Blog]() Topics: [Localization (l10n)](), [macOS](), [ASCII](), [Vim]() Tags: [ascii](), [japanese](), [keyboard](), [layout](), [macos](), [shortcuts](), [vim]() ### AI overview Zed 0.162 changes keyboard shortcut handling so shortcuts work across Cyrillic, Japanese IME-based, and non-US Latin keyboard layouts. The update changes modifier requirements, coordinates shortcut processing with IMEs, and uses macOS Latin-based layouts for non-Latin keyboards. ### Source excerpt How macOS shortcuts work on different layouts. [Next page]()