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

translation at torproject.org translation at torproject.org
Wed Apr 18 08:49:52 UTC 2018 

commit 53cded7f5e51d5fb732300b00df4733924f47d22
Author: Translation commit bot <translation at torproject.org>
Date:   Wed Apr 18 08:49:50 2018 +0000

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

diff --git a/ja.json b/ja.json
index 42d95fd92..8d876722e 100644
--- a/ja.json
+++ b/ja.json
@@ -9,7 +9,7 @@
 	"id": "#検閲-2",
 	"control": "検閲-2",
 	"title": "お気に入りのWEBサイトへのアクセスが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\">申し訳ありませんが、あなたの望むWEBサイトにアクセスすることはできません！WEBサイトはしばしばTorユーザーをブロックします。彼らは通常のTorユーザーと自動トラフィックの違いを見分けることができないからです。ブロックを解除しサイトを取得するのにもっとも適した手段は、TOAユーザーがサイト管理者に対して直接的にコンタクトを取ることです。このようなトリックが使えるかもしれません:<br />\"やあ！私はあなたのサイトxyz.comにTorブラウザーでアクセスしようとしたのだけれど、あなたのサイトはTorユーザーへのアクセスを許可していないみたいなんだ。この決定は再検討することをお勧めするよ。Torはプライバシー保護と検閲への対抗の為に世界中の人々によって使われているんだ。Torユーザーã
 ‚’ブロックすることは、自由なインターネットを望む抑圧的な国の人々や、露出から守られるべきジャーナリストや調査員、内部告発者、活動家、及び侵略的なサードパーティのトラッキングから逃れたい普通の人々をもブロックしてしまうんだ。どうか、デジタルプライバシーとインターネットの自由を尊重して、Torユーザーがxyz.comにアクセスできるようにしてほしい。ありがとう。\"<br />銀行やその他の厳密なWEBサイトの場合、その地域の地理的な遮断情報を見ましょう。（銀行があなたが普段ある国からアクセスしていることを知っていれば、あなたのアカウントは突然ロックされたり中断される可能性があります）。もしあなたがオニオンサービスに接続できない場合は、<a href=\"#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ログをクリップボードにコピーする」選択肢を選んで、ログをメモ帳あるいはドキュメントファイルに貼り付けて下さい。以下の良くあるエラーメッセージを見つけるはずです：</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>"
     },
     "censorship-6": {
 	"id": "#検閲-6",

More information about the tor-commits mailing list