convert.py, markdown: use UTF-8.

Guile use ISO-8859-1 by default for ports. Since the markdown contain
some UTF-8 characters, the resulting HTML ended up with unknown
characters replaced by some '??'.

Converting some dashes or quotes to ASCII equivalent was done in
previous commits and was not a big issue, but some files also have
characters with accents, so keeping most of the UTF-8 characters as-is
and moving directly to UTF-8 is a better solution.

Some characters still don't work, and end up in some haunt build
errors (which is better than silent faillures like before). They all
have valid equivalents so they were replaced by their equivalents.

Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>

11 files changed, 50 insertions, 50 deletions

diff --git a/markdown/2011_04_replicant-lacks-tracking-antifeatures.md b/markdown/2011_04_replicant-lacks-tracking-antifeatures.md
index 35606e8..0cc1bdb 100644
--- a/markdown/2011_04_replicant-lacks-tracking-antifeatures.md
+++ b/markdown/2011_04_replicant-lacks-tracking-antifeatures.md
@@ -52,7 +52,7 @@ Here are some reasons:
 
 * The modem or the network has no access to the CPU where replicant is
   running. That opens up some possibilities such as [VPN][6],
-  [TOR][7],[SSH][8], etc…
+  [TOR][7],[SSH][8], etc...
 
 * If mobile phones become the computers of the future we want to run [free
   software][9] on them.
diff --git a/markdown/2011_11_replicant-on-nexus-s-preview.md b/markdown/2011_11_replicant-on-nexus-s-preview.md
index e6e1491..7de2802 100644
--- a/markdown/2011_11_replicant-on-nexus-s-preview.md
+++ b/markdown/2011_11_replicant-on-nexus-s-preview.md
@@ -34,7 +34,7 @@ be achieved:
 * 3D acceleration
 
 * Whatever needs the non-free firmwares we don't include (NFC, MFC, WiFi,
-  Bluetooth…)
+  Bluetooth...)
 
 We are indeed not including any non-free firmware (100% free is our goal) and
 are not going to provide any free replacement for these as we are not skilled
diff --git a/markdown/2013_11_fairphone.md b/markdown/2013_11_fairphone.md
index dfdc212..2c6044f 100644
--- a/markdown/2013_11_fairphone.md
+++ b/markdown/2013_11_fairphone.md
@@ -5,7 +5,7 @@ tags: Replicant news, Fairphone, Paul Kocialkowski
 ---
 Over the past months, we have been asked a lot whether Replicant is going to
 be running on the [Fairphone][1]. The goal behind [Fairphone][1], as its name
-suggests, is to build a phone that is "fair". This covers a lot of different
+suggests, is to build a phone that is “fair”. This covers a lot of different
 aspects that the [Fairphone][1] company took care of: such topics as using
 fair and conflict-free resources, ensuring that all workers along the supply
 chain get a fair wage, improving the handling of electronic waste, being
@@ -13,7 +13,7 @@ transparent about the cost of each part of the device, its technical
 specifications and encouraging open and flexible designs.  
 We are really glad to see a company producing electronic devices taking care
 of such many important aspects as social conditions of workers, ecology and
-handling of e-waste as well as transparency and being "technically open".
+handling of e-waste as well as transparency and being “technically open”.
 
 What we are especially interested in, at the Replicant project, is how good
 the device will be when it comes to software freedom. Hence, we have spent
diff --git a/markdown/2015_01_replicant-at-fosdem-2015.md b/markdown/2015_01_replicant-at-fosdem-2015.md
index d58fa6c..dbba8af 100644
--- a/markdown/2015_01_replicant-at-fosdem-2015.md
+++ b/markdown/2015_01_replicant-at-fosdem-2015.md
@@ -6,8 +6,8 @@ tags: Events, Paul Kocialkowski
 This year's edition of [FOSDEM][1], one of the major free software conferences
 in Europe, is just around the corner! Among the various talks that mention the
 state of free software on [embedded devices][2], I (Paul Kocialkowski) will be
-presenting a talk entitled "[Reached milestones and ongoing development on
-Replicant][3]" on Sunday afternoon, that will first highlight the various
+presenting a talk entitled “[Reached milestones and ongoing development on
+Replicant][3]” on Sunday afternoon, that will first highlight the various
 achievements that were accomplished within the Replicant project to handle the
 numerous devices it supports today, only to explain how the majority of those
 devices are fatally flawed when it comes to freedom and privacy/security.
diff --git a/markdown/2017_12_contributions-to-arcep-work-on-terminal-devices-and-public-consultation.md b/markdown/2017_12_contributions-to-arcep-work-on-terminal-devices-and-public-consultation.md
index 633b276..6116370 100644
--- a/markdown/2017_12_contributions-to-arcep-work-on-terminal-devices-and-public-consultation.md
+++ b/markdown/2017_12_contributions-to-arcep-work-on-terminal-devices-and-public-consultation.md
@@ -24,11 +24,11 @@ The EU regulation is however less specific and the articles related to
 terminals can be interpreted with different scopes:
 
 > When accessing the internet, end-users should be free to choose between
-> various types of terminal equipment […].
+> various types of terminal equipment [...].
 
 > End-users shall have the right to access and distribute information and
 > content, use and provide applications and services, and use terminal
-> equipment of their choice […].
+> equipment of their choice [...].
 
 A narrow understanding would associate the choice of the terminal witch
 choices made available from the industry, while a broader understanding, that
diff --git a/markdown/2019_12_replicant-36c3.md b/markdown/2019_12_replicant-36c3.md
index bf736ed..57f6c47 100644
--- a/markdown/2019_12_replicant-36c3.md
+++ b/markdown/2019_12_replicant-36c3.md
@@ -20,16 +20,16 @@ DECT: 6506
 There will also be a few talks about Replicant and related topics in several
 spots around the congress:
 
-* [Introduction to Replicant][5] - December 27 19:15, Central
+* [Introduction to Replicant][5] – December 27 19:15, Central
   Decentralization Cluster (CDC) stage
 
-* [Android's build system is messier than your distro's][6] - December 28
+* [Android's build system is messier than your distro's][6] – December 28
   20:30, Lecture Room M1
 
-* [Extending the lifetime of smartphones with Replicant][7] - December 28
+* [Extending the lifetime of smartphones with Replicant][7] – December 28
   20:50, Open Infrastructure Orbit (OIO) stage
 
-* [The chromium mess meets Android][8] - December 29 21:00, Lecture Room M1
+* [The chromium mess meets Android][8] – December 29 21:00, Lecture Room M1
 
  [1]: <https://events.ccc.de/congress/2019/wiki/index.php/Main_Page>
 
diff --git a/markdown/2020_01_replicant-at-fosdem-2020.md b/markdown/2020_01_replicant-at-fosdem-2020.md
index 997da85..8bacaf9 100644
--- a/markdown/2020_01_replicant-at-fosdem-2020.md
+++ b/markdown/2020_01_replicant-at-fosdem-2020.md
@@ -54,7 +54,7 @@ If there's any other topic you deem as relevant please let us know in the
 comment section, mailing list or IRC. Everyone's point of view is welcomed.
 
 On Sunday's afternoon, there will be a talk at the Hardware Enablement devroom
-on the topic of "Extending the lifetime of smartphones with Replicant":
+on the topic of “Extending the lifetime of smartphones with Replicant”:
 
 * Location: room K.4.401, ULB, Brussels, Belgium
 
diff --git a/markdown/2020_04_what-could-go-wrong-with-devices-that-have-non-replaceable-batteries.md b/markdown/2020_04_what-could-go-wrong-with-devices-that-have-non-replaceable-batteries.md
index cab44c9..c87020a 100644
--- a/markdown/2020_04_what-could-go-wrong-with-devices-that-have-non-replaceable-batteries.md
+++ b/markdown/2020_04_what-could-go-wrong-with-devices-that-have-non-replaceable-batteries.md
@@ -228,8 +228,8 @@ the device in the fridge each time people came by.
 Sometimes he forgot to put the device in the fridge and started to have
 political and/or intimate conversation and at some point he remembered the
 device and had to go put it in the fridge in the middle of the conversations.
-That was very weird. Especially the "Can you wait a second? I've to put the
-phone in the fridge." part.
+That was very weird. Especially the “Can you wait a second? I've to put the
+phone in the fridge.” part.
 
 In addition to all these issues, we also had the device crash during
 development, however we couldn't wait until the battery was fully depleted as
@@ -270,7 +270,7 @@ He was charged with:
 He plead innocent for all of the charges, and most of the charges were
 dismissed:
 
-* The "explosive device" was in fact the Samsung SM-N930F, which is best
+* The “explosive device” was in fact the Samsung SM-N930F, which is best
   known as Galaxy Note 7. As many other people also had one at some point,
   the court dismissed that charge, especially because this wasn't done on
   purpose. The judge also said that they couldn't condemn people for being
@@ -290,7 +290,7 @@ dismissed:
   fair use. Various leaked documents like the Snowden documents, or
   Wikileaks revelations were also used during the case to prove that some
   leaked documents could be considered as fair use. The fact that the
-  documents had "proprietary" markings was also not sufficient as many
+  documents had “proprietary” markings was also not sufficient as many
   public documents also still bear markings that were just not removed.
 
 * Counterfeiting was also dismissed because no proof of violation of
@@ -323,9 +323,9 @@ However he was still charged with the following:
 
 Subpoena and other declarations:
 
-* The court also gave him a subpoena "Be more careful next time and work on
+* The court also gave him a subpoena “Be more careful next time and work on
   more constructive things like adding support for phones with a removable
-  battery only." to which the developer agreed.
+  battery only.” to which the developer agreed.
 
 * He also declared that rushing to add support for a phone wasn't a good
   idea either, as because of that, he didn't realize that the device was a
@@ -347,13 +347,13 @@ back, the following conversations occurred when filling the list of hardware:
 * Developer: It's a UART adapter for smartphone, you know behind the USB
   connector there is [very long technical explanations].
 
-* Employee: Let's write "UART adapter for smartphone".
+* Employee: Let's write “UART adapter for smartphone”.
 
 * Developer: It also probably works on tablets you know, and it can also do
   many other things other than UART, like power on the phone and switch
   modes [very long technical explanations].
 
-* Employee: Let's write "complicated computer hardware".
+* Employee: Let's write “complicated computer hardware”.
 
 Or:
 
@@ -363,12 +363,12 @@ Or:
   the phone modem, there is a standard called terminal profile which has
   many privacy implications like [very long explanations].
 
-* Employee: Let's write "SIM card tracker".
+* Employee: Let's write “SIM card tracker”.
 
 * Developer: It can't track SIM cards at all, but it can trace the protocol
   [very long explanation again].
 
-* Employee: Sigh, let's write "complicated computer hardware" again.
+* Employee: Sigh, let's write “complicated computer hardware” again.
 
 Or:
 
@@ -378,11 +378,11 @@ Or:
   Libreboot, this has many freedom implications like [very long
   explanations].
 
-* Employee: Let's write "vintage computer".
+* Employee: Let's write “vintage computer”.
 
 * Developer: But I use that computer you know [very long explanations].
 
-* Employee: Sigh, let's write "complicated computer hardware" again.
+* Employee: Sigh, let's write “complicated computer hardware” again.
 
 Or:
 
@@ -390,12 +390,12 @@ Or:
 
 * Developer: It's just a usual Galaxy S II (GT-I9100G).
 
-* Employee: Let's write "Galaxy S II".
+* Employee: Let's write “Galaxy S II”.
 
 * Developer: I've also a Galaxy S II (GT-I9100) which has a very different
   system on a chip [very long explanations].
 
-* Employee: Sigh, let's write "complicated computer hardware" again.
+* Employee: Sigh, let's write “complicated computer hardware” again.
 
 Or even:
 
@@ -415,13 +415,13 @@ Or even:
 * Developer: [very long explanations starting].
 
 * Employee: Sorry [interrupting the developer], bad idea, forget about my
-  question, let's again write "complicated computer hardware".
+  question, let's again write “complicated computer hardware”.
 
 At the end the developer got it all back, and the staff said it was the
 strangest set of seized equipment they ever seen.
 
 He then was unavailable during a full week, as he was reflashing all the
-"complicated computer hardware" for security reasons. That meant that in
+“complicated computer hardware” for security reasons. That meant that in
 practice he had to reinstall Libreboot[1] or other fully free versions of
 Coreboot that he used, Parabola[2] on all the desktops, laptops, servers,
 single board computers and smartphones that weren't fully encrypted,
@@ -436,20 +436,20 @@ reinstalling everything. If the hardware had to run nonfree software, it would
 have been a different story.
 
 Besides about 1 month of Apache logs, and the phone number of his contacts,  
-not much was exposed. We also hope that Android "Factory erase" worked fine on
+not much was exposed. We also hope that Android “Factory erase” worked fine on
 the SM-N930F but we can't know as we didn't try to recover any data.
 
 The only device he didn't got back was the Samsung SM-N930F, as it was
 probably kept or disposed by the Justice Department.
 
-About the lost of the device, the developer commented: "I lost weeks [of work]
-because of that shitty phone", "I don't want that phone anywhere near me.".
+About the lost of the device, the developer commented: “I lost weeks [of work]
+because of that shitty phone”, “I don't want that phone anywhere near me.”.
 
 It turned out that, in addition to his allergy to nonfree software, freedom
 and privacy violations, that developer now became allergic to non-replaceable
-batteries as well. "Deciding to make devices with non-repleacable batteries is
+batteries as well. “Deciding to make devices with non-repleacable batteries is
 completely insane, it would be very important to ask ourselves how we got
-there." that developer commented.
+there.” that developer commented.
 
 ## References:
 
diff --git a/markdown/2020_07_late-report-from-fosdem-2020.md b/markdown/2020_07_late-report-from-fosdem-2020.md
index e8354f2..73aef9a 100644
--- a/markdown/2020_07_late-report-from-fosdem-2020.md
+++ b/markdown/2020_07_late-report-from-fosdem-2020.md
@@ -110,14 +110,14 @@ This year we improved the organization of the Replicant BoF:
 
 During the BoF, we did a quick presentation of the issues we were having with
 the Android build system. More details on the issues are available on the
-["Android's build system is messier than your distro's" talk][8] that was
+[“Android's build system is messier than your distro's” talk][8] that was
 presented at 36C3.
 
 ### GeckoView
 
 We also did a quick presentation of the freedom issues we were having with
 WebView. As with the build system, more details are also available in a
-presentation (["The Chromium mess meets Android"][9]) that was held at 36C3.
+presentation ([“The Chromium mess meets Android”][9]) that was held at 36C3.
 
 We then got questions and ideas on how to solve that issue.
 
@@ -375,7 +375,7 @@ it currently supports do not respect users freedom, and do run nonfree
 software as well.
 
 Necunos also told us that they had some underlying issues because their
-devices would be "dual use" devices. This is related to the fact that they are
+devices would be “dual use” devices. This is related to the fact that they are
 also targeting some markets like the Finish defense or secret services, but we
 didn't understood what it meant practically speaking.
 
@@ -469,9 +469,9 @@ happened in several conferences throughout the years.
 
 * * *
 
-Edit1: Fixed "ssupported" typo
+Edit1: Fixed “ssupported” typo
 
-Edit2: Fixed the "onthe" typo
+Edit2: Fixed the “onthe” typo
 
 GNUtoo and dllud
 
diff --git a/markdown/2022_06_new-replicant-6-0-0004-release-and-replicant-11-status.md b/markdown/2022_06_new-replicant-6-0-0004-release-and-replicant-11-status.md
index ab4e287..5e6d1b4 100644
--- a/markdown/2022_06_new-replicant-6-0-0004-release-and-replicant-11-status.md
+++ b/markdown/2022_06_new-replicant-6-0-0004-release-and-replicant-11-status.md
@@ -39,7 +39,7 @@ This new release fixes some very serious freedom and privacy issues:
   how to deal with it.
 
 * Several binary firmwares (without source code) related to the back and
-  home "touch" buttons were found and removed with 4 patches ([10],
+  home “touch” buttons were found and removed with 4 patches ([10],
   [11], [12],[13]). The firmwares seem to have only been
   used for factory testing, so the buttons should still work on the devices
   that have them.
@@ -61,7 +61,7 @@ This new release fixes some very serious freedom and privacy issues:
 
 This release may also fix [several bug(s) which made some SIM cards not
 recognizable by Replicant 6.0][19]: we have now merged a fix for one of the
-bug ([#1909][20]) but as we don't know if all the "SIM card not recognized"
+bug ([#1909][20]) but as we don't know if all the “SIM card not recognized”
 bugs are related. We would highly appreciate if those that opened the original
 bug report could confirm if it also fixes their issues as well.
 
@@ -130,9 +130,9 @@ Other improvements were also made:
 
 * [Scripts to switch between OpenGL implementations globally][31] have been
   added to the image as well. Thus, if you want to revert back to the old
-  behaviour, just run "graphics.sh faster" in a root terminal. To switch
-  back to the new behavior you can instead use "graphics.sh compatible".
-  Note that "graphics.sh compatible" will still keep the old OpenGL
+  behaviour, just run “graphics.sh faster” in a root terminal. To switch
+  back to the new behavior you can instead use “graphics.sh compatible”.
+  Note that “graphics.sh compatible” will still keep the old OpenGL
   implementation for the system components mentioned above, so there is
   little risk in trying the scripts.
 
@@ -248,7 +248,7 @@ need to:
 * Take care of the releases (as Replicant developers will probably not have
   these devices, they would not be able to test the releases).
 
-As for the details on what constitute a "replaceable battery", all the
+As for the details on what constitute a “replaceable battery”, all the
 smartphones currently supported by Replicant 6.0 have removable batteries, so
 the batteries are very easy to replace. Compatible batteries can still be
 found in several cities and/or countries.
diff --git a/markdown/2023_12_replicant-37c3.md b/markdown/2023_12_replicant-37c3.md
index 0af6f68..53b4b13 100644
--- a/markdown/2023_12_replicant-37c3.md
+++ b/markdown/2023_12_replicant-37c3.md
@@ -23,17 +23,17 @@ ideas. Please drop by if you feel keen to help on any of these field.
 There will also be a few talks and gatherings about Replicant and related
 topics in several spots around the congress:
 
-* [Short introduction to Replicant as part of the CDC][5] - December 27
+* [Short introduction to Replicant as part of the CDC][5] – December 27
   16:30, Saal E
 
-* [Introduction to Replicant][6] - December 28 10:00, Saal D
+* [Introduction to Replicant][6] – December 28 10:00, Saal D
 
-* [Replicant struggle: past and present successes and failures][7] -
+* [Replicant struggle: past and present successes and failures][7] –
   December 28 14:00, Saal 3, CDC, Round Table
 
-* [Smartphones freedom status in 2023][8] - December 30 12:30, Saal E
+* [Smartphones freedom status in 2023][8] – December 30 12:30, Saal E
 
-* [Replicant Meetup][9] - December 30 14:00, Saal 3, CDC, Round Table
+* [Replicant Meetup][9] – December 30 14:00, Saal 3, CDC, Round Table
 
  [1]: <https://events.ccc.de/congress/2023/wiki/index.php/Main_Page>