On Sun, Dec 30, 2018 at 11:40:55PM +0900, Jean-Christophe Helary wrote:
> t{ r{ c{...} c{...}}
> r{ c{...} c{...}}}
> Of course, it doesn't have to be t, r, c.
This would work.
> It could be:
>
> [{ ~{ |{...} |{...}}
> ~{ |{...} |{...}}}
Not a very good idea. It introduces '[' as a new meta-character. Then you have
to escape it whenever '[' appears in the normal text, and have to document it as
a special case. It adds complexity and a new syntax concept.
> And from what I'm seeing in lib.l where there is no check regarding whether
> <li> are within <ul> or <ol>,
Right, because "-{" can render to <li> in HTML (or \item in Latex) for both
list types.
> my very non educated guess would be that something like the following would
> work:
> ("t" # Table
> (_render "table") )
> ("r" # Table row
> (_render "tr") )
> ("c" # Table cell
> (_render "td") )
>
> but then, I don't understand (yet) why you're not using letters for the wiki
> syntax...
For the above reasons. Imagine you have (foo () (println '("t" "u" "v") ... in
the article's text. It would render as a table! So the user has to escape it
with '\', and surely be confused about the many rules.
Currently *only* '{' starts markup, so it is still rather KISS ;)
Letters could indeed be used, but are still a little "dangerous", eg. if one
writes abc{def}ghi in the text. Who knows? ;) I feel that a punctuation
character just before the "{" is more visibly distinct and kind of safer.
So I would rather use some other charaters than "t", "r" and "c".
BUT: I'm still not convinced that adding tables to the Wiki markup syntax is a
good idea. It opens a can of worms. You will quickly need more parameters, like
captions, table headers, column/row alignments, widths and heights, colspans and
whatnot. Again, we lose the simplicity of the markup language.
☺/ A!ex
--
UNSUBSCRIBE: mailto:[email protected]?subject=Unsubscribe
