|
From: David G. <go...@py...> - 2002-12-20 01:49:39
|
[David Goodger] >> 2. Near the end of the table, there's a cell that spans both >> columns. It doesn't have any border in the PDF file. It >> should. In this particular case it looks OK (it's a >> pseudo-title), but it's >> still wrong. [Engelbert Gruber] > in the html version there is no border at all. is this because the > table was without vertical lines or because of me. Are you referring to the markup in the source file being a simple table, without "|" characters between columns? That doesn't get stored in the doctree, and doesn't influence the output. A grid table produces the exact same doctree as an equivalent simple table. I suspect it may be a browser/stylesheet issue. In Mozilla and IE I see the table with full borders and row/column separators. > should i make no border too. There should be a border by default. > tables are an itch and used far to often Not following you here. > the configuration files entries might be done by a description > environment as the option-list, but this might need another markup, > if we donot use field-lists. That's just avoiding the real issue. If there's a bug in table processing, you can't say "use feature X instead", unless tables (or some aspect of tables) are not supported at all, in which case the docs and help (and even the code) should say so explicitly. -- David Goodger <go...@py...> Open-source projects: - Python Docutils: http://docutils.sourceforge.net/ (includes reStructuredText: http://docutils.sf.net/rst.html) - The Go Tools Project: http://gotools.sourceforge.net/ |