I see the Awesomeness.
It's always done that to my knowledge.
Fight smart, not fair.
Dragon Writer
It does get just a little bit annoying when you have numbers with comma delimited thousands, because then you can't tell it apart from a simple list of numbers.
An Ear Worm is like a Rickroll: It is never going to give you up.
World's Toughest Milkman
Should be easy to solve with a little regular-expression magic. I'm sure it's currently searching for ",(\\S)" (a comma followed by a non-whitespace character). This could easily be changed to ",([^\\s\\d])" (a comma followed by a character that is neither whitespace nor a digit).
edited 1st Oct '12 1:38:47 AM by Xtifr
Speaking words of fandom: let it squee, let it squee.
Lost in Space
This has been part of the parsing code for ages. Not sure why. It also affects URL's.
"It's Occam's Shuriken! If the answer is elusive, never rule out ninjas!"
Dragon Writer
^ Affecting UR Ls is B A D. Not that there are many relevant UR Ls that need commas in them to begin with, but .... [1]
It also takes priority over nowiki tag, which is also bad. NOTHING is supposed to get priority over the nowiki tag, ever.
edited 1st Oct '12 8:39:37 AM by Stratadrake
An Ear Worm is like a Rickroll: It is never going to give you up.
Is a fix for this wanted?
"For a successful technology, reality must take precedence over public relations, for Nature cannot be fooled." - Richard Feynman
Grr... <3
1,2000,30 hello,world.
It works fine on the forum. It works fine on the main pages. I think this is fixed.
edited 14th Mar '16 10:45:15 AM by war877
Locking then.
"For a successful technology, reality must take precedence over public relations, for Nature cannot be fooled." - Richard Feynman
Is there any reason why the parser now automatically adds a space after a comma?
Example: 500,700,023.75
Programming and surgery have a lot of things in common: Don't start removing colons until you know what you're doing.