Skip to content
Browse files

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

0 comments on commit ed68aaf

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