Unaunga mkono muundo gani wa faili?

Tunaunga mkono muundo wa Edge extension messages.json. Pakia kwa lugha yoyote ya chanzo—AI yetu huitambua kiotomatiki. Kila faili inapaswa kuwa na funguo za ujumbe zenye sehemu ya 'message', hiari 'description', na hiari 'placeholders'. Tunathibitisha muundo wakati wa kupakia na tunakataa faili zisizo sahihi.

Je, mnatfsiri vishikizo kama $PLACEHOLDER$?

Hapana—tunavihifadhi kama vilivyo. AI yetu imefunzwa kutambua sintaksia ya kishikizo cha Chrome ($PLACEHOLDER$) na kuviacha bila kuguswa katika tafsiri zote. Maandishi yanayozunguka hutafsiriwa huku vishikizo vikibaki salama.

Bei inategemea ada ya chini ya $9.99 pamoja na gharama ya kila lugha inayoongezeka kulingana na idadi ya tokeni za faili yako. Faili kubwa = bei ya juu. Pia tunatoa chaguo la Uchakataji wa Kipaumbele (+$5) kuruka foleni na kukamilisha ndani ya saa 1. Unaona bei kamili baada ya kupakia faili yako.

Tafsiri huchukua muda gani?

Kazi nyingi hukamilika ndani ya chini ya dakika 5. Tunachakata lugha zote kwa wakati mmoja kwa kutumia GPT-5. Kazi za kipaumbele huchakatwa mbele ya foleni na kwa kawaida hukamilika ndani ya dakika 1-2.

Je, mnahifadhi faili zangu?

Tunahifadhi faili yako ya chanzo na tafsiri zilizozalishwa kwa siku 7 ili uweze kuzipakua tena. Baada ya siku 7, faili zote hufutwa kabisa. Hatushiriki maudhui yako na wahusika wengine zaidi ya API ya OpenAI (inayohitajika kwa tafsiri).

Ni lugha gani zinazotumika?

Tunaunga mkono maeneo 52 yanayojumuisha lugha zote kuu za Microsoft Edge Add-ons: Kijerumani, Kifaransa, Kihispania, Kiitaliano, Kireno (Brazili na Ureno), Kijapani, Kikorea, Kichina (Rahisi na Jadi), Kiarabu, Kihindi, Kirusi, na nyingine nyingi. Kila eneo hutumia msimbo sahihi wa eneo (mf., pt_BR, zh_CN).

Imeundwa mahsusi kwa viendelezi vya Edge

Ujanibishaji wa AI kwa Viendelezi vya Edge

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 Edge 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 Kiendelezi cha Edge yako. Tafsiri huanza baada ya malipo—tunaweka kazi kwenye foleni na kutengeneza ZIP ndani ya dakika chache.

Pakia

Dondosha faili yako ya messages.json ya chanzo. Tunaichanganua papo hapo na kuthibitisha umbizo la Kiendelezi cha Edge.

Chagua lugha na uone bei

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

Pakua ZIP

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

Imeundwa kwa ajili ya wasanidi programu

Imeundwa mahsusi kwa muundo wa eneo wa Kiendelezi cha Edge. Si zana ya tafsiri ya jumla.

Inatambua muundo wa Edge

Imeundwa mahsusi kwa muundo wa messages.json wa Kiendelezi cha Edge 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 Edge inavyofanya kazi

Viendelezi vya Microsoft Edge hutumia muundo wa i18n wa Chromium ulio sawa kabisa — muundo uleule wa _locales/{locale}/messages.json kama Chrome. Ikiwa kiendelezi chako tayari kinalenga Chrome, matokeo ya LocalePack hufanya kazi kwa Edge bila marekebisho yoyote.

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

Mfano wa mwito

chrome.i18n.getMessage("appName")

Inahitajika kwenye manifest

"default_locale"

Edge imejengwa juu ya Chromium. ZIP yoyote ya _locales inayofanya kazi kwa Chrome itafanya kazi kwa Edge kama ilivyo.

Duka la Viongezi vya Microsoft Edge husoma _locales/ ili kuonyesha majina na maelezo ya viendelezi yaliyotafsiriwa kwa watumiaji wanaovinjari duka kwa lugha yao.

Jifunze muundo wa i18n wa Chromium →

Edge is Chromium, so Chrome's rules apply

Edge extensions use the identical Chromium i18n format. That means the compatibility is total — and so are Chrome's constraints.

Byte-identical file format: Edge reads the same _locales/{locale}/messages.json structure as Chrome. A package that already works in Chrome works in Edge with no modification.
The same locale-code rules carry over: Because Edge inherits Chromium's locale resolution, the underscore convention (pt_BR, not pt-BR) and the supported-code list apply exactly as they do in Chrome.
One ZIP, two stores: The same LocalePack output can be submitted to both the Microsoft Edge Add-ons store and the Chrome Web Store without rebuilding the locale files.
chrome.i18n, not edge.i18n: There is no Edge-specific namespace. Extension code calls chrome.i18n.getMessage() exactly as it does on Chrome.

Because Edge inherits Chromium's behaviour, it also inherits the silent failure: an unsupported locale folder is ignored rather than reported.

Kwa nini usitumie tu zana za jumla?

Zana za tafsiri za matumizi ya jumla hazielewi muundo wa Kiendelezi cha Edge.

	LocalePack	Tafsiri ya mkono	TMS ya jumla
Muda wa usanidi	Dakika 2	Saa kwa kila lugha	Dakika 30+
Uwazi wa gharama
Usalama wa muundo wa Edge
Ulinzi wa placeholder
Kasi (lugha 52)	< dakika 5	Wiki	Saa
Inafaa zaidi kwa	Viendelezi vya Edge	Miradi midogo	Programu 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

“Hatimaye zana inayoelewa muundo wa kiendelezi cha Edge. Hakuna tena kurekebisha vishikilia nafasi vilivyovunjika baada ya tafsiri.”

Marcus T.

Msimamizi wa kiendelezi

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

Dev J.

Mchangiaji wa chanzo huria

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.

Chrome extension i18n: _locales structure and default_locale

How to set up the _locales folder, what default_locale does in manifest.json, and how Chrome picks the right messages.json at runtime.

Localizing your Edge Add-ons listing

Why Partner Center shows only one listing language even when your package ships twenty, how __MSG_ manifest references drive language detection, and which listing fields Edge requires for every language versus just one.

chrome.i18n: the complete API reference

All four chrome.i18n methods with exact signatures and return types: which are synchronous, which return promises, what getMessage() returns when it fails, and how browser.i18n differs in Firefox and Safari.

Chrome extension locale codes: all 55

Every locale code Chrome accepts as a _locales folder name, with language and native names, the underscore-vs-hyphen trap that makes pt-BR silently ignored, and how Chrome picks a locale at runtime.

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.

Browse all guides →

Uko tayari kusambaza Kiendelezi cha Edge yako duniani kote?

Lipa mara moja - Pakua ZIP - Sambaza duniani kote

Ijaribu LocalePack

{ "appName": { "message": "My Extension", "description": "Name" }, "welcomeMsg": { "message": "Hello, $USER$!", "placeholders": { "user": { "content": "$1" } } } }

{ "appName": { "message": "Meine Erweiterung", "description": "Name" }, "welcomeMsg": { "message": "Hallo, $USER$!", "placeholders": { "user": { "content": "$1" } } } }

_locales/ ├── en/ │ └── messages.json ← default_locale ├── de/ │ └── messages.json ├── fr/ │ └── messages.json └── ja/ └── messages.json

{ "appName": { "message": "My Extension", "description": "Extension name" }, "greeting": { "message": "Hello, $USER$!", "placeholders": { "user": { "content": "$1" } } } }

Edge is Chromium, so Chrome's rules apply

Edge extensions use the identical Chromium i18n format. That means the compatibility is total — and so are Chrome's constraints.

Byte-identical file format

Edge reads the same _locales/{locale}/messages.json structure as Chrome. A package that already works in Chrome works in Edge with no modification.

The same locale-code rules carry over

Because Edge inherits Chromium's locale resolution, the underscore convention (pt_BR, not pt-BR) and the supported-code list apply exactly as they do in Chrome.

One ZIP, two stores

The same LocalePack output can be submitted to both the Microsoft Edge Add-ons store and the Chrome Web Store without rebuilding the locale files.

chrome.i18n, not edge.i18n

There is no Edge-specific namespace. Extension code calls chrome.i18n.getMessage() exactly as it does on Chrome.

Because Edge inherits Chromium's behaviour, it also inherits the silent failure: an unsupported locale folder is ignored rather than reported.

LocalePack

Tafsiri ya mkono

TMS ya jumla

Muda wa usanidi

Dakika 2

Saa kwa kila lugha

Dakika 30+

Uwazi wa gharama

Usalama wa muundo wa Edge

Ulinzi wa placeholder

Kasi (lugha 52)

< dakika 5

Wiki

Saa

Inafaa zaidi kwa

Viendelezi vya Edge

Miradi midogo

Programu za wavuti za makampuni

Related developer guides

Deep dives on the formats, APIs and errors behind this page — written for developers, not translators.

Ujanibishaji wa AI kwa Viendelezi vya Edge

Inavyofanya kazi

Pakia

Chagua lugha na uone bei

Pakua ZIP

Kikokotoo cha bei iliyo wazi

1. Pakia faili

2. Chagua lugha

3. Makadirio yako

Imeundwa kwa ajili ya wasanidi programu

Inatambua muundo wa Edge

Ulinzi wa placeholder

Muktadha wa maelezo

Uhamishaji wa ZIP tayari

Uchakataji sambamba

Malipo ya mara moja

Jinsi i18n ya kiendelezi cha Edge inavyofanya kazi

Edge is Chromium, so Chrome's rules apply

Kwa nini usitumie tu zana za jumla?

Visa vya Mafanikio

Inaaminiwa na watengenezaji wa viendelezi

Maswali yanayoulizwa mara kwa mara

Unaunga mkono muundo gani wa faili?

Je, mnatfsiri vishikizo kama $PLACEHOLDER$?

Bei huhesabiwaje?

Tafsiri huchukua muda gani?

Je, mnahifadhi faili zangu?

Ni lugha gani zinazotumika?

Je, mnaunga mkono vivinjari vingine mbali na Edge?

Related developer guides

Uko tayari kusambaza Kiendelezi cha Edge yako duniani kote?

Ujanibishaji wa AI kwa Viendelezi vya Edge

Inavyofanya kazi

Pakia

Chagua lugha na uone bei

Pakua ZIP

Kikokotoo cha bei iliyo wazi

1. Pakia faili

2. Chagua lugha

3. Makadirio yako

Imeundwa kwa ajili ya wasanidi programu

Inatambua muundo wa Edge

Ulinzi wa placeholder

Muktadha wa maelezo

Uhamishaji wa ZIP tayari

Uchakataji sambamba

Malipo ya mara moja

Jinsi i18n ya kiendelezi cha Edge inavyofanya kazi

Edge is Chromium, so Chrome's rules apply

Kwa nini usitumie tu zana za jumla?

Visa vya Mafanikio

Inaaminiwa na watengenezaji wa viendelezi

Maswali yanayoulizwa mara kwa mara

Unaunga mkono muundo gani wa faili?

Je, mnatfsiri vishikizo kama $PLACEHOLDER$?

Bei huhesabiwaje?

Tafsiri huchukua muda gani?

Je, mnahifadhi faili zangu?

Ni lugha gani zinazotumika?

Je, mnaunga mkono vivinjari vingine mbali na Edge?

Related developer guides

Uko tayari kusambaza Kiendelezi cha Edge yako duniani kote?