Traditional Chinese needs repair~

:arrow_forward: GAME INFORMATION

:point_down: These details are CRITICAL; DO NOT skip them or your issue may not be reviewed.

  • **GAME BUILD #:13.9057 (Portuguese’s technology tree and geography, African civilian introduction missing always happened before)
  • **GAME PLATFORM: Steam
  • **OPERATING SYSTEM: Windows 10

:arrow_forward: ISSUE EXPERIENCED

:point_down: DESCRIBE THE ISSUE IN DETAIL (below). LIMIT TO ONE BUG PER THREAD.
Traditional Chinese version’s units, geography introduction and technology tree need to be fix, adding, change, and translate completely.

:arrow_forward: FREQUENCY OF ISSUE

:point_down: How often does the issue occur? CHOSE ONE; DELETE THE REST!

  • 100% of the time / matches I play (ALWAYS)

:arrow_forward: REPRODUCTION STEPS

:point_down: List CLEAR and DETAILED STEPS we can take to reproduce the issue ourselves… Be descriptive!

Here’s the steps to reproduce the issue:

  1. Turn the game into Traditional Chinese version
  2. Open the introduction of military units and geography
  3. Open Portuguese and Malta’s technology tree

:arrow_forward: EXPECTED RESULT

:point_down: What was SUPPOSED to happen if the bug you encountered were not present?
Make sure introduction of military, civilian units and geography be translate completely, change repeat picture and introduction, adding the missing picture.
Technology tree be corrected.
My solution to repeat parts:
Use new one replace it or just remove the old one, because not every civs rely on mercs/outlaw to fight the war.
We should have new “Revolution Units”, “Treasure Guardian” and “Outlaw” branches in the introduction to prevent mistake and repeated like AOE2 since DE launched!
Let me say again:
If you have SIMILAR NEW ONE, just REMOVE OLD ONE!

:arrow_forward: IMAGE

:point_down: ALWAYS attach a PICTURE (.jpg, .png, .gif) or VIDEO (.mp4, YouTube link) that highlights the problem.














Sorry, I just found another part need to correct.
Since US and Mexico became playable civs, these introduction should be update as well.
Also since WarChiefs, minor civs became playable, the developers use NEW minor to replace it.
(Aztecs replaced by Zapotecs, Haudenosaunee replaced by Huron, Lakota replaced by Cheyenne)
I don’t understand, WHY NOT follow the minor civ example with Revolution option to prevent mistake and awkward at same time???
eg.
British → Ireland (replace US)
Dutch and French → Belgium (replace US)
Italians (replace US) with Malta, Russia and Ottoman-> Greek
Swedes (replace US) → Finland and Norway

Spanish (replace Mexico) → Cuba and Philippines


Finally, it’s really not hard to find how was the bayonet looking before modern bayonet…
These just part of it, we really need small change these units model…






@gmenyhart
Dear developer, please help…
If you couldn’t find the Chinese interpreter, at least let me know…



Thanks for your report. I’ve passed this info onto the localization team. :+1:

2 Likes

看上去繁体中文版本似乎比简体中文问题还要多一些……
不过起码“泰半”这个词只能说比较古,因为泰本身作为程度副词就有“很、极”的意思,这是一个正确用法。
微信截图_20220708014554

另外,不知道您是不是台湾朋友,“扎波罗热”是中港澳的译法,根据我在维基百科上的查询,台湾通行译名应该就是“扎波罗结”。
微信截图_20220708014506
微信截图_20220708014523

1 Like

你好
感謝您的解釋,我的確需要加強國學常識 :smiling_face_with_tear:

我是台灣人,我認為名稱翻譯還是應該貼近原音,而不是永遠英語看天下
這只是我個人觀點,如果不妥我馬上編輯刪除 :sweat_smile:

当然不会觉得不妥。音译人名地名常常会有各种各样的译法,尤其是两岸之间似乎大多数西文译名都不一样,比如游戏中的“鄂图曼”和“奥斯曼”,我在这方面的知识也不足,所以这个问题我也无法提供比较有意义的看法。更希望您反馈的问题尽快得到修正!

1 Like

音譯的部分僅是我個人觀點,不用更動沒關係
但我真的希望團隊已經在修復繁體中文概要的路上,千萬不要因為"沒人在乎"選擇視而不見
就像單機歷史戰役的部分一樣,遊戲開發者一直以為多數人都像電競、硬核玩家一樣"不在乎"單機內容,卻忽略他們本身就以遊戲為業隨時上網,自然說話比較大聲
根據多項民調顯示,大多數人仍屬傾向單機遊戲的休閒玩家,只不過我們除了玩遊戲還有太多事情要忙,無法隨時上網自然就成為"被代表"的沉默多數…

1 Like

@gmenyhart
Dear developer, seems like you guys are not just forgot these issues I mentioned above, but also created new bugs:
Repeated


唉,如果FE能把这次的新卡片的机器翻译全部改了就不错了

2 Likes

他們好像缺少中文翻譯,所以沒有回應
但西班牙文、德文、韓文翻譯錯誤卻能得到回覆,難不成中文翻譯是兼職所以無法及時處理? :face_with_spiral_eyes:

并非如此。现在的游戏多语言本地化基本上都是外包翻译公司制作,至于外包公司的水平……反正WE和FE显然没有足够的人力去确保最终成品品质。实际上,3DE的非英语版本都有大量翻译错误,论坛上也有人发帖指出,但官方也一直没有跟进处理。

原來是這樣…
看來英語之外都是公平的 :smiling_face_with_tear:
感謝解惑~

Looks like this existed with above bugs at same time, didn’t notice it until now. :dizzy_face: