From: Adam S. <ad...@pe...> - 2001-11-27 22:33:51
|
> Ooph. {{{text}}} is ugly. yep. maybe |text| or will that mess with table rendering? or >text< i'm just trying to think of what could be used. &text& or %text% none are particularly intuitive. at least ``text`` kinda fits in with past schemes though it also lends to confusion since most people are bad at spotting the differences and in fact some browser font rendering makes it almost impossible to tell the difference. > Usemod supports <tt></tt>, <b></b>, <i></i>, <em></em>, > <strong></strong>, and also supports the legacy ''italic'' and > '''bold'''. I don't know if there are alternate forms for <tt> (I > don't think so). that would work though i like not having to type html tags. another thought, i don't like the leading whitespace for mono-spaced text at all because it means that "^ *" doesn't begin a list and that's pretty confusing i think. if supporting <tt>text</tt> could mean doing away leading white space for mono that would be great and leading whitespace could stop being significant. > Maybe not. I think the above syntaxes could be added without breaking > the older syntaxes (at least not much), so we could have it all. maybe an option to activate old syntax and at some point make the new syntax standard? there's a lot of good thoughts on meatball about wiki syntax ... i think a lot of this stuff has evolved since wiki markup was first invented and certainly the purposes for which wiki's have used do to. another thing i'd really like is an alternate table syntax i stubled across on NiKki (a moin spin off). the way all the wiki's i know of renders tables gets *really* hard to maintain as tables get more complex. if you want an example check this page and edit it: http://www.personaltelco.net/index.cgi/Prism2Card i like the idea of treating tables like lists so you could make a table like this: * table heading ** row one *** column one *** column two ** row two *** etc ... i'm not sure of the exact syntax that NiKki uses and you'd have to make sure that it was able to tell teh difference between lists and tables, but i think it would be *much* nicer to maintain tables that way, and sometimes tables are the only way to effectively present data. on the prism2card page we started with lists and it was visually overwhelming and hard to find the information you wanted (let alone cross reference it with anything else). > It's true that I can't imagine very many circumstances where one would > want monospaced WikiWords. However, I think it's just plain confusing > if italicizing and emboldening behave differently than monospacing. > (Unless the markup gives more specific hints that other magic is going > on, e.g. <code>ThisIsNotaWikiWord</code>.) fair enough. maybe limited support for certain html tags would make sense then? adam. |