(anonymous guest) (logged out)

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

Sponsored by the Wiki Symposium and the Nuveon GmbH.

 
This is version . It is not the current version, and thus it cannot be edited.
[Back to current version]   [Restore this version]

Good for all likely not of importance anymore in two days

You can always move interesting conversations to a page with an appropriate title later. It's a wiki ;)

Entiteling day-entries helps finding back things easier. New day-entries below this line, please.


2007-02-06 Spicing things up#

RadomirDopieralski: As Creole matures, it starts to attract more attention. Soon we will have to direct our efforts more on advertising it and developing various plugins and converters than developing the standard.

This brings us to the topic of looks. It didn't matter at the beginning, but I think that we should improve the looks of this wiki a little, to give it impression of silidness and professionalism, and maybe even design some kind of good logo for Creole, for those little banners (colophons?) and "edit with Creole" buttons, so that the users will immediately know that they can use Creole on particular site.

If yuo don't mind, I'll try and prepare some style sheet for this wiki. We can also think about making a LogoContest soon.

2007-01-23 How to handle invalid bold/italic#

WankerRoot: Hi there, the Creole0.3 specs says that such bold/italic mixes are "unacceptable": //**bold-italic//**. But - how shall the interpreter handle it? I was unsure so I decided for PodWiki to correct the invalid code and render it anyhow, Here is how it looks. My question is: is this the intended way to handle this? Any comments? - kind regards.

RadomirDopieralski: I don't think there is one and only good one way of handling such malformed markup -- and I think that different parsers will handle it differently. The important thing to remember is to never just ignore characters and eat them silently. So there are a few options: 1) Ignore the markup and display the characters verbatim, indicating this way that something is wrong with them, 2) First "//" starts italics, first "**" starts bold, then there is the text "bold-italic", then: 2.1) second "//" ends both the bold and the italic, second "**" starts a new bold span, that ends with the end of paragraph, 2.2) second "//" is treated as normal text (as there is no active italic span to close), second "**" closes the bold span, the rest of text is italic until the end of paragraph. 3a) only "//" are treated as markup, "**" is treated as normal text, 3b) the other way around, only "**" are treated as markup, "//" is treated as normal text, 4) your parser uses some heuristics and properly guesses what the user meant. To my understanding of the Goals, especially there is no wrong way to implement Creole, each of these approaches is correct.

2007-01-22#

SteffenSchramm: Hello. I updated the creole filter to support LineBreaks in blog-style. Please test if everything is ok, and whether the linebreaks work. You can use this as a test to see if you like blog-style linebreaks better.

ChristophSauer: Steffen, I installed the previous version again, since the new one messed up the commentboxes. It's not a good Idea to test the filter in this wiki anymore, and I guess it never was - my fault. I've installed a sandbox wiki now where we can install and test the latest Creole pagefilter: http://www.wikicreole.org/creole-sandbox

2007-01-13#

ChristophSauer: Updated the creole filter and activated it again. After some problems I hope we finally got it to work. Some markup still is not working as expected. But I don't want to wait no longer. You should finally be able to use Creole on the creole wiki as well. We are late, could have put more effort on it earlier. Thanks Steffen for the implementation. If you have trouble with it, report it on the CreoleFilterError page or let me or SteffenSchramm know.

2007-01-09#

RadomirDopieralski: I did a little cleanup, moved parts of discussions into relevant "proposal" pages and apropriate talk pages. I hope this will help to keep things in order. I also linked from the Versions page to the proposals discussed for particular version. Should we also refactor the discussions into "rationale" descriptions on the Elements pages? They have grown to sizes impossible to catch up to for new readers.

2006-12-10 / About PukiWiki#

Please refer to the following links for the syntax of PukiWiki:

2006-09-23#

RadomirDopieralski: We are making some progress, and receiving some feedback, but it seems to be pretty disorganized. In particular, it's hard to find rationales and explanations behind the decissions, as well as proper discussions on alternatives. I'm afraid that we will end up with some markup format, and not much more.

That's why I'd like to start creating some GoodPractices descriptions related to creating markup language for wikis in particular, and (maybe) text markup languages in general.

If each new proposition, recommendation, good practice, etc. is on a separate page, then it's easier to document it's pros and cons, interactions with other parts, discussion.

I'm not sure if this wiki is a good place to do it, but we can try. I'm a little afraid of clashes with existing pages on this wiki, and of "hijacking recent changes" -- after all it would be nice to just look at RC here and see what's new in the draft.

What do you people think? Would you be interested in such a wiki? Maybe somehting like this already exists?

ChristophSauer: Good Idea. I think this wiki would be a good place to put it, and actually Ward also mentioned this idea of BestPractices. If we have more implementations I would like to set up a student research project that would test the usability of creole in non technical faculties. They then could use and extend those GoodPractices for creole. Let's keep it here and see how it works out. Let's keep the efforts focused on one wiki for now. I would not be too afraid of hijacking RC. If people are interested in a particular set of pages, for example how the standard is evolving, they can use the individual RSS feeds of every page to compile their own RC through their blogreader.

2006-09-07#

ChristophSauer: Just added an interwiki link to ohanawiki.net - you can shortcut links to pages there with prefixing your link like this [[Ohana:WikiPrinciples]]

Add new attachment

Only authorized users are allowed to upload new attachments.

« This particular version was published on 06-Feb-2007 13:25 by ChristophSauer.