>From af290804fbb9868bb242c8ad6d889d46dfa9add1 Mon Sep 17 00:00:00 2001
From: Akira Yokosawa <akiyks@xxxxxxxxx>
Date: Fri, 18 Aug 2017 23:53:45 +0900
Subject: [PATCH 0/4] Style guide updates (round 2)
Hi Paul,
Let me explain each patch in this set first.
Patch #1 is for compatibility to older LaTeX installation.
Patch #2 adds the tweaked tables described below.
Patch #3 converts "tabulary" tables to "tabularx". It involves manual
width adjustment, but the end result is not so different, with the
bonus of increased font size. This enables us to try dashed lines of
arydshln package.
Patch #4 adds examples using dashed lines. They look not so appealing
in the particular tables, but there might be cases they are useful.
On Ubuntu Trusty, an additional package "texlive-humanities" is necessary.
Regarding your message On 2017/08/14 08:32:46 -0700:
> Perhaps single-column tables with (say) three or fewer rows might
> look like D.3, and more complex ones like D.4? Really complicated
> tables might need more \hlines, shaded cells, or some such.
There are few tables with three or fewer rows. So, most tables should
look like D.4 (in the previous round). It is now Table D.3
Coloring of alternate rows could not be applied simply to Table 3.1
because of the \textcolor{} tweaks. I used siunitx's "S" column specifier
instead in Table D.4.
>> For the coloring, all I did was adding a command
>> "\rowcolors{1}{}{lightgray}".
>> The (not so) hard part was to make the header row to be actually
>> one row. I used parbox for the moment.
>> Please give a look when you have time.
>
> That does seem eminently reasonable for that table.
>
> Tables 5.1 and 5.2 have more "interesting" headers, with the
> "Reads" spanning two columns, each of which has a subcolumn
> header. One approach would be to apply the "Reads" to each
> subcolumn like you did for D.4. But this approach looks to me
> to be less applicable to Table 13.1. And Table C.1.
I touched Tables 13.1 and C.1 in this patch set.
They are Tables D.5 and D.7.
D.6 is another version of Table 13.1 with proper legends.
I didn't touch Tables 5.1 nor 5.2 in this round, but they should be
easy.
>
> Table 9.4 is a bit more challenging, and 10.1 is similar, though
> more suitable for your parbox trick. Thoughts?
Table 9.4 is reworked as Table D.8. As you see, I removed the "Category"
column for coloring of rows to work.
Table 9.1 requires a different approach (not tried yet).
Table 10.1 can be regarded as a figure drawn by tabular environment
and is not suitable to booktabs' rules.
Tables 7.1 and C.5 don't look suitable to booktabs' rules either.
I'll keep them as is for the moment.
>
> Table 14.1 might need to keep its hlines, but what are your thoughts?
> A clear separation between the number on the left and the columns
> corresponding to each CPU seems important. Ditto 14.2.
Table 14.1 is reworked as Table D.9.
Gaps in the mid-rule can represent the separation done by vertical rules
in the original one. I don't think hlines are necessary here either.
Or using dashed hlines might be an option.
>
> Thoughts on Tables 17.1 and 17.2? (The HTM comparison tables.)
I have not tried these large and complex tables yet.
The "tabu" package might improve them. I'm kind of scared by the fancy
looks of tabu document, though... There can be other options.
Please give me a while.
>
> But most of the rest of the tables look like they would do just fine
> as either D.3 (for the single-column ones with three or fewer
> columns) or D.4 (for the rest).
>
> But what are your impressions?
So the other simple tables can have the rows colored.
Let me know what you think of the added tables.
Thanks, Akira
--
Akira Yokosawa (4):
Use 'fixltx2e' package
styleguide: Add more table experiments
Get rid of 'tabulary' package
styleguide: Add table examples with dashed lines
FAQ-BUILD.txt | 5 +-
SMPdesign/SMPdesign.tex | 8 +-
appendix/styleguide/styleguide.tex | 557 +++++++++++++++++++++++++++++--------
defer/rcuapi.tex | 11 +-
defer/whichtochoose.tex | 10 +-
perfbook.tex | 6 +-
6 files changed, 462 insertions(+), 135 deletions(-)
--
2.7.4
--
To unsubscribe from this list: send the line "unsubscribe perfbook" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
