pokerogue/public/locales/ja/mystery-encounters/trash-to-treasure-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

20 lines
1.4 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": "どうしますか?",
"option": {
"1": {
"label": "アイテムを掘り出す",
"tooltip": "(-) ショップで アイテムの 価格は {{costMultiplier}}倍\n(+) 素晴らしい アイテムを もらう",
"selected": "ゴミを 押し渡って 恐ろしく 汚れます。$こんなに 汚れた 人に 普段な価格で アイテムを 売る ショップの店員が いる わけじゃない ですよ……$今から ショップの アイテムは 高くなります。$しかし、 ゴミの 中で 素晴らしい アイテムを 見つけました!"
},
"2": {
"label": "さらに調べる",
"tooltip": "(?) ゴミの 起源を 見つける",
"selected": "山の 周りを 歩き回り ゴミが どのようにして ここに 現れたのかを 示す 何かを 探します……",
"selected_2": "不意に、 ゴミは 動き出します! 結局 ただのゴミじゃなくて、 ポケモンでした!"
}
}
}