* [PATCH 0/3] Fix for Fedora31
@ 2020-01-16 21:54 Akira Yokosawa
2020-01-16 21:57 ` [PATCH 1/3] utilities/fixsvgfonts-urwps.sh: Use symbol font available on F31 Akira Yokosawa
` (2 more replies)
0 siblings, 3 replies; 9+ messages in thread
From: Akira Yokosawa @ 2020-01-16 21:54 UTC (permalink / raw)
To: Paul E. McKenney; +Cc: perfbook, Akira Yokosawa
Hi Paul,
I recently noticed that on Fedora 31, there are a few .svg figures
which don't look they should do.
It turned out that Fedora 31 upgraded pango to 1.44, which doesn't
support type1 fonts. StandardSymbolsPS.t1 we used as an alternative
font for Symbol on Fedora no longer works.
Patch 1/3 updates fixsvgfonts-urwps.sh to use "MdSymbol" font
instead, with the existence check of the font added in Makefile.
It also removes a couple of unnecessary rules around symbol fonts
in fixfonts.sh and its derivatives.
By this change, numbers in Figures 14.5, 14.7, and 14.9 become
sans-serif on Ubuntu, which look more consistent.
Patches 2/3 and 3/3 are independent "fixes" of possible typos.
I'm not sure they are the right fixes, though.
They are more like reminders to show you where I couldn't figure
the grammatical structure.
Thanks, Akira
--
Akira Yokosawa (3):
utilities/fixsvgfonts-urwps.sh: Use symbol font available on F31
howto: Fix typo
intro: Fix typo
FAQ-BUILD.txt | 3 ++-
Makefile | 11 ++++++++++-
howto/howto.tex | 2 +-
intro/intro.tex | 2 +-
utilities/fixfonts-urwps.sh | 5 +----
utilities/fixfonts.sh | 4 +---
utilities/fixsvgfonts-urwps.sh | 8 +++-----
utilities/fixsvgfonts.sh | 4 +---
8 files changed, 20 insertions(+), 19 deletions(-)
--
2.17.1
^ permalink raw reply [flat|nested] 9+ messages in thread* [PATCH 1/3] utilities/fixsvgfonts-urwps.sh: Use symbol font available on F31 2020-01-16 21:54 [PATCH 0/3] Fix for Fedora31 Akira Yokosawa @ 2020-01-16 21:57 ` Akira Yokosawa 2020-01-16 21:59 ` [PATCH 2/3] howto: Fix typo Akira Yokosawa 2020-01-16 22:00 ` [PATCH 3/3] intro: " Akira Yokosawa 2 siblings, 0 replies; 9+ messages in thread From: Akira Yokosawa @ 2020-01-16 21:57 UTC (permalink / raw) To: Paul E. McKenney; +Cc: perfbook, Akira Yokosawa From 539b8d93663885fd9184ebee35bfd0ad91482687 Mon Sep 17 00:00:00 2001 From: Akira Yokosawa <akiyks@gmail.com> Date: Tue, 14 Jan 2020 21:35:06 +0900 Subject: [PATCH 1/3] utilities/fixsvgfonts-urwps.sh: Use symbol font available on F31 Fedora 31 upgraded pango to 1.44 which abandoned support of bitmap and type1 fonts such as StandardSymbolsPS.t1 [1]. This change affected some of .svg figures under advsync/. Use MdSymbol (.otf) as an alternative which should be available in texlive-collection-fontsextra on Fedora. Or it can be installed on its own as texlive-mdsymbol. Update Makefile and FAQ-BUILD.txt to add existence check of MdSymbol. Also remove a few unnecessary rules for symbol fonts in scripts for .eps files and Ubuntu's .svg files. [1]: https://blogs.gnome.org/mclasen/2019/05/25/pango-future-directions/ Signed-off-by: Akira Yokosawa <akiyks@gmail.com> --- FAQ-BUILD.txt | 3 ++- Makefile | 11 ++++++++++- utilities/fixfonts-urwps.sh | 5 +---- utilities/fixfonts.sh | 4 +--- utilities/fixsvgfonts-urwps.sh | 8 +++----- utilities/fixsvgfonts.sh | 4 +--- 6 files changed, 18 insertions(+), 17 deletions(-) diff --git a/FAQ-BUILD.txt b/FAQ-BUILD.txt index 56d60a3e..27780759 100644 --- a/FAQ-BUILD.txt +++ b/FAQ-BUILD.txt @@ -146,7 +146,7 @@ http://tex.stackexchange.com/questions/88423/ Following is a list of links to font packages perfbook - depends on as of October 2019 which are not included + depends on as of January 2020 which are not included in -fonts-recommended: https://www.ctan.org/pkg/newtx @@ -155,6 +155,7 @@ https://www.ctan.org/pkg/courier-scaled https://www.ctan.org/pkg/inconsolata https://www.ctan.org/pkg/newtxsf + https://www.ctan.org/pkg/mdsymbol (for Fedora/CentOS) Note 1: Manually installing a font package newer than the one already exists in your TeX installation is a tricky business diff --git a/Makefile b/Makefile index 7f2af1b1..06226d63 100644 --- a/Makefile +++ b/Makefile @@ -71,13 +71,14 @@ STEELFONT := $(shell fc-list | grep -c -i steel) URWPS := $(shell fc-list | grep "Nimbus Mono PS" | wc -l) # required font packages -FONTPACKAGES := $(shell kpsewhich newtxtext.sty nimbusmono.sty newtxtt.sty newtxsf.sty inconsolata.sty couriers.sty) +FONTPACKAGES := $(shell kpsewhich newtxtext.sty nimbusmono.sty newtxtt.sty newtxsf.sty inconsolata.sty couriers.sty mdsymbol.sty) NEWTXTEXT := $(findstring newtxtext,$(FONTPACKAGES)) NIMBUSMONO := $(findstring nimbusmono,$(FONTPACKAGES)) NEWTXTT := $(findstring newtxtt,$(FONTPACKAGES)) COURIERS := $(findstring couriers,$(FONTPACKAGES)) NEWTXSF := $(findstring newtxsf,$(FONTPACKAGES)) INCONSOLATA := $(findstring inconsolata,$(FONTPACKAGES)) +MDSYMBOL := $(findstring mdsymbol,$(FONTPACKAGES)) # for line break in error text define n @@ -91,6 +92,11 @@ FIXANEPSFONTS = utilities/fixanepsfonts.sh else FIXSVGFONTS = utilities/fixsvgfonts-urwps.sh FIXANEPSFONTS = utilities/fixanepsfonts-urwps.sh + ifeq ($(MDSYMBOL),) + NEEDMDSYMBOL := 1 + else + NEEDMDSYMBOL := 0 + endif endif STEELFONTID := $(shell fc-list | grep -i steel | grep -c Steel) @@ -302,6 +308,9 @@ ifeq ($(STEELFONTID),0) @sh $(FIXSVGFONTS) < $< | sed -e 's/Steel City Comic/Test/g' > $<i else @sh $(FIXSVGFONTS) < $< > $<i +endif +ifeq ($(NEEDMDSYMBOL),1) + $(error Font package 'mdsymbol' not found. See #9 in FAQ-BUILD.txt) endif @inkscape --export-pdf=$@ $<i > /dev/null 2>&1 @rm -f $<i diff --git a/utilities/fixfonts-urwps.sh b/utilities/fixfonts-urwps.sh index 7521f15b..f3e41fe3 100644 --- a/utilities/fixfonts-urwps.sh +++ b/utilities/fixfonts-urwps.sh @@ -40,7 +40,6 @@ sed -e 's+Times-Roman-BoldItalic+NimbusSans-BoldItalic+g' \ -e 's+Helvetica-Narrow+NimbusSansNarrow-Regular+g' \ -e 's+Helvetica-iso+NimbusSans-Regular+g' \ -e 's+Helvetica+NimbusSans-Regular+g' \ - -e 's+Symbol+StandardSymbolsPS+g' \ -e 's+Courier-BoldOblique+NimbusMonoPS-BoldItalic+g' \ -e 's+Courier-Oblique+NimbusMonoPS-Italic+g' \ -e 's+Courier-Bold+NimbusMonoPS-Bold+g' \ @@ -53,10 +52,8 @@ sed -e 's+Times-Roman-BoldItalic+NimbusSans-BoldItalic+g' \ -e 's+NimbusMonL-ReguObli+NimbusMonoPS-Italic+g' \ -e 's+NimbusMonL-Bold+NimbusMonoPS-Bold+g' \ -e 's+NimbusMonL-Regu+NimbusMonoPS-Regular+g' \ - -e 's+StandardSymL+StandardSymbolsPS+g' \ -e 's+NimbusMono-Regular-Bold+NimbusMonoPS-Bold+g' \ -e 's+NimbusMono-Regular+NimbusMonoPS-Regular+g' \ -e 's+NimbusSans-Regular-Italic+NimbusSans-Italic+g' \ -e 's+NimbusSans-Regular-BoldItalic+NimbusSans-BoldItalic+g' \ - -e 's+NimbusSans-Regular-Bold+NimbusSans-Bold+g' \ - -e 's+StandardSymbolsPS-+Symbol-+g' + -e 's+NimbusSans-Regular-Bold+NimbusSans-Bold+g' diff --git a/utilities/fixfonts.sh b/utilities/fixfonts.sh index f50ac6db..c5ea888a 100644 --- a/utilities/fixfonts.sh +++ b/utilities/fixfonts.sh @@ -38,12 +38,10 @@ sed -e 's+Times-Roman-BoldItalic+NimbusSanL-BoldItal+g' \ -e 's+Helvetica-Narrow+NimbusSanL-ReguCond+g' \ -e 's+Helvetica-iso+NimbusSanL-Regu+g' \ -e 's+Helvetica+NimbusSanL-Regu+g' \ - -e 's+Symbol+StandardSymL+g' \ -e 's+Courier-BoldOblique+NimbusMonL-BoldObli+g' \ -e 's+Courier-Oblique+NimbusMonL-ReguObli+g' \ -e 's+Courier-Bold+NimbusMonL-Bold+g' \ -e 's+Courier+NimbusMonL-Regu+g' \ -e 's+NimbusSanL-Regu-Italic+NimbusSanL-ReguItal+g' \ -e 's+NimbusSanL-Regu-BoldItalic+NimbusSanL-BoldItal+g' \ - -e 's+NimbusSanL-Regu-Bold+NimbusSanL-Bold+g' \ - -e 's+StardardSymL-+Symbol-+g' + -e 's+NimbusSanL-Regu-Bold+NimbusSanL-Bold+g' diff --git a/utilities/fixsvgfonts-urwps.sh b/utilities/fixsvgfonts-urwps.sh index a917fea2..55a5a3f2 100644 --- a/utilities/fixsvgfonts-urwps.sh +++ b/utilities/fixsvgfonts-urwps.sh @@ -11,13 +11,11 @@ sed -e 's+family:Helvetica+family:Nimbus Sans+g' \ -e 's+cation:Sans+cation:Nimbus Sans+g' \ -e 's+family:Courier+family:Nimbus Mono PS+g' \ -e 's+family="Courier+family="Nimbus Mono PS+g' \ - -e 's+family:Symbol+family:Standard Symbols PS+g' \ - -e 's+cation:Symbol+cation:Standard Symbols PS+g' \ + -e 's+family:Symbol+family:MdSymbol+g' \ + -e 's+cation:Symbol+cation:MdSymbol+g' \ -e 's+family:Nimbus Sans L+family:Nimbus Sans+g' \ -e 's+family="Nimbus Sans L+family="Nimbus Sans+g' \ -e 's+cation:Nimbus Sans L+cation:Nimbus Sans+g' \ -e 's+family:Nimbus Mono L+family:Nimbus Mono PS+g' \ -e 's+family="Nimbus Mono L+family="Nimbus Mono PS+g' \ - -e 's+cation:Nimbus Mono L+cation:Nimbus Mono PS+g' \ - -e 's+family:Standard Symbols L+family:Standard Symbols PS+g' \ - -e 's+cation:Standard Symbols L+cation:Standard Symbols PS+g' + -e 's+cation:Nimbus Mono L+cation:Nimbus Mono PS+g' diff --git a/utilities/fixsvgfonts.sh b/utilities/fixsvgfonts.sh index 287d3e2c..657c3001 100644 --- a/utilities/fixsvgfonts.sh +++ b/utilities/fixsvgfonts.sh @@ -10,6 +10,4 @@ sed -e 's+family:Helvetica+family:Nimbus Sans L+g' \ -e 's+family:Sans+family:Nimbus Sans L+g' \ -e 's+cation:Sans+cation:Nimbus Sans L+g' \ -e 's+family:Courier+family:Nimbus Mono L+g' \ - -e 's+family="Courier+family="Nimbus Mono L+g' \ - -e 's+family:Symbol+family:Standard Symbols L+g' \ - -e 's+cation:Symbol+cation:Standard Symbols L+g' + -e 's+family="Courier+family="Nimbus Mono L+g' -- 2.17.1 ^ permalink raw reply related [flat|nested] 9+ messages in thread
* [PATCH 2/3] howto: Fix typo 2020-01-16 21:54 [PATCH 0/3] Fix for Fedora31 Akira Yokosawa 2020-01-16 21:57 ` [PATCH 1/3] utilities/fixsvgfonts-urwps.sh: Use symbol font available on F31 Akira Yokosawa @ 2020-01-16 21:59 ` Akira Yokosawa 2020-01-17 3:36 ` Paul E. McKenney 2020-01-16 22:00 ` [PATCH 3/3] intro: " Akira Yokosawa 2 siblings, 1 reply; 9+ messages in thread From: Akira Yokosawa @ 2020-01-16 21:59 UTC (permalink / raw) To: Paul E. McKenney; +Cc: perfbook, Akira Yokosawa From cd352d3dfd20d8fcfdddafe5547ad191cbdda37e Mon Sep 17 00:00:00 2001 From: Akira Yokosawa <akiyks@gmail.com> Date: Mon, 13 Jan 2020 16:18:19 +0900 Subject: [PATCH 2/3] howto: Fix typo Signed-off-by: Akira Yokosawa <akiyks@gmail.com> --- howto/howto.tex | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/howto/howto.tex b/howto/howto.tex index bbdacbf1..fe80cca8 100644 --- a/howto/howto.tex +++ b/howto/howto.tex @@ -23,7 +23,7 @@ Parallel programming is not as hard as some say, and we hope that this book makes your parallel-programming projects easier and more fun. -In short, where parallel programming once focused on science, research, +In short, while parallel programming once focused on science, research, and grand-challenge projects, it is quickly becoming an engineering discipline. We therefore examine specific parallel-programming tasks -- 2.17.1 ^ permalink raw reply related [flat|nested] 9+ messages in thread
* Re: [PATCH 2/3] howto: Fix typo 2020-01-16 21:59 ` [PATCH 2/3] howto: Fix typo Akira Yokosawa @ 2020-01-17 3:36 ` Paul E. McKenney 2020-01-18 10:52 ` Akira Yokosawa 0 siblings, 1 reply; 9+ messages in thread From: Paul E. McKenney @ 2020-01-17 3:36 UTC (permalink / raw) To: Akira Yokosawa; +Cc: perfbook On Fri, Jan 17, 2020 at 06:59:10AM +0900, Akira Yokosawa wrote: > >From cd352d3dfd20d8fcfdddafe5547ad191cbdda37e Mon Sep 17 00:00:00 2001 > From: Akira Yokosawa <akiyks@gmail.com> > Date: Mon, 13 Jan 2020 16:18:19 +0900 > Subject: [PATCH 2/3] howto: Fix typo > > Signed-off-by: Akira Yokosawa <akiyks@gmail.com> I took the other two, thank you very much! I treated this one as a bug report, again, thank you! Please see below for the corresponding commit. Thoughts? Thanx, Paul > --- > howto/howto.tex | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/howto/howto.tex b/howto/howto.tex > index bbdacbf1..fe80cca8 100644 > --- a/howto/howto.tex > +++ b/howto/howto.tex > @@ -23,7 +23,7 @@ Parallel programming is not as hard as some say, and we hope > that this book makes your parallel-programming projects easier and > more fun. > > -In short, where parallel programming once focused on science, research, > +In short, while parallel programming once focused on science, research, > and grand-challenge projects, it is quickly becoming an engineering > discipline. > We therefore examine specific parallel-programming tasks > -- > 2.17.1 ------------------------------------------------------------------------ commit b094718ddbe4256e606a41c660b4d4f1836baa66 Author: Paul E. McKenney <paulmck@kernel.org> Date: Thu Jan 16 19:31:26 2020 -0800 howto: Word parallel-programming-as-engineering less obscurely The "where ... once ... becoming" wording might be legal English, it is a bit obscure and less than friendly to those whose native language is not English. This commit therefore rewrites the offending paragraph. Reported-by: Akira Yokosawa <akiyks@gmail.com> Signed-off-by: Paul E. McKenney <paulmck@kernel.org> diff --git a/howto/howto.tex b/howto/howto.tex index bbdacbf..8a93774 100644 --- a/howto/howto.tex +++ b/howto/howto.tex @@ -23,11 +23,12 @@ Parallel programming is not as hard as some say, and we hope that this book makes your parallel-programming projects easier and more fun. -In short, where parallel programming once focused on science, research, -and grand-challenge projects, it is quickly becoming an engineering -discipline. -We therefore examine specific parallel-programming tasks -and describe how to approach them. +In short, the focus of parallel programming is quickly shifting away +from science, research, and grand-challenge projects. +And this is all to the good, because it means that parallel programming +is finally becoming an engineering discipline. +Therefore, as befits an engineering discipline, this book examines +specific parallel-programming tasks and describes how to approach them. In some surprisingly common cases, they can even be automated. This book is written in the hope that presenting the engineering ^ permalink raw reply related [flat|nested] 9+ messages in thread
* Re: [PATCH 2/3] howto: Fix typo 2020-01-17 3:36 ` Paul E. McKenney @ 2020-01-18 10:52 ` Akira Yokosawa 2020-01-18 19:42 ` Paul E. McKenney 0 siblings, 1 reply; 9+ messages in thread From: Akira Yokosawa @ 2020-01-18 10:52 UTC (permalink / raw) To: Paul E. McKenney; +Cc: perfbook, Akira Yokosawa On Thu, 16 Jan 2020 19:36:08 -0800, Paul E. McKenney wrote: > On Fri, Jan 17, 2020 at 06:59:10AM +0900, Akira Yokosawa wrote: >> >From cd352d3dfd20d8fcfdddafe5547ad191cbdda37e Mon Sep 17 00:00:00 2001 >> From: Akira Yokosawa <akiyks@gmail.com> >> Date: Mon, 13 Jan 2020 16:18:19 +0900 >> Subject: [PATCH 2/3] howto: Fix typo >> >> Signed-off-by: Akira Yokosawa <akiyks@gmail.com> > > I took the other two, thank you very much! > > I treated this one as a bug report, again, thank you! Please see below > for the corresponding commit. Thoughts? Please find inline comments below. > > Thanx, Paul > >> --- >> howto/howto.tex | 2 +- >> 1 file changed, 1 insertion(+), 1 deletion(-) >> >> diff --git a/howto/howto.tex b/howto/howto.tex >> index bbdacbf1..fe80cca8 100644 >> --- a/howto/howto.tex >> +++ b/howto/howto.tex >> @@ -23,7 +23,7 @@ Parallel programming is not as hard as some say, and we hope >> that this book makes your parallel-programming projects easier and >> more fun. >> >> -In short, where parallel programming once focused on science, research, >> +In short, while parallel programming once focused on science, research, >> and grand-challenge projects, it is quickly becoming an engineering >> discipline. >> We therefore examine specific parallel-programming tasks >> -- >> 2.17.1 > > ------------------------------------------------------------------------ > > commit b094718ddbe4256e606a41c660b4d4f1836baa66 > Author: Paul E. McKenney <paulmck@kernel.org> > Date: Thu Jan 16 19:31:26 2020 -0800 > > howto: Word parallel-programming-as-engineering less obscurely > > The "where ... once ... becoming" wording might be legal English, it > is a bit obscure and less than friendly to those whose native language > is not English. This commit therefore rewrites the offending paragraph. > > Reported-by: Akira Yokosawa <akiyks@gmail.com> > Signed-off-by: Paul E. McKenney <paulmck@kernel.org> > > diff --git a/howto/howto.tex b/howto/howto.tex > index bbdacbf..8a93774 100644 > --- a/howto/howto.tex > +++ b/howto/howto.tex > @@ -23,11 +23,12 @@ Parallel programming is not as hard as some say, and we hope > that this book makes your parallel-programming projects easier and > more fun. > > -In short, where parallel programming once focused on science, research, > -and grand-challenge projects, it is quickly becoming an engineering > -discipline. > -We therefore examine specific parallel-programming tasks > -and describe how to approach them. > +In short, the focus of parallel programming is quickly shifting away > +from science, research, and grand-challenge projects. > +And this is all to the good, because it means that parallel programming > +is finally becoming an engineering discipline. > +Therefore, as befits an engineering discipline, this book examines > +specific parallel-programming tasks and describes how to approach them. > In some surprisingly common cases, they can even be automated. Well, nowadays, you can try "google translate". It recognizes the use of "where" as a subordinate conjunction in the original paragraph. I don't know why such a use case of "where" is not on my dictionary... And saying "shifting away from" could be misleading because "science, research, and grand-challenge projects" are still driving parallel programming. So maybe it might be better to revert this change, or to rephrase some more. Thanks, Akira > > This book is written in the hope that presenting the engineering > ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [PATCH 2/3] howto: Fix typo 2020-01-18 10:52 ` Akira Yokosawa @ 2020-01-18 19:42 ` Paul E. McKenney 2020-01-18 23:11 ` Akira Yokosawa 0 siblings, 1 reply; 9+ messages in thread From: Paul E. McKenney @ 2020-01-18 19:42 UTC (permalink / raw) To: Akira Yokosawa; +Cc: perfbook On Sat, Jan 18, 2020 at 07:52:29PM +0900, Akira Yokosawa wrote: > On Thu, 16 Jan 2020 19:36:08 -0800, Paul E. McKenney wrote: > > On Fri, Jan 17, 2020 at 06:59:10AM +0900, Akira Yokosawa wrote: > >> >From cd352d3dfd20d8fcfdddafe5547ad191cbdda37e Mon Sep 17 00:00:00 2001 > >> From: Akira Yokosawa <akiyks@gmail.com> > >> Date: Mon, 13 Jan 2020 16:18:19 +0900 > >> Subject: [PATCH 2/3] howto: Fix typo > >> > >> Signed-off-by: Akira Yokosawa <akiyks@gmail.com> > > > > I took the other two, thank you very much! > > > > I treated this one as a bug report, again, thank you! Please see below > > for the corresponding commit. Thoughts? > > Please find inline comments below. > > > > > Thanx, Paul > > > >> --- > >> howto/howto.tex | 2 +- > >> 1 file changed, 1 insertion(+), 1 deletion(-) > >> > >> diff --git a/howto/howto.tex b/howto/howto.tex > >> index bbdacbf1..fe80cca8 100644 > >> --- a/howto/howto.tex > >> +++ b/howto/howto.tex > >> @@ -23,7 +23,7 @@ Parallel programming is not as hard as some say, and we hope > >> that this book makes your parallel-programming projects easier and > >> more fun. > >> > >> -In short, where parallel programming once focused on science, research, > >> +In short, while parallel programming once focused on science, research, > >> and grand-challenge projects, it is quickly becoming an engineering > >> discipline. > >> We therefore examine specific parallel-programming tasks > >> -- > >> 2.17.1 > > > > ------------------------------------------------------------------------ > > > > commit b094718ddbe4256e606a41c660b4d4f1836baa66 > > Author: Paul E. McKenney <paulmck@kernel.org> > > Date: Thu Jan 16 19:31:26 2020 -0800 > > > > howto: Word parallel-programming-as-engineering less obscurely > > > > The "where ... once ... becoming" wording might be legal English, it > > is a bit obscure and less than friendly to those whose native language > > is not English. This commit therefore rewrites the offending paragraph. > > > > Reported-by: Akira Yokosawa <akiyks@gmail.com> > > Signed-off-by: Paul E. McKenney <paulmck@kernel.org> > > > > diff --git a/howto/howto.tex b/howto/howto.tex > > index bbdacbf..8a93774 100644 > > --- a/howto/howto.tex > > +++ b/howto/howto.tex > > @@ -23,11 +23,12 @@ Parallel programming is not as hard as some say, and we hope > > that this book makes your parallel-programming projects easier and > > more fun. > > > > -In short, where parallel programming once focused on science, research, > > -and grand-challenge projects, it is quickly becoming an engineering > > -discipline. > > -We therefore examine specific parallel-programming tasks > > -and describe how to approach them. > > +In short, the focus of parallel programming is quickly shifting away > > +from science, research, and grand-challenge projects. > > +And this is all to the good, because it means that parallel programming > > +is finally becoming an engineering discipline. > > +Therefore, as befits an engineering discipline, this book examines > > +specific parallel-programming tasks and describes how to approach them. > > In some surprisingly common cases, they can even be automated. > > Well, nowadays, you can try "google translate". > It recognizes the use of "where" as a subordinate conjunction in the > original paragraph. Huh. I didn't realize that Google Translate could recognize parts of speech. That would be quite nice! Except that I am still not seeing how to make it do that. What is the trick? Or was the trick for you to translate it into Japanese and used your knowledge of Japanese and Google Translate's mapping of words and phrases to identify the part of speech? > I don't know why such a use case of "where" is not on my dictionary... I have a printed copy of The Shorter Oxford English Dictionary (the larger version was more than ten dictionary-sized volumes back in the mid-1970s), and it says in definition B4: Introducing a clause as obj. of the verb or preposition, or as a predicate: orig., a case in which, a person to whom (now only spec. as the object of love or marriage): now, the respect or particular in which. So my use is a bit old-fashioned, which might be why it is not in your dictionary. But I have the hair color to match old fashioned, so maybe it was OK while it lasted. ;-) > And saying "shifting away from" could be misleading because "science, > research, and grand-challenge projects" are still driving parallel > programming. Excellent point, thank you! I certainly should not unnecessarily alienate people in those fields. > So maybe it might be better to revert this change, or to rephrase some more. How about the following instead? Thanx, Paul ------------------------------------------------------------------------ commit 64cf378960689deef3d23359eaddea9a21ee683d Author: Paul E. McKenney <paulmck@kernel.org> Date: Thu Jan 16 19:31:26 2020 -0800 howto: Word parallel-programming-as-engineering less obscurely The "where ... once ... becoming" wording might be legal English, it is a bit obscure and less than friendly to those whose native language is not English. This commit therefore rewrites the offending paragraph. Reported-by: Akira Yokosawa <akiyks@gmail.com> Signed-off-by: Paul E. McKenney <paulmck@kernel.org> diff --git a/howto/howto.tex b/howto/howto.tex index bbdacbf..9d73269 100644 --- a/howto/howto.tex +++ b/howto/howto.tex @@ -23,11 +23,12 @@ Parallel programming is not as hard as some say, and we hope that this book makes your parallel-programming projects easier and more fun. -In short, where parallel programming once focused on science, research, -and grand-challenge projects, it is quickly becoming an engineering -discipline. -We therefore examine specific parallel-programming tasks -and describe how to approach them. +In short, parallel programming is no longer focused solely on science, +research, and grand-challenge projects. +And this is all to the good, because it means that parallel programming +is finally becoming an engineering discipline. +Therefore, as befits an engineering discipline, this book examines +specific parallel-programming tasks and describes how to approach them. In some surprisingly common cases, they can even be automated. This book is written in the hope that presenting the engineering ^ permalink raw reply related [flat|nested] 9+ messages in thread
* Re: [PATCH 2/3] howto: Fix typo 2020-01-18 19:42 ` Paul E. McKenney @ 2020-01-18 23:11 ` Akira Yokosawa 2020-01-19 5:46 ` Paul E. McKenney 0 siblings, 1 reply; 9+ messages in thread From: Akira Yokosawa @ 2020-01-18 23:11 UTC (permalink / raw) To: Paul E. McKenney; +Cc: perfbook, Akira Yokosawa On Sat, 18 Jan 2020 11:42:13 -0800, Paul E. McKenney wrote: > On Sat, Jan 18, 2020 at 07:52:29PM +0900, Akira Yokosawa wrote: >> On Thu, 16 Jan 2020 19:36:08 -0800, Paul E. McKenney wrote: >>> On Fri, Jan 17, 2020 at 06:59:10AM +0900, Akira Yokosawa wrote: >>>> >From cd352d3dfd20d8fcfdddafe5547ad191cbdda37e Mon Sep 17 00:00:00 2001 >>>> From: Akira Yokosawa <akiyks@gmail.com> >>>> Date: Mon, 13 Jan 2020 16:18:19 +0900 >>>> Subject: [PATCH 2/3] howto: Fix typo >>>> >>>> Signed-off-by: Akira Yokosawa <akiyks@gmail.com> >>> >>> I took the other two, thank you very much! >>> >>> I treated this one as a bug report, again, thank you! Please see below >>> for the corresponding commit. Thoughts? >> >> Please find inline comments below. >> >>> >>> Thanx, Paul >>> >>>> --- >>>> howto/howto.tex | 2 +- >>>> 1 file changed, 1 insertion(+), 1 deletion(-) >>>> >>>> diff --git a/howto/howto.tex b/howto/howto.tex >>>> index bbdacbf1..fe80cca8 100644 >>>> --- a/howto/howto.tex >>>> +++ b/howto/howto.tex >>>> @@ -23,7 +23,7 @@ Parallel programming is not as hard as some say, and we hope >>>> that this book makes your parallel-programming projects easier and >>>> more fun. >>>> >>>> -In short, where parallel programming once focused on science, research, >>>> +In short, while parallel programming once focused on science, research, >>>> and grand-challenge projects, it is quickly becoming an engineering >>>> discipline. >>>> We therefore examine specific parallel-programming tasks >>>> -- >>>> 2.17.1 >>> >>> ------------------------------------------------------------------------ >>> >>> commit b094718ddbe4256e606a41c660b4d4f1836baa66 >>> Author: Paul E. McKenney <paulmck@kernel.org> >>> Date: Thu Jan 16 19:31:26 2020 -0800 >>> >>> howto: Word parallel-programming-as-engineering less obscurely >>> >>> The "where ... once ... becoming" wording might be legal English, it >>> is a bit obscure and less than friendly to those whose native language >>> is not English. This commit therefore rewrites the offending paragraph. >>> >>> Reported-by: Akira Yokosawa <akiyks@gmail.com> >>> Signed-off-by: Paul E. McKenney <paulmck@kernel.org> >>> >>> diff --git a/howto/howto.tex b/howto/howto.tex >>> index bbdacbf..8a93774 100644 >>> --- a/howto/howto.tex >>> +++ b/howto/howto.tex >>> @@ -23,11 +23,12 @@ Parallel programming is not as hard as some say, and we hope >>> that this book makes your parallel-programming projects easier and >>> more fun. >>> >>> -In short, where parallel programming once focused on science, research, >>> -and grand-challenge projects, it is quickly becoming an engineering >>> -discipline. >>> -We therefore examine specific parallel-programming tasks >>> -and describe how to approach them. >>> +In short, the focus of parallel programming is quickly shifting away >>> +from science, research, and grand-challenge projects. >>> +And this is all to the good, because it means that parallel programming >>> +is finally becoming an engineering discipline. >>> +Therefore, as befits an engineering discipline, this book examines >>> +specific parallel-programming tasks and describes how to approach them. >>> In some surprisingly common cases, they can even be automated. >> >> Well, nowadays, you can try "google translate". >> It recognizes the use of "where" as a subordinate conjunction in the >> original paragraph. > > Huh. I didn't realize that Google Translate could recognize parts of > speech. That would be quite nice! Except that I am still not seeing > how to make it do that. What is the trick? When you select English -> Japanese, it is translated most of the time as the same as In short, although parallel programming once focused on science, research, and grand-challenge projects, it is quickly becoming an engineering discipline. "Most of the time" is due to the variation of translation for their machine learning purposes. English -> Spanish translation simply maps "where" to "donde". "Donde" does not mean "although" in Spanish, I guess. Translation between European languages tends to be better than that involving Japanese (especially regarding the delicate choice of particles such as "ha" and "ga"), but not in this case. > > Or was the trick for you to translate it into Japanese and used your > knowledge of Japanese and Google Translate's mapping of words and phrases > to identify the part of speech? > >> I don't know why such a use case of "where" is not on my dictionary... > > I have a printed copy of The Shorter Oxford English Dictionary (the > larger version was more than ten dictionary-sized volumes back in > the mid-1970s), and it says in definition B4: > > Introducing a clause as obj. of the verb or preposition, or > as a predicate: orig., a case in which, a person to whom > (now only spec. as the object of love or marriage): now, > the respect or particular in which. > > So my use is a bit old-fashioned, which might be why it is not in > your dictionary. But I have the hair color to match old fashioned, > so maybe it was OK while it lasted. ;-) In https://en.wiktionary.org/wiki/where#English, 1st entry in Conjunction reads: 1. While on the contrary; although; whereas. It has a few quotations which match the pattern in question. > >> And saying "shifting away from" could be misleading because "science, >> research, and grand-challenge projects" are still driving parallel >> programming. > > Excellent point, thank you! I certainly should not unnecessarily alienate > people in those fields. > >> So maybe it might be better to revert this change, or to rephrase some more. > > How about the following instead? > > Thanx, Paul > > ------------------------------------------------------------------------ > > commit 64cf378960689deef3d23359eaddea9a21ee683d > Author: Paul E. McKenney <paulmck@kernel.org> > Date: Thu Jan 16 19:31:26 2020 -0800 > > howto: Word parallel-programming-as-engineering less obscurely > > The "where ... once ... becoming" wording might be legal English, it > is a bit obscure and less than friendly to those whose native language > is not English. This commit therefore rewrites the offending paragraph. > > Reported-by: Akira Yokosawa <akiyks@gmail.com> > Signed-off-by: Paul E. McKenney <paulmck@kernel.org> > > diff --git a/howto/howto.tex b/howto/howto.tex > index bbdacbf..9d73269 100644 > --- a/howto/howto.tex > +++ b/howto/howto.tex > @@ -23,11 +23,12 @@ Parallel programming is not as hard as some say, and we hope > that this book makes your parallel-programming projects easier and > more fun. > > -In short, where parallel programming once focused on science, research, > -and grand-challenge projects, it is quickly becoming an engineering > -discipline. > -We therefore examine specific parallel-programming tasks > -and describe how to approach them. > +In short, parallel programming is no longer focused solely on science, > +research, and grand-challenge projects. > +And this is all to the good, because it means that parallel programming > +is finally becoming an engineering discipline. > +Therefore, as befits an engineering discipline, this book examines > +specific parallel-programming tasks and describes how to approach them. Looks good to me! Thanks, Akira > In some surprisingly common cases, they can even be automated. > > This book is written in the hope that presenting the engineering > ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [PATCH 2/3] howto: Fix typo 2020-01-18 23:11 ` Akira Yokosawa @ 2020-01-19 5:46 ` Paul E. McKenney 0 siblings, 0 replies; 9+ messages in thread From: Paul E. McKenney @ 2020-01-19 5:46 UTC (permalink / raw) To: Akira Yokosawa; +Cc: perfbook On Sun, Jan 19, 2020 at 08:11:48AM +0900, Akira Yokosawa wrote: > On Sat, 18 Jan 2020 11:42:13 -0800, Paul E. McKenney wrote: > > On Sat, Jan 18, 2020 at 07:52:29PM +0900, Akira Yokosawa wrote: > >> On Thu, 16 Jan 2020 19:36:08 -0800, Paul E. McKenney wrote: > >>> On Fri, Jan 17, 2020 at 06:59:10AM +0900, Akira Yokosawa wrote: > >>>> >From cd352d3dfd20d8fcfdddafe5547ad191cbdda37e Mon Sep 17 00:00:00 2001 > >>>> From: Akira Yokosawa <akiyks@gmail.com> > >>>> Date: Mon, 13 Jan 2020 16:18:19 +0900 > >>>> Subject: [PATCH 2/3] howto: Fix typo > >>>> > >>>> Signed-off-by: Akira Yokosawa <akiyks@gmail.com> > >>> > >>> I took the other two, thank you very much! > >>> > >>> I treated this one as a bug report, again, thank you! Please see below > >>> for the corresponding commit. Thoughts? > >> > >> Please find inline comments below. > >> > >>> > >>> Thanx, Paul > >>> > >>>> --- > >>>> howto/howto.tex | 2 +- > >>>> 1 file changed, 1 insertion(+), 1 deletion(-) > >>>> > >>>> diff --git a/howto/howto.tex b/howto/howto.tex > >>>> index bbdacbf1..fe80cca8 100644 > >>>> --- a/howto/howto.tex > >>>> +++ b/howto/howto.tex > >>>> @@ -23,7 +23,7 @@ Parallel programming is not as hard as some say, and we hope > >>>> that this book makes your parallel-programming projects easier and > >>>> more fun. > >>>> > >>>> -In short, where parallel programming once focused on science, research, > >>>> +In short, while parallel programming once focused on science, research, > >>>> and grand-challenge projects, it is quickly becoming an engineering > >>>> discipline. > >>>> We therefore examine specific parallel-programming tasks > >>>> -- > >>>> 2.17.1 > >>> > >>> ------------------------------------------------------------------------ > >>> > >>> commit b094718ddbe4256e606a41c660b4d4f1836baa66 > >>> Author: Paul E. McKenney <paulmck@kernel.org> > >>> Date: Thu Jan 16 19:31:26 2020 -0800 > >>> > >>> howto: Word parallel-programming-as-engineering less obscurely > >>> > >>> The "where ... once ... becoming" wording might be legal English, it > >>> is a bit obscure and less than friendly to those whose native language > >>> is not English. This commit therefore rewrites the offending paragraph. > >>> > >>> Reported-by: Akira Yokosawa <akiyks@gmail.com> > >>> Signed-off-by: Paul E. McKenney <paulmck@kernel.org> > >>> > >>> diff --git a/howto/howto.tex b/howto/howto.tex > >>> index bbdacbf..8a93774 100644 > >>> --- a/howto/howto.tex > >>> +++ b/howto/howto.tex > >>> @@ -23,11 +23,12 @@ Parallel programming is not as hard as some say, and we hope > >>> that this book makes your parallel-programming projects easier and > >>> more fun. > >>> > >>> -In short, where parallel programming once focused on science, research, > >>> -and grand-challenge projects, it is quickly becoming an engineering > >>> -discipline. > >>> -We therefore examine specific parallel-programming tasks > >>> -and describe how to approach them. > >>> +In short, the focus of parallel programming is quickly shifting away > >>> +from science, research, and grand-challenge projects. > >>> +And this is all to the good, because it means that parallel programming > >>> +is finally becoming an engineering discipline. > >>> +Therefore, as befits an engineering discipline, this book examines > >>> +specific parallel-programming tasks and describes how to approach them. > >>> In some surprisingly common cases, they can even be automated. > >> > >> Well, nowadays, you can try "google translate". > >> It recognizes the use of "where" as a subordinate conjunction in the > >> original paragraph. > > > > Huh. I didn't realize that Google Translate could recognize parts of > > speech. That would be quite nice! Except that I am still not seeing > > how to make it do that. What is the trick? > > When you select English -> Japanese, it is translated most of the time > as the same as > > In short, although parallel programming once focused on science, > research, and grand-challenge projects, it is quickly becoming > an engineering discipline. > > "Most of the time" is due to the variation of translation for their > machine learning purposes. > > English -> Spanish translation simply maps "where" to "donde". > "Donde" does not mean "although" in Spanish, I guess. > > Translation between European languages tends to be better than > that involving Japanese (especially regarding the delicate choice of > particles such as "ha" and "ga"), but not in this case. Interesting, thank you! > > Or was the trick for you to translate it into Japanese and used your > > knowledge of Japanese and Google Translate's mapping of words and phrases > > to identify the part of speech? > > > >> I don't know why such a use case of "where" is not on my dictionary... > > > > I have a printed copy of The Shorter Oxford English Dictionary (the > > larger version was more than ten dictionary-sized volumes back in > > the mid-1970s), and it says in definition B4: > > > > Introducing a clause as obj. of the verb or preposition, or > > as a predicate: orig., a case in which, a person to whom > > (now only spec. as the object of love or marriage): now, > > the respect or particular in which. > > > > So my use is a bit old-fashioned, which might be why it is not in > > your dictionary. But I have the hair color to match old fashioned, > > so maybe it was OK while it lasted. ;-) > > In https://en.wiktionary.org/wiki/where#English, > 1st entry in Conjunction reads: > > 1. While on the contrary; although; whereas. > > It has a few quotations which match the pattern in question. > > > > >> And saying "shifting away from" could be misleading because "science, > >> research, and grand-challenge projects" are still driving parallel > >> programming. > > > > Excellent point, thank you! I certainly should not unnecessarily alienate > > people in those fields. > > > >> So maybe it might be better to revert this change, or to rephrase some more. > > > > How about the following instead? > > > > Thanx, Paul > > > > ------------------------------------------------------------------------ > > > > commit 64cf378960689deef3d23359eaddea9a21ee683d > > Author: Paul E. McKenney <paulmck@kernel.org> > > Date: Thu Jan 16 19:31:26 2020 -0800 > > > > howto: Word parallel-programming-as-engineering less obscurely > > > > The "where ... once ... becoming" wording might be legal English, it > > is a bit obscure and less than friendly to those whose native language > > is not English. This commit therefore rewrites the offending paragraph. > > > > Reported-by: Akira Yokosawa <akiyks@gmail.com> > > Signed-off-by: Paul E. McKenney <paulmck@kernel.org> > > > > diff --git a/howto/howto.tex b/howto/howto.tex > > index bbdacbf..9d73269 100644 > > --- a/howto/howto.tex > > +++ b/howto/howto.tex > > @@ -23,11 +23,12 @@ Parallel programming is not as hard as some say, and we hope > > that this book makes your parallel-programming projects easier and > > more fun. > > > > -In short, where parallel programming once focused on science, research, > > -and grand-challenge projects, it is quickly becoming an engineering > > -discipline. > > -We therefore examine specific parallel-programming tasks > > -and describe how to approach them. > > +In short, parallel programming is no longer focused solely on science, > > +research, and grand-challenge projects. > > +And this is all to the good, because it means that parallel programming > > +is finally becoming an engineering discipline. > > +Therefore, as befits an engineering discipline, this book examines > > +specific parallel-programming tasks and describes how to approach them. > > Looks good to me! Very good, one down! ;-) Thanx, Paul > Thanks, Akira > > > In some surprisingly common cases, they can even be automated. > > > > This book is written in the hope that presenting the engineering > > ^ permalink raw reply [flat|nested] 9+ messages in thread
* [PATCH 3/3] intro: Fix typo 2020-01-16 21:54 [PATCH 0/3] Fix for Fedora31 Akira Yokosawa 2020-01-16 21:57 ` [PATCH 1/3] utilities/fixsvgfonts-urwps.sh: Use symbol font available on F31 Akira Yokosawa 2020-01-16 21:59 ` [PATCH 2/3] howto: Fix typo Akira Yokosawa @ 2020-01-16 22:00 ` Akira Yokosawa 2 siblings, 0 replies; 9+ messages in thread From: Akira Yokosawa @ 2020-01-16 22:00 UTC (permalink / raw) To: Paul E. McKenney; +Cc: perfbook, Akira Yokosawa From 865d0b46e811f6a719f4af1a59d65c6f70185108 Mon Sep 17 00:00:00 2001 From: Akira Yokosawa <akiyks@gmail.com> Date: Mon, 13 Jan 2020 19:51:52 +0900 Subject: [PATCH 3/3] intro: Fix typo Signed-off-by: Akira Yokosawa <akiyks@gmail.com> --- intro/intro.tex | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/intro/intro.tex b/intro/intro.tex index beda0464..e3ec3a43 100644 --- a/intro/intro.tex +++ b/intro/intro.tex @@ -361,7 +361,7 @@ which shows that writing single-threaded code and simply waiting a year or two for the CPUs to catch up may no longer be an option. Given the recent trends on the part of all major manufacturers towards multicore/multithreaded systems, parallelism is the way to go for -those wanting the avail themselves of the full performance of their +those wanting to avail themselves of the full performance of their systems. Even so, the first goal is performance rather than scalability, -- 2.17.1 ^ permalink raw reply related [flat|nested] 9+ messages in thread
end of thread, other threads:[~2020-01-19 5:46 UTC | newest] Thread overview: 9+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2020-01-16 21:54 [PATCH 0/3] Fix for Fedora31 Akira Yokosawa 2020-01-16 21:57 ` [PATCH 1/3] utilities/fixsvgfonts-urwps.sh: Use symbol font available on F31 Akira Yokosawa 2020-01-16 21:59 ` [PATCH 2/3] howto: Fix typo Akira Yokosawa 2020-01-17 3:36 ` Paul E. McKenney 2020-01-18 10:52 ` Akira Yokosawa 2020-01-18 19:42 ` Paul E. McKenney 2020-01-18 23:11 ` Akira Yokosawa 2020-01-19 5:46 ` Paul E. McKenney 2020-01-16 22:00 ` [PATCH 3/3] intro: " Akira Yokosawa
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.