AstrologerAI: an AI astrology app localized into 52 languages
How the AstrologerAI app translated its entire experience into 52 languages with LocalePack — 6.3M tokens for $58.73 — to reach a worldwide audience in their own language.
One format, every major browser
AI lokalizacija za browser extensions
Naložite izvorni messages.json, izberite ciljne jezike, plačajte enkrat in prenesite ZIP _locales, pripravljen za objavo.
Prevodi, varni za označbe (placeholders)
Skladno z WebExtension messages.json
Transparentne cene
Kako deluje
Trije preprosti koraki za lokalizacijo vaše browser extension. Prevodi se zaženejo po plačilu—opravila uvrstimo v čakalno vrsto in ZIP ustvarimo v nekaj minutah.
01
Naloži
Spustite izvorno datoteko messages.json. Takoj jo razčlenimo in preverimo obliko browser extension.
02
Izberite jezike in si oglejte ceno
Izbirajte med 52 jeziki. Pred plačilom si oglejte transparentno ceno glede na velikost datoteke.
03
Prenesite ZIP
Plačajte enkrat prek Stripe. Ustvarimo vse datoteke _locales/{lang}/messages.json in jih združimo v ZIP.
Demo cen v živo
Transparentni ocenjevalnik cen
Pred nalaganjem natančno preverite, koliko boste plačali. Končna ponudba se po nalaganju izračuna glede na dolžino nizov in izbrane jezike.
1. Naložite datoteko
Sem spustite messages.json
ali kliknite za brskanje
WebExtension messages.json format. Max 500KB.
2. Izberite jezike
|
Izbranih 3 od 55 jezikov
3. Vaša ocena
Izbrani jeziki3
Končna cena se izračuna po nalaganju datoteke na strani blagajne
Enkratno plačilo • Brez naročnine
Narejeno za razvijalce
Namenjeno posebej za format lokalizacije browser extension. Ni generično prevajalsko orodje.
Pozna format WebExtension
Zgrajeno posebej za strukturo browser extension messages.json s podporo za message, description in placeholders.
Zaščita označevalnikov
Natančno ohrani sintakso $PLACEHOLDER$ takšno, kot je. Vaše spremenljivke ostanejo nedotaknjene v vseh jezikih.
Kontekst opisa
Preberemo vaša polja description in jih uporabimo kot kontekstne namige za natančnejše AI prevode.
Pripravljen izvoz ZIP
Prenesite ZIP s pravilno strukturo map _locales/{lang}/messages.json. Vstavite ga v svojo razširitev.
Vzporedna obdelava
Vsi jeziki se prevajajo hkrati. Večina opravil je končanih v manj kot 5 minutah.
Enkratno plačilo
Brez naročnin, brez mesečnih stroškov. Plačate enkrat na opravilo, prenesete za vedno.
Kako deluje i18n razširitve WebExtension
Every major browser reads the same _locales/{locale}/messages.json structure. Chrome, Edge and Opera expose the chrome.i18n namespace; Firefox and Safari expose browser.i18n. The file format, the placeholder syntax and the default_locale requirement are identical across all of them, which is why a single translated folder ships everywhere.
Struktura mape _locales/
_locales/
├── en/
│ └── messages.json ← default_locale
├── de/
│ └── messages.json
├── fr/
│ └── messages.json
└── ja/
└── messages.jsonmessages.json
{
"appName": {
"message": "My Extension",
"description": "Extension name"
},
"greeting": {
"message": "Hello, $USER$!",
"placeholders": {
"user": { "content": "$1" }
}
}
}API izvajalnega okolja
chrome.i18n / browser.i18nPrimer klica
getMessage("key")Zahtevano v manifestu
"default_locale"In-extension strings come from _locales/. Store listing copy is managed separately in each store's own dashboard — translating one does not translate the other.
What actually differs between browsers
The messages.json format is shared across every major browser. Only four things vary, and none of them require re-translating your strings.
- Runtime namespace
- Chrome, Edge, and Opera expose chrome.i18n. Firefox and Safari expose browser.i18n. The method names and arguments are otherwise the same.
- Folder location
- Most browsers read _locales/ from the extension root. Build frameworks move it: WXT emits public/_locales/, and Plasmo reads locales/ rather than _locales/.
- Store listing text
- In-extension strings come from _locales/. Store listing copy does not — Chrome Web Store, AMO, and App Store Connect each manage listing translations in their own dashboard.
- Locale-code lists
- Chromium browsers accept a fixed set of underscore-separated codes and silently ignore anything else. Check your codes before shipping rather than after.
One translated _locales/ folder covers Chrome, Firefox, Edge, Opera, and Safari. The porting work is in the build, never in the strings.
Zakaj ne bi preprosto uporabili generičnih orodij?
Splošna prevajalska orodja ne razumejo formata browser extension.
LocalePack | Ročno prevajanje | Generični TMS | |
|---|---|---|---|
| Čas nastavitve | 2 minuti | Ure na jezik | 30+ minut |
| Preglednost stroškov | |||
| Varnost formata WebExtension | |||
| Zaščita označevalnikov | |||
| Hitrost (52 jezikov) | < 5 min | Tedni | Ure |
| Najboljše za | Cross-browser extensions | Majhni projekti | Poslovne spletne aplikacije |
Primeri uspeha
Resnični projekti, ki so z LocalePackom dosegli globalno občinstvo v do 52 jezikih.
DevToys.pro: 400% international traffic growth across 52 languages
How the DevToys.pro web app translated its entire UI into 52 languages with LocalePack — 5.8M tokens for $58.44 — and quadrupled its international organic traffic.
DevToys New Tab: a Chrome extension localized UI + store listing in 52 languages
How the DevToys New Tab Chrome extension localized both its in-extension UI and its Chrome Web Store listing into 52 languages to reach a global audience.
LocalePack localized itself into 52 languages — with LocalePack
We used our own tool to translate the entire LocalePack site into 52 languages — 2.9M tokens for $27.37 — so developers worldwide find us in their own language.
Zaupajo nam razvijalci razširitev
“Prihranilo mi je ure dolgočasnega dela. Naložil sem svoj messages.json in dobil popolne prevode v natanko takšni obliki, kot sem jo potreboval.”
Sarah K.
Neodvisna razvijalka, razširitev AdBlock
“We ship the same _locales folder to Chrome, Firefox and Edge. One translation pass covers all three.”
Marcus T.
Vzdrževalec razširitve
“Transparentne cene so bile odločilne. Točno sem vedel, koliko bom plačal, še preden sem karkoli naložil.”
Dev J.
Sodelavec odprtokodne skupnosti
52
Podprte lokalizacije
100%
Izhod, varen za označbe mesta
ZIP
Pripravljeno za objavo
Pogosta vprašanja
Vse, kar morate vedeti o LocalePacku.
Related developer guides
Deep dives on the formats, APIs and errors behind this page — written for developers, not translators.
messages.json format explained (with placeholders)
A complete reference for the WebExtension messages.json format: the message, description, and placeholders fields, $PLACEHOLDER$ syntax, $1 positional substitutions, and common mistakes.
WXT i18n: @wxt-dev/i18n and messages.json
How @wxt-dev/i18n compiles YAML, JSON, JSONC, JSON5 and TOML message files into standard _locales/{lang}/messages.json — setup, nested keys, plurals, substitutions, type safety, and how to translate a WXT project.
Plasmo i18n: the locales/ folder gotcha
Plasmo does not read _locales/ at the project root. The three paths it does accept, where default_locale actually lives, the alphabetical-default trap, and how to place a translated _locales ZIP correctly.
Adding i18n to a CRXJS extension
CRXJS ships no i18n helper and its docs have no i18n page. Here is the working pattern: put _locales under public/, declare default_locale in manifest.config.ts, and call chrome.i18n directly.
Ste pripravljeni poslati svoj browser extension po vsem svetu?
Plačate enkrat – Prenesete ZIP – Pošljete globalno
Preizkusite LocalePack