HTML Conversion

When you copy over the content of the old site to the new, a lot of things made use of HTML--Reports, News Posts, Recommendations, etc. Is there a way to run a one-time conversion to switch these HTML elements to the new markup? It's not really a "bug", but it does make it more difficult to read through older stuff. I figure conversion (if possible) would be better than letting the new site use both html and the markup. The image tags are the most noticeable, and most reports are filled with them. Makes them nigh unreadable.

Thought I'd toss that out there.

I'm already trying my best to convert them to Markdown best as I can... Image tags should actually be converted over to the new syntax... Strange.

Made the conversion a bit more forgiving and reloaded the data. How's it like this?

From a quick check, it looks like most of the news post/report stuff is good... just has the tag text issue still. (reference: http://staging.darkjedibrotherhood.com/news/19791)

Only other thing I've noticed is the
tag on medal/promo reasons from the "Awards" tab and "DJB History" tab. (reference: http://staging.darkjedibrotherhood.com/members/84/award_events/5)

Other than that, it looks good as far as data conversion goes. Big difference from the earlier release, which is awesome. Both medals/promos show up fine when I check via the "Events" history (no stray html, though they lack doublespacing, which isn't a big deal) (reference: http://staging.darkjedibrotherhood.com/events)

Can't think of anything else to check re: this particular issue. Hope that helps.

You do know that
by itself is not valid (X )HTML right? I'll add an exception to the conversion script for that one... as for , there's no support for presentation markup (as opposed to content structure markup that eventually leads to a certain presentation) in Markdown, and adding it feels a bit... wrong... I'll see what I can do though.


edit: accidentally an X

Added some support for centering elements, and will fix existing reports next conversion round (or maybe do a separate intermediate conversion for just the reports and news posts). ARE YOU HAPPY NOW? lol

You do know that
by itself is not valid HTML right? I'll add an exception to the conversion script for that one... as for , there's no support for presentation markup (as opposed to content structure markup that eventually leads to a certain presentation) in Markdown, and adding it feels a bit... wrong... I'll see what I can do though.

It's valid, just obsolete, isn't it?

Actually couldn't care less. You guys asked for feedback/bugs. Seeing thousands of
and tags seemed like a bug.

You do know that
by itself is not valid HTML right?

Sure it is.
is a void element. By the spec (even as late as HTML5) void elements MUST not have an end tag, but may optionally include the / character just before the ending > to be compatible with the XHTML self-closing tag syntax.

That said, the
form does look more organized and is less likely to mess up XML parsers

1. http://www.whatwg.org/specs/web-apps/current-work/multipage/syntax.html#start-tags
   http://www.w3.org/TR/html-markup/syntax.html#syntax-elements
   http://dev.w3.org/html5/html-author/#void (I really wish I could find a more recent version of this one)
   [/list:u]

There. fixed my post.

~J

Actually couldn't care less. You guys asked for feedback/bugs. Seeing thousands of
and tags seemed like a bug.

Yeah, it was a bug. I wasn't aware the converter didn't pick up
tags (it did work for
, fixed it now. will be converted properly next conversion round too

There. fixed my post.

~J

I'm content with this