[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

[tor-commits] [translation/support-portal] new translations in support-portal

commit fdae1f2c3bb611e3560ffe536420bce3459f63b0
Author: Translation commit bot <translation@xxxxxxxxxxxxxx>
Date:   Fri Jan 14 16:47:41 2022 +0000

    new translations in support-portal
---
 contents+zh-TW.po | 32 ++++++++++++++++++++------------
 1 file changed, 20 insertions(+), 12 deletions(-)

diff --git a/contents+zh-TW.po b/contents+zh-TW.po
index 49762bb8f4..4a2f18e5a9 100644
--- a/contents+zh-TW.po
+++ b/contents+zh-TW.po
@@ -10044,21 +10044,21 @@ msgstr "ç?ºä»?麼æ??ç??æ´?è?¥è·¯ç?±ä¸­ç¹¼ç¯?é»?ç??è¨?æ?¶é«?使ç?¨é??é??麼é«?ï¼?
 msgid ""
 "If your Tor relay is using more memory than you'd like, here are some tips "
 "for reducing its footprint:"
-msgstr ""
+msgstr "å¦?æ??æ?¨ç??æ´?è?¥è·¯ç?±ä¸­ç¹¼ç¯?é»?使ç?¨ç??è¨?æ?¶é«?è¶?é??æ?¨ç??é ?æ??ï¼?å?¯ä»¥å??試以ä¸?æ?¹å¼?ä¾?é??ä½?該使ç?¨ç??ï¼?"
 
 #: https//support.torproject.org/relay-operators/relay-memory/
 #: (content/relay-operators/relay-memory/contents+en.lrquestion.description)
 msgid ""
 "* If you're on Linux, you may be encountering memory fragmentation bugs in "
 "glibc's malloc implementation."
-msgstr ""
+msgstr "* å¦?æ??æ?¨æ?¯ä½¿ç?¨Linux系統ç??話ï¼?æ??å?¯è?½æ?¯é?­é??å?°äº?å?¨Glibcç??mallocå?½å¼?裡ç??è¨?æ?¶é«?ç¢?è£?è?­è?²ã??"
 
 #: https//support.torproject.org/relay-operators/relay-memory/
 #: (content/relay-operators/relay-memory/contents+en.lrquestion.description)
 msgid ""
 "That is, when Tor releases memory back to the system, the pieces of memory "
 "are fragmented so they're hard to reuse."
-msgstr ""
+msgstr "ä¹?å°±æ?¯èªªï¼?ç?¶æ´?è?¥è·¯ç?±ç¨?å¼?å°?è¨?æ?¶é«?é??æ?¾å??ä½?業系統å¾?ï¼?å?ºç?¾ç ´ç¢?ç??è¨?æ?¶é«?空é??ï¼?æ??é?£ä»¥è¢«å??度å?©ç?¨ã??"
 
 #: https//support.torproject.org/relay-operators/relay-memory/
 #: (content/relay-operators/relay-memory/contents+en.lrquestion.description)
@@ -10066,6 +10066,7 @@ msgid ""
 "The Tor tarball ships with OpenBSD's malloc implementation, which doesn't "
 "have as many fragmentation bugs (but the tradeoff is higher CPU load)."
 msgstr ""
+"ç?®å??æ´?è?¥è·¯ç?±ç??tarballå¥?件å??裡æ??é ?è¼?OpenBSDç??æ?¬ç??mallocå?½å¼?ï¼?æ­¤ç??æ?¬ç??å?½å¼?è¼?å°?ç?¼ç??è¨?æ?¶é«?ç¢?è£?ç??å??é¡?(ä½?æ?¯ä»£å?¹å°±æ?¯ä¸­å¤®è??ç??å?¨ç??使ç?¨ç??æ??æ¯?è¼?é«?)ï¼?"
 
 #: https//support.torproject.org/relay-operators/relay-memory/
 #: (content/relay-operators/relay-memory/contents+en.lrquestion.description)
@@ -10073,6 +10074,7 @@ msgid ""
 "You can tell Tor to use this malloc implementation instead: `./configure "
 "--enable-openbsd-malloc`."
 msgstr ""
+"æ?¨å?¯ä»¥é??é??é??å??設å®?ï¼?ä¾?è¦?æ±?æ´?è?¥è·¯ç?±ç¨?å¼?使ç?¨æ­¤ç??æ?¬ç??mallocå?½å¼?ï¼?`./configure --enable-openbsd-malloc`"
 
 #: https//support.torproject.org/relay-operators/relay-memory/
 #: (content/relay-operators/relay-memory/contents+en.lrquestion.description)
@@ -10081,6 +10083,8 @@ msgid ""
 "open, you are probably losing a lot of memory to OpenSSL's internal buffers "
 "(38KB+ per socket)."
 msgstr ""
+"* "
+"è?¥æ?¨æ?¶è¨­ç??æ?¯è¼?é«?é??ç??中繼ç¯?é»?ç??話ï¼?é?£å°±æ??æ??å¾?å¤?æ¢?TLSç??é?£ç·?å??æ??é??é??ï¼?æ­¤æ??OpenSSLç??å?§é?¨ç·©è¡?å??å°±æ??ä½?ç?¨æ??大é??ç??è¨?æ?¶é«?空é??(æ¯?å??網路æ?¥å¥?ç´?é ?38KBç??空é??)ã??"
 
 #: https//support.torproject.org/relay-operators/relay-memory/
 #: (content/relay-operators/relay-memory/contents+en.lrquestion.description)
@@ -10089,44 +10093,46 @@ msgid ""
 "aggressively](https://lists.torproject.org/pipermail/tor-";
 "dev/2008-June/001519.html)."
 msgstr ""
+"æ??å??å·²æ??ç?¹å?¥é??å°?OpenSSLç¨?å¼?é?²è¡?ä¿®è£?é??ï¼?è®?å®?æ??[æ?´ç©?極ç??é??æ?¾å?ºç·©è¡?å??è¨?æ?¶é«?空é??](https://lists.torproject.org/pipermail/tor-";
+"dev/2008-June/001519.html)ã??"
 
 #: https//support.torproject.org/relay-operators/relay-memory/
 #: (content/relay-operators/relay-memory/contents+en.lrquestion.description)
 msgid ""
 "If you update to OpenSSL 1.0.0 or newer, Tor's build process will "
 "automatically recognize and use this feature."
-msgstr ""
+msgstr "è?¥æ?¨æ??OpenSSLæ?´æ?°å?°1.0.0æ??æ?´æ?°ç??ç??æ?¬ï¼?æ´?è?¥è·¯ç?±è¡?ç¨?å°±æ??è?ªå??è­?å?¥ä¸¦ä¸?å??ç?¨è©²å??è?½ã??"
 
 #: https//support.torproject.org/relay-operators/relay-memory/
 #: (content/relay-operators/relay-memory/contents+en.lrquestion.description)
 msgid ""
 "* If you still can't handle the memory load, consider reducing the amount of"
 " bandwidth your relay advertises."
-msgstr ""
+msgstr "* å¦?æ??æ?¨é??æ?¯ç?¡æ³?æ?§å?¶è¨?æ?¶é«?使ç?¨é??ç??話ï¼?å?¯ä»¥è??æ?®èª¿é??中繼ç¯?é»?ç??é¡?å®?頻寬ã??"
 
 #: https//support.torproject.org/relay-operators/relay-memory/
 #: (content/relay-operators/relay-memory/contents+en.lrquestion.description)
 msgid ""
 "Advertising less bandwidth means you will attract fewer users, so your relay"
 " shouldn't grow as large."
-msgstr ""
+msgstr "å°?å¤?廣æ?­è¼?ä½?ç??å?¯ç?¨é »å¯¬å?¼å?¯ä»¥æ¸?å°?å?¸å¼?å?°ç??使ç?¨è??ï¼?é?²è??å°±æ??é??ä½?中繼ç¯?é»?主æ©?ç??è² è¼?é??ï¼?"
 
 #: https//support.torproject.org/relay-operators/relay-memory/
 #: (content/relay-operators/relay-memory/contents+en.lrquestion.description)
 msgid "See the `MaxAdvertisedBandwidth` option in the man page."
-msgstr ""
+msgstr "è«?å??é?±ä¸»é ?ç??`MaxAdvertisedBandwidth`設å®?é ?ç?®ã??"
 
 #: https//support.torproject.org/relay-operators/relay-memory/
 #: (content/relay-operators/relay-memory/contents+en.lrquestion.description)
 msgid ""
 "All of this said, fast Tor relays do use a lot of ram. It is not unusual for"
 " a fast exit relay to use 500-1000 MB of memory."
-msgstr ""
+msgstr "總è??è¨?ä¹?ï¼?é«?é??ç??æ´?è?¥è·¯ç?±ä¸­ç¹¼ç¯?é»?é??常é?½æ??使ç?¨è¼?å¤?ç??主è¨?æ?¶é«?空é??ï¼?å? æ­¤å®?å?¨é??è¡?ç??æ??中ä½?ç?¨æ??500-1000MBç??è¨?æ?¶é«?空é??æ?¯å¾?常è¦?ç??ç?¾è±¡ã??"
 
 #: https//support.torproject.org/relay-operators/relay-write-more-bytes/
 #: (content/relay-operators/relay-write-more-bytes/contents+en.lrquestion.title)
 msgid "Why does my relay write more bytes onto the network than it reads?"
-msgstr ""
+msgstr "ç?ºä»?麼æ??ç??中繼ç¯?é»?å?¨ç¶²è·¯ä¸?å?³é??äº?æ¯?實é??é??æ±?é??é??è¦?å¤?ç??ä½?å??çµ?æ?¸ï¼?"
 
 #: https//support.torproject.org/relay-operators/relay-write-more-bytes/
 #: (content/relay-operators/relay-write-more-bytes/contents+en.lrquestion.description)
@@ -10134,27 +10140,28 @@ msgid ""
 "You're right, for the most part a byte into your Tor relay means a byte out,"
 " and vice versa. But there are a few exceptions:"
 msgstr ""
+"æ?¨ç??è§?念並æ²?æ??é?¯ï¼?å?¨å¤§å¤?æ?¸ç??æ??æ³?ä¸?ï¼?ç?¶æ??ä¸?å??ä½?å??çµ?ç??è³?æ??æµ?é?²æ?¨ç??æ´?è?¥è·¯ç?±ä¸­ç¹¼ç¯?é»?ï¼?就代表ä¹?æ??æ??ä¸?å??ä½?å??çµ?ç??è³?æ??æµ?å?ºï¼?å??ä¹?ä¹?æ?¯äº¦ç?¶ï¼?ä½?æ?¯ä»?æ??æ??å°?æ?¸å¹¾å??ä¾?å¤?æ??æ³?ï¼?"
 
 #: https//support.torproject.org/relay-operators/relay-write-more-bytes/
 #: (content/relay-operators/relay-write-more-bytes/contents+en.lrquestion.description)
 msgid ""
 "If you open your DirPort, then Tor clients will ask you for a copy of the "
 "directory."
-msgstr ""
+msgstr "è?¥æ?¨æ??é??å??DirPortæ??æ¨?ç??話ï¼?é?£æ´?è?¥è·¯ç?±å®¢æ?¶ç«¯ç¨?å¼?å°±æ??å°?æ?¨ç??主æ©?ç´¢å??ç?®é??æ¸?å?®è³?æ??ï¼?"
 
 #: https//support.torproject.org/relay-operators/relay-write-more-bytes/
 #: (content/relay-operators/relay-write-more-bytes/contents+en.lrquestion.description)
 msgid ""
 "The request they make (an HTTP GET) is quite small, and the response is "
 "sometimes quite large."
-msgstr ""
+msgstr "é??種索å??ç?®é??ç??è«?æ±?(HTTP GET)è³?æ??é??é?½å¾?å°?ï¼?ä½?é ?å??è¦?ç??è³?æ??é??å??é??常ç?¸å°?é¾?大ï¼?"
 
 #: https//support.torproject.org/relay-operators/relay-write-more-bytes/
 #: (content/relay-operators/relay-write-more-bytes/contents+en.lrquestion.description)
 msgid ""
 "This probably accounts for most of the difference between your \"write\" "
 "byte count and your \"read\" byte count."
-msgstr ""
+msgstr "é??常é??å°±æ?¯è®?æ?¨ç??主æ©?å°?網路ã??寫å?¥ã??è??ã??è®?å??ã??è³?æ??é??æ??æ??å·®ç?°ç??主è¦?å??å? ã??"
 
 #: https//support.torproject.org/relay-operators/relay-write-more-bytes/
 #: (content/relay-operators/relay-write-more-bytes/contents+en.lrquestion.description)
@@ -10164,6 +10171,7 @@ msgid ""
 "or ssh connection) and wrap it up into an entire 512 byte cell for transport"
 " through the Tor network."
 msgstr ""
+"å?¦ä¸?å??å°?ä¾?å¤?å??æ?¯ç?¶æ?¨æ?¶è¨­ç??æ?¯å?ºå?£ç¯?é»?æ??ï¼?æ?¨ç??主æ©?æ??å¾?é?£ç·?å?ºå?£ç«¯(ä¾?å¦?å?³æ??é??è¨?è»?é«?æ??SSHé?£ç·?)æ?¥æ?¶å°?é??ç??ä½?å??çµ?è³?æ??ï¼?å??å°?ä¹?çµ?è£?æ??512ä½?å??çµ?ç??è³?æ??å??å¾?ï¼?é??å?¥æ´?è?¥è·¯ç?±ç¶²è·¯ä¸­ã??"
 
 #: https//support.torproject.org/relay-operators/run-relay-in-windows/
 #: (content/relay-operators/run-relay-in-windows/contents+en.lrquestion.title)


_______________________________________________
tor-commits mailing list
tor-commits@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits