[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

[tor-commits] [translation/master] pulling translations from transifex

To: tor-commits@xxxxxxxxxxxxxxxxxxxx
Subject: [tor-commits] [translation/master] pulling translations from transifex
From: translation@xxxxxxxxxxxxxx
Date: Fri, 6 Apr 2018 23:42:18 +0000 (UTC)
Delivered-to: archiver@xxxxxxxx
Delivery-date: Fri, 06 Apr 2018 19:42:51 -0400
List-archive: <http://lists.torproject.org/pipermail/tor-commits/>
List-help: <mailto:tor-commits-request@lists.torproject.org?subject=help>
List-id: "auto: code repository commits" <tor-commits.lists.torproject.org>
List-post: <mailto:tor-commits@lists.torproject.org>
List-subscribe: <https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits>, <mailto:tor-commits-request@lists.torproject.org?subject=subscribe>
List-unsubscribe: <https://lists.torproject.org/cgi-bin/mailman/options/tor-commits>, <mailto:tor-commits-request@lists.torproject.org?subject=unsubscribe>
Patch-author: Translation commit bot <translation@xxxxxxxxxxxxxx>
Sender: "tor-commits" <tor-commits-bounces@xxxxxxxxxxxxxxxxxxxx>

commit 403e59d23a7292da1f75424e746b1a92fd70bb8f
Author: Translation commit bot <translation@xxxxxxxxxxxxxx>
Date:   Fri Apr 6 23:42:13 2018 +0000

    pulling translations from transifex
---
 .tx/config              |  9 +++++++++
 de.json                 | 20 ++++++++++++++++++++
 es.json                 | 20 ++++++++++++++++++++
 fr.json                 | 20 ++++++++++++++++++++
 ga.json                 | 20 ++++++++++++++++++++
 id.json                 | 20 ++++++++++++++++++++
 it.json                 | 20 ++++++++++++++++++++
 ja.json                 | 20 ++++++++++++++++++++
 ms_MY.json              | 20 ++++++++++++++++++++
 nl.json                 | 20 ++++++++++++++++++++
 pt_BR.json              | 20 ++++++++++++++++++++
 ro.json                 | 20 ++++++++++++++++++++
 support-connecting.json | 20 ++++++++++++++++++++
 uk.json                 | 20 ++++++++++++++++++++
 zh_CN.json              | 20 ++++++++++++++++++++
 15 files changed, 289 insertions(+)

diff --git a/.tx/config b/.tx/config
new file mode 100644
index 000000000..819a1e2ae
--- /dev/null
+++ b/.tx/config
@@ -0,0 +1,9 @@
+[torproject.support-connectingjson]
+file_filter = <lang>.json
+source_file = support-connecting.json
+source_lang = en
+
+[main]
+host = https://www.transifex.net
+
+minimum_perc = 100
diff --git a/de.json b/de.json
new file mode 100644
index 000000000..05b1a5862
--- /dev/null
+++ b/de.json
@@ -0,0 +1,20 @@
+{
+    "connecting-1": {
+	"id": "#connecting-1",
+	"control": "connecting-1",
+	"title": "Tor-Browser kann sich nicht verbinden, aber es scheint nicht an Zensur-MaÃ?nahmen zu liegen.",
+	"description": "<p class=\"mb-3\">Eines der hÃ¤ufigsten Probleme, die bei Tor-Browser Verbindungsprobleme verursacht, ist eine verstellte System-Uhr. Stelle daher sicher, dass deine System-Uhr und die Zeitzone richtig eingestellt ist. Wenn dies das Problem nicht behebt, besuche die Fehlerbehebungsseite in der <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\";>Tor-Browser-Anleitung</a></mark>.</p>"
+    },
+    "connecting-2": {
+	"id": "#connecting-2",
+	"control": "connecting-2",
+	"title": "Ich habe Probleme mich mit Tor zu verbinden und kann die Ursache nicht finden.",
+	"description": "<p class=\"mb-3\">Wenn du Verbindungsprobleme hast, wÃ¤hle bitte die Option \"Tor-Protokoll in die Zwischenablage kopieren\" aus. FÃ¼ge dann das Tor-Protokoll in eine Textdatei oder ein anderes Dokument ein. Du solltest nun einen der folgenden verbreiteten FehlereintrÃ¤ge sehen (suche nach foldenden Zeilen in deinem Tor-Protokoll):</p><h5>Ã?blicher Fehlereintrag #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code>2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150\n2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server\n2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server\n2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")\n2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")\n2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to
  connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">Wenn du solche Zeilen in deinem Tor-Protokoll siehst bedeutet das, dass die Verbindung zu einem SOCKS-Proxy fehlschlÃ¤gt. Wenn fÃ¼r deine Netzwerkkonfiguration ein SOCKS-Proxy erforderlich ist, stelle sicher, dass du die erforderlichen Proxy-Daten korrekt eingegeben hast. Wenn kein SOCKS-Proxy benÃ¶tigt wird oder du diesbezÃ¼glich nicht sicher bist, versuche ohne SOCKS-Proxy eine Verbindung zum Tor-Netzwerk herzustellen.<p><h5>Ã?blicher Fehlereintrag #2: Kann WÃ¤chter-Weiterleitung nicht erreichen</h5><p class=\"mb-3\"><pre><code>11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150\n11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network\n11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.\n11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop\n11/1/20
 17 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">Wenn du solche Zeilen in deinem Tor-Protokoll siehst bedeutet das, dass die Verbindung des Tor-Clients mit dem ersten Knoten im Tor-Circuit fehlschlÃ¤gt. Dies kann bedeuten, dass du dich in einem zensierten Netzwerk befindest. Versuche dich mit BrÃ¼cken zu verbinden, was das Problem beheben sollte.</p><h5>Ã?blicher Fehlereintrag #3: Fehlschlag bei der VervollstÃ¤ndigung des TLS-Handschlags</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server\n13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx)\n13-11-17 19:53:49.300 [WARN] 10 connections have failed:\n13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read
  server hello A in HANDSHAKE\n13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">Wenn du solche Zeilen in deinem Tor-Protokoll siehst bedeutet das, dass dein Tor-Client einen TLS-Handschlag mit den Verzeichnisinstanzen nicht erfolgreich abschlieÃ?en konnte. Die Verwendung von BrÃ¼cken wird das wahrscheinlich beheben.</p><h5>Ã?blicher Fehlereintrag #4: Taktversatz</h5><p class=\"mb-3\"><pre><code>19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150\n19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server\n19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server\n19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead.\nTor requires an accurate clock to work: please check your time, timezone, and d
 ate settings.</code></pre></p><p class=\"mb-3\">Wenn du solche Zeilen in deinem Tor-Protokoll siehst bedeutet das, dass deine System-Uhr verstellt ist. Bitte stelle sicher, dass deine System-Uhr und die entsprechende Zeitzone richtig gestellt sind. Starte Tor danach neu.</p>"
+    },
+    "connecting-3": {
+	"id": "#connecting-3",
+	"control": "connecting-3",
+	"title": "Ich kann X.onion nicht erreichen!",
+	"description": "<p class=\"mb-3\">Wenn du den gewÃ¼nschten Onion-Dienst nicht erreichen kannst, stelle sicher, dass du die 16 Zeichen lange Onion-Adresse richtig eingegeben hast: Sogar ein kleiner Tippfehler verhindert, dass Tor-Browser die Website finden kann. Wenn du dich dann mit dem Onion-Dienst immer noch nicht verbinden kannst, versuche es spÃ¤ter noch einmal. Es kann vorÃ¼bergehende Verbindungsprobleme im Netz geben oder die Seitenbetreiber haben ohne Vorwarnung die Seite vom Netz genommen.</p><p class=\"mb-3\">Du kannst auch Ã¼berprÃ¼fen, ob es dir grundsÃ¤tzlich mÃ¶glich ist Onion-Dienste zu nutzen, in dem du dich mit <a href=\"http://3g2upl4pq6kufc4m.onion\";>DuckDuckGo</a>s Onion-Dienst verbindest.</p>"
+    }
+}
diff --git a/es.json b/es.json
new file mode 100644
index 000000000..5f8938425
--- /dev/null
+++ b/es.json
@@ -0,0 +1,20 @@
+{
+    "connecting-1": {
+	"id": "#connecting-1",
+	"control": "connecting-1",
+	"title": "El Navegador Tor no conecta, pero no parece ser un problema con la censura.",
+	"description": "<p class=\"mb-3\">Uno de los problemas mÃ¡s habituales que causa errores de conexiÃ³n en el Navegador Tor es un reloj del sistema incorrectamente ajustado. Por favor, asegÃºrate de que el reloj de tu sistema y tu zona horaria estÃ¡n configurados correctamente. Si esto no soluciona tu problema, dirÃgete a la pÃ¡gina de SoluciÃ³n de Problemas en el <mark><a href=\"https://tb-manual.torproject.org/es-ES/bridges.html\";>manual del Navegador Tor</a></mark></p>"
+    },
+    "connecting-2": {
+	"id": "#connecting-2",
+	"control": "connecting-2",
+	"title": "Estoy teniendo problemas conectando a Tor, y no logro averiguar quÃ© es lo que estÃ¡ mal.",
+	"description": "Si tienes problemas para conectarte, por favor selecciona la opciÃ³n \"copiar el registro de Tor al portapapeles\". Luego pega el registro Tor en un archivo de texto u otro documento. DeberÃas ver uno de estos errores comunes de registro (busca las siguientes lÃneas en tu registro Tor): Error comÃºn de registro #1: Fallo de conexiÃ³n proxy 2017-10-29 09:23:40.800[NOTICE] Abriendo socks en 127.0.0.1:9150\n2017-10-29 09:23:47.900[NOTICE] Bootstrapped 5%: ConexiÃ³n al servidor de directorios\n2017-10-29 09:23:47.900[NOTICE] Bootstrapped 10%: Finaliza hankshake con el servidor de directorios\n2017-10-29 09:24:08.900[ADVERTENCIA] Cliente proxy: incapaz de conectarse a xx... xxx... xxx. xx: xxxxx (\"fallo general del servidor SOCKS\")\n2017-10-29 09:24:08.900[ADVERTENCIA] Cliente proxy: incapaz de conectarse a xx... xxx... xxx. xx: xxxxx (\"fallo general del servidor SOCKS\")\n2017-10-29 09:24:08.900[ADVERTENCIA] Cliente proxy: incapaz de conectar toxx.. xxx.. xxx. xx: 
 xxxxxxx (\"fallo general del servidor SOCKS\") Si ves lÃneas como estas en tu registro Tor, significa que no te estÃ¡s conectando a un proxy SOCKS. Si se requiere un proxy SOCKS para la configuraciÃ³n de red, asegÃºrate de introducir correctamente los datos del proxy. Error de registro comÃºn #2: No se puede llegar a los relÃ©s de guardia 11/1/2017 21:11:43 PM. 500[AVISO] Abriendo el socks en 127.0.0.1:9150\n11/1/2017 21:11:44 PM. 300[AVISO] Bootstrapped 80%: ConexiÃ³n a la red Tor\n11/1/2017 21:11:44 PM. 300[ADVERTENCIA] No encontramos nodo para el salto 0 de nuestro camino. Descartar este circuito.\n11/1/2017 21:11:44 PM. 500[AVISO] Bootstrapped 85%: Acabando el  handshake con el primer salto\n11/1/2017 21:11:11:45 PM. 300[ADVERTENCIA] No se ha encontrado nodo para el salto 0 de nuestra ruta. Descartando este circuito: si ves lÃneas como estas en tu registro Tor, significa que tu Tor no se conectÃ³ al primer nodo del circuito Tor. Esto podrÃa significar que estÃ¡s en una red ce
 nsurada. Error de registro comÃºn #3: No se pudo completar el handshake TLS 13-11-17 19:52:24:24.300[ATENCIÃ?N) Bootstrapped 10%: Finalizar handshake con el servidor de directorios\n13-11-17 19:53:49.300[ADVERTENCIA] Problema con el bootstrapping. Atascado al 10%: Acabando handshake con el servidor de directorios. (HECHO; HECHO; conteo 10; recomendaciÃ³n; host[host] en xxx. xxx. xxx. xxx. xx: xxx)\n13-11-17 19:53:49.300[ATENCIÃ?N] 10 conexiones han fallado:\n13-11-17 19:53:49.300[ADVERTENCIA] 9 conexiones caidas en estado handshaking (TLS) con estado SSL SSLv2/v3 lea servidor hola A en HANDSHAKE\n13-11-17 19:53:49.300[ADVERTENCIA] 1 conexiones muertas en estado connect()ing con estado SSL (sin objeto SSL) Si ves lÃneas como esta en tu registro de Tor, significa que Tor no pudo completar un handshake TLS con las competencias del directorio. Error de registro comÃºn #4: DesviaciÃ³n del reloj 19.11.2017 00:04:47.400[ATENCIÃ?N] IntÃ©rprete de socks de apertura en 127.0.0.0.1:9150\n19.1
 1.2017 00:04:48.000[ADVERTENCIA] Bootstrapped 5%: ConexiÃ³n al servidor de directorios\n19.11.2017 00:04:48.200[ADVERTENCIA] Bootstrapped 10%: Finalizando el handshake con el servidor de directorios\n19.11.2017 00:04:48.800[ADVERTENCIA] Celda de NETINFO recibida con tiempo sesgado (OR: xxx. xx. xx. xx: xxxx): Parece que nuestro reloj estÃ¡ atrasado 1 dÃa, 0 horas, 1 minutos, o que el suyo estÃ¡ adelantado.\nTor requiere un reloj preciso para funcionar: por favor, comprueba tus ajustes de hora, zona horaria y fecha Si ves lÃneas como esta en tu registro Tor, significa que el reloj de tu sistema es incorrecto. AsegÃºrate de que tu reloj estÃ¡ ajustado correctamente, incluyendo la zona horaria. A continuaciÃ³n, reinicia Tor."
+    },
+    "connecting-3": {
+	"id": "#connecting-3",
+	"control": "connecting-3",
+	"title": "Â¡No puedo conectar a X.onion!",
+	"description": "<p class=\"mb-3\">Si no puede alcanzar el servicio onion que desea, asegÃºrese de que ha introducido correctamente la direcciÃ³n onion de 16 caracteres: incluso un pequeÃ±o error evitarÃ¡ que el Navegador Tor logre alcanzar el sitio. Si aÃºn asÃ no puede conectar al servicio onion, por favor, intÃ©ntelo de nuevo mÃ¡s tarde. Puede haber un problema temporal con la conexiÃ³n, o los operadores del sitio pueden haberle permitido desconectar sin avisar.</p><p class=\"mb-3\">TambiÃ©n puede asegurarse de que es capaz de acceder a otros servicios onion conectando al servicio onion de <a href=\"http://3g2upl4pq6kufc4m.onion\";>DuckDuckGo</a>.</p>"
+    }
+}
diff --git a/fr.json b/fr.json
new file mode 100644
index 000000000..4ed10c84e
--- /dev/null
+++ b/fr.json
@@ -0,0 +1,20 @@
+{
+    "connecting-1": {
+	"id": "#connexion-1",
+	"control": "connexion-1",
+	"title": "Le navigateur Tor nâ??arrive pas Ã  se connecter, mais il ne semble pas que ce soit un problÃ¨me de censure.",
+	"description": "<p class=\"mb-3\">Lâ??un des problÃ¨mes les plus courants qui entraÃ®ne des erreurs de connexion dans le navigateur Tor est une horloge systÃ¨me qui nâ??est pas Ã  lâ??heure. Veuillez vous assurer que votre horloge systÃ¨me et votre fuseau horaire sont rÃ©glÃ©s avec prÃ©cision. Si le problÃ¨me persiste, voir la page DÃ©pannage du <mark><a href=\"https://tb-manual.torproject.org/fr/bridges.html\";>â??guide du navigateur Tor</a></mark>.</p>"
+    },
+    "connecting-2": {
+	"id": "#connexion-2",
+	"control": "connexion-2",
+	"title": "Jâ??Ã©prouve des difficultÃ©s Ã  me connecter Ã  Tor et je nâ??arrive pas Ã  comprendre ce qui ne va pas.",
+	"description": "<p class=\"mb-3\">Si vous Ã©prouvez des difficultÃ©s Ã  vous connecter, veuillez sÃ©lectionner lâ??option Â«Â Copier le journal de Tor dans le presse-papiersÂ Â». Collez ensuite le journal de Tor dans un fichier texte ou un autre document. Vous devriez trouver lâ??une de ces erreurs de journal habituelles (cherchez les lignes suivantes dans votre journal de Tor)Â : </p><h5>Erreur habituelle de journal noÂ 1 : Ã©chec de connexion au mandataire</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150\n2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server\n2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server\n2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")\n2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")\n
 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">Si vous rencontrez de telles lignes dans votre journal de Tor, cela signifie que vous nâ??arrivez pas Ã  vous connecter Ã  un mandataire SOCKS. Si un mandataire SOCKS est nÃ©cessaire Ã  la configuration de rÃ©seau, veuillez alors vous assurer dâ??avoir bien saisi les renseignements concernant le mandataire. Si un mandataire SOCKS nâ??est pas nÃ©cessaire ou si vous ne savez pas, veuillez tenter de vous connecter au rÃ©seau Tor sans mandataire SOCKS.<p><h5>Erreur habituelle de journal noÂ 2 : impossible dâ??atteindre les relais gardes</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150\n11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network\n11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.\n11/1/
 2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop\n11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">Si vous rencontrez de telles lignes dans votre journal de Tor, cela signifie que vous nâ??arrivez pas Ã  vous connecter au premier nÅ?ud du circuit Tor. Cela pourrait signifier que vous Ãªtes sur un rÃ©seau qui est censurÃ©. Tentez de vous connecter avec des ponts, ce qui devrait corriger la situation.</p><h5>Erreur habituelle de journal noÂ 3 : Ã©chec dâ??Ã©tablissement dâ??une liaison TLS</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server\n13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx)\n13-11-17 19:53:49.300 [WARN] 10 connections have failed:\n13-11-17 19
 :53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE\n13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\"> Si vous rencontrez de telles lignes dans votre journal de Tor, cela signifie que Tor n'a pas rÃ©ussi Ã  Ã©tablir une liaison TLS avec les autoritÃ©s d'annuaire. Lâ??utilisation de ponts corrigera certainement cette situation.</p><h5>Erreur habituelle de journal noÂ 4 : dÃ©calage dâ??horloge</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150\n19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server\n19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server\n19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or t
 hat theirs is ahead.\nTor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">\nSi vous rencontrez de telles lignes dans votre journal de Tor, cela signifie que votre horloge systÃ¨me nâ??est pas juste. Veuillez vous assurer que votre horloge est rÃ©glÃ©e avec prÃ©cision, fuseau horaire inclus, puis redÃ©marrez Tor. </p>"
+    },
+    "connecting-3": {
+	"id": "#connexion-3",
+	"control": "connexion-3",
+	"title": "Je ne peux pas accÃ©der Ã  X.onionâ??!",
+	"description": "<p class=\"mb-3\">Si vous ne pouvez pas atteindre le service oignon que vous souhaitez, assurez-vous dâ??avoir saisi correctement lâ??adresse oignon de 16 caractÃ¨res. Toute erreur, mÃªme minime, empÃªchera le navigateur Tor dâ??atteindre le site. Si vous nâ??arrivez toujours pas Ã  vous connecter au service oignon, veuillez ressayer ultÃ©rieurement. Il pourrait y avoir un problÃ¨me temporaire de connexion ou les exploitants du site pourraient lâ??avoir dÃ©sactivÃ© sans avertissement.</p><p class=\"mb-3\">Vous pouvez aussi vous assurer que vous arrivez Ã  accÃ©der Ã  dâ??autres services oignon en vous connectant au service oignon de <a href=\"http://3g2upl4pq6kufc4m.onion\";>DuckDuckGo</a>.</p>\n\n"
+    }
+}
diff --git a/ga.json b/ga.json
new file mode 100644
index 000000000..26d45c2d5
--- /dev/null
+++ b/ga.json
@@ -0,0 +1,20 @@
+{
+    "connecting-1": {
+	"id": "#connecting-1",
+	"control": "connecting-1",
+	"title": "NÃ fÃ©idir le BrabhsÃ¡laÃ Tor ceangal a bhunÃº, cÃ© nach mbaineann an fhadhb le cÃºrsaÃ cinsireachta.",
+	"description": "<p class=\"mb-3\">Is minic go mbÃonn fadhb le clog an chÃ³rais ina chÃºis le hearrÃ¡idÃ i mBrabhsÃ¡laÃ Tor. Ba chÃ³ir duit deimhniÃº go bhfuil clog an chÃ³rais agus an crios ama socraithe mar is ceart. Mura rÃ©itÃonn seo an fhadhb, fÃ©ach an leathanach FabhtcheartÃº i <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\";>LÃ¡mhleabhar BhrabhsÃ¡laÃ Tor</a></mark>.</p>"
+    },
+    "connecting-2": {
+	"id": "#connecting-2",
+	"control": "connecting-2",
+	"title": "NÃ fÃ©idir liom ceangal le lÃonra Tor, agus nÃ thuigim cad Ã© an fhadhb.",
+	"description": "<p class=\"mb-3\">MÃ¡ tÃ¡ fadhb agat ag ceangal le lÃonra Tor, ÃºsÃ¡id an rogha â??cÃ³ipeÃ¡il logchomhad Tor go dtÃ an ghearrthaisce.â?? Ansin, greamaigh an logchomhad i dtÃ©acschomhad nÃ³ cÃ¡ipÃ©is eile. Is dÃ³cha go bhfeicfidh tÃº ceann de na hearrÃ¡idÃ coitianta seo (cuardaigh na lÃnte seo a leanas sa logchomhad):</p><h5>EarrÃ¡id choitianta #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to co
 nnect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">MÃ¡ fheiceann tÃº na lÃnte seo i do logchomhad Tor, ciallaÃonn siad gur theip ort ceangal a bhunÃº le seachfhreastalaÃ SOCKS. MÃ¡ theastaÃonn seachfhreastalaÃ SOCKS uait ar do lÃonra, deimhnigh gur chuir tÃº mionsonraÃ an fhreastalaÃ isteach go ceart. Mura dteastaÃonn seachfhreastalaÃ SOCKS uair, nÃ³ mura bhfuil tÃº cinnte, dÃ©an iarracht ceangal a bhunÃº le lÃonra Tor gan seachfhreastalaÃ SOCKS.<p><h5>EarrÃ¡id choitianta #2: Canâ??t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] F
 ailed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">MÃ¡ fheiceann tÃº na lÃnte seo i do logchomhad Tor, ciallaÃonn sÃ© gur theip ort ceangal a bhunÃº leis an chÃ©ad nÃ³d sa gciorcad Tor. Uaireanta, ciallaÃonn seo go bhfuil do lÃonra faoi chinsireacht. Bain triail as ceangal trÃ dhroichead; is dÃ³cha go rÃ©iteoidh sin an fhadhb.</p><h5>EarrÃ¡id choitianta #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 co
 nnections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">MÃ¡ fheiceann tÃº na lÃnte seo i do logchomhad Tor, ciallaÃonn sÃ© gur theip ar Tor croitheadh lÃ¡imhe TLS leis na hÃºdarÃ¡is a chur i gcrÃch. Is dÃ³cha go rÃ©iteoidh droichead an fhadhb seo.</p><h5>EarrÃ¡id choitianta #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">MÃ¡ fheiceann tÃº na lÃnte seo i do logchomhad Tor, c
 iallaÃonn sÃ© go bhfuil an clog i do rÃomhaire mÃcheart. Ba chÃ³ir duit socruithe an chloig a dheimhniÃº, an t-am, dÃ¡ta, agus crios ama san Ã¡ireamh. Ansin, atosaigh Tor. </p>"
+    },
+    "connecting-3": {
+	"id": "#connecting-3",
+	"control": "connecting-3",
+	"title": "NÃlim in ann teacht ar X.onion!",
+	"description": "<p class=\"mb-3\">Mura bhfuil tÃº in ann seirbhÃs .onion a shroicheadh, deimhnigh gur chuir tÃº an seoladh 16-carachtar isteach go ceart: mÃ¡ tÃ¡ aon bhotÃºn ann, fiÃº botÃºn an-bheag, nÃ bheidh BrabhsÃ¡laÃ Tor in ann an suÃomh a shroicheadh. MÃ¡ tÃ¡ tÃº cinnte gur chuir tÃº an seoladh ceart isteach, bain triail eile as ar ball. Seans go bhfuil fadhb shealadach leis an lÃonra, nÃ³ b'fhÃ©idir gur bhain riarthÃ³irÃ an tsuÃmh as lÃne Ã© gan rabhadh.</p><p class=\"mb-3\">B'fhiÃº freisin fÃ©achaint an fÃ©idir leat dul i dteagmhÃ¡il le seirbhÃsÃ .onion eile, mar shampla <a href=\"http://3g2upl4pq6kufc4m.onion\";>seirbhÃs DuckDuckGo</a>.</p>"
+    }
+}
diff --git a/id.json b/id.json
new file mode 100644
index 000000000..0fdc118e3
--- /dev/null
+++ b/id.json
@@ -0,0 +1,20 @@
+{
+    "connecting-1": {
+	"id": "#connecting-1",
+	"control": "connecting-1",
+	"title": "Tor Browser tidak dapat tersambung, tapi ini tampaknya bukan akibat sensor oleh pihak lain.",
+	"description": "<p class=\"mb-3\">Salah satu masalah umum yang menyebabkan kegagalan koneksi di Tor Browser adalah jam sistem operasi yang tidak tepat. Silakan pastikan jam di sistem operasi dan zona waktu diatur dengan tepat di komputer Anda. Jika ini tidak memperbaiki masalah koneksi, lihat halaman Troubleshooting di <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\";>petunjuk Tor Browser</a></mark>.</p>"
+    },
+    "connecting-2": {
+	"id": "#connecting-2",
+	"control": "connecting-2",
+	"title": "Saya mengalami masalah dalam terhubung ke Tor, dan saya tidak dapat mengetahui apa yang salah.",
+	"description": "<p class=\"mb-3\"> Jika Anda mendapat masalah dalam terhubung ke jaringan Tor, silakan pilih \"copy Tor Log ke clipboard.\" Lalu, salin ke Notepad atau program dokumen lain. Anda seharusnya dapat melihat log error umum seperti ini (cari baris-baris seperti di bawah ini):\n\n</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS se
 rver failure\")</code></pre></p><p class=\"mb-3\">Jika Anda melihat baris seperti ini, Anda gagal terkoneksi ke proxy SOCKS. Jika proxy SOCKS diperlukan di pengaturan jaringan Anda, silakan pastikan Anda telah memasukkan detail proxy dengan akurat. Jika proxy SOCKS tidak diperlukan, atau Anda tidak yakin bahwa proxy SOCKS diperlukan, silakan coba tanpa proxy SOCKS.\n\n<p><h5>Common log error #2: Canâ??t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\"> Jika Anda melihat baris seperti ini, Tor 
 gagal tersambung ke node pertama di Tor circuit. Ini mungkin artinya Anda berada di jaringan yang terkena sensor pihak lain. Silakan coba gunakan bridge.\n\n</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">Jika Anda melihat baris seperti ini, artinya Tor gagal melakukan TLS handshake dengan otoritas directory. Gunakan bridge untuk 
 masalah ini.<h5>\n\nCommon log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. Tor memerlukan jam yang akurat supaya berfungsi dengan baik. Silakan periksa pengaturan waktu, zona waktu, dan tanggal. Pastikan jam di komputer Anda diatur dengan benar, termasuk zona waktu yang tepat. Lalu, restart Tor.\n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set 
 accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "connecting-3": {
+	"id": "#connecting-3",
+	"control": "connecting-3",
+	"title": "Tidak dapat terhubung ke X.onion!",
+	"description": "<p class=\"mb-3\">Jika Anda tidak dapat terhubung ke sebuah onion service yang diinginkan, pastikan Anda telah dengan tepat memasukkan 16-karakter alamat onion-nya. Bahkan kesalahan sedikit akan membuat Tor Browser tidak dapat terhubung ke situs yang dimaksud. Jika Anda tetap tidak dapat terhubung, silakan coba lagi nanti. Mungkin ada masalah sedikit di situsnya, atau operator situsnya sedang membuat situsnya menjadi offline tanpa pemberitahuan. </p><p class=\"mb-3\">Anda juga dapat memastikan jika Anda juga dapat terhubung ke situs onion service lain dengan mencoba terhubung ke <a href=\"http://3g2upl4pq6kufc4m.onion\";>DuckDuckGo</a>."
+    }
+}
diff --git a/it.json b/it.json
new file mode 100644
index 000000000..7a04f1284
--- /dev/null
+++ b/it.json
@@ -0,0 +1,20 @@
+{
+    "connecting-1": {
+	"id": "#connessione-1",
+	"control": "connessione-1",
+	"title": "Tor Browser non si connette, ma non sembra che sia dovuto alla censura.",
+	"description": "<p class=\"mb-3\">Uno dei problemi piÃ¹ comuni che causano errori di connessione in Tor Browser Ã¨ un orologio di sistema errato. Assicurati che l'orologio di sistema e il fuso orario siano impostati correttamente. Se ciÃ² non risolve il problema, consultare la pagina Risoluzione dei problemi su <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\";>manuale di Tor Browser</a></mark>.</p>"
+    },
+    "connecting-2": {
+	"id": "#connessione-2",
+	"control": "connessione-2",
+	"title": "Sto avendo problemi nella connessione a Tor e non riesco a capire quale sia la causa.",
+	"description": "<p class=\"mb-3\">Se stai avendo problemi a connetterti, per favore seleziona l'opzione \"copia i log di Tor sulla clipboard.\" Poi incolla il log di Tor su un file di testo o un altro tipo di documento. Dovresti vedere uno di questi errori di log comuni (cerca per le seguenti linee nei log di Tor):</p><h5>Errore di log comune #1: Errore di connessione Proxy </h5><p class=\"mb-3\"><pre><code>2017-10-29 09:23:40.800 [AVVISO] Apertura ascoltatore porte Socks su 127.0.0.1:9150\n2017-10-29 09:23:47.900 [AVVISO] Progressione 5%: Connessione all'elenco dei server\n2017-10-29 09:23:47.900 [AVVISO] Progressione 10%: Completando l'handshake con l'elenco dei server\n2017-10-29 09:24:08.900 [ATTENZIONE] Proxy Client: impossibile connettersi a xx.xx.xxx.xxx.xx:xxxxx (\"errore generale server SOCKS\")\nÂ 2017-10-29 09:24:08.900 [ATTENZIONE] Proxy Client: impossibile connettersi a xx.xx.xxx.xxx.xx:xxxxx (\"errore generale server SOCKS\")\n2017-10-29 09:24:08.900 [ATTENZIONE] Prox
 y Client: impossibile connettersi a xx..xxx..xxx.xx:xxxxx (\"errore generale server SOCKS\")</code></pre></p><p class=\"mb-3\">Se vedi delle linee come queste nei log di Tor, significa che la connessione a un proxy SOCKS sta fallendo.Se un proxy SOCKS Ã¨ richiesto per la tua configurazione di rete, controlla di aver inserito i dettagli del proxy correttamente.Se un proxy SOCKS non Ã¨ richiesto, o non ne sei sicuro, prova a connetterti alla rete Tor senza un proxy SOCKS.<p><h5>Errore di log comune #2: Non Ã¨ possibile raggiungere i guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [AVVISO] Apertura ascoltatore porte Socks su 127.0.0.1:9150 \n11/1/2017 21:11:44 PM.300 [AVVISO] Progressione 80%: Connessione alla rete Tor\n11/1/2017 21:11:44 PM.300 [ATTENZIONE] Impossibile trovare nodo hop 0 sull'instradamento. Circuito scartato.\n11/1/2017 21:11:44 PM.500 [AVVISO] Progressione 85%: Terminando l'handshake con il primo hop\nÂ 11/1/2017 21:11:45 PM.300 [ATTENZIONE] 
 Impossibile trovare nodo hop 0 sull'instradamento. Circuito scartato.</code></pre></p><p class=\"mb-3\">Se vedi delle linee come questo nel tuo log di Tor, significa che Tor ha fallito la connesione al primo nodo del circuito Tor. Questo potrebbe significare che ti trovi su una rete censurata. Per favore prova a connetterti con i bridge, e questo dovrebbe risolvere il problema.</p><h5>Errore di log comune #3: Errore nel completare l'handshake TLS</h5><p class=\"mb-3\"><pre><code>13-11-17 19:52:24.300 [AVVISO] Progressione 10%: Handshake con l'elenco dei server completato\n13-11-17 19:53:49.300 [ATTENZIONE] Problema durante la progressione. Fermo al 10%: Completando l'handshake con l'elenco dei server (FATTO; FATTO; contatore 10; avviso di raccomandazione; host [host] a xxx.xxx.xxx.xx:xxx)\n13-11-17 19:53:49.300 [ATTENZIONE] 10 connessioni hanno fallito:\n13-11-17 19:53:49.300 [ATTENZIONE] 9 connessioni sono scadute durante lo stato di handshaking (TLS) con lo stato SSL di SSLv2/v3 r
 isposta server hello A in HANDSHAKE \n13-11-17 19:53:49.300 [ATTENZIONE] 1 connessione Ã¨ scaduta nello stato di connessione con stato SSL (Nessun oggetto SSL)</code></pre></p><p class=\"mb-3\">Se vedi delle linee cosÃ¬ nel tuo log Tor, significa che Tor ha fallito il completamento dell'handshake TLS con le autoritÃ  dell'elenco. Usare i bridge risolverÃ  probabilmente il problema.</p><h5>Errore log comune #4: Distorsione orario</h5><p class=\"mb-3\"><pre><code>19.11.2017 00:04:47.400 [AVVISO] Apertura ascoltatore porte SOCKS su 127.0.0.1:9150\n19.11.2017 00:04:48.000 [AVVISO] Progressione 5%: Connessione all'elenco dei server\n19.11.2017 00:04:48.200 [AVVISO] Progressione 10%: Terminando l'handshake con l'elenco dei server\n19.11.2017 00:04:48.800 [ATTENZONE] Ricevuta cella NETINFO con orario distorto (O:xxx.xx.x.xx:xxxx): Sembra che il tuo orologio sia indietro di 1 giorno, 0 ore, 1 minuto, o che il loro sia avanti.\nTor richiede un orologio accurato per funzionare: per favore con
 trolla l'ora, la tua zona temporale e le impostazioni sulla data.</code></pre></p><p class=\"mb-3\">Se vedi queste linee nel tuo log di Tor, significa che l'ora del sistema Ã¨ incorretta. Per favore controlla che il tuo orologio sia impostato accuratamente, inclusa la zona temporale. DopodichÃ© riavvia Tor.</p>"
+    },
+    "connecting-3": {
+	"id": "#connessione-3",
+	"control": "connessione-3",
+	"title": "Non posso raggiungere X.onion!",
+	"description": "<p class=\"mb-3\">Se non riesci a raggiungere il sito che desideri, assicurati di aver inserito correttamente l'indirizzo a 16 caratteri: anche un piccolo errore puÃ² impedire al Tor Browser di raggiungere il sito. Se non riesci ancora a connetterti al sito, riprova piÃ¹ tardi. Potrebbe esserci un problema di connessione temporaneo, oppure gli operatori del sito lo hanno lasciato andare offline senza lasciare preavviso.</p><p class=\"mb-3\">Puoi anche provare a connetterti a <a href=\"http://3g2upl4pq6kufc4m.onion\";>DuckDuckGo</a> per vedere se riesci ad accedere ad altri siti.</p>"
+    }
+}
diff --git a/ja.json b/ja.json
new file mode 100644
index 000000000..24309f341
--- /dev/null
+++ b/ja.json
@@ -0,0 +1,20 @@
+{
+    "connecting-1": {
+	"id": "#æ?¥ç¶?-1",
+	"control": "æ?¥ç¶?-1",
+	"title": "Torã??ã?©ã?¦ã?¶ã?¼ã?¯æ?¥ç¶?ã??ã?¾ã??ã??ã??ã??æ¤?é?²ã?®å??é¡?ã?§ã?¯ã?ªã??ã??ã??ã?§ã??ã??",
+	"description": "Torã??ã?©ã?¦ã?¶ã?¼ã?§æ?¥ç¶?ã?¨ã?©ã?¼ã??ç?ºç??ã??ã??æ??ã??ä¸?è?¬ç??ã?ªå??é¡?ã?®1ã?¤ã?¯ã??ä¸?æ£ã?ªã?·ã?¹ã??ã? ã?¯ã?ã??ã?¯ã?§ã??ã??ã?·ã?¹ã??ã? ã?®æ??è¨?ã?¨ã?¿ã?¤ã? ã?¾ã?¼ã?³ã??æ£ç¢ºã?«è¨å®?ã??ã??ã?¦ã??ã??ã??ã?¨ã??ç¢ºèª?ã??ã?¦ã??ã? ã??ã??ã??ã??ã??ã?§å??é¡?ã??è§£æ±ºã??ã?ªã??å ´å??ã?¯ã??Torã??ã?©ã?¦ã?¶ã?¼ã?®ã??ã??ã?¥ã?¢ã?«ã?®ã??ã?©ã??ã?«ã?·ã?¥ã?¼ã??ã?£ã?³ã?°ã?®ã??ã?¼ã?¸ã??å??ç?§ã??ã?¦ã??ã? ã??ã??ã??"
+    },
+    "connecting-2": {
+	"id": "#æ?¥ç¶?-2",
+	"control": "æ?¥ç¶?-2",
+	"title": "Torã?«ã?¢ã?¯ã?»ã?¹ã?§ã??ã?ªã??ã??ã??ä½?ã??å??é¡?ã?ªã?®ã??å??ã??ã??ã?¾ã??ã??ã??",
+	"description": "<p class=\"mb-3\">Torã?«ã?¢ã?¯ã?»ã?¹ã?§ã??ã?ªã??å ´å??ã??ã??Torã?ã?°ã??ã?¯ã?ªã??ã??ã??ã?¼ã??ã?«ã?³ã??ã?¼ã??ã??ã??é?¸æ??è?¢ã??é?¸ã??ã?§ã??ã?ã?°ã??ã?¡ã?¢å¸³ã??ã??ã??ã?¯ã??ã?ã?¥ã?¡ã?³ã??ã??ã?¡ã?¤ã?«ã?«è²¼ã??ä»?ã??ã?¦ä¸?ã??ã??ã??ä»¥ä¸?ã?®è?¯ã??ã??ã??ã?¨ã?©ã?¼ã?¡ã??ã?»ã?¼ã?¸ã??è¦?ã?¤ã??ã??ã?¯ã??ã?§ã??ï¼?</p><h5>ã??ã??ã??ã??ã?ã?°ã?¨ã?©ã?¼#1: ã??ã?ã?ã?·æ?¥ç¶?å¤±æ??</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..
 xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\")</code></pre></p><p class=\"mb-3\">Torã?ã?°ã?«ã??ã?®ã??ã??ã?ªè¡?ã??ã??ã??ã?°ã??SOCKSã??ã?ã?ã?·ã?¨ç¹?ã??ã??ã?ªã??ã?¨ã??ã??ã??ã?¨ã?§ã??ã??ã??ã??ã??ã?¯ã?¼ã?¯ã?«ã?¯SOCKSã??ã?ã?ã?·ã??å¿?è¦?ã?ªã??ã??è¨å®?ã??ç¢ºèª?ã??ã?¦ä¸?ã??ã??ã??SOCKSã??ã?ã?ã?·ã??å¿?è¦?ã?§ã?¯ã?ªã??å ´å??ã??ã??ã??ã??ã?¯ã??ã??å??ã??ã??ã?ªã??å ´å??ã??SOCKSã??ã?ã?ã?·ç?¡ã??ã?§Torã?«ã?¢ã?¯ã?»ã?¹ã??ã?¦ã?¿ã?¦ä¸?ã??ã??ã??<p><h5>ã??ã??ã??ã??ã?ã?°ã?¨ã?©ã?¼#2: ã?¬ã?¼ã??ã?ªã?¬ã?¼ã?¨æ?¥ç¶?ã?§ã??ã?ªã??</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discardi
 ng this circuit.</code></pre></p><p class=\"mb-3\">Torã?ã?°ã?«ã??ã?®ã??ã??ã?ªè¡?ã??ã??ã??ã?°ã??Torã?¯circuitã?®æ??å??ã?®ã??ã?¼ã??ã?¨æ?¥ç¶?ã?§ã??ã?ªã??ã?£ã??ã?¨ã??ã??ã??ã?¨ã?§ã??ã??æ¤?é?²ã??ã??ã??ã??ã??ã??ã?¯ã?¼ã?¯ã?«æ?¥ç¶?ã??ã?¦ã??ã??å?¯è?½æ?§ã??ã??ã??ã?¾ã??ã??ã??ã?ªã??ã?¸ã??ä½¿ã?£ã?¦Torã?«ã?¢ã?¯ã?»ã?¹ã??ã??ã??å??é¡?ã??è§£æ±ºã?§ã??ã??ã?¯ã??ã?§ã??ã??</p><h5>ã??ã??ã??ã??ã?ã?°ã?¨ã?©ã?¼#3: TLSã??ã?³ã??ã?·ã?§ã?¤ã?¯ã?®å¤±æ??</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state
  connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">Torã?ã?°ã?«ã??ã?®ã??ã??ã?ªè¡?ã??ã??ã??ã?°ã??Torã??ã??ã?£ã?¬ã?¯ã??ã?ªã?ªã?¼ã?½ã?ªã??ã?£ã?¨TLSã??ã?³ã??ã?·ã?§ã?¤ã?¯ã??å®?äº?ã?§ã??ã?ªã??ã?£ã??ã?¨ã??ã??ã??ã?¨ã?§ã??ã??ã??ã?ªã??ã?¸ã??ä½¿ã?£ã?¦Torã?«ã?¢ã?¯ã?»ã?¹ã??ã??ã??å??é¡?ã??è§£æ±ºã?§ã??ã??å?¯è?½æ?§ã??ã??ã??ã??</p><h5>ã??ã??ã??ã??ã?ã?°ã?¨ã?©ã?¼#4: ã?¯ã?ã??ã?¯ã?¹ã?ã?¥ã?¼</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p clas
 s=\"mb-3\">Torã?ã?°ã?«ã??ã?®ã??ã??ã?ªè¡?ã??ã??ã??ã?°ã??ã?·ã?¹ã??ã? ã?»ã?¯ã?ã??ã?¯ã?«ã?¯é??é??ã?£ã??æ??å?»ã??è¨å®?ã??ã??ã?¾ã??ã??ã?·ã?¹ã??ã? ã?»ã?¯ã?ã??ã?¯ã??æ£ã??ã??æ??å?»ã?¨ã?¿ã?¤ã? ã?¾ã?¼ã?³ã?«å??ã??ã??ã?¦ã??ã??Torã??å??èµ·å??ã??ã?¦ä¸?ã??ã??ã?? </p>"
+    },
+    "connecting-3": {
+	"id": "#æ?¥ç¶?-3",
+	"control": "æ?¥ç¶?-3",
+	"title": "X.onionã??å??å¾?ã?§ã??ã?¾ã??ã??ï¼?",
+	"description": "ã??ã?ªã??ã??æ??ã??ã?ªã??ã?ªã?³ã?®ã?µã?¼ã??ã?¹ã?«ã?¢ã?¯ã?»ã?¹ã?§ã??ã?ªã??å ´å??ã?¯ã??16æ??å?ã?®ã?ªã??ã?ªã?³ã?¢ã??ã?¬ã?¹ã??æ£ã??ã??å?¥å??ã??ã??ã??ã?¨ã??ç¢ºèª?ã??ã?¦ã??ã? ã??ã??ã??å°?ã??ã?ªé??é??ã??ã?§ã??ã??Torã??ã?©ã?¦ã?¶ã?¼ã??ã?µã?¤ã??ã?«ã?¢ã?¯ã?»ã?¹ã?§ã??ã?ªã??ã?ªã??ã?¾ã??ã??"
+    }
+}
diff --git a/ms_MY.json b/ms_MY.json
new file mode 100644
index 000000000..94afcb73e
--- /dev/null
+++ b/ms_MY.json
@@ -0,0 +1,20 @@
+{
+    "connecting-1": {
+	"id": "#menyambung-1",
+	"control": "menyambung-1",
+	"title": "Pelayar Tor tidak dapat bersambung, tetapi ia bukanlah isu berkenaan penapisan.",
+	"description": "<p class=\"mb-3\">Salah satu masalah utama yang menyebabkan ralat sambungan dalam Pelayar Tor ialah jam sistem yang salah. Sila pastikan jam sistem dan zon waktu anda telah ditetapkan dengan betul. Jika masalah ini masih berlaku, sila rujuk laman Pencarisilapan di dalam <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\";>â??panduan Pelayar Tor</a></mark>.</p>"
+    },
+    "connecting-2": {
+	"id": "#menyambung-2",
+	"control": "menyambung-2",
+	"title": "Saya menghadapi masalah ketika menyambung dengan Tor, dan saya tidak tahu apa masalah yang berlaku.",
+	"description": "<p class=\"mb-3\">Jika anda menghadapi masalah sambungan, pilih pilihan \"salin log Tor ke papan keratan.â?? Kemudian tampal log Tor ke dalam fail teks atau lain-lain fail dokumen. Anda akan dapati terdapat ralat log (lihat baris berikut di dalam log Tor anda):</p><h5>Ralat log umum #1: Kegagalan sambungan proksi</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\"
 )</code></pre></p><p class=\"mb-3\">Jika anda dapat terdapat baris seperti ini di dalam log Tor anda, ia bermaksud anda gagal menyambung dengan proksi SOCKS. Jika proksi SOCKS diperlukan untuk persediaan rangkaian anda, maka sila pastikan anda telah memasukkan perincian proksi tersebut dengan betul.  Jika proksi SOCKS tidak diperlukan, atau anda tidak pasti,  cuba sambung ke rangkaian Tor tanpa proksi SOCKS.<p><h5>Ralat log umum #2: Tidak dapat capai geganti pengawal</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-
 3\">Jika anda dapat terdapat baris seperti ini di dalam log Tor anda, ia bermaksud Tor anda gagal menyambung ke nod pertama dalam litar Tor. Ia bermaksud anda berada dalam rangkaian bertapis. Cuba menyambung dengan titi, dan sepatutnya ia masalah selesai.</p><h5>Ralat log umum #3: Gagal menyelesaikan jabat-tangan TLS</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">Jika anda dapat terdapat ba
 ris seperti ini di dalam log Tor anda, ia bermaksud Tor gagal menyelesaikan jabat-tangan TLS dengan autoriti direktori. Penggunaan titi dapat menyelesaikan masalah ini.</p><h5>Ralat log umum #4: Pencong jam</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">Jika anda dapat terdapat baris seperti ini dalam log Tor anda, ia bermaksud jam sistem anda salah. Sila pastikan jam anda telah ditetapkan dengan tepat, termasuklah zon waktu yang betul.
  Kemudian mulakan semula Tor. </p>"
+    },
+    "connecting-3": {
+	"id": "#menyambung-3",
+	"control": "menyambung-3",
+	"title": "Saya tidak dapat mencapai X.onion!",
+	"description": "<p class=\"mb-3\">Jika anda masih tidak dapat mencapai servis onion yang dikehendaki, pastikan anda telah memasukkan alamat onion 16-aksara dengan betul: walaupun dengan kesilapan kecil akan menghentikan Pelayar Tor mencapai laman. Jika anda masih tidak dapat menyambung ke servis onion, cuba sekali lagi. Kadangkala ia merupakan masalah sambungan sementara, atau operator laman telah menjadi luar talian tanpa apa-apa amaran.</p><p class=\"mb-3\">Anda juga perlu pastikan dapat mencapai servis onion lain dengan menyambung ke Servis Onion <a href=\"http://3g2upl4pq6kufc4m.onion\";>DuckDuckGo</a>.</p>"
+    }
+}
diff --git a/nl.json b/nl.json
new file mode 100644
index 000000000..4fdd4e365
--- /dev/null
+++ b/nl.json
@@ -0,0 +1,20 @@
+{
+    "connecting-1": {
+	"id": "#verbinden-1",
+	"control": "verbinden-1",
+	"title": "Tor Browser maakt geen verbinding, maar het lijkt geen probleem te zijn met censuur.",
+	"description": "<p class=\"mb-3\">Een van de meest voorkomende problemen die verbindingsfouten in Tor Browser veroorzaken, is een onjuiste systeemklok. Zorg ervoor dat uw systeemklok en tijdzone nauwkeurig zijn ingesteld. Als dit het probleem niet oplost, zie de pagina Problemen oplossen op de <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\";> Tor Browser manual</a></mark>.</p>"
+    },
+    "connecting-2": {
+	"id": "#verbinden-2",
+	"control": "verbinden-2",
+	"title": "Ik ondervind problemen bij het verbinding maken met Tor, en ik vind maar niet wat er fout gaat.",
+	"description": "<p class=\"mb-3\">Als u problemen ondervindt bij het verbinden, selecteert u de optie om \"Tor log naar klembord te kopiÃ«ren\". Plak vervolgens het Tor-log in een tekstbestand of een ander document. U zou een van deze Vaak voorkomend logfouten moeten zien (kijk naar de volgende regels in uw Tor-logboek): </p><h5>Vaak voorkomend logboekfout # 1: Proxy-verbindingsfout</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09: 23: 40.800 [LET OP] Opening Socks luisteraar op 127.0.0.1 : 9150 \n 2017-10-29 09: 23: 47.900 [LET OP] Bootstrapped 5%: verbinden met directoryserver \n 2017-10-29 09: 23: 47.900 [LETICE] Bootstrap 10%: handshake beÃ«indigen met directoryserver \n 09-10-09 09: 24: 08.900 [WARN] Proxy-client: kan geen verbinding maken met xx..xxx..xxx.xx: xxxxx (\"algemene SOCKS-serverstoring\") \n 09-10-09 09: 24: 08.900 [WARN] Proxy-client: kan geen verbinding maken met xx..xxx..xxx.xx: xxxxx (\"algemene SOCKS-serverstoring\") \n 09-10-09 09: 24: 08.900 [WARN] Proxy-clie
 nt: kan toxx..xxx..xxx.xx: xxxxx niet verbinden (\"algemene SOCKS-serverstoring\") </code></pre></p><p class=\"mb-3\">Als u dergelijke lijnen in uw Tor-logboek ziet, is dit betekent dat u geen verbinding kunt maken met een SOCKS-proxy. Als een SOCKS-proxy vereist is voor uw netwerkconfiguratie, moet u ervoor zorgen dat u uw proxy-gegevens correct hebt ingevoerd. Als een SOCKS-proxy niet vereist is, of als u het niet zeker weet, probeer dan verbinding te maken met het Tor-netwerk zonder een SOCKS-proxy.<p><h5>Gebruikslog fout # 2: Kan relais niet bereiken</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM .500 [LET OP] Luisteraar luisterpositie openen op 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [LET OP] Bootstrapped 80%: Verbinding maken met het Tor-netwerk \n 11/1/2017 21:11:44 PM.300 [WARN] Kan knooppunt voor hop 0 van ons pad niet vinden. Dit circuit weggooien. \n 11/1/2017 21:11:44 PM.500 [LET OP] Bootstrap 85%: Handshake beÃ«indigen met eerste hop \n 11/1/2017 21:11:45 P
 M.300 [WARN] Kan knooppunt niet vinden voor hop 0 van ons pad. Dit circuit verwijderen.</code></pre></p><p class=\"mb-3\">Als u dergelijke lijnen in uw Tor-logboek ziet, betekent dit dat uw Tor geen verbinding kon maken met het eerste knooppunt in het Tor-circuit. Dit kan betekenen dat u zich op een netwerk bevindt dat gecensureerd is. Probeer te verbinden met bruggen, en dat zou het probleem moeten verhelpen.</p><h5> Algemene logfout # 3: Kan TLS-handshake niet voltooien</h5><p class=\"mb-3\"><pre><code> 13-11-17 19: 52: 24.300 [LET OP] Bootstrap 10%: handshake beÃ«indigen met directoryserver \n 13-11-17 19: 53: 49.300 [WARN] Probleem met bootstrappen. Vastgelopen met 10%: handshake beÃ«indigen met directoryserver. (GEDAAN, GEDAAN, aantal 10; advieswaarschuwing; host [host] op xxx.xxx.xxx.xx: xxx) \n 13-11-17 19: 53: 49.300 [WARN] 10 verbindingen zijn mislukt: \n 13-11-17 19: 53: 49.300 [WARN] 9 verbindingen stierven in staatshandshaking (TLS) met SSL-status SSLv2 / v3 lezen server
  hallo A in HANDSHAKE \n 13-11-17 19: 53: 49.300 [WARN] 1 verbindingen zijn overleden in state connect () ing met SSL-staat (No SSL-object) </code></pre></p><p class=\"mb-3\">Als u dergelijke lijnen in uw Tor-logboek ziet, betekent dat Tor een TLS-handshake niet kon voltooien met de directory-autoriteiten. Het gebruik van bruggen lost dit waarschijnlijk op.</p><h5>Veel logboekfout # 4: Klok skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00: 04: 47.400 [LET OP] Opening Socks luisteraar op 127.0.0.1:9150 \n  19.11.2017 00: 04: 48.000 [LET OP] Bootstrap 5%: verbinding maken met directoryserver \n  19.11.2017 00: 04: 48.200 [LET OP] Bootstrap 10%: handshake beÃ«indigen met directoryserver \n  19.11.2017 00: 04: 48.800 [WARN] NETINFO-cel ontvangen met scheve tijd (OF: xxx.xx.x.xx: xxxx): het lijkt erop dat onze klok 1 dag, 0 uur, 1 minuut achterloopt, of die van hen liggen voor de deur. \n  Tor vereist een nauwkeurige klok om te werken: controleer uw tijd-, tijdzone- en datuminstellin
 gen.</code></pre></p><p class=\"mb-3\">Als u lijnen zoals deze in uw Tor-logboek ziet, betekent dit dat uw systeemklok onjuist is. Zorg ervoor dat uw klok correct is ingesteld, inclusief de juiste tijdzone. Start dan Tor opnieuw. </p>"
+    },
+    "connecting-3": {
+	"id": "#verbinden-3",
+	"control": "verbinden-3",
+	"title": "Ik kan X.onion niet bereiken!",
+	"description": "<p class=\"mb-3\">Als u de gewenste onion service niet kunt bereiken, moet u ervoor zorgen dat u het onion adres van 16 tekens correct hebt ingevoerd: zelfs een kleine fout zal ervoor zorgen dat Tor Browser de site niet kan bereiken. Als u nog steeds geen verbinding kunt maken met de onion service, probeert u het later opnieuw. Er kan een tijdelijke verbinding probleem zijn, of de site exploitanten kunnen hebben toegestaan dat het offline gaan zonder waarschuwing.</p><p class=\"mb-3\"> U kunt er ook voor zorgen dat u in staat om toegang te krijgen tot andere diensten ui door verbinding te maken <a href=\"http://3g2upl4pq6kufc4m.onion\";>DuckDuckGo</a>'s Onion Service.</p>"
+    }
+}
diff --git a/pt_BR.json b/pt_BR.json
new file mode 100644
index 000000000..a1bf886e7
--- /dev/null
+++ b/pt_BR.json
@@ -0,0 +1,20 @@
+{
+    "connecting-1": {
+	"id": "#conectando-1",
+	"control": "conectando-1",
+	"title": "O Navegador Tor nÃ£o se conectarÃ¡, mas nÃ£o parece ser um problema com a censura.",
+	"description": "<p class=\"mb-3\">Um dos problemas mais comuns que causa erros de conexÃ£o no Navegador Tor Ã© um relÃ³gio do sistema incorreto. Por favor, certifique-se de que o relÃ³gio do sistema e o fuso horÃ¡rio estejam definidos com precisÃ£o. Se isso nÃ£o resolver o problema, consulte a pÃ¡gina SoluÃ§Ã£o de Problemas no manual do Navegador Tor</a></mark>.</p>"
+    },
+    "connecting-2": {
+	"id": "#conectando-2",
+	"control": "conectando-2",
+	"title": "Estou tendo problemas para conectar com o Tor e nÃ£o consigo descobrir o que estÃ¡ acontecendo de errado.",
+	"description": "<p class=\"mb-3\">Se estiver tendo problemas ao se conectar, por favor selecione a opÃ§Ã£o para \"copiar o log de Tor para a Ã¡rea de transferÃªncias\". Em seguida cole o log do Tor em um arquivo de texto ou outro documento. VocÃª deverÃ¡ ver um destes erros de logs comuns (procure as seguintes linhas no seu log do Tor):<h5>Erro de log comum #1: Falha na conexÃ£o de Proxy</h5><p class=\"mb-3\"><pre>2017-10-29 09:23:40.800 [OBSERVE] Opening Socks listener on 127.0.0.1:9150\n2017-10-29 09:23:47.900 [OBSERVE] Bootstrapped 5%: Conectando ao servidor do diretÃ³rio\n2017-10-29 09:23:47.900 [OBSERVE] Bootstrapped 10%: Concluindo o 'handshake' com o servidor do diretÃ³rio\n2017-10-29 09:24:08.900 [AVISO] Cliente: de Proxy: nÃ£o foi possÃvel conectar-se Ã   xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")\n2017-10-29 09:24:08.900 [AVISO] Cliente: de Proxy: nÃ£o foi possÃvel conectar-se Ã   xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")\n2017-10-29 09:24:0
 8.900 [AVISO] Cliente: de Proxy: nÃ£o foi possÃvel conectar-se Ã   xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") Se vocÃª encontrar linhas como estas  em seu log do Tor, isto significa que falhou em conectar-se Ã  um SOCKS proxy. Se um SOCKS proxy Ã© obrigatÃ³rio para a sua configuraÃ§Ã£o de rede, por favor certifique-se que vocÃª digitou seus detalhes de proxy corretamente. Se um SOCKS proxy nÃ£o Ã© obrigatÃ³rio, ou vocÃª nÃ£o estÃ¡ certo sobre isso, por favor tente conectar-se Ã  rede Tor sem um SOCKS proxy. Common log error #2: Canâ??t reach guard relays 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150\n11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network\n11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.\n11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop\n11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our
  path. Discarding this circuit.If you see lines like these in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâ??re on a network thatâ??s censored. Please try connecting with bridges, and that should fix the problem.Common log error #3: Failed to complete TLS handshake 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server\n13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx)\n13-11-17 19:53:49.300 [WARN] 10 connections have failed:\n13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE\n13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)If you see lines like this in your Tor log, it means that Tor failed to complete a TLS hand
 shake with the directory authorities. Using bridges will likely fix this.Common log error #4: Clock skew 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150\n19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server\n19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server\n19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead.\nTor requires an accurate clock to work: please check your time, timezone, and date settings.If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. "
+    },
+    "connecting-3": {
+	"id": "#conectando-3",
+	"control": "conectando-3",
+	"title": "NÃ£o consigo conectar ao X.onion!",
+	"description": "<p class=\"mb-3\">Se vocÃª nÃ£o conseguir acessar o serviÃ§o onion desejado, certifique-se de ter digitado  o endereÃ§o onion com 16 caracteres corretamente: atÃ© mesmo um pequeno erro impedirÃ¡ que o Navegador Tor alcance o site. Se vocÃª ainda nÃ£o conseguir se conectar ao serviÃ§o onion, tente novamente mais tarde. Pode haver um problema de conexÃ£o temporÃ¡ria ou os operadores do site podem ter permitido que ele fique offline sem aviso prÃ©vio.</p><p class=\"mb-3\"> VocÃª tambÃ©m pode garantir que poderÃ¡ acessar outros serviÃ§os onion conectando-se ao  <a href=\"http://3g2upl4pq6kufc4m.onion\";>ServiÃ§o Onion</a>do DuckDuckGo.</p>"
+    }
+}
diff --git a/ro.json b/ro.json
new file mode 100644
index 000000000..2fe13067e
--- /dev/null
+++ b/ro.json
@@ -0,0 +1,20 @@
+{
+    "connecting-1": {
+	"id": "#connecting-1",
+	"control": "conectare-1",
+	"title": "Tor Browser nu se conecteazÄ?, dar nu pare a fi o problemÄ? de cenzurÄ?.",
+	"description": "<p class=\"mb-3\">Una din cele mai frecvente cauze pentru problemele de conectare ale Tor Browser este ora sistemului incorectÄ?. VerificÄ? dacÄ? ora È?i fusul orar sunt setate corect. DacÄ? aceasta nu rezolvÄ? problema, urmeazÄ? indicaÈ?iile de Depanare din <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\";>â??manualul Tor Browser</a></mark>.</p>"
+    },
+    "connecting-2": {
+	"id": "#connecting-2",
+	"control": "conectare-2",
+	"title": "Am dificultÄ?È?i Ã®n conectarea la Tor È?i nu Ã®nÈ?eleg ce e greÈ?it.",
+	"description": "<p class=\"mb-3\">DacÄ? ai probleme de conectare, selecteazÄ? opÈ?iunea \"copiazÄ? log-ul Tor Ã®n clipboard\". Apoi lipeÈ?te log-ul astfel copiat Ã®ntr-un fiÈ?ier text sau alt document. Ar trebui sÄ? vezi unul dintre aceste mesaje de eroare comune (cautÄ? astfel de linii Ã®n log-ul Tor):</p><h5>Eroare comunÄ? #1: Eroare de conectare la proxy</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"g
 eneral SOCKS server failure\")</code></pre></p><p class=\"mb-3\">DacÄ? vezi astfel de linii in log-ul Tor, Ã®nseamnÄ? cÄ? nu te poÈ?i conecta la un proxy SOCKS. DacÄ? un proxy SOCKS este necesar pentru reÈ?eaua pe care o foloseÈ?ti, atunci asigurÄ?-te cÄ? ai introdus setÄ?rile de proxy corecte. DacÄ? un proxy SOCKS nu e necesar sau nu eÈ?ti sigur, Ã®ncearcÄ? sÄ? te conectezi la reÈ?eaua Tor fÄ?rÄ? un proxy SOCKS.<p><h5>Eroare comunÄ? #2: Canâ??t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\"
 >DacÄ? vezi astfel de linii in log-ul Tor Ã®nseamnÄ? ca nu s-a reuÈ?it conectarea la primul nod din circuitul Tor. Aceasta ar putea Ã®nsemna cÄ? te afli Ã®ntr-o reÈ?ea cenzuratÄ?. Ã?ncearcÄ? conectarea prin punÈ?i, care ar trebui sÄ? rezolve problema.</p><h5>Eroare comunÄ? #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">DacÄ? vezi astfel de linii in log-u
 l Tor Ã®nseamnÄ? cÄ? nu s-a realizat o conexiune completÄ? TLS cu serverele de directoare. Folosirea punÈ?ilor va rezolva probabil acest lucru. </p><h5>Eroare comunÄ? #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">DacÄ? vezi astfel de linii in log-ul Tor Ã®nseamnÄ? cÄ? ceasul sistemului tÄ?u e incorect. AsigurÄ?-te cÄ? ceasul sistemului este corect, inclusiv fusul orar, apoi reporneÈ?te Tor. </p>"
+    },
+    "connecting-3": {
+	"id": "#connecting-3",
+	"control": "conectare-3",
+	"title": "Nu pot ajunge la X.onion!",
+	"description": "<p class=\"mb-3\">DacÄ? nu poÈ?i ajunge la serviciul onion dorit, asigurÄ?-te cÄ? ai introdus cele 16 caractere din adresa onion corect - chiar È?i cea mai micÄ? eroare va Ã®mpiedica Tor Browser sÄ? ajungÄ? la site. DacÄ? tot nu poÈ?i ajunge la serviciul onion, Ã®ncearcÄ? mai tÃ¢rziu. E posibil sÄ? fie o problemÄ? temporarÄ? de conexiune sau operatorii site-ului l-au deconectat fÄ?rÄ? avertizare. </p><p class=\"mb-3\">PoÈ?i sÄ? te asiguri cÄ? alte servicii onion sunt accesibile conectÃ¢ndu-te la serviciul onion al <a href=\"http://3g2upl4pq6kufc4m.onion\";>DuckDuckGo</a>.</p>"
+    }
+}
diff --git a/support-connecting.json b/support-connecting.json
new file mode 100644
index 000000000..cac143183
--- /dev/null
+++ b/support-connecting.json
@@ -0,0 +1,20 @@
+{
+    "connecting-1": {
+	"id": "#connecting-1",
+	"control": "connecting-1",
+	"title": "Tor Browser won't connect, but it doesnâ??t seem to be an issue with censorship.",
+	"description": "<p class=\"mb-3\">One of the most common issues that causes connection errors in Tor Browser is an incorrect system clock. Please make sure your system clock and timezone are set accurately. If this doesn't fix the problem, see the â??Troubleshooting page on the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\";>â??Tor Browser manual</a></mark>.</p>"
+    },
+    "connecting-2": {
+	"id": "#connecting-2",
+	"control": "connecting-2",
+	"title": "I am having trouble connecting to Tor, and I canâ??t figure out whatâ??s wrong.",
+	"description": "<p class=\"mb-3\">If youâ??re having trouble connecting, please select the option to â??copy Tor log to clipboard.â?? Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server 
 failure\")</code></pre></p><p class=\"mb-3\">If you see lines like these  in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâ??ve entered your proxy details correctly.  If a SOCKS proxy is not required, or youâ??re not sure,  please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canâ??t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like the
 se in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâ??re on a network thatâ??s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that To
 r failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>"
+    },
+    "connecting-3": {
+	"id": "#connecting-3",
+	"control": "connecting-3",
+	"title": "I cannot reach X.onion!",
+	"description": "<p class=\"mb-3\">If you cannot reach the onion service you desire, make sure that you have entered the 16-character onion address correctly: even a small mistake will stop Tor Browser from being able to reach the site. If you are still unable to connect to the onion service, please try again later. There may be a temporary connection issue, or the site operators may have allowed it to go offline without warning.</p><p class=\"mb-3\">You can also ensure that you're able to access other onion services by connecting to <a href=\"http://3g2upl4pq6kufc4m.onion\";>DuckDuckGo</a>'s â??Onion Service.</p>"
+    }
+}
diff --git a/uk.json b/uk.json
new file mode 100644
index 000000000..32a35f4fc
--- /dev/null
+++ b/uk.json
@@ -0,0 +1,20 @@
+{
+    "connecting-1": {
+	"id": "#Ð·'Ñ?Ð´Ð½Ð°Ð½Ð½Ñ?-1",
+	"control": "Ð·'Ñ?Ð´Ð½Ð°Ð½Ð½Ñ?-1",
+	"title": "Ð?Ñ?Ð°Ñ?Ð·ÐµÑ? Tor Ð½Ðµ Ð±Ñ?Ð´Ðµ Ð¿Ñ?Ð´'Ñ?Ð´Ð½Ñ?Ð²Ð°Ñ?Ð¸Ñ?Ñ?, Ð°Ð»Ðµ Ñ?Ðµ, Ð·Ð´Ð°Ñ?Ñ?Ñ?Ñ?Ñ?, Ð½Ðµ Ñ? Ð¿Ñ?Ð¾Ð±Ð»ÐµÐ¼Ð¾Ñ? Ð· Ñ?ÐµÐ½Ð·Ñ?Ñ?Ð¾Ñ?.",
+	"description": "<p class=\"mb-3\">Ð?Ð´Ð½Ñ?Ñ?Ñ? Ð· Ð½Ð°Ð¹Ð±Ñ?Ð»Ñ?Ñ? Ð¿Ð¾Ñ?Ð¸Ñ?ÐµÐ½Ð¸Ñ? Ð¿Ñ?Ð¾Ð±Ð»ÐµÐ¼, Ñ?Ð¾ Ð¿Ñ?Ð¸Ð·Ð²Ð¾Ð´Ñ?Ñ?Ñ? Ð´Ð¾ Ð¿Ð¾Ð¼Ð¸Ð»Ð¾Ðº Ð·'Ñ?Ð´Ð½Ð°Ð½Ð½Ñ? Ñ? Ð±Ñ?Ð°Ñ?Ð·ÐµÑ?Ñ? Tor, Ñ? Ð½ÐµÐ¿Ñ?Ð°Ð²Ð¸Ð»Ñ?Ð½Ð¸Ð¹ Ñ?Ð¸Ñ?Ñ?ÐµÐ¼Ð½Ð¸Ð¹ Ð³Ð¾Ð´Ð¸Ð½Ð½Ð¸Ðº. Ð?ÐµÑ?ÐµÐºÐ¾Ð½Ð°Ð¹Ñ?ÐµÑ?Ñ?, Ñ?Ð¾ Ð²Ð°Ñ?Ñ? Ñ?Ð¸Ñ?Ñ?ÐµÐ¼Ð½Ð¸Ð¹ Ð³Ð¾Ð´Ð¸Ð½Ð½Ð¸Ðº Ñ?Ð° Ñ?Ð°Ñ?Ð¾Ð²Ð¸Ð¹ Ð¿Ð¾Ñ?Ñ? Ð²Ñ?Ñ?Ð°Ð½Ð¾Ð²Ð»ÐµÐ½Ñ? Ñ?Ð¾Ñ?Ð½Ð¾. Ð¯ÐºÑ?Ð¾ Ñ?Ðµ Ð½Ðµ Ð²Ð¸Ñ?Ñ?Ñ?Ð¸Ñ?Ñ? Ð¿Ñ?Ð¾Ð±Ð»ÐµÐ¼Ñ?, Ð¿ÐµÑ?ÐµÐ³Ð»Ñ?Ð½Ñ?Ñ?Ðµ Ñ?Ñ?Ð¾Ñ?Ñ?Ð½ÐºÑ? Ñ?Ñ?Ñ?Ð½ÐµÐ½Ð½Ñ? Ð½ÐµÐ¿Ð¾Ð»Ð°Ð´Ð¾Ðº Ñ? <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\";>Ð¿Ð¾Ñ?Ñ?Ð±Ð½Ð¸ÐºÑ? ÐºÐ¾Ñ?Ð¸Ñ?Ñ?Ñ?Ð²Ð°Ñ?Ð° Ð±Ñ?Ð°Ñ?Ð·ÐµÑ?Ð° Tor</a></mark>.</p>"
+    },
+    "connecting-2": {
+	"id": "#Ð·'Ñ?Ð´Ð½Ð°Ð½Ð½Ñ?-2",
+	"control": "Ð·'Ñ?Ð´Ð½Ð°Ð½Ð½Ñ?-2",
+	"title": "Ð£ Ð¼ÐµÐ½Ðµ Ð²Ð¸Ð½Ð¸ÐºÐ»Ð° Ð¿Ñ?Ð¾Ð±Ð»ÐµÐ¼Ð° Ð· Ð¿Ñ?Ð´'Ñ?Ð´Ð½Ð°Ð½Ð½Ñ?Ð¼ Ð´Ð¾ Tor, Ñ? Ñ? Ð½Ðµ Ð¼Ð¾Ð¶Ñ? Ð·Ñ?Ð¾Ð·Ñ?Ð¼Ñ?Ñ?Ð¸, Ñ?Ð¾ Ð½Ðµ Ñ?Ð°Ðº.",
+	"description": "<p class=\"mb-3\">Ð¯ÐºÑ?Ð¾ Ñ? Ð²Ð°Ñ? Ð²Ð¸Ð½Ð¸ÐºÐ»Ð¸ Ð¿Ñ?Ð¾Ð±Ð»ÐµÐ¼Ð¸ Ð· Ð¿Ñ?Ð´'Ñ?Ð´Ð½Ð°Ð½Ð½Ñ?Ð¼, Ð²Ð¸Ð±ÐµÑ?Ñ?Ñ?Ñ? Ð¾Ð¿Ñ?Ñ?Ñ? Â«ÐºÐ¾Ð¿Ñ?Ñ?Ð²Ð°Ñ?Ð¸ Ð¶Ñ?Ñ?Ð½Ð°Ð» Tor Ñ? Ð±Ñ?Ñ?ÐµÑ? Ð¾Ð±Ð¼Ñ?Ð½Ñ?Â». Ð?Ð¾Ñ?Ñ?Ð¼ Ð²Ñ?Ñ?Ð°Ð²Ñ?Ðµ Ð¶Ñ?Ñ?Ð½Ð°Ð» Tor Ñ? Ñ?ÐµÐºÑ?Ñ?Ð¾Ð²Ð¸Ð¹ Ñ?Ð°Ð¹Ð» Ð°Ð±Ð¾ Ñ?Ð½Ñ?Ð¸Ð¹ Ð´Ð¾ÐºÑ?Ð¼ÐµÐ½Ñ?. Ð?Ð¸ Ð¼Ð°Ñ?Ñ?Ðµ Ð¿Ð¾Ð±Ð°Ñ?Ð¸Ñ?Ð¸ Ð¾Ð´Ð½Ñ? Ð· Ñ?Ð¸Ñ? Ð¿Ð¾Ð¼Ð¸Ð»Ð¾Ðº Ð·Ð°Ð³Ð°Ð»Ñ?Ð½Ð¾Ð³Ð¾ Ð¶Ñ?Ñ?Ð½Ð°Ð»Ñ? (Ñ?Ñ?ÐºÐ°Ð¹Ñ?Ðµ Ð½Ð°Ñ?Ñ?Ñ?Ð¿Ð½Ñ? Ñ?Ñ?Ð´ÐºÐ¸ Ð² Ð¶Ñ?Ñ?Ð½Ð°Ð»Ñ? Tor):</p><h5>Ð?Ð¾Ð¼Ð¸Ð»ÐºÐ° Ð·Ð°Ð³Ð°Ð»Ñ?Ð½Ð¾Ð³Ð¾ Ð¶Ñ?Ñ?Ð½Ð°Ð»Ñ? â??1: Ð?Ð¾Ð¼Ð¸Ð»ÐºÐ° Ð·'Ñ?Ð´Ð½Ð°Ð½Ð½Ñ? Ð· Ð¿Ñ?Ð¾ÐºÑ?Ñ?-Ñ?ÐµÑ?Ð²ÐµÑ?Ð¾Ð¼</h5><p class=\"mb-3\"><pre><code>2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150\n2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server\n2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server\n2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"g
 eneral SOCKS server failure\")\n2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")\n2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")</code></pre></p> <p class=\"mb-3\">Ð¯ÐºÑ?Ð¾ Ð²Ð¸ Ð±Ð°Ñ?Ð¸Ñ?Ðµ Ñ?Ð°ÐºÑ? Ñ?Ñ?Ð´ÐºÐ¸ Ð² Ð¶Ñ?Ñ?Ð½Ð°Ð»Ñ? Tor, Ñ?Ðµ Ð¾Ð·Ð½Ð°Ñ?Ð°Ñ?, Ñ?Ð¾ Ð²Ð¸ Ð½Ðµ Ð¼Ð¾Ð¶ÐµÑ?Ðµ Ð¿Ñ?Ð´'Ñ?Ð´Ð½Ð°Ñ?Ð¸Ñ?Ñ? Ð´Ð¾ Ð¿Ñ?Ð¾ÐºÑ?Ñ? SOCKS. Ð¯ÐºÑ?Ð¾ Ð´Ð»Ñ? Ð½Ð°Ð»Ð°Ñ?Ñ?Ñ?Ð²Ð°Ð½Ð½Ñ? Ð¼ÐµÑ?ÐµÐ¶Ñ? Ð¿Ð¾Ñ?Ñ?Ñ?Ð±ÐµÐ½ Ð¿Ñ?Ð¾ÐºÑ?Ñ?-Ñ?ÐµÑ?Ð²ÐµÑ? SOCKS, Ð±Ñ?Ð´Ñ? Ð»Ð°Ñ?ÐºÐ°, Ð¿ÐµÑ?ÐµÐºÐ¾Ð½Ð°Ð¹Ñ?ÐµÑ?Ñ?, Ñ?Ð¾ Ð²Ð¸ Ð¿Ñ?Ð°Ð²Ð¸Ð»Ñ?Ð½Ð¾ Ð²Ð²ÐµÐ»Ð¸ Ñ?Ð½Ñ?Ð¾Ñ?Ð¼Ð°Ñ?Ñ?Ñ? Ð¿Ñ?Ð¾ Ð¿Ñ?Ð¾ÐºÑ?Ñ?. Ð¯ÐºÑ?Ð¾ Ð¿Ñ?Ð¾ÐºÑ?Ñ? SOCKS Ð½Ðµ Ð¿Ð¾Ñ?Ñ?Ñ?Ð±Ð½Ð¸Ð¹, Ð°Ð±Ð¾ Ð²Ð¸ Ð½Ðµ Ð²Ð¿ÐµÐ²Ð½ÐµÐ½Ñ?, Ñ?Ð¿Ñ?Ð¾Ð±Ñ?Ð¹Ñ?Ðµ Ð¿Ñ?Ð´'Ñ?Ð´Ð½Ð°Ñ?Ð¸Ñ?Ñ? Ð´Ð¾ Ð¼ÐµÑ?ÐµÐ¶Ñ? Tor Ð±ÐµÐ· Ð¿Ñ?Ð¾ÐºÑ?Ñ?-Ñ?ÐµÑ?Ð²ÐµÑ?Ð° SOCKS.<p><h5>Ð?Ð¾Ð¼Ð¸Ð»ÐºÐ° Ð·Ð°Ð³Ð°Ð»Ñ?Ð½Ð¾Ð³Ð¾ Ð¶Ñ?Ñ?Ð½Ð°Ð»Ñ? â??2: Ð?Ðµ Ð²Ð´Ð°Ñ?Ñ?Ñ?Ñ?Ñ? Ð
 ´Ñ?Ñ?Ñ?Ð°Ñ?Ð¸Ñ?Ñ? Ð±ÐµÐ·Ð¿ÐµÑ?Ð½Ð¸Ñ? Ð¿ÐµÑ?ÐµÐ´Ð°Ð²Ð°Ñ?Ñ?Ð²</h5><p class=\"mb-3\"><pre><code>11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150\n11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network\n11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.\n11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop\n11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">Ð¯ÐºÑ?Ð¾ Ñ? Ð¶Ñ?Ñ?Ð½Ð°Ð»Ñ? Tor Ð²Ð¸ Ð±Ð°Ñ?Ð¸Ñ?Ðµ Ñ?Ð°ÐºÑ? Ñ?Ñ?Ð´ÐºÐ¸, Ñ?Ð¾ Ñ?Ðµ Ð¾Ð·Ð½Ð°Ñ?Ð°Ñ?, Ñ?Ð¾ Ð²Ð°Ñ?Ð¾Ð¼Ñ? Tor Ð½Ðµ Ð²Ð´Ð°Ð»Ð¾Ñ?Ñ? Ð¿Ñ?Ð´'Ñ?Ð´Ð½Ð°Ñ?Ð¸Ñ?Ñ? Ð´Ð¾ Ð¿ÐµÑ?Ñ?Ð¾Ð³Ð¾ Ð²Ñ?Ð·Ð»Ð° Ð² Ð»Ð°Ð½Ñ?Ñ?Ð·Ñ? Tor. Ð¦Ðµ Ð¼Ð¾Ð¶Ðµ Ð¾Ð·Ð½Ð°Ñ?Ð°Ñ?Ð¸, Ñ?Ð¾ Ð²Ð¸ Ð¿ÐµÑ?ÐµÐ±Ñ?Ð²Ð°Ñ?Ñ?Ðµ Ñ? Ð¼ÐµÑ?ÐµÐ¶Ñ?, Ñ?ÐºÐ° Ð¿Ñ?Ð´Ð´Ð°Ñ?Ñ?Ñ?Ñ?Ñ? Ñ?ÐµÐ½Ð·Ñ?Ñ?Ñ?. Ð?Ñ?Ð´Ñ? Ð»Ð°Ñ?ÐºÐ°, Ñ?Ð¿Ñ?Ð¾Ð±Ñ?Ð¹Ñ?Ðµ Ð¿Ñ?Ð´ÐºÐ»Ñ?Ñ?Ð¸Ñ?Ð¸Ñ?Ñ? Ð´Ð¾ Ð¼Ð¾Ñ
 ?Ñ?Ñ?Ð², Ñ? Ñ?Ðµ Ð¼Ð°Ñ? Ð²Ð¸Ñ?Ñ?Ñ?Ð¸Ñ?Ð¸ Ð¿Ñ?Ð¾Ð±Ð»ÐµÐ¼Ñ?.</p><h5>Ð?Ð¾Ð¼Ð¸Ð»ÐºÐ° Ð·Ð°Ð³Ð°Ð»Ñ?Ð½Ð¾Ð³Ð¾ Ð¶Ñ?Ñ?Ð½Ð°Ð»Ñ? â??3: Ð½Ðµ Ð²Ð´Ð°Ð»Ð¾Ñ?Ñ? Ð·Ð°Ð²ÐµÑ?Ñ?Ð¸Ñ?Ð¸ Ñ?Ñ?ÐºÐ¾Ñ?Ñ?Ð¸Ñ?ÐºÐ°Ð½Ð½Ñ? TLS</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server\n13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx)\n13-11-17 19:53:49.300 [WARN] 10 connections have failed:\n13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE\n13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">Ð¯ÐºÑ?Ð¾ Ð²Ð¸ Ð±Ð°Ñ?Ð¸Ñ?Ðµ Ñ?Ð°ÐºÑ? Ñ?Ñ?Ð´ÐºÐ¸ Ð² Ð¶Ñ?Ñ?Ð½Ð°Ð»Ñ? Tor, Ñ?Ðµ Ð¾Ð·Ð½Ð°Ñ?Ð°Ñ?, Ñ?Ð¾ Tor Ð½Ðµ Ð²Ð´Ð°Ð»Ð¾Ñ?Ñ? Ð²Ð¸ÐºÐ¾Ð½Ð°Ñ?Ð¸ Ñ?Ñ?ÐºÐ¾Ñ?Ñ?Ð¸Ñ?ÐºÐ°Ð½Ð½Ñ?
  TLS Ð·Ð° Ð´Ð¾Ð¿Ð¾Ð¼Ð¾Ð³Ð¾Ñ? Ñ?Ð»Ñ?Ð¶Ð± ÐºÐ°Ñ?Ð°Ð»Ð¾Ð³Ñ?. Ð?Ð¸ÐºÐ¾Ñ?Ð¸Ñ?Ñ?Ð°Ð½Ð½Ñ? Ð¼Ð¾Ñ?Ñ?Ñ?Ð², Ñ?Ð²Ð¸Ð´Ñ?Ðµ Ð·Ð° Ð²Ñ?Ðµ, Ð±Ñ?Ð´Ðµ Ð²Ð¸Ð¿Ñ?Ð°Ð²Ð»Ñ?Ñ?Ð¸ Ñ?Ðµ.</p><h5> Ð?Ð¾Ð¼Ð¸Ð»ÐºÐ° Ð·Ð°Ð³Ð°Ð»Ñ?Ð½Ð¾Ð³Ð¾ Ð¶Ñ?Ñ?Ð½Ð°Ð»Ñ? â??4: Ð·Ð±Ð¸Ñ?Ð¸Ð¹ Ð³Ð¾Ð´Ð¸Ð½Ð½Ð¸Ðº</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150\n19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server\n19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server\n19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead.\nTor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">Ð¯ÐºÑ?Ð¾ Ð²Ð¸ Ð±Ð°Ñ?Ð¸Ñ?Ðµ Ñ?Ð°ÐºÑ? Ñ?Ñ?Ð´ÐºÐ¸ Ð² Ð¶Ñ?Ñ?Ð½Ð°Ð»Ñ? Tor, Ñ?Ðµ Ð¾Ð·Ð½Ð°Ñ?Ð°Ñ?, Ñ?Ð¾ Ð²Ð°Ñ? Ñ?Ð¸Ñ?Ñ?ÐµÐ¼Ð½Ð¸Ð¹ Ð³Ð¾Ð´Ð¸Ð½Ð½Ð¸Ðº Ð½ÐµÐ¿Ñ?
 Ð°Ð²Ð¸Ð»Ñ?Ð½Ð¸Ð¹. Ð?Ñ?Ð´Ñ?-Ð»Ð°Ñ?ÐºÐ°, Ð¿ÐµÑ?ÐµÐºÐ¾Ð½Ð°Ð¹Ñ?ÐµÑ?Ñ?, Ñ?Ð¾ Ð²Ð°Ñ?Ð¸Ð¹ Ð³Ð¾Ð´Ð¸Ð½Ð½Ð¸Ðº Ð²Ñ?Ñ?Ð°Ð½Ð¾Ð²Ð»ÐµÐ½Ð¸Ð¹ Ñ?Ð¾Ñ?Ð½Ð¾, Ð²ÐºÐ»Ñ?Ñ?Ð½Ð¾ Ð· Ð¿Ñ?Ð°Ð²Ð¸Ð»Ñ?Ð½Ð¸Ð¼ Ñ?Ð°Ñ?Ð¾Ð²Ð¸Ð¼ Ð¿Ð¾Ñ?Ñ?Ð¾Ð¼. Ð?Ð¾Ñ?Ñ?Ð¼ Ð¿ÐµÑ?ÐµÐ·Ð°Ð¿Ñ?Ñ?Ñ?Ñ?Ñ?Ñ? Tor.</p>"
+    },
+    "connecting-3": {
+	"id": "#Ð·'Ñ?Ð´Ð½Ð°Ð½Ð½Ñ?-3",
+	"control": "Ð·'Ñ?Ð´Ð½Ð°Ð½Ð½Ñ?-3",
+	"title": "Ð¯ Ð½Ðµ Ð¼Ð¾Ð¶Ñ? Ð·Ð½Ð°Ð¹Ñ?Ð¸ X.onion!",
+	"description": "<p class=\"mb-3\">Ð¯ÐºÑ?Ð¾ Ð²Ð¸ Ð½Ðµ Ð¼Ð¾Ð¶ÐµÑ?Ðµ Ð·Ð½Ð°Ð¹Ñ?Ð¸ Ñ?Ð»Ñ?Ð¶Ð±Ñ? onion, Ñ?ÐºÑ? Ð²Ð¸ Ð±Ð°Ð¶Ð°Ñ?Ñ?Ðµ, Ð¿ÐµÑ?ÐµÐºÐ¾Ð½Ð°Ð¹Ñ?ÐµÑ?Ñ?, Ñ?Ð¾ Ð²Ð¸ Ð¿Ñ?Ð°Ð²Ð¸Ð»Ñ?Ð½Ð¾ Ð²Ð²ÐµÐ»Ð¸ 16-Ñ?Ð¸Ð¼Ð²Ð¾Ð»Ñ?Ð½Ñ? onion-Ð°Ð´Ñ?ÐµÑ?Ñ?: Ð½Ð°Ð²Ñ?Ñ?Ñ? Ð½ÐµÐ²ÐµÐ»Ð¸ÐºÐ° Ð¿Ð¾Ð¼Ð¸Ð»ÐºÐ° Ð½Ðµ Ð´Ð¾Ð·Ð²Ð¾Ð»Ð¸Ñ?Ñ? Tor Browser Ð·Ð°Ð¹Ñ?Ð¸ Ð½Ð° Ñ?Ð°Ð¹Ñ?. Ð¯ÐºÑ?Ð¾ Ð²Ð¸ Ð²Ñ?Ðµ Ð¶ Ð½Ðµ Ð¼Ð¾Ð¶ÐµÑ?Ðµ Ð¿Ñ?Ð´'Ñ?Ð´Ð½Ð°Ñ?Ð¸Ñ?Ñ? Ð´Ð¾ Ñ?Ð»Ñ?Ð¶Ð± onion, Ñ?Ð¿Ñ?Ð¾Ð±Ñ?Ð¹Ñ?Ðµ Ð¿Ñ?Ð·Ð½Ñ?Ñ?Ðµ. Ð?Ð¾Ð¶Ðµ Ñ?Ñ?Ð°Ð¿Ð¸Ñ?Ð¸Ñ?Ñ? Ð¿Ñ?Ð¾Ð±Ð»ÐµÐ¼Ð° Ñ?Ð¸Ð¼Ñ?Ð°Ñ?Ð¾Ð²Ð¾Ð³Ð¾ Ð¿Ñ?Ð´'Ñ?Ð´Ð½Ð°Ð½Ð½Ñ?, Ð°Ð±Ð¾ Ð¾Ð¿ÐµÑ?Ð°Ñ?Ð¾Ñ?Ð¸ Ñ?Ð°Ð¹Ñ?Ñ? Ð¼Ð¾Ð¶Ñ?Ñ?Ñ? Ð´Ð¾Ð·Ð²Ð¾Ð»Ð¸Ñ?Ð¸ Ð¹Ð¾Ð¼Ñ? Ð²Ð¸Ñ?Ð¾Ð´Ð¸Ñ?Ð¸ Ð² Ð°Ð²Ñ?Ð¾Ð½Ð¾Ð¼Ð½Ð¸Ð¹ Ñ?ÐµÐ¶Ð¸Ð¼ Ð±ÐµÐ· Ð¿Ð¾Ð¿ÐµÑ?ÐµÐ´Ð¶ÐµÐ½Ð½Ñ?.</p><p class=\"mb-3\">Ð?Ð¸ Ñ?Ð°ÐºÐ¾Ð¶ Ð¼Ð¾Ð¶ÐµÑ?Ðµ Ð¿ÐµÑ?ÐµÐºÐ¾Ð½Ð°Ñ?Ð¸Ñ?Ñ?, Ñ?Ð¾ Ð²Ð¸ Ð¼Ð¾Ð¶ÐµÑ?Ðµ Ð¾Ñ?Ñ?Ð¸Ð¼Ð°Ñ?Ð¸ Ð´Ð¾Ñ?Ñ?Ñ?Ð¿ Ð´Ð¾ Ñ?Ð½Ñ?Ð¸Ñ? Ð¿Ð¾Ñ?Ð»Ñ?Ð³ onion, Ð¿Ñ?Ð´'Ñ?Ð´Ð½Ð°Ð²Ñ?Ð¸Ñ?Ñ? Ð´Ð¾ Ñ?Ð»Ñ?Ð¶Ð±Ð¸ Onion Ð½Ð° <a href=\"http://3g2upl4pq6kufc4m.onion\";>DuckDuckGo</
 a>.</p>"
+    }
+}
diff --git a/zh_CN.json b/zh_CN.json
new file mode 100644
index 000000000..d2f692083
--- /dev/null
+++ b/zh_CN.json
@@ -0,0 +1,20 @@
+{
+    "connecting-1": {
+	"id": "#è¿?æ?¥-1",
+	"control": "è¿?æ?¥-1",
+	"title": "Toræµ?è§?å?¨æ²¡æ??è¿?æ?¥ä¸?äº?è??ç½?ï¼?ä½?è¿?ä¼¼ä¹?å¹¶ä¸?æ?¯å? ä¸ºç½?ç»?ç®¡æ?§é? æ??ç??é?®é¢?ã??",
+	"description": "<p class=\"mb-3\">é? æ??Torè¿?æ?¥å¤±è´¥ç??æ??å¸¸è§?ç??é?®é¢?ä¹?ä¸?æ?¯ç³»ç»?æ?¶é?´è®¾ç½®é??è¯¯ã??è¯·ç¡®è®¤æ?¨ç??ç³»ç»?æ?¶é?´ä»¥å??æ?¶å?ºè®¾ç½®æ£ç¡®ã??å¦?æ??è¿?ä¸ªé?®é¢?è¿?æ²¡æ??è¢«è§£å?³ï¼?è¯·æ?¥ç??ä½?äº?<mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\";>Toræµ?è§?å?¨æ??å??</a></mark>ç??æ??é??æ??æ?¥ç??é?¢ã??</p>"
+    },
+    "connecting-2": {
+	"id": "#è¿?æ?¥-2",
+	"control": "è¿?æ?¥-2",
+	"title": "æ? æ³?è¿?æ?¥å?° Torï¼?æ??ä¸?ç?¥é??å??ç??äº?ä»?ä¹?ä»?ä¹?é??è¯¯ã??",
+	"description": "<p class=\"mb-3\">å¦?æ??æ?¨ç??è¿?æ?¥å?ºç?°é?®é¢?ï¼?è¯·é??æ?©â??å¤?å?¶Toræ?¥å¿?å?°å?ªè´´æ?¿â??é??é¡¹ã??ç?¶å??ç²?è´´Toræ?¥å¿?å?°æ??æ?¬æ??ä»¶æ??è??å?¶ä»?æ??æ¡£æ ¼å¼?ã??æ?¨åº?è¯¥è?½å¤?å?¨ç²?è´´ç??Toræ?¥å¿?ä¸å??ç?°è¿?äº?å¸¸è§?é?®é¢?ï¼?è¯·å?¨Toræ?¥å¿?é??å¯»æ?¾å¦?ä¸?æ??ç¤ºç??é??è¯¯ï¼?:</p><h5> å¸¸è§?é??è¯¯#1: ä»£ç??è¿?æ?¥å¤±è´¥ </h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx  (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx  (\"general SOCKS server
  failure\")</code></pre></p><p class=\"mb-3\"> å¦?æ??æ?¨ç??è§?è¿?äº?æ??ç¤ºå?ºç?°å?¨æ?¨ç??æ?¥å¿?é??é?¢ï¼?è¿?æ??å?³ç??æ?¨è¿?æ?¥SOCKSä»£ç??å¤±è´¥äº?ã??å¦?æ??æ?¨ç??ç³»ç»?è®¾ç½®é??è¦?ä¸?ä¸ªSOCKSä»£ç??, è¯·ä¿?è¯?æ?¨æ£ç¡®ç??è¾?å?¥äº?å?³äº?è¿?ä¸ªä»£ç??ç??é??ç½®ã?? å¦?æ??æ?¨ç??ç³»ç»?ä¸?é??è¦?ä»£ç??ï¼?æ??è??æ?¨ä¸?æ?¢è?¯å®?ï¼?è¯·å°?è¯?ç?´æ?¥è¿?æ?¥Torç½?ç»?ã??<p><h5>å¸¸è§?é??è¯¯ #2: æ? æ³?è¿?æ?¥å?°ä¸ç»§</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\"> å¦?æ??æ?¨ç??è§?è¿?äº?æ??ç¤ºå?ºç?°å?¨æ?¨ç??æ?¥å¿?é??é?¢ï¼?è¿?æ??å?³ç??æ
 ?¨ç??Torè¿?æ?¥ Torç½?ç»?ä¸ç??ç¬¬ä¸?ä¸ªè??ç?¹å¤±è´¥äº?ã??è¿?å?¯è?½æ??å?³ç??æ?¨å¤?äº?è¢«ç??ç®¡ç??ç½?ç»?ä¹?ä¸ã??è¯·å°?è¯?é??è¿?ç½?æ¡¥è¿?æ?¥ï¼?è¿?åº?è¯¥è?½è§£å?³æ?¨ç??é?®é¢?ã??</p><h5>å¸¸è§?é??è¯¯#3: TLSæ?¡æ??å¤±è´¥ </h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN]  9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">å¦?æ??æ?¨ç??è§?è¿?äº?æ??ç¤ºå?ºç?°å?¨æ?¨ç??æ?¥å¿?é??é?¢ï¼?è¿?æ??å?³ç??Tor ä¸?ä¸ç»§ç?®å½?æ??ä¾?æ??å?¡å?¨ç??TLSæ?¡æ??å¤±è´¥äº?ã?? ä½¿
 ç?¨ç½?æ¡¥åº?è¯¥è?½è§£å?³è¿?ä¸ªé?®é¢?</p><h5>å¸¸è§?é??è¯¯#4: æ?¶é?´è®¾ç½®é??è¯¯ <pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Toré??è¦?ä¸?ä¸ªå??ç¡®ç??æ?¶é?´æ?¥ç»´æ??å®?ç??è¿?ä½?ã??</code></pre></p><p class=\"mb-3\">è¯·æ£?æ?¥æ?¨ç??æ?¶é?´ï¼?æ?¶å?ºä»¥å??æ?¥æ??è®¾ç½®ã??å¦?æ??æ?¨ç??è§?è¿?äº?æ??ç¤ºå?ºç?°å?¨æ?¨ç??æ?¥å¿?é??é?¢ï¼?è¿?æ??å?³ç??æ?¨ç??ç³»ç»?æ?¶é?´è®¾ç½®é??è¯¯ã??è¯·ç¡®è®¤æ?¨ç??æ?¶é?´è®¾ç½®æ?¯æ£ç¡®ç??ï¼?å??æ?¬æ£ç¡®ç??æ?¶å?ºã??ç?¶å??é??æ?°å?¯å?¨Torã?? </p>"
+    },
+    "connecting-3": {
+	"id": "#è¿?æ?¥-3",
+	"control": "è¿?æ?¥-3",
+	"title": "æ??æ? æ³?è®¿é?®X.onionï¼?",
+	"description": "<p class=\"mb-3\">å¦?æ??æ?¨æ? æ³?è®¿é?®æ´?è?±ç«?ç?¹ï¼?è¯·ç¡®è®¤æ?¨è¾?å?¥äº?æ£ç¡®ç??ï¼?16ä½?ç??ç½?å??ï¼?å?³ä½¿ä¸?ä¸ªå¾®å°?ç??é??è¯¯ä¹?ä¼?é?»æ¢Toræµ?è§?å?¨è®¿é?®è¿?ä¸ªç«?ç?¹ã??å¦?æ??æ?¨è¿?æ?¯æ? æ³?è®¿é?®è¿?ä¸ªç½?ç«?ï¼?è¯·ç¨?å??é??è¯?ã??è¿?å?¯è?½æ?¯æ??æ?¶æ?§ç??é?®é¢?ï¼?æ??è??ç½?ç«?ç®¡ç??å??æ?ªç»?å?ºæ ?ç¤ºå°±ä¸?çº¿äº?ç½?ç«?ã??</p><p class=\"mb-3\">æ?¨ä¹?å?¯ä»¥é??è¿?è®¿é?®<a href=\"http://3g2upl4pq6kufc4m.onion\";>DuckDuckGo</a>ç??æ´?è?±ç«?ç?¹æ?¥ç¡®è®¤æ?¨ç??æµ?è§?å?¨é??ç½®æ£ç¡®ã??"
+    }
+}

_______________________________________________
tor-commits mailing list
tor-commits@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits

Prev by Author: [tor-commits] [translation/master] Fixing master
Next by Author: [tor-commits] [translation/tor-launcher-network-settings] Update translations for tor-launcher-network-settings
Previous by thread: [tor-commits] [translation/support-connecting] pulling translations from transifex
Next by thread: [tor-commits] [translation/master] Fixing master
Index(es):
- Author
- Thread