pokerogue/public/locales/ja/mystery-encounters/absolute-avarice-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

26 lines
1.8 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": "待ち伏せの {{greedentName}}が\n手持ちポケモンの きのみを 全部 奪った",
"title": "よくよく欲張り",
"description": "{{greedentName}}の 不意打ちで 持っていた きのみを 全部 失った!\n\n{{greedentName}}は 食べ始めそうですが、 突然に 止まって 気になる 顔で あなとを 見つめる。",
"query": "どうしますか",
"option": {
"1": {
"label": "勝負だ",
"tooltip": "(-) 勝負がきつい\n(+) きのみの山積みからご褒美",
"selected": "{{greedentName}}は 頬張って おそいかかってくる!",
"boss_enraged": "{{greedentName}}の 食べ物への 情熱で ぐっと キレた!",
"food_stash": "{{greedentName}}は 巨大な 食べ物の\n山積みを 守っていたようだ$@s{item_fanfare}手持ちポケモンは 各々 {{foodReward}}を もらう!"
},
"2": {
"label": "言い聞かせてみる",
"tooltip": "(+) きのみを数個取り戻す",
"selected": "あなたの 言い聞かせてる姿は {{greedentName}}の 胸に ちょっと こたえたようです。$きのみを 全部 戻さないが、\n数個を あなたの 方面へ 投げてあげる。"
},
"3": {
"label": "全部食べさせて",
"tooltip": "(-) きのみを全部失う\n(?) {{greedentName}}は好きになる",
"selected": "あっという間に {{greedentName}}は\nきのみの 山積みを むさぼり食う$お腹を ポンポンしながら\nありがたさうな 表情で 見つめる。$もしかして、 冒険中に きのみを\nもっと 食べさせて あげようかなぁ……$@s{level_up_fanfare}{{greedentName}}は 手持ちに 入りたい!"
}
}
}