On 2015-02-10 21:08, Stéphane Blondon wrote: > 2015-02-05 23:23 GMT+01:00 Stephan Beck <sb...@mailbox.org>: >> The first quick and dirty solution (only touching the .html file) is to >> suppress >> the second table row in the.html file. > > The solution I provided is CSS only. If we need to change the HTML, I > think your second solution (removing the table) is a better one. > > >> A second solution I'll work on is to replace the table with a >> "div id="navfooter" containing a nav element that includes anchors and >> images. >> I think it's better to use "table" only for "real" tables, not as a space >> structuring design element. This solution will imply changes to the .css. > > I agree. Replacing the table (by a list for example) is a better > solution. I don't know how much the maintainers are ready to change > the rendering. > [...]
The main problem with changing the HTML is that it is mostly generated beyond our control. So far I managed to extend the existing HTML using "supported" hooks for the given cases, but I fear this table might not have such a hook. Disclaimer, I know nothing more about docbook-xml than I can google - by all means, feel free to prove me wrong. Provided there is a decent maintainer solution, I am happy to accept it. I just do not want to end up maintaining a custom "XML -> XHTML" transformation only used by us (or a "handwritten HTML-post processor for fixing style issues"). ~Niels -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
