Antonio Vivace

Monospaced text and/or diagrams draw with unicode symbols are excluded for the reasons @ISSOtm mentioned. We should not use images and/or graphical diagrams if not stricly needed, as they don't...

> The table loses the "visual" aspect of it. Why? What you are losing listing the bytes by rows instead of by columns? If you think that can help, you...

On the other hand, something like this can go in a "preliminary" chapter on how to read the document ``` Bits: X 6 5 4 3 2 1 0 |...

> > > The table loses the "visual" aspect of it. > > > > > > Why? What you are losing listing the bytes by rows instead of by...

> Do we support column spanning like that? Yes, we do. There are examples of "markdown can't do that, let's fall back to HTML" around the document and I don't...

> Nintendo's diagrams handle this by putting the long explanations outside of the table. For example, the fields could be given names, and then explained below. > Bit 7 6...

Before actually starting to apply this style, we should formalize it https://github.com/gbdev/pandocs/wiki/Document-Style

Definitely not. I'll keep this issue up so we can check other parts of the document, too.

> Imo, an automated solution would fall flat too often to be worth the effort. A per-file override would work much better imo. Per-file override would be better, yes, but...

> No, nothing is currently being done. "All" that there is, is [the `rgbds-deb` repo](https://github.com/ISSOtm/rgbds-deb), which has usage instructions [in its wiki](https://github.com/ISSOtm/rgbds-deb/wiki/Process); and really, that's everything that's needed. > >...