# translation Published articles for translation. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Automating Highly Similar Translations DevFeed: [Automating Highly Similar Translations]() Original publisher: [Read original article]() Author: Khan Academy Published: 2016-02-15T23:00:00Z Content type: article Language: en Sources: [Khan Academy]() Topics: [ui](), [Template](), [Tool]() Tags: [engineering](), [languages](), [news](), [templates](), [tool](), [translation](), [ui](), [web-frontend]() ### AI overview Khan Academy describes a redesigned translator dashboard and a translation tool with smart translations. The system groups highly similar English strings, reuses existing translations through templates, and updates the UI to show which strings can be translated automatically. ### Source excerpt By Kevin Barabash Khan Academy is available in 12 languages and is in the process of being translated ... Read more ## Emulating Terraform on Pulumi's Engine DevFeed: [Emulating Terraform on Pulumi's Engine]() Original publisher: [Read original article]() Author: Ian Wahbe Published: 2026-08-04T00:00:00Z Content type: article Language: en Sources: [Pulumi]() Topics: [Terraform](), [opentofu](), [terraform provider](), [configuration]() Tags: [engineering](), [hcl](), [modules](), [opentofu](), [protocol](), [providers](), [pulumi](), [terraform](), [terraform-provider](), [translation]() ### AI overview This article explains how Pulumi's HCL interpreter maps Terraform configuration, resources, providers, and modules onto the Pulumi engine. It reports that the implementation works with 96% of Pulumi's top Terraform modules and describes how Pulumi's terraform-provider relays between Pulumi and Terraform provider protocols. ### Source excerpt The core promise of Pulumi's HCL support is that you can bring your existing Terraform configuration and modules, and pulumi will run them. If it works in OpenTofu and doesn't work in Pulumi, we would like to fix that. Given that goal, our HCL interpreter needs to take HCL as input and emit instructions to the Pulumi engine that semantically match how tofu would interpret the same input. This is made harder by the fact that Pulumi and OpenTofu have fundamentally different engine semantics and provider ecosystems. This blog post will explore how we have implemented that mapping well enough to get 96%1 of our top Terraform modules working on Pulumi. We'll briefly walk through how Pulumi's HCL interpreter handles Terraform's resource semantics, providers, and modules. It will also call out where Pulumi's HCL support lets you do things that Terraform and OpenTofu will not allow. Providers Both Pulumi and Terraform have providers, but they don't have the same providers. While there are providers that Terraform does not have, Pulumi can always resolve a Terraform provider using Pulumi's confusingly named terraform-provider provider.2 This is the same provider that lets you consume Any Terraform Provider in another Pulumi program with pulumi package add terraform-provider .... The terraform-provider provider acts as a relay: it speaks Pulumi's protocol to the Pulumi engine, and speaks Terraform's provider protocol to the Terraform provider it stands up. Because Pulumi HCL needs to work with all Pulumi providers and because terraform-provider lets Pulumi HCL speak to Terraform providers via the Pulumi protocol, Pulumi HCL actually only speaks Pulumi protocols directly: flowchart LR subgraph n2Entry[" "] n2["terraform-provider"] end subgraph providerBox["Pulumi Provider"] direction TD n2Entry n3["Terraform Provider"] end n0["Pulumi HCL"] <--> n1["Pulumi Engine"] n1 <--> n2Entry n2 <--> n3 n2@{ shape: rect} n3@{ shape: rect} n0@{ shape: rect} n1@{ shape: rect} style n2Entry f ## Why I needed Durable Execution to read a toy manual DevFeed: [Why I needed Durable Execution to read a toy manual]() Original publisher: [Read original article]() Author: Shy Ruparel Published: 2026-07-13T00:00:00Z Content type: opinion Language: en Sources: [Temporal Blog]() Topics: [Artificial Intelligence](), [Software](), [Python]() Tags: [ai](), [cleanup](), [japanese](), [ocr](), [pipeline](), [retries](), [temporal-voices](), [translation]() ### AI overview Shy Ruparel describes building Toku Solutions, an AI pipeline that translates Japanese collectible toy manuals into editable static sites. Durable Execution handles OCR, retries, and cleanup so processing does not have to restart from the beginning. ### Source excerpt Shy Ruparel built an AI pipeline to translate Japanese toy manuals. Durable Execution keeps OCR, retries, and cleanup from starting over. ## 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 ## Operation "Date Bait": AI-enabled scam targeting loveseekers DevFeed: [Operation "Date Bait": AI-enabled scam targeting loveseekers]() Original publisher: [Read original article]() Published: 2026-02-01T00:00:00Z Content type: news Language: en Sources: [OpenAI News]() Topics: [Artificial Intelligence](), [OpenAI](), [ChatGPT](), [Automation](), [API]() Tags: [ads](), [ai](), [api](), [automation](), [chatgpt](), [engagement](), [openai](), [safety](), [scam](), [social-media](), [structured](), [tasks](), [telegram](), [translation](), [trust]() ### AI overview OpenAI describes Operation "Date Bait," in which accounts likely originating in Cambodia used ChatGPT and API access for a semi-automated romance and task scam targeting Indonesian men. The operation used translated and emotionally manipulative outreach across advertisements, an AI chatbot, Telegram, and dating platforms. ### Source excerpt OpenAI banned accounts that very likely originated in Cambodia and used AI for scam outreach to Indonesian loveseekers, including translation and engagement. ## Romance scams: AI-enabled romance scam workflows DevFeed: [Romance scams: AI-enabled romance scam workflows]() Original publisher: [Read original article]() Published: 2026-02-01T00:00:00Z Content type: article Language: en Sources: [OpenAI News]() Topics: [Artificial Intelligence](), [OpenAI]() Tags: [ai](), [case-study](), [chatgpt](), [emotion](), [engagement](), [fraud](), [investment](), [manipulate](), [money](), [openai](), [report](), [safety](), [scam](), [translation]() ### AI overview OpenAI describes romance-scam workflows in which accounts used AI for outreach, translation, victim engagement, emotional manipulation, and investment-fraud lures. The company says it banned those accounts and disrupted related scam operations. ### Source excerpt OpenAI banned accounts using AI to support romance scam workflows, including outreach, translation, victim engagement, and investment-fraud lures. ## Glitch Effect in Jetpack Compose DevFeed: [Glitch Effect in Jetpack Compose]() Original publisher: [Read original article]() Author: sinasamaki Published: 2025-10-11T08:00:46Z Content type: tutorial Language: en Sources: [sinasamaki]() Topics: [Jetpack Compose](), [Compose](), [Graphics](), [GUI]() Tags: [animation](), [article](), [canvas](), [compose](), [graphics](), [jetpack-compose](), [mutation](), [random](), [scale](), [slices](), [translation]() ### AI overview A tutorial on implementing a glitch effect in Jetpack Compose by drawing composable content to an offscreen buffer, slicing it horizontally, and applying randomized translations, scaling, color overlays, and timed animation. ### Source excerpt Easily apply sci-fi, cyberpunk effects on to your app ## 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 ## Build a self-hosted, GPU-accelerated translation API with open-source LLMs DevFeed: [Build a self-hosted, GPU-accelerated translation API with open-source LLMs]() Original publisher: [Read original article]() Author: fm.mateo Published: 2025-08-07T12:57:31Z Content type: tutorial Language: en Sources: [Homegate Engineering Blog - Medium]() Topics: [Low Latency](), [Large Language Model](), [Cloud](), [Google Cloud Platform (GCP)](), [GPU](), [Inference](), [Open Source](), [Self-hosted](), [API](), [Back end](), [Monitoring](), [Tooling]() Tags: [ai](), [amazon](), [api](), [backend](), [cloud](), [cost](), [deepl](), [energy](), [google-translate](), [inference](), [infrastructure](), [latency](), [low-latency](), [machine-translation](), [monitoring](), [open-source](), [tooling](), [translation]() ### AI overview This step-by-step guide describes how Swiss Marketplace Group built and deployed a self-hosted, GPU-accelerated translation service using open-source large language models on Google Cloud Platform. The article reports over 85% cost savings, sub-three-second latency, and no impact on buyers' conversion rate compared with its previous DeepL API usage. ### Source excerpt Build a low-cost, low-latency, low-energy AI Translator: a DeepL alternative that worksA step-by-step guide to deploying your own AI-powered translation API at scale, and get rid of DeepL, Google Translate, Amazon Translate, etc.Introduction and motivation At Swiss Marketplace Group (SMG), we operate multiple online platforms used daily by millions of people across Switzerland. One of them, Ricardo, is a second-hand marketplace where buyers and sellers interact in four different languages: French, German, Italian, and English. To deliver a seamless experience across languages, we had been relying on DeepL API, one of the most accurate translation APIs on the market. And while DeepL served us well in terms of quality and response time, it came with significant downsides: A monthly cost of over 7,000 CHF A black-box approach, offering no insight into how translations were produced Data privacy risks As usage grew, so did the bill, and the urgency to reduce it. Around that time, generative AI had made enormous improvements, and open-source large language models (LLMs) had become more accessible than ever. This sparked a question: Can we replace DeepL API with a self-hosted open-source LLM, without sacrificing translation quality, speed, and user experience? The answer turned out to be yes. Over the course of my master thesis, I built a production-grade, GPU-accelerated translation service using modern LLM tooling, hosted entirely on Google Cloud Platform (GCP), and fully integrated into Ricardo's infrastructure. The result: Over 85% cost savings Sub-3-second latency No impact on conversion rate of buyers And everything is reproducible, transparent, and extensible. In this article, I'll walk you through exactly how I built it, from selecting the right model, optimizing inference time, and wrapping it in an API, to deploying and monitoring it in production. My goal is simple: enable you to do the same. Whether you're a backend developer, a ML engineer, or just AI-curious ## Gemma 3n fully available in the open-source ecosystem! DevFeed: [Gemma 3n fully available in the open-source ecosystem!]() Original publisher: [Read original article]() Author: Aritra Roy Gosthipaty; Pedro Cuenca; Sergio Paniego; Vaibhav Srivastav; Christopher Fleetwood; Joshua; Steven Zheng; Kashif Rasul Published: 2025-06-26T00:00:00Z Content type: article Language: en Sources: [Hugging Face - Blog]() Topics: [gemma](), [Open Source](), [AI Development](), [llama.cpp](), [MLX](), [Ollama](), [transformers.js](), [GPU](), [Hardware](), [timm](), [asr](), [Embeddings]() Tags: [ai](), [artificial-intelligence](), [audio](), [community](), [embeddings](), [gemma](), [gpu](), [hardware](), [implementation](), [llama-cpp](), [llm](), [mlx](), [multimodal](), [ollama](), [open-source](), [release](), [research](), [speech](), [timm](), [transformers](), [transformers-js](), [translation](), [vision](), [vlm]() ### AI overview This article announces the availability of Gemma 3n in major open-source libraries and presents practical usage and fine-tuning examples. It describes the model variants, memory-efficient hardware requirements, multimodal audio and vision encoders, speech-to-text and translation capabilities, and architectural features including MatFormer and Per-Layer Embeddings. ### Source excerpt We're on a journey to advance and democratize artificial intelligence through open source and open science. ## Translating Keycloak with Weblate DevFeed: [Translating Keycloak with Weblate]() Original publisher: [Read original article]() Author: Alexander Schwartz Published: 2025-04-07T00:00:00Z Content type: article Language: en Sources: [Keycloak Blog]() Topics: [Keycloak](), [Front end](), [GitHub](), [pull-requests]() Tags: [community](), [frontend](), [git](), [github](), [idm](), [kerberos](), [keycloak](), [languages](), [ldap](), [native](), [notifications](), [openid-connect](), [pull-requests](), [q-a](), [review](), [saml](), [sso](), [translation]() ### AI overview Keycloak now integrates with Weblate to simplify translation contributions. Contributors can use a web-based frontend without Git skills, while language maintainers receive automated notifications and review submissions. The article also describes maintainer requirements and the continued use of GitHub pull requests. ### Source excerpt Keycloak runs in a lot of regions and countries. Translations help Keycloak to reach a wider audience by making the platform usable for speakers of various languages. For translations, Keycloak now integrates with Weblate to simplify the process. The community can use a web-based frontend to contribute translations, and the language maintainers get automated notifications and review the translations. Read on for more details on the process. We had an online Q&A session for AMER/EMEA and APAC where you can see this process live and in action. Translate using Weblate Weblate eliminates the need for Git skills; and browsers suffice for translation contributions. Two language maintainers are needed to set up a translation for Keycloak in Weblate. They need to be native speakers of that language and will regularly review the contributions from the community. Today this is the case for languages like Catalan, German, Dutch, Italian, Japanese and Spanish. To have your language added to Weblate, join the GitHub discussion on translations and pair up with others. '' ## Ethereum.org 2024 Translatathon recap DevFeed: [Ethereum.org 2024 Translatathon recap]() Original publisher: [Read original article]() Author: Digital Studio Published: 2024-10-16T00:00:00Z Content type: article Language: en Sources: [Ethereum Foundation Blog]() Topics: [Ethereum](), [Documentation](), [Learning](), [Remix](), [Solidity]() Tags: [contributors](), [devcon](), [developer](), [documentation](), [ethereum](), [ethereum-org](), [languages](), [learning](), [recap](), [remix](), [translation]() ### AI overview The article recaps ethereum.org's 2024 Translatathon, in which 327 contributors translated 2.53 million words across 70 languages. It reports growth from the previous year, prize distribution, expanded multilingual coverage, and translation activity across Ethereum-related projects. ### Source excerpt The 2nd edition of the ethereum.org Translatathon is in the books! This year, we saw 327 contributors translate an incredible 2.53 million words across 70 languages. Let's look at the details:... ## Keycloak 25.0.2 released DevFeed: [Keycloak 25.0.2 released]() Original publisher: [Read original article]() Author: Keycloak Team Published: 2024-07-18T00:00:00Z Content type: release Language: en Sources: [Keycloak Blog]() Topics: [Keycloak](), [migration](), [LDAP](), [REST API](), [Quarkus]() Tags: [health-checks](), [idm](), [kerberos](), [keycloak](), [keycloak-release](), [ldap](), [migration](), [migration-guide](), [openid-connect](), [release](), [rest-api](), [saml](), [secret-rotation](), [sso](), [translation]() ### AI overview Keycloak 25.0.2 was released on July 18, 2024. The release includes enhancements to management-interface configuration, Admin REST API documentation, and documentation language, along with fixes across the user interface, LDAP synchronization, authorization, migration, operators, and other components. ### Source excerpt To download the release go to Keycloak downloads. Upgrading Before upgrading refer to the migration guide for a complete list of changes. All resolved issues Enhancements #30094 Do not inherit 'https-client-auth' property for the management interface #30537 Document how Admin REST API endpoints work with Hostname config docs #30856 Remove inclusive language foreword docs Bugs #19070 authBaseUrl error on different hostname-admin-url, hostname-url admin/ui #26042 Issue when start-dev in 23.0.1 dist/quarkus #28489 Missing help text on tokens tab admin/ui #29407 Need refresh attributes group translations on Users > Details tab admin/ui #29566 User Profile attributes/groups in Admin UI are not translated using Localization for non-master realm when signed in the master realm account/ui #29761 bug: disabling all default features no longer works core #29784 Exception while trying to run a LDAP sync with a group importer and a batch size less then the actual number of groups ldap #30329 Client secret rotation UI shows wrong rotated secret admin/ui #30355 New operator failing on health checks operator #30383 Account Console (v3) no longer highlights the current page in the nav bar account/ui #30436 Client Roles are not shown when clientId property is set admin/ui #30440 UI theme bug in KC 25.0.0 admin/ui #30444 Failed to evaluate permissions when fetchRoles is enabled on role policies authorization-services #30449 Migration stuck if versions incompatible operator #30521 "Client Offline Session Max" no longer available admin/ui #30541 Account UI resources try to load from admin path instead of frontend path account/ui #30552 After migrating from 24 to 25, the signature algorithms names do not display in drop down menu admin/ui #30591 Invalid character in spanish translation file for Identity Provider Link Template translations #30652 Default server port is used instead of the management interface port in the guide about running Keycloak in a container #30662 User policy -> se ## Evolution of translations management for Android at Revolut DevFeed: [Evolution of translations management for Android at Revolut]() Original publisher: [Read original article]() Author: Yaroslav T Published: 2023-12-05T17:28:51Z Content type: article Language: en Sources: [Revolut Engineering]() Topics: [Android](), [Development](), [migration](), [Script](), [Gradle](), [Groovy]() Tags: [android](), [development](), [evolution](), [gradle](), [gradle-plugin](), [groovy](), [kotlin](), [management](), [migration](), [translation]() ### AI overview An engineering retrospective on how Revolut evolved Android translation management across multiple apps, modules, and languages. It describes using Lokalise, moving translation downloads from app startup to scripts, and migrating the script from Python to Groovy through a Gradle task. ### Source excerpt Here's everything you need to know about how translations have evolved at Revolut. We currently have 6 apps, with 330 modules containing strings.xml files. And don't forget, we need to support 33 languages. To make the translation process smooth, we use the API of Lokalise. When one of our engineers adds a new string on the platform, it's translated into all languages within 1 hour. After that, we need to download and place the translations into the correct module. Now, from an engineering perspective, here comes the most interesting part! Initial implementation In 2017, we began our expansion, and the first supported languages were French and Polish. We quickly reached a stage where fast translation became an integral part of the feature release process. Using our partner, Lokalise.com, we started implementing translations for a single app (only Revolut retail app existed at the time). We added Lokalise library to our project and used keys from it via a Singleton pattern: https://medium.com/media/b55574683f8ebc328b4049d46f1114bf/href Library downloads translations from the server once the user opens the app. This approach was fast to implement, but had 2 limitations: API has user limit, which is critical for the fast-growing application Download translations on app launch degrades the performance First script To answer both of these problems, we created a simple local script that downloads strings and puts them into the resources' folder. Before releasing a new version of the app, one of the engineers has to call this script and merge translated files into the release branch. https://medium.com/media/78c6e72e4148de66b8d461b467b0df55/hrefSimplifying developers' life Later on, one of our engineers introduced an additional script to upload keys to Lokalise. The goal was to let engineers create new keys in strings.xml during the development process, automatically upload them to the provider, translate them, and then download them back. However, we soon discovered that ## Ethereum.org Translatathon Recap DevFeed: [Ethereum.org Translatathon Recap]() Original publisher: [Read original article]() Author: Digital Studio Published: 2023-09-20T00:00:00Z Content type: article Language: en Sources: [Ethereum Foundation Blog]() Topics: [Ethereum](), [Website](), [Open Source](), [Hackathon](), [Learning]() Tags: [community](), [competition](), [ethereum](), [ethereum-org](), [event](), [hackathon](), [open-source](), [recap](), [translation]() ### AI overview Ethereum.org recaps its first Translatathon, a translation competition held to increase access to Ethereum educational and onboarding content in more languages. The event involved applications, team formation, a translation period, evaluation, and competition between teams and individuals. ### Source excerpt Ethereum.org is an educational website and portal to Ethereum - for many people, it is their first contact with Ethereum, the place where they find their first wallet or dapp to use, and their go-to resource to start learning or level up their knowledge. To best serve this purpose,... ## Polish edition of Trino: The Definitive Guide DevFeed: [Polish edition of Trino: The Definitive Guide]() Original publisher: [Read original article]() Author: Manfred Moser, Martin Traverso, Matt Fuller Published: 2023-04-06T00:00:00Z Content type: news Language: en Sources: [Trino Blog]() Topics: [big-data](), [Maintainers]() Tags: [announce](), [big-data](), [book](), [community](), [contributors](), [java](), [maintainers](), [summit](), [translation]() ### AI overview The article announces that a Polish translation of the book Trino: The Definitive Guide is available for communities in Poland and beyond. It highlights Trino's global use and Poland's active Trino, Java, and Big Data communities, including contributors and maintainers. ### Source excerpt At this stage Trino is used all around the globe as we know from the community chat and our speakers at Trino Summit 2022. One large community of Trino contributors and maintainers, many employed by Starburst, is located in Poland. Poland also has a very active participation of developers and users in the Java and Big Data communities. ## Docusaurus 2.4 DevFeed: [Docusaurus 2.4]() Original publisher: [Read original article]() Author: Sébastien Lorber Published: 2023-03-23T00:00:00Z Content type: release Language: en Sources: [Docusaurus Blog]() Topics: [Documentation](), [Query (disambiguation)](), [Developer experience]() Tags: [bug-fixes](), [bun](), [changes](), [embedding](), [google-analytics](), [migrate](), [npm](), [pnpm](), [release](), [translation]() ### AI overview Docusaurus 2.4 is announced as a minor release with updates to sidebar item descriptions, theme selection through a query-string parameter, npm-to-Yarn conversion, Google Analytics tracking IDs, error rendering, translations, and several other fixes and changes. ### Source excerpt We are happy to announce Docusaurus 2.4. ## Translating the Ethereum Foundation blog DevFeed: [Translating the Ethereum Foundation blog]() Original publisher: [Read original article]() Author: Digital Studio Published: 2022-08-31T00:00:00Z Content type: opinion Language: en Sources: [Ethereum Foundation Blog]() Topics: [Ethereum](), [Website]() Tags: [blog](), [community](), [contributors](), [ethereum](), [ethereum-org](), [languages](), [open-source](), [translation]() ### AI overview The Ethereum Foundation blog has historically published primarily in English, limiting access for the global Ethereum community. Drawing on ethereum.org's community-driven translation program, the Foundation discusses expanding blog translations and the demonstrated demand for Ethereum content in readers' native languages. ### Source excerpt Since the first post in December 2013, the Ethereum Foundation (EF) blog has been the primary way teams within the EF communicate. From announcements about events, to grant waves, protocol upgrades, regular [updates from specific teams](/2021/12/22/ef-supported-teams-research-an... ## Ethereum.org Translation Program: Milestones and Updates DevFeed: [Ethereum.org Translation Program: Milestones and Updates]() Original publisher: [Read original article]() Author: Luka Kropec Published: 2021-10-04T00:00:00Z Content type: news Language: en Sources: [Ethereum Foundation Blog]() Topics: [Ethereum](), [Documentation](), [Website](), [Discord]() Tags: [community](), [contributors](), [discord](), [documentation](), [ethereum](), [ethereum-org](), [translation](), [updates]() ### AI overview The ethereum.org Translation Program reports that more than 2,000 community members have translated 2.8 million words, making the site available in 37 languages. The update also describes expanded translator resources, translation groups, and new content versions organized into more granular work areas. ### Source excerpt The ethereum.org Translation Program has been live for over two years, and we are excited to share a couple of milestones we have hit since its inception, as well as some of our plans for the future. Since we launched the initiative in 2019, over 2,000 community members have... ## Principles and Techniques for Effective Localization DevFeed: [Principles and Techniques for Effective Localization]() Original publisher: [Read original article]() Published: 2021-08-30T09:00:00Z Content type: article Language: en Sources: [Material.io - Material Design]() Topics: [Localization (l10n)]() Tags: [effective](), [inclusive](), [techniques](), [translation]() ### AI overview The article presents principles and techniques for effective localization, emphasizing inclusive experiences beyond direct translation. ### Source excerpt Going beyond translation to create more inclusive experiences ## Ethereum.org Translation Program: Milestones and Updates DevFeed: [Ethereum.org Translation Program: Milestones and Updates]() Original publisher: [Read original article]() Author: Digital Studio Published: 2020-12-21T00:00:00Z Content type: news Language: en Sources: [Ethereum Foundation Blog]() Topics: [Ethereum](), [Website](), [data]() Tags: [community](), [developer-resources](), [ethereum](), [ethereum-org](), [program](), [translation](), [updates]() ### AI overview Ethereum.org reports milestones from its Translation Program and announces a new content push covering Eth2, the Beacon Chain, staking, network upgrades, and developer resources. The article also describes expanded language support and changes intended to keep users informed when translations are unavailable. ### Source excerpt We hope that you are all excited for the upcoming year-end holidays. Today, we've got some exciting new changes to announce for Ethereum.org's Translation Program and some milestones to celebrate. To start, we can't thank you enough for all of your support this year. Thanks to you we've been... ## Ethereum.org Translation Program: Milestone and Updates DevFeed: [Ethereum.org Translation Program: Milestone and Updates]() Original publisher: [Read original article]() Author: Digital Studio Published: 2020-07-29T00:00:00Z Content type: article Language: en Sources: [Ethereum Foundation Blog]() Topics: [Ethereum](), [Website]() Tags: [collaboration](), [community](), [ethereum](), [ethereum-org](), [languages](), [translation](), [updates]() ### AI overview Ethereum.org reports that its Website Translation Program has reached 30 supported languages, with 467 volunteers from 52 language groups contributing. The article also outlines translation progress and Q3 goals for updating languages to version 1.1. ### Source excerpt Your browser does not support the video tag. Today we're excited to celebrate a huge milestone - Ethereum.org now supports 30 languages! 🎉🎉🎉 Since we launched the Website Translation Program seven months ago, we've se... ## Development Update #3 - Ethereum.org DevFeed: [Development Update #3 - Ethereum.org]() Original publisher: [Read original article]() Author: Digital Studio Published: 2020-05-05T00:00:00Z Content type: news Language: en Sources: [Ethereum Foundation Blog]() Topics: [Development](), [Website](), [Algolia](), [IPFS](), [Ethereum Name Service (ENS)]() Tags: [algolia](), [development](), [ethereum](), [ethereum-org](), [html](), [implementation](), [search](), [translation]() ### AI overview Ethereum.org's third development update reports progress on community translations, availability through IPFS and ENS, a new Algolia-powered search function, and planned content updates. ### Source excerpt Hey Ethereum! Here's the latest update from the ethereum.org team:... ## Automatically translate Firebase in-app messages using Google Translate DevFeed: [Automatically translate Firebase in-app messages using Google Translate]() Original publisher: [Read original article]() Author: Ali Satter Published: 2020-01-21T00:00:00Z Content type: tutorial Language: en Sources: [Firebase Blog]() Topics: [Firebase](), [Google](), [Messaging](), [App]() Tags: [firebase](), [google](), [in-app-messaging](), [launch](), [messaging](), [product-updates](), [translation](), [tutorials]() ### AI overview Firebase In-App Messaging can automatically translate campaign messages into multiple languages using Google Translate. The article explains how to localize messages and how Firebase delivers translated or default content based on each user's locale. ### Source excerpt News, tutorials, and updates from the Firebase team. [Next page]()