Fix typos in the rest of the codebase (Stellarium#2862)

Found via `codespell -q 3 -S *.po,*.pot,*.utf8,ChangeLog,./src/external,./plugins/RemoteControl/webroot/js -L anonymus,bu,ded,dout,eyt,fiter,inout,lod,maka,mane,nd,ned,previousy,regio,sav,ser,serie,som,statics,te,tht,ue,unter`

CONTRIBUTING.md

@@ -62,7 +62,7 @@ include the following:
 
 - **Documentation**: if you are adding new functionality, be sure to include a 
 description in the main documentation (in ``docs/``) or doxygen description/comments 
-for code in the ``*.hpp`` files (commenting the code may be extremelly helpful!).
+for code in the ``*.hpp`` files (commenting the code may be extremely helpful!).
 
 Thanks!
 

CREDITS.md

@@ -139,7 +139,7 @@
 		time 1995-2050. It is applied for years -4000..+8000 only.
 
 2. Included source code
-	2.1 Some computation of the sideral time (sidereal_time.h/c) and pluto
+	2.1 Some computation of the sidereal time (sidereal_time.h/c) and pluto
 	    orbit contains code from the libnova library (LGPL) by Liam Girdwood.
 	2.2 The orbit.cpp/h and solve.h files are directly borrowed from
 	    Celestia (Chris Laurel). (GPL license)
@@ -190,7 +190,7 @@
 	       nr_of_measurements, combination of flags, tycho2 number)
 	    -) add all stars from Hipparcos (incl. component solutions), and
 	       tycho2+1st supplement
-	    -) reorganize the stars in several brigthness levels and
+	    -) reorganize the stars in several brightness levels and
 	       triangular zones according to position and magnitude
 	    The programs that are used to generate the star files are called
 	    "MakeCombinedCatalogue", "ParseHip", "ParseNomad", and can be
@@ -246,7 +246,7 @@
 	         Edited by Thomas Watson. Taken from CloudyNights
 	         http://www.cloudynights.com/page/articles/cat/articles/the-collinder-catalog-updated-r2467
 	3.10 Cross-identification of objects in consolidated DSO catalog was
-	     maked with:
+	     made with:
 	    [1]  SIMBAD Astronomical Database
 	         http://simbad.u-strasbg.fr
 	    [2]  Merged catalogue of reflection nebulae (Magakian, 2003)

data/ssystem_major.ini

@@ -2,7 +2,7 @@
 # Some clean-up can be done when processing this file for V0.16.
 # - all occurrences of tex_halo (not used as of 0.15 and earlier; already removed.)
 # - all occurrences of texture=nomap.png are redundant (now simply loaded as default)
-# - all occurences of parent=Sun (default when loading). Keep parent=none for sun.
+# - all occurrences of parent=Sun (default when loading). Keep parent=none for sun.
 # - lighting=(true|false) will be ignored (processed like previous "true")
 # - color=1.0,1.0,1.0 (now loaded as default; This influences the halo color and should always have at least one component 1.0.)
 # Default values in the loader, to be removed from ssystem.ini: 

data/ssystem_minor.ini

@@ -3,7 +3,7 @@
 # - NEW split ssystem.ini into ssystem_major.ini (planets and moons) available in program folder from ssystem_minor.ini in user data directory.
 # - all occurrences of tex_halo (not used as of 0.15 and earlier; already removed.)
 # - all occurrences of texture=nomap.png are redundant (now simply loaded as default)
-# - all occurences of parent=Sun (default when loading). Keep parent=none for sun.
+# - all occurrences of parent=Sun (default when loading). Keep parent=none for sun.
 # - lighting=(true|false) will be ignored (processed like previous "true")
 # - color=1.0,1.0,1.0 (now loaded as default; This influences the halo color and should always have at least one component 1.0.)
 # Default values in the loader, to be removed from ssystem_*.ini: 

doc/codingConventions.doxygen

@@ -141,7 +141,7 @@ Use C++ replacement for C functions and %Qt replacements for C++ functions/STL w
  - Use <a href="http://doc.qt.io/qt-5/qstring.html">QString</a>
  instead of @c std::string or <tt>char *</tt>
  - Use <a href="http://doc.qt.io/qt-5/qiodevice.html">QIODevice</a>
- instead of C file managment with @c fopen()
+ instead of C file management with @c fopen()
  - Pass objects as references when needed instead of using pointers.
  - Include standard headers the C++ way, it is more portable:
  @code
@@ -157,7 +157,7 @@ Use C++ replacement for C functions and %Qt replacements for C++ functions/STL w
 #define RADIUS 12 // Bad 
 static const int RADIUS = 12; // Good
  @endcode
- - Use stdc++ math functions instead of C ones. There are more portable and are also overrided for float, thus may be faster.
+ - Use stdc++ math functions instead of C ones. They're more portable and are also overridden for float, thus may be faster.
  @code
 double cosLat = cos(lat);     // Bad 
 double cosLat = std::cos(lat); // Good
@@ -181,7 +181,7 @@ A string literal can be marked for translation in with three different macros,
 
 Several guidelines:
  - Translatable text in sources or data files should be written in English, encoded in ASCII or UTF-8 if needed.
- - Translatable strings should be modified only if really necessary. Any modification to one of them means that all the translators for all the langages will have to re-translate the new string.
+ - Translatable strings should be modified only if really necessary. Any modification to one of them means that all the translators for all the languages will have to re-translate the new string.
  This also means that new strings should be chosen carefully, to avoid the need to modify them later.
  - Do not concatenate strings, use @c QString::arg() instead. Concatenated strings are very hard (or even impossible) to translate.
 @code
@@ -193,7 +193,7 @@ text = q_("Distance: %1AU").arg(distance);          // Good
 QString myTranslatedText(q_("Distance of the planet :")); // Bad
 QString myTranslatedText(q_("Distance of the planet:"));  // Good
 @endcode
- - In general no translated text should be output on the console because there are problems when string and wstring are output on the same console. This means that you should never use wcout, wcerr or wprintf(). Console output should be used for informations, errors and warnings which are not required by the user in nominal use.
+ - In general no translated text should be output on the console because there are problems when string and wstring are output on the same console. This means that you should never use wcout, wcerr or wprintf(). Console output should be used for information, errors and warnings which are not required by the user in nominal use.
  - Errors and warnings should be output in the stderr file, not stdout. [OBSOLETE? We use qDebug() and qWarning() now.]
 @code
 std::cout << "Error while opening file " << qPrintable(myFileName) << "." << std::endl; // Bad 

doc/interfaceMap.mm

@@ -186,7 +186,7 @@
 <edge STYLE="bezier"/>
 </node>
 </node>
-<node CREATED="1202857342628" ID="Freemind_Link_1429727652" MODIFIED="1202857361258" TEXT="intial parameters">
+<node CREATED="1202857342628" ID="Freemind_Link_1429727652" MODIFIED="1202857361258" TEXT="initial parameters">
 <node CREATED="1150487450203" ID="Freemind_Link_789803054" MODIFIED="1202857507206" TEXT="initial time" VSHIFT="-5">
 <node CREATED="1150487477093" FOLDED="true" ID="Freemind_Link_398279288" MODIFIED="1202859413120" TEXT="start at preset sky time">
 <node CREATED="1202859416560" ID="Freemind_Link_1783872930" MODIFIED="1202859428220" TEXT="preset time list"/>
@@ -313,22 +313,22 @@
 </node>
 <node CREATED="1202853671886" ID="Freemind_Link_1987145465" MODIFIED="1202857115653" STYLE="fork" TEXT="amateur astronomer tools" VSHIFT="6">
 <cloud/>
-<node CREATED="1150481385281" FOLDED="true" ID="Freemind_Link_882075950" MODIFIED="1202855755737" TEXT="telescopes managment" VSHIFT="1">
+<node CREATED="1150481385281" FOLDED="true" ID="Freemind_Link_882075950" MODIFIED="1202855755737" TEXT="telescopes management" VSHIFT="1">
 <cloud/>
 <node CREATED="1150485648468" ID="Freemind_Link_1719502300" MODIFIED="1150485655828" TEXT="telescope goto"/>
 <node CREATED="1150485657671" ID="Freemind_Link_1224894730" MODIFIED="1150485659984" TEXT="status"/>
 <node CREATED="1202854369108" ID="Freemind_Link_411524457" MODIFIED="1202854379248" TEXT="telescope server control"/>
 </node>
 <node CREATED="1150487663937" ID="Freemind_Link_110718623" MODIFIED="1202856944119" TEXT="show image flip controls" VSHIFT="-7"/>
-<node CREATED="1202854506626" FOLDED="true" ID="Freemind_Link_1168478955" MODIFIED="1202854576741" TEXT="occulars managment">
+<node CREATED="1202854506626" FOLDED="true" ID="Freemind_Link_1168478955" MODIFIED="1202854576741" TEXT="occulars management">
 <node CREATED="1202855180109" ID="Freemind_Link_444624157" MODIFIED="1202855201099" TEXT="occular list"/>
 <node CREATED="1202855216844" ID="Freemind_Link_1171424144" MODIFIED="1202855227009" TEXT="add new occular"/>
 </node>
 <node CREATED="1150486017062" ID="Freemind_Link_1861025500" MODIFIED="1202854561581" TEXT="night view mode"/>
 <node CREATED="1150486020140" HGAP="23" ID="Freemind_Link_223731728" MODIFIED="1202854591548" TEXT="chart view mode" VSHIFT="-18"/>
-<node CREATED="1202854756910" HGAP="23" ID="Freemind_Link_1630778095" MODIFIED="1202855019339" TEXT="show sideral time" VSHIFT="-28"/>
+<node CREATED="1202854756910" HGAP="23" ID="Freemind_Link_1630778095" MODIFIED="1202855019339" TEXT="show sidereal time" VSHIFT="-28"/>
 </node>
-<node CREATED="1190407499812" HGAP="21" ID="Freemind_Link_1348197327" MODIFIED="1202859322907" TEXT="plugins managment" VSHIFT="8"/>
+<node CREATED="1190407499812" HGAP="21" ID="Freemind_Link_1348197327" MODIFIED="1202859322907" TEXT="plugins management" VSHIFT="8"/>
 </node>
 </node>
 <node CREATED="1202858347096" HGAP="74" ID="Freemind_Link_1690075164" MODIFIED="1202859648310" POSITION="left" TEXT="windows toggle bar" VSHIFT="-204">

doc/mainpage.doxygen

@@ -24,7 +24,7 @@
 @section intro_sec Introduction
 
 This documentation concerns the inner workings of Stellarium.  This documentation
-is targetted at developers of scripts, plugins and the core program.
+is targeted at developers of scripts, plugins and the core program.
 
 @section architecture_sec Program Architecture
 

doc/scripting.doxygen

@@ -42,7 +42,7 @@ itself.  See @ref scripting_api for more details.
 
 @section scripting_api Scripting API
 
-Interation with Stellarium-specific functionality is done by calling the
+Interaction with Stellarium-specific functionality is done by calling the
 <b>public slots</b> of instances of a group of Stellarium's core classes.
 
 - The public slots in the class StelMainScriptAPI are available via an object
@@ -124,7 +124,7 @@ ENABLE_SCRIPT_CONSOLE=1 or =0 option to cmake.
 
 The best source of examples is the \b scripts sub-directory of the main Stellarium 
 source tree.  This directory contains a sub-directory called \b tests which are not
-installed with Stellarium, but are nontheless useful sources of example code for
+installed with Stellarium, but are nonetheless useful sources of example code for
 various scripting features. (The directory can be <a href="https://github.com/Stellarium/stellarium/tree/master/scripts">browsed online</a>. Script files end in <tt>.ssc</tt> and <tt>.inc</tt>. Download links
 are to the right.)
 

guide/README.md

@@ -15,7 +15,7 @@ The classic TeX environment on Windows is MikTeX, a very complete TeX environmen
 
 Alternatively, to be inline with the other Systems, consider TeXlive also for Windows (https://www.tug.org/texlive/windows.html). 
 
-Windows is still the most common desktop platform in 2019, like it or not. However, its command shell is an embarassing relic of the DOS era and a far cry from tools available on the tiniest Linux system. 
+Windows is still the most common desktop platform in 2019, like it or not. However, its command shell is an embarrassing relic of the DOS era and a far cry from tools available on the tiniest Linux system. 
 The shortcomings of the command line have brought several Options for Linux-affine working:
 
 * GNUWin32 tools

guide/app_acknowledgements.tex

@@ -272,7 +272,7 @@ \section{Data}
      \item The Collinder Catalog of Open Star Clusters. An Observer’s Checklist. Edited by Thomas Watson 
 	       from CloudyNights (\url{http://www.cloudynights.com/page/articles/cat/articles/the-collinder-catalog-updated-r2467})
 	\end{enumerate}
-\item Cross-identification of objects in consolidated DSO catalog was maked with:
+\item Cross-identification of objects in consolidated DSO catalog was made with:
 	\begin{enumerate}
     \item  SIMBAD Astronomical Database \url{http://simbad.u-strasbg.fr}
     \item  Merged catalogue of reflection nebulae (Magakian, 2003) \url{http://vizier.u-strasbg.fr/viz-bin/VizieR-3?-source=J/A+A/399/141}

guide/app_nomenclature.tex

@@ -371,7 +371,7 @@ \subsection{Chart of landform types}
 \begin{longtable}{p{45mm}|p{45mm}|p{45mm}}\toprule
 \begin{center}\textbf{Lacus} [LC] and \textbf{Mare} [ME]\end{center} & \begin{center}\textbf{Oceanus} [OC] and \textbf{Palus} [PA]\end{center} & \begin{center}\textbf{Planitia} [PL] and \textbf{Planum} [PM]\end{center} \\
 \includegraphics[width=45mm]{toponomy_lacus_mare.jpg}  & \includegraphics[width=45mm]{toponomy_oceanus_palus.jpg} & \includegraphics[width=45mm]{toponomy_planitia_planum.jpg} \\
-``lake'' (small irregular patch of dark, smooth material of the Moon) and ``sea'' (large, often circular, region of dark smooth material of the Moon) & ``ocean'' (vast, irregular, dark, smooth region -- Oceanus Procellarum only) and ``swamp'' (small irregular area, on the Moon a mixture of mare and highland meterial) & low plain or large level expanse of lowlands and high plain or a plateau \\\midrule
+``lake'' (small irregular patch of dark, smooth material of the Moon) and ``sea'' (large, often circular, region of dark smooth material of the Moon) & ``ocean'' (vast, irregular, dark, smooth region -- Oceanus Procellarum only) and ``swamp'' (small irregular area, on the Moon a mixture of mare and highland material) & low plain or large level expanse of lowlands and high plain or a plateau \\\midrule
 \begin{center}\textbf{Catena} [CA]\end{center} & \begin{center}\textbf{Cavus} [CB]\end{center} & \begin{center}\textbf{Chaos} [CH]\end{center} \\
 \includegraphics[width=45mm]{toponomy_catena.jpg} & 
 \includegraphics[width=45mm]{toponomy_cavus.jpg} & 

guide/app_ssystem_ini.tex

@@ -452,7 +452,7 @@ \subsubsection{Comet section}
 which is more typical for comets which may have no orbital period when
 they are on parabolic or hyperbolic orbits. Frequently orbital
 elements are given for a date very close to perihelion so that the
-perihel date $T$ is used whereever 
+perihel date $T$ is used wherever 
 \texttt{orbit\_Epoch} is not given. However, this assumption does not always hold,
 so we\newFeature{0.21.3} recommend to state \texttt{orbit\_Epoch} explicitly.
 

guide/app_star_catalogue.tex

@@ -410,7 +410,7 @@ \subsubsection{Eruptive Variable Stars}\label{eruptive-variable-stars}
 				to this type on the basis of the following (purely spectroscopic)
 				criteria: spectral types are in the range Fe-Me. The spectra of most
 				typical stars resemble the spectrum of the solar chromosphere. The
-				feature specific to the type is the presence of the flourescent emission
+				feature specific to the type is the presence of the fluorescent emission
 				lines Fe II 4046, 4132 A (anomalously intense in the spectra of these
 				stars), emission lines {[}Si II{]} and {[}O I{]}, as well as the
 				absorption line Li I 6707 A. These variables are usually observed only

guide/ch_advanced_use.tex

@@ -332,7 +332,7 @@ \subsection{GPS Position}
 \subsubsection{GPSD (Linux, Mac OS X only)}
 \label{sec:ExtraData:GPS:GPSD}
 
-On Linux, Mac-OS X and other Unixoid platforms, Stellarium preferrably
+On Linux, Mac-OS X and other Unixoid platforms, Stellarium preferably
 should not connect directly to a GPS USB device, serial device,
 bluetooth device, etc., but use a connection to the \program{gpsd}
 daemon running on a computer in your network which provides GPS

guide/ch_dso.tex

@@ -12,7 +12,7 @@ \chapter{Deep-Sky Objects}
 
 If the object has a name (not just a catalogue number), you should add
 one or more records to the \file{.../nebulae/default/names.dat} file
-(where \file{...} is either the installation directory or (preferrably) the user
+(where \file{...} is either the installation directory or (preferably) the user
 directory). See section~\ref{sec:dso:modifyingNamesDat} Modifying
 \file{names.dat} for details of the file format.
 

guide/ch_landscapes_gz.tex

@@ -607,7 +607,7 @@ \subsection{Fisheye landscape}
 
 
 The image file (Fig.~\ref{fig:landscapes:Fisheye}) should be saved in
-PNG format with alpha transparency. Whereever the image is transparent
+PNG format with alpha transparency. Wherever the image is transparent
 Stellarium will render the sky.
 
 The \file{landscape.ini} file for a fish-eye type landscape looks like

guide/guide.bib

@@ -1007,7 +1007,7 @@ @book{Reingold-Dershowitz:2001
        title = {Calendrical Calculations (The Millennium Edition)},
      address = {Cambridge},
    publisher = {Cambridge University Press},
-     edition = {2rd},
+     edition = {2nd},
         year = 2001
 }
 

guide/plg_atTheTelescope.tex

@@ -758,7 +758,7 @@ \subsubsection{INDI telescopes}
 
 \subsubsection{ASCOM telescopes}
 \newFeature{0.19.3}ASCOM specific settings can be configured when a ASCOM telescope was selected.
-Please see section~\ref{sec:plugins:TelescopeControl:ASCOM} for futher information about
+Please see section~\ref{sec:plugins:TelescopeControl:ASCOM} for further information about
 configuration possibilities.
 
 \subsubsection{Virtual telescope}
@@ -770,7 +770,7 @@ \subsubsection{Virtual telescope}
 indicators for a possible practical application (emulating 'Telrad'
 circles).  
 
-%% We don't neeed this remark any longer after 5 years...
+%% We don't need this remark any longer after 5 years...
 %This feature is equivalent to the 'Dummy' type of telescope
 %supported by Stellarium's original telescope control feature.
 
@@ -1018,7 +1018,7 @@ \subsection*{Explanation of some parameters}
   first day of the year when a star becomes visible. It happens when
   the star is close to the eastern horizon roughly before the end of
   the astronomical night (i.e., at the astronomical twilight). In the
-  following nights, the star will be visibile during longer periods of
+  following nights, the star will be visible during longer periods of
   time, until it reaches its Heliacal set (i.e., the last night of the
   year when the star is still visible). At the Heliacal set, the star
   sets roughly after the beginning of the astronomical night.