On Sat, 16 Sep 2006, Georg Baum wrote:

> > (In addition, I'm trying to make it as easy as possible for you guys 
> > to check/modify my texts. I think that's easier if I can just link to 
> > a wiki page, or email a piece of text).
> 
> I don't know how it is for others, but for me personally it would be easier 
> if it was in the source. I know next to nothing of wiki markup. When I 
> edit something in a wiki I use either plain text and hope that somebody 
> will format it or copy existing stuff.

You don't need to know anything special about the wiki markup. I'll be 
*very* happy if you just do plain text. For that matter, I suspect that 
most frequent comments will arrive via e-mail. So if you (and others) just 
read what I've written and give me comments that's a good start.

I'll give you one tip though, related to the plain text bit. If you want 
to make sure that your text is displayed as is within a wiki page (with 
spaces and all), just enclose it in [EMAIL PROTECTED]@].  Like this

        [@
        This text will be shown just like it is, no ''markup'' is
        recognized....       and spacing is preserved. Useful for very
        simpel tables, i.e.
        Column 1         Column 2       column 23
        Bla              Bla           Bla bla
        @]

Having said the above, maybe I should relatively soon do as you suggest 
and move the documentation to the source, and there insert "templates" for 
each of the LFUNs. Then everybody can relativel easy commit patches for 
separate LFUNs. However, before I do this I should figure out what the 
template should look like, and with this I mean what kind of information 
it should contain. And in order to do that, I need to first document some 
functions.

> > As it's Friday, I might as well say that since I'm doing it, I'll do 
> > it my way :-)
> 
> That has nothing to do with friday, that holds on all days.

Quite true, I'm *saying* it since it's Friday :-)

/C

-- 
Christian Ridderström, +46-8-768 39 44               http://www.md.kth.se/~chr

Reply via email to