pokerogue/public/locales/zh-CN/mystery-encounters/clowning-around-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

35 lines
1.8 KiB
JSON
Raw Blame History

This file contains ambiguous Unicode characters

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": "是个…@d{64}小丑?",
"speaker": "小丑",
"intro_dialogue": "小丑踩高跷,战斗要来到!\n吵吵闹闹将你打倒",
"title": "小丑闹剧",
"description": "有点不对劲,这小丑想要挑衅你,\n目的是什么呢\n尤其是那{{blacephalonName}}看起来非常奇怪,\n就好像它有着\n@[TOOLTIP_TITLE]{与众不同的属性和特性。}",
"query": "你要怎么做?",
"option": {
"1": {
"label": "与小丑战斗",
"tooltip": "(-)奇妙的战斗\n(?)影响宝可梦特性",
"selected": "你可怜的宝可梦正准备上演可悲的马戏!",
"apply_ability_dialogue": "精彩的演出!\n出色的指挥与夺目的招式相得益彰",
"apply_ability_message": "小丑将永久地将你的一只宝可梦的特性交换为{{ability}}",
"ability_prompt": "你想永久地教会一只宝可梦{{ability}}吗?",
"ability_gained": "@s{level_up_fanfare}{{chosenPokemon}}获得了{{ability}}特性!"
},
"2": {
"label": "保持冷静",
"tooltip": "(-)让小丑失望\n(?)影响宝可梦道具",
"selected": "小懦夫,竟敢拒绝我。\n尝尝我的厉害",
"selected_2": "小丑的{{blacephalonName}}使用了戏法!\n你的{{switchPokemon}}的所有道具都被随机变换了!",
"selected_3": "傻了吧,我的把戏毫无破绽!"
},
"3": {
"label": "骂回去",
"tooltip": "(-)让小丑失望\n(?)影响宝可梦属性",
"selected": "小懦夫,竟敢拒绝我。\n尝尝我的厉害",
"selected_2": "小丑的{{blacephalonName}}使用了一个奇异的招式!\n你队伍的所有属性都被随机变换了",
"selected_3": "傻了吧,我的把戏毫无破绽!"
}
},
"outro": "小丑和他的帮手\n在一阵烟雾中消失了。"
}