LocalePack
ChromeFirefoxEdgeOperaSafariSeznam v CWS
Vue.jsReact
Next.jsi18nextReact Native
Vodniki za razvijalcePrimeri uspeha
Placeholder-safe messages.json translation

AI lokalizacija za messages.json files

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
messages.json
Izvorni jezik (primer)
{
  "appName": {
    "message": "My Extension",
    "description": "Name"
  },
  "welcomeMsg": {
    "message": "Hello, $USER$!",
    "placeholders": {
      "user": {
        "content": "$1"
      }
    }
  }
}
Nemščina (izhod)
{
  "appName": {
    "message": "Meine Erweiterung",
    "description": "Name"
  },
  "welcomeMsg": {
    "message": "Hallo, $USER$!",
    "placeholders": {
      "user": {
        "content": "$1"
      }
    }
  }
}
52 locales

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

messages.json input. 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

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 mape _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" }
    }
  }
}

API izvajalnega okolja

chrome.i18n / browser.i18n

Primer klica

getMessage("key")

Zahtevano v 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.

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 nastavitve2 minutiUre na jezik30+ minut
Preglednost stroškov
Varnost formata WebExtension
Zaščita označevalnikov
Hitrost (52 jezikov)< 5 minTedniUre
Najboljše zaAny messages.json fileMajhni projektiPoslovne spletne aplikacije

Primeri uspeha

Resnični projekti, ki so z LocalePackom dosegli globalno občinstvo v do 52 jezikih.

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.

Oglejte si vse primere uspeha

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

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

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.

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 →

Ste pripravljeni poslati svoj browser extension po vsem svetu?

Plačate enkrat – Prenesete ZIP – Pošljete globalno

Preizkusite LocalePack
LocalePack
VodnikiZasebnostPogojiPodpora

© 2025 LocalePack. Vse pravice pridržane.

Ta projekt je bil preveden z LocalePack logoLocalePack