ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #weblate
Weblate's REST API handles CI automation well, but token scoping, plural-form validation, and batch limits trip up first integrations. Here's what actually works.
Architecture note for integrating Weblate's Git branching and pull-request workflow into CI/CD: minimal design, trust boundaries, operational checks, failure modes, and redesign triggers with a concrete GitHub Actions example.
Weblate’s translation memory automatically suggests fuzzy matches for repetitive strings, cutting translator effort while preserving consistency.
A diagnostic guide for self-hosted Weblate when a component stops pulling or pushing translations, shows merge alerts, or has stale pending changes. Covers symptom mapping, ordered checks, and safe fixes.
Weblate Projects group work, Components isolate it. Using per-component repository, filemask and workflow settings lets you manage JSON, PO and other formats in one project without forcing a single review policy.
Step‑by‑step guide to identify why Weblate does not show new Git commits as translation suggestions and how to restore automatic sync.
Learn how to enable Weblate's auto-addon to scan a repository and create translation components automatically, with steps, verification checks, and rollback options.
A decision guide for engineering teams adopting self-hosted Weblate: compare direct-push vs. pull-request write-back, merge-style trade-offs, and a staging validation plan.
Guide on choosing between Weblate's built-in Whoosh index and external TMX files for large-scale localization, focusing on performance, Celery memory management, and index maintenance.