[tor-commits] [translation/support-connecting] Update translations for support-connecting

translation Tue, 19 Jun 2018 22:50:01 -0700

commit 22726fbc96a5b52f7ea5cc306ef34fe51dd34bf5
Author: Translation commit bot <[email protected]>
Date:   Wed Jun 20 05:49:04 2018 +0000


    Update translations for support-connecting
---
 tr.json | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/tr.json b/tr.json
index 19e7f3301..9388eb3fc 100644
--- a/tr.json
+++ b/tr.json
@@ -1,19 +1,19 @@
 {
     "connecting-1": {
-       "id": "#baglaniyor-1",
-       "control": "baglaniyor-1",
+       "id": "#baglanti-1",
+       "control": "baglanti-1",
        "title": "Tor Browser baÄlantÄ± kuramÄ±yor ancak bu sorun sansÃ¼r ile 
ilgili gibi gÃ¶rÃ¼nmÃ¼yor.",
-       "description": "<p class=\"mb-3\">Tor Browser'Ä±n baÄlantÄ± 
hatalarÄ±na yok aÃ§an en bÃ¼yÃ¼k sorunlardan biri yanlÄ±Å sistem saati. 
LÃ¼tfen sistem saatiniz ve saat diliminizin doÄru ayarlandÄ±ÄÄ±ndan emin 
olun. EÄer bu probleminizi Ã§Ã¶zmezse, Sorun Giderme sayfasÄ±na<mark><a 
href=\"https://tb-manual.torproject.org/en-US/bridges.html\";>Tor Browser 
KÄ±lavuzu</a></mark> sayfasÄ±ndan ulaÅÄ±n.</p>"
+       "description": "<p class=\"mb-3\">Tor Browser Ã¼zerinde baÄlantÄ± 
sorunlarÄ±na yol aÃ§an en bÃ¼yÃ¼k sorunlardan biri sistem saatinin yanlÄ±Å 
olmasÄ±dÄ±r. LÃ¼tfen sistem saati ve saat diliminin doÄru ayarlandÄ±ÄÄ±ndan 
emin olun. Sorun Ã§Ã¶zÃ¼lmezse, <mark><a 
href=\"https://tb-manual.torproject.org/en-US/bridges.html\";>Tor Browser 
KÄ±lavuzu</a></mark> Ã¼zerindeki Sorun Giderme bÃ¶lÃ¼mÃ¼ne bakabilirsiniz.</p>"
     },
     "connecting-2": {
-       "id": "#connecting-2",
-       "control": "connecting-2",
-       "title": "Tor 'a baÄlanmakta sÄ±kÄ±ntÄ± Ã§ekiyorum ve ne de problem 
olduÄunu bulamÄ±yorum",
+       "id": "#baglanti-2",
+       "control": "baglanti-2",
+       "title": "Tor baÄlantÄ±sÄ± kurmakta sorun yaÅÄ±yorum ve sorunun ne 
olduÄunu bulamÄ±yorum.",
        "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 fa
 ilure\")</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 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.</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 Tor 
 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",
+       "id": "#baglanti-3",
+       "control": "baglanti-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>"
     }

_______________________________________________
tor-commits mailing list
[email protected]
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits

[tor-commits] [translation/support-connecting] Update translations for support-connecting

Reply via email to