pokerogue/public/locales/ja/mystery-encounters/berries-abound-dialogue.json
flx-sta 95386861bb
[Qol][Refactor] i18n lazy-loading (#4327)
* move: locales files to `/public` (from `/src`)

* install: i18next-http-backend module

* implement: i18next language lazy-loading

* remove: all `config.ts` files (for locales)

* disable: enConfig import in i18next.d.ts

* remove: console.log from utils.camelCaseToKebabCase()

* remove localization tests

we don't need to test if i18next is working.
This is the job of i18next itself

* mock i18next for tests

* fix: tests that have to use the i18next key now

instead of the english translation

* fix: absolute-avarice-encounter test

* fix: loading mystery-encounter translations

with lazy-load

* fix: 2 mystery encounter translation loading

* replace: i18next mocks any vi.fn() calls

* fix: new namespace usage in ME tests

now using "mysteryEncounters/..."

* fix: delibirdy encounter not being language specific

the encounter was checking if the modifier name includes `Berry` which is only true for english. Instead it has to check if the modifier is an instance of BerryModifier

* fix: the-expert-pokemon-breeder

the new i18n pattern requires a different namespacing which has been adopted

* fix: GTS encounter tests

* add: `MockText.on()`

* fix: berries abound test

* chore: apply review suggestion

from @DayKev

* update i18next.d.ts

* chore: fix i18next.d.ts

* fix: `dialogue-misc` switchup between `en` and `ja`

* move: `SpeciesFormKey` into enum

there was an issue with circular dependencies

* replace: `#app/enums/` with `#enums/` for `SpeciesFormKey` imports

* re-sync locales from `beta`

* rename: `ca_ES` -> `ca-ES`

* rename: `pt_BR` -> `pt-BR`

* rename: `zh_CN` -> `zh-CN`

* rename: `zh_TW` -> `zh-TW`

* fix loading Species-Form-Key in poemon-evo.

* update: i18next `supporterLngs` ...

and remove `nonExplicitSupportedLngs`

* fix: `${namespace}.` -> `${namespace}:`

thanks @MokaStitcher
2024-10-01 21:55:16 +01:00

27 lines
1.5 KiB
JSON
Raw Blame History

This file contains invisible Unicode characters

This file contains invisible Unicode characters that are indistinguishable to humans but may be processed differently by a computer. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

{
"intro": "あのポケモンの 近くに\n巨大な きのみの木が あります",
"title": "溢れるきのみ",
"description": "強いポケモンは きのみの木を 守っている ようです。一番 当たり前な 対処法は バトルですが、 結構 強力そう です。 早いポケモンが いれば 捕まえられずに 数個 取れる かもしれません……",
"query": "どうしますか?",
"berries": "きのみ",
"option": {
"1": {
"label": "バトルだ",
"tooltip": "(-) 勝負がきつい\n(+) きのみをもらう",
"selected": "怖がらないで ポケモンに 近寄っていく……"
},
"2": {
"label": "木に突っ走る!",
"tooltip": "(-) {{fastestPokemon}}は素早さを使う\n(+) きのみをもらう",
"selected": "{{fastestPokemon}}は きのみの木へ 突っ走っていきます!${{enemyPokemon}}は 受け止められる 前に {{numBerries}}を 取れます!$新たに得た ご褒美で 早く 逃げます。",
"selected_bad": "{{fastestPokemon}}は きのみの木へ 突っ走って行きます!$ダメ! {{enemyPokemon}}の方は 早くて 受け止められました!",
"boss_enraged": "相手の {{enemyPokemon}}は 怒り出した!"
},
"3": {
"label": "置いていく",
"tooltip": "(-) ご褒美なし",
"selected": "強いポケモンを そのままで 置いて 進んでいきます。"
}
}
}