pokerogue/public/locales/ja/mystery-encounters/fiery-fallout-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.9 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": "猛烈な 煙と灰の嵐に 遭遇しました! ",
"title": "燃える熱気",
"description": "渦巻く 灰と 残り火に より、 視界は ほぼゼロに なりました。 どうやら この状況を 引き起こしている 原因は 何かある ようです…… しかし、これほどの規模の 現象を 起こしたのは 一体 何でしょうのか​​?",
"query": "どうしますか?",
"option": {
"1": {
"label": "原因を見つける",
"tooltip": "(?) 原因を発見\n(-) キツいバトル",
"selected": "火の嵐を 突き進むと、 交配の踊りを している 2匹の {{volcaronaName}} を 見つけます!$邪魔に 快く思わないで 襲いかかってきます!"
},
"2": {
"label": "避難してみる",
"tooltip": "(-) 気象状態に耐える",
"selected": "避難を 探してみる 間に 気象状態が 重大な 被害を もたらします! $ 手持ちポケモンは 最大HPの 20 ダメージを 受けます",
"target_burned": "その上、 {{burnedPokemon}} も やけど状態 になりました!"
},
"3": {
"label": "ほのおポケモンが助ける",
"tooltip": "(+) 状態が治まる\n(+) もくたんをもらう",
"disabled_tooltip": "選ぶには 2匹の ほのおタイプの ポケモンが 必要",
"selected": "{{option3PrimaryName}}と {{option3SecondaryName}}が 交配の踊りを している 2匹の {{volcaronaName}}まで 導きます!$おかげさまで 落ち着かせる ことができ\n{{volcaronaName}}が 問題なく 立ち去ります。"
}
},
"found_charcoal": "気象状態が 治ってから \n{{leadPokemon}}が 地面で 何かを 見つけます。$@s{item_fanfare}{{leadPokemon}}が もくたんを 手に入れた!"
}