Skip to content

Commit f23c546

Browse files
baijumbaijum
committed
Expand colophon
Signed-off-by: Baiju Muthukadan <[email protected]>
1 parent 77713bd commit f23c546

File tree

4 files changed

+186
-47
lines changed

4 files changed

+186
-47
lines changed

‎colophon.tex

+82-26
Original file line numberDiff line numberDiff line change
@@ -3,39 +3,95 @@
33
\chapter*{Colophon}
44
\pagenumbering{gobble}
55

6-
The print version of this book is typeset by the author in Dejavu \&
7-
Source Code Pro typeface using the
8-
\TeX\ system. It used \LaTeX\ macros and {\hologo {XeTeX}} extension.
9-
There are many other \TeX\ packages used in the preparation of this
10-
book. The book uses two variants of Dejavu typeface: DejaVuSerif and
11-
DejaVuSans. It also uses SourceCodePro for the monospace text.
12-
13-
The picture used in the book cover is taken from
14-
\href{https://commons.wikimedia.org/wiki/File:The_ladder_of_life_is_full_of_splinters.jpg}{Wikimedia Commons}.
15-
The original photo is from Mykl Roventine and he has licensed it under
16-
Creativce
17-
Commons \href{https://creativecommons.org/licenses/by/2.0}{CC BY 2.0}
6+
The author typeset the print version of this book in Dejavu and Source Code Pro
7+
typefaces using the \TeX\ system. \LaTeX\ macros and {\hologo {XeTeX}}
8+
extensions were used. Many other \TeX\ packages were also used in the
9+
preparation of this book. The book uses two variants of the Dejavu typeface:
10+
DejaVuSerif and DejaVuSans. It also uses SourceCodePro for monospaced text.
11+
12+
The picture used on the book cover is taken
13+
from \href{https://commons.wikimedia.org/wiki/File:The_ladder_of_life_is_full_of_splinters.jpg}{Wikimedia
14+
Commons}. The original photo is by Mykl Roventine and it is licensed under the
15+
Creative Commons \href{https://creativecommons.org/licenses/by/2.0}{CC BY 2.0}
1816
license.
1917

20-
The type faces used for cover design includes Cabin, CabinCondensed,
21-
and DejaVuSans.
18+
The typefaces used in the cover design include Cabin, CabinCondensed, and
19+
DejaVuSans.
20+
21+
Without the contributions of all the developers who work on free and open source
22+
projects, it would not be possible to publish a book like this. Thank you to all
23+
of these contributors for their hard work and dedication.
24+
25+
\section*{Reviews and Feedback}
26+
27+
The author would be very grateful for your reviews on Amazon and other websites.
28+
When you tweet about the book, please include the hashtag \#essentialsofgo. Your
29+
blog posts, videos, or anything else you create about this book will help to
30+
spread the word. Your reviews and social media posts can help other people find
31+
the book and learn about Go programming.
32+
33+
34+
Please kindly send your feedback and suggestions to the following email address:
35+
\href{mailto:[email protected]}{[email protected]}. You have the option
36+
to create issues in the GitHub repository at:
37+
\url{https://github.com/baijum/essential-go}. Additionally, you can propose changes by
38+
creating pull requests.
39+
40+
Thank you for reviewing my book. Your feedback and suggestions are very valuable
41+
and will help me improve the book. I will carefully consider your feedback and
42+
make changes as needed. If you have any further questions or suggestions, please
43+
do not hesitate to contact me.
44+
45+
\subsection*{Why should you review the book?}
46+
47+
\begin{enumerate}
48+
49+
\item This book will help many people learn Go programming. As a fellow Go community member, you are contributing to this effort.
50+
51+
\item Your feedback will influence the content of the book.
52+
53+
\item As you study the book with a critical mind, you are enhancing your Go knowledge. The learning is more intense than reading a book casually.
54+
55+
\item You will be required to refer to other works to verify the content in the text. This will help you to broaden your knowledge on the subject.
56+
57+
\item You are supporting a fellow Go community member. This will motivate me to contribute more.
58+
59+
\item Your name will be mentioned in the book at the beginning in the acknowledgments, just after the preface.
60+
61+
\item The book is a free or open source book licensed under the \href{http://creativecommons.org/licenses/by-sa/4.0/}{Creative Commons Attribution-ShareAlike 4.0 International} license.
62+
63+
\end{enumerate}
64+
65+
\subsection*{How to review the book?}
66+
67+
Reflect on these questions as you read the book.
68+
69+
\begin{enumerate}
70+
71+
\item How is the structure of the chapters in the book?
72+
\item How are the sections under each chapter organized?
73+
\item Is the book consistent throughout all the pages? (Consider consistency of organization, writing style, terminology usage, etc.)
74+
\item Is there any essential point missing when explaining a particular topic?
75+
\item Is the logical flow of introducing the concepts easy to follow?
76+
\item Is the narrative clear, reasonable, and engaging?
77+
\item Are the examples and exercises short and easy to understand?
78+
\item Did you notice any sentence or paragraph that is difficult to understand?
79+
\item Did you see an opportunity to add a side note that would be helpful to the reader?
80+
\item Did you notice any awkward use of the English language? (You can ignore minor language issues.)
81+
\item How can this book be made more interesting?
2282

23-
%% The eBook is creeated from the \LaTeX\ source using \textit{tex4ebook}
24-
%% and \textit{Calibre}. The \textit{tex4ebook} is built on top
25-
%% of \href{http://www.tug.org/tex4ht}{tex4ht} system.
83+
\end{enumerate}
2684

27-
I am grateful to all these free/open source projects. Thanks to all
28-
the contributors of these projects.
85+
When you provide feedback about a chapter, please specify the chapter title. If
86+
your feedback is about a section, please include the section number and chapter
87+
title. There is no need to mention the page number, as it may change.
2988

30-
\section*{Feedback}
89+
If you are able to send a pull request to the Git repo with your changes, that
90+
would be preferable to sending an email. If sending a pull request is not
91+
possible, you can send an email as explained here.\\[40mm]
3192

32-
Please send your feedback
33-
to \href{mailto:[email protected]}{[email protected]} I would
34-
appreciate your tweets and reviews on Amazon and other websites. More
35-
information is available on the book
36-
source repository:\\ \url{https://github.com/baijum/essential-go}
93+
%% \pagebreak
3794

38-
\pagebreak
3995
\thispagestyle{empty} %% Remove header and footer.
4096

4197
\section*{About the Author}

‎copyright.tex

+3-3
Original file line numberDiff line numberDiff line change
@@ -7,9 +7,9 @@
77
{\sf\bfseries Baiju Muthukadan}\\[.1in]
88
{\small \copyright}{\small \tt 2015-2023} {\small Baiju Muthukadan <[email protected]>}\\
99

10-
Essentials of Go Programming {\small \copyright} 2015-2023 by Baiju Muthukadan is licensed
11-
under Attribution-ShareAlike 4.0 International. To view a copy of this license,
12-
visit:\\
10+
Essentials of Go Programming {\small \copyright} 2015-2023 by Baiju Muthukadan
11+
is licensed under Creative Commons Attribution-ShareAlike 4.0 International. To
12+
view a copy of this license, visit:\\
1313
\url{http://creativecommons.org/licenses/by-sa/4.0/}
1414

1515
\rule{200pt}{0.4pt}\\[3mm]

‎essential-go.tex

+1
Original file line numberDiff line numberDiff line change
@@ -259,6 +259,7 @@
259259
\printindex
260260
\end{ebookr}
261261

262+
\blankpage
262263
\input{./colophon.tex}
263264
%% \blankpage
264265
%% \blankpage

‎sphinx/colophon.rst

+100-18
Original file line numberDiff line numberDiff line change
@@ -1,31 +1,113 @@
11
Colophon
22
========
33

4-
The print version of this book is typeset by the author in Dejavu &
5-
Source Code Pro typeface using the TeX system. It used LaTeX macros and
6-
extension. There are many other TeX packages used in the preparation of
7-
this book. The book uses two variants of Dejavu typeface: DejaVuSerif
8-
and DejaVuSans. It also uses SourceCodePro for the monospace text.
4+
The author typeset the print version of this book in Dejavu and Source
5+
Code Pro typefaces using the TeX system. LaTeX macros and extensions
6+
were used. Many other TeX packages were also used in the preparation of
7+
this book. The book uses two variants of the Dejavu typeface:
8+
DejaVuSerif and DejaVuSans. It also uses SourceCodePro for monospaced
9+
text.
910

10-
The picture used in the book cover is taken from `Wikimedia
11+
The picture used on the book cover is taken from `Wikimedia
1112
Commons <https://commons.wikimedia.org/wiki/File:The_ladder_of_life_is_full_of_splinters.jpg>`__.
12-
The original photo is from Mykl Roventine and he has licensed it under
13-
Creativce Commons `CC BY
13+
The original photo is by Mykl Roventine and it is licensed under the
14+
Creative Commons `CC BY
1415
2.0 <https://creativecommons.org/licenses/by/2.0>`__ license.
1516

16-
The type faces used for cover design includes Cabin, CabinCondensed, and
17-
DejaVuSans.
17+
The typefaces used in the cover design include Cabin, CabinCondensed,
18+
and DejaVuSans.
1819

19-
I am grateful to all these free/open source projects. Thanks to all the
20-
contributors of these projects.
20+
Without the contributions of all the developers who work on free and
21+
open source projects, it would not be possible to publish a book like
22+
this. Thank you to all of these contributors for their hard work and
23+
dedication.
2124

22-
Feedback
23-
--------
25+
Reviews and Feedback
26+
--------------------
2427

25-
| Please send your feedback to [email protected] I would appreciate
26-
your tweets and reviews on Amazon and other websites. More information
27-
is available on the book source repository:
28-
| https://github.com/baijum/essential-go
28+
The author would be very grateful for your reviews on Amazon and other
29+
websites. When you tweet about the book, please include the hashtag
30+
#essentialsofgo. Your blog posts, videos, or anything else you create
31+
about this book will help to spread the word. Your reviews and social
32+
media posts can help other people find the book and learn about Go
33+
programming.
34+
35+
Please kindly send your feedback and suggestions to the following email
36+
address: [email protected]. You have the option to create issues in
37+
the GitHub repository at: https://github.com/baijum/essential-go.
38+
Additionally, you can propose changes by creating pull requests.
39+
40+
Thank you for reviewing my book. Your feedback and suggestions are very
41+
valuable and will help me improve the book. I will carefully consider
42+
your feedback and make changes as needed. If you have any further
43+
questions or suggestions, please do not hesitate to contact me.
44+
45+
Why should you review the book?
46+
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
47+
48+
#. This book will help many people learn Go programming. As a fellow Go
49+
community member, you are contributing to this effort.
50+
51+
#. Your feedback will influence the content of the book.
52+
53+
#. As you study the book with a critical mind, you are enhancing your Go
54+
knowledge. The learning is more intense than reading a book casually.
55+
56+
#. You will be required to refer to other works to verify the content in
57+
the text. This will help you to broaden your knowledge on the
58+
subject.
59+
60+
#. You are supporting a fellow Go community member. This will motivate
61+
me to contribute more.
62+
63+
#. Your name will be mentioned in the book at the beginning in the
64+
acknowledgments, just after the preface.
65+
66+
#. The book is a free or open source book licensed under the `Creative
67+
Commons Attribution-ShareAlike 4.0
68+
International <http://creativecommons.org/licenses/by-sa/4.0/>`__
69+
license.
70+
71+
How to review the book?
72+
~~~~~~~~~~~~~~~~~~~~~~~
73+
74+
Reflect on these questions as you read the book.
75+
76+
#. How is the structure of the chapters in the book?
77+
78+
#. How are the sections under each chapter organized?
79+
80+
#. Is the book consistent throughout all the pages? (Consider
81+
consistency of organization, writing style, terminology usage, etc.)
82+
83+
#. Is there any essential point missing when explaining a particular
84+
topic?
85+
86+
#. Is the logical flow of introducing the concepts easy to follow?
87+
88+
#. Is the narrative clear, reasonable, and engaging?
89+
90+
#. Are the examples and exercises short and easy to understand?
91+
92+
#. Did you notice any sentence or paragraph that is difficult to
93+
understand?
94+
95+
#. Did you see an opportunity to add a side note that would be helpful
96+
to the reader?
97+
98+
#. Did you notice any awkward use of the English language? (You can
99+
ignore minor language issues.)
100+
101+
#. How can this book be made more interesting?
102+
103+
When you provide feedback about a chapter, please specify the chapter
104+
title. If your feedback is about a section, please include the section
105+
number and chapter title. There is no need to mention the page number,
106+
as it may change.
107+
108+
| If you are able to send a pull request to the Git repo with your
109+
changes, that would be preferable to sending an email. If sending a
110+
pull request is not possible, you can send an email as explained here.
29111
30112
About the Author
31113
----------------

0 commit comments

Comments
 (0)