Clarifying the format support table

[mahkoh]

The format support table has a complex layout where the descriptions of the columns are written horizontally

This makes it unclear which column belongs to which bit. However, the border pointed at by the arrow can be removed by adding border-right: none to the row and border-left: none to the column, which creates a continuous space from the row to the downwards arrow.

[oddhack]

Agreed that would be a clarity improvement. I am not clear that this is possible to do in asciidoc markup without some sort of postprocessing hack, as it does not appear to let you assign asciidoc roles (aka CSS classes) at the table cell level, but will check with them.

(Edit: this does not appear to currently be possible but I'm confirming with the asciidoc folks: https://asciidoctor.zulipchat.com/#narrow/channel/279642-users/topic/Adding.20roles.20to.20table.20cells/near/587802303 )

[oddhack]

N.b. this is the result of trying to cram 15+ different columns for each format, each with a long name, into something readable. Andrew made a heroic effort but if you have any better layout ideas, please let us know. We could convert from a table to a list, but the lists would generally speaking be much, much longer than the table due to many of the long feature bit names being replicated many times over.

[mahkoh]

This is the best way to represent an NxM table that I've come across so far.

I've in fact proposed adopting this design elsewhere: vially/wayland-explorer#187

[oddhack]

One of the folks on the asciidoctor chat suggested a workaround using JS which I'm hoping they will share, as it sounds like the most viable way to approach this in the present asciidoctor implementation.