Skip to content

Add Japanese translations for Arena rebalanced cards - #11941

Merged
Jetz72 merged 1 commit into
Card-Forge:masterfrom
Saku3san:localization/ja-arena-rebalanced-batch-7
Sep 19, 2026
Merged

Jetz72 merged 1 commit into
Card-Forge:masterfrom
Saku3san:localization/ja-arena-rebalanced-batch-7

Conversation

@Saku3san

Copy link
Copy Markdown
Contributor

Summary

Adds 239 missing Japanese card translation entries for Arena rebalanced (A-) cards 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 #11872.

Scope

  • Arena rebalanced (A-) translation entries added: 239
  • Total: 239

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

The rebalanced-card census identified 245 canonical Forge translation keys:

  • Added in this PR: 239
  • Held back: 6

Sources

The added entries were verified against official Japanese sources, primarily MTG Arena Japanese localization data.

Existing official Japanese card translations were reused where the rebalanced card retained the same Japanese text as the normal version.

Official Wizards Japanese sources were also used where needed to verify historical rebalanced text that differs from the current Arena data.

Current Forge card scripts were used to verify English keys, Oracle structure, card types, rules-text structure, rebalanced-card identity, and related-face structure.

No manually translated Japanese rules text is included.

Rebalanced card names

Forge represents rebalanced cards internally with the A- prefix.

Existing Forge translations in other languages also preserve this prefix in the localized display name, so the Japanese entries follow the same convention.

For example:

A-Akki Ronin|A-悪忌の浪人|...

The A- prefix is used for the displayed rebalanced card name only; Japanese rules text remains based on the official Japanese wording.

Validation

The final candidate was checked for:

  • canonical Forge A- 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
  • related-face atomicity
  • rebalanced / normal card separation
  • localized A- display-name consistency
  • Forge Japanese type formatting
  • encoding and formatting issues

Final result:

  • additions: 239
  • deletions: 0
  • existing rows modified: 0
  • duplicate or malformed rows: 0
  • unverified or manually translated Japanese text: 0
  • incomplete related-face groups included: 0
  • held entries included: 0
  • localized rebalanced names missing the A- prefix: 0
  • BOM added: no
  • existing CRLF line endings preserved

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

Held entries

Six keys were held back because their Japanese translation could not be safely integrated against the current Forge script and available official source data:

  • A-Blessed Hippogriff
  • A-Tyr's Blesing
  • A-Alrund's Epiphany
  • A-Mischievous Catgeist
  • A-Catlike Curiosity
  • A-Sorin, Imperious Bloodlord

These entries were excluded rather than guessing, modifying Forge card scripts as part of this localization PR, or including an incomplete related-face group.

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 sources, existing official Japanese translations where applicable, and current Forge card scripts.

@Jetz72

Jetz72 commented Sep 17, 2026

Copy link
Copy Markdown
Contributor

These cards might be on the way out, considering it was recently announced they'd be removed from Arena. We've discussed splitting them into a separate custom set. I think the translations should still work for cards outside the main cards folder? If so we might merge this anyway.

@Saku3san

Copy link
Copy Markdown
Contributor Author

Thanks for the context!

I took a look at the current translation handling, and my understanding is that card translations are looked up by their translation keys rather than by where the card scripts are stored. So I think the Japanese entries may still work if the rebalanced cards are moved to a separate custom set, as long as the same A- keys are kept.

But I may be missing some project-specific details, so please correct me if I’m misunderstanding anything. I’m happy to leave the decision about this PR to you.

I’d also be glad to keep helping with Japanese localization if it would be useful to the project. There are still some untranslated cards and sets I could work on, including parts of the Pioneer-era card pool and Secret Lair cards.

I’m also interested in helping with Adventure Mode Japanese localization. Some existing Japanese UI strings feel a little literal in places, so I think there may be room to make them more natural.

At the same time, I’ve noticed that Forge’s localization and Adventure Mode translation support have been changing quite a bit recently. I don’t want to duplicate work that is already in progress or create translations that would need to be redone soon.

English isn’t my strongest language, so it can sometimes be difficult for me to follow all of the project discussions and understand the current direction.

If you have a preference, would it be better for me to continue with Japanese localization work now, or wait a little while for the recent localization changes to settle? If there are particular areas where Japanese translation help would be more useful, I’d be happy to focus there.

I’m just happy if my translations can be a useful contribution to Forge.

@Jetz72 Jetz72 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As long as you're fluent in the language, feel free to contribute whatever localization changes you want. Card translations are easy enough to approve. UI translations can be a bit of a hassle if they cover a huge batch of strings at once and sit in the queue long enough that some other dev tweaks something in the file, but feel free to submit them. Adventure content translations are new - detailed in #11621. Might be worth waiting a few weeks to ensure no issues turn up with them.

@churrufli

Copy link
Copy Markdown
Contributor

Hi @Saku3san, I’m glad you’re getting involved in the internationalization of Forge.

Regarding translating Adventure, as @Jetz72 rightly points out, I’d recommend waiting for now, as the Spanish translation is still in the testing phase. I’m playing through Adventure again, taking note of details that are still missing translations (items, enemy names, etc.) and figuring out what groundwork is needed so that other languages can be implemented properly as well.

I’m taking things slowly and carefully because I want to make sure that the internationalization process doesn’t cause any issues in such a carefully crafted and special project as Adventure. A lot of time and effort has been put into it by many people, and I want to make sure we respect all that work while also allowing the developers to continue working without the internationalization getting in their way.

As I said, I’m still working on it, so please be patient, and thank you!

@Jetz72
Jetz72 merged commit 19c21f8 into Card-Forge:master Sep 19, 2026
2 checks passed
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.

3 participants