archive-org.com » ORG » W » WIKICREOLE.ORG

Total: 1035

Choose link from "Titles, links and description words view":

Or switch to "Titles and links view".
  • Creole 0.6 Poll Archive
    rules B C s D E F YvesPiguet 1 2 5 4 2 1 Axel Rauschmayer 1 1 1 1 3 5 Gregor Hagedorn 1 1 5 4 2 1 Michele Tomaiuolo 1 2 4 5 4 1 Footnotes A As in Creole 0 5 weakly defined B As in Creole 0 5 but with disambiguation rules for bold e g no bold at the beginning of a line in the context of a list C One or more stars at the beginning of a line followed by at least one space can be mixed with D One or more stars with leading spaces ignored followed by at least one space can be mixed with E One or more hyphens at the beginning of a line followed by at least one space can be mixed with F Single hyphen followed by at least one space leading spaces used to indicate the nesting level hyphen replaced with for numbered lists Where are those alternatives G One or more stars at the beginning of a line no space required afterwards In fact could be A but would be clearer This is B YvesPiguet H One or more hyphens at the beginning of a line no space required afterwards Further information ListMarkupAlternatives Escape character 1 strongly disagree 2 disagree 3 don t care 4 agree 5 strongly agree Name None tilde any tilde nonalphanum tilde Creole markup excl pre block tilde Creole markup incl pre block other esc char Postpone to 0 7 YvesPiguet 2 4 5 1 1 3 2 Axel Rauschmayer 5 1 1 1 1 1 1 Gregor Hagedorn 2 5 1 1 1 1 1 Michele Tomaiuolo 2 4 4 1 1 5 1 None still leaves us plain text nowiki right Axel Rauschmayer Gregor to Axel which sense

    Original URL path: http://wikicreole.org/wiki/Creole0.6PollArchive (2016-02-11)
    Open archived version from archive


  • Creole Markup Collision Analysis
    Some rights reserved license BY SA Sponsored by the Wiki Symposium and the Nuveon GmbH view find Quick search type ahead Recent Searches Clear Creole Markup Collision Analysis Your trail Home ComparisonWithOLPCMarkup Home CorporateUser Home Creole0 6Poll Home Creole0 6PollArchive Home CreoleFilterError View Page Discussion V iew A ttach I nfo I ve done some collision analysis of the wikis at WikiPopularity The results are at Wiki Structural Markup Usage and Wiki Character Markup Usage I ve split this into two pages so that the tables display across the width of a single page The analysis shows the choice of and for bold and italic is collision free for images collides with following wikis MediaWiki for templates Confluence for mono JSP Wiki for mono Wikispaces for mono StikiPad for mono collides with MediaWiki template parameters for headings has two partial collisions TikiWiki where is used for underline DokuWiki where the heading order is reveresed that is is a level 1 heading link text has a partial collision with TiddlyWiki bulleted list has a collision with PukiWiki where it is used for heading numbered list has a collision with Midgard Wiki where it is used for heading has a collision with

    Original URL path: http://wikicreole.org/wiki/CreoleMarkupCollisionAnalysis (2016-02-11)
    Open archived version from archive

  • Creoleparser.py
    External Discussion Promotion Recent Changes Talk Index wiki node Sandbox Copyright C by the contributors Some rights reserved license BY SA Sponsored by the Wiki Symposium and the Nuveon GmbH view find Quick search type ahead Recent Searches Clear Creoleparser py Your trail Home CorporateUser Home Creole0 6Poll Home Creole0 6PollArchive Home CreoleFilterError CreoleMarkupCollisionAnalysis Home View Page Discussion V iew A ttach I nfo The homepage for Creoleparser py has

    Original URL path: http://wikicreole.org/wiki/Creoleparser.py (2016-02-11)
    Open archived version from archive

  • Crossmark Creole Unification
    has more flexibility because it allows raw spans without monospace font styling and vice versa It should also be noted that the Crossmark fourth draft spec contains backslash as an escape character but I don t get the sense this is thoroughly thought through My guess is that it can be simply dropped in favor of the raw macro If left in there would be a collision with the proposed syntax for forced line breaks Since the hybrid has considerably greater collision risk than either source I expect that the use of raw spans to avoid collisions will be fairly common Therefore I would recommend at the very least that the raw span markup be adopted in most Creole only implementations Of course having Creole adopt Crossmark s raw span markup would remove this wart entirely and add a desirable feature CornerCase s yeah baby Headers Crossmark uses a row of equals or dashes to indicate first and second level headers as in Markdown Third and fourth level headers are already compatible Implementing both is not a serious problem but an argument can be made that it is the Crossmark syntax that is warty because of its lack of consistency Going between second and third level headers is a much more major editing operation than in Creole I weakly recommend that Crossmark drop its Markdown style headers but will tolerate both There is also a potential collision between horizontal line syntax and Crossmark second level headers This can be resolved in a number of ways including requiring a blank line before the horizontal line separator but is definitely a wart Lists Crossmark supports both the and 1 syntaxes a la Markdown The only real problem here is the collisions A more fundamental issue is that Crossmark uses indentation to indicate list nesting depth It is possible for a hybrid to implement both schemes with relatively low risk of collision indentation is unmeaningful in the current Creole draft so is unlikely to occur but it s definitely a large wart Macro syntax I m not 100 thrilled with Crossmark s macro syntax For one the single angle brackets collide head on into HTML XML markup and there are quite a number of wikis MediaWiki in particular who support this kind of hybrid For two the preceding colon syntax for block macros doesn t clearly telegraph that the block macro namespace is the same as the inline macro namespace I d much rather have a visual resemblance between the two Thus I suggest double angle brackets as the macro delimiter for both inline and block usage My suggestion for block syntax is math a b I realize that having a block close delimiter is not as Pythonic as the Crossmark draft but I think my suggestion will be clearer for more people Indented blocks Crossmark uses indentation to delimit indented blocks Only one level of indentation is mandated in the draft It s not clear to me what s supposed to happen

    Original URL path: http://wikicreole.org/wiki/CrossmarkCreoleUnification (2016-02-11)
    Open archived version from archive

  • Customization Alternative
    do that for wikitext wikiCreole Instead of or together with promoting a standard source text markup we may promote a background file saving format Then however the text has been typed it will be saved in a standard form which allows any other form for display as well as for edition We may use any kind of format for saving It may even be identical to the present or future wikiCreole markup once made slightly more consistent see http www riehle org wp content uploads 2008 01 a4 junghans pdf It may also be more formal using for instance unique tokens in order to ease and speed up the rendering process It may also be directly transcoded to x html see also STIF Semantic Web project toward a file exchange format but customization not adressed can it be easily implemented If ever this idea sounds not only romantic to your ears please help and improve this section particuliarly as I haven t ever done such a job Here is how thez pb looks to my eyes after a brief exploration case of wikitext on a remote server Not only an encoding decoding extension is needed for the editor but there may be several syntax variants and also the parameters have to be saved somewhere There may be be several norms for a user to choose when about to edit the site s own dialect standard Creole a local Creole variant e g using tokens closer to the local dialect the user s own preferred norm The three first cases lie at the site level About the last one a preference file could be uploaded or if the user is a registered member of the wiki it may be stored together with his her profile Anyway it s at most a few hundred bytes of plain text Then remains the question of encoding and decoding from to the saving format The specification itself is the job of the people who promote a standard but delivering tools to help complying with it helps much a parser Still if the format is clear coherent its parsing will be highly easier This is especially true I guess if the saving format specifies only semantic classes using only semantics Some of the people who promote text structuring markup standards not only for wiki express the opinion that such a language should only specify the semantics of the structure To do this not only the language specification must avoid using words who evoke styles bold but the html transcoding must not specify any concrete styling b This requirement is achieved by specifying only semantic classes instead whose names or IDs can be clear unambiguous and functional For instance litteral block of text nowiki unprocessed important segment of text or simply highlighted but better avoid x html vocabulary link or pointer target anchor note or reference The above examples don t pretend to be good Just for lauching your imagination Still it should be much easier to

    Original URL path: http://wikicreole.org/wiki/CustomizationAlternative (2016-02-11)
    Open archived version from archive

  • Deleted Page
    Changes Talk Index wiki node Sandbox Copyright C by the contributors Some rights reserved license BY SA Sponsored by the Wiki Symposium and the Nuveon GmbH view find Quick search type ahead Recent Searches Clear Deleted Page Your trail Home CreoleFilterError CreoleMarkupCollisionAnalysis Home Creoleparser py Home CrossmarkCreoleUnification Home CustomizationAlternative Home View Page Discussion V iew A ttach I nfo Refering Pages Camel Case Link Didi Wiki Eltc 4 Tacel Erchi

    Original URL path: http://wikicreole.org/wiki/DeletedPage (2016-02-11)
    Open archived version from archive

  • Discussion Comment.jsp
    don t forget the fritter How come this page never gets locked I guess this has already been discussed but why isn t editing restricted to registered users Seems that most real contributions are from registered users except when we forget to login sorry to discuss that here but it ll be one less page to remove if I don t create the Discussion page YvesPiguet 07 Feb 09 I guess that it s because this is a wiki and we are want the process of designing the standard as open as possible There is already a huge barrier to entry as we could observe recently catching up with all the discussions that accumulated here Besides if you look closely at these spam edits you ll notice that they all come from registered users And different each time The next solution would be to make users jump through adidtional hoops in order to create an account Or disable account creation entirely which in practice amounts to the same thing Once you start putting up fences there is no end to it until you dig an atomic bunker in your backyard Personally I don t mean all this spam much it

    Original URL path: http://wikicreole.org/wiki/DiscussionComment.jsp (2016-02-11)
    Open archived version from archive

  • EBNF Grammar For Wiki Creole 1.0
    Recent Changes Talk Index wiki node Sandbox Copyright C by the contributors Some rights reserved license BY SA Sponsored by the Wiki Symposium and the Nuveon GmbH view find Quick search type ahead Recent Searches Clear EBNF Grammar For Wiki Creole 1 0 Your trail CrossmarkCreoleUnification Home CustomizationAlternative Home DeletedPage Home DidiWiki Discussion DiscussionComment jsp Home View Page Discussion V iew A ttach I nfo Renamed to EBNF Grammar for

    Original URL path: http://wikicreole.org/wiki/EBNFGrammarForWikiCreole1.0 (2016-02-11)
    Open archived version from archive



  •