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

translation at torproject.org translation at torproject.org
Sat Apr 21 04:49:47 UTC 2018 

commit 87ddaff4617eeb6b129335e162d1ed9a0b0e8d59
Author: Translation commit bot <translation at torproject.org>
Date:   Sat Apr 21 04:49:45 2018 +0000

    Update translations for support-censorship
---
 zh_CN.json | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/zh_CN.json b/zh_CN.json
index d681ecd8e..77e144e42 100644
--- a/zh_CN.json
+++ b/zh_CN.json
@@ -9,7 +9,7 @@
 	"id": "#审查-2",
 	"control": "审查-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 />“嗨，在用 Tor Browser 的时候发现你的网站 xyz.com 不允许来自 Tor 的访问，希望你可以重新考虑这个决定。全球各地很多人都在使用 Tor 来保护隐私和对抗审查，屏蔽 Tor 的同时你也屏蔽了强权国家中想自由访问互联网的用户、需要隐藏自己的记者和检举者、想躲避网络跟踪的研究者和普通用户。请站在支持在线隐私和网络自由的立场上，允许 Tor 用户访问 xyz.com，谢谢！”<br />另外，银行这类比较敏感的网站经常进行地区范围的屏蔽。如果你平时只在某个特定的国家使用他们的服务，从å…
 ¶ä»–国家进行访问时你的账号可能就会被冻结。如无法连接 onion 服务，请参阅 <a href=\\\"http://127.0.0.1:5000/#onionservices-3\\\">无法连接 x.onion！</a></p>"
     },
     "censorship-3": {
 	"id": "#审查-3",
@@ -27,7 +27,7 @@
 	"id": "#审查-5",
 	"control": "审查-5",
 	"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>"
+	"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: 时间设置错误</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. \\nTor需要一个准确的时间来维持它的运作。请检查您的时间，时区以及日期设置。</code></pre></p><p class=\\\"mb-3\\\">如果您看见这些提示出现在您的日志里面，这意味着您的系统时间设置错误。请确认您的时间设置是正确的，包括正确的时区。然后重新启动Tor。 </p>"
     },
     "censorship-6": {
 	"id": "#审查-6",

More information about the tor-commits mailing list