.
Good for everything 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 ;)
Putting in titles for day-entries helps finding back things easier. New day-entries below this line, please.
2007-Apr-14#
I'm not sure where to put this, so I'll mention it here. So far we have focussed on making Creole easy for the users to write in and relatively easy to parse (mainly convert from Creole to HTML and other markups). But there is also a second aspect, one that also is an indication of how clear and well defined the language is: the possibility and ease of converting to Creole from various popular markups. This will be needed to migrate wikis. It will be needed for wiki engines that use WYSIWYG editors. It's also a good test on how well defined and streamlined the markup is. Note that this doesn't mean that Creole should have all features that HTML offers, of course.-- Radomir Dopieralski, 2007-Apr-14
Escape characters will help there (see Nyctergatis sandbox with Creole output).
-- YvesPiguet, 2007-Apr-14
Not if they use "heuristics" or come together with insane markup -- then you'd have to escape practically every "hot" character, making the result totally unreadable for humans.
-- Radomir Dopieralski, 2007-Apr-14
2007-04-04#
I like pie, but I'm a little concerned about the sampling of wiki engines used to make those charts. I noticed that every chart uses a different set of wiki engines to compare against -- what are the rules of choosing them? Shouldn't the sample set be uniform?I started making the No Wiki Markup Comparison and I understand perfectly how hard it is to collect information about markup on wikis -- that's why I'm listing the engines that are on WikiMatrix, but that I failed to collect information about (they lack documentation, their site is down or otherwise unusable, they only use a WYSIWYG editor).
I know that the collected statistics are not biased on purpose and that it's technical and/or organisational difficulties that rule the choice of engines, but at the same time I think we should play it safe and don't lie when we don't have full info.
-- Radomir Dopieralski, 2007-Apr-04
Thanks Radomir. Yes, the charts should be uniform. And if it is impossible for some reason (e.g. because some engines don't support some markup) there should be at least an explanation why the charts are not uniform. Chuck, could you add this please?
-- Christoph Sauer, 2007-Apr-10
2007-02-25#
Gregor Hagedorn I found this resource today and looked through it, being a content rather than system person. I like the ideas and hope this wins more support. I do not understand what is intended with Placeholder on Creole 0.5, please elaborate. I wrote Levels of Interoperability, please someone link it in - or ignore if out of scope - I cannot find a good parent place. I wrote a list of some markup wishes and comments on my personal page.
2007-02-22#
Christoph Sauer Dear creole parser developers. We have proposed a HyphenListMarkupProposal. I know that it is quite yet another change, but I think it's crucial. Please read through it carefully before you rant at me, because that was Chucks first response as well ;). I consider this as an important decision towards a Creole version 1.0. If we have sorted this out I feel pretty much that we are through.My personal todolist/whishlist towards a Version 1.0
- getting through the HyphenListMarkupProposal discussion.
- general escape character (clarify usage of spaces before elements), see Escape Character Proposal
- clarify the usage of placeholder, discuss separate markup for placeholder and plugins/extensions/macros (term is engine specific) see confusion in Remove Placeholder Proposal.