From: SourceForge.net <no...@so...> - 2006-03-23 03:05:50
|
Feature Requests item #619532, was opened at 2002-10-07 15:11 Message generated for change (Comment added) made by xmldoc You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=373750&aid=619532&group_id=21935 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: XSL Group: output: manpages >Status: Closed >Resolution: Fixed Priority: 3 Submitted By: Ben Secrest (blsecres) Assigned to: Michael Smith (xmldoc) Summary: man: No support for tables Initial Comment: The current xsl documents do not provide templates for rendering the different types of tables available in DocBook. ---------------------------------------------------------------------- >Comment By: Michael Smith (xmldoc) Date: 2006-03-23 12:05 Message: Logged In: YES user_id=118135 So I finally got around to implementing table support. And it only too 3.5 years to do it... The manpages stylesheet now support tables, including rowspans and colspans, nested tables, table footnotes, options for controlling borders and alignment, etc. ---------------------------------------------------------------------- Comment By: Michael Smith (xmldoc) Date: 2006-03-23 12:05 Message: Logged In: YES user_id=118135 A change for this issue has been added to the current codebase. Please test the change with the latest snapshot from: http://docbook.sourceforge.net/snapshots/ ---------------------------------------------------------------------- Comment By: Michael Smith (xmldoc) Date: 2004-10-22 03:45 Message: Logged In: YES user_id=118135 Adding table support is a lot of work and not a super-high priority. Workaround for now is not use tables in your XML source :-) Use lists instead if you can. I wondering if it might be possible to hack together a hybrid solution by taking HTML output, running that through links/w3m to get the tables rendered as text, then replacing the table in a copy of the source with that text version, then running through manpages stylesheet. Less than ideal, but would be better than nothing. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=373750&aid=619532&group_id=21935 |