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".
  • Talk.Good Practices
    WikiToolkit Home WikiPopularity Home View Page Discussion V iew A ttach I nfo I took that out of the page and into the discussion here because I am not shure if this is not out of the CreoleScope The only term for the markup page which is generally used is Text Formatting Rules across wikis as shown on List of Wiki Markup so we would suggest as a GoodPractice to

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


  • Good Practices
    reserved license BY SA Sponsored by the Wiki Symposium and the Nuveon GmbH view find Quick search type ahead Recent Searches Clear Good Practices Your trail Home PhpWiki Home LiferayPortal5 0 Home WikiToolkit Home WikiPopularity Home Talk GoodPractices View Page Discussion V iew A ttach I nfo Add new attachment Only authorized users are allowed to upload new attachments This page revision 23 was last changed on 26 Sep 2007 09 44 by ChuckSmith This page was created on 23 Sep 2006 18 43 by null Only authorized users are allowed to rename pages Only authorized users are allowed to delete pages Incoming links Good Practices Block Markup Notion Criticism Home Left Menu Talk Change Linebreak Markup Proposal Talk Creole 0 2 Talk List Markup Alternatives Talk Make The Machine Work Harder Talk Reasoning Talk Yaroslav Stavnichiy Outgoing links GoodPractices Ambiguities AvoidSpecialCharacters AvoidTextTags CheatSheet CollisionFree CommonTextElements CommonThingsPeopleNeed CommonWikiParsingTechniques Creole EasyToLearn EasyToTeach EdgeCases ExtensibleByOmission FastToType Goals HintsOnExtending InternationalizationConcerns MakeTheMachineWorkHarder NonDestructive NotNew ReadableMarkup Pagination Previous 1 2 all Total items 23 Version Date Modified Size Author Changes Change note 23 26 Sep 2007 09 44 1 428 kB ChuckSmith to previous restore 22 26 Sep 2007 01 45 1 463 kB 80

    Original URL path: http://wikicreole.org/PageInfo.jsp?page=GoodPractices (2016-02-11)
    Open archived version from archive

  • Creole
    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 Your trail PhpWiki Home LiferayPortal5 0 Home WikiToolkit Home WikiPopularity Home Talk GoodPractices Home View Page Discussion V iew A ttach I nfo Creole is the name of a common markup for wiki engines It s not intended to replace existing markup but to be

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

  • Common Things People Need
    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 Common Things People Need Your trail LiferayPortal5 0 Home WikiToolkit Home WikiPopularity Home Talk GoodPractices Home Creole Home View Page Discussion V iew A ttach I nfo Concentrating on the common things people need helps us to keep creole simple The KISS principle Keep it simple and stupid We can derive those Common Text Elements from analyzing already available markup but this good practice goes beyond analyzing commonalities in existing markup variants We also can derive it from material that where created by users and researchers in an effort to improve usability Usability reports and papers for example provide us with feedback how end users outside the domain of programming and IT actually use markup and what their problems are Here s a list of articles reports and initiatives that help us find the common things people need Are Wikis Usable PDF by Alain Desilets Sebastien Paquet Norman G Vinson Proceedings of the Wikisym 2005 Wikipedia Spickzettel PDF Cheat Sheet for the MediaWiki Markup Cheat sheets created by users show us what

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

  • Edge Cases
    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 Edge Cases Your trail WikiToolkit Home WikiPopularity Home Talk GoodPractices Home Creole Home CommonThingsPeopleNeed Home View Page Discussion V iew A ttach I nfo An example for an edge case is a minus sign at the beginning of a line A counterexample is the use of bold as the first markup in a list item just take a look at the formatting on this example page http www c2 com cgi wiki WikiDesignPrinciples This is quite common and therefore not an edge case Programmers tend to give users all the options a user could possibly want making it really difficult for a user to actually find what they want Extensive menus of word processors are good examples of this What is the most important thing to the average computer user They want their machine to just work Why does Google know how to correctly translate a United Parcel Service tracking number while the actual UPS website requires multiple entries just to get to the point where the tracking number can be entered A two

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

  • Internationalization Concerns
    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 Internationalization Concerns Your trail WikiPopularity Home Talk GoodPractices Home Creole Home CommonThingsPeopleNeed Home EdgeCases Home View Page Discussion V iew A ttach I nfo Creole is supposed to be used all over the Internet to write in many languages using many scripts by many users using various software and hardware It s important to not create additional obstacles for people who use different setups than we We should AvoidTextTags as they only have meaning in one language Translating the tags is not always possible and creates more problems especially in multilingual wikis Another important fact is that there are many different Keyboards with different layouts and not all characters are easily accessible for all users Therefore we must AvoidSpecialCharacters in order to make markup FastToType also for people with different keyboard layouts than ours WikiWord s used to form links are pretty useless in scripts that don t have the notion of lower and uppercase letters Reading direction also varies for different scripts so care must be taken to not use any directional constructs

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

  • Common Wiki Parsing Techniques
    iew A ttach I nfo Braindamaged substitution This is the simplest parsing method used by some scratch wikis and write a wiki in minimal number of lines of code engines It s pretty easy to uderstand and implement in any language that supports regular expressions but is very limited and not guaranteed to produce valid html Still it works most of the time The idea is to apply a number of regexp subtitutions s amp s lt s gt s p s p s n s n p p s n hr s n p h1 1 h1 p s n p h2 1 h2 p s n p h3 1 h3 p s n s s p ul li 1 li ul p s n s s p ul li ul li 1 li ul li ul p s n s s p ul li ul li ul li 1 li ul li ul li ul p s n n p pre 1 pre p s code 1 code s em 1 em s strong 1 strong s w a href wiki 1 1 a s w a href wiki 1 2 a s http a href 1 1 a s http a href 1 2 a s p p s li ul ul li s li ul ul li s li ul ul li You get the point This technique has a number of drawbacks no mixing of bold italic no markup inside lists headings etc no mixing of list types unless a large number of regexps is introduced to accommodate them like n etc limited number of headings and list levels impossible or extremely hard to accommodate special cases like the n br in paragraphs only or the list bold special case impossible to distinguish different levels

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

  • Make The Machine Work Harder
    to verify a concealed entry and avoid losing system access This is close to poka yoke so it s OK Similarly if the input files are to be heavily edited by various people then it s good to keep them readable by restricting markup syntax stripping formatting markup added by word processing bloatware etc Of course such a strict syntax should be paired with validation and a good non destructive way of indicating errors This is a good practice use your computation power to ease the use of markup even if that complicates your parser Users will be grateful for a forgiving parser unless they have to become more forgiving for other sloppy users too as a result There are also some pieces of advice useful for web browser and wiki engine developers When using real time parsers to check syntax make sure they don t interrupt the user s pattern of entry Do mark the error but don t require the user to fix it right then Never throw formatting errors unless the user s meaning is ambiguous and only then when the system needs non ambiguity For example phone numbers read by people can be ambiguous while auto dialed ones should not Where entries must be unambiguous e g entering credit card numbers parse the input and auto correct all unambiguous exceptions e g dropping non numerics switching to all uppercase etc For ambiguous exceptions calculate the exception level in the parser and display a likely guess of the correct entry For example a user entering a two digit birth year probably means one in the past 100 years a reservation is probably in the next 100 years and a food safety date is probably within 50 years either way Never EVER lose or discard a person s

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



  •