LocalePack
ChromeFirefoxEdgeOperaSafariOrodha ya CWS
Vue.jsReact
Next.jsi18nextReact Native
Miongozo ya WasanidiVisa vya Mafanikio
Placeholder-safe messages.json translation

Ujanibishaji wa AI kwa messages.json files

Pakia messages.json yako ya chanzo, chagua lugha lengwa, lipa mara moja, kisha pakua ZIP ya _locales iliyo tayari kutumwa.

Tafsiri salama kwa vishikizo
Inalingana na WebExtension messages.json
Bei iliyo wazi
messages.json
Lugha ya chanzo (mfano)
{
  "appName": {
    "message": "My Extension",
    "description": "Name"
  },
  "welcomeMsg": {
    "message": "Hello, $USER$!",
    "placeholders": {
      "user": {
        "content": "$1"
      }
    }
  }
}
Kijerumani (matokeo)
{
  "appName": {
    "message": "Meine Erweiterung",
    "description": "Name"
  },
  "welcomeMsg": {
    "message": "Hallo, $USER$!",
    "placeholders": {
      "user": {
        "content": "$1"
      }
    }
  }
}
52 locales

Inavyofanya kazi

Hatua tatu rahisi za kujanibisha browser extension yako. Tafsiri huanza baada ya malipo—tunaweka kazi kwenye foleni na kutengeneza ZIP ndani ya dakika chache.

01

Pakia

Dondosha faili yako ya messages.json ya chanzo. Tunaichanganua papo hapo na kuthibitisha umbizo la browser extension.

02

Chagua lugha na uone bei

Chagua kutoka lugha 52. Ona bei iliyo wazi kulingana na ukubwa wa faili yako kabla ya kulipa.

03

Pakua ZIP

Lipa mara moja kupitia Stripe. Tunatengeneza faili zote za _locales/{lang}/messages.json na kuzikusanya kwenye ZIP.

Onyesho la bei moja kwa moja

Kikokotoo cha bei iliyo wazi

Ona hasa utakacholipa kabla ya kupakia. Nukuu ya mwisho huhesabiwa baada ya kupakia kulingana na urefu wa maandishi na lugha ulizochagua.

1. Pakia faili

Dondosha messages.json hapa

au bofya ili kuvinjari

messages.json input. Max 500KB.

2. Chagua lugha

|

3 kati ya 55 lugha zimechaguliwa

3. Makadirio yako

Lugha zilizochaguliwa3

Bei ya mwisho huhesabiwa baada ya kupakia faili kwenye ukurasa wa malipo

Malipo ya mara moja • Hakuna usajili

Imeundwa kwa ajili ya wasanidi programu

Imeundwa mahsusi kwa muundo wa eneo wa browser extension. Si zana ya tafsiri ya jumla.

Inatambua muundo wa WebExtension

Imeundwa mahsusi kwa muundo wa messages.json wa browser extension wenye usaidizi wa message, description, na placeholders.

Ulinzi wa placeholder

Huhifadhi sintaksia ya $PLACEHOLDER$ kama ilivyo. Vigeu vyako hubaki salama katika lugha zote.

Muktadha wa maelezo

Tunasoma sehemu zako za description na kuzitumia kama vidokezo vya muktadha kwa tafsiri sahihi zaidi za AI.

Uhamishaji wa ZIP tayari

Pakua ZIP yenye muundo sahihi wa folda _locales/{lang}/messages.json. Iweke kwenye kiendelezi chako.

Uchakataji sambamba

Lugha zote hutafsiriwa kwa wakati mmoja. Kazi nyingi hukamilika ndani ya chini ya dakika 5.

Malipo ya mara moja

Hakuna usajili, hakuna ada za kila mwezi. Lipa mara moja kwa kila kazi, pakua milele.

Jinsi i18n ya kiendelezi cha WebExtension inavyofanya kazi

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.

Muundo wa folda ya _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 ya wakati wa utekelezaji

chrome.i18n / browser.i18n

Mfano wa mwito

getMessage("key")

Inahitajika kwenye manifest

"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.

Kwa nini usitumie tu zana za jumla?

Zana za tafsiri za matumizi ya jumla hazielewi muundo wa browser extension.

LocalePack
Tafsiri ya mkono
TMS ya jumla
Muda wa usanidiDakika 2Saa kwa kila lughaDakika 30+
Uwazi wa gharama
Usalama wa muundo wa WebExtension
Ulinzi wa placeholder
Kasi (lugha 52)< dakika 5WikiSaa
Inafaa zaidi kwaAny messages.json fileMiradi midogoProgramu za wavuti za makampuni

Visa vya Mafanikio

Miradi halisi iliyotumia LocalePack kufikia hadhira ya kimataifa katika hadi lugha 52.

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.

Tazama visa vyote vya mafanikio

Inaaminiwa na watengenezaji wa viendelezi

“Imeniokoa saa nyingi za kazi ya kuchosha. Nilipakia messages.json yangu, nikapata tafsiri kamili katika muundo uleule niliouhitaji.”

Sarah K.

Msanidi huru, kiendelezi cha AdBlock

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

Marcus T.

Msimamizi wa kiendelezi

“Bei iliyo wazi ndiyo iliyonishawishi. Nilijua hasa nitakacholipa kabla ya kupakia chochote.”

Dev J.

Mchangiaji wa chanzo huria

52

Lugha zinazotumika

100%

Matokeo salama kwa vishikizo

ZIP

Tayari kusafirisha

Maswali yanayoulizwa mara kwa mara

Kila unachohitaji kujua kuhusu LocalePack.

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 →

Uko tayari kusambaza browser extension yako duniani kote?

Lipa mara moja - Pakua ZIP - Sambaza duniani kote

Ijaribu LocalePack
LocalePack
MiongozoFaraghaMashartiMsaada

© 2025 LocalePack. Haki zote zimehifadhiwa.

Mradi huu ulitafsiriwa kwa LocalePack logoLocalePack