(anonymous guest) (logged out)

Copyright (C) by the contributors. Some rights reserved, license BY-SA.

Sponsored by the Wiki Symposium and the Nuveon GmbH.


Add new attachment

Only authorized users are allowed to upload new attachments.

This page (revision-45) was last changed on 26-Sep-2007 08:56 by ChuckSmith  

This page was created on 11-Apr-2007 10:38 by ChuckSmith

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Difference between version and

At line 13 added one line
* [[Gregor Hagedorn]]: asterisks are massively more popular on wikis and feel natural. And I still do not understand why the problem of leading double-asterisks also being bold can be solved by using list-hyphens, which have the problem of leading double (signature, m-dash) and quadruple hyphen (horizontal rule). I feel the problem largely goes aways by requiring a blank after bullets, and disallowing a blank after opening bold/strong (e.g. TWiki works that way, and it works well). But I am //not// a programmer.
At line 22 added one line
* [[Gregor Hagedorn]]: **strongly** Wikis are about ease of use. Blank after bullets is readable, no-blank looks like Perl-code. Introducing two alternative markups, which really look different and which every user must learn (because not only personal preference counts, also other peoples preference counts) makes markup learning curve significantly steeper.
At line 24 added one line
At line 37 added one line
* [[Gregor Hagedorn]]: **moderately** Wikis are about ease of use. Wikis supporting CamelCase will absolutely require a single-character escape. Nowiki markup is quite laborious, when one has to remove all the wrongly-interpreted markup from a page. In my experience, e.g. technical xml-schema discussions running on TWiki easily will have a few dozens on a page that need to be escaped (both CamelCase, and html-enabled, thus all xml/html reserved characters must be escaped or replaced with entity. JSPWiki with CamelCase and html turned off is much better of course.
At line 60 added 2 lines
(Problem with Poll: Where has the pre-block gone to? Gregor)
At line 73 added 7 lines
* [[Gregor Hagedorn]]:
** (a) **strongly** Call the block nowiki-monospace "pre", because by preserving whitespace it has additional properties.
** (b) **moderately** Use same markup (e.g. triple braces) for inline nowiki-monospace (e.g. xhtml:tt). So far like Creole 0.5. This seems more consistent than switching to different formatting here.
** (c) **strongly** provide content authors with a solution for dealing with **their** problems that their content is erroneously considered markup by wiki - I believe there is too much discussion here what programmers think the expected content will look like, what they "probably" want. I believe it won't work, the world is bigger! Do you know what field codes ecologists invent and want to talk about? The important need here will be to allow formatting running through the part erroneously escaped
*** (c1) I prefer an easily memorizable solution, i.e. reserving double-brace for non-formatting no-wiki
*** (c2) I prefer an additional escape character for ease of use, based on my experience with Wikis.
*** (c3) I can live with either an inline non-formatting nowiki, or an escape character (rather than both).
At line 83 added 2 lines
At line 92 added one line
* [[Gregor Hagedorn]]: **weakly** - but together with a general solution for advanced formatting options like super/subscript, color, highlighting, etc.
Version Date Modified Size Author Changes ... Change note
45 26-Sep-2007 08:56 13.328 kB ChuckSmith to previous restore
44 26-Sep-2007 00:52 13.342 kB to previous | to last
43 24-Apr-2007 20:25 13.328 kB ChristophSauer to previous | to last escape characters should be core.
42 23-Apr-2007 17:42 13.469 kB YvesPiguet to previous | to last minor precision
41 23-Apr-2007 00:44 13.455 kB YvesPiguet to previous | to last Yves' opinion
« This page (revision-45) was last changed on 26-Sep-2007 08:56 by ChuckSmith