http://sourceforge.net/tracker/?func=detail&aid=2977130&group_id=38414&atid=
422032
I was told that it could not be added because it had an html specific option
for the table directive.
The comment also suggested making it a global option whereas I wanted to
still have specific control over each table. My team-mates and I have been
successfully using this patch for some time now, with no problems.
--James
please help!
--
You received this message because you are subscribed to the Google Groups
"sphinx-dev" group.
To post to this group, send email to sphin...@googlegroups.com.
To unsubscribe from this group, send email to
sphinx-dev+...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/sphinx-dev?hl=en.
On 2010-08-04, James Evans wrote:
> I had submitted a patch to docutils a while back that added a lot more
> control to tables and their columns:
> http://sourceforge.net/tracker/?func=detail&aid=2977130&group_id=38414&atid=
> 422032
> I was told that it could not be added because it had an html specific option
> for the table directive.
> The comment also suggested making it a global option whereas I wanted to
> still have specific control over each table.
Actually the comment suggested turning the HTML-specific option into a
"special class argument" (like 'borderless') so that it can be savely
ignored by other output formats.
Besides following the general Docutils conventions (options are for all
writers, class arguments are optional), this also has the added benefit
that the 'nocolgroup' can be specified as a global configuration value as
well as on a per-table basis.
> My team-mates and I have been successfully using this patch for some
> time now, with no problems.
What happens if you generate PDF, XML, or LaTeX output from a document
containing the "nocolgroup" option?
Günter