安装 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(越南语)
Українська(乌克兰语)
报告翻译问题
Because the latter, is outdated for secure/trust related work-flows and integrations. Chrome it.
My real gripe is that curators are 90% cowboys and never help anyone out.
Like I said, my issue has persisted for months.
I guess we need to have steam remove the feature for everyone. If it only works for some people, then that is not equitable really.
Stay toasty
2. if it works for nobody Valve should remove the functionality.
Not saying you are wrong, but rather the tech support response is designed to deflect damage, as they often are. I'm trying to understand which part of this is "external", I think the externality here is what Jerry Wienberg was 97 percent right about when he was saying. "no matter what the problem is, it's always a people problem."
https://blog.codinghorror.com/no-matter-what-they-tell-you-its-a-people-problem/
The fact the function works for some people makes it completely obvious to me that it's a configuration problem, not a code-paths problem.