aboutsummaryrefslogtreecommitdiffstats
path: root/markdown/2017_12_contributions-to-arcep-work-on-terminal-devices-and-public-consultati...
diff options
context:
space:
mode:
authorDenis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>2024-03-19 16:05:37 +0100
committerDenis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>2025-06-15 01:30:26 +0200
commit37068cada1cc06b5442482d5a1c69e8791e134be (patch)
treecbf0c56facb86900a62fff39dda9b170db14ade0 /markdown/2017_12_contributions-to-arcep-work-on-terminal-devices-and-public-consultation.md
parente254ef843ad19e72eff0327718b769f343835906 (diff)
downloadhaunt-blog-37068cada1cc06b5442482d5a1c69e8791e134be.tar.gz
haunt-blog-37068cada1cc06b5442482d5a1c69e8791e134be.tar.bz2
haunt-blog-37068cada1cc06b5442482d5a1c69e8791e134be.zip
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>
Diffstat (limited to 'markdown/2017_12_contributions-to-arcep-work-on-terminal-devices-and-public-consultation.md')
-rw-r--r--markdown/2017_12_contributions-to-arcep-work-on-terminal-devices-and-public-consultation.md4
1 files changed, 2 insertions, 2 deletions
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