So I just wanted to review what most of my new code does for those  
who are not familiar with it yet.
=====
The biggest feature of my work is the docbook export. This means that  
any valid textile markup can be exported to the docbook standard. I  
added a new chapter tag to go along with the export.
   ch. 1. Here is the title
In HTML, this will produce:
   <h1>1. Here is the title</h1>
In Docbook, this will produce:
   <chapter label="1" id="Here is the
title"><title>Here is the
title</title>
   </chapter>
=====
Another major features I have implemented is allowing for div''s  
(multi-line chunks). Whereas before if you did:
   p(some_class). here is a paragraph of text
Now you can also do:
   div(some_class).
   Here are many paragraphs of text.
   All styled will some_class.
   Yay.
   div(some_class).
=====
I also implemented a definition list that follows this standard:
in: |-
   here is a definition list:
   - yes := no
   - no:=no
   - maybe:= yes
out: |-
   <p>here is a definition list:</p>
   <dl>
   	<dt>yes</dt>
   	<dd>no</dd>
   	<dt>no</dt>
   	<dd>no</dd>
   	<dt>maybe</dt>
   	<dd>yes</dd>
   </dl>
=====
One of the cooler features is continued lists:
---
in: |-
   # one
   # two
   # three
   test
   #_ four
   # five
   # six
   test
   #_ seven
   # eight
   # nine
out: |-
   <ol>
   	<li>one</li>
   	<li>two</li>
   	<li>three</li>
   </ol>
   	<p>test</p>
   <ol start="4">
   	<li>four</li>
   	<li>five</li>
   	<li>six</li>
   </ol>
   	<p>test</p>
   <ol start="7">
   	<li>seven</li>
   	<li>eight</li>
   	<li>nine</li>
   </ol>
====
Another bonus feature to lists:
in: |-
   # six
   _# a continuation of six
out: |-
   <ol>
     <li><p>six</p><p>a continuation of
six</p></li>
   </ol>
====
I also fixed an odd behavior of tables where blank <td>''s (via
||)
simply didn''t show up. Now they are converted to
<td> </td>.
====
Otherwise, RedCloth passes all its previous unit tests and all the  
new ones I wrote to test the features I added. (I also make running  
unit tests a lot nicer BTW: try rake test).
So I propose we make a release with all these new spanking features.  
Are there any pressing bugs that should stop us from doing so? What  
version number should we go for? The ultra-conservative 3.0.5  
release... the conservative 3.1.0 release... the crack-addict 4.0.0  
release... the idiot-savant 1.2.3 release... the Bill Gates RedCloth  
2005 release... the Apple RedCloth Nano release... the typical  
SourceForge project 3.0.4a11202005 release?
- Lucas
http://rufy.com/
Lucas Carlson wrote : | So I just wanted to review what most of my new code does for those | who are not familiar with it yet. | | .... Wow quite a lot of new exciting stuff here ! I''m going to have a look at this ! | So I propose we make a release with all these new spanking features. | Are there any pressing bugs that should stop us from doing so? What | version number should we go for? The ultra-conservative 3.0.5 | release... the conservative 3.1.0 release... the crack-addict 4.0.0 | release... the idiot-savant 1.2.3 release... the Bill Gates RedCloth | 2005 release... the Apple RedCloth Nano release... the typical | SourceForge project 3.0.4a11202005 release? +1 for 3.0.5 -- Frederick Ros aka Sleeper -- sleeper at jabber.fr "...Deep Hack Mode--that mysterious and frightening state of consciousness where Mortal Users fear to tread." (By Matt Welsh) -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available Url : http://rubyforge.org/pipermail/redcloth-upwards/attachments/20051121/042db043/attachment.bin
Lucas Carlson wrote:>So I propose we make a release with all these new spanking features. >Are there any pressing bugs that should stop us from doing so? What >version number should we go for? The ultra-conservative 3.0.5 >Yes, 3.0.5. A few changes I''ve just made: * let''s merge bin/redcloth and bin/redcloth_to_docbook. the output format should be a commandline flag. * docbook support isn''t loaded by default. * use ''redcloth/all_formats'' to load every output format. Good work, rufy. _why
Lucas Carlson wrote:>The biggest feature of my work is the docbook export. This means that >any valid textile markup can be exported to the docbook standard. I >added a new chapter tag to go along with the export. > > ch. 1. Here is the title > >In HTML, this will produce: > <h1>1. Here is the title</h1> > >In Docbook, this will produce: > > <chapter label="1" id="Here is the title"><title>Here is the >title</title> > </chapter> > >What about: h1(#1). Here is the title Maybe?>Another bonus feature to lists: > >in: |- > # six > _# a continuation of six > > >Why not just: # six a continuation of six # seven # eight Do hard breaks break? I think all the extended syntax needs to go in an optional module, I''m not ready to add anything beyond what Textile and Markdown become when combined. _why