Locale Engine
19 locales. One pipeline. Zero manual plural rules.
The Locale Engine handles every locale-specific rule automatically — from Arabic 6-form plurals to CJK line-height adjustments to Hebrew RTL directionality metadata.
Engine capabilities
Handles the hard parts of every locale
RTL layout signals
Arabic and Hebrew outputs include dir="rtl" metadata and Unicode bidirectional marks where needed. Your React-i18n, gettext, or iOS LocalizedString pipeline reads this natively.
CLDR plural forms
Each locale's plural categories per the Unicode CLDR spec — zero/one/two/few/many/other — are generated where applicable. Arabic gets all 6 forms. Russian gets the correct few/many split.
CJK typography metadata
CJK locale outputs (Japanese, Korean, Chinese) include recommended line-height ratios and word-break hints. Your CSS can read these hints to prevent CJK text overflow.
CI/CD push workflow
New strings in your PR? The Locale Engine detects the diff and translates only changed keys. Output files land in your repo via a GitHub PR or are synced to Contentful automatically.
CI/CD integration
Plug into your existing pipeline
The Locale Engine connects to your GitHub repo. When you merge a string change, Lingowright opens a PR with translated output files in all 19 locales — ready to merge alongside your code.
No new deploy step. No localization meeting. The PR is part of your normal review flow.
# .github/workflows/localize.yml
name: Lingowright Sync
on:
push:
paths: ['locales/en.json']
jobs:
translate:
uses: lingowright/action@v2
with:
api_key: ${{ secrets.LWR_API_KEY }}
source: locales/en.json
locales: all
create_pr: true
One GitHub Action. 19 locales. No manual plural rules.
Free tier covers 3 locales — enough to prove it in your pipeline before you commit.
Get started free