安装 Steam
登录
|
语言
繁體中文(繁体中文)
日本語(日语)
한국어(韩语)
ไทย(泰语)
български(保加利亚语)
Čeština(捷克语)
Dansk(丹麦语)
Deutsch(德语)
English(英语)
Español-España(西班牙语 - 西班牙)
Español - Latinoamérica(西班牙语 - 拉丁美洲)
Ελληνικά(希腊语)
Français(法语)
Italiano(意大利语)
Bahasa Indonesia(印度尼西亚语)
Magyar(匈牙利语)
Nederlands(荷兰语)
Norsk(挪威语)
Polski(波兰语)
Português(葡萄牙语 - 葡萄牙)
Português-Brasil(葡萄牙语 - 巴西)
Română(罗马尼亚语)
Русский(俄语)
Suomi(芬兰语)
Svenska(瑞典语)
Türkçe(土耳其语)
Tiếng Việt(越南语)
Українська(乌克兰语)
报告翻译问题
I released a minor update v141 without debug information in the DLLs and at least according to virustotal it is clear in bitdefender now. Was definitely a false positive since debug information that I removed wasn't even executable code or loaded during normal use.
edit: ahh wait, now it's flagging a different DLL, libiconv-2 ? What the hell. I'm pretty confident it's not actual Babar since Babar isn't known for having a Linux version and I do my Windows builds under Linux, not to mention that majority of antiviruses are not flagging anything.
I'm pretty confident this can't be Babar because the builds are made under Linux, plus Babar is not known for being cross platform or infecting arbitrary binaries like an old school virus.
But for libiconv-2.dll it is the opposite: with debug symbols, no alert, without debug symbols, alert.
That is particularly ridiculous because the one without debug information is literally a cut down version of the one with. I even verified by making a comparison between the files and finding that the one without debug information didn't have anything added to it, only removed.
I could probably just remove 32-bit version altogether since almost nobody on Steam uses 32-bit windows any more, but I'd rather keep it since the original release supported 32-bit and I'd rather honor original system requirements.
It's like one guy has to take off the beret to not be mistaken for a french spy, and their co-worker has to wear a beret to not be mistaken for a french spy.