LocalePack
ChromeFirefoxEdgeOperaSafariSenarai CWS
Vue.jsReact
Next.jsi18nextReact Native
Panduan PembangunKisah Kejayaan
Placeholder-safe messages.json translation

Penyetempatan AI untuk messages.json files

Muat naik messages.json sumber anda, pilih bahasa sasaran, bayar sekali, dan muat turun ZIP _locales yang sedia untuk dihantar.

Terjemahan selamat-ruang letak
Mematuhi messages.json WebExtension
Harga telus
messages.json
Bahasa sumber (contoh)
{
  "appName": {
    "message": "My Extension",
    "description": "Name"
  },
  "welcomeMsg": {
    "message": "Hello, $USER$!",
    "placeholders": {
      "user": {
        "content": "$1"
      }
    }
  }
}
Jerman (output)
{
  "appName": {
    "message": "Meine Erweiterung",
    "description": "Name"
  },
  "welcomeMsg": {
    "message": "Hallo, $USER$!",
    "placeholders": {
      "user": {
        "content": "$1"
      }
    }
  }
}
52 locales

Cara ia berfungsi

Tiga langkah mudah untuk menyetempatkan browser extension anda. Terjemahan dijalankan selepas pembayaran—kami beraturkan tugasan dan menjana ZIP dalam beberapa minit.

01

Muat naik

Letakkan fail messages.json sumber anda. Kami menghurainya serta-merta dan mengesahkan format browser extension.

02

Pilih bahasa & lihat harga

Pilih daripada 52 bahasa. Lihat harga telus berdasarkan saiz fail anda sebelum anda membayar.

03

Muat turun ZIP

Bayar sekali melalui Stripe. Kami menjana semua fail _locales/{lang}/messages.json dan membungkusnya ke dalam ZIP.

Demo harga langsung

Anggaran harga telus

Lihat dengan tepat apa yang anda akan bayar sebelum memuat naik. Sebut harga akhir dikira selepas muat naik berdasarkan panjang rentetan dan bahasa yang dipilih.

1. Muat naik fail

Letakkan messages.json di sini

atau klik untuk semak imbas

messages.json input. Max 500KB.

2. Pilih bahasa

|

3 daripada 55 bahasa dipilih

3. Anggaran anda

Bahasa dipilih3

Harga akhir dikira selepas muat naik fail di halaman daftar keluar

Bayaran sekali sahaja • Tiada langganan

Dibina untuk pembangun

Dibina khusus untuk format locale browser extension. Bukan alat terjemahan generik.

Serasi dengan format WebExtension

Dibina khusus untuk struktur messages.json browser extension dengan sokongan message, description, dan placeholders.

Perlindungan placeholder

Mengekalkan sintaks $PLACEHOLDER$ tepat seperti asal. Pembolehubah anda kekal utuh merentas semua bahasa.

Konteks penerangan

Kami membaca medan description anda dan menggunakannya sebagai petunjuk konteks untuk terjemahan AI yang lebih tepat.

Eksport ZIP sedia

Muat turun ZIP dengan struktur folder _locales/{lang}/messages.json yang betul. Letakkannya ke dalam sambungan anda.

Pemprosesan selari

Semua bahasa diterjemah serentak. Kebanyakan kerja siap dalam masa kurang daripada 5 minit.

Bayaran sekali sahaja

Tiada langganan, tiada yuran bulanan. Bayar sekali bagi setiap kerja, muat turun selamanya.

Cara i18n sambungan WebExtension berfungsi

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.

Struktur folder _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 Runtime

chrome.i18n / browser.i18n

Contoh panggilan

getMessage("key")

Diperlukan dalam 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.

Mengapa tidak gunakan alat generik sahaja?

Alat terjemahan tujuan umum tidak memahami format browser extension.

LocalePack
Terjemahan manual
TMS generik
Masa persediaan2 minitBerjam-jam setiap bahasa30+ minit
Ketelusan kos
Keselamatan format WebExtension
Perlindungan placeholder
Kelajuan (52 bahasa)< 5 minMingguJam
Paling sesuai untukAny messages.json fileProjek kecilAplikasi web perusahaan

Kisah Kejayaan

Projek sebenar yang menggunakan LocalePack untuk mencapai audiens global dalam sehingga 52 bahasa.

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.

Lihat semua kisah kejayaan

Dipercayai oleh pembangun sambungan

“Menjimatkan saya berjam-jam kerja yang membosankan. Muat naik messages.json saya, dapat semula terjemahan yang sempurna dalam format tepat yang saya perlukan.”

Sarah K.

Pembangun indie, sambungan AdBlock

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

Marcus T.

Penyelenggara sambungan

“Harga yang telus ialah faktor penentu. Saya tahu dengan tepat berapa yang perlu saya bayar sebelum memuat naik apa-apa.”

Dev J.

Penyumbang sumber terbuka

52

Lokal yang disokong

100%

Output selamat-placeholder

ZIP

Sedia untuk dihantar

Soalan lazim

Semua yang anda perlu tahu tentang 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 →

Bersedia untuk menghantar browser extension anda ke seluruh dunia?

Bayar sekali - Muat turun ZIP - Hantar ke seluruh dunia

Cuba LocalePack
LocalePack
PanduanPrivasiTermaSokongan

© 2025 LocalePack. Hak cipta terpelihara.

Projek ini diterjemahkan dengan LocalePack logoLocalePack