LocalePack
ChromeFirefoxEdgeOperaSafariCWS listing
Vue.jsReact
Next.jsi18nextReact Native
Vodiči za programerePrimeri uspeha
Placeholder-safe messages.json translation

AI lokalizacija za messages.json files

Otpremite svoj izvorni messages.json, izaberite ciljne jezike, platite jednom i preuzmite ZIP _locales spreman za objavu.

Prevodi bezbedni za placeholder-e
Usklađeno sa WebExtension messages.json
Transparentne cene
messages.json
Izvorni jezik (primer)
{
  "appName": {
    "message": "My Extension",
    "description": "Name"
  },
  "welcomeMsg": {
    "message": "Hello, $USER$!",
    "placeholders": {
      "user": {
        "content": "$1"
      }
    }
  }
}
Nemački (izlaz)
{
  "appName": {
    "message": "Meine Erweiterung",
    "description": "Name"
  },
  "welcomeMsg": {
    "message": "Hallo, $USER$!",
    "placeholders": {
      "user": {
        "content": "$1"
      }
    }
  }
}
52 locales

Kako funkcioniše

Tri jednostavna koraka da lokalizujete svoju browser extension. Prevodi se pokreću nakon uplate—stavljamo zadatke u red i generišemo ZIP za nekoliko minuta.

01

Otpremi

Prevucite svoj izvorni messages.json fajl. Odmah ga parsiramo i proveravamo format za browser extension.

02

Izaberite jezike i pogledajte cenu

Birajte između 52 jezika. Pre uplate vidite transparentnu cenu na osnovu veličine fajla.

03

Preuzmite ZIP

Platite jednom putem Stripe-a. Generišemo sve _locales/{lang}/messages.json fajlove i pakujemo ih u ZIP.

Demo cena uživo

Transparentni kalkulator cena

Tačno vidite koliko ćete platiti pre otpremanja. Konačna ponuda se izračunava nakon otpremanja na osnovu dužine stringova i izabranih jezika.

1. Otpremite fajl

Prevucite messages.json ovde

ili kliknite da biste pretražili

messages.json input. Max 500KB.

2. Izaberite jezike

|

Izabrano 3 od 55 jezika

3. Vaša procena

Izabrani jezici3

Konačna cena se obračunava nakon otpremanja fajla na stranici za naplatu

Jednokratno plaćanje • Bez pretplate

Napravljeno za programere

Namenski napravljeno za format lokalizacije browser extension. Nije generički alat za prevođenje.

Razume format WebExtension

Napravljeno posebno za browser extension messages.json strukturu, uz podršku za message, description i placeholders.

Zaštita placeholder-a

Čuva $PLACEHOLDER$ sintaksu tačno onakvu kakva jeste. Vaše promenljive ostaju netaknute na svim jezicima.

Kontekst iz opisa

Čitamo vaša polja description i koristimo ih kao kontekstualne smernice za preciznije AI prevode.

ZIP izvoz spreman

Preuzmite ZIP sa ispravnom strukturom foldera _locales/{lang}/messages.json. Ubacite ga u svoju ekstenziju.

Paralelna obrada

Svi jezici se prevode istovremeno. Većina poslova se završi za manje od 5 minuta.

Jednokratno plaćanje

Bez pretplata, bez mesečnih naknada. Platite jednom po poslu, preuzimajte zauvek.

Kako radi i18n ekstenzije za WebExtension

A messages.json entry pairs a key with a "message" string, an optional "description" used as translation context, and an optional "placeholders" map. LocalePack parses all three: it translates only the message text, forwards the description to the model as context, and returns $PLACEHOLDER$ and $1 substitution tokens byte-identical.

Struktura foldera _locales/
_locales/
├── en/
│   └── messages.json   ← default_locale
├── de/
│   └── messages.json
├── fr/
│   └── messages.json
└── ja/
    └── messages.json
messages.json
{
  "appName": {
    "message": "My Extension",
    "description": "Extension name"
  },
  "greeting": {
    "message": "Hello, $USER$!",
    "placeholders": {
      "user": { "content": "$1" }
    }
  }
}

Runtime API

chrome.i18n / browser.i18n

Primer poziva

getMessage("key")

Obavezno u manifestu

"default_locale"

The same translated messages.json drops into _locales/{locale}/ for Chrome, Firefox, Edge, Opera and Safari without further edits.

messages.json format explained →

What the translator has to preserve

A messages.json entry is more than a key and a string. Getting these four pieces wrong is what breaks extensions after machine translation.

message
The user-visible string, and the only field that should ever change during translation.
description
Context for whoever — or whatever — translates the string. LocalePack feeds this to the model as translation context, so a good description measurably improves output quality.
placeholders
Named substitutions written as $PLACEHOLDER$ in the message, with their own content definitions. These must survive translation exactly, including the dollar signs and casing.
Positional substitutions
$1 through $9 map to arguments passed to getMessage(). A translator that reorders a sentence must keep these tokens intact, not renumber them.

Most generic translation tools treat $PLACEHOLDER$ and $1 as ordinary words. Once they are translated or reordered, the extension ships with broken interpolation.

Zašto ne biste jednostavno koristili generičke alate?

Alati za prevođenje opšte namene ne razumeju format browser extension.

LocalePack
Ručni prevod
Generički TMS
Vreme podešavanja2 minutaSati po jeziku30+ minuta
Transparentnost troškova
Bezbednost formata WebExtension
Zaštita placeholder-a
Brzina (52 jezika)< 5 minНедељеСати
Najbolje zaAny messages.json fileМали пројектиEnterprise veb aplikacije

Primeri uspeha

Stvarni projekti koji su koristili LocalePack da dopru do globalne publike na čak 52 jezika.

AstrologerAI AI astrology app localized into 52 languages

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.

DevToys.pro developer tools web app localized into 52 languages

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 Chrome extension localized into 52 languages

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.

The LocalePack site localized into 52 languages with LocalePack

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.

Pogledajte sve primere uspeha

Poverenje programera ekstenzija

“Uštedelo mi je sate zamornog posla. Otpremio sam svoj messages.json i dobio savršene prevode u tačno onom formatu koji mi je bio potreban.”

Sarah K.

Indie programer, AdBlock ekstenzija

“Our $PLACEHOLDER$ tokens came back untouched in all 52 locales. That is the whole reason we stopped scripting it ourselves.”

Marcus T.

Održavalac ekstenzije

“Транспарентне цене су биле пресудне. Тачно сам знао колико ћу платити пре него што било шта отпремим.”

Dev J.

Сарадник на пројектима отвореног кода

52

Подржани локали

100%

Izlaz bezbedan za placeholder-e

ZIP

Спремно за испоруку

Често постављана питања

Sve što treba da znate o LocalePack-u.

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.

Validate messages.json before shipping

How to catch every class of messages.json error before your users do: JSON syntax, missing required fields, missing keys across locales, malformed placeholder syntax, and manifest key mismatches.

__MSG_key__ in manifest.json explained

How the __MSG_key__ substitution syntax works in Chrome and Firefox extension manifests: which fields support it, how Chrome resolves tokens at load time, and the pitfalls that cause silent failures or upload rejections.

chrome.i18n.getMessage() returns empty

getMessage() returns an empty string when a message is missing, and logs nothing at all. Every cause of the silent empty string, how to tell it apart from undefined, and how to confirm each one.

Browse all guides →

Spremni ste da isporučite svoj browser extension globalno?

Platite jednom - Preuzmite ZIP - Isporučite globalno

Isprobajte LocalePack
LocalePack
VodičiPrivatnostUsloviPodrška

© 2025 LocalePack. Sva prava zadržana.

Ovaj projekat je preveden uz pomoć LocalePack logoLocalePack