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

- added integrated common dictionary for English and German
  in xtras/e+d*.dict

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

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
 %

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
 %

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
 %

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
 %

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

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
 %

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
 %

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

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

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}

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
 %

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
 %

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
 %

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

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

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
 %

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
 %

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
 %

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
 %

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

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

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
 %

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
 %

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{}