website internationalization (#1922)

* website Internationalization (#1904)

* added devcontainer config

* internationalization under dev

* internationalization of _data done

* overlays internationalization done

* improved routing

* updated gitignore

* remove .devcontainer

* internationalization in progess
deleted all the intermediate files
added translation of few sections

* remaining website strings are added to translation

* done internationalization
- fully converted to i18n plugin
- wrote bash script for creating a combined translations.json

* internationalization UI done

* a quick fix

* remove jq installation

* Added translation using Weblate (German)

* Translated using Weblate (French)

Currently translated at 100.0% (212 of 212 strings)

Translation: SimpleX Chat/SimpleX Chat website
Translate-URL: https://hosted.weblate.org/projects/simplex-chat/website/fr/

* Translated using Weblate (German)

Currently translated at 42.9% (91 of 212 strings)

Translation: SimpleX Chat/SimpleX Chat website
Translate-URL: https://hosted.weblate.org/projects/simplex-chat/website/de/

* fixes of web Internationalization (#1925)

* a quick fix

* blog route for all languages is shifted to root blog route

* wrote merge_translations.js

* remove language label from dropdown

* update language names

* refactor scripts

* remove catch from script

* Added translation using Weblate (Dutch)

* Added translation using Weblate (Norwegian Bokmål)

* Translated using Weblate (Dutch)

Currently translated at 33.0% (70 of 212 strings)

Translation: SimpleX Chat/SimpleX Chat website
Translate-URL: https://hosted.weblate.org/projects/simplex-chat/website/nl/

* website: internationalization fixes (#1931)

* added devcontainer config

* internationalization under dev

* internationalization of _data done

* overlays internationalization done

* improved routing

* updated gitignore

* remove .devcontainer

* internationalization in progess
deleted all the intermediate files
added translation of few sections

* remaining website strings are added to translation

* done internationalization
- fully converted to i18n plugin
- wrote bash script for creating a combined translations.json

* internationalization UI done

* a quick fix

* blog route for all languages is shifted to root blog route

* wrote merge_translations.js

* remove flag from blog

* updated nav stylings & logo links

* add enabled key

* updated nav dropdown styling

* gave specific lang to i18n plugin.
overlay translations are now working.

* enable nl & nb_NO

* updated nav stylings

* updated contact.js

---------

Co-authored-by: M Sarmad Qadeer <msarmadqadeer@gmail.com>

* Translated using Weblate (German)

Currently translated at 47.6% (101 of 212 strings)

Translation: SimpleX Chat/SimpleX Chat website
Translate-URL: https://hosted.weblate.org/projects/simplex-chat/website/de/

* fixed internationalization issues

* updated strings, refactor contact.js

* updated nav stylings for mobile

* a bit smaller padding on mobile

* Added translation using Weblate (Czech)

* Translated using Weblate (Czech)

Currently translated at 100.0% (212 of 212 strings)

Translation: SimpleX Chat/SimpleX Chat website
Translate-URL: https://hosted.weblate.org/projects/simplex-chat/website/cs/

* Translated using Weblate (French)

Currently translated at 100.0% (212 of 212 strings)

Translation: SimpleX Chat/SimpleX Chat website
Translate-URL: https://hosted.weblate.org/projects/simplex-chat/website/fr/

* Translated using Weblate (German)

Currently translated at 100.0% (212 of 212 strings)

Translation: SimpleX Chat/SimpleX Chat website
Translate-URL: https://hosted.weblate.org/projects/simplex-chat/website/de/

* enabled languages

* check/correct (#1949)

---------

Co-authored-by: M Sarmad Qadeer <MSarmadQadeer@gmail.com>
Co-authored-by: Ophiushi <Ophiushi@users.noreply.hosted.weblate.org>
Co-authored-by: mlanp <github@lang.xyz>
Co-authored-by: John m <jvanmanen@gmail.com>
Co-authored-by: zenobit <zen@osowoso.xyz>
Co-authored-by: Ophiushi <41908476+ishi-sama@users.noreply.github.com>

website/src/_includes/overlay_content/simplex_network/card_1.html

@@ -1,53 +1,23 @@
 <p>
-    <a href="https://en.wikipedia.org/wiki/Peer-to-peer">P2P</a>
-    messaging protocols and apps have various problems that make
-    them less reliable than SimpleX, more complex to analyse,
-    and vulnerable to several types of attack.
+    {{ "simplex-network-overlay-card-1-p-1" | i18n({}, lang ) | safe }}
 </p>
 <ol style="list-style: auto; padding-left: 1em;">
     <li>
-        P2P networks rely on some variant of
-        <a href="https://en.wikipedia.org/wiki/Distributed_hash_table">DHT</a>
-        to route messages. DHT designs have to balance delivery guarantee and latency.
-        SimpleX has both better delivery guarantee and lower latency than P2P, because
-        the message can be redundantly passed via several servers in parallel,
-        using the servers chosen by the recipient.
-        In P2P networks the message is passed through <em>O(log N)</em> nodes
-        sequentially, using nodes chosen by the algorithm.
+        {{ "simplex-network-overlay-card-1-li-1" | i18n({}, lang ) | safe }}
     </li>
     <li>
-        SimpleX design, unlike most P2P networks, has no global user identifiers
-        of any kind, even temporary, and only uses temporary pairwise identifiers,
-        providing better anonymity and metadata protection.
+        {{ "simplex-network-overlay-card-1-li-2" | i18n({}, lang ) | safe }}
     </li>
     <li>
-        P2P does not solve
-        <a href="https://en.wikipedia.org/wiki/Man-in-the-middle_attack">MITM attack</a>
-        problem, and most existing implementations do not use out-of-band messages
-        for the initial key exchange. SimpleX uses out-of-band messages or, in some
-        cases, pre-existing secure and trusted connections for the initial key exchange.
+        {{ "simplex-network-overlay-card-1-li-3" | i18n({}, lang ) | safe }}
     </li>
     <li>
-        P2P implementations can be blocked by some Internet providers (like
-        <a href="https://en.wikipedia.org/wiki/BitTorrent">BitTorrent</a>).
-        SimpleX is transport agnostic - it can work over standard web protocols, e.g. WebSockets.
+        {{ "simplex-network-overlay-card-1-li-4" | i18n({}, lang ) | safe }}
     </li>
     <li>
-        All known P2P networks may be vulnerable to
-        <a href="https://en.wikipedia.org/wiki/Sybil_attack">Sybil attack</a>,
-        because each node is discoverable, and the network operates as a whole.
-        Known measures to mitigate it require either a centralized component or expensive
-        <a href="https://en.wikipedia.org/wiki/Proof_of_work">proof of work</a>.
-        SimpleX network has no server discoverability, it is fragmented and operates
-        as multiple isolated sub-networks,
-        making network-wide attacks impossible.
+        {{ "simplex-network-overlay-card-1-li-5" | i18n({}, lang ) | safe }}
     </li>
     <li>
-        P2P networks may be vulnerable to
-        <a href="https://www.usenix.org/conference/woot15/workshop-program/presentation/p2p-file-sharing-hell-exploiting-bittorrent">DRDoS attack</a>,
-        when the clients can rebroadcast and amplify traffic, resulting in network-wide
-        denial of service.
-        SimpleX clients only relay traffic from known connection
-        and cannot be used by an attacker to amplify the traffic in the whole network.
+        {{ "simplex-network-overlay-card-1-li-6" | i18n({}, lang ) | safe }}
     </li>
 </ol>