Skip to content

chore(i18n): translate the Pokéstop Events strings - #822

Merged
hokiepokedad2 merged 2 commits into
developfrom
chore/showcase-translations
Aug 24, 2026
Merged

chore(i18n): translate the Pokéstop Events strings#822
hokiepokedad2 merged 2 commits into
developfrom
chore/showcase-translations

Conversation

@hokiepokedad2

Copy link
Copy Markdown
Contributor

Follows #817, which shipped its 29 new keys as verbatim English in all ten non-English locale files. Key parity held so nothing rendered raw, but the Pokéstop Events page read untranslated beside a nav that was not.

Scope

Only #817 was affected. I diffed each of today's other five feature commits and they translated properly, so this is 29 keys × 10 files (French gets 30, see below).

Namespace Keys
POKESTOP_EVENTS.* 24
NAV.POKESTOP_EVENTS, DASHBOARD.CARD_POKESTOP_EVENTS, ..._SUB 3
ADMIN_SETTINGS.DISABLE_SHOWCASE_LABEL / _DESC 2

Terminology came from what was already on screen

Each locale already had a translated INVASIONS.EVENT_TYPES block — the invasion chips have been rendering Showcase, Kecleon and Gold Stop names all along. Those were used as the reference so the new page and the existing chips agree rather than inventing a second vocabulary: Fremvisning / Gylden PokéStop (da), Gold-PokéStop (de), Exhibición / PokéParada dorada (es), Esibizione / Pokéstop d'oro (it), Gouden PokéStop (nl), Pokaz / Złoty PokéStop (pl), Exibição / PokéStop dourada (pt, pt-BR), Uppvisning / Gyllene PokéStop (sv).

pt and pt-BR diverge throughout, as they should — European guardar / eliminar / Tenta outra vez against Brazilian salvar / excluir / Tente de novo.

Kecleon is identical in all ten: it is a Pokémon name, shared across EN/FR/DE/ES/IT, and da/nl/pl/sv have no game localization for it.

One correction outside the new keys

French INVASIONS.EVENT_TYPES.SHOWCASE read "Présentation". Niantic's French term is "Vitrine". The existing chip is corrected too, rather than leaving the page and the chip disagreeing — that is French's thirtieth key.

Found while sweeping, deliberately not fixed here

  • en.json is inconsistent about "Pokéstop". Four spellings coexist: Pokéstop Events, PokéStop Events, Pokestop Changes, and lowercase pokestop in help text. The in-game spelling is PokéStop. Normalizing it touches keys well outside this branch.
  • fr and it hold accent-stripped stringsPOKEMON.SNACK_CREATED_WITH_DUPLICATES reads "creee(s)… deja suivie(s)" and "gia tracciato/i". Pre-existing, from a much older PR.
  • A pre-existing backlog of roughly 35 untranslated keys, unrelated to today: the whole TEMPLATE.COND_* block, five ADMIN_SETTINGS.*, two ADMIN.APPROVAL_*, four RAIDS.LEVEL.*, two MAX_BATTLES.* and ALARM_INFO.PING_TOOLTIP. Worth its own branch.

Verification

All eleven files parse, 1813 keys in every one, zero missing, key order preserved. npx jest --ci — 116 suites, 1389 tests, including locale-parity.spec.ts. prettier --check clean.

#817 shipped the Pokéstop Events feature with its 29 new keys carrying the
English text verbatim in da, de, es, fr, it, nl, pl, pt, pt-BR and sv. Key
parity held, so nothing rendered as a raw key and no test caught it -- the
page simply read in English beside a sidebar that did not.

Terminology follows the INVASIONS.EVENT_TYPES block each locale already had,
so the event names on the new page match the chips the invasion list has been
showing all along. The one departure is French, where SHOWCASE was
"Présentation"; Niantic's French term is "Vitrine", so both the existing chip
and the new strings now use it.

The other five features merged today (#815, #816, #818, #819, #821) were
checked the same way and were translated properly. What still matches English
in them is legitimately identical in that language: "Costume" in French and
Italian, "Event" in German, "Area" in Italian, "Gym", "Pokestop", "Station",
"15 min" and the countdown abbreviations.
@hokiepokedad2
hokiepokedad2 merged commit d238aaa into develop Aug 24, 2026
6 checks passed
@hokiepokedad2
hokiepokedad2 deleted the chore/showcase-translations branch August 24, 2026 18:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant