Hi Clemens,

I'm very sorry for long silence.

> From: Clemens Wyss
> Sent: Wednesday, February 21, 2001 3:40 PM

> >How does the server interprete rbi_code tag?
> >Does this patch engage your interest?
> >Though I have not run the code...

> To be honest, I hacked rw.cgi to get this thing running.

I'm happy to hear my code is hacked.

> Of course your
> proposal (putting it into rd2rwiki-lib.rd) would make it much cleaner.
> Would it eventually even make sense to generally extend rw2rwiki by
> allowing the developer to register special tag-handlers in the
> rd2rwiki-processor?

Hmm.  I want to hear developer's voice.
RWiki only supports RD's reference extension.

ex. To support inline img with RWiki, add below code
  and try
  ((<img:http://www.rubygarden.org/rubygarden.jpg>)).
  (not tested...)

  class RD
    class RD2RWikiVisitor
      def ref_ext_img(label, content)
        return nil unless /^img:\s*(.+)$/ =~ label
        ref = $1
        %Q[<img href="#{ref}" alt="#{content}" />]
      end
    end
  end

First point.  What?
Clemens, would you explain full detail of "special
tag-handlers?"  Is "tag" not a RD reference but a
(X)HTML tag?

Second point.  When?
This is a simplified DFD around RD.

  RD text
   | (1) submitted via CGI or E-mail
   V
  RD file
   | (2) compiled by RDtool and rd2rwiki-lib.rb
   V
  HTML/eRuby
   | (3) compiled by ERb
   V
  HTML (body part only)
   | (4) mearged by RWiki server
   V
  HTML (full)

(2) is processed when RD file was changed or RWiki
server was started.
(3) is processed when an user retrieved the page.

Where do you want to hook the process?

# By the way, we plan to extend RD -> RD/eRuby in the
# future version of RWiki.

> NOTE: Providing the absolute url to my interpreter allows *any* rwiki to
> make use of this feature! 

Funtastic.  I plan to use it.

> Hopefully I (we) get some more feedback to this issue.

Thanks.  I hope so, too.

// NaHi