Missing Chinese/Japanese/Korea fonts in Linux

Started by yangtsesu, July 15, 2017, 02:05:24 PM

Previous topic - Next topic

yangtsesu

Archlinux zh_cn.
I can not see any CJK fonts in this game.
Windows version works well.

Maybe It is a Unity3D bug,which is fixed in up-to-date version ( above 1:5.6.2f1+20170628-1 ) of unity-editor.
https://issuetracker.unity3d.com/issues/linux-simplified-chinese-characters-are-not-supported-on-linux
Can you rebuild this game with new version Unity3D. Thank you.

yangtsesu

我英语不是很好。说中文吧。
bug提交这么多天也没人理会,这是个EA game,开发不活跃?还是没人愿意管中文日文韩文的显示?
    如果需要确认这个bug,自己安装linux,看看语言选项是不是有4个显示空白。
这个bug在unity3d开发的游戏上普遍存在。

Calahan

#2
The developers do care about bugs, and I am sure they will try to fix this font problem you are having if they can (assuming it is not a problem caused by Unity, in which case they might not be able to fix it).

Although please be aware that the RimWorld developers usually work to a fairly set schedule, and when they are working on making new content for the game it is rare to see them post in the bugs forum, or any part of the forum. But when they finish working on the new content they will change to looking at the bugs that have been reported, and this is when your bug will be looked at. Along with all the other bugs that have been reported for A17.

So just because nobody has replied to your bug after a few days does NOT mean the developers do not care about it. Also please look at the other bugs being reported. The developers have not replied to any of those either, so it is not only your bug that has not received a reply.

So please have some patience. Even if the developers read your bug report today, and fix your problem today in their test builds, I very much doubt you will be able to access the fixed version until A18 is released. Meaning whether or not a developer reads and replies to your post today will not have any impact on when A18 is released, and there is currently no indication of what date A18 will be available on, so you will have to wait for A18 to be released for any fix to this problem (regardless of when, or how soon, a developer replies to this bug report).

ison


ison

We're still using Unity 5, and it looks like the bug was fixed in Unity 2017 but it doesn't say anything about Unity 5. We've updated to the newest Unity 5 version though, so there's a chance that this bug is gone. Anyway, there's not much else we can do. Thanks for reporting.