commit 180554e7293e4cafa83aa8f5d212bbd3de5b36ea
Author: Translation commit bot <translat...@torproject.org>
Date: Thu Nov 21 09:45:09 2013 +0000
Update translations for tsum
---
gl/short-user-manual_gl_noimg.xhtml | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/gl/short-user-manual_gl_noimg.xhtml
b/gl/short-user-manual_gl_noimg.xhtml
index 571c6b7..84e7604 100644
--- a/gl/short-user-manual_gl_noimg.xhtml
+++ b/gl/short-user-manual_gl_noimg.xhtml
@@ -52,13 +52,13 @@ sub 2048R/EB399FD7 2003-10-16
<code>gpg --verify tor-browser-2.2.33-2_en-US.exe.asc
tor-browser-2.2.33-2_en-US.exe
</code>
</pre>
- <p>The output should say <em>"Good signature"</em>. A bad signature means
that the file may have been tampered with. If you see a bad signature, send
details about where you downloaded the package from, how you verified the
signature, and the output from GnuPG in an email to h...@rt.torproject.org.</p>
- <p>Once you have verified the signature and seen the <em>"Good
signature"</em> output, go ahead and extract the package archive. You should
then see a directory similar to <strong>tor-browser_en-US</strong>. Inside that
directory is another directory called <strong>Docs</strong>, which contains a
file called <strong>changelog</strong>. You want to make sure that the version
number on the top line of the changelog file matches the version number in the
filename.</p>
- <h3 id="how-to-use-the-tor-browser-bundle">How to use the Tor Browser
Bundle</h3>
+ <p>A saÃda debe dicir <em>"Boa sinatura"</em>. Unha sinatura mala
significa que o ficheiro pode estar adulterado. Se ve unha sinatura mala,
envÃe información sobre o lugar de onde descargou o paquete, como comprobou a
sinatura, ea saÃda de GnuPG nun e-mail a h...@rt.torproject.org.</p>
+ <p>Despois de ter verificado a sinatura e visto a saÃda <em>"Boa
sinatura"</em>, extraia o ficheiro do paquete. DeberÃa ver un directorio como
<strong>tor-browser_en-US</strong>. Dentro deste directorio está outro
directorio chamado <strong>Docs</strong>, que contén un ficheiro chamado
<strong>changelog</strong>. Asegúrese de que o número de versión na liña
superior do ficheiro de changelog corresponde ao número de versión no nome do
ficheiro.</p>
+ <h3 id="how-to-use-the-tor-browser-bundle">Como usar o Tor Browser
Bundle</h3>
<p>After downloading the Tor Browser Bundle and extracting the package,
you should have a directory with a few files in it. One of the files is an
executable called "Start Tor Browser" (or "start-tor-browser", depending on
your operating system).</p>
- <p>When you start the Tor Browser Bundle, you will first see Vidalia start
up and connect you to the Tor network. After that, you will see a browser
confirming that you are now using Tor. This is done by displaying <a
href="https://check.torproject.org/";>https://check.torproject.org/</a>. You can
now browse the Internet through Tor.</p>
+ <p>Cando inicie o Tor Browser Bundle, vai ver primeiro iniciarse Vidalia
e conectalo á rede Tor. Despois diso, vai ver un navegador, confirmando que
está a usar o Tor, amosando <a
href="https://check.torproject.org/";>https://check.torproject.org/</a>. Xa pode
navegar por Internet a través de Tor.</p>
<p>
- <em>Please note that it is important that you use the browser that comes
with the bundle, and not your own browser.</em>
+ <em>Teña en conta que é importante que use o navegador que vén co
paquete, e non o seu propio navegador.</em>
</p>
<h3 id="what-to-do-when-tor-does-not-connect">What to do when Tor does not
connect</h3>
<p>Some users will notice that Vidalia gets stuck when trying to connect
to the Tor network. If this happens, make sure that you are connected to the
Internet. If you need to connect to a proxy server, see <em>How to use an open
proxy</em> below.</p>
_______________________________________________
tor-commits mailing list
tor-commits@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits
