- tor-commits - lists.torproject.org

[translation/vidalia] Update translations for vidalia
by translation＠torproject.org 25 Dec '12

25 Dec '12

commit fd927f837e83cdeb5fc156dd509f93ed24b5a8fe Author: Translation commit bot <translation(a)torproject.org> Date: Tue Dec 25 20:15:15 2012 +0000 Update translations for vidalia --- es/vidalia_es.po | 12 ++++++------ 1 files changed, 6 insertions(+), 6 deletions(-) diff --git a/es/vidalia_es.po b/es/vidalia_es.po index 845f624..6856b1f 100644 --- a/es/vidalia_es.po +++ b/es/vidalia_es.po @@ -11,7 +11,7 @@ msgstr "" "Project-Id-Version: The Tor Project\n" "Report-Msgid-Bugs-To: https://trac.torproject.org/projects/tor\n" "POT-Creation-Date: 2012-03-21 17:52+0000\n" -"PO-Revision-Date: 2012-12-25 17:13+0000\n" +"PO-Revision-Date: 2012-12-25 20:10+0000\n" "Last-Translator: strel <strelnic(a)gmail.com>\n" "Language-Team: Spanish (http://www.transifex.com/projects/p/torproject/language/es/)\n" "MIME-Version: 1.0\n" @@ -3297,7 +3297,7 @@ msgstr "Tor ha determinado que el reloj de su equipo podría estar ajustado con msgctxt "StatusEventWidget" msgid "Your Computer's Clock is Potentially Incorrect" -msgstr "El reloj de su equipo podría estar desajustado." +msgstr "La hora del reloj de su equipo podría ser incorrecta." msgctxt "StatusEventWidget" msgid "" @@ -3324,7 +3324,7 @@ msgid "" "using a protocol that may leak information about your destination. Please " "ensure you configure your applications to use only SOCKS4a or SOCKS5 with " "remote hostname resolution." -msgstr "Una de sus aplicaciones ha establecido una conexión a través de Tor a \"%1\" usando un protocolo que podría revelar información sobre su destino. Asegúrese de configurar sus aplicaciones utilizando solamente SOCKS4a o SOCKS5 con resolución remota del nombre del servidor." +msgstr "Una de sus aplicaciones ha establecido una conexión a través de Tor a \"%1\" usando un protocolo que podría revelar información sobre su destino. Asegúrese de configurar sus aplicaciones para usar solamente SOCKS4a o SOCKS5 con resolución de nombre de servidor remoto." msgctxt "StatusEventWidget" msgid "Unknown SOCKS Protocol" @@ -3335,7 +3335,7 @@ msgid "" "One of your applications tried to establish a connection through Tor using a" " protocol that Tor does not understand. Please ensure you configure your " "applications to use only SOCKS4a or SOCKS5 with remote hostname resolution." -msgstr "Una de sus aplicaciones ha tratado de establecer una conexión a través de Tor usando un protocolo que Tor no reconoce. Asegúrese de configurar sus aplicaciones utilizando solamente SOCKS4a o SOCKS5 con resolución remota del nombre del servidor." +msgstr "Una de sus aplicaciones ha tratado de establecer una conexión a través de Tor usando un protocolo que Tor no reconoce. Asegúrese de configurar sus aplicaciones utilizando solamente SOCKS4a o SOCKS5 con resolución de nombre de servidor remoto." msgctxt "StatusEventWidget" msgid "Invalid Destination Hostname" @@ -3346,7 +3346,7 @@ msgid "" "One of your applications tried to establish a connection through Tor to " "\"%1\", which Tor does not recognize as a valid hostname. Please check your " "application's configuration." -msgstr "Una de sus aplicaciones ha tratado de establecer una conexión a través de Tor a \"%1\", que Tor no reconoce como un nombre de servidor válido. Revise la configuración de su aplicación." +msgstr "Una de sus aplicaciones trató de establecer una conexión a través de Tor a \"%1\", que Tor no reconoce como un nombre de servidor válido. Revise la configuración de su aplicación." msgctxt "StatusEventWidget" msgid "External IP Address Changed" @@ -3361,7 +3361,7 @@ msgstr "Tor ha determinado que la dirección IP pública de su repetidor es %1%2 msgctxt "StatusEventWidget" msgid "DNS Hijacking Detected" -msgstr "Manipulación del DNS Detectada" +msgstr "Detectado secuestro del DNS" msgctxt "StatusEventWidget" msgid ""

1 0

r25966: {website} fix bad link from r25865 (website/trunk/docs/en)
by Roger Dingledine 25 Dec '12

25 Dec '12

Author: arma Date: 2012-12-25 19:54:40 +0000 (Tue, 25 Dec 2012) New Revision: 25966 Modified: website/trunk/docs/en/bridges.wml Log: fix bad link from r25865 Modified: website/trunk/docs/en/bridges.wml =================================================================== --- website/trunk/docs/en/bridges.wml 2012-12-25 19:48:46 UTC (rev 25965) +++ website/trunk/docs/en/bridges.wml 2012-12-25 19:54:40 UTC (rev 25966) @@ -95,9 +95,9 @@ flow of Tor, making its detection harder. To connect to obfuscated bridges you need to use the <a - href=https://www.torproject.org/projects/obfsproxy.html.en#download>Obfproxy + href="<page projects/obfsproxy>#download">Obfsproxy Tor Browser Bundle</a>. The bundle includes some pre-configured - obfsproxy bridges and you can get more off <a + obfsproxy bridges and you can get more from <a href=https://bridges.torproject.org/?transport=obfs2>BridgeDB</a> <a id="Understanding"></a>

1 0

r25965: {website} they'll figure out what vidalia is soon enough (website/trunk/docs/en)
by Roger Dingledine 25 Dec '12

25 Dec '12

Author: arma Date: 2012-12-25 19:48:46 +0000 (Tue, 25 Dec 2012) New Revision: 25965 Modified: website/trunk/docs/en/sidenav.wmi Log: they'll figure out what vidalia is soon enough Modified: website/trunk/docs/en/sidenav.wmi =================================================================== --- website/trunk/docs/en/sidenav.wmi 2012-12-25 19:48:06 UTC (rev 25964) +++ website/trunk/docs/en/sidenav.wmi 2012-12-25 19:48:46 UTC (rev 25965) @@ -63,7 +63,7 @@ 'txt' => 'Configuring a Relay manually', }, {'url' => 'docs/tor-doc-relay', - 'txt' => 'Configuring a Relay with Vidalia', + 'txt' => 'Configuring a Relay graphically', }, {'url' => 'docs/tor-hidden-service', 'txt' => 'Configuring a Hidden Service',

1 0

r25964: {website} and add the new page to the sidenav as well (website/trunk/docs/en)
by Roger Dingledine 25 Dec '12

25 Dec '12

Author: arma Date: 2012-12-25 19:48:06 +0000 (Tue, 25 Dec 2012) New Revision: 25964 Modified: website/trunk/docs/en/sidenav.wmi Log: and add the new page to the sidenav as well Modified: website/trunk/docs/en/sidenav.wmi =================================================================== --- website/trunk/docs/en/sidenav.wmi 2012-12-25 19:44:46 UTC (rev 25963) +++ website/trunk/docs/en/sidenav.wmi 2012-12-25 19:48:06 UTC (rev 25964) @@ -59,8 +59,11 @@ 'url' => 'docs/short-user-manual', 'txt' => 'Short User Manual', }, + {'url' => 'docs/tor-relay-debian', + 'txt' => 'Configuring a Relay manually', + }, {'url' => 'docs/tor-doc-relay', - 'txt' => 'Configuring a Relay', + 'txt' => 'Configuring a Relay with Vidalia', }, {'url' => 'docs/tor-hidden-service', 'txt' => 'Configuring a Hidden Service',

1 0

r25963: {website} make the page more usable for non-debian folks (website/trunk/docs/en)
by Roger Dingledine 25 Dec '12

25 Dec '12

Author: arma Date: 2012-12-25 19:44:46 +0000 (Tue, 25 Dec 2012) New Revision: 25963 Modified: website/trunk/docs/en/tor-relay-debian.wml Log: make the page more usable for non-debian folks Modified: website/trunk/docs/en/tor-relay-debian.wml =================================================================== --- website/trunk/docs/en/tor-relay-debian.wml 2012-12-25 19:44:05 UTC (rev 25962) +++ website/trunk/docs/en/tor-relay-debian.wml 2012-12-25 19:44:46 UTC (rev 25963) @@ -36,6 +36,9 @@ instructions to use our repository. </p> + <p>For other Unix/Linux uesrs, you can download Tor from one of our + <a href="<page download/download-unix>">repositories</a>.</p> + <hr> <a id="setup"></a> <h2><a class="anchor" href="#setup">Step Two: Set it up as a relay</a></h2>

1 0

r25962: {website} link from the relays-activism page to the linux relay instru (website/trunk/getinvolved/en)
by Roger Dingledine 25 Dec '12

25 Dec '12

Author: arma Date: 2012-12-25 19:44:05 +0000 (Tue, 25 Dec 2012) New Revision: 25962 Modified: website/trunk/getinvolved/en/relays.wml Log: link from the relays-activism page to the linux relay instructions too Modified: website/trunk/getinvolved/en/relays.wml =================================================================== --- website/trunk/getinvolved/en/relays.wml 2012-12-25 19:25:40 UTC (rev 25961) +++ website/trunk/getinvolved/en/relays.wml 2012-12-25 19:44:05 UTC (rev 25962) @@ -36,7 +36,7 @@ href="https://media.torproject.org/video/2012-03-04-BuildingBridges-HD-spanish.ogv">Spanish</a></p> <p>The Tor network relies on volunteers to donate bandwidth. The more -people who run Tor as a bridge or a relay, the faster and safer the +people who run Tor as a relay or a bridge, the faster and safer the network becomes.</p> <h1>Three ways to join and help out</h1> @@ -52,7 +52,7 @@ <div class="dbox donate"> <a name="diy"></a> <h2>Run it yourself</h2> -<p>You can run Tor as either a bridge or a relay. A bridge will usually +<p>You can run Tor as either a relay or a bridge. A bridge will usually see less traffic than a relay, and will only be the first hop in the three hop circuit. </p> @@ -85,12 +85,9 @@ docs/tor-doc-relay>#setup">relay</a>.</p> <h3>Unix, Linux, BSD, and everything else</h3> -<p>We assume you're an expert and can figure out how to install -Tor by yourself. You can also download Tor from one of our <a -href="https://www.torproject.org/download/download-unix.html.en">repositories</a>.</p> -<p>Read the instructions on how to configure a <a href="<page -docs/bridges>#RunningABridge">bridge</a> or a <a href="<page -docs/tor-doc-relay>#setup">relay</a>.</p> +<p>Read the instructions on how to configure a +<a href="<page docs/tor-relay-debian>">relay</a> +or a <a href="<page docs/bridges>#RunningABridge">bridge</a>.</p> </div> </div>

1 0

r25961: {website} vidalia users can't do all that mumbo-jumbo (website/trunk/docs/en)
by Roger Dingledine 25 Dec '12

25 Dec '12

Author: arma Date: 2012-12-25 19:25:40 +0000 (Tue, 25 Dec 2012) New Revision: 25961 Modified: website/trunk/docs/en/tor-doc-relay.wml Log: vidalia users can't do all that mumbo-jumbo Modified: website/trunk/docs/en/tor-doc-relay.wml =================================================================== --- website/trunk/docs/en/tor-doc-relay.wml 2012-12-25 19:21:39 UTC (rev 25960) +++ website/trunk/docs/en/tor-doc-relay.wml 2012-12-25 19:25:40 UTC (rev 25961) @@ -161,23 +161,12 @@ <h2><a class="anchor" href="#after">Step Four: Once it is working</a></h2> <br> - <p> - We recommend the following steps as well: - </p> - - <ol> - <li>Read + <p>Read <a href="<wiki>doc/OperationalSecurity">about operational security</a> to get ideas how you can increase the security of your relay. - </li> + </p> - <li> - If you want to run more than one relay that's great, but please set <a - href="<page docs/faq>#MultipleRelays">the - MyFamily option</a> in all your relays' configuration files. - </li> - - <li> + <p> If you control the name servers for your domain, consider setting your reverse DNS hostname to 'anonymous-relay', 'proxy' or 'tor-proxy', so when other people see the address in their web logs, they will more quickly @@ -185,24 +174,8 @@ href="<gitblob>contrib/tor-exit-notice.html">Tor exit notice</a> on a vhost for this name can go a long way to deterring abuse complaints to you and your ISP if you are running an exit node. - </li> + </p> - <li> - If your computer isn't running a webserver, please consider - changing your ORPort to 443 and your DirPort to 80. Many Tor - users are stuck behind firewalls that only let them browse the - web, and this change will let them reach your Tor relay. Win32 - relays can simply change their ORPort and DirPort directly - in their torrc and restart Tor. OS X or Unix relays can't bind - directly to these ports (since they don't run as root), so they will - need to set up some sort of <a - href="<wikifaq>#ServerForFirewalledClients"> - port forwarding</a> so connections can reach their Tor relay. If you are - using ports 80 and 443 already but still want to help out, other useful - ports are 22, 110, and 143. - </li> - </ol> - <p> When you change your Tor configuration, remember to verify that your relay still works correctly after the change.

1 0

r25960: {website} simplify tor-doc-relay since it's mainly for vidalia users n (website/trunk/docs/en)
by Roger Dingledine 25 Dec '12

25 Dec '12

Author: arma Date: 2012-12-25 19:21:39 +0000 (Tue, 25 Dec 2012) New Revision: 25960 Modified: website/trunk/docs/en/tor-doc-relay.wml Log: simplify tor-doc-relay since it's mainly for vidalia users now Modified: website/trunk/docs/en/tor-doc-relay.wml =================================================================== --- website/trunk/docs/en/tor-doc-relay.wml 2012-12-25 19:11:34 UTC (rev 25959) +++ website/trunk/docs/en/tor-doc-relay.wml 2012-12-25 19:21:39 UTC (rev 25960) @@ -53,24 +53,13 @@ <h2><a class="anchor" href="#setup">Step Two: Set it up as a relay</a></h2> <br> <ol> + <li>Verify that your clock and timezone are set correctly. If possible, synchronize your clock with public <a href="http://en.wikipedia.org/wiki/Network_Time_Protocol">time servers</a>. </li> - <li><strong>Manual Configuration</strong>: - <ul> - <li>Edit the bottom part of <a href="<page docs/faq>#torrc">your - torrc file</a>. If you want to be a public relay (recommended), - make sure to define ORPort and <a href="<page - docs/faq>#ExitPolicies">look at ExitPolicy</a>; otherwise - if you want to be a <a href="<page docs/faq>#RelayOrBridge">bridge</a> - for users in countries that censor their Internet, - just use <a href="<page docs/bridges>#RunningABridge">these lines</a>. - </li> - </ul></li> - <li><strong>Configuring Tor with the Vidalia Graphical Interface</strong>: <ol> @@ -176,49 +165,30 @@ We recommend the following steps as well: </p> - <p> - 6. Read + <ol> + <li>Read <a href="<wiki>doc/OperationalSecurity">about operational security</a> to get ideas how you can increase the security of your relay. - </p> + </li> - <p> - 7. If you want to run more than one relay that's great, but please set <a + <li> + If you want to run more than one relay that's great, but please set <a href="<page docs/faq>#MultipleRelays">the MyFamily option</a> in all your relays' configuration files. - </p> + </li> - <p> - 8. Decide about rate limiting. Cable modem, DSL, and other users - who have asymmetric bandwidth (e.g. more down than up) should - rate limit to their slower bandwidth, to avoid congestion. See the <a - href="<wikifaq>#LimitBandwidth">rate - limiting FAQ entry</a> for details. - </p> - - <p> - 9. Back up your Tor relay's private key (stored in "keys/secret_id_key" - in your DataDirectory). This is your relay's "identity," and - you need to keep it safe so nobody can read the traffic that goes - through your relay. This is the critical file to keep if you need to <a - href="<wikifaq>#UpgradeRelay">move - or restore your Tor relay</a> if something goes wrong. - </p> - - <p> - - 10. If you control the name servers for your domain, consider setting your + <li> + If you control the name servers for your domain, consider setting your reverse DNS hostname to 'anonymous-relay', 'proxy' or 'tor-proxy', so when other people see the address in their web logs, they will more quickly understand what's going on. Adding the <a href="<gitblob>contrib/tor-exit-notice.html">Tor exit notice</a> on a vhost for this name can go a long way to deterring abuse complaints to you and your ISP if you are running an exit node. + </li> - </p> - - <p> - 11. If your computer isn't running a webserver, please consider + <li> + If your computer isn't running a webserver, please consider changing your ORPort to 443 and your DirPort to 80. Many Tor users are stuck behind firewalls that only let them browse the web, and this change will let them reach your Tor relay. Win32 @@ -230,52 +200,13 @@ port forwarding</a> so connections can reach their Tor relay. If you are using ports 80 and 443 already but still want to help out, other useful ports are 22, 110, and 143. - </p> + </li> + </ol> <p> - 12. If your Tor relay provides other services on the same IP address - — such as a public webserver — make sure that connections to the - webserver are allowed from the local host too. You need to allow these - connections because Tor clients will detect that your Tor relay is the <a - href="<wikifaq>#ExitEavesdroppers">safest - way to reach that webserver</a>, and always build a circuit that ends - at your relay. If you don't want to allow the connections, you must - explicitly reject them in your exit policy. - </p> - - <p> - 13. (Unix only). Make a separate user to run the relay. If you - installed the OS X package or the deb or the rpm, this is already - done. Otherwise, you can do it by hand. (The Tor relay doesn't need to - be run as root, so it's good practice to not run it as root. Running - as a 'tor' user avoids issues with identd and other services that - detect user name. If you're the paranoid sort, feel free to <a - href="<wiki>doc/TorInChroot">put Tor - into a chroot jail</a>.) - </p> - - <p> - 14. (Unix only.) Your operating system probably limits the number - of open file descriptors per process to 1024 (or even less). If you - plan to be running a fast exit node, this is probably not enough. On - Linux, you should add a line like "toruser hard nofile 8192" to your - /etc/security/limits.conf file (where toruser is the user that runs the - Tor process), and then restart Tor if it's installed as a package (or log - out and log back in if you run it yourself). The Debian/Ubuntu package - does this step for you. - </p> - - <p> - 15. If you installed Tor via some package or installer, it probably starts - Tor for you automatically on boot. But if you installed from source, - you may find the initscripts in contrib/tor.sh or contrib/torctl useful. - </p> - - <p> When you change your Tor configuration, remember to verify that your - relay still works correctly after the change. Be sure to set your - "ContactInfo" line in the torrc so we can contact you if you need to - upgrade or something goes wrong. If you have problems or questions, see + relay still works correctly after the change. + If you have problems or questions, see the <a href="<page docs/documentation>#Support">Support</a> section or <a href="<page about/contact>">contact us</a> on the tor-ops list. Thanks for helping to make the Tor network grow! @@ -295,3 +226,4 @@ </div>  #include <foot.wmi> +

1 0

r25959: {website} link to the debian-relay instructions (website/trunk/docs/en)
by Roger Dingledine 25 Dec '12

25 Dec '12

Author: arma Date: 2012-12-25 19:11:34 +0000 (Tue, 25 Dec 2012) New Revision: 25959 Modified: website/trunk/docs/en/tor-doc-relay.wml Log: link to the debian-relay instructions Modified: website/trunk/docs/en/tor-doc-relay.wml =================================================================== --- website/trunk/docs/en/tor-doc-relay.wml 2012-12-25 06:57:04 UTC (rev 25958) +++ website/trunk/docs/en/tor-doc-relay.wml 2012-12-25 19:11:34 UTC (rev 25959) @@ -27,6 +27,11 @@ Windows Server 2003 or later. </p> + <p>If you're comfortable editing text files, skip this page and + go to our dedicated <a href="<page docs/tor-relay-debian>">Relay + Configuration Instructions on Debian/Ubuntu</a> page. That page is + the best one for relay operators on BSD, Unix, etc as well.</p> + <hr> <a id="zero"></a> <a id="install"></a>

1 0

[translation/vidalia_alpha_completed] Update translations for vidalia_alpha_completed
by translation＠torproject.org 25 Dec '12

25 Dec '12

commit 70462cb21a8699686f9dd1bfdf58602644ac3173 Author: Translation commit bot <translation(a)torproject.org> Date: Tue Dec 25 17:45:25 2012 +0000 Update translations for vidalia_alpha_completed --- es/vidalia_es.po | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/es/vidalia_es.po b/es/vidalia_es.po index f9d0aed..d12da23 100644 --- a/es/vidalia_es.po +++ b/es/vidalia_es.po @@ -9,7 +9,7 @@ msgstr "" "Project-Id-Version: The Tor Project\n" "Report-Msgid-Bugs-To: https://trac.torproject.org/projects/tor\n" "POT-Creation-Date: 2012-03-21 17:46+0000\n" -"PO-Revision-Date: 2012-12-25 17:15+0000\n" +"PO-Revision-Date: 2012-12-25 17:18+0000\n" "Last-Translator: strel <strelnic(a)gmail.com>\n" "Language-Team: Spanish (http://www.transifex.com/projects/p/torproject/language/es/)\n" "MIME-Version: 1.0\n" @@ -3365,7 +3365,7 @@ msgstr "Una de las aplicaciones de su computadora podría haber intentado establ msgctxt "StatusEventWidget" msgid "Potentially Dangerous Connection!" -msgstr "¡Es posible que su conexión sea peligrosa!" +msgstr "¡Conexión potencialmente peligrosa!" msgctxt "StatusEventWidget" msgid ""

1 0