34

Yes, the small caps you're using are bad for machines. People also may have issues with them. AceCalhoon pointed us in comments to a question on Super User about the usage and purpose of these glyphs. The top answer explains they're not intended for usage as regular written text, and that trying to use them that way breaks stuff: Those characters are not ...


33

Code formatting should never be used for non-code markup. Semantic markup (like code tags) was not added just to make HTML pages pretty, it was added to make the structural meaning of parts of the page comprehensible to software so that it can be rendered correctly. Misusing it can have unexpected consequences, especially for users who use accessibility ...


31

I feel that other formatting would be more appropriate than code tags. It's highly unusual for that formatting style to be used for every book title and game term, and some users may not appreciate their questions and answers being edited to include a non-standard formatting type. It doesn't adhere to the HTML5 specification for the 'code' element, which ...


25

Well, of course upvotes are at anyone's discretion, they can upvote because they like your clever use of headers. However, you are making a false dichotomy between "format" and "content." If someone posts a question or answer that is not readable, then it's not good content, regardless of the research the poster put into it. Let's look at your Qs and As. ...


20

Titles should clearly represent the content of the post, yes. We need to be able to find them later, and they should be good front-page advertisements for their question. But they need not be phrased as a question so long as they are clear. Titles are just that: titles. A title's first job is to succinctly inform the reader about the contents of the post, ...


15

The F in your iterations of Let Us Discuss This Further appears as a white box for me. Kind of a case-in-point: if this is happening to me, it’s happening to others, it’s degrading the readability and accessibility of the website, and therefore it should not be done. This site does not offer any feature that will correctly render small caps, and faking it ...


14

Code formatting is for code; it is not just a different way to format your text. Don't use it for non-code text. If that means we never use code formatting, so be it. Like all HTML formatting, it actually has a purpose, and using it for non-code text is using it incorrectly. HTML elements are incredibly meaningful. To you and I, bold text is just thicker, ...


14

The observation is founded 1. Style is secondary to comprehensibility Though we do prefer to maintain the style used in sources, this isn't a hard rule and is always secondary to making sure posts are comprehensible. We also have a limited palette of styling tools available and have to make do with them. 2. These aren't small-caps anyway These aren't ...


13

They are not undesired. Please do feel free to use curly quotes and apostrophes. Those curly quotes and apostrophes should not have been removed. Overall we respect your writing decisions as the original author, and should not seek to “fix” someone else's writing preferences by replacing them with our own. We may choose to replace your writing style where ...


12

The reasons are well-founded. The original question was not written in English. This meant it was extremely difficult to access the page using a screen reader. The SuperUser question Why shouldn’t I use Unicode characters to simulate typographic styles (such as small caps or script)? (linked a couple of times already) has a lot of reasons but it misses the ...


11

First, see mxyzplk's answer, which addresses the feedback to the questions and answers you've posted so far on the site. Second, RPG.SE can be confusing to newer users, so it may help to address some potential questions going forward. I've compiled these based on the content of your question here: 1. What kind of site is Roleplaying Games StackExchange (...


10

Small caps won't be implemented at SE any time soon because they can't be represented in the flavour of Markdown used by SE currently, and all feature requests that require extending the Markdown parser, which aren't mission-critical, have been turned down. (The one mission-critical extension SE has done is spoiler blocks, and they're very buggy.) The ...


10

We encourage people to edit questions to improve them. Making titles more clear is an improvement that can always be reverted by the querent.


10

If the only “problem” with a question is that its title is not phrased in the form of a question, then there is no problem with the question. Please do not clutter the top of the site with idiosyncratic edits that do not improve anything. A title in the form of a question is not inherently better than a title that is not. Of course, if there is anything ...


9

Sometimes a good comment is a bad answer First of all, to answer your stated question: both content and formatting are things which can add (or subtract) from the quality of a post. They are both things that will help an answer be correct, clear, and convincing: if an answer is all three, it is more likely to be well received (in the form of upvotes). It ...


8

In chat, sticky returns (manual line breaks to make a second paragraph in the same chat entry) break most code. And all links need http:// or they won't process as links at all.


8

(Thanks for clarifying.) No, titles do not need to be formatted as questions. They just need to communicate well what the question is about. They're titles! If you want to know what the question is, read the question body. That's the place where all the important context is, too, and you should be reading that. (If you're not, you're answering the title ...


7

Pasting isn't always necessary Mostly you don't need to paste any PHB material into posts. Anyone who can answer already has their own copy to read, so usually you just need to say what you're asking about. Your first question How complex can my commands be with the conjured animal spell? is plenty clear on what it's asking about, and is an example of a ...


7

You're doing what will answer the question the best. In most cases, this is neither essay nor newspaper form - believe it or not (I know some of our users don't) but many questions can be answered in a single paragraph. Keep in mind that adding an essay on a related subject or your related thoughts can degrade and not enhance the value of a concise answer ...


7

I prefer putting special terms in bold font, but can live with the code formatting. I think SteveC's format for DDI links is sub-optimal though and have been pondering mentioning it. I find having the ddi link sitting all by itself in brackets after each linked term interrupts the text.


6

I'm not a big user here, but here's my two cents: I could see highlighting certain specific game terms, when they are a big deal to the overall context of the post. Like, I dunno, highlighting class abilities for D&D 3/4 does make the text a bit more readable in some ways. It sorta stops you a little and says, "Here, here is the thing you should look up....


6

Here's my strategy for writing answers on all SE sites: Use only as much quotation as is absolutely required to make your point. It's almost always better to summarize rather than to quote giant chunks because your answer needs to be tailored to answer the question. Use integrated quotes when possible as it makes you totally look like you know what you you'...


5

I largely agree with SevenSidedDie. However, I wrote a long comment about the magic jar question and decided it made more sense as an answer: I read the magic jar question, and there's nothing wrong with the title, but instead something wrong with the question. The question doesn't contain one specific question. It's just asking for general information ...


5

I tend to go with whatever seems to “work” for a particular answer, but in general having some kind of headline, abstract, or what have you, helps to give people a perspective on what your answer is, so they can read your case in the appropriate lens. It also does help those who, yes, don’t read entire answers – especially when they don’t know where a long ...


5

Code has just few valid aplications for RPG, it should not be used for others: proper code in a programming language by extent command code for a plugin/program/page such as anydice pseudocode isn't proper code but highly relies on code structuring Examples An example for proper code using BASIC. This is a non-aborting loop that just continiues to print ...


4

It has the practical benefit of making keywords standing out. The way this has been done does not meet my personal aesthetic preference. Also, it's difficult to define a rule when doing this kind of review. How Deep? Which are the terms to be formatted? If a system has a clear definition for attack, should the word attack be formatted? Should it be ...


4

The About page already has plenty of attention drawn to it. Log out of the site or enter it in private/incognito mode: there's an introductory panel to briefly inform new users about the site's basics, plus a button that links to the About page. Maybe the FAQ and the Formatting Help pages can do with more attention, but the About page already has plenty. ...


4

What you're doing wrong is trying to start a new list already nested. That's not an option, there's no other list for them to be nested inside yet! You're right that the list indentation syntax conflicts with code indentation, but that's sorted out by the list indentation syntax taking precedence. You can start a list out at the first list level. It can ...


4

Actually, you can even include code blocks inside lists without <pre>, as long as you indent them by an extra four spaces (or one tab) for each level of nesting. It looks best if you also consistently indent your nested lists by four spaces; while the Markdown parser is generally forgiving and allows you to use any number of spaces to indent lists, ...


3

What's happening is that when you include an empty line and don’t indent the next one, Markdown treats that as starting a new paragraph (specifically, whatever block tag you are currently in is closed, and then a <p> tag is inserted). Thus, in your case, it ends the list (which is a <ul>; putting a blank line triggers </ul> followed by <...


Only top voted, non community-wiki answers of a minimum length are eligible