pokerogue/public/locales/ja/mystery-encounters/field-trip-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

32 lines
1.7 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": "先生と 生徒です!",
"speaker": "先生",
"intro_dialogue": "あら、 こんにちは! 少しも 生徒のために\nお時間を させていただきますか$ポケモンの 技に付いて 教えています から\n実演を 見た方が 良いです。$手持ちポケモンの 技を 一つ 見させても 良いですか?",
"title": "修学旅行",
"description": "先生は ポケモンの 技の 実演を 頼んでいます。 技の 分類によって お礼に 便利な アイテムを くれるかもしれません。",
"query": "どの分類の 技を 見せますか?",
"option": {
"1": {
"label": "物理技",
"tooltip": "(+) 物理アイテム"
},
"2": {
"label": "特殊技",
"tooltip": "(+) 特殊アイテム"
},
"3": {
"label": "変化技",
"tooltip": "(+) 変化アイテム"
},
"selected": "{{pokeName}}は {{move}}を 堂々と 実演します!"
},
"second_option_prompt": "使いたい 技を 選んでください",
"incorrect": "……$あれは {{moveCategory}}では ありませんね!\n申し訳ありませんが、 何も あげられません。$さあ みんな、\nましな 実演を 探しに 行きましょう。",
"incorrect_exp": "……とにかく いい勉強に なりました?$ポケモンも 経験値を 得ました。",
"correct": "見せてくれて ありがとう ございます!\nこのアイテムは 冒険中に 役に立つと 良いです!",
"correct_exp": "{{pokeName}}も 貴重な 経験値を 得ました!",
"status": "変化技",
"physical": "物理技",
"special": "特殊技"
}