commit 56a4abecace4b3c32d9e61e9436a3742a896ad33
Author: Translation commit bot <translat...@torproject.org>
Date: Fri Apr 6 23:47:26 2018 +0000
pulling translations from transifex
---
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 ++++++++++++++++++++
14 files changed, 280 insertions(+)
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@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits
