@@ -9,12 +9,12 @@

 [80%]:  https://upload.wikimedia.org/wikipedia/commons/thumb/5/57/Progress_80.svg/80px-Progress_80.svg.png "80%"

 [90%]:  https://upload.wikimedia.org/wikipedia/commons/thumb/b/ba/Progress_90.svg/80px-Progress_90.svg.png "90%"

 [100%]: https://upload.wikimedia.org/wikipedia/commons/thumb/8/82/Progress_100.svg/80px-Progress_100.svg.png "100%"

-[abandonned]: http://wiki.flightgear.org/images/thumb/3/30/Cross_32px.png/16px-Cross_32px.png         "abandonné"

-[done]:       http://wiki.flightgear.org/images/thumb/7/75/Tick_32px.png/16px-Tick_32px.png           "fait"

-[ongoing]:    http://wiki.flightgear.org/images/thumb/3/37/Ongoing.png/16px-Ongoing.png               "en cours"

-[pending]:    http://wiki.flightgear.org/images/thumb/8/8d/Hourglass_32px.png/16px-Hourglass_32px.png "en attente"

-[fixed]:      http://wiki.flightgear.org/images/thumb/8/85/WIP.png/26px-WIP.png                       "réparé"

-[paused]:     http://wiki.flightgear.org/images/thumb/d/dc/Paused.png/16px-Paused.png                 "en pause"

+[abandonned]: https://wiki.flightgear.org/images/thumb/3/30/Cross_32px.png/16px-Cross_32px.png         "abandonné"

+[done]:       https://wiki.flightgear.org/images/thumb/7/75/Tick_32px.png/16px-Tick_32px.png           "fait"

+[ongoing]:    https://wiki.flightgear.org/images/thumb/3/37/Ongoing.png/16px-Ongoing.png               "en cours"

+[pending]:    https://wiki.flightgear.org/images/thumb/8/8d/Hourglass_32px.png/16px-Hourglass_32px.png "en attente"

+[fixed]:      https://wiki.flightgear.org/images/thumb/8/85/WIP.png/26px-WIP.png                       "réparé"

+[paused]:     https://wiki.flightgear.org/images/thumb/d/dc/Paused.png/16px-Paused.png                 "en pause"

 [green-bug]:  https://upload.wikimedia.org/wikipedia/commons/thumb/6/63/Green_bug.svg/32px-Green_bug.svg.png "non blocking bug"

 [red-bug]:    https://upload.wikimedia.org/wikipedia/commons/thumb/a/a4/Red_bug.svg/32px-Red_bug.svg.png "blocking bug"

 [warning]:    https://upload.wikimedia.org/wikipedia/commons/thumb/1/12/Achtung-orange.svg/32px-Achtung-orange.svg.png "warning symbol"

@@ -23,7 +23,7 @@

 [other pictures available here](https://seb.lautre.net/bozon/index.php?f=158cf95340742d)

 # Thanks

-Thanks to [www2](https://forum.flightgear.org/viewtopic.php?f=14&t=25291) the modeller of the [GDU104X project "Farmin/G1000"](http://wiki.flightgear.org/Project_Farmin/FG1000) I can continue the work began many years ago with a nicer (and working) 3D model instrument. Thanks to him/her for the SVG basis file too.  

+Thanks to [www2](https://forum.flightgear.org/viewtopic.php?f=14&t=25291) the modeller of the [GDU104X project "Farmin/G1000"](https://wiki.flightgear.org/Project_Farmin/FG1000) I can continue the work began many years ago with a nicer (and working) 3D model instrument. Thanks to him/her for the SVG basis file too.  

 Thanks to Hooray's nice efforts, and some examples ans snipsets of code here and there from the Canvas team.  

 Thanks to all FlightGear community for the funny project I let too many years off side... Especially to authors of Avidyne Entegra 9 on extra500, from which the map is largely inspired (and many lines of code copied and adapted): Dirk Dittmann and Eric van den Berg 

@@ -54,7 +54,7 @@ Please report bug at <zkv1000@seb.lautre.net>.

 * ![][100%]

   * The whole 3D model is animated, with necessary popups (in order to separate nested knobs for example), and adaptable to the size of the panel.

   * The basic fligth instrumentation is here (AI, speeds, altitude and vertical speed, etc.), plus many other helpers and information (often displayed in widgets or alerts). Also the radio stack (NAV and COMM) tools are implemented. ADF is available for bearing.

-  * The official autopilot [GFC700 from the official Stuart Buchanan's FG1000](http://wiki.flightgear.org/FG1000#GFC700_Autopilot) is available and usable.

+  * The official autopilot [GFC700 from the official Stuart Buchanan's FG1000](https://wiki.flightgear.org/FG1000#GFC700_Autopilot) is available and usable.

   * Screens are fully animated, with softkeys and menus, on map (PFD inset and MFD) background is configurable with the preferred one, navaids and [route](https://seb.lautre.net/git/seb/zkv1000/issues/6) are displayed. Traffic and topography layers are available for display only on MFD screen (not in PFD inset as the window is too small).

   * There is also per-aircraft settings storage for preferred units (speed, distance, etc.).

   * Flightplan management is delegated to the more usable FG interface lauched from inside the zkv100, but it is possible to use DirectTo on selected navaid, and OBS mode with GPS.

@@ -65,7 +65,7 @@ Please report bug at <zkv1000@seb.lautre.net>.

 * ![][90%]

   * route displayed on map: legs ![][done], current and next leg ![][done], OBS ![][done], TOC/TOD ![][ongoing]

   * XPDR: emergency code depending of the country (eg.: 1200 for US, 7700 for Europe), should be set in settings

-  * integration of Octal450's [S-TEC 55X](http://wiki.flightgear.org/S-TEC_55X) autopilot system[][ongoing]

+  * integration of Octal450's [S-TEC 55X](https://wiki.flightgear.org/S-TEC_55X) autopilot system[][ongoing]

 * ![][80%]

   * Flight plans catalog (display on map doesn't work each time...)

   * Alerts: voice description of the alert ![][ongoing]

@@ -86,7 +86,7 @@ Please report bug at <zkv1000@seb.lautre.net>.

   * VNAV

   * scrolling lift in menus

   * tutorials

-  * [touchable screen](http://wiki.flightgear.org/Canvas_Event_Handling) ([other interesting link](http://wiki.flightgear.org/Touch_Animation))

+  * [touchable screen](https://wiki.flightgear.org/Canvas_Event_Handling) ([other interesting link](https://wiki.flightgear.org/Touch_Animation))

   * many more...

 # Installation

@@ -293,14 +293,14 @@ Not sur I'm clear on this point though :)

 There are two systems supported: the GFC700 shipped with the official Stuart Buchanan's FG1000 and the Octal450's STEC 55X (and at time of writing only HDG and buggy NAV/GPS modes are available).

 ### GFC700

-To make the magic operate, you just need to insert these lines into the `sim/systems` section. Be aware that this autopilot [has been tuned for the Cessna 182, so may not be correct for light jets](http://wiki.flightgear.org/FG1000#Include_the_GFC700_autopilot_.28optional.29).

+To make the magic operate, you just need to insert these lines into the `sim/systems` section. Be aware that this autopilot [has been tuned for the Cessna 182, so may not be correct for light jets](https://wiki.flightgear.org/FG1000#Include_the_GFC700_autopilot_.28optional.29).

         <autopilot>

           <path>Aircraft/Instruments-3d/FG1000/GFC700.xml</path>

         </autopilot>

 ### S-TEC 55X

-To make it available you have to follow the installation rules of the device [on its own page](http://wiki.flightgear.org/S-TEC_55X). The zkv1000 will find it by its own and make it available.

+To make it available you have to follow the installation rules of the device [on its own page](https://wiki.flightgear.org/S-TEC_55X). The zkv1000 will find it by its own and make it available.

 This STEC55X autopilot system would remain shipped in the zkv1000 as it is described in the documentation of Cirrus Perspective SR2x, but the zkv1000 will in near future let you create your own and make its choice depending of the availibilities or property set.

@@ -357,17 +357,17 @@ Please send issues to <zkv1000@seb.lautre.net>

 # Documentation

 Documentation is being actively written. There are two differents guides:

-* [Aircraft Maintainer's Guide](http://wiki.flightgear.org/User:Zakharov/zkv1000_installation_guide)

-* [User's Guide](http://wiki.flightgear.org/User:Zakharov/zkv1000_user_guide)

+* [Aircraft Maintainer's Guide](https://wiki.flightgear.org/User:Zakharov/zkv1000_installation_guide)

+* [User's Guide](https://wiki.flightgear.org/User:Zakharov/zkv1000_user_guide)

 Here is a list of useful links:

-* [Canvas in FG](http://wiki.flightgear.org/Category:Canvas)

-* [Nasal](http://wiki.flightgear.org/Category:Nasal)

-* the guides used to create the scenario from [Garmin website](http://support.garmin.com/support/manuals/searchManuals.faces)

-    * [G1000 Pilot’s Guide for the Diamond DA42 (v0370.22)](http://static.garmin.com/pumac/190-00406-07_0B_Web.pdf) *(94 pages)*

-    * [Pilot's Guide, Cirrus Perspective, SR2x (v0764.30)](http://static.garmin.com/pumac/190-00820-11_A.pdf) *(752 pages)*

+* [Canvas in FG](https://wiki.flightgear.org/Category:Canvas)

+* [Nasal](https://wiki.flightgear.org/Category:Nasal)

+* the guides used to create the scenario from [Garmin website](https://support.garmin.com/support/manuals/searchManuals.faces)

+    * [G1000 Pilot’s Guide for the Diamond DA42 (v0370.22)](https://static.garmin.com/pumac/190-00406-07_0B_Web.pdf) *(94 pages)*

+    * [Pilot's Guide, Cirrus Perspective, SR2x (v0764.30)](https://static.garmin.com/pumac/190-00820-11_A.pdf) *(752 pages)*

 # FG1000

 There is an implementation of the Primus Garmin 1000 by Stuart Buchanan which is much more respectful of the Canvas principles, using new technology Emesary, with far better coding style, and with the intent to stay close as possible with the Garmin 1000 real device.  

-The device is avaiblable in [FGData repo](https://sourceforge.net/p/flightgear/fgdata/ci/next/tree/Aircraft/Instruments-3d/FG1000) and has a [specific wiki page](http://wiki.flightgear.org/FG1000).

+The device is avaiblable in [FGData repo](https://sourceforge.net/p/flightgear/fgdata/ci/next/tree/Aircraft/Instruments-3d/FG1000) and has a [specific wiki page](https://wiki.flightgear.org/FG1000).