Does BBCode need to define how to handle malformed markup like HTML5 is doing?
Does BBCode need to explain itself about how it escapes BBCode tags when using [code] tags and other peculiar behaviors that catches novice BBCoders off-guard?
>>2
This is why this is terrible. It's too easy to abuse all the tags like that and everybody and their mom will be typing every single post with B I O and U tags. Fuck off.
>>3 This is why this is terrible. It's too easy to abuse all the tags like that and everybody and their mom will be typing every single post with B I O and U tags. Fuck off.
o - overline
u - underline
b - bold
i - italics
s - strikeout
spoiler - makes readers hover with mouse to see text
sub - makes text smaller slightly lower
sup - makes text smaller and slightly higher
code - fixed width font, tries to do syntax highlighting, most bbcode inside code tags will not work
BBCode can be nested to your hearts content(or until you cause something to break).
To quote: use '> ' on a new line (the space is necessary) followed by text.
>>19
I have a hard time believing that the multi-line quote "system" -- with [o] tags and so on -- was by design. Especially when there's an obvious solution in having nested > signs on each newline. That this behavior does not format as expected in the first place is the true flaw.