Changes between Version 33 and Version 34 of TracDev/Proposals/AdvancedWikiFormatting

Timestamp:

Jun 30, 2010, 10:07:00 AM (14 years ago)

Author:

Christian Boos

Comment:

removing obsolete items, some additional notes and ideas

TracDev/Proposals/AdvancedWikiFormatting

@@ -6 +6 @@
 == Topics ==
 === Tables ===
+ - support WikiCreole single pipe style (#6630)
  - add `|+` MediaWiki style caption or `#!caption`
- - support WikiCreole single pipe style (#6630)
+ - annotation for specifying vertical alignment (top `||^` and bottom `||.`) (ticket:9309#comment:9)
  - also support MediaWiki style?? (#1424)
- - annotation for specifying vertical alignment (`||^`/`||.`) (ticket:9309#comment:9)
 
 === Definition lists ===
@@ -46 +46 @@
 
    1. continue in the same list
+
+      another paragraph in the //same item//
    }}}
    }}}
@@ -52 +54 @@
 
    1. continue in the same list
+
+      another paragraph in the //same item//
    }}}
  - when continuing an item on the next line, one should stay within the item
@@ -82 +86 @@
 
 The automatic ids generated for headings are not readable.
-We should replace spaces by hyphens, at the very least. 
+We should replace spaces by hyphens instead of squashing them, at the very least. 
 Compatibility with the old compact style could be achieved by using the `name` attribute, whereas `id` would be used for the new, more readable style.
 This is especially important for languages when titles use sentence-style capitalization, not title-style capitalization (see e.g. [Wikipedia:Wikipedia:Manual_of_Style_(capital_letters)#Section_headings Section_headings] in Wikipedia).
@@ -89 +93 @@
 === Enhanced processors ===
 
-Allowing `{{{ div ...` would be easy, is it worth it? ''probably not, let's keep #! ''
-
 For div and tables, add some more "standard" classes (we already have "important" for divs and "listing" for tables):
  - see MoinMoin:HelpOnAdmonitions
- - another interesting possibility: 
-   [http://meta.wikimedia.org/wiki/Help:Collapsing#Collapsible_DIV collapsible and collapsed] (#9214)
+ - [http://meta.wikimedia.org/wiki/Help:Collapsing#Collapsible_DIV collapsible and collapsed] (#9214)
+ - sortable (#8949)
 
 === TracLinks ===
-==== CamelCase ====
-
-The MoinMoin style internal free link has been introduced to cope with wiki words with appended content, like when writing `["WikiProcessor"]s`. ~~First, the implementation is restricted: it doesn't allow for a lhref equivalent, `["WikiProcessor" the wiki processors]` ~~ (#7695). What if we would instead re-use the lhref regexp, in the quoted case? It would be equivalent to making the ''wiki:'' prefix the default namespace. The advantage would be that ''any'' word could be wikified that way. //This is what `[[...]]` links do.//
- - `["checking"]` -> ["checking"]: works already
- - `["checking" the check]` -> ["checking" the check]: works now (r9535)
-
 
 ==== Alternative forms of linking ==== #linking
 
- - shorthand for `[[Image(<img>)]]`: `{{<img>}}`, see MoinMoin:HelpOnLinking
- - `[=#anchor <label>]` creation, see #6413 **FIXME: document this in WikiFormatting**. Preliminary documentation added to WikiFormatting#AddingIDstoanyitem (much of it taken from the r8697 commit comment)
+ - shorthand for `[[Image(<img>)]]`: `{{<img>}}`, see MoinMoin:HelpOnLinking; `{{...}}` is also used for [MediaWiki:Help:Template transclusion] in MediaWiki
  - shorthand for footnotes? see #9037
 
@@ -126 +121 @@
  - !GoogleCode uses http://code.google.com/p/support/wiki/WikiSyntax [[br]]
    * Mostly compatible markup, with the notable exception of `*...*` and `_..._` used for bold and italics. This is ''not'' something we're going to support, considering all the complaints we already had with our underline style `__...__`.
+     //
+     However, with strict patterns this can perhaps "work": `*this is bold*` would match, but not `use *this and *that`, and `that's /really/ useful` or `that's /really useful/` but neither of  `see /trunk/README, and/or, / etc.` 
+     //
    * Internal Wiki links are a bit easier to write: `[Wikipage]` instead of `["Wikipage"]` for us.
    * automatic heading anchors are more readable (`== Wiki-style markup ==` corresponds to `Wiki-style_markup` instead of `Wiki-stylemarkup`) (#8645)
  - BitBucket uses http://www.wikicreole.org/wiki/Creole1.0 [[br]]
-   * See WikiCreole.
+   * See WikiCreole 
  - RedMine uses http://www.redmine.org/help/wiki_syntax_detailed.html based on http://hobix.com/textile [[br]]
    * also uses  `*...*` and `_..._` used for bold and italics...
@@ -138 +136 @@
  - [http://daringfireball.net/projects/markdown/syntax Markdown] is used in a number of developer oriented sites (e.g. [http://stackoverflow.com/editing-help StackOverflow], [http://gitorious.org/gitorious/mainline/blobs/master/lib/markup_renderer.rb Gitorious wiki], [http://github.github.com/github-flavored-markdown/ GitHub Flavored Markdown]). Some of the interesting parts:
    - [http://daringfireball.net/projects/markdown/syntax#header headings by underlining] (similar to reStructuredText, but limited to `========` and `--------`)
-   - the [http://daringfireball.net/projects/markdown/syntax#list rules for list items] are quite interesting as well (how to deal with empty lines and paragraphs within lists)
+   - the [http://daringfireball.net/projects/markdown/syntax#list rules for list items] are quite interesting as well (how to deal with empty lines and paragraphs within lists, see [#Lists] above)
  - others?