(anonymous guest) (logged out)

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

Sponsored by the Wiki Symposium and the Nuveon GmbH.

 
View Attach Info

Add new attachment

Only authorized users are allowed to upload new attachments.

This page (revision-67) was last changed on 26-Sep-2007 09:44 by ChuckSmith  

This page was created on 09-Jan-2007 20:54 by RadomirDopieralski

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Difference between version and

At line 472 added 18 lines
I thought about it some more, and maybe it would be easier to find a common ground if we stated the problem that we want solved with the particular change explicitly. Not the "which one is better in general" thing, but what is that one (or several) particular thing that is bad in the established wiki markup that blog-like line breaks fix?
I have basically two problems that (I think) would be solved by changing the Creole's line break handling into wiki-like:
# There is no way to introduce additional, non-meaningful, presentational (for presentation of the raw source, not rendered text) structure in the document raw source, using the line breaks.
This especially affects e-mails and other already formatted, wrapped text, but is also needed for especially long or complicated texts typed directly in the textarea.
# Current syntax encourages sloppy writing, with different style for everyone and no standards for things like lists or headings (both in source and in presentation). Things like "TITLES" and "e m p h a s i s" and "-=(o)=- I like weird bullets".
The first problem could be addressed (with some additional costs) also by some ability to "escape" line breaks, so that they are not meaningful. This increases complexity of the language and still requires special work when including already formatted text. And is non-standard, of course.
The second problem is mainly solved by education of the users and correcting their markup. It can also be helped by chosing certain styles so that the "home-made" formatting sticks out as especially ugly. Introducing "Rules" and forcing the users somehow to abide "The Style Guide" could be also a solution for certain kinds of environments. But I believe that making the "homemade" markup just don't work without additional "yes, I really mean it" syntax is the simplest and most successful solution. Of course, not perfect :).
Sure, you can argue that user freedom is sacred and they have the right to choose -- but what do we need Creole then? :)
PS. It does feel like I'm talking to myself all the time. That'd explain the lack of progress with this issue.
-- RadomirDopieralski, 2007-01-31
Version Date Modified Size Author Changes ... Change note
67 26-Sep-2007 09:44 49.696 kB ChuckSmith to previous restore
66 26-Sep-2007 01:47 49.716 kB 63.241.9.240 to previous | to last
65 25-Sep-2007 23:34 49.696 kB RadomirDopieralski to previous | to last restore
64 25-Sep-2007 19:40 49.72 kB 207.44.238.95 to previous | to last
63 01-Mar-2007 09:06 49.696 kB ChristophSauer to previous | to last typo
62 08-Feb-2007 18:29 49.696 kB YvesPiguet to previous | to last No headings and rules in lists
61 08-Feb-2007 18:07 49.284 kB RadomirDopieralski to previous | to last how do we do it in other contexts?
« This page (revision-67) was last changed on 26-Sep-2007 09:44 by ChuckSmith