Title: Non-attributive "the GPLvn" unidiomatic
Correct inconsistency in use/nonuse of definite article before non-attributive uses of *GPLvn by opting for typical present-day FSF usage (with no article). I believe the FSF tends to use "GPLvn" (rather than "the GPLvn") when the license is referred to by abbreviation and is not prefixed by "GNU". This can be confirmed by analysis of usage on the fsf.org website.
git pull https://k.copyleft.org/guide-fontana gplvn-idiomatic
2014-12-07 04:21:33
Richard Fontana (fontana)
fontana@sharpeleven.org
Git pull requests don't support updates yet.
Pull Request Reviewers
2 comments (0 inline, 2 general)
Showing 1 commit
 1 2015-04-03 00:44:59 fontana dc84691b9398 gplvn-idiomatic Correct inconsistency in use/nonuse of definite article before non-attributive uses of *GPLvn by opting for typical present-day FSF usage (with no article). I believe the FSF tends to use "GPLvn" (rather than "the GPLvn") when the license is referred to by abbreviation and is not prefixed by "GNU". This can be confirmed by analysis of usage on the fsf.org website.
Common ancestor: 26def8538a10
1 file changed
##### Changeset was too big and was cut off... Show full diff anyway
comprehensive-gpl-guide.tex | master gplvn-idiomatic
 1 1 % comprehensive-gpl-guide.tex -*- LaTeX -*-  2 2 %  3 3 % Toplevel file to build the entire book.  4 4 \documentclass[10pt, letterpaper, openany, oneside]{book}  5 5 % I'm somewhat convinced that this book would be better formatted using  6 6 % the memoir class :  7 7 % http://www.ctan.org/pkg/memoir  8 8 % http://mirror.unl.edu/ctan/macros/latex/contrib/memoir/memman.pdf  9 9 10 10 % For the moment, I've thrown in fancychap because I don't have time to  11 11 % research memoir.  12 12 13 13 14 14 % FIXME: Some overall formatting hacks that would really help:  15 15 16 16 % * I have started using \hyperref[LABEL]{text} extensively, which seems  17 17 % to work great in the PDF and HTML versions, but in the Postscript  18 18 % version, the link lost entirely. I think we need an additional command  19 19 % to replace \hyperref which takes an optional third argument that will  20 20 % insert additional text only when generating print versions, such as:  21 21 % \newhyperref[GPLv2s3]{the requirements for binary distribution under  22 22 % GPLv2}{(see section~\ref*{GPLv2s3} for more information)}  23 23 %  24 24 % This is a careful balance, because it'd be all too easy to over-pepper  25 25 % the printed version with back/forward references, but there are  26 26 % probably times when this is useful.  27 27 28 28 % * Similar issue: \href{} is well known not to carry the URLs in the print  29 29 % versions. Adding a footnote with the URL for the print version is  30 30 % probably right. (or maybe a References page?)  31 31 32 32 % * The text is extremely inconsistent regarding formatting of code and  33 33 % commands. The following varied different methods have been used:  34 34 % + the \verb%..% inline form  35 35 % + verbatim environment (i.e., \begin{verbatim}  36 36 % + {\tt }  37 37 % + \texttt{}  38 38 % + the lstlisting environment (i.e., \begin{lstlisting}  39 39 % These should be made consistent, using only two forms: one for line and  40 40 % one for a long quoted section.  41 41 42 42 43 43 44 44 % FIXME: s/GPL enforcers/COGEOs/g  45 45 46 46 % (the term coined later but not used throughout) This can't be done  47 47 % by rote, since it may not be appropriate everywhere and shouldn't be  48 48 % used *before* it's coined in the early portions of  49 49 % compliance-guide.tex (and it's probably difficult to coin it earlier  50 50 % anyway). BTW, I admit COGEOs isn't the best acronym, but I started  51 51 % with Community Enforcement Organizations'', which makes CEO, which  52 52 % is worse. :) My other opting was COEO, which seemed too close to  53 53 % CEO. Suggestions welcome.  54 54 55 55 \usepackage{listings}  56 56 \usepackage{enumerate}  57 57 \usepackage{enumitem}  58 58 \usepackage[Conny]{fncychap}  59 59 \usepackage[dvips]{graphicx}  60 60 \usepackage[verbose, twoside, dvips,  61 61  paperwidth=8.5in, paperheight=11in,  62 62  left=1in, right=1in, top=1.25in, bottom=.75in,  63 63  ]{geometry}  64 64 % Make sure hyperref is last in the package list. Order matters here, See:  65 65 % http://tex.stackexchange.com/questions/77886/fncychap-and-hyperref-messes-up-page-references  66 66 \usepackage{hyperref}  67 67 68 68 \newcommand{\tutorialpartsplit}[2]{#2}  69 69 70 70 %\input{no-numbers-on-table-of-contents}  71 71 \providecommand{\hrefnofollow}[2]{\href{#1}{#2}}  72 72 73 73 \hypersetup{pdfinfo={Title={Copyleft and the GNU General Public License: A Comprehensive Tutorial and Guide}}}  74 74 75 75  \begin{document}  76 76 77 77 \pagestyle{plain}  78 78 \pagenumbering{roman}  79 79 80 80 \frontmatter  81 81 82 82 \begin{titlepage}  83 83 84 84 \begin{center}  85 85 86 86 {\Huge  87 87 {\sc Copyleft and the \\  88 88 89 89 GNU General Public License:  90 90 91 91 \vspace{.25in}  92 92 93 93 A Comprehensive Tutorial \\  94 94 95 95 \vspace{.1in}  96 96 97 97 and Guide  98 98 }}  99 99 \vfill  100 100 101 101 {\parindent 0in  102 102 \begin{tabbing}  103 103 Copyright \= \copyright{} 2003--2005, 2008, 2014--2015 \hspace{1.mm} \= \kill  104 104 Copyright \> \copyright{} 2003--2005, 2008, 2014--2015 \> Bradley M. Kuhn. \\  105 105 Copyright \> \copyright{} 2014--2015 \> Anthony K. Sebro, Jr. \\  106 106 Copyright \= \copyright{} 2014 \> Denver Gingerich. \\  107 107 Copyright \= \copyright{} 2003--2007, 2014 \> Free Software Foundation, Inc. \\  108 108 Copyright \> \copyright{} 2008, 2014 \> Software Freedom Law Center. \\  109 109 \end{tabbing}  110 110 111 111 \vspace{.3in}  112 112 113 113 The copyright holders grant the freedom to copy, modify, convey,  114 114 adapt, and/or redistribute this work (except  115 115 Appendices~\ref{GPLv2-full-text}--\ref{AGPLv3-full-text}) under the terms of the Creative Commons  116 116 Attribution Share Alike 4.0 International License. A copy of that license is  117 117 available at \url{https://creativecommons.org/licenses/by-sa/4.0/legalcode}.  118 118 119 119 Appendices~\ref{GPLv2-full-text}--\ref{AGPLv3-full-text} include copies of the texts of various licenses published  120 120 by the FSF, and they are all licensed under the license, Everyone is permitted  121 121 to copy and distribute verbatim copies of this license document, but changing  122 122 it is not allowed.''. However, those who seek to make modified versions of  123 123 those licenses should note the  124 124 \href{https://www.gnu.org/licenses/gpl-faq.html#ModifyGPL}{explanation given in the GPL FAQ}.  125 125 126 126 \vfill  127 127 128 128 As a public, collaborative project, this Guide is primarily composed of the  129 129 many contributions received via its  130 130 \href{https://gitorious.org/copyleft-org/tutorial/source/master:CONTRIBUTING.md}{public  131 131  contribution process}. Please  132 132 \href{https://gitorious.org/copyleft-org/tutorial/history/master}{review its  133 133  Git logs} for full documentation of all contributions, and  134 134 Appendix~\ref{third-party-citation-list}  135 135  contains a list of third-party works from which some material herein was  136 136 adapted.  137 137 138 138 The most recent version is  139 139 available online at \url{https://copyleft.org/guide/}. Patches  140 140 are indeed welcome to this material. Sources can be found in the Git  141 141 repository at \url{https://gitorious.org/copyleft-org/tutorial/}.  142 142 }  143 143 \end{center}  144 144 145 145 \end{titlepage}  146 146 147 147 \tableofcontents  148 148 149 149 \chapter{Preface}  150 150 151 151 This tutorial is the culmination of nearly a decade of studying and writing  152 152 about software freedom licensing and the GPL\@. Each part of this tutorial  153 153 is a course unto itself, educating the reader on a myriad of topics from the  154 deep details of the GPLv2 and GPLv3, common business models in the copyleft  154 deep details of GPLv2 and GPLv3, common business models in the copyleft  155 155 licensing area (both the friendly and unfriendly kind), best practices for  156 156 compliance with the GPL, for engineers, managers, and lawyers, as well as  157 157 real-world case studies of GPL enforcement matters.  158 158 159 159 It is unlikely that all the information herein is necessary to learn all at  160 160 once, and therefore this tutorial likely serves best as a reference book.  161 161 The material herein has been used as the basis for numerous live tutorials  162 162 and discussion groups since 2002, and the materials have been periodically  163 163 updated. They likely stand on their own as excellent reference material.  164 164 165 165 However, if you are reading these course materials without attending a live  166 166 tutorial session, please note that this material is merely a summary of the  167 167 highlights of the various CLE and other tutorial courses based on this  168 168 material. Please be aware that during the actual courses, class discussion  169 169 and presentation supplements this printed curriculum. Simply reading this  170 170 material is \textbf{not equivalent} to attending a course.  171 171 172 172 \mainmatter  173 173 174 174 % FIXME: We need an Introduction. I think ideally it goes here, before Part  175 175 % I. The introduction should cover initially:  176 176 %  177 177 %  178 178 % * Why we cover the topics in the order that we do, in particular, why  179 179 % we discuss all GPLv2 before mentioning GPLv3 (i.e., explain why we  180 180 % take a diachronic approach to study of GPL).  181 181 %  182 182 % * It should briefly discuss Free Culture / Software Freedom stuff.  183 183 % Maybe some early material currently living in gpl-lgpl.tex should move  184 184 % to the introduction, maybe not. The goal is to prepare for the  185 185 % moment when we can merge in material about CC-BY-SA.  186 186 187 187 \input{gpl-lgpl}  188 188 189 189 \input{compliance-guide}  190 190 191 191 \input{enforcement-case-studies}  192 192 193 193 \appendix  194 194 195 195 \part{Appendices}  196 196 197 197 \input{third-party-citations}  198 198 199 199 \input{license-texts}  200 200 201 201 202 202 \end{document}

#### Changeset was too big and was cut off... Show full diff anyway

2 comments (0 inline, 2 general)
Richard Fontana (fontana)
3 years and 6 months ago on pull request "Non-attributive "the GPLvn" unidiomatic"

Status change: Under review

Auto status change to Under Review

Stephen Compall (S11001001)
3 years and 3 months ago on pull request "Non-attributive "the GPLvn" unidiomatic"

Looks good to me.