623
edits
PhoenixGraphix
Joined 5 March 2008
removed typo as per invitation; see User_talk:Tmwps#For_a_person_that_hates_misspellings...
(removed typo as per invitation; see User_talk:Tmwps#For_a_person_that_hates_misspellings...) |
(removed typo as per invitation; see User_talk:Tmwps#For_a_person_that_hates_misspellings...) |
||
| Line 575: | Line 575: | ||
<h2>Grr, <span class="explain" title="and all variants">Wikicode</span>...</h2> | <h2>Grr, <span class="explain" title="and all variants">Wikicode</span>...</h2> | ||
If you don't know yet, I HATE <span class="explain" title="and all variants">Wikicode</span>. No offense to anyone, but I hate it with a vengeance. Personally, I'd much rather just be able to use HTML and CSS. Bulbapedia isn't bad with its support of HTML, but it would be much easier if it would parse for the img and a tags instead of automatically linking them. No, what really gets me are the sites that support ONLY <span class="explain" title="and all | If you don't know yet, I HATE <span class="explain" title="and all variants">Wikicode</span>. No offense to anyone, but I hate it with a vengeance. Personally, I'd much rather just be able to use HTML and CSS. Bulbapedia isn't bad with its support of HTML, but it would be much easier if it would parse for the img and a tags instead of automatically linking them. No, what really gets me are the sites that support ONLY <span class="explain" title="and all variants">Wikicode</span>, nothing else. I can't blame Bulbapedia for supporting Wikicode, as non-coders are more likely to get interested in learning HTML and related languages. And now for some reasons that I hate <span class="explain" title="and all variants">Wikicode</span>: | ||
<ul> | <ul> | ||
<li>Much too simple and text-oriented, makes it messy and confusing.</li> | <li>Much too simple and text-oriented, makes it messy and confusing.</li> | ||