-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Noah Kantrowitz skrev 04. juni 2009 22:13:
> Link to the last discussion on this (or at least one of the last)
> http://groups.google.com/group/trac-dev/browse_thread/thread/f79a1cbb894fe079/8e7d047d0c9fcf16
>
> --Noah
Thanks for the link -- didn't think to include it -- my questions re
syntax was partly motivated by the points made in that thread. I'd be
very interested to hear some more detailed views on ReST vs wiki markup
- -- right now I see two points in favour of the wiki markup:
1) It's what a great number of trac users already know
2) Existing trac macros already integrated with the trac
wiki processor.
I'd be interested in hearing other points of view, especially against
ReST, as I might be blind to any real deficiencies others find crippling ?
Christian Boos mentioned "the WikiEngine refactoring which will make it
possible to generate structured output (e.g. Genshi events or docutils
nodes, so that we could hijack the docutils writers for generating the
static documentation)"
Has this taken place in trunk ? I think the consensus is that there are
problems with managing documentation (exclusively) in the (any) wiki,
due to difficulties with maintaining separate versions (0.11, 0.12 as
well as multiple languages) -- but making it easier to do general
transforms on the wiki content would be great either way.
This is beginning to sound a bit like reinventing xml and xlst -- even
though I personally think working with either of those tend to be painful.
Christian further mentions: "(Trac has) Much improved table markup (the
reST table markup is unbearable)".
This would be:
http://trac.edgewall.org/wiki/WikiFormatting#Tables
vs:
http://docutils.sourceforge.net/docs/ref/rst/restructuredtext.html#simple-tables
http://docutils.sourceforge.net/docs/ref/rst/restructuredtext.html#grid-tables
I agree the trac simple syntax is easier than the rest simple syntax,
but I think "unreadable" is a bit strong ?
It does illustrate a major difference between ReST and TracWiki-markup:
Underline-markup vs side-by-side/inline-markup:
ReST: Trac:
Headline =Headline=
========
===== ===== ===== ||Cell1||Cell2||Cell3||
Cell1 Cell2 Cell3 ||Cell4||Cell5||Cell6||
Cell4 Cell5 Cell6
===== ===== =====
Mentioned in the thread on trac-dev is also the "external dependencies
problem" -- and I agree that that needs to be taken into accounts. I'm
not aware of any good way to ensure pdf-generation with included images
that does not touch a wide range of dependencies, however.
Also while a lot of the default ReST templates are horribly ugly -- the
ability to seamlessly generate LaTeX is a great benefit -- this is of
course something eg. docutils also would grant us.
Best regards,
- --
.---. Eirik Schwenke <eirik.schwe...@nsd.uib.no>
( NSD ) Harald Hårfagresgate 29 Rom 150
'---' N-5007 Bergen tlf: (555) 889 13
GPG-key at pgp.mit.edu Id 0x8AA3392C
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkotBeEACgkQxUW7FIqjOSwwzgCbB9INW793O1X+5jzG+dD/cire
KI0AoIEOPqXQR5aDjtvp0zLZKorFAlRp
=y77G
-----END PGP SIGNATURE-----
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac
Users" group.
To post to this group, send email to trac-users@googlegroups.com
To unsubscribe from this group, send email to
trac-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/trac-users?hl=en
-~----------~----~----~----~------~----~------~--~---
