(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-13) was last changed on 13-Apr-2007 22:55 by  

This page was created on 02-Apr-2007 12:02 by YvesPiguet

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Difference between version and

At line 55 added 18 lines
Gregor, I agree with you that we need either this, or one of the other things you proposed. Currently I'm in favor of the [[GenericExtensionElementProposal]], but that may be just because it was discussed best so far.
Now, to address your needs, I see several problems and several possible solutions -- these are to start the discussion, not to counter your arguments, mind you. Also note, that there is already [[Superscript And Subscript Proposal]] and that it will likely be included in [[Creole Additions]].
The problem with advanced formatting in links and page names: URLs don't support it! They do support the Unicode alternatives I mentioned in the [[Talk.SuperscriptAndSubscriptProposal]], at least when the engine uses UTF-8. So, Creole would have to specify an algorithm for encoding this formatting into URLs -- which is out of the [[Creole scope]] and poses an additional problem, as not all wiki engines allow the same set of characters in their page names, due to either design decisions or implementation of their storage (think C2). Note how the original wiki swiftly sidesteps this problem by spelling out any advanced markup in page names (CeePlusPlus).
Another problem with advanced formatting -- it's going to be, by necessity, quite elaborate. I doubt your users will me happy writing {{{2m__sup__2__sup__}}}, and I'm pretty much sure they won't be happy reading it. Using Unicode (with some nice way of enabling the users to enter it comfortably in the engine, like buttons or even just a list of them for copy-pasting) is the most readable and portable way. Using a LaTeX-like plugin (not necessarily LaTeX, it may render to normal HTML and use even simplier syntax, custom-crafted for the purpose) is a second-in-order comfortable option, at least in my opinion and limited experience. Compare:
Lastly, things like text alignment, floating of elements, spacing, colors, etc. are the domain of web designers and are best accomplished using styles and style sheets. Sure, a way of inserting a classed div or span would be then handy, but that's hardly core wiki syntax.
-- [[Radomir Dopieralski]], 2007-Apr-05
Version Date Modified Size Author Changes ... Change note
13 13-Apr-2007 22:55 16.905 kB to previous
12 13-Apr-2007 22:46 16.791 kB to previous | to last
11 13-Apr-2007 22:45 16.791 kB to previous | to last
10 11-Apr-2007 23:23 14.391 kB to previous | to last all users would have to learn css
9 11-Apr-2007 22:43 11.36 kB Gregor Hagedorn to previous | to last chem etc. plugin not general enough
8 11-Apr-2007 10:42 10.522 kB RadomirDopieralski to previous | to last <>
7 11-Apr-2007 04:10 9.507 kB Gregor Hagedorn to previous | to last
6 05-Apr-2007 12:19 8.071 kB to previous | to last advanced formatting
5 04-Apr-2007 23:24 5.855 kB Gregor Hagedorn to previous | to last Proposal misunderstood? Definitely NotNew!
4 03-Apr-2007 09:37 2.614 kB ChristophSauer to previous | to last seems not to be quite common, reject
3 03-Apr-2007 09:06 1.636 kB YvesPiguet to previous | to last Agree
2 03-Apr-2007 07:51 1.295 kB to previous | to last -- is out :(
1 02-Apr-2007 12:02 0.693 kB YvesPiguet to last Why not XML?
« This page (revision-13) was last changed on 13-Apr-2007 22:55 by