(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-2) was last changed on 11-Jan-2007 21:55 by RaphLevien  

This page was created on 01-Jan-2007 06:42 by 71.132.129.68

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Difference between version and

At line 3 changed one line
I am using Creole as the basis for the markup language in [Barghest], which is the content management system under development for ghilbert.org, a site for hosting machine-verifiable mathematical proofs. I am also developer of Advogato, and have been hacking on typesetting and publishing systems for over 20 years.
I am using Creole as the basis for the markup language in [Ghestalt], which is the content management system under development for ghilbert.org, a site for hosting machine-verifiable mathematical proofs. I am also developer of Advogato, and have been hacking on typesetting and publishing systems for over 20 years.
At line 9 changed one line
* I'm in favor of newlines in the source ''not'' resolving to <br /> tags. Because my markup will live in text files manipulated by plain 'ol text editors, very long lines to indicate paragraph structure are unpalatable. I'm ok with \\ being the explicit line break markup, but will have to move away from backslash as an escape character to accommodate that.
* I think there should be a required space after the initial list bullet, to disambiguate it from bold: [RequireSpaceAfterBulletProposal].
At line 11 changed one line
* I think there should be a required space after the initial list bullet, to disambiguate it from bold.
* I like the {{{|*}}} syntax best for indicating table headers. I see no problem with overloading asterisks in this way - they already mean bold, and tables are special: [Tables].
At line 13 changed one line
* I like the {{{|*}}} syntax best for indicating table headers. I see no problem with overloading asterisks in this way - they already mean bold, and tables are special.
* I'm feeling the lack of an indented block markup. Some content migrating to the Barghest is now hosted on an Oddmuse, which uses an initial colon to indicate indented blocks, much the same as bulleted lists (and with similar logic for nesting). I've added this to Ghestalt as an extension, but also think it wouldn't be out of place in the core. Most of the discussion for this has been in [Talk.Quoting], but it's all over the map. Should we distill the main arguments into a single page, say IndentedBlockProposal?
At line 15 changed one line
* I'm feeling the lack of an indented block markup. Some content migrating to the Barghest is now hosted on an Oddmuse, which uses an initial colon to indicate indented blocks, much the same as bulleted lists (and with similar logic for nesting). I'll likely add this to Barghest as an extension, but also think it wouldn't be out of place in the core.
* I see no reason to change italics (emph) and bold (strong) from the 0.3 spec. I also have no real need for underlining or strikethrough. Subscript ''is'' part of the markup on metamath.org, which is another source of content being adapted to the Barghest, but most of that will end inside mathematics markup, so it's not feeling urgent: [Change Italics Markup Proposal] and [Subscript].
At line 17 changed one line
* I see no reason to change italics (emph) and bold (strong) from the 0.3 spec. I also have no real need for underlining or strikethrough. Subscript ''is'' part of the markup on metamath.org, which is another source of content being adapted to the Barghest, but most of that will end inside matematics markup, so it's not feeling urgent.
* "\}}}" or "~}}}" as escape within block pre markup: [Talk.PreformattedAndNowiki].
At line 19 changed one line
I'm looking forward to participating in the discussion here, and offering code and other help to other Creole developers.
* No extra markup for inline quoting [Talk.Quoting] and [Talk.WikiMarkupHasPresentationFlavor]; this discussion should probably be distilled and refactored, say to InlineQuotingProposal.
All that said, I'm also very worried about the gratuitous incompatibilities with [Crossmark]. I feel strongly that some attempt should be made to reconcile the two efforts, because they really do have similar goals, and having stuff break horribly when cutting and pasting between the two would be a disservice to the world. The order of link and label within [Links], in particular, has the potential to be a rerun of the 0x08 vs 0x7F debate for the code for the "backspace" key.
Version Date Modified Size Author Changes ... Change note
2 11-Jan-2007 21:55 2.539 kB RaphLevien to previous consolidate my recommendations here
1 01-Jan-2007 06:42 2.004 kB 71.132.129.68 to last introducing myself
« This page (revision-2) was last changed on 11-Jan-2007 21:55 by RaphLevien