Last modified: 2013-05-26 14:13:20 UTC
<section> tag name collides with HTML 5 <section> tag, thus should be renamed - suggesting <sect> instead...
Why do we care? Wikitext is not html.
Actually, inspired by the documentation, I think <sectioninclude> or <includesection> as complement to wikitext include tags seems to be even better way than my original suggestion. (In reply to comment #1) > Why do we care? Wikitext is not html. But you can enable HTML tags. And <section> is quite important one.
HTML5's <section> is something I'd really like to support. Though at the same time I don't want to just break all the wikis currently who have already been using LST with the previous tag name. It's a bit of a hack but I did think of one way to handle this. In HTML you use: <section>...</section> In LST you use: <section begin=... /> This is actually perfect. An opening/closing tag has no meaning in LST. And we don't support self-closing non self-closing elements in WikiText (if you write <div ... /> it just gets escaped and output as plaintext). So it might be a tiny little parser hack but it would be possible (even if we recommend LST users to change their wikitext to use a new name) to make HTML5 section and LST section to work on the same wiki.
(In reply to comment #3) > It's a bit of a hack but I did think of one way to handle this. > In HTML you use: <section>...</section> > In LST you use: <section begin=... /> > > This is actually perfect. An opening/closing tag has no meaning in LST. And we > don't support self-closing non self-closing elements in WikiText (if you write > <div ... /> it just gets escaped and output as plaintext). Ugh. Since when we don't support self-closing elements? > So it might be a tiny little parser hack but it would be possible (even if we > recommend LST users to change their wikitext to use a new name) to make HTML5 > section and LST section to work on the same wiki. It's quite easy to run bot on all wikis to rename the tag and then drop its original meaning in favour of HTML5.
(In reply to comment #4) > (In reply to comment #3) > > > It's a bit of a hack but I did think of one way to handle this. > > In HTML you use: <section>...</section> > > In LST you use: <section begin=... /> > > > > This is actually perfect. An opening/closing tag has no meaning in LST. And we > > don't support self-closing non self-closing elements in WikiText (if you write > > <div ... /> it just gets escaped and output as plaintext). > > Ugh. Since when we don't support self-closing elements? I didn't know either. Until I saw someone add a parser test for that behaviour. Though it looks like en.wp doesn't work that way right now. Either that's tidy screwing around Either way <section /> in html is meaningless. There wouldn't be any harm in letting LST have it. > > So it might be a tiny little parser hack but it would be possible (even if we > > recommend LST users to change their wikitext to use a new name) to make HTML5 > > section and LST section to work on the same wiki. > > It's quite easy to run bot on all wikis to rename the tag and then drop its > original meaning in favour of HTML5. That assumes that every single wiki using LST knows how to use bots and how to do this replacement properly. Bots are not simple to use. Frankly I know how to use them and it would be really annoying for me to have to do that if I still use LST.
