Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse code

2012-08-17: review with eclipse spell checking functionality

- added integrated common dictionary for English and German
  in xtras/e+d*.dict
  • Loading branch information...
commit ed68aaf49a3f6d16ff25338bb75db193c6de9bd4 1 parent 25471a6
Karsten Reincke authored

Showing 45 changed files with 472,581 additions and 95 deletions. Show diff stats Hide diff stats

  1. +6 6 oslic-de.tex
  2. +1 1  snippets/en/01-introduction/0100-chapterAbstractInc.tex
  3. +1 1  snippets/en/01-introduction/0101-chapterStartInc.tex
  4. +1 1  snippets/en/02-prolegomena/0200-chapterAbstractInc.tex
  5. +1 1  snippets/en/02-prolegomena/0201-why01Inc.tex
  6. +3 3 snippets/en/02-prolegomena/0202-APC-LicenseMissedInc.tex
  7. +1 1  snippets/en/02-prolegomena/0203-ifrossWithoutGuideInc.tex
  8. +1 1  snippets/en/02-prolegomena/0204-AnotherCompendiumTryInc.tex
  9. +6 6 snippets/en/02-prolegomena/0205-why02Inc.tex
  10. +1 1  snippets/en/02-prolegomena/0206-whatInc.tex
  11. +3 3 snippets/en/02-prolegomena/0207-PrintAndBibWebAndFreeWebEn.tex
  12. +1 1  snippets/en/03-osIdeaAndConcepts/0300-chapterAbstractInc.tex
  13. +1 1  snippets/en/03-osIdeaAndConcepts/0301-chapterStartInc.tex
  14. +1 1  snippets/en/03-osIdeaAndConcepts/0302-osOsiAndOsd.tex
  15. +10 10 snippets/en/03-osIdeaAndConcepts/0303-osHistory.tex
  16. +2 2 snippets/en/03-osIdeaAndConcepts/0304-fsVsOs.tex
  17. +1 1  snippets/en/04-sameIdeaDifferentLicenseModels/0400-chapterAbstractInc.tex
  18. +1 1  snippets/en/04-sameIdeaDifferentLicenseModels/0401-chapterStartInc.tex
  19. +1 1  snippets/en/05-osImportantMinorPoints/0500-chapterAbstractInc.tex
  20. +1 1  snippets/en/05-osImportantMinorPoints/0501-chapterStartInc.tex
  21. +4 4 snippets/en/05-osImportantMinorPoints/0502-derivativeWorks.tex
  22. +4 4 snippets/en/05-osImportantMinorPoints/0503-licenseCompatibility.tex
  23. +1 1  snippets/en/05-osImportantMinorPoints/0504-osAndMoney.tex
  24. +1 1  snippets/en/05-osImportantMinorPoints/0505-oslicAndPatents.tex
  25. +2 2 snippets/en/06-osUseCases/0600-chapterAbstractInc.tex
  26. +9 8 snippets/en/06-osUseCases/0601-chapterStartInc.tex
  27. +1 1  snippets/en/06-osUseCases/0602-chapterTheOslicUseCasesInc.tex
  28. +1 1  snippets/en/07-osToDoListFinder/0700-chapterAbstractInc.tex
  29. +3 3 snippets/en/07-osToDoListFinder/0701-chapterStartInc.tex
  30. +1 1  snippets/en/08-osFulfillmentByToDoLists/0800-chapterAbstractInc.tex
  31. +2 2 snippets/en/08-osFulfillmentByToDoLists/0801-chapterStartInc.tex
  32. +1 1  snippets/en/08-osFulfillmentByToDoLists/0802-apacheFulfillToDoList.tex
  33. +12 12 snippets/en/08-osFulfillmentByToDoLists/0803-bsdFulfillToDoList.tex
  34. +1 1  snippets/en/08-osFulfillmentByToDoLists/0804-gplv2FulfillToDoList.tex
  35. +1 1  snippets/en/08-osFulfillmentByToDoLists/0805-mitFulfillToDoList.tex
  36. +1 1  snippets/en/09-osLegalEnvironments/0900-chapterAbstractInc.tex
  37. +1 1  snippets/en/09-osLegalEnvironments/0901-chapterStartInc.tex
  38. +1 1  snippets/en/0a-Conclusion/0a00-chapterAbstractInc.tex
  39. +1 1  snippets/en/0a-Conclusion/0a01-chapterStartInc.tex
  40. +1 1  snippets/en/0b-Appendices/0b00-chapterAbstractInc.tex
  41. +1 1  snippets/en/0b-Appendices/0b01-chapterStartInc.tex
  42. +1 1  snippets/en/0b-Appendices/0b02-MythsOfOsEn.tex
  43. +11 1 snippets/en/20110928-Changes.tex
  44. +472,446 0 xtras/e+d.dict
  45. +29 0 xtras/e+d_user.dict
12 oslic-de.tex
@@ -120,7 +120,7 @@
120 120 \normalsize
121 121
122 122 \chapter{Vorwort}
123   -Drei Fragen stellen sich vor der Lektüren eines jeden Buches: {\bfseries Wieso}
  123 +Drei Fragen stellen sich vor der Lektüre eines jeden Buches: {\bfseries Wieso}
124 124 dieses Buch? {\bfseries Weshalb} von diesen Autoren? Und {\bfseries warum} in
125 125 dieser Form?\footnote{Und klar: mit diesen Fragen bekennen wir uns ausdrücklich als Sesam-Strassen-sozialisiert:
126 126 'Der, die, das, wieso, weshalb, warum - wer nicht fragt bleibt dumm'. Es ist
@@ -129,13 +129,13 @@ \chapter{Vorwort}
129 129
130 130 Wir, die Initiatoren dieses schließlich und hoffentlich gemeinsam
131 131 geschriebenen Buches, sind Mitarbeiter der Deutschen Telekom AG. Und wir sind - jeder für sich
132   -und jeder auf seine Weise - überzeugte Anhänger des Open Source Gedankens.
  132 +und jeder auf seine Weise - überzeugte Anhänger des Oben Source Gedankens.
133 133 \chapter{Einleitung}
134 134 \section{Inhalt}
135 135 Open Source Software\footnote{Es ist länglich diskutiert worden, was der bessere
136 136 Begriff sei, {\itshape Open Source Software} oder {\itshape Free Software}.
137 137 Obwohl beides letztlich auf dasselbe ziele, so sei - wie gesagt wird - der
138   -Begriff Opne Source Software eingeführt worden, um damit auf eine
  138 +Begriff Open Source Software eingeführt worden, um damit auf eine
139 139 Entwicklungsmethode (``development methodology'') zu rekurieren und weniger auf
140 140 eine politische Bewegung (``political movement'') \cite[vgl. dazu] [S.232]
141 141 {Fogel2006a} } wird bereits vielfach verwendet. Durch die Nutzung der Open Source
@@ -152,7 +152,7 @@ \section{Inhalt}
152 152 alltäglichen Arbeit weniger gefragt. Also brauchen wir ein Kompendium, in dem
153 153 wir nicht nur fallweise allgemeine Open Source Begriffe verlässlich nachlesen
154 154 können, sondern in dem wir auch belastbar immer wieder einmal - sozusagen auf
155   -die Schnelle - nachschlagen können, was witr konkret tun müssen, um eine
  155 +die Schnelle - nachschlagen können, was wir konkret tun müssen, um eine
156 156 bestimmte Lizenz zu erfüllen.
157 157
158 158 Einen solchen doppelten Service will \emph{diese Anleitung zur Open Source
@@ -192,7 +192,7 @@ \chapter{Open Source: Der Grundgedanke}
192 192 gemeinsame an Open Source Software ist.
193 193 \end{quote}
194 194
195   -Am Ende soll klarwerden, dass Open Source dann vorliegt, wenn ihre Lizenz die
  195 +Am Ende soll klar werden, dass Open Source dann vorliegt, wenn ihre Lizenz die
196 196 freie Weitergabe des Quellcodes \ldots.
197 197
198 198 \chapter{Ein Grundgedanke, verschiedene Lizenzmodelle}
@@ -201,7 +201,7 @@ \chapter{Ein Grundgedanke, verschiedene Lizenzmodelle}
201 201 Unterschiede gibt. Es sollte eine aussagekräftige Klassifikation entstehen, auf
202 202 die nachfolgende Kapitel zurückgreifen können.
203 203 \end{quote}
204   -Das Linux Magazin Mai oder April 2011 enthält einen längereren Artikel [\ldots]
  204 +Das Linux Magazin Mai oder April 2011 enthält einen längeren Artikel [\ldots]
205 205
206 206 \section{Minimal präskribierende Lizenzmodelle}
207 207 Lizenzen: MIT, BSD
2  snippets/en/01-introduction/0100-chapterAbstractInc.tex
... ... @@ -1,4 +1,4 @@
1   -% Telekom osCompendium 'for beeing included' snippet template
  1 +% Telekom osCompendium 'for being included' snippet template
2 2 %
3 3 % (c) Karsten Reincke, Deutsche Telekom AG, Darmstadt 2011
4 4 %
2  snippets/en/01-introduction/0101-chapterStartInc.tex
... ... @@ -1,4 +1,4 @@
1   -% Telekom osCompendium 'for beeing included' snippet template
  1 +% Telekom osCompendium 'for being included' snippet template
2 2 %
3 3 % (c) Karsten Reincke, Deutsche Telekom AG, Darmstadt 2011
4 4 %
2  snippets/en/02-prolegomena/0200-chapterAbstractInc.tex
... ... @@ -1,4 +1,4 @@
1   -% Telekom osCompendium 'for beeing included' snippet template
  1 +% Telekom osCompendium 'for being included' snippet template
2 2 %
3 3 % (c) Karsten Reincke, Deutsche Telekom AG, Darmstadt 2011
4 4 %
2  snippets/en/02-prolegomena/0201-why01Inc.tex
... ... @@ -1,4 +1,4 @@
1   -% Telekom osCompendium 'for beeing included' snippet template
  1 +% Telekom osCompendium 'for being included' snippet template
2 2 %
3 3 % (c) Karsten Reincke, Deutsche Telekom AG, Darmstadt 2011
4 4 %
6 snippets/en/02-prolegomena/0202-APC-LicenseMissedInc.tex
... ... @@ -1,4 +1,4 @@
1   -% Telekom osCompendium 'for beeing included' snippet
  1 +% Telekom osCompendium 'for being included' snippet
2 2 %
3 3 % (c) Karsten Reincke, Deutsche Telekom AG, Darmstadt 2011
4 4 %
@@ -29,7 +29,7 @@
29 29 \texttt{http://www.apache.org/}, wp.). Therefor you can not directly jump into
30 30 the \emph{Apache License}. First of all you have to visit the project site (cf.
31 31 \texttt{http://httpd.apache.org/}, wp.) even if at the end its' license link
32   -leads you back to the general \emph{Apache License subsite} (cf.
  32 +leads you back to the general \emph{Apache License sub site} (cf.
33 33 \texttt{http://www.apache.org/licenses/}, wp.) which announces, that \enquote{all
34 34 software produced by The Apache Software Foundation or any of its projects or
35 35 subjects is licensed according to the terms of the documents listed
@@ -53,7 +53,7 @@
53 53 software together\footcite[cf.][\nopage wp]{Netcraft2011a}. Hence many business
54 54 models depends on the Apache License. Another aspect is that even the famous
55 55 \emph{Apache Cookbook}, which explains the installation, the configuration and
56   -the maintaining of an Apache Web Server detailedly\footcite[cf.][\nopage et
  56 +the maintaining of an Apache Web Server in details\footcite[cf.][\nopage et
57 57 passim]{CoaBow2004a}, does not mention anything about the license which allows
58 58 for installation, configuration and maintenance. Neither the index lists the
59 59 word 'license'\footcite[cf.][245ff, esp. p. 250]{CoaBow2004a}, nor the chapters
2  snippets/en/02-prolegomena/0203-ifrossWithoutGuideInc.tex
... ... @@ -1,4 +1,4 @@
1   -% Telekom osCompendium 'for beeing included' snippet
  1 +% Telekom osCompendium 'for being included' snippet
2 2 %
3 3 % (c) Karsten Reincke, Deutsche Telekom AG, Darmstadt 2011
4 4 %
2  snippets/en/02-prolegomena/0204-AnotherCompendiumTryInc.tex
... ... @@ -1,4 +1,4 @@
1   -% Telekom osCompendium 'for beeing included' snippet template
  1 +% Telekom osCompendium 'for being included' snippet template
2 2 %
3 3 % (c) Karsten Reincke, Deutsche Telekom AG, Darmstadt 2011
4 4 %
12 snippets/en/02-prolegomena/0205-why02Inc.tex
... ... @@ -1,4 +1,4 @@
1   -% Telekom osCompendium 'for beeing included' snippet template
  1 +% Telekom osCompendium 'for being included' snippet template
2 2 %
3 3 % (c) Karsten Reincke, Deutsche Telekom AG, Darmstadt 2011
4 4 %
@@ -24,7 +24,7 @@
24 24 %\nocite{*}
25 25
26 26 So again: Did we need a new book about Open Source Software? We had looked for a
27   -reliable integrated Open Source Compendium. But we found seperate pieces of
  27 +reliable integrated Open Source Compendium. But we found separate pieces of
28 28 information and - as we know today - some rumors. Our answer was clear:
29 29 naturally we did not need a new general book about Open Source. But what was
30 30 lacking was a description what responsible developers, project managers or
@@ -32,8 +32,8 @@
32 32 \textit{Open Source License Compendium}.
33 33
34 34 At the best such an \textit{Open Source License Compendium} would contain a set
35   -of simply to process \textit{'For-Fulfilling-The-Licence-To-Do-Lists'}.
36   -Additionally it should offer an intuitively user-freindly search option for
  35 +of simply to process \textit{'For-Fulfilling-The-License-To-Do-Lists'}.
  36 +Additionally it should offer an intuitively user-friendly search option for
37 37 these lists. In any case, it should share developers and project managers the
38 38 effort of having to become Open Source License experts. For the other users, it
39 39 should also clearly explain why one has to do this and not that. Hence a
@@ -98,8 +98,8 @@
98 98 license texts as they were. If they lacked anything\footcite[The systematical
99 99 underdetermination of licenses is a problem being also known in the Open
100 100 Source respectively Free Software movement. Following the biography of RMS his
101   - main judicial councelor Moglen has stated, that \enquote{there is uncertainty in
102   - every legal process (\ldots) } and that it seemed to be silly to try
  101 + main judicial counselor Moglen has stated, that \enquote{there is uncertainty
  102 + in every legal process (\ldots) } and that it seemed to be silly to try
103 103 \enquote{(\ldots) to take out all the bugs (\ldots)}. Nevertheless - so
104 104 Moglen resp. Williams - the goal of Richard Stallman was \enquote{the complete
105 105 opposite}: He tried \enquote{(\ldots) to remove uncertainty which is
2  snippets/en/02-prolegomena/0206-whatInc.tex
@@ -38,7 +38,7 @@ \section{What}
38 38 and acting as a 'splitter'. The mentioned logograms are introduced to
39 39 re-establish or - at least - to underline the common history and the common
40 40 center of 'both' movements, whereby the word \textit{Libre} shall resolve the
41   - abiguity of the word \textit{Free}. For a first survey cf.] [\nopage
  41 + ambiguity of the word \textit{Free}. For a first survey cf.] [\nopage
42 42 wp.]{wpFloss2011a}, the \emph{Open Source Software movement}\footcite[For
43 43 another brief and informative introduction cf.][231ff esp. p.
44 44 232f.]{Fogel2006a} or the GNU-Project\footnote{ We ourselves will stay with the
6 snippets/en/02-prolegomena/0207-PrintAndBibWebAndFreeWebEn.tex
@@ -60,8 +60,8 @@
60 60 read\footnote{But because of the copyright we ourselves are naturally not
61 61 allowed to offer a download link for them or to send a copy of it to those who
62 62 want to verify our quotes.}. And thirdly we should lay open to our readers the
63   -different levels of reliableness of our sources. Therefore we use the following
64   -markers in our bibliographic data\footnote{And another hint: Nowadays sometimes
  63 +different levels of reliableness of our sources. Therefore we use
  64 +the following markers in our bibliographic data\footnote{And another hint: Nowadays sometimes
65 65 even scientific libraries doesn't offer exact 'e-copies' of the original. In
66 66 some cases one can get only html-versions of articles which formerly were
67 67 printed as part of journals. In these case the scholar has to use sources which
@@ -85,6 +85,6 @@
85 85 destroy the pleasing appearance of a text because it's difficult to wrap the
86 86 lines acceptably. Hence we wished to make it easier for LaTeX to do this job.
87 87 Therefor we sometime split the urls and inserted blanks. So you have to erase
88   - all blanks if you want to verify our urls.} and the date when we dowloaded /
  88 + all blanks if you want to verify our urls.} and the date when we downloaded /
89 89 saw the text.
90 90 \end{itemize}
2  snippets/en/03-osIdeaAndConcepts/0300-chapterAbstractInc.tex
... ... @@ -1,4 +1,4 @@
1   -% Telekom osCompendium 'for beeing included' snippet template
  1 +% Telekom osCompendium 'for being included' snippet template
2 2 %
3 3 % (c) Karsten Reincke, Deutsche Telekom AG, Darmstadt 2011
4 4 %
2  snippets/en/03-osIdeaAndConcepts/0301-chapterStartInc.tex
... ... @@ -1,4 +1,4 @@
1   -% Telekom osCompendium 'for beeing included' snippet template
  1 +% Telekom osCompendium 'for being included' snippet template
2 2 %
3 3 % (c) Karsten Reincke, Deutsche Telekom AG, Darmstadt 2011
4 4 %
2  snippets/en/03-osIdeaAndConcepts/0302-osOsiAndOsd.tex
... ... @@ -1,4 +1,4 @@
1   -% Telekom osCompendium 'for beeing included' snippet template
  1 +% Telekom osCompendium 'for being included' snippet template
2 2 %
3 3 % (c) Karsten Reincke, Deutsche Telekom AG, Darmstadt 2011
4 4 %
20 snippets/en/03-osIdeaAndConcepts/0303-osHistory.tex
... ... @@ -1,4 +1,4 @@
1   -% Telekom osCompendium 'for beeing included' snippet template
  1 +% Telekom osCompendium 'for being included' snippet template
2 2 %
3 3 % (c) Karsten Reincke, Deutsche Telekom AG, Darmstadt 2011
4 4 %
@@ -28,22 +28,22 @@ \section{Open Source and its history: some hints}
28 28 \begin{quote}\itshape
29 29 Here we present main lines of the Open Source genesis: The start with the
30 30 bundling of hardware and software in the beginning on the one side and the
31   -monopol of AT\&T and the free distribution of unix in the universities on the
  31 +monopole of AT\&T and the free distribution of unix in the universities on the
32 32 other side - which together established the free hacker culture. We will shortly
33 33 describe the increase of the value of software evoked by the IBM unbundling
34   -strategy and the antitrust suit against AT\&T which let become the software a
35   -value itself worthful of protection and which destroyed the free exchange within
36   -the early hacker community. Naturally we will illuminate the answer of RMS, the
  34 +strategy and the antitrust suit against AT\&T which let become the software an
  35 +object of a specific which had to be protected and which
  36 +destroyed the free exchange within the early hacker community. Naturally we will illuminate the answer of RMS, the
37 37 GNU project, the founding of the FSF and the GPL. Then we will highlight the
38 38 introduction of the concept Open Source invented for dissolving the troubles to
39 39 talk about Free Software with managers of companies. We will hint to the Linux
40 40 kernel as an unwelcome completion of the GNU system. Finally we will outline the
41   -convergency of business and Open Source, not only by Netscape/Mozilla, IBM
42   -apache, Redhat, SUN/OpenOffice but also by IBM/eclipse, Sun/Java and so on. And
  41 +convergency of business and Open Source, not only by Netscape/Mozilla, IBM,
  42 +Apache, Redhat, SUN/OpenOffice but also by IBM/eclipse, Sun/Java and so on. And
43 43 naturally we will highlight the meaning of 'the Cathedral and the Bazar', which
44   -had not been written to contrast the working style of the Open Source Developemt
45   -and the proprietary 'in company' development by for example microsoft, but for
46   -dicern the working and leading style of RMS and Linus.
  44 +had not been written to contrast the working style of the Open Source
  45 +Development and the proprietary 'in company' development by for example
  46 +Microsoft, but for discern the working and leading style of RMS and Linus.
47 47 \end{quote}
48 48 \normalsize
49 49 \ldots
4 snippets/en/03-osIdeaAndConcepts/0304-fsVsOs.tex
... ... @@ -1,4 +1,4 @@
1   -% Telekom osCompendium 'for beeing included' snippet template
  1 +% Telekom osCompendium 'for being included' snippet template
2 2 %
3 3 % (c) Karsten Reincke, Deutsche Telekom AG, Darmstadt 2011
4 4 %
@@ -23,7 +23,7 @@
23 23 %% use all entries of the bibliography
24 24 %\nocite{*}
25 25
26   -\section{\emph{Free Software} versus \emph{Open Sourc}e: some hints}
  26 +\section{\emph{Free Software} versus \emph{Open Source}: some hints}
27 27 \footnotesize
28 28 \begin{quote}\itshape
29 29 Here we will illuminate the differences between the ideas of the Free Software
2  snippets/en/04-sameIdeaDifferentLicenseModels/0400-chapterAbstractInc.tex
... ... @@ -1,4 +1,4 @@
1   -% Telekom osCompendium 'for beeing included' snippet template
  1 +% Telekom osCompendium 'for being included' snippet template
2 2 %
3 3 % (c) Karsten Reincke, Deutsche Telekom AG, Darmstadt 2011
4 4 %
2  snippets/en/04-sameIdeaDifferentLicenseModels/0401-chapterStartInc.tex
... ... @@ -1,4 +1,4 @@
1   -% Telekom osCompendium 'for beeing included' snippet template
  1 +% Telekom osCompendium 'for being included' snippet template
2 2 %
3 3 % (c) Karsten Reincke, Deutsche Telekom AG, Darmstadt 2011
4 4 %
2  snippets/en/05-osImportantMinorPoints/0500-chapterAbstractInc.tex
... ... @@ -1,4 +1,4 @@
1   -% Telekom osCompendium 'for beeing included' snippet template
  1 +% Telekom osCompendium 'for being included' snippet template
2 2 %
3 3 % (c) Karsten Reincke, Deutsche Telekom AG, Darmstadt 2011
4 4 %
2  snippets/en/05-osImportantMinorPoints/0501-chapterStartInc.tex
... ... @@ -1,4 +1,4 @@
1   -% Telekom osCompendium 'for beeing included' snippet template
  1 +% Telekom osCompendium 'for being included' snippet template
2 2 %
3 3 % (c) Karsten Reincke, Deutsche Telekom AG, Darmstadt 2011
4 4 %
8 snippets/en/05-osImportantMinorPoints/0502-derivativeWorks.tex
... ... @@ -1,4 +1,4 @@
1   -% Telekom osCompendium 'for beeing included' snippet template
  1 +% Telekom osCompendium 'for being included' snippet template
2 2 %
3 3 % (c) Karsten Reincke, Deutsche Telekom AG, Darmstadt 2011
4 4 %
@@ -26,7 +26,7 @@
26 26 \section{Excursion: The Problem of Derivated Works}
27 27 \footnotesize
28 28 \begin{quote}\itshape
29   -We will shortly discuss exsting attempts to define the derivated works of
  29 +We will shortly discuss existing attempts to define the derivated works of
30 30 technical aspects, like dynamical or statical linking or not. We will
31 31 prove that linking can not deliver a definite criteria: 1) modules are only
32 32 unzipped libraries. 2) you can distribute software as modules added by a script,
@@ -35,8 +35,8 @@ \section{Excursion: The Problem of Derivated Works}
35 35 attempts do not match the constituting features of script languages. Therefore we
36 36 will follow Moglen(?) and will argue from the viewpoint of a developer: it's
37 37 only a question of a function, method or anything else which calls (jumps into)
38   -a piece of code which has been licenced by a license protecting
39   -on-top-developements and you have a derivated work.
  38 +a piece of code which has been licensed by a license protecting
  39 +on-top-developments and you have a derivated work.
40 40 \end{quote}
41 41 \normalsize
42 42 \ldots
8 snippets/en/05-osImportantMinorPoints/0503-licenseCompatibility.tex
@@ -27,16 +27,16 @@ \section{Excursion: The Problem of Combining Different Licensemodels}
27 27 \footnotesize
28 28 \begin{quote}\itshape
29 29 Here we discuss the often neglected or only loosely touched problem of combining
30   -differently licended software. We will hint to the Exlusion-List of the Free
  30 +differently licensed software. We will hint to the Exclusion-List of the Free
31 31 software foundation; we will hint to the eclipse / GPL-plugin problem; we will
32 32 mention the recent discussion whether the kernel requires to license the
33 33 complete Android as GPL; and finally we will discuss the just now published, short
34 34 analysis of Jaeger and Metzger presenting a combining matrix which seems to fall
35 35 into their lap. We ourselves will argue that question can simply be answered:
36 36 only if you embed two libraries which both are licensed by an on
37   -on-top-develeopment protecting license and if these both license require the
38   -licensing of the derivated work by diffent licenses then you have a problem. In
39   -all other case which we will describe an list there is no problem.
  37 +on-top-development protecting license and if these both license require the
  38 +licensing of the derivated work by different licenses then you have a problem.
  39 +In all other case which we will describe an list there is no problem.
40 40 \end{quote}
41 41 \normalsize
42 42 \ldots
2  snippets/en/05-osImportantMinorPoints/0504-osAndMoney.tex
... ... @@ -1,4 +1,4 @@
1   -% Telekom osCompendium 'for beeing included' snippet template
  1 +% Telekom osCompendium 'for being included' snippet template
2 2 %
3 3 % (c) Karsten Reincke, Deutsche Telekom AG, Darmstadt 2011
4 4 %
2  snippets/en/05-osImportantMinorPoints/0505-oslicAndPatents.tex
... ... @@ -1,4 +1,4 @@
1   -% Telekom osCompendium 'for beeing included' snippet template
  1 +% Telekom osCompendium 'for being included' snippet template
2 2 %
3 3 % (c) Karsten Reincke, Deutsche Telekom AG, Darmstadt 2011
4 4 %
4 snippets/en/06-osUseCases/0600-chapterAbstractInc.tex
... ... @@ -1,4 +1,4 @@
1   -% Telekom osCompendium 'for beeing included' snippet template
  1 +% Telekom osCompendium 'for being included' snippet template
2 2 %
3 3 % (c) Karsten Reincke, Deutsche Telekom AG, Darmstadt 2011
4 4 %
@@ -29,7 +29,7 @@
29 29 the context of a par\-ti\-cu\-lar \emph{Open Source Use Case}, will be fulfilled
30 30 by following the corresponding to-do list. Additionally this chapter introduces a
31 31 taxonomy for these \emph{Open Source Use Cases}. Later on, this taxonomy will
32   -organize the \emph{Open Sourse Use Case Finder}.
  32 +organize the \emph{Open Source Use Case Finder}.
33 33 \end{quote}
34 34 \normalsize{}
35 35
17 snippets/en/06-osUseCases/0601-chapterStartInc.tex
... ... @@ -1,4 +1,4 @@
1   -% Telekom osCompendium 'for beeing included' snippet template
  1 +% Telekom osCompendium 'for being included' snippet template
2 2 %
3 3 % (c) Karsten Reincke, Deutsche Telekom AG, Darmstadt 2011
4 4 %
@@ -85,7 +85,7 @@
85 85 interlocutors. Too often we had to amend that we were not only talking about
86 86 applications and libraries in the strict sense of the words. Finally we
87 87 decided to find our own words - and to stay open for better proposals ;-) }.
88   - More specifially, we will ask you, whether the Open Source Software, you
  88 + More specifically, we will ask you, whether the Open Source Software, you
89 89 want to use, is an includable code snippet, a linkable module or library, or a
90 90 loadable plugin, or whether it is an autonomous application or server which
91 91 can be executed or processed. In the first case, the answer should be 'it's a
@@ -93,7 +93,7 @@
93 93
94 94 \item The \textbf{\underline{state} of the of the Open Source Software}: It
95 95 might be used, as one has got it. Or it can be modified, before being used.
96   - More specifially, we will ask you, whether you want to leave the Open Source
  96 + More specifically, we will ask you, whether you want to leave the Open Source
97 97 Software as you have got it, or whether you want to modify it before using
98 98 and/or distributing it to 3rd parties. In the first case, the answer should be
99 99 '\underline{unmodified}', in the second '\underline{modified}'.
@@ -102,16 +102,16 @@
102 102 Software}: On the hand you might use the received Open Source Software as a
103 103 readily prepared application. On the other hand you might embed the received
104 104 Open Source into a larger application as one of its' components. More
105   - specifially, we will ask you, whether you are you using the Open Source
  105 + specifically, we will ask you, whether you are you using the Open Source
106 106 Software as an autonomous piece of software, or whether you are using it as an
107   - embbeded part of a larger, more complex piece of software. In the first case,
  107 + embedded part of a larger, more complex piece of software. In the first case,
108 108 the answer should be '\underline{independent}', in the second
109 109 '\underline{embedded}'.
110 110
111 111 \item The \textbf{\underline{recipient} of the of the Open Source Software}:
112 112 Sometimes you might wish to use the received Open Source Software only for
113 113 yourself. In other cases you might intend to hand over the software (also) to
114   - other people. More specifially, we will ask you, whether you are going to use
  114 + other people. More specifically, we will ask you, whether you are going to use
115 115 the Open Source Software only for yourself, or whether you plan to
116 116 (re)distribute it (also) to third parties. In the first case, the answer
117 117 should be '\underline{4yourself}', in the second '\underline{4others}'.
@@ -126,7 +126,8 @@
126 126
127 127 \end{itemize}
128 128
129   -From a more programmatic point-of-view, we can summarise these tokens as follows:
  129 +From a more programmatic point-of-view, we can summarize these tokens as
  130 +follows:
130 131
131 132 \begin{itemize}
132 133 \item \texttt{type::snimoli} \emph{or} \texttt{type::proapse}
@@ -183,6 +184,6 @@
183 184 Does this sound complex? We thought so too. We spent much
184 185 time explaining these constraints to ourselves, and only when we had transposed
185 186 all the combinations and rules into a tree, did the situation become clearer.
186   -The following diagrams shall summarise this way of clarification:
  187 +The following diagrams shall summarize this way of clarification:
187 188
188 189 %\bibliography{../../../bibfiles/oscResourcesEn}
2  snippets/en/06-osUseCases/0602-chapterTheOslicUseCasesInc.tex
... ... @@ -1,4 +1,4 @@
1   -% Telekom osCompendium 'for beeing included' snippet template
  1 +% Telekom osCompendium 'for being included' snippet template
2 2 %
3 3 % (c) Karsten Reincke, Deutsche Telekom AG, Darmstadt 2011
4 4 %
2  snippets/en/07-osToDoListFinder/0700-chapterAbstractInc.tex
... ... @@ -1,4 +1,4 @@
1   -% Telekom osCompendium 'for beeing included' snippet template
  1 +% Telekom osCompendium 'for being included' snippet template
2 2 %
3 3 % (c) Karsten Reincke, Deutsche Telekom AG, Darmstadt 2011
4 4 %
6 snippets/en/07-osToDoListFinder/0701-chapterStartInc.tex
... ... @@ -1,4 +1,4 @@
1   -% Telekom osCompendium 'for beeing included' snippet template
  1 +% Telekom osCompendium 'for being included' snippet template
2 2 %
3 3 % (c) Karsten Reincke, Deutsche Telekom AG, Darmstadt 2011
4 4 %
@@ -97,7 +97,7 @@ \section{A standard form for gathering the relevant information}
97 97 an interpreter like php, perl, bash etc.) if you can start an interpreter taking
98 98 the file as one of its' arguments. \item[State:] You modify Open Source Software
99 99 if you expand, reduce or modify at least one of the received software files, and
100   -- in case of dealing woth binary object code - if you (re)compile and (re)link
  100 +- in case of dealing with binary object code - if you (re)compile and (re)link
101 101 the modified software to a new binary file. If you only modify configuration
102 102 files, you do not modify the Open Source Software.
103 103 \item[Context:] You use Open Source Software embedded into a larger unit, if one
@@ -115,7 +115,7 @@ \section{A standard form for gathering the relevant information}
115 115 device or transport medium to anyone (other than a direct member
116 116 of your development group), then you indeed handover the Open Source Software to
117 117 third parties\footnote{Please remember that - at least in Germany - there are
118   -opinions that even handing over software to another legal enity or department
  118 +opinions that even handing over software to another legal entity or department
119 119 of the same company is also a kind of distribution. It is always safest
120 120 to take the broadest possible meaning of distributing or handing over.}.
121 121 \item[Mode] This follows the standard terminology of software development.
2  snippets/en/08-osFulfillmentByToDoLists/0800-chapterAbstractInc.tex
... ... @@ -1,4 +1,4 @@
1   -% Telekom osCompendium 'for beeing included' snippet template
  1 +% Telekom osCompendium 'for being included' snippet template
2 2 %
3 3 % (c) Karsten Reincke, Deutsche Telekom AG, Darmstadt 2011
4 4 %
4 snippets/en/08-osFulfillmentByToDoLists/0801-chapterStartInc.tex
... ... @@ -1,4 +1,4 @@
1   -% Telekom osCompendium 'for beeing included' snippet template
  1 +% Telekom osCompendium 'for being included' snippet template
2 2 %
3 3 % (c) Karsten Reincke, Deutsche Telekom AG, Darmstadt 2011
4 4 %
@@ -24,7 +24,7 @@
24 24 %\nocite{*}
25 25
26 26 % TODO MIT integrieren
27   -% TODO apacheFulFill ausfüllen
  27 +% TODO apacheFulfill ausfüllen
28 28 % TODO ECL integrieren
29 29
30 30 %\bibliography{../../../bibfiles/oscResourcesEn}
2  snippets/en/08-osFulfillmentByToDoLists/0802-apacheFulfillToDoList.tex
... ... @@ -1,4 +1,4 @@
1   -% Telekom osCompendium 'for beeing included' snippet template
  1 +% Telekom osCompendium 'for being included' snippet template
2 2 %
3 3 % (c) Karsten Reincke, Deutsche Telekom AG, Darmstadt 2011
4 4 %
24 snippets/en/08-osFulfillmentByToDoLists/0803-bsdFulfillToDoList.tex
... ... @@ -1,4 +1,4 @@
1   -% Telekom osCompendium 'for beeing included' snippet template
  1 +% Telekom osCompendium 'for being included' snippet template
2 2 %
3 3 % (c) Karsten Reincke, Deutsche Telekom AG, Darmstadt 2011
4 4 %
@@ -47,7 +47,7 @@ \subsection{The BSD specific mini finder}
47 47 Source Use Cases tokens} see p. \pageref{OsucTokens}. For Details of the
48 48 \textit{Open Source Use Cases} based on these token see p.
49 49 \pageref{OsucDefinitionTree} }. Additionally the BSD license considers the form
50   -of the distribution, e.g. whether the work is distributed as a (set of) source
  50 +of the distribution, eg. whether the work is distributed as a (set of) source
51 51 code file(s) or as a (set of) the binary file(s). Use the following tree to find
52 52 the BSD license fulfilling to-do lists.
53 53
@@ -211,7 +211,7 @@ \subsubsection{BSD-2: Passing the unmodified software as a source code package}
211 211
212 212 \item[requires] the tasks in order to fulfill the license conditions
213 213 \begin{itemize}
214   - \item \textbf{[mandatory:]} Ensure, that the licensing elements - e.g.
  214 + \item \textbf{[mandatory:]} Ensure, that the licensing elements - eg.
215 215 the BSD license text, the specific copyright notice of the original author(s),
216 216 and the BSD disclaimer - are retained in your package in the form you have got
217 217 them.
@@ -247,13 +247,13 @@ \subsubsection{BSD-3: Passing the unmodified software as a binary package}
247 247 \end{description}
248 248
249 249 \begin{itshape}
250   -\emph{\textbf{General remark for all binary distribitions}:}
  250 +\emph{\textbf{General remark for all binary distributions}:}
251 251 \label{MobileDeviceHint} Even if you are distributing a BSD bi\-na\-ry package
252 252 on a medium, which doesn't allow the user, to see package files directly - some
253 253 mobile devices don't give their users the full access to all stored elements -
254 254 you have to fulfill the mandatory requirements. So, sometimes, it is necessary,
255   -to let simply the BSD license and the copyright notice become an unvisible part
256   -of the binary pakage and to deploy the files together with the package. The
  255 +to let simply the BSD license and the copyright notice become an invisible part
  256 +of the binary package and to deploy the files together with the package. The
257 257 point is: you have fulfilled the license.
258 258 \end{itshape}
259 259
@@ -448,10 +448,10 @@ \subsection{Discussions and Explanations}
448 448 wp]{BsdLicense2Clause}. Hence, you are not allowed, to modify any of the
449 449 copyright notes, which are already embedded in the received (source) files. And
450 450 from a logical point of view, there must exist an explicit or implicit
451   -assertion, that the software is lincensed under the \textit{BSD 2-Clause
  451 +assertion, that the software is licensed under the \textit{BSD 2-Clause
452 452 license}\footcite[The BSD license requires, that a re-distributed software
453 453 package must contain the (package specific) copyright notice, the (license
454   -specific) conditions and the BSD discaimer. (cf.][\nopage wp.) You might ask
  454 +specific) conditions and the BSD disclaimer. (cf.][\nopage wp.) You might ask
455 455 what you should do, if these elements are missed in the package you got. If so,
456 456 the package you got had not been licensed adequately. Hence, you do not know
457 457 reliably whether you have received it under a BSD license. In other words: If
@@ -462,7 +462,7 @@ \subsection{Discussions and Explanations}
462 462 modify these files or corresponding text snippets. For our purposes, we
463 463 translated the bans into the following executable task:
464 464
465   -\begin{quote}\textit{Ensure, that the licensing elements - e.g. the BSD license
  465 +\begin{quote}\textit{Ensure, that the licensing elements - eg. the BSD license
466 466 text, the specific copyright notice of the original author(s), and the BSD disclaimer
467 467 - are retained in your package in the form you have got them.}\end{quote}
468 468
@@ -472,10 +472,10 @@ \subsection{Discussions and Explanations}
472 472 distribution}\footcite[cf.][\nopage wp]{BsdLicense2Clause}. Hence, this is
473 473 not required as necessary condition for the (re)distribution as source code
474 474 package . But nevertheless, even for a distribution in form of source code, it
475   -is often possible, to fulfill this rule too - e.g., if you offer an own download
  475 +is often possible, to fulfill this rule too - eg., if you offer an own download
476 476 site for source code packages. In such cases, it is a sign of respect, to
477 477 mention the licensing not only inside of the packages, but also in the text of
478   -your site. Because of that, we added thow following voluntary task for all BSD
  478 +your site. Because of that, we added the following voluntary task for all BSD
479 479 Open Source Use Cases, which deal with the redistribution in form of source
480 480 code'
481 481
@@ -501,7 +501,7 @@ \subsection{Discussions and Explanations}
501 501 that the licensing elements are also automatically generated and embedded into
502 502 the 'binary package'. But nevertheless, you have to add the copyright notice,
503 503 the conditions and the disclaimer to this package for acting according to the
504   -BSD license. Therefore we choosed the following form of an executable, license
  504 +BSD license. Therefore we chose the following form of an executable, license
505 505 fulfilling task for all binary oriented distributions:
506 506
507 507 \begin{quote}\textit{Ensure, that your distribution contains the original
2  snippets/en/08-osFulfillmentByToDoLists/0804-gplv2FulfillToDoList.tex
... ... @@ -1,4 +1,4 @@
1   -% Telekom osCompendium 'for beeing included' snippet template
  1 +% Telekom osCompendium 'for being included' snippet template
2 2 %
3 3 % (c) Karsten Reincke, Deutsche Telekom AG, Darmstadt 2011
4 4 %
2  snippets/en/08-osFulfillmentByToDoLists/0805-mitFulfillToDoList.tex
... ... @@ -1,4 +1,4 @@
1   -% Telekom osCompendium 'for beeing included' snippet template
  1 +% Telekom osCompendium 'for being included' snippet template
2 2 %
3 3 % (c) Karsten Reincke, Deutsche Telekom AG, Darmstadt 2011
4 4 %
2  snippets/en/09-osLegalEnvironments/0900-chapterAbstractInc.tex
... ... @@ -1,4 +1,4 @@
1   -% Telekom osCompendium 'for beeing included' snippet template
  1 +% Telekom osCompendium 'for being included' snippet template
2 2 %
3 3 % (c) Karsten Reincke, Deutsche Telekom AG, Darmstadt 2011
4 4 %
2  snippets/en/09-osLegalEnvironments/0901-chapterStartInc.tex
... ... @@ -1,4 +1,4 @@
1   -% Telekom osCompendium 'for beeing included' snippet template
  1 +% Telekom osCompendium 'for being included' snippet template
2 2 %
3 3 % (c) Karsten Reincke, Deutsche Telekom AG, Darmstadt 2011
4 4 %
2  snippets/en/0a-Conclusion/0a00-chapterAbstractInc.tex
... ... @@ -1,4 +1,4 @@
1   -% Telekom osCompendium 'for beeing included' snippet template
  1 +% Telekom osCompendium 'for being included' snippet template
2 2 %
3 3 % (c) Karsten Reincke, Deutsche Telekom AG, Darmstadt 2011
4 4 %
2  snippets/en/0a-Conclusion/0a01-chapterStartInc.tex
... ... @@ -1,4 +1,4 @@
1   -% Telekom osCompendium 'for beeing included' snippet template
  1 +% Telekom osCompendium 'for being included' snippet template
2 2 %
3 3 % (c) Karsten Reincke, Deutsche Telekom AG, Darmstadt 2011
4 4 %
2  snippets/en/0b-Appendices/0b00-chapterAbstractInc.tex
... ... @@ -1,4 +1,4 @@
1   -% Telekom osCompendium 'for beeing included' snippet template
  1 +% Telekom osCompendium 'for being included' snippet template
2 2 %
3 3 % (c) Karsten Reincke, Deutsche Telekom AG, Darmstadt 2011
4 4 %
2  snippets/en/0b-Appendices/0b01-chapterStartInc.tex
... ... @@ -1,4 +1,4 @@
1   -% Telekom osCompendium 'for beeing included' snippet template
  1 +% Telekom osCompendium 'for being included' snippet template
2 2 %
3 3 % (c) Karsten Reincke, Deutsche Telekom AG, Darmstadt 2011
4 4 %
2  snippets/en/0b-Appendices/0b02-MythsOfOsEn.tex
... ... @@ -1,4 +1,4 @@
1   -% Telekom osCompendium 'for beeing included' snippet template
  1 +% Telekom osCompendium 'for being included' snippet template
2 2 %
3 3 % (c) Karsten Reincke, Deutsche Telekom AG, Darmstadt 2011
4 4 %
12 snippets/en/20110928-Changes.tex
... ... @@ -1,4 +1,4 @@
1   -% Telekom osCompendium 'for beeing included' snippet template
  1 +% Telekom osCompendium 'for being included' snippet template
2 2 %
3 3 % (c) Karsten Reincke, Deutsche Telekom AG, Darmstadt 2011
4 4 %
@@ -31,6 +31,16 @@
31 31 \begin{tabular}{|r|c|p{10cm}|}
32 32 \hline
33 33 \hline
  34 + \texttt{2012-08-25}
  35 + & \texttt{0.5.0}
  36 + & Expanded Break Through Release\newline
  37 + $\vartriangleright$ MIT license fulfilling to-do lists(Chapter ?.?)\newline
  38 + $\vartriangleright$ Apache license fulfilling to-do lists(Chapter
  39 + ?.?)\newline
  40 + $\vartriangleright$ using integrated eclipse spell checking methods\newline
  41 + \\
  42 +
  43 +\hline
34 44 \texttt{2012-07-06}
35 45 & \texttt{0.4.0}
36 46 & Break Through Release\newline
472,446 xtras/e+d.dict
472,446 additions, 0 deletions not shown
29 xtras/e+d_user.dict
... ... @@ -0,0 +1,29 @@
  1 +derivated
  2 +Free
  3 +Installationskits
  4 +internet
  5 +Kompendium
  6 +Open
  7 +OSLiC
  8 +prolegomena
  9 +Prolegomena
  10 +rekurieren
  11 +Softwareentwickler
  12 +Source
  13 +unrestrictive
  14 +subchapter
  15 +toto
  16 +subchapters
  17 +checkable
  18 +Veröffentlichungsprozess
  19 +Urheberpersönlichkeitsrecht
  20 +underdetermination
  21 +logograms
  22 +reliableness
  23 +negativo
  24 +unbundling
  25 +convergency
  26 +plugins
  27 +includable
  28 +plugin
  29 +facultative

0 comments on commit ed68aaf

Please sign in to comment.
Something went wrong with that request. Please try again.