On Sat, Dec 31, 2016 at 12:33:13AM +0900, Akira Yokosawa wrote:
> On 2016/12/28 19:56:03 -0800, Paul E. McKenney wrote:
> > On Wed, Dec 28, 2016 at 07:07:28AM +0900, Akira Yokosawa wrote:
> >> On 2016/12/27 12:53:45 -0800, Paul E. McKenney wrote:
> >>> On Wed, Dec 28, 2016 at 12:25:48AM +0900, Akira Yokosawa wrote:
> >>>> >From 3f4f73d738b77422bd074322f3ac67f644a8d580 Mon Sep 17 00:00:00 2001
> >>>> From: Akira Yokosawa <akiyks@xxxxxxxxx>
> >>>> Date: Wed, 28 Dec 2016 00:10:28 +0900
> >>>> Subject: [PATCH 0/2] Enable inlinelinks of alphapf.bst for 1c
> >>>>
> >>>> Hi Paul,
> >>>>
> >>>> On 2016/12/26 16:39:52 -0800, Paul E. McKenney wrote:
> >>>>> On Mon, Dec 26, 2016 at 11:52:40PM +0900, Akira Yokosawa wrote:
> >>>> [snip]
> >>>>>> One idea is to use alphapf.bst only for 1c with inlinelinks enabled.
> >>>>>>
> >>>>>> Thoughts?
> >>>>>
> >>>>> I am good with enabling alphaph.bst inlinelinks only for 1c!
> >>>>
> >>>> So, this patch set does the change.
> >>>> For 2c, we reverted to the original alpha bibliography style for the
> >>>> moment.
> >>>> And I'll keep polishing the band-aid script to shorten the href-ed part
> >>>> in titles. You might want to try it for 2c when you do a release.
> >>>
> >>> Applied and pushed, thank you!
> >>>
> >>> Speaking of releases, for whatever it is worth, I expect to do one
> >>> in a few days.
> >>
> >> Every 6 month!
> >>
> >> At the current state of ongoing bibliography update, I don't think
> >> it makes much difference if you try inlinelinks for 2c.
> >> Or, will you apply the "bib-append-dio" series this time?
> >> Then it might be worthwhile. You can replace the released .pdf with
> >> inlinelinks enabled after the fact.
> >>
> >> I have readied other branches of url updates of .bib files, but I thought
> >> I should wait and send their pull request after the doi updates are applied.
> >> If you are willing to apply the other (lot of) updates for the next release,
> >> I can send the pull requests soon. But it is not urgent.
> >>
> >> By the way, I want the "courier scaled" font to be default monospace
> >> font for 2c and 1c builds. Have you tried the "mss" target lately?
> >> If you are ok with it, I'll prepare a patch to do so.
> >
> > It does build, but what am I looking for? Does it allow me to remove
> > the bogus "~" characters in some of the tables containing \co{}?
>
> JFYI, those bogus "~" characters have nothing to do with the choice of
> monospace font.
> It is the \co{} command (or the \lstinline command it uses) that confuses
> tabular environment's column width estimation. When a \co{} contains "_"
> characters, it seems that the tabular environment sometimes treats them
> as if they prefixed subscripts and estimates the width shorter than the
> string to be actuary typeset.
>
> I did some search, but could not find anyone else reporting the issue...
>
> Most of \co{}s within tables are used because they don't require escaping of
> LaTeX delimiters such as "_". For this purpose, the \co{} command is
> overkill. I'll define another command to be used inside tables.
>
> A few of them are used for automatic line breaks provided by lstinline.
> They seem to need protection of parbox or minipage around them on case by
> case bases.
>
> I'll see proper ways to present those tables. But some of them may take
> a while.
Thank you for the explanation! And the "~" characters have been there
for some time, so no overwhelming urgency.
But at least I now know that the number of "~" characters needed is
a function of the number of "_" characters, so less experimentation
required. ;-)
Thanx, Paul
--
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
