mirror of
https://github.com/pagefaultgames/pokerogue.git
synced 2024-12-01 11:16:21 +00:00
95386861bb
* 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
26 lines
1.1 KiB
JSON
26 lines
1.1 KiB
JSON
{
|
||
"intro": "宝可梦附近的地上\n有闪闪发光的东西！",
|
||
"title": "战逃反应",
|
||
"description": "似乎有强大的宝可梦守护着这一道具。\n战斗是最直接的方法，但是\n它的实力似乎不容小觑。\n如果你有合适的宝可梦，\n似乎也可以直接偷走它。",
|
||
"query": "你要怎么做？",
|
||
"option": {
|
||
"1": {
|
||
"label": "战斗",
|
||
"tooltip": "(-)困难的战斗\n(+)新道具",
|
||
"selected": "你无所畏惧的走向宝可梦。",
|
||
"stat_boost": "{{enemyPokemon}}的潜在实力提升了它的一项能力！"
|
||
},
|
||
"2": {
|
||
"label": "窃取物品",
|
||
"disabled_tooltip": "你的宝可梦需要习得\n特定的招式来选择。",
|
||
"tooltip": "(+){{option2PrimaryName}}使用{{option2PrimaryMove}}",
|
||
"selected": ".@d{32}.@d{32}.@d{32}$你的{{option2PrimaryName}}愿意帮忙，并使用了{{option2PrimaryMove}}！$你偷走了道具！"
|
||
},
|
||
"3": {
|
||
"label": "离开",
|
||
"tooltip": "(-)无奖励",
|
||
"selected": "你决定把宝贝留给这只宝可梦\n并继续上路了。"
|
||
}
|
||
}
|
||
}
|