Skip to content

Add Japanese translations for Wilds of Eldraine - #11756

Open
Saku3san wants to merge 1 commit into
Card-Forge:masterfrom
Saku3san:localization/ja-pioneer-batch-5-woe
Open

Add Japanese translations for Wilds of Eldraine#11756
Saku3san wants to merge 1 commit into
Card-Forge:masterfrom
Saku3san:localization/ja-pioneer-batch-5-woe

Conversation

@Saku3san

@Saku3san Saku3san commented Sep 1, 2026

Copy link
Copy Markdown
Contributor

Summary

Adds 293 missing Japanese card translation entries for Wilds of Eldraine (WOE) to cardnames-ja-JP.txt.

This PR only adds missing entries. It does not modify or remove any existing Japanese translation entries.

This is a follow-up to #11722.

Scope

  • Wilds of Eldraine (WOE): 293
  • Total: 293

Existing translation entries modified: 0
Existing entries removed: 0
Other files changed: 0

The WOE census identified 316 canonical Forge faces:

  • Main faces: 266
  • Adventure faces: 50
  • Already translated upstream: 15
  • Added in this PR: 293
  • Held back: 8

Sources

The 293 added entries were verified against official Japanese sources:

  • Official Wizards Japanese card gallery: 289 entries
  • Official Wizards Japanese Wilds of Eldraine release notes: 4 entries

Official Japanese card gallery:

The official Japanese WOE release notes were used for four face records whose gallery pages did not provide usable Japanese card text:

  • Beanstalk Wurm
  • Plant Beans
  • Gumdrop Poisoner
  • Tempt with Treats

Current Forge card scripts were used to verify English keys, Oracle structure, card types, rules-text structure, Adventure relationships, and reminder-text presence.

No manually translated or synthetic Japanese text is included.

Validation

The final candidate was checked for:

  • canonical Forge English keys
  • current Forge card-script resolution
  • four-column cardnames-ja-JP.txt structure
  • duplicate English keys
  • mana symbols and numeric values
  • card type and rules-text structure
  • existing-row modifications
  • reminder text
  • Adventure related-face atomicity
  • encoding and formatting issues

Final result:

  • additions: 293
  • deletions: 0
  • existing rows modified: 0
  • duplicate or malformed rows: 0
  • unverified or manually translated Japanese text: 0
  • incomplete related-face groups included: 0
  • reminder-text HOLD entries included: 0
  • BOM added: no
  • existing CRLF line endings preserved

The final Git diff contains one changed file with 293 additions and 0 deletions.

Reminder text

Cards whose current Forge Oracle includes reminder text were only included when the corresponding official Japanese reminder text could be confirmed.

Among the missing WOE candidates with Forge reminder text:

  • Official Japanese reminder text confirmed: 119
  • Held because the corresponding official Japanese reminder text could not be fully verified: 3

Those 3 entries were excluded rather than translated manually or included with incomplete reminder text.

Related faces and Adventures

WOE Adventure cards were handled as atomic related-face groups.

50 Adventure groups were audited:

  • atomic PASS: 47
  • atomic HOLD: 3
  • incomplete related groups included: 0

If one face of an Adventure group could not be verified safely, the unresolved face and any required sibling entry were held back rather than including an incomplete group.

Eight keys were held back in total:

  • unresolved official Japanese source: 3
  • unverified official reminder text: 3
  • sibling entries excluded because their related Adventure groups were atomic HOLD groups: 2

No held key is included in this PR.

Notes

AI-assisted tooling was used for comparison, source tracking, structural auditing, and validation.

Final Japanese card text was restricted to verified official Japanese Wizards sources and current Forge card scripts.

@Saku3san

Saku3san commented Sep 5, 2026

Copy link
Copy Markdown
Contributor Author

@Jetz72 Thanks for the review and approval! Just checking if there’s anything else needed from my side before this can be merged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants