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

translation Thu, 05 Jul 2018 02:19:24 -0700

commit c7572245777013c0d3779c51233cfa0003a1d2ec
Author: Translation commit bot <[email protected]>
Date:   Thu Jul 5 09:19:08 2018 +0000


    Update translations for support-censorship
---
 tr.json | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/tr.json b/tr.json
index 339e1a72f..225d4f0c0 100644
--- a/tr.json
+++ b/tr.json
@@ -27,7 +27,7 @@
        "id": "#sansur-5",
        "control": "sansur-5",
        "title": "Tor 'a baÄlanmakta sÄ±kÄ±ntÄ± Ã§ekiyorum ve ne de problem 
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>"
+       "description": "<p class=\"mb-3\">BaÄlanmakta sorun yaÅÄ±yorsanÄ±z, 
lÃ¼tfen \"Tor gÃ¼nlÃ¼ÄÃ¼nÃ¼ panoya kopyala\" seÃ§eneÄini seÃ§in. Daha sonra 
Tor gÃ¼nlÃ¼ÄÃ¼nÃ¼ bir metin dosyasÄ±na veya baÅka bir belgeye yapÄ±ÅtÄ±rÄ±n. 
Bu genel gÃ¼nlÃ¼k hatalarÄ±ndan birini gÃ¶rmelisiniz (Tor log'unuzda 
aÅaÄÄ±daki satÄ±rlarÄ± arayÄ±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 server failure\")</code></pre></p><p 
class=\"mb-3\">Tor gÃ¼nlÃ¼ÄÃ¼nÃ¼zde bu gibi satÄ±rlar gÃ¶rÃ¼rseniz, SOCKS 
vekil sunucusuna baÄlanamadÄ±ÄÄ±nÄ±z anlamÄ±na gelir. AÄ kurulumunuz iÃ§in 
bir SOCKS sunucusu gerekiyorsa, lÃ¼tfen vekil sunucu ayrÄ±ntÄ±larÄ±nÄ±zÄ± 
doÄru girdiÄinizden emin olun. Bir SOCKS vekil sunucu gerekli deÄilse veya 
emin deÄilseniz, lÃ¼tfen SOCKS vekil sunucu olmadan Tor aÄÄ±na baÄlanmayÄ± 
deneyin.<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. 
Discar
 ding this circuit.</code></pre></p><p class=\"mb-3\">Tor logunuzda bunlara 
benzer satÄ±rlar gÃ¶rÃ¼rseniz, Tor'nuzun Tor devresindeki ilk dÃ¼ÄÃ¼me 
baÄlanamadÄ±ÄÄ± anlamÄ±na gelir. Bu, sansÃ¼rlenen bir aÄda olduÄunuz 
anlamÄ±na gelebilir. LÃ¼tfen kÃ¶prÃ¼lerle baÄlantÄ± kurmayÄ± deneyin, bu 
sorunu Ã§Ã¶zebilir.</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\">Tor gÃ¼nlÃ¼ÄÃ¼nÃ¼zde bunun gibi satÄ±rlar 
 >gÃ¶rÃ¼rseniz, Tor'un dizin yetkilileriyle TLS el sÄ±kÄ±ÅmalarÄ±nÄ± 
 >tamamlayamadÄ±ÄÄ± anlamÄ±na gelir. KÃ¶prÃ¼ler kullanÄ±lmasÄ± muhtemelen bunu 
 >dÃ¼zeltecektir.</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\">Tor gÃ¼nlÃ¼ÄÃ¼nÃ¼zde bunun gibi satÄ±rlar gÃ¶rÃ¼rseniz, 
 >sistem saatinizin yanlÄ±Å olduÄu anlamÄ±na gelir. LÃ¼tfen doÄ
 ru saat dilimi dahil saatinizin doÄru ayarlandÄ±ÄÄ±ndan emin olun. 
ArdÄ±ndan Tor'u tekrar baÅlatÄ±n.</p>"
     },
     "censorship-6": {
        "id": "#sansur-6",

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

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

Reply via email to