2 posts tagged with html by orthogonality.
Displaying 1 through 2 of 2.
HTML entities, like Π or Σ get converted in the input area to the actual displayed characters after a preview.
So when the comment is posted, the displayed characters -- not the entities -- are actually submitted, and the submitted displayed characters are then converted to question marks in the posted comment.
The result is that a preview that looked fine turns into a comment that doesn't.
Also: using the
tag (say to preserve original whitespace) results in double-spaced lines, taking up too much vertical space. Using the tag prevents this, but whitespace is not preserved. Adding appears to be a (n ugly and hard to edit) work-around, but while leading non-breaking spaces within tags are retained in previews, they are stripped in the posted comment.
As a number of askMefi's ask for program code, and as even some FPPs may contain code fragments, this makes the code unreadable or even syntactically incorrect in languages than foolishly assign meaning to whitespace.
And it's a pure pain to spend the time to carefully add the whitespace and to Google the correct HTML entities for a post, only to see them stripped out.
(Browser: Firefox 1.0.3)The HTML markup of Metafilter proper ("the blue") differs from the markup of Metatalk and Ask Metafilter. Given the upcoming changes to Metafilter's look, can we expect similarity in markup across the site, or should we explicitly not rely on undocumented features of Metafilter? [mi]
posted by orthogonality
on Feb 16, 2005 -
8 comments
