(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-43) was last changed on 26-Sep-2007 09:06 by ChuckSmith  

This page was created on 29-Aug-2006 01:46 by 85.221.141.46

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Difference between version and

At line 97 changed one line
Don't see creole as a standard repleacing your markup, please. Take a look at the [Implementation] alternatives, like the "extra creole edit button", that will keep your markup completely seperate from creole. This button will make wikis inviting for people that might be an asset to communities using your engine, but don't know your markup.
Don't see creole as a standard replacing your markup, please. Take a look at the [Implementation] alternatives, like the "extra creole edit button", that will keep your markup completely separate from creole. This button will make wikis inviting for people that might be an asset to communities using your engine, but don't know your markup.
At line 105 added 10 lines
The main difference between headings and inline emphasis is that headings create structure of your document, labeling its parts, while inline emphasis merely distinguishes part of the paragraph text. Again, the presentation of both is out of the user's control, as it is defined in the style. Headings can, for example, be totally hidden and only appear in the table of contents. Emphasis, as Thomas mentioned, can be done using foreground or background colors, different font, different font style, weight, variant, size, decoration, even position.
If you insist on consistency between the {{{//}}} and {{{**}}} markup and its presentation on the rendered page, then the markup is purely visual, not semantic, and visual formatting tags, like {{{<i>}}} and {{{<b>}}} should be therefore used instead of {{{<em>}}} and {{{<strong>}}}.
I think it's a question of decision whether the markup is visual or semantic. Once this is decided, the rest is easy to sort out.
Note that indeed "semantic" markup requires some dose of "symbolic" thinking, which people learn pretty late in their life. If you are catering to kids and young teenagers, "visual" markup is much easier to introduce, while the idea of "semantic" markup might be even impossible to explain.
-- [RadomirDopieralski], 2006-09-14
Version Date Modified Size Author Changes ... Change note
43 26-Sep-2007 09:06 13.375 kB ChuckSmith to previous restore
42 26-Sep-2007 01:00 13.415 kB 218.58.136.4 to previous | to last
41 26-Sep-2007 00:59 13.404 kB 59.45.211.51 to previous | to last
« This page (revision-43) was last changed on 26-Sep-2007 09:06 by ChuckSmith