jh> Not sure about options formatting. Me either. Nothing wrong with using @table @option as you (mostly) did. But as a matter of convention, @option is usually used for command line options. I'm not sure weight values, etc., are "options", semantically. It's a gray area, as such markup tends to be. Therefore I tend to use @code for nearly everything. It makes no practical difference.
Aside from that, because these particular tables (in Low-level font comands) have such short items, I hacked in some kludges to put them on one line in at least the Info output. Seemed easier to read. Thanks, Karl
