Discussions of the Parallel Programming book
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Akira Yokosawa <akiyks@gmail.com>
Cc: perfbook@vger.kernel.org
Subject: Re: [PATCH 0/2] Style guide updates
Date: Sun, 3 Sep 2017 21:18:09 -0700	[thread overview]
Message-ID: <20170904041809.GF15437@linux.vnet.ibm.com> (raw)
In-Reply-To: <fc924fba-1dd2-dede-c557-2d42b7777fb0@gmail.com>

On Mon, Sep 04, 2017 at 07:30:32AM +0900, Akira Yokosawa wrote:
> On 2017/09/04 2:38, Paul E. McKenney wrote:
> > On Sun, Sep 03, 2017 at 11:54:19PM +0900, Akira Yokosawa wrote:
> >> >From 91874614a21874550a5d9ffa3d0fba5f6d6416f1 Mon Sep 17 00:00:00 2001
> >> From: Akira Yokosawa <akiyks@gmail.com>
> >> Date: Sun, 3 Sep 2017 23:39:54 +0900
> >> Subject: [PATCH 0/2] Style guide updates
> >>
> >> Hi Paul,
> >>
> >> This patch set adds a section of ellipsis and a couple of experimental
> >> tables corresponding to new tables in memorder.
> >> Booktabs' rules and gaps in mid-rules still works in these tables, I
> >> suppose.
> >>
> >> Let me know what you think.
> > 
> > Nice!  I have applied these.
> > 
> > I played with Table D.13 (WWC) a bit, as the lightgray looked a bit
> > heavy to me.  Using lightgray!25 was too light and made me strain a bit
> > to see the grey line, but anywhere between lightgray!35 and lightgray!60
> > looked fine.
> 
> lightgray is defined on line 930 in styleguide.tex at the moment.
> Current definition is:
> 
> 	\definecolor{lightgray}{gray}{0.9}
> 
> You can tweak it as you like. If you need more variation, you can define
> another color and use it in specific tables.
> But I'm against tweaking darkness in each table.

Ah, I was assuming that lightgray was a builtin.  Agreed, per-table
tweaks should be avoided.

> > The answer is probably "it depends" because my printer favors slightly
> > darker than does my monitor.  Might depend on the table as well, as I
> > would guess that the more empty cells the heavier the color needs to be.
> > Left to myself, I would choose lightgray!50.  But what level of shading
> > looks best to you on your equipment?
> 
> It definitely depends on the printer/display to use.
> But as the definition of lightgray can be tuned as you like, I'm OK with
> the default of, for example:
> 
> 	\definecolor{lightgray}{gray}{0.95}
> 
> Let's see what people think.
> 
> The definition will be moved into perfbook.tex when we start conversion
> of table layout and should be easy to find for people to customize.

The people I showed printouts to prefered your level of grayness,
so let's stick with that for the time being.  But yes, easy adjustment
is good, given the variation in monitors, printers, and eyes.  ;-)

							Thanx, Paul

>       Thanks, Akira
> 
> > > Either way, it looks way better than the current pervasive use of \hline
> > in the main body of the text for those particular tables.
> > 
> > 							Thanx, Paul
> > 
> >>     Thanks, Akira
> >> --
> >> Akira Yokosawa (2):
> >>   styleguide: Add 'Ellipsis' section
> >>   styleguide: Add more experimental tables
> >>
> >>  appendix/styleguide/styleguide.tex | 206 ++++++++++++++++++++++++++++++-------
> >>  1 file changed, 169 insertions(+), 37 deletions(-)
> >>
> >> -- 
> >> 2.7.4
> >>
> > 
> > 
> 
> --
> To unsubscribe from this list: send the line "unsubscribe perfbook" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  https://urldefense.proofpoint.com/v2/url?u=http-3A__vger.kernel.org_majordomo-2Dinfo.html&d=DwICaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=ux41CW3B5BSVxDMRNRWyLbUmPebZc70Kq4AkfdiRGMI&m=uyhL4QLWRXYTZychfv95fU4Rb5i9T45Skiw-rOvTrSY&s=sHKlmz4HbWX3x0yqdKF5SarQcDgJHf8f3R9ZYQk2mm4&e= 
> 

--
To unsubscribe from this list: send the line "unsubscribe perfbook" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  https://urldefense.proofpoint.com/v2/url?u=http-3A__vger.kernel.org_majordomo-2Dinfo.html&d=DwIBAg&c=jf_iaSHvJObTbx-siA1ZOg&r=ux41CW3B5BSVxDMRNRWyLbUmPebZc70Kq4AkfdiRGMI&m=MS4Ss7GQu0IZzTJ120BmJpvVMyZnQuEAFTFByGvMMx4&s=8Vyd5hRdslQKHP3rZclReXUd4jJP8CzoJqAkc22SLDo&e= 


      reply	other threads:[~2017-09-04  4:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-03 14:54 [PATCH 0/2] Style guide updates Akira Yokosawa
2017-09-03 14:56 ` [PATCH 1/2] styleguide: Add 'Ellipsis' section Akira Yokosawa
2017-09-03 14:58 ` [PATCH 2/2] styleguide: Add more experimental tables Akira Yokosawa
2017-09-03 17:38 ` [PATCH 0/2] Style guide updates Paul E. McKenney
2017-09-03 22:30   ` Akira Yokosawa
2017-09-04  4:18     ` Paul E. McKenney [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170904041809.GF15437@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=akiyks@gmail.com \
    --cc=perfbook@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox