Leveraging Weblate Translation Memory for Consistent UI Strings
Learn how to turn on Weblate’s Translation Memory, tune its similarity threshold, and reuse approved translations to reduce repetitive work and improve consistency.
Loading…
ReadMeFeed / Community knowledge
#i18n
Real questions. Useful conversations. Find the people who know your stack.
weblateEvaluating the 'norg' Library for Norwegian Language Support
Learn how to verify whether the 'norg' package truly offers Norwegian locale support before depending on it in your application.
norgUsing Weblate's Shared Translation Memory to Reduce Translation Work
Learn how to enable Weblate's shared translation memory to reuse approved strings across components, cut translation effort, and avoid common pitfalls.
Which method ensures consistent timezone display in the AngularJS date filter?
Regional Timezone Handling in AngularJS AngularJS 1.x utilizes the native JavaScript Date object for time representation. While the built-in date filter provides extensive options for formatting date strings into specific patterns, it relies on the browser's local environment for timezone offsets. When an application must display timestamps in a specific reg
Weblate Automatic Translation: Bootstrap and Maintain Translations Without Overwriting Human Work
How Weblate's Automatic translation add-on works, a safe bootstrap configuration that never overwrites human translations, and the limits teams hit with machine translation at scale.
Sulu CMS Internationalization: Quick Guide to Page Translations
Sulu CMS uses the sulu_content table to store page translations, linking them to sulu_page via a translations association. URLs use locale prefixes and fallback to a default locale. This guide explains how to add translations, configure routing, and avoid common pitfalls.
Next.js i18n: Where to Convert Dates for User Time Zones
Goal Determine the optimal location for converting server‑side timestamps into the user’s local time zone within a Next.js application. Current Constraints Server Components run on the server and cannot read navigator.timezone directly. The framework’s i18n routing only detects locale, not time zone. Time zone information must be explicitly passed from the c
nextjs