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".
  • Collision Free
    collisions in the markup Collision with content text is when you type something intending it to be displayed as is but it s being interpreted as part of the markup and interpreted accordingly when this happens you have to EscapeMarkup Collision with existing markup of the wiki in which Creole is being used This is when both the original wiki markup and Creole use the same construct to mean different

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


  • Common Text Elements
    words of which some may require TextEmphasis It s often helpful to structure the pages using HeadingText and HorizontalLine s as well as NumberedList s and BulletList s even if their overuse may be considered BadStyle For technical reasons it s good to have a way to EscapeMarkup or even include whole blocks of PreformattedText also superscript and subscript is very common science and engineering As wikis are hypertext environments they will usually need a way to mark InternalLink s and as they do not exist in vacuum also ExternalLink s Many articles refer to external materials either by just mentioning them often in footnotes or bibliography or by using QuotedText Both need to specify the source Articles and discussions often benefit from IncludedFigures both in form of images drawings photographs and in form of mathematical equations diagrams charts and tables maps etc It is not the CreoleScope to enforce any particular style of writing on the user but one is sure stylistically correct text should be possible and easy to create with minimized amount of additional work like fancy formatting or escaping Apart from properly styled text also various notes text in loose informal form common shortcuts and notations

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

  • Extensible By Omission
    search type ahead Recent Searches Clear Extensible By Omission Your trail StricterSyntax Home NewlineSpace Home Talk Goals Home CollisionFree Home CommonTextElements Home View Page Discussion V iew A ttach I nfo When specifying markup we can specify what markup will have a particular effect and what markup will not have any effect If we say nothing at all that markup may have an effect in future releases The specification is extensible by omission because we haven t specified everything Some things have been left undefined to be defined later Example In HTML em and strong elements can be nested If we just specify that foo will result in bold text and bar will result in italic text and we don t specify whether these will nest or not then we are extensible by omission Obviously they don t have to nest right now but they might have to nest in a later revision of the specification Having spent an evening making my parser accept badly nested format this is now part of my creole specification which to be honest has had to make so many assumptions about what is creole and what isn t creole that I m beginning to

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

  • Not New
    Quick search type ahead Recent Searches Clear Not New Your trail NewlineSpace Home Talk Goals Home CollisionFree Home CommonTextElements Home ExtensibleByOmission Home View Page Discussion V iew A ttach I nfo Creole should follow the established traditions and wiki practices whenever possible There are several sources from which we can draw Existing wiki engines and their markup Various rich text formats like StructuredText ReStructuredText Markdown OLPC document format even languages

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

  • Fast To Type
    nfo Fast to type doesn t always mean short It usually means that you should AvoidSpecialCharacters that are not available on the keyboards easily and make it ReadableMarkup so that the user doesn t have to slow down to check if what he has written is what he means The need for excessive escaping of text can slow down typing considerably so it s good if the markup is CollisionFree

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

  • Readable Markup
    iew A ttach I nfo The markup should not hinder reading of the RawText of the page Only characters rarely used in normal text should be used for markup When a common character is used like a dash or a slash it shoudn t be used alone by itself Escaping should be rarely necessary The markup should be visually separated from the content text it should be obvious what is

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

  • Easy To Learn
    Learn Your trail CommonTextElements Home ExtensibleByOmission Home NotNew Home FastToType Home ReadableMarkup Home View Page Discussion V iew A ttach I nfo The markup should be easy to learn both by exploring existing documents and comparing them to RenderedPage and reading the manuals The rules should be consistent similar constructs should be created in similar way The characters used should be related to the function they perform in some way

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

  • Easy To Teach
    Your trail ExtensibleByOmission Home NotNew Home FastToType Home ReadableMarkup Home EasyToLearn Home View Page Discussion V iew A ttach I nfo The markup should be easy to describe and explain This requires it to be EasyToLearn but also places some additional requirements The concepts used should not be new but also they shoudn t be overly advanced e g using CSS within RawText to style elements seems a little too

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



  •