[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[tor-commits] [translation/support-censorship] Update translations for support-censorship
commit 603db85bb53dd1dc71697735b2f4193fabaf9874
Author: Translation commit bot <translation@xxxxxxxxxxxxxx>
Date: Fri May 11 20:48:56 2018 +0000
Update translations for support-censorship
---
ru.json | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/ru.json b/ru.json
index cf1b6877a..1947a5841 100644
--- a/ru.json
+++ b/ru.json
@@ -9,13 +9,13 @@
"id": "#censorship-2",
"control": "censorship-2",
"title": "Ð?ой лÑ?бимÑ?й Ñ?айÑ? блокиÑ?Ñ?еÑ? доÑ?Ñ?Ñ?п Ñ?еÑ?ез Tor.",
- "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv
acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"#onionservices-3\">I cannot reach X.onion!</a></p>"
+ "description": "<p class=\"mb-3\">Ð?еÑ?алÑ?но Ñ?лÑ?Ñ?аÑ?Ñ?, Ñ?Ñ?о вÑ? не можеÑ?е поÑ?еÑ?иÑ?Ñ? веб-Ñ?айÑ?, коÑ?оÑ?Ñ?й вам нÑ?жен! Ð?ногда веб-Ñ?айÑ?Ñ? блокиÑ?Ñ?Ñ?Ñ? полÑ?зоваÑ?елей Tor, поÑ?омÑ? Ñ?Ñ?о они не могÑ?Ñ? опÑ?еделиÑ?Ñ? Ñ?азниÑ?Ñ? междÑ? обÑ?Ñ?нÑ?м полÑ?зоваÑ?елем Tor и авÑ?омаÑ?иÑ?еÑ?ким Ñ?Ñ?аÑ?иком. Ð?аилÑ?Ñ?Ñ?им извеÑ?Ñ?нÑ?м нам вÑ?Ñ?одом длÑ? Ñ?азблокиÑ?ованиÑ? полÑ?зоваÑ?елей Tor бÑ?деÑ? Ñ?ледÑ?Ñ?Ñ?ее: полÑ?зоваÑ?елÑ?м надлежиÑ? напÑ?Ñ?мÑ?Ñ? обÑ?аÑ?аÑ?Ñ?Ñ?Ñ? к админиÑ?Ñ?Ñ?аÑ?оÑ?ам Ñ?айÑ?а. Ð?ногда Ñ?Ñ?абаÑ?Ñ?ваеÑ? Ñ?акой Ñ?Ñ?Ñ?к:<br />\"Ð?Ñ?ивеÑ?! Я попÑ?Ñ?алÑ?Ñ? полÑ?Ñ?иÑ?Ñ? доÑ?Ñ?Ñ?п к ваÑ?емÑ? Ñ?айÑ?Ñ? xyz.com Ñ?еÑ?ез Tor Browser и обнаÑ?Ñ?жил, Ñ?Ñ?о вÑ? не Ñ?азÑ?еÑ?аеÑ?е полÑ?зоваÑ?елÑ?Ð
¼ Tor заÑ?одиÑ?Ñ? на него. Я наÑ?Ñ?оÑ?Ñ?елÑ?но пÑ?изÑ?ваÑ? ваÑ? пеÑ?еÑ?моÑ?Ñ?еÑ?Ñ? Ñ?Ñ?о Ñ?еÑ?ение: Tor иÑ?полÑ?зÑ?еÑ?Ñ?Ñ? лÑ?дÑ?ми во вÑ?ем миÑ?е длÑ? заÑ?иÑ?Ñ? иÑ? конÑ?иденÑ?иалÑ?ноÑ?Ñ?и и боÑ?Ñ?бÑ? Ñ? Ñ?ензÑ?Ñ?ой. Ð?локиÑ?Ñ?Ñ? полÑ?зоваÑ?елей Tor, вÑ? навеÑ?нÑ?ка блокиÑ?Ñ?еÑ?е лÑ?дей в Ñ?епÑ?еÑ?Ñ?ивнÑ?Ñ? Ñ?Ñ?Ñ?анаÑ?, коÑ?оÑ?Ñ?е Ñ?оÑ?Ñ?Ñ? иÑ?полÑ?зоваÑ?Ñ? Ñ?вободнÑ?й инÑ?еÑ?неÑ?, жÑ?Ñ?налиÑ?Ñ?ов и иÑ?Ñ?ледоваÑ?елей, коÑ?оÑ?Ñ?е Ñ?оÑ?Ñ?Ñ? заÑ?иÑ?иÑ?Ñ? Ñ?ебÑ? оÑ? Ñ?лежки и оÑ?ведомиÑ?елей, акÑ?ивиÑ?Ñ?ов и обÑ?Ñ?нÑ?Ñ? лÑ?дей, коÑ?оÑ?Ñ?е Ñ?оÑ?Ñ?Ñ? оÑ?казаÑ?Ñ?Ñ?Ñ? оÑ? инвазивного оÑ?Ñ?леживаниÑ? Ñ?Ñ?еÑ?Ñ?ей Ñ?Ñ?оÑ?оной. Ð?ожалÑ?йÑ?Ñ?а, пÑ?идеÑ?живайÑ?еÑ?Ñ? Ñ?еÑ?иÑ?елÑ?ной позиÑ?ии в полÑ?зÑ? конÑ?и
денÑ?иалÑ?ноÑ?Ñ?и Ñ?иÑ?Ñ?ового конÑ?енÑ?а и Ñ?вободÑ? в инÑ?еÑ?неÑ?е и Ñ?азÑ?еÑ?айÑ?е полÑ?зоваÑ?елÑ?м Tor заÑ?одиÑ?Ñ? на xyz.com. СпаÑ?ибо.\"<br />Ð? Ñ?лÑ?Ñ?ае Ñ? банками и дÑ?Ñ?гими Ñ?Ñ?вÑ?Ñ?виÑ?елÑ?нÑ?ми веб-Ñ?айÑ?ами Ñ?акже Ñ?аÑ?Ñ?о наблÑ?даеÑ?Ñ?Ñ? блокиÑ?ование на оÑ?нове меÑ?Ñ?оположениÑ? (еÑ?ли банк знаеÑ?, Ñ?Ñ?о вÑ? обÑ?Ñ?но обÑ?аÑ?аеÑ?еÑ?Ñ? к иÑ? Ñ?Ñ?лÑ?гам из одной Ñ?Ñ?Ñ?анÑ? и вдÑ?Ñ?г вÑ? подклÑ?Ñ?аеÑ?еÑ?Ñ? Ñ?еÑ?ез Ñ?еÑ?Ñ?анÑ?лÑ?Ñ?оÑ? на дÑ?Ñ?гой Ñ?Ñ?оÑ?оне миÑ?а, ваÑ?а Ñ?Ñ?Ñ?Ñ?наÑ? запиÑ?Ñ? и Ñ?Ñ?Ñ?Ñ? могÑ?Ñ? бÑ?Ñ?Ñ? заблокиÑ?ованÑ? или замоÑ?оженÑ?). Ð?Ñ?ли вÑ? не можеÑ?е подклÑ?Ñ?иÑ?Ñ?Ñ?Ñ? к onion-Ñ?айÑ?Ñ?, Ñ?м. <a href=\"#onionservices-3\">Я не могÑ? оÑ?кÑ?Ñ?Ñ?Ñ? X.onion!</a></p>"
},
"censorship-3": {
"id": "#censorship-3",
"control": "censorship-3",
"title": "Ð?ак загÑ?Ñ?зиÑ?Ñ? Tor, еÑ?ли torproject.org заблокиÑ?ован?",
- "description": "<p class=\"mb-3\">Ð?Ñ?ли Ð?Ñ? не можеÑ?е Ñ?каÑ?аÑ?Ñ? Tor Ñ?еÑ?ез наÑ? <mark><a href=\"https://www.torproject.org\";>Ñ?айÑ?</a></mark>, вÑ? можеÑ?е полÑ?Ñ?иÑ?Ñ? копиÑ? Tor Ñ?еÑ?ез GetTor. GetTor - Ñ?Ñ?о Ñ?Ñ?лÑ?га, коÑ?оÑ?аÑ? авÑ?омаÑ?иÑ?еÑ?ки оÑ?веÑ?аеÑ? на Ñ?ообÑ?ениÑ? Ñ?Ñ?Ñ?лками на поÑ?леднÑ?Ñ? веÑ?Ñ?иÑ? Tor Browser, Ñ?азмеÑ?еннÑ?е в Ñ?азлиÑ?нÑ?Ñ? меÑ?Ñ?аÑ?, коÑ?оÑ?Ñ?е менее веÑ?оÑ?Ñ?но подвеÑ?гаÑ?Ñ?Ñ?Ñ? Ñ?ензÑ?Ñ?е, Ñ?акие как Dropbox, Google Ð?иÑ?к и Github.</p>"
+ "description": "<p class=\"mb-3\">Ð?Ñ?ли вÑ? не можеÑ?е Ñ?каÑ?аÑ?Ñ? Tor Ñ?еÑ?ез наÑ? <mark><a href=\"https://www.torproject.org\";>Ñ?айÑ?</a></mark>, вÑ? можеÑ?е полÑ?Ñ?иÑ?Ñ? копиÑ? Tor Ñ?еÑ?ез GetTor. GetTor - Ñ?Ñ?о Ñ?Ñ?лÑ?га, коÑ?оÑ?аÑ? авÑ?омаÑ?иÑ?еÑ?ки оÑ?веÑ?аеÑ? на Ñ?ообÑ?ениÑ? Ñ?Ñ?Ñ?лками на поÑ?леднÑ?Ñ? веÑ?Ñ?иÑ? Tor Browser, Ñ?азмеÑ?еннÑ?е в Ñ?азлиÑ?нÑ?Ñ? меÑ?Ñ?аÑ?, коÑ?оÑ?Ñ?е менее веÑ?оÑ?Ñ?но подвеÑ?гаÑ?Ñ?Ñ?Ñ? Ñ?ензÑ?Ñ?е, Ñ?акие как Dropbox, Google Ð?иÑ?к и Github.</p>"
},
"censorship-4": {
"id": "#censorship-4",
@@ -26,7 +26,7 @@
"censorship-5": {
"id": "#censorship-5",
"control": "censorship-5",
- "title": "I am having trouble connecting to Tor, and I canâ??t figure out whatâ??s wrong.",
+ "title": "У менÑ? пÑ?облемÑ? Ñ? подклÑ?Ñ?ением к Tor и Ñ? не могÑ? понÑ?Ñ?Ñ?, Ñ?Ñ?о не Ñ?ак.",
"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>"
},
"censorship-6": {
_______________________________________________
tor-commits mailing list
tor-commits@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits