Fix for Fedora31
cover Fix for Fedora31
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(-)
Signature · 1 line
2.17.1
PATCH 1/3 utilities/fixsvgfonts-urwps.sh: Use symbol font available on F31
From 539b8d93663885fd9184ebee35bfd0ad91482687 Mon Sep 17 00:00:00 2001
From: Akira Yokosawa <[email protected]>
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/
--- 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(-)
FAQ-BUILD.txt +2 -1
@@ -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
Makefile +10 -1
@@ -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
utilities/fixfonts-urwps.sh +1 -4
@@ -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'
utilities/fixfonts.sh +1 -3
@@ -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'
utilities/fixsvgfonts-urwps.sh +3 -5
@@ -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'
utilities/fixsvgfonts.sh +1 -3
@@ -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'
Signature · 1 line
2.17.1
PATCH 2/3 howto: Fix typo
In reply to Akira YokosawaFrom cd352d3dfd20d8fcfdddafe5547ad191cbdda37e Mon Sep 17 00:00:00 2001
From: Akira Yokosawa <[email protected]>
Date: Mon, 13 Jan 2020 16:18:19 +0900
Subject: [PATCH 2/3] howto: Fix typo
--- howto/howto.tex | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
howto/howto.tex +1 -1
@@ -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
Signature · 1 line
2.17.1
Re: [PATCH 2/3] howto: Fix typo
Quoted 6 lines · Akira Yokosawa
Quoted 1 line
From
cd352d3dfd20d8fcfdddafe5547ad191cbdda37eMon Sep 17 00:00:00 2001From: Akira Yokosawa <[email protected]>
Date: Mon, 13 Jan 2020 16:18:19 +0900
Subject: [PATCH 2/3] howto: Fix typoSigned-off-by Akira Yokosawa <[email protected]>
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
Quoted 19 lines
--- howto/howto.tex | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)howto/howto.tex +1
-1@@ -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 tasksSignature · 1 line
2.17.1
------------------------------------------------------------------------
commit b094718ddbe4256e606a41c660b4d4f1836baa66
Author: Paul E. McKenney <[email protected]> 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.
howto/howto.tex +6 -5
@@ -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
Re: [PATCH 2/3] howto: Fix typo
Quoted 6 lines · Paul E. McKenney
Quoted 5 lines · Akira Yokosawa
Quoted 1 line
From
cd352d3dfd20d8fcfdddafe5547ad191cbdda37eMon Sep 17 00:00:00 2001From: Akira Yokosawa <[email protected]>
Date: Mon, 13 Jan 2020 16:18:19 +0900
Subject: [PATCH 2/3] howto: Fix typo
Quoted 6 lines
Quoted 1 line
Signed-off-by Akira Yokosawa <[email protected]>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.
Quoted 48 lines
Thanx, Paul
Quoted 19 lines
--- howto/howto.tex | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)howto/howto.tex +1
-1@@ -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 tasksSignature · 1 line
2.17.1------------------------------------------------------------------------
commit
b094718ddbe4256e606a41c660b4d4f1836baa66Author: Paul E. McKenney <[email protected]> Date: Thu Jan 16 19:31:26 2020 -0800howto: 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 <[email protected]>Signed-off-by Paul E. McKenney <[email protected]>howto/howto.tex +0
-2@@ -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
howto/howto.tex Parallel programming is not as hard as some say, and we hope · line 32
Quoted 10 lines
howto/howto.tex +6
-3-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
Quoted 3 lines
howto/howto.tex +0
-0This book is written in the hope that presenting the engineering
Re: [PATCH 2/3] howto: Fix typo
Quoted 62 lines · Akira Yokosawa
Quoted 6 lines · Paul E. McKenney
Quoted 5 lines · Akira Yokosawa
Quoted 1 line
From
cd352d3dfd20d8fcfdddafe5547ad191cbdda37eMon Sep 17 00:00:00 2001From: Akira Yokosawa <[email protected]>
Date: Mon, 13 Jan 2020 16:18:19 +0900
Subject: [PATCH 2/3] howto: Fix typoQuoted 6 lines
Quoted 1 line
Signed-off-by Akira Yokosawa <[email protected]>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.
Quoted 46 lines
Thanx, Paul
Quoted 19 lines
--- howto/howto.tex | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)howto/howto.tex +1
-1@@ -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 tasksSignature · 1 line
2.17.1------------------------------------------------------------------------
commit
b094718ddbe4256e606a41c660b4d4f1836baa66Author: Paul E. McKenney <[email protected]> Date: Thu Jan 16 19:31:26 2020 -0800howto: 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 <[email protected]>Signed-off-by Paul E. McKenney <[email protected]>howto/howto.tex +0
-0@@ -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.
Quoted 16 lines
howto/howto.tex Parallel programming is not as hard as some say, and we hope · line 32
Quoted 12 lines
howto/howto.tex +6
-5-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?
Quoted 1 line
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. ;-)
Quoted 3 lines
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.
Quoted 1 line
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 <[email protected]> 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.
howto/howto.tex +6 -5
@@ -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
Re: [PATCH 2/3] howto: Fix typo
Quoted 80 lines · Paul E. McKenney
Quoted 62 lines · Akira Yokosawa
Quoted 6 lines · Paul E. McKenney
Quoted 5 lines · Akira Yokosawa
Quoted 1 line
From
cd352d3dfd20d8fcfdddafe5547ad191cbdda37eMon Sep 17 00:00:00 2001From: Akira Yokosawa <[email protected]>
Date: Mon, 13 Jan 2020 16:18:19 +0900
Subject: [PATCH 2/3] howto: Fix typoQuoted 6 lines
Quoted 1 line
Signed-off-by Akira Yokosawa <[email protected]>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.
Quoted 46 lines
Thanx, Paul
Quoted 19 lines
--- howto/howto.tex | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)howto/howto.tex +1
-1@@ -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 tasksSignature · 1 line
2.17.1------------------------------------------------------------------------
commit
b094718ddbe4256e606a41c660b4d4f1836baa66Author: Paul E. McKenney <[email protected]> Date: Thu Jan 16 19:31:26 2020 -0800howto: 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 <[email protected]>Signed-off-by Paul E. McKenney <[email protected]>howto/howto.tex +0
-0@@ -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.Quoted 16 lines
howto/howto.tex Parallel programming is not as hard as some say, and we hope · line 32
Quoted 12 lines
howto/howto.tex +6
-5-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.
Quoted 3 lines
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.
Quoted 11 lines
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?
Quoted 1 line
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:
Quoted 8 lines
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.
Quoted 38 lines
Quoted 4 lines
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.
Quoted 1 line
So maybe it might be better to revert this change, or to rephrase some more.
How about the following instead?
Thanx, Paul
------------------------------------------------------------------------
commit
64cf378960689deef3d23359eaddea9a21ee683dAuthor: Paul E. McKenney <[email protected]> Date: Thu Jan 16 19:31:26 2020 -0800howto: 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 <[email protected]>Signed-off-by Paul E. McKenney <[email protected]>howto/howto.tex +0
-1@@ -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,
howto/howto.tex Parallel programming is not as hard as some say, and we hope · line 31
Quoted 10 lines
howto/howto.tex +6
-4-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
Quoted 4 lines
howto/howto.tex +0
-0In some surprisingly common cases, they can even be automated. This book is written in the hope that presenting the engineering
Re: [PATCH 2/3] howto: Fix typo
Quoted 95 lines · Akira Yokosawa
Quoted 80 lines · Paul E. McKenney
Quoted 62 lines · Akira Yokosawa
Quoted 6 lines · Paul E. McKenney
Quoted 5 lines · Akira Yokosawa
Quoted 1 line
From
cd352d3dfd20d8fcfdddafe5547ad191cbdda37eMon Sep 17 00:00:00 2001From: Akira Yokosawa <[email protected]>
Date: Mon, 13 Jan 2020 16:18:19 +0900
Subject: [PATCH 2/3] howto: Fix typoQuoted 6 lines
Quoted 1 line
Signed-off-by Akira Yokosawa <[email protected]>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.
Quoted 46 lines
Thanx, Paul
Quoted 19 lines
--- howto/howto.tex | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)howto/howto.tex +1
-1@@ -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 tasksSignature · 1 line
2.17.1------------------------------------------------------------------------
commit
b094718ddbe4256e606a41c660b4d4f1836baa66Author: Paul E. McKenney <[email protected]> Date: Thu Jan 16 19:31:26 2020 -0800howto: 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 <[email protected]>Signed-off-by Paul E. McKenney <[email protected]>howto/howto.tex +0
-0@@ -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.Quoted 16 lines
howto/howto.tex Parallel programming is not as hard as some say, and we hope · line 32
Quoted 12 lines
howto/howto.tex +6
-5-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.Quoted 3 lines
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.
Quoted 6 lines
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!
Quoted 63 lines
Quoted 10 lines
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?
Quoted 1 line
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:
Quoted 8 lines
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.
Quoted 37 lines
Quoted 4 lines
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.
Quoted 1 line
So maybe it might be better to revert this change, or to rephrase some more.
How about the following instead?
Thanx, Paul
------------------------------------------------------------------------
commit
64cf378960689deef3d23359eaddea9a21ee683dAuthor: Paul E. McKenney <[email protected]> Date: Thu Jan 16 19:31:26 2020 -0800howto: 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 <[email protected]>Signed-off-by Paul E. McKenney <[email protected]>howto/howto.tex +0
-0@@ -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.
Quoted 13 lines
howto/howto.tex Parallel programming is not as hard as some say, and we hope · line 31
Quoted 11 lines
howto/howto.tex +6
-5-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
Quoted 6 lines
Thanks, Akira
Quoted 4 lines
howto/howto.tex +0
-0In some surprisingly common cases, they can even be automated. This book is written in the hope that presenting the engineering
PATCH 3/3 intro: Fix typo
In reply to Akira YokosawaFrom 865d0b46e811f6a719f4af1a59d65c6f70185108 Mon Sep 17 00:00:00 2001
From: Akira Yokosawa <[email protected]>
Date: Mon, 13 Jan 2020 19:51:52 +0900
Subject: [PATCH 3/3] intro: Fix typo
--- intro/intro.tex | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
intro/intro.tex +1 -1
@@ -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,
Signature · 1 line
2.17.1