====== Pagerendering ======

===== More Flexible List Implementation =====
A clean way of integrating the more flexible list scheme in the[[http://wiki.splitbrain.org/plugin:lists|un/ordered lists]] plugin into the core wiki code would be nice.  While it could be argued that bullet items that big should be in their own paragraph :-) , for technical documents this would be very useful.  For example, it would be nice to in-line equations:
<code>Some mathematical discussion on some tiddly-doodad.  Here's what we mean:
  * Some item worth bulleting.
  * Another item worth bulleting.  Let's emphasize with an equation:
<latex>\alpha = \beta + \omega</latex>
Where α is alpha, and β and ω are other things.
  * The last bullet.</code>

The renders to something like:

Some mathematical discussion on some tiddly-doodad.  Here's what we mean:\\
  • Some item worth bulleting.\\
  • Another item worth bulleting.  Let's emphasize with an equation:\\
α = β + ω\\
Where α is alpha, and β and ω are other things.\\
  • The last bullet.\\

When what would be nice is:

Some mathematical discussion on some tiddly-doodad.  Here's what we mean:\\
  • Some item worth bulleting.\\
  • Another item worth bulleting.  Let's emphasize with an equation:\\
    α = β + ω\\
    Where α is alpha, and β and ω are other things.\\
  • The last bullet.\\

Basically, the bulleted list should not automatically end the moment the carriage return occurs.  This is even more relevant for numbered lists, where you can't just live with the outdented lines, and really would like the numbering preserved.

Along those lines, allowing for numbered lists where the first listing's number can be forced to some value would be great.

> Is there a reason you can't use ''%%\\%%'' to add a blank line into your wiki markup whilst still preserving the list integrity ([[http://wiki.jalakai.co.uk/dokuwiki/doku.php/sandbox/list|for example]] - using the math plugin, but I presume the latex plugin will work in a similar manner.).  The idea is to keep the core code slim - if there is a plugin that meets your requirements what purpose does it serve to add that code to the core wiki? \\ \\ <nowiki>%%</nowiki> doesn't apply ''white-space:pre'' so multiple spaces will be reduced by your browser. You can use one of, " "," " or " ", for hard spaces. --- //[[chris@jalakai.co.uk|Christopher Smith]] 2006-05-22 00:41//

>> Chris -- thanks for your input.  Looking at the wikimarkup for your entry has proved very enlightening -- I had utterly misread the section about ''%%\\%%'' syntax in the manual.  I had believed that the ''%%\\%%'' had to be at the end of the line, and //wouldn't// work otherwise.  Should have read more carefully.  Appreciate you taking it easy on this n00b!  ^_^ \\ \\ Re: hard spaces -- this much probably should have occured to me.  In case anyone is interested, the following article served as refresher for me: [[http://en.wikipedia.org/wiki/Non-breaking_space|Non-Breaking Space]].



===== Markdown / Textile =====

Are there any plans to add [[http://daringfireball.net/projects/markdown/|Markdown]] and/or [[http://textism.com/tools/textile/|Textile]] support?

> No. Integrating parsers other than DokuWiki's own one is currently not planned.  --- //[[andi@splitbrain.org|Andreas Gohr]] 22.11.2004 20:36//
>> Sounds like two candidate plugin's to me, once there is a plugin api :)
>>> Could we do something like surround the code with <markdown></markdown> tags. For me I'm not as interested in Running the wiki with Markdown, but want/need to have the ability to paste/edit Markdown code in a wiki context. The copy is then used on our formal website. **UPDATE:** I have an install with this kind of behavior working. Here's [[http://mikezornek.com/archives/2005/02/12/how_i_added_markdown_to_dokuwiki.php|how I did it]] --[[MikeZornek]]
>>>> [[http://wiki.ioslo.net/dokuwiki/markdown|New-style markdown plugin]]  --- //[[calle@ioslo.net|Carl-Christian Salvesen]] 2005-05-25 16:39//
>>>>> I'm using DokuWiki for few months and try to live with <markdown> tags. But it's not effective in long term. I really like DokuWiki but at the same time I'm very used to Markdown as I find it much more clean, simple and intuitive than any other wiki syntax. Also, Markdown is a great and unified solution for most of syntax issues with DokuWiki syntax (un/ordered lists, definition lists, multi-paragraph list-items etc.). If there would be a way to switch a parser to a preferable one (in this case to Markdown & SmartyPants combo) it would be more than great a feature of DokuWiki. PHP implementation of Markdown and SmartyPants are available on [[http://michelf.com/projects/|Michel Fortin's site]]. --- //[[modx.grad@gmail.com|Grzegorz Adamiak]] 6.10.2007]]//

===== Floating Header =====

I've changed the footer and header button bars to better suit the team needs. I don't know if it's possible, but could the header be a layout element that is always visible even on a long document? Meaning, if the user is reading a long document and scrolls vertically, the header and footer are now shown. Does CSS allow for a DIV to be always visible at the top of the browser's viewframe? -- 2004.10.08.

> CSS gives the property ''postion:fixed'' to do this. However it's only supported in modern Browsers (Mozilla and Opera) - not in IE((There are some JavaScript hacks to simulate it in IE)). --- [[andi@splitbrain.org|Andi]]

>> You should be able to achieve something along those lines with
>> <code css>div.page {overflow:scroll; height:500px;}</code>
>> Ideally height needs to be expressed as a percentage.  That seems to work ok with IE6 but not with Firefox or Opera.  Perhaps with further playing around or adding an additional containing div you could get an optimum solution :-).
>> --- [[chris@knowledge.teevee|chris]]

===== Table of Contents =====

Can I modify Table of contents to show internal links to other pages not links to headers on the same page? (Sorry for my bad english) or make other "window" with links to other pages (like on Wikipedia homepage)?
BTW. Im translating DokuWiki to Polish now.

> This sounds like it would be tricky, as TOC is only displayed once a certain number of headings is reached.

===== Acronyms as Hovers with Javascript =====

Thought [[http://livsey.org/experiments/hoverhelp/|hoverhelp]] is a pretty nice implementation. Could be something to use on marking up acronyms or similar