All of lore.kernel.org
 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/5] Layout tweaks for 2c layout
Date: Thu, 26 Jan 2017 08:22:30 -0800	[thread overview]
Message-ID: <20170126162230.GS3989@linux.vnet.ibm.com> (raw)
In-Reply-To: <8fc83317-ec1d-da55-526a-fe63d5233df0@gmail.com>

On Fri, Jan 27, 2017 at 12:16:51AM +0900, Akira Yokosawa wrote:
> >From 15aea071f9a8ff33b0f97310b2afd4730d33afa1 Mon Sep 17 00:00:00 2001
> From: Akira Yokosawa <akiyks@gmail.com>
> Date: Thu, 26 Jan 2017 23:25:08 +0900
> Subject: [PATCH 0/5] Layout tweaks for 2c layout
> 
> Hi Paul,
> 
> This is *not* a bibliography update.
> 
> Because of wide textwidth for two-column layout, the cover page, legal
> section, and TOC, which are one column, looks too wide.
> 
> Patch 1 adds an explicit line break before "What" in the title. Another
> candidate might be before "And, If So,", but I think this looks better.
> 
> Patch 2 narrows effective textwidth of legal section and TOC as the same as
> that of one-column layout by using "changepage" package.
> 
> Patches 3 and 4 can be regarded as a workaround of build error in 2c layout
> when "inlinelinks" is enabled. By using one-column layout for bibliography,
> the issue can be avoided. Also, wider column width permits freedom in
> typesetting of "alpha" style bibliography. The effective textwidth for
> bibliography is a little wider than the one-column one considering indent
> of entries. You might want to skip patch 4 which enables inlinelinks, but
> as far as I could test by choosing varieties of monospace fonts, there was
> no build error caused by hyperlinks in bibliography.
> 
> Patch 5 tweaks parameters for placement for floating objects. In two-column
> layout, when a not so tall figure occupies a column, it looks imbalanced
> if the neighboring column is flushed from top to bottom. By increasing
> "floatpagefraction", such placements can be prevented.
> 
> Please give it a try and let me know what you think.

It does look quite good -- queued and pushed, thank you!

							Thanx, Paul

>                                             Thanks, Akira
> --
> Akira Yokosawa (5):
>   Specify line break in title of cover page
>   Narrow textwidth of legal and TOB pages in 2c build
>   Change bibliography to one-column layout in 2c build
>   Enable inlinelinks for 2c build
>   Increase floatpagefraction for 2c layout
> 
>  appendix/appendix.tex |  6 +++++-
>  legal.tex             |  4 ----
>  perfbook.tex          | 13 ++++++++++++-
>  3 files changed, 17 insertions(+), 6 deletions(-)
> 
> -- 
> 2.7.4
> 


      parent reply	other threads:[~2017-01-26 16:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-26 15:16 [PATCH 0/5] Layout tweaks for 2c layout Akira Yokosawa
2017-01-26 15:18 ` [PATCH 1/5] Specify line break in title of cover page Akira Yokosawa
2017-01-26 15:19 ` [PATCH 2/5] Narrow textwidth of legal and TOB pages in 2c build Akira Yokosawa
2017-01-26 15:20 ` [PATCH 3/5] Change bibliography to one-column layout " Akira Yokosawa
2017-01-26 15:21 ` [PATCH 4/5] Enable inlinelinks for " Akira Yokosawa
2017-01-26 15:23 ` [PATCH 5/5] Increase floatpagefraction for 2c layout Akira Yokosawa
2017-01-26 16:22 ` 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=20170126162230.GS3989@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.