LocalePack
ChromeFirefoxEdgeOperaSafariListing CWS
Vue.jsReact
Next.jsi18nextReact Native
Panduan DevKisah Sukses
Placeholder-safe messages.json translation

Pelokalan AI untuk messages.json files

Unggah messages.json sumber Anda, pilih bahasa target, bayar sekali, lalu unduh ZIP _locales yang siap dirilis.

Terjemahan aman untuk placeholder
Sesuai dengan messages.json WebExtension
Harga transparan
messages.json
Bahasa sumber (contoh)
{
  "appName": {
    "message": "My Extension",
    "description": "Name"
  },
  "welcomeMsg": {
    "message": "Hello, $USER$!",
    "placeholders": {
      "user": {
        "content": "$1"
      }
    }
  }
}
Jerman (hasil)
{
  "appName": {
    "message": "Meine Erweiterung",
    "description": "Name"
  },
  "welcomeMsg": {
    "message": "Hallo, $USER$!",
    "placeholders": {
      "user": {
        "content": "$1"
      }
    }
  }
}
52 locales

Cara kerjanya

Tiga langkah sederhana untuk melokalkan browser extension Anda. Terjemahan berjalan setelah pembayaran—kami mengantrekan pekerjaan dan menghasilkan ZIP dalam hitungan menit.

01

Unggah

Letakkan file messages.json sumber Anda. Kami memprosesnya seketika dan memvalidasi format browser extension.

02

Pilih bahasa & lihat harga

Pilih dari 52 bahasa. Lihat harga transparan berdasarkan ukuran file Anda sebelum membayar.

03

Unduh ZIP

Bayar sekali melalui Stripe. Kami menghasilkan semua file _locales/{lang}/messages.json dan mengemasnya menjadi ZIP.

Demo harga langsung

Estimator harga transparan

Lihat persis berapa yang akan Anda bayar sebelum mengunggah. Penawaran final dihitung setelah unggah berdasarkan panjang string dan bahasa yang dipilih.

1. Unggah file

Letakkan messages.json di sini

atau klik untuk menelusuri

messages.json input. Max 500KB.

2. Pilih bahasa

|

3 dari 55 bahasa dipilih

3. Perkiraan Anda

Bahasa dipilih3

Harga final dihitung setelah file diunggah di halaman checkout

Pembayaran sekali bayar • Tanpa langganan

Dibuat untuk developer

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

Mendukung format WebExtension

Dibuat khusus untuk struktur messages.json browser extension dengan dukungan message, description, dan placeholders.

Perlindungan placeholder

Mempertahankan sintaks $PLACEHOLDER$ persis apa adanya. Variabel Anda tetap utuh di semua bahasa.

Konteks deskripsi

Kami membaca kolom description Anda dan menggunakannya sebagai petunjuk konteks untuk terjemahan AI yang lebih akurat.

Ekspor ZIP siap pakai

Unduh ZIP dengan struktur folder _locales/{lang}/messages.json yang benar. Masukkan ke ekstensi Anda.

Pemrosesan paralel

Semua bahasa diterjemahkan secara bersamaan. Sebagian besar pekerjaan selesai dalam kurang dari 5 menit.

Pembayaran sekali bayar

Tanpa langganan, tanpa biaya bulanan. Bayar sekali per pekerjaan, unduh selamanya.

Cara kerja i18n ekstensi 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.

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 pemanggilan

getMessage("key")

Wajib di 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.

Kenapa tidak pakai alat generik saja?

Alat terjemahan serbaguna tidak memahami format browser extension.

LocalePack
Terjemahan manual
TMS generik
Waktu penyiapan2 menitBerjam-jam per bahasa30+ menit
Transparansi biaya
Keamanan format WebExtension
Perlindungan placeholder
Kecepatan (52 bahasa)< 5 menitMingguJam
Paling cocok untukAny messages.json fileProyek kecilAplikasi web perusahaan

Kisah Sukses

Proyek nyata yang menggunakan LocalePack untuk menjangkau audiens global hingga 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 studi kasus sukses

Dipercaya oleh pengembang ekstensi

“Menghemat saya berjam-jam pekerjaan yang membosankan. Saya mengunggah messages.json, lalu mendapatkan terjemahan sempurna dalam format persis yang saya butuhkan.”

Sarah K.

Pengembang indie, ekstensi AdBlock

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

Marcus T.

Pengelola ekstensi

“Harga yang transparan adalah poin penentunya. Saya tahu persis berapa yang akan saya bayar sebelum mengunggah apa pun.”

Dev J.

Kontributor open source

52

Locale yang didukung

100%

Output aman untuk placeholder

ZIP

Siap dirilis

Pertanyaan yang sering diajukan

Semua yang perlu Anda ketahui 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 →

Siap merilis browser extension Anda secara global?

Bayar sekali - Unduh ZIP - Rilis secara global

Coba LocalePack
LocalePack
PanduanPrivasiKetentuanDukungan

© 2025 LocalePack. Hak cipta dilindungi undang-undang.

Proyek ini diterjemahkan dengan LocalePack logoLocalePack