[tor-commits] [translation/support-portal] new translations in support-portal
    translation at torproject.org 
    translation at torproject.org
       
    Fri Jan 14 16:47:42 UTC 2022
    
    
  
commit fdae1f2c3bb611e3560ffe536420bce3459f63b0
Author: Translation commit bot <translation at torproject.org>
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)
    
    
More information about the tor-commits
mailing list