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{}?
Well, that may be possible, but for now, I want you to see if the
reduced height of the monospace font in the text is acceptable for you.
The direct effect of the change is that we can revert 2 commits
which manually specified smaller font sizes for code sample figures.
See commits bc0fd9d40035 ("after: Tweak font size of Figure A.2") and
c7c5e8a1829e ("formal/dyntickrcu: Adjust font size of sample code").
Undoing tweaks in Tables can be looked at once we switch the default font.
Thanks, Akira
>
> Thanx, Paul
>
>> Thanks, Akira
>>
>>>
>>> Thanx, Paul
>>>
>>>> Thanks, Akira
>>>> --
>>>> Akira Yokosawa (2):
>>>> Makefile: Fix .bbl dependency
>>>> Enable 'inlinelinks' option of alphapf.bst for 1c layout
>>>>
>>>> Makefile | 4 ++--
>>>> alphapf.bst | 2 +-
>>>> appendix/appendix.tex | 6 +++++-
>>>> 3 files changed, 8 insertions(+), 4 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
