I'm working on 'python-r1 by examples' guide and I wanted to create it in style of side-by-side diffs. To be more exact, I want to show the python.eclass ebuild in one column, and python-r1 ebuild in the second column like: | python.eclass ebuild | python-r1 ebuild | | | | | PYTHON_DEPEND=... | PYTHON_COMPAT=... | ... which would be really helpful to explain migration from one eclass to another. Is it possible to create something like this in our guide format? So far, I have tried using <pre/> in table but that ain't permitted by the DTD.
Beyond doing this in a single <pre>...</pre> one, I don't see an immediate way to handle this without loosing a preserved whitespace. I think allowing a <pre> in a table wouldn't make much sense as it might make things very ugly; however, perhaps we could just allow <code> or <tt> so that you can use whitespace-preserved stuff in a table. Another possibility would be to use our wiki, which allows for more formatting than GuideXML.
(In reply to comment #1) > Beyond doing this in a single <pre>...</pre> one, I don't see an immediate > way to handle this without loosing a preserved whitespace. > > I think allowing a <pre> in a table wouldn't make much sense as it might > make things very ugly; however, perhaps we could just allow <code> or <tt> > so that you can use whitespace-preserved stuff in a table. Well, a quick try with gorg shows it doesn't look best but I'd say it's acceptable [1]. It would be great if the table was stretched to the width of content area, and the code blocks were of same width by default; but so far, the worst thing is the numbering which results in repeating '1.1'. [1]:http://dev.gentoo.org/~mgorny/python-r1/examples.html > > Another possibility would be to use our wiki, which allows for more > formatting than GuideXML. I'd rather keep all the docs in a single place, and mediawiki would be the last resort to me. I'd rather write plain HTML.
seems to be dead/moot. closing.
