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.Bold And Italics
    this can actually be parsed pretty simply all the parser needs to do is to recognize URLs as special This is really easy as the problematic URLs are very easy for a parser to recognize MediaWiki actually does an excellent job of this when detecting so called freelinks EPAstor The current spec is simply wrong You have to decide Either ignore W3C and use visual markup italic i Or follow W3C and use semantic markup emphasized em Trying to do both doesn t make sense Personally I like semantic more and it also makes more sense for me There is a relation emphasized strong emphasized Thus makes sense doesn t make sense ThomasWaldmann If the one and only truth is that bold and italics are both emphasis one weaker one stronger then you are right But i never thought of these both elements in that way before and as you can see in this discussions from the decisions made by the people at wikisym and from what I hear from endusers they don t agree either Creole will always sound weired in some aspect to native speakers on foreign territory engines But in the end we are all foreigners somewhere So we are all simply wrong and make no sense to someone sometimes Don t see creole as a standard replacing your markup please Take a look at the Implementation alternatives like the extra creole edit button that will keep your markup completely separate from creole This button will make wikis inviting for people that might be an asset to communities using your engine but don t know your markup Christoph 8 Sep 2006 Here s an after thought on this Bold and Italics maybe both emphasis as headings are emphasis too But they are all different kinds of emphasis different kind of display Bold bolder boldest would be the same kind of emphasis like small medium and large heading But with bold and italics the look is different and therefore my mind sorts that in differently Therefore i would like to have a different markup because we distinguish headings from bold italics with different markup as well It is inconsistent if we don t do that with bold and italics Christoph 8 Sep 2006 The main difference between headings and inline emphasis is that headings create structure of your document labeling its parts while inline emphasis merely distinguishes part of the paragraph text Again the presentation of both is out of the user s control as it is defined in the style Headings can for example be totally hidden and only appear in the table of contents Emphasis as Thomas mentioned can be done using foreground or background colors different font different font style weight variant size decoration even position If you insist on consistency between the and markup and its presentation on the rendered page then the markup is purely visual not semantic and visual formatting tags like i and b should be therefore used instead of em

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


  • Talk.Bold And Italics Reasoning
    is the most used symbol to bold text online but it s ALSO used for unordered list s in most wikis That said other marks like mean one thing at the start of a line see headings and something else within text so it s not wholly impossible to do It s astonishing to accept that a slash looks like slanted italics so it is intuitive when there is no precedent for this use and the slash is universally and necessarily used for extremely semantically meaningful categorizing in URLs including every single URL with a slash in it that ever showed up on a TV screen It s unwise in the extreme to overload a character that is already widely used for a wholly different reason at an entirely different semantic level At least overloading stars to mean bold and list item was arguably both syntatic A bad convention like use of slash for italics would prevent its use in extensions of Creole that wanted to add say semantic links or embedded content or whatever Such usage would extend the user s existing understanding of a slash which is to refer to a more specialized version or included item in a hierarchy They would realize that they shouldn t try to use slashes unless they knew that hierarchy exactly as they know for URLs Above all they wouldn t get confused about the that ALREADY EXISTS AT THE FRONT OF ALL URLS where it separates the protocol from the domain See also colon Though two single quotes do look a bit like a double quote both mediawiki and tikiwiki use this convention and where that is true it s dangerous to defy all that data weight and try to invent a new convention The mediawiki use of single quotes for emphasis so that bold italic and bold italic all use the same symbol is perfectly acceptable The tikiwiki convention of bold remains useful for alternate titles even if the mediawiki usage is retained since there are reasons to bold things sometimes that are not alternate titles Therefore use of the title convention could imply some reasonable default behaviour like to automatically create redirect page s to that page with the alternate titles or notify the user that pages with those titles already existed The logic that the underscore was not chosen because that could be confused for underlining is absurd since links normally appear underlined and the title is exactly the text that does normally appear underlined in a link to that page This proposal does not even dealing with underline If it did it would have to deal also with the fact that an alternate title could and should be both bolded to signal it as a title and underlined or linked usually also therefore underlined to the redirect directive itself so it can be changed or its talk page accessed Using one symbol the single quote for the font style choice works well enough in mediawiki and it

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

  • Talk.Bold And Lists Ambiguity
    in Engines is to some old test wiki I left lying around Sorry about that fixing it now RadomirDopieralski 2007 02 23 The PEAR Text Wiki sandbox should work now The two backslashes before the list were taken with all following newlines and interpreted as a single break Dashes for lists are also supported experimentally Very good idea this testing Michele Tomaiuolo 2007 02 23 Why should the penultimate line look like this text does not close see what happens not closing when the bold tags aren t closed Shouldn t it be this text does not close not closing ChrisPurcell 2007 02 23 That d require infinite unbound lookup to parse RadomirDopieralski 2007 02 23 If that s a requirement on Creole parsers it should be specified somewhere After all regular expressions are quite happy to look until the end of the file to see if a tag is closed unbound lookup is only a problem for certain parser classes If it s up to the implementer it should not be in an ambiguity test as a pass fail requirement ChrisPurcell 2007 02 26 I m not as much concerned with the parsers themselves after all even if they can t parse the way that state machines do they usually have a buffer much larger than the page s text available anyways What I m concerned with are the parsing abilities of the users who need to understand the text every time they want to change something in it Having the rendering of something at a beginning of the paragraph depend on appearance of something at the end of it is not exactly humane If you react to the opening tag right away then you signal that it s special and needs escaping and you do it right when

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

  • Talk.Change Italics Markup Proposal
    to clarify my thoughts on this I feel that the tilde option is the worst choice It s not an obvious underscore marker isn t widely used which should say enough and I m wondering if it wouldn t be a bad choice considering keyboard layouts Using the underscore characters would be second worst The fact that it is tradidtionally used to mark italic text whenever italics are not technically available by authors is irrelevant in my opinion Most users are probably unaware of that tradition and would probably find it an unintuitive marker My primary choice would still be the slashes the earlier comment that URIs should be matched on is spot on and would remove any confusion with regards to URIs and italics MartijnVanDerKleijn 11 jan 2007 Shall we mark it as rejected somehow Just for book keeping RadomirDopieralski 2007 Styczeń 11 I think that ISO dates would be saner in this context Agreed I took the liberty to put a comment box on the top of the page MartijnVanDerKleijn 2007 01 11 many non techies are unfamiliar with ISO dates in my experience but you re probably right rant I prefer ISO modified like 2007 Jan 11

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

  • Talk.Cheat Sheet
    Page Discussion V iew A ttach I nfo Hmmm the cheatsheet seems to use three external files creole cheat sheet files injection graph css creole cheat sheet files injection graph func js creole cheat sheet files none icon png I can t seem to actually find any of them though Is there a permission problem on the server Another question what are they for Sam 2007 Nov 12 Second thought We really could use an xhtml version of the cheat sheet There are a bunch of open br tags and an hr tag and a few other things that need to be cleaned up to make this happen Sam 2007 Nov 12 Re the paragraphs paragraph Paragraphs are created by simply typing the text To separate paragraphs just leave an empty line between them Line ends will be preserved inside paragraphs You can use to force a line break most everywhere I think the sentence Line ends will be preserved inside paragraphs is misleading and I think you really meant to say something like Line breaks will be preserved inside paragraphs In CheatSheet wikicreole1 pdf the top level heading should have a single equal character not two to match Mediawiki

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

  • Talk.Christoph Sauer
    Talk BoldAndItalicsReasoning Home Talk BoldAndListsAmbiguity Home Talk ChangeItalicsMarkupProposal Home Talk CheatSheet Home View Page Discussion V iew A ttach I nfo Note the spaces after bullets Radomir Dopieralski 2007 May 4 You re right I m not a troll pitches creole in the bitbucket Thanks for setting up this site Christoph I am writing a specialized wiki for a new project and wanted to start with the most standard easy

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

  • Talk.Code Highlighting Proposal
    sure we need it but I use it in the MoinMoin plugin because moin needs it and I figured out I ll describe it Actually this proposition is different from what I use for moin the shebang is on the same line as the opening braces whil in my plugin it is located on the next line The reason is simple if I made it on the same line in moin the page text would be incompatible with Creole Not sure about the naming convention too It seems right to move away from the engine s plugin naming convention and avoid things like ceeplusplus or ceesharp when there is nothing preventing us from writing c or c We should probably decide wether to ignore character case though In case of conflict with the internal plugin naming conventions no or allowed in the plugin names for example a translation table can be used internally Other solution would be similar to how macros and other extensions are to be handled leave the naming as the responsibility of the engine developer wiki admin gaining some flexibility and ease of implementation but losing interoperability There is also a problem of using this markup for

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

  • Talk.Collision Free
    rights reserved license BY SA Sponsored by the Wiki Symposium and the Nuveon GmbH view find Quick search type ahead Recent Searches Clear Talk Collision Free Your trail Talk BoldAndListsAmbiguity Home Talk ChangeItalicsMarkupProposal Home Talk CheatSheet Home Talk ChristophSauer Home Talk CodeHighlightingProposal Home View Page Discussion V iew A ttach I nfo I propose another collision type Collision between Creole markup means that there is ambiguity in the Creole Markup

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



  •