Issues with the Japanese translation in FoA V1.3.0.0

Now that I’ve finally finished the main campaign, I’d like to share some feedback regarding the Japanese localization.
There are a few critical translation issues, some of which are serious enough to interfere with completing the main quest itself.
Please consider the detailed explanation below as supplementary information.


Hello! First of all, I’m really enjoying Fangs of Asterkarn.
Unfortunately, I also have some disappointing feedback regarding the Japanese localization. There are a number of significant issues with the current translation.
The most serious problem is that many proper nouns do not match the terminology used in the previous Japanese localization. This inconsistency makes it surprisingly difficult to follow even the main quest.

To summarize the issues:

  • Proper nouns are inconsistent with the previous localization. (Severity: Critical)
  • The writing style and terminology are inconsistent with the previous localization. (Severity: High)
  • Monster Infrequents (MIs) have been translated into Japanese. (Severity: Depends on the player — since affixes and suffixes remain untranslated, every new MI item ends up with an awkward or inconsistent name.)
  • Some text is not wrapped correctly, causing parts of it to be cut off in the UI. (Severity: Medium — this even affects important messages near the climax of the main quest.)
  • Some translations are grammatically correct Japanese, but the wording feels out of place and doesn’t fit Grim Dawn’s established tone and world-building. (Severity: Medium)
  • Some previously translated text has been altered for no apparent reason, and the changes make it worse. (Severity: Low)
  • Various smaller mistranslations. (Severity: Low)

One additional point that I haven’t included in the list is that some characters’ dialogue also feels unnatural in Japanese. However, since I’m not a native English speaker, I can’t confidently judge whether this is due to the original English or the translation itself, so I don’t want to make claims I’m not certain about.
To be honest, I don’t think these issues can realistically be resolved simply by asking the localization company to revise them. The only practical solution, in my opinion, would be to bring back the community localization effort.
I’d be happy to help fix these issues myself if I could, but unfortunately that’s beyond my abilities. I’m sorry.

1 Like

As a supplement, I will cite specific locations.

#1. This is likely a fix to address the difficulty in locating the quest target when its name differs from the standard version.

・bq_av01.txt
《永遠なる》イルゴールを破壊せよ >イルゴア, ザ エターナルを破壊せよ
《処刑卿》アルカモスを放逐せよ >アルカモス, 主席死刑執行人を放逐せよ

・bq_av02.txt
《血の先触れ》ラゴス’アクを放逐せよ >ラゴス’アク, ハービンジャー オブ ブラッドを放逐せよ
《混沌の先触れ》シャー’ズールを放逐せよ >シャー’ズール, ハービンジャー オブ カオスを放逐せよ

・bq_av03.txt
《歪みの悪疫》ジャレンを討て >ジャレン ザ プレイグワープトを討て
《大君主》ヴァン・アルドリッチを討て >オーバーロード ヴァン アルドリッチを討て

・bq_av04.txt
《イセリアルの眼》スラスサーを討て >スラッサー イーサーゲイズを討て
《野生の心臓》ガルガボルを討て >ガルガボル, 野生の心を討て

・bq_av05.txt
大魔導師モルゴネスを討て >大魔術師モルゴネスを討て

・bq_ku04.txt
クトーニアンの予兆を討て >クトーニアンの兆しを討て

・bq_ku12.txt
フォーティチュードのレリックを製作せよ >剛勇 のレリックを製作せよ
フォーティチュードを カーンの バウンティテーブルへ 届けろ >剛勇 を カーンの バウンティテーブルへ 届けろ

・mq_06a_ugdenbog.txt
《朽ちゆく塚》バルゴール > バルゴール, 朽ちゆく小山

・mq_06b_korvan.txt
異形の太陽の墓所 > エルドリッチの太陽の墓

・sq_potionsugdenbog.txt
シルヴァリアン樹脂を 入手しろ > シルヴァリアンの樹脂を 入手しろ


#2. Regarding place names, item names, and monster names that differ from the original versions: while this does not significantly impact gameplay, it feels unnatural, so it is advisable to correct them. (I believe you can perform a batch replacement for the files in the FoA folder.)

イコン砦 >アイコン砦
エルラン>エルーラン
アルコヴィア>アーコヴィア
ウグデンボグ>ウグデンボーグ
《黒の軍団》>ブラックリージョン
グロブル>グローブル
バーゴル>バルゴール

I will report on other lower-priority items later.


postscript:

Please note that these corrections have already been applied to the Japanese-language files containing the community-created custom rainbow filters, providing a provisional solution.

2 Likes

#3 I found an issue that appears to be of importance.

・sq_22_houndsofchthon.txt

The number of lines does not match the English file, which may prevent the quest from progressing correctly.

1 Like

It’s going to be next to impossible for the new translation team to perfectly line things up with a decade of community localization. They are different people with their own style.

We are happy to make corrections and changes if they are reported.

The Hounds of Ch’thon quest is missing several lines in all languages. This is an error we forwarded to localization for a future hotfix.

I think the issues go well beyond differences in translation style.

My main question is this: if the community eventually completes a revised Japanese localization (I’m sorry that, personally, I can probably only help by identifying translation errors), would you be willing to accept it as a whole for consideration?

The reason I ask is that there are at least several thousand issues that would need to be corrected. Reporting every single one individually isn’t really practical.

If the answer is yes, that would be fantastic.

Keeping these fixes as a mod would also create a number of complications—for example, compatibility with GrimTools, confusion for new players, and the need for the community to maintain a separate localization indefinitely. That’s why I’d much rather see the official Japanese localization improved if possible.

I thought the Japanese translation for FoA was quite well done; it handles the unique line-breaking requirements of the Japanese version effectively. (To be honest, I had feared it might require more extensive corrections. :sweat_smile:)

That said, I do plan to report any issues that might actually hinder gameplay. While it is possible to make manual corrections on the PC version, that isn’t an option on Xbox.

1 Like

#4: While the game handles line breaks for irregular characters unique to the Japanese language environment very well, unfortunately, there are a few places in the quest text where characters are cut off and unreadable.

However, this is not something typically done in standard translation work, and it takes some practice to separate the text with spaces effectively; so, no matter who does the work, there will inevitably be some minor issues at first.

I was a little unsure about the best course of action this time, but since it would take the community a long time to check every single part within the game, I’ve revised the entire quest file by adding half-width spaces to ensure there are no text truncations. I’ve attached the file below.

After reviewing the contents, you may either make corrections only to the relevant sections or simply replace the file with this one. (This file includes the corrections listed above under #1 through #3.)

Quest_JA_0726_2026.zip (54.0 KB)

In addition, here are two tips for using spaces to break up text.

  1. Always insert a space after a period 「。」 in the middle of a sentence. If you don’t, the block of text will become too long, making it more likely for characters to be cut off.
  2. Rather than breaking the text into fixed-length segments, I think you’ll achieve a more natural line break if you treat the Japanese text as if it were an English sentence and break it up accordingly.

I apologize for causing you this extra work, but I appreciate your cooperation.

1 Like

The suggested changes made here have been incorporated.

I studied Japanese for a while, but nowhere near enough to vet this, so I’m trusting you guys. :wink:

1 Like

In fact, addressing issues like text wrapping and text cutoff is a challenging task—even for native Japanese speakers—and cannot be fully resolved without checking all the text within the game itself. Furthermore, since default fonts differ across platforms such as Linux and Mac, the extent of text cutoff varies slightly, so this factor must also be taken into account.

I do not believe it is realistic to ask the translation team to handle this task, so we would like the community to provide support for this specific part. For this reason, I expect to be in touch regarding some additional minor corrections going forward. :joy:

1 Like

#5: This is an addition to #2.

審問官 > 尋問官
ドランゴール > ドレングール

I have checked, and it appears that a batch replacement for the files in the FoA folder will work fine; however, regarding “Lord Vidurian of the Inquisition,” this is a newly introduced name, and since there is insufficient information to determine the most appropriate translation, I believe it should be left as is. (Please exclude just this one instance.)

・tagsgdx3_items.txt
tagGDX3WeaponGun1hD302_Desc=“異端審問官ヴィドゥリアン卿は、 刃のように 致命的な一発一発を 愉しんだ。 撃つたびに またひとりの異端者を 墓へ送ったからだ。”


#6: Upon checking the actual game screen, I found instances where the text was cut off.

*I have attached the corrected files for the items below; please review them and feel free to swap out the existing files.
Text_JA_0730_2026.zip (61.8 KB)

This is the additional information for #1.

・npc_kurndruid_01.txt
・npc_kurndruid_02.txt

《朽ちゆく塚》バルゴール > バルゴール, 朽ちゆく小山
異形の太陽の墓所 > エルドリッチの太陽の墓

The text was cut off.
・mq_06c_void.txt

・object_beronathhorn_01


・npc_avianelder_01.txt

The ID is missing in two places, resulting in a “Tag not” status.

・tagsgdx3_storyelements.txt
Line 157 : tagNotification_Beaver05=
Line 784 : tagGDX3LoreObj_AREAH_KastorranNoteA04Name=


1 Like

The following is a list of translation issues that remain unfixed even in the community version (created by Matougi-sensei!).
I wrote this in Japanese because I lack the ability to communicate the details in English. I wasn’t sure where to post this, but I’m dropping it here for the time being.
Also, I haven’t done the hidden quests yet.

・コリニア
い生き延びて来た
~恐らく以前からのもの
・チルハート
原文を読む限り
「もう一つの現実で 立往生したら」ではなく「もう一つの現実で 立往生しました」ではないか?
~原文にそういうニュアンスがあったらごめんなさい
・ウルグリム(npc_ulgrim_06.txt)
一人称が俺、なのはどうなんだろう?
俺たちで教団を止めるんだ。はおかしい。我々で教団を止めるんだ。にするべき
~ロルバしてほしい
・派閥友好度アップ時のチュートリアル(tagQuickTip54)
改行されていない
・ファルディスのセリフ全般
バーサーカー時のセリフ変化の関係で全部変わっている
~別に問題があるようには見えないが
・破砕
は、から始まって違和感がある
~破砕は、で良いのでは
・影の心臓
~~ハートで統一されているのでシャドウハートのほうがよい
・Act5開始時のクリードのセリフ(npc_inquisitorcreed_02.txt)
全体的に何故かスペースが大量に入っている上に異常な空欄があったりとおかしい、キャラクサスがカラクサスになっている等の固有名詞の問題点も山積み。
~以前の内容にロールバックすべき
・コンポーネント類の一括収納が試薬と書かれている
~別の表現のほうが良さげ
・昇越の祭壇の説明文がヘン
イーサーアイテムがイセリアルアイテムになっている、毒酸が酸と毒になっている
・アイテムの設計図の名前と実際に作られるアイテムがかなり一致していない
・あくまで個人的だがMIアイテム名はカタカナ表記にしてほしい
~ルシウスのレイスアーム等
・イオンとイーオンの表記揺れ
~イオンに統一したほうが良いと思う
・魔女の神
結構ある
~魔神にすべき
・異形の太陽の墓所
~エルドリッチの太陽の墓
・セレスティアル
~セレスチャルに統一してほしい
・骨まで凍る叫び
流石にダサい
・バーサーカーのスキル説明文
ダサい
・ヴィン「巨人」オズマルド
ヴィン “巨人” オズマルドのほうがいい
・〜の表記
文字コードがおかしくて文字化けを発生させる。~に統一すべきかも?
・クトーニックの名前
一部の’入りの名前の’が・に置換されているため原文のニュアンスを損なっている
・ヒーロータイプ
統一してほしい
・WPS周りと二刀流二丁拳銃周り
表記揺れがすごいので以前の方式に統一してほしい
・ヴェールとベール
どちらでもいいが以前から使われているベールに統一してほしい
・神話級 セレスティアルのワーム
Mythical Celestial Wyrmなのでおかしい。ウィルム。
・凍てついたアスター
統一がなされていない。
フローズン・アスターやフローズンアスターになっている箇所がある。

This report covers areas beyond just FoA, and since it includes some issues that have already been reported—and the specific points requiring correction aren’t entirely clear—the developers might not know exactly what needs fixing. I’m not very confident in my English either, so how about we organize the details and resubmit the report via the Japanese section of RoT? We can use Japanese there. Alternatively, if there’s no need to keep a public record of the conversation, we could also communicate via DM.

1 Like

I’m afraid I can’t do anything with this :laughing:

Regarding the posts by maniruka, we have successfully clarified which points require correction and which do not; I will now report on the specific points that need to be addressed (outlining methods that are straightforward and easy to implement :sweat_smile:).


#7 : The names in the blueprints do not match the actual item names, so they need to be aligned.

・\foa\tagsgdx3_items.txt
tagGDX3FocusD301=秘奥の無限の目
tagGDX3Blueprint_WeaponD301=設計図:無限の秘奥の目

tagGDX3WeaponCaster1hF303=《嵐乗り》サンドル・シル
tagGDX3Blueprint_WeaponF308=設計図 : 嵐乗りのサンドル・シル

*Regarding “Arcanum Infinite Eye”: since “infinite eye” appears in files like tags_skills.txt and \FG\tagsgdx2_storyelements.txt and is translated as “無限の目”, I believe the translation for this specific term would be “秘奥の無限の目” .


#8 : The original text uses the word “Guard,” but since the intended meaning is “reinforcement,” that translation doesn’t fit the context. I suspect the correct term should be “ガード” or “番人.”

・tags_creatures.txt
tagRace017=強化
tagRace017P=強化


I have attached the corrected file for the report mentioned below; please review it and replace the existing file with this version. (The corrections were made to the v1.3.0.5 file.only #14 uses the base game text; all others use the FoA text.)

Text_JA_0803_2026.zip (169.8 KB)

Regarding item #5, I found that not everything had been corrected and there was a mix of translations, so I have now fixed the remaining parts.

ドランゴール > ドレングール

bq_av10.txt
bq_ku07.txt
npc_dranghoulchief_01.txt
\npc_dranghoulchief_03.txt
npc_kurnchieftain_01.txt
npc_thanevilgar_01.txt
npc_thanevilgar_02.txt
npc_thanevilgar_03.txt
object_bounty_kurn.txt
sq_kurn_02_oldalliances.txt
sq_kurn_03_legacyofwar.txt
tagsgdx3_achievements.txt
tagsgdx3_creatures.txt
tagsgdx3_items.txt
tagsgdx3_storyelements.txt

審問官 > 尋問官

mq_.txt
npc_blacklegionscout_01.txt
npc_sageamera_01.txt
npc_thanevilgar_01.txt


#9 : As with #2 and #5, these are conventional terms that need to be reverted.

Although there are differences, these are not translation errors and the meaning remains clear, so I initially thought no corrections were necessary; however, I decided that corrections were required because item and monster names do not match the established terminology—causing issues such as failing to yield expected results when searching on GrimDawnTools.

イーオン > イオン

tagsgdx3_creatures.txt
tagsgdx3_items.txt

セレスティアル > セレスチャル

tagsgdx3_creatures.txt
tagsgdx3_items.txt
tagsgdx3_skills.txt

ワーム > ウィルム

tagsgdx3_items.txt

アーケイン > アルケイン
リフレクティブ > 反射

tagsgdx3_creatures.txt

ヴェール > ベール

bq_ku04.txt
bq_ku12.txt
bq_ku13.txt
npc_avianelder_01.txt
npc_meadmustflow_mykola_01.txt
npc_meadmustflow_mykola_01.txt
npc_sageamera_01.txt
npc_thanevilgar_01.txt
npc_veilwalkerutaro_01.txt
npc_wight_01.txt
npc_wight_03.txt
object_bounty_kurn.txt
sq_05_restlessdead.txt
tagsgdx3_creatures.txt
tagsgdx3_items.txt
tagsgdx3_skills.txt
tagsgdx3_storyelements.txt
tagsgdx3_ui.txt

魔女の神 > 魔神

mq_06b_korvan.txt
npc_kurndruid_02.txt


#10 : The translation of “Frozen Aster” was inconsistent across different locations. After reviewing the entire text, I determined that “凍てついたアスター” was the correct translation, so I have updated it accordingly.

フローズン・アスター > 凍てついたアスター

npc_mysticerfunn_01.txt
object_cleansethelandshrine_01.txt
sq_02_cleansetheland.txt
tagsgdx3_items.txt

フローズンアスター > 凍てついたアスター

tagsgdx3_storyelements.txt


#11 : I corrected “Aether,” which was being used as the translation for “Aetherials.”

・foa\tagsgdx3_ui.txt
tagExclusiveAscensionFormula09={^E}イセリアルアイテムの追加出現率 > イーサーアイテムの追加出現率

・tagsgdx3_items.txt
tagGDX3WeaponMelee2hB315=イセリアルに祝福されし槍 > イーサーに祝福されし槍
tagGDX3ShieldC301=イセリアルコアの防壁 > イーサーコアの防壁


#12 : It is a form of additional text added to the base game file, but since the entire file has been retranslated, it seems that players are confused because the translation changes with and without FoA. It is not good to have different translations of the same original text mixed together. It hurts to discard the translated parts, but I replaced everything other than the additional text with the base game text.

・foa\npc_lowercrossing_survivor_02.txt
・foa\npc_lowercrossing_survivor_01.txt


#13 : This appears to have been an error during the work process; I have performed repairs because some IDs and text were missing when compared to the pre-patch files.

・tagsgdx3_items.txt
Line973 : 彼の血の契約は、 部族の運命を クトーンの栄光へ 永遠に縛りつけた。" > tagGDX3ItemSetC301Desc=“ロクホルは かつてモグドロゲンの シャーマンだったが、 絶望の中で より暗い力へ 手を伸ばした。彼の血の契約は、 部族の運命を クトーンの栄光へ 永遠に縛りつけた。”


#14 : While the translation isn’t technically incorrect, the term Reagents (translated as “試薬”) carries a meaning closer to “potions” in Japanese; however, since the actual items don’t move like potions do, this causes confusion. Another issue is Stash (translated as “隠し箱” ); translating this back into English yields “Secret Box,” making it unclear—especially for players returning to the game after a long break, who often end up wondering, “Where did my items go?”

Therefore, rather than using the standard translation in this instance, I decided it would be best to switch to terms that most clearly reflect the actual functionality: “素材”(material)
and “共有倉庫”(shared warehouse).

tagMoveReagents=試薬を移動 > 素材を移動
tagMoveReagentsConfirm=本当に試薬を隠し箱へ 移動しますか? > 本当に素材を共有倉庫へ 移動しますか?
tagHUDOption25=試薬移動の確認 > 素材移動の確認

*I apologize for the length. Also, since Google Translate tends to become unreliable with long explanations, there may be parts that are difficult to understand. :joy:

1 Like

There was one instance where a report was omitted. :laughing:

#15 : I corrected the instances where boss names differed from previous translations, while making every effort to align with the naming conventions used for the FoA bosses in the current translation.

In addition, the following terms were slightly modified because they sounded unnatural in Japanese.
隠された隠し箱 > 隠された財宝

Please replace the file with the one I attached earlier.

tagsgdx3_achievements.txt (8.0 KB)

1 Like

addition:

#16 I corrected the place name, as it was incorrect in the original text.

・\foa\sq_02_cleansetheland.txt

Line6 : Activate the Voldur River Kurn Shrine

フレヨル渓谷の カーンの祠を 起動せよ > ヴォルドゥル川の カーンの祠を 起動せよ

Please replace this with the file I attached earlier as well.

sq_02_cleansetheland.txt (1.3 KB)

1 Like

I’m fine with incorporating corrections, but I will not put in something like this.

I accept all your decisions; please discard anything you deem unsuitable. :grinning:

#12 : I’ve come up with another approach, so please allow me to propose it. (Sorry for being persistent. :sweat_smile:)

Alternatively, how about replacing the base game’s files with the new translation?

Regarding this point, either translation is fine; I simply would like to align with one or the other if possible.
I tried replacing the base game files with the new translation from FoA.
Text_JA_0804_2026…zip (3.6 KB)

Then, while checking the revised file, I noticed that a place name differed from the existing translation in one instance.

If this proposal is to be discarded, please only make the following place-name corrections in \foa\npc_lowercrossing_survivor_02.txt.
(Since this place name isn’t tied to any quests, it’s not a high priority; however, it’s impossible to find even when searching for it, so I think it should be corrected.)

・npc_lowercrossing_survivor_02.txt
Line9 : マッド・ロウ > ぬかるみ街

・tags_storyelements.txt
tagMapMudRow=ぬかるみ街

#17: Two different translations are mixed together, so they need to be standardized to one or the other.

“Sorkar”

ソルカール <> ソーカー

ソルカール
・tagsgdx3_storyelements.txt

ソーカー
・object_mammothgraveyardmonolith_01.txt
・object_mammothgraveyardmonolith_02.txt

“Ironeye”

アイアンアイ <> 鉄眼(《鉄眼》)

Generally speaking, I would say “アイアンアイ” is the reading used for a proper name, while “鉄眼” is used as a moniker; however, either is possible.

“アイアンアイ” is located at the following two spots:

・\foa\tagsgdx3_storyelements.txt
tagGDX3FortressCave=Ironeye’s Hideout: アイアンアイの隠れ家
tagGDX3POI_AREAH_IronEyeB=アイアンアイの隠れ家の出口

There are a total of seven instances of “鉄眼” in the file below.
・tagsgdx3_creatures.txt
・tagsgdx3_items.txt
・npc_thanevilgar_03.txt
・sq_kurn_03_legacyofwar.txt


I have attached the corrected files for the items below; please use them to review the changes made. (The corrections were applied to the V1.3.0.6 files.)
Text_JA_0808_2026.zip (28.5 KB)

#18: This is the same as #17, but since a determination could be made in this case, I have created a corrected file.

“Questing Beast”

《探索獣》、クエストの獣 > 唸る獣

There are two types of translations. The community-created translation is the name of a monster from the legend of King Arthur.

・tagsgdx3_creatures.txt
tagGDX3Boss_Special01=N’erfatal, the Questing Beast : 《探索獣》ナ・アファタル
tagGDX3Boss_Special01D=Uber N’erfatal, the Questing Beast : ウーバー・ナ・アファタル、クエストの獣

Existing translation:
・\fg\tagsgdx2_items.txt
tagGDX2FocusC204=Fewmets of the Questing Beast : 唸る獣の落とし物

“Soul Echo”

エコー > 残響

foa\tagsgdx3_ui.txt
tagSoulDropsEnable=魂の欠片とエコーがドロップ可能
tagAscensionFormula03={^H}{%+.0f0}%{^E} 魂の欠片/エコーのドロップ率

Since it is translated as “残響” in tagsgdx3_items.txt, I think we should align with that.
tagGDX3CraftMaterial_SoulLesser=Soul Echo : 魂の残響

“Commander Lucius”

ルシウス > ルーシャス

This differs from the existing translation, so it needs to be aligned.

・\foa\tagsgdx3_items.txt
tagGDX3WeaponMelee2hB310=Lucius’ Wraith-Arm : ルシウスのレイスアーム

Existing translation:
・\tags_items.txt
tagWeaponMelee2hB016=Lucius’ Blade-Arm : ルーシャス ブレイドアーム


#20: Added a space because the text was getting cut off.

・tagsgdx3_ui.txt
tagAscendItemButtonInfo=アイテムをアセンドさせ、 追加属性を付与する。コモンアイテムは、 より強力な結果を 生成できる。アイテムを アセンドさせられるのは 一度だけ。

tagRerollAscendedAffixInfo=アイテムのアセンディッドボーナスを 変更し、 同等品質の新しい ボーナスにする。


Finally, there were some remaining items regarding the corrections for #2.

グロブル>グローブル

\foa\tagsgdx3_items.txt
tagGDX3FocusB301=グロブルの霜の偶像
tagGDX3FocusB302=グロブルの虚無の偶像

Similarly, there was one remaining point to be corrected from #1.

異形の太陽の墓所 > エルドリッチの太陽の墓
・\foa\mq_06b_korvan.txt
line4

*I am adding this note because replies exceeding three messages result in an error.

There was one more thing remaining in #2.

ウグデンボグ > ウグデンボーグ

\foa\tagsgdx3_items.txt
Line437 : tagGDX3WaistB304=ウグデンボグの紐帯

1 Like