安装 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（越南语）
Українська（乌克兰语）
报告翻译问题
讨论规则及指引
举报此帖
/spoiler is for [spoiler] spoiler tagging [/spoiler]
/quote is for [quote] quoting [/quote]
/pre and /code is for [code] code stuff [/code] , with the difference of /code colorizing, while /pre does not.
None of these can be nested, nor can they be used inline... And the chat doesn't even support basic formatting such as bold, italics, etc...
Why not just implement Markdown in the chat since it's already trying so hard to be a Discord clone? That would've been a good entry-point for a full transition over to Markdown eventually.
But the way it lacks text control means it's impossible to quickly make a page unique and stand out slightly and create sidenotes or sidebars. But not impossible if you use tables. I am wary of tables as a tool, had enough pain with tables, they work best when you design it all in excel though. But it does work.
Too much power creates a mess. But maybe some extensions to jazz things up would be nice as a forward looking move.
In some ways, I'm rooting for EGS and other platforms just so Valve gets off their lazy behinds and brings its technology up to date.
Oh, should they remove the shopping cart as well?
So quote where I said that or find something better to do with your time than being a troll.
I wouldn't expect to see markdown implemented until Valve overhauls the forums, and I figure that will be a few years yet. And even then, Valve may prefer BBCode and there's nothing wrong with that. They're both working solutions to giving user formatting options.
And if Valve provides some text formatting controls it would matter even less which solution they use. No one is going to have a strong opinion which is used when they just press a button to quote some text or create a list.
Well some people might still pitch a fit because their preferred technology wasn't used, but those people are just looking to be miserable IMO.
No Markdown.
Markdown sucks.
With BBCode, the text is clear and the formatting is clear. They are very separate elements.
Markdown tries to make formatting that looks like text. As a result, it mixes formatting and text.
If you want to format something in a specific way, you can easily go outside of BBCode and use your own choice of plaintext formatting, because BBCode formatting doesn't look anything like normal text.
If you want to format something in a way that accidentally uses Markdown, you need to dance around Markdown in order to get the formatting you want.
For example: Quote blocks? You can put them in adjacent lines in BBCode. Markdown instead thinks that it's all one continuous paragraph. It's stupid.
Also, how do you do links? In HTML, you put the URL first, in a tag, and then surround the display text with that tag. You do it in the same order in BBCode. What do you do in Markdown? You put enclosers around the text, and then put the link. ...with a different set of enclosers, too. wtf is that crap
You basically said EGS is superior to Steam. Since it was in the context of discussion about the design choices they've made about forums Cathulhu correctly implied that you would prefer the inexistance of a forum at all; since that is the current state of your beloved EGS
Better yet they can both be analized about their strengths and weaknesses. Markdown surely is a more lightweight design of user formatting and in many cases that would make live a lot easier such as on creating tables but for what this user forum is BBCode is the better choice as there is a lot of "colourful" texting. It is more like spoken / written text rather than Blogposting - which is what Markdown was designed for.
EDIT:
A quick example: take my last sentence. If Markdown was a thing on here it would render to thisThought inserts would not be possible on Markdown
EDIT2:
If you want to boil it down:
Markdown is designed for texts that are prepared already and only have to be written down easily while BBCodes are more of a fluid design feature where you can make decisions on your design just in the moment of writing a word.
Probably the language barrier hitting hard here. As the rules literally state
Source: https://support.steampowered.com/kb_article.php?ref=4045-USHJ-3810&l=english
"Argumenting" or "Arguing" in different languages can mean totally different things. In Germany for example if you translate this word by word that could mean as soon as you openly have a different opinion than a moderator they are allowed to punish you - which is plain bullstuff obviously. Plus what is to be defined as "arguing"?
So if there's ever two options presented to the user, that could be nice. I'd stick with BBCode while other people could use Markdown.
I won't have beef with it as long as BBCode is an option. Or simply plaintext with no formatting available, frankly; I can prefer that over Markdown.