Em Wed, 4 May 2016 11:34:08 +0200 Markus Heiser <markus.heiser@xxxxxxxxxxx> escreveu: > Hi all, (hi Jonathan, please take note of my offer below) > > Am 03.05.2016 um 16:31 schrieb Daniel Vetter <daniel.vetter@xxxxxxxx>: > > > Hi all, > > > > So sounds like moving ahead with rst/sphinx is the option that should > > allow us to address everyone's concerns eventually? Of course the > > first one won't have it all (media seems really tricky), ... > > BTW: Mauro mentioned that ASCII-art tables are not diff-friendly ... > > Am 18.04.2016 um 13:16 schrieb Mauro Carvalho Chehab <mchehab@xxxxxxxxxxxxxxx>: > > > With that sense, the "List tables" format is also not good, as > > one row addition would generate several hunks (one for each column > > of the table), making harder to review the patch by just looking at > > the diff. > > For this, I wrote the "flat-table" reST-directive, which adds > missing cells automatically: > > doc: http://return42.github.io/sphkerneldoc/articles/table_concerns.html#flat-table > source: https://github.com/return42/sphkerneldoc/blob/master/doc/extensions/rstFlatTable.py Yeah, this should address the lack of a proper way to markup cell/row spans, providing the additional bits for the tables we have at media. Yet, there are some issues with table conversions. See below. > > I used "flat-table" to migrate all DocBook-XML documents to reST. With this > directive, I also managed to migrate the complete media book (no more TODOs) > incl. the large tables like them from subdev-formats: > > https://return42.github.io/sphkerneldoc/books/linux_tv/media/v4l/subdev-formats.html > > (Rendering large tables is a general discussion which should not take place in this MT) Some tables, like the one here: https://return42.github.io/sphkerneldoc/books/linux_tv/media/v4l/control.html are truncated (tested with Mozilla and Chrome), and part of the information is lost due to that. Regards, Mauro -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
