Merge 'migrate-to-codeu' into 'stable', >

regarding docs, git-fixes, bump EUPL-1.1+ --> 1.2+.

.gitattributes

-text eol=crlf
\ No newline at end of file
+*   text=auto

.mailmap

+Markus QUARITSCH <markus.quaritsch@tugraz.at>
+Markus QUARITSCH <markus.quaritsch@tugraz.at>       <Markus.Quaritsch@tugraz.at>
+Markus QUARITSCH <markus.quaritsch@tugraz.at>       <markusquaritsch@fvkmb037.vkmthd.tugraz.at>
+Markus QUARITSCH <markus.quaritsch@tugraz.at>       <quaritsch@ivt.tugraz.at>
+Stefan MEYER <stefan.meyer@student.tugraz.at>
+Harald MARTINI <harald.martini@ivt.tugraz.at>       <harald.martini@student.tugraz.at>
+Harald MARTINI <harald.martini@ivt.tugraz.at>       <63290044+marha333@users.noreply.github.com>
+Harald MARTINI <harald.martini@ivt.tugraz.at>       <Martini@ivt.tugraz.at>
+Harald MARTINI <harald.martini@ivt.tugraz.at>
+Franz KOBER josef<franz.josef.kober@ivt.tugraz.at>
+Franz KOBER josef<franz.josef.kober@ivt.tugraz.at>  <ko6er.franz@gmail.com>
+Michael KRISPER <michael.krisper@tugraz.at>
+Michael KRISPER <michael.krisper@tugraz.at>         <michael.krisper@gmail.com>
+Michael KRISPER <michael.krisper@tugraz.at>         <michaelkrisper@fvkmb037.vkmthd.tugraz.at>
+Stefan BRANDT <brandt@ivt.tugraz.at>                <Brandt@ivt.tugraz.at>
+Raphael LUZ <luz@ivt.tugraz.at>                     <Luz@ivt.tugraz.at>
+Glenn Zarb <glenn@ascentsoftware.eu>
+Glenn Zarb <glenn@ascentsoftware.eu>                <STC\GZ1>
+Glenn Zarb <glenn@ascentsoftware.eu>                “Glenn <“glenn@ascentsoftware.eu”>
+Terry Burns <Terry.Burns@ricardo.com>
+Kostis Anagnostopoulos <ankostis@gmail.com>
+Kostis Anagnostopoulos <ankostis@gmail.com>         <konstantinos.anagnostopoulos@ext.jrc.ec.europa.eu>
+Raphael Kalchgruber <kalchgruber@ivt.tugraz.at>
+Vasilis Kouliaridis <vasilis.k@emisia.com>          <baboulas8@gmail.com>
\ No newline at end of file

README.md

-# BUILD
-
-Before compiling you need to add references to:
-
-- vectolic.dll
-- itextsharp.dll
-- Newtonsoft.Json.dll
-
-
-# EXECUTE
-
-The following directories/files must be provided in the application folder (e.g. `..\bin\Release`):
-
-- User Manual
-- Declaration
-- User Manual\Release Notes.pdf (provided with the VECTO release)
-- vectolic.dll (should be placed there automatically when compiling)
-- itextsharp.dll (should be placed there automatically when compiling)
-- Newtonsoft.Json.dll (should be placed there automatically when compiling)
-- license.dat (provided by EC/JRC)
-
-
-# RELEASE
-Checklist to build a new release:
-
-- Make  zip-folder named with the "Semantic-version", ie: 2014_15_5-VECTO-2.0.1-beta1.
-- Copy into it:
-    - executable (`.EXE`) (from bin/Debug when pre/beta release)
-    - itextsharp.dll
-    - Newtonsoft.Json.dll
-    - vectolic.dll (check for right version!! Source is currently in beta for file signing features)
-    - User Manual (dir)
-    - User Manual\Release Notes.pdf (generate(!) it from source)
-    - Declaration (dir)
-    - Generic Vehicles (dir)
-- Make a temp-copy of the folder and run it with a license to check everything alright
-- ZIP the folder.
-- Upload into CITNet's SVN:
-    https://webgate.ec.europa.eu/CITnet/svn/VECTO/trunk/Share/
-  and link from:
-    https://webgate.ec.europa.eu/CITnet/confluence/display/VECTO/Releases
-- Make licenses and update private pages
-- Tag repos.
-- Announce in VECTO-58
+# VECTO: Vehicle Energy Consumption Calculation TOol
+
+|                 |         |
+| ---:            | :---    |
+|       **home:** | https://climate.ec.europa.eu/eu-action/transport-emissions/road-transport-reducing-co2-emissions-vehicles/vehicle-energy-consumption-calculation-tool-vecto_en |
+| **repository:** | https://code.europa.eu/vecto/vecto |
+|   **keywords:** | CO2, fuelconsumption, energy, vehicle, automotive, HDV, simulation, engineering, EU, DG_CLIMA, JRC, IET, STU, policy |
+|      **email**: | JRC-VECTO@ec.europa.eu |
+|  **copyright:** | [2012-2022 European Commission, DG_CLIMA](https://climate.ec.europa.eu/index_en) <br> consider also other copyright mentions present in sub-components. |
+|    **license:** | [EUPL 1.2+](https://joinup.ec.europa.eu/software/page/eupl) |
+
+<img src="Documentation/User Manual/pics/VECTOlarge.png" alt="Vecto banner" height="120"/> <img src="Documentation/User Manual/pics/JRClogo.jpg" alt="JRC logo" height="120"/>
+
+## What is VECTO?
+
+VECTO is the offical vehicle simulator developed by the European Commission
+to certify & monitoring energy demands, fuel consumption & CO<sub>2</sub> emissions
+from Heavy Duty Vehicles (HDVs).
+
+VECTO is a downloadable executable program written for .Net (C# & VBasic for the GUI)
+designed to operate on a single computer.
+
+The purpose of [VECTO's repository at code.europe.eu](https://code.europa.eu/vecto/vecto)
+is to facilitate the communication between the Commission and VECTO's development team
+with its users, to streamline support related issues contributing to the development,
+review, and dissemination of VECTO. 
+
+### EU Policy
+
+From the 1st of January 2019, it is mandatory to certify CO<sub>2</sub> emissions
+for all new truck vehicles of categories 4, 5, 9 and 10, as foreseen by regulation 2017/2400/EU
+and [related legislation](http://ec.europa.eu/growth/sectors/automotive/environment-protection/emissions_en).  Data determined with VECTO along with other related parameters,
+are [monitored and reported](https://climate.ec.europa.eu/eu-action/transport-emissions/road-transport-reducing-co2-emissions-vehicles/vehicle-energy-consumption-calculation-tool-vecto_en)
+to the European Commission and made publicly available for each of those new trucks.
+
+
+## Installation
+
+VECTO is distributed as a portable application, downloaded from 
+[**"Deployments" | "Releases releases"**](https://code.europa.eu/vecto/vecto/-/releases)
+(or from the latest release-badges at the top of the landing page).
+This means you can simply unzip the distributed archive and directly execute it.
+
+### Requirements
+
+- Microsoft Windows PC running Microsoft Windows 7 or later
+- Microsoft .NET Framework 4.5
+
+### Procedure
+
+Installing VECTO requires the following two steps:
+
+1. Copy the VECTO directory and all its files and subdirectories to the appropriate location
+  where the user has *execute* permissions
+  (e.g. inside `C:\Program Files` or ask your system administrator).
+
+2. Edit the file `install.ini` and remove the comment character (`#`) in the line containing:
+
+      `ExecutionMode = install`
+
+  **Note:** If the `ExecutionMode` is set to `install`,
+  it is necessary to copy the generic VECTO models distributed with VECTO
+  to a location where you have *write* permissions, as VECTO writes results
+  into the same directory of the input job file.
+
+
+## Usage
+
+Five different mission profiles for trucks and five different mission profiles for buses and coaches have been developed and implemented in the tool to better reflect the current European fleet.
+
+The inputs for VECTO are characteristic parameters to determine the power consumption of every relevant vehicle component. Amongst others, the parameters for rolling resistance, air drag, masses and inertias, gearbox friction, auxiliary power and engine performance are input values to simulate energy consumption and CO2 emissions on standardised driving cycles.
+
+Launch the `./User Manual/help.html` file in your browser (included in the distributed archive)
+and read it for further usage instructions.
+
+<img src="Documentation/User Manual/OriginalPictures/VECTO_MainForm.jpg" alt="Vecto main form" width="480"/>
+
+
+## The [`trailer` branch](https://code.europa.eu/vecto/vecto/-/tree/trailer)
+
+For a later regulation, the VECTO GUI [has been extended](https://ec.europa.eu/clima/system/files/2020-01/report_bodies_trailers_en.pdf) 
+for bodies and trailers, where only the relevant data has to be entered
+(total mass, RRC of the tyres and air drag changes compared to the standard body or trailer).
+Also vehicle VIN, some technology information and certainly the manufacturer,
+production date etc. can be entered to produce a VECTO result file complete for certification.
+For bodies from rigid lorries, also the _Primary vehicle Information File_ (PIF)
+has to be loaded to VECTO, which has to be provided by the manufacturer of the primary vehicle.
+For trailers and semi-trailers, VECTO allocates the generic data automatically.
+
+You may download the Generic Truck/Trailer 3D shapes for CFD simulations from
+the [ECoGeT 3D shapes](https://code.europa.eu/vecto/vecto-cfd) project.
+
+
+## Related vecto software
+
+In the [`vecto` group](https://code.europa.eu/vecto) you may find additionally:
+
+- **Vecto Airdrag:** certify $C_d·A$ values from constant speed tests
+- **Vecto Engine:** certify engine declaration XML files as VECTO input
+- **Vecto EEA hashing-tool:** (archived) monitoring-aid for European Environment Agency 
+- **Vecto Git:** (unused) cirtify any pre-processing file
\ No newline at end of file

README.txt

-
-COMPILING VECTO
----------------
-
-Compiling VECTO requires Microsoft Visual Studio 2013 (or later)
-
-Option 1: Compiling from the command-line
-
-you can build VECTO using the following command:
-
-"c:\Program Files (x86)\MSBuild\14.0\Bin\MSBuild.exe" Vecto.sln /t:Build /p:Configuration=Release
-
-or
-
-"c:\Program Files (x86)\MSBuild\14.0\Bin\MSBuild.exe" Vecto.sln /t:Build /p:Configuration=Debug
-
-"C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\MSBuild\Current\Bin\amd64\MSBuild.exe"
-
-Option 2: Load the solution file in Visual Studio and compile VECTO.
-
-The executable can be found in 
-
-<Path to VECTO-Source Folder>\VECTO\bin\Release 
-
-or
-
-<Path to VECTO-Source Folder>\VECTO\bin\Debug
-
-depending on the configuration.
\ No newline at end of file