qt: translation update

This commit is contained in:
Wladimir J. van der Laan
2015-04-28 09:47:26 +02:00
parent 1d9d314573
commit f9645ba80a
72 changed files with 9829 additions and 3400 deletions

View File

@@ -1,9 +1,9 @@
<TS language="zh_TW" version="2.0">
<TS language="zh_TW" version="2.1">
<context>
<name>AddressBookPage</name>
<message>
<source>Double-click to edit address or label</source>
<translation></translation>
<source>Right-click to edit address or label</source>
<translation></translation>
</message>
<message>
<source>Create a new address</source>
@@ -344,11 +344,11 @@
</message>
<message>
<source>&amp;Send</source>
<translation></translation>
<translation></translation>
</message>
<message>
<source>&amp;Receive</source>
<translation></translation>
<translation></translation>
</message>
<message>
<source>Show information about Bitcoin Core</source>
@@ -576,6 +576,14 @@ Address: %4
<source>Amount</source>
<translation></translation>
</message>
<message>
<source>Received with label</source>
<translation></translation>
</message>
<message>
<source>Received with address</source>
<translation></translation>
</message>
<message>
<source>Date</source>
<translation></translation>
@@ -796,7 +804,7 @@ Address: %4
<name>FreespaceChecker</name>
<message>
<source>A new data directory will be created.</source>
<translation></translation>
<translation></translation>
</message>
<message>
<source>name</source>
@@ -1280,6 +1288,14 @@ Address: %4
<source>Refund from %1</source>
<translation>來自 %1 的退款</translation>
</message>
<message>
<source>Payment request %1 is too large (%2 bytes, allowed %3 bytes).</source>
<translation>付款要求 %1 過大 (%2 位元組, 上限 %3 位元組).</translation>
</message>
<message>
<source>Payment request DoS protection</source>
<translation>支付請求的分佈式阻斷服務攻擊DoS保護</translation>
</message>
<message>
<source>Error communicating with %1: %2</source>
<translation>跟 %1 通訊時發生錯誤: %2</translation>
@@ -1842,7 +1858,7 @@ Address: %4
</message>
<message>
<source>Choose...</source>
<translation>選...</translation>
<translation>選...</translation>
</message>
<message>
<source>collapse fee-settings</source>
@@ -1850,24 +1866,64 @@ Address: %4
</message>
<message>
<source>Minimize</source>
<translation>最小化</translation>
<translation>縮小</translation>
</message>
<message>
<source>If the custom fee is set to 1000 satoshis and the transaction is only 250 bytes, then "per kilobyte" only pays 250 satoshis in fee, while "at least" pays 1000 satoshis. For transactions bigger than a kilobyte both pay by kilobyte.</source>
<translation>如果自訂手續費設定為 1000 satoshi, 而交易資料大小只有 250 個位元組的話,那麽選擇「每千位元組」就只會付 250 satoshi 的手續費,換做選「總共至少」就會付 1000 satoshi. 但是如果交易資料大小超過一千個位元組,那麽兩者都是每千位元組的費用。</translation>
</message>
<message>
<source>per kilobyte</source>
<translation>每千位元組</translation>
</message>
<message>
<source>If the custom fee is set to 1000 satoshis and the transaction is only 250 bytes, then "per kilobyte" only pays 250 satoshis in fee, while "total at least" pays 1000 satoshis. For transactions bigger than a kilobyte both pay by kilobyte.</source>
<translation>如果自訂手續費設定為 1000 satoshi, 而交易資料大小只有 250 個位元組的話,那麽選擇「每千位元組」就只會付 250 satoshi 的手續費,換做選「總共至少」就會付 1000 satoshi. 但是如果交易資料大小超過一千個位元組,那麽兩者都是每千位元組的費用。</translation>
</message>
<message>
<source>total at least</source>
<translation>總共最少</translation>
</message>
<message>
<source>Paying only the minimum fee is just fine as long as there is less transaction volume than space in the blocks. But be aware that this can end up in a never confirming transaction once there is more demand for bitcoin transactions than the network can process.</source>
<translation>當交易量少於區塊可容納的空間時,只付最低手續費不會有什麽問題。但是當交易量的需求成長到超過整體網路可以處理的量時,可能會造成一筆一直不會被確認的交易。</translation>
</message>
<message>
<source>(read the tooltip)</source>
<translation>(請看提示)</translation>
</message>
<message>
<source>Recommended:</source>
<translation>建議值:</translation>
</message>
<message>
<source>Custom:</source>
<translation>自訂:</translation>
</message>
<message>
<source>(Smart fee not initialized yet. This usually takes a few blocks...)</source>
<translation>(手續費智慧演算法還沒準備好。通常都要等幾個區塊才行...)</translation>
</message>
<message>
<source>Confirmation time:</source>
<translation>確認時間:</translation>
</message>
<message>
<source>normal</source>
<translation>正常</translation>
</message>
<message>
<source>fast</source>
<translation>快速</translation>
</message>
<message>
<source>Send as zero-fee transaction if possible</source>
<translation>盡可能送不用付手續費的交易</translation>
</message>
<message>
<source>(confirmation may take longer)</source>
<translation>(確認時間可能拉長)</translation>
</message>
<message>
<source>Send to multiple recipients at once</source>
<translation>一次付給多個收款人</translation>
@@ -1972,6 +2028,18 @@ Address: %4
<source>The transaction was rejected! This might happen if some of the coins in your wallet were already spent, such as if you used a copy of wallet.dat and coins were spent in the copy but not marked as spent here.</source>
<translation>交易被拒絕了!有時候會發生這種錯誤,是因為你錢包中的一些錢已經被花掉了。比如說你複製了錢包檔 wallet.dat, 然後用複製的錢包花掉了錢,你現在所用的原來的錢包中,卻沒有那筆錢已經花掉的紀錄。</translation>
</message>
<message>
<source>A fee higher than %1 is considered an insanely high fee.</source>
<translation>高於 %1 的手續費會被認為是不正常。</translation>
</message>
<message>
<source>Pay only the minimum fee of %1</source>
<translation>只付最低手續費 %1</translation>
</message>
<message>
<source>Estimated to begin confirmation within %1 block(s).</source>
<translation>預計可在 %1 個區塊內開始確認。</translation>
</message>
<message>
<source>Warning: Invalid Bitcoin address</source>
<translation>警告: 位元幣位址無效</translation>
@@ -2747,30 +2815,6 @@ Address: %4
<source>Accept connections from outside (default: 1 if no -proxy or -connect)</source>
<translation>(預設值: 當沒有 -proxy -connect 1)</translation>
</message>
<message>
<source>%s, you must set a rpcpassword in the configuration file:
%s
It is recommended you use the following random password:
rpcuser=bitcoinrpc
rpcpassword=%s
(you do not need to remember this password)
The username and password MUST NOT be the same.
If the file does not exist, create it with owner-readable-only file permissions.
It is also recommended to set alertnotify so you are notified of problems;
for example: alertnotify=echo %%s | mail -s "Bitcoin Alert" admin@foo.com
</source>
<translation>%s, RPC (rpcpassword):
%s
建議你使用以下隨機產生的密碼:
rpcuser=bitcoinrpc
rpcpassword=%s
()
使(rpcuser)(rpcpassword)
比如說設定成:
alertnotify=echo %%s | mail -s "Bitcoin Alert" admin@foo.com</translation>
</message>
<message>
<source>Bind to given address and always listen on it. Use [host]:port notation for IPv6</source>
<translation>IPv6 []: </translation>
@@ -2787,14 +2831,6 @@ alertnotify=echo %%s | mail -s "Bitcoin Alert" admin@foo.com</translation>
<source>Enter regression test mode, which uses a special chain in which blocks can be solved instantly.</source>
<translation>使</translation>
</message>
<message>
<source>Error: The transaction was rejected! This might happen if some of the coins in your wallet were already spent, such as if you used a copy of wallet.dat and coins were spent in the copy but not marked as spent here.</source>
<translation>錯誤: 交易被拒絕了 wallet.dat, </translation>
</message>
<message>
<source>Error: This transaction requires a transaction fee of at least %s because of its amount, complexity, or use of recently received funds!</source>
<translation>錯誤: 這筆交易需要至少 %s 使</translation>
</message>
<message>
<source>Execute command when a wallet transaction changes (%s in cmd is replaced by TxID)</source>
<translation>( %s )</translation>
@@ -2907,10 +2943,6 @@ alertnotify=echo %%s | mail -s "Bitcoin Alert" admin@foo.com</translation>
<source>Error: Disk space is low!</source>
<translation>錯誤: 磁碟空間很少</translation>
</message>
<message>
<source>Error: Wallet locked, unable to create transaction!</source>
<translation>錯誤: 錢包被上鎖了</translation>
</message>
<message>
<source>Failed to listen on any port. Use -listen=0 if you want this.</source>
<translation> -listen=0.</translation>
@@ -3031,14 +3063,30 @@ alertnotify=echo %%s | mail -s "Bitcoin Alert" admin@foo.com</translation>
<source>Fees (in BTC/Kb) smaller than this are considered zero fee for transaction creation (default: %s)</source>
<translation>當製造交易時,如果每千位元組(Kb)的手續費比這個值低,就視為沒付手續費 (預設值: %s)</translation>
</message>
<message>
<source>If paytxfee is not set, include enough fee so transactions begin confirmation on average within n blocks (default: %u)</source>
<translation>當沒有設定 paytxfee 時,自動包含可以讓交易能在平均 n 個區塊內開始確認的手續費(預設值: %u)</translation>
</message>
<message>
<source>Invalid amount for -maxtxfee=&lt;amount&gt;: '%s' (must be at least the minrelay fee of %s to prevent stuck transactions)</source>
<translation>-maxtxfee=&lt;amount&gt;: '%s' 的金額無效 (必須大於最低轉發手續費 %s 以避免交易無法確認)</translation>
</message>
<message>
<source>Maximum size of data in data carrier transactions we relay and mine (default: %u)</source>
<translation>轉發和開採時,對只帶資料的交易的大小上限(預設值: %u)</translation>
</message>
<message>
<source>Maximum total fees to use in a single wallet transaction, setting too low may abort large transactions (default: %s)</source>
<translation>一次錢包交易允許付出最高的總手續費,設定太低的話,可能會無法進行資料量大的交易(預設值: %s)</translation>
</message>
<message>
<source>Query for peer addresses via DNS lookup, if low on addresses (default: 1 unless -connect)</source>
<translation>是否允許在節點位址數目不足時,使用域名查詢來搜尋節點 (預設值: 當沒用 -connect 時為 1)</translation>
</message>
<message>
<source>Require high priority for relaying free or low-fee transactions (default:%u)</source>
<translation>沒有手續費或手續費比較低的交易是否必須要是高優先權才會轉發(預設值: %u)</translation>
</message>
<message>
<source>Set maximum size of high-priority/low-fee transactions in bytes (default: %d)</source>
<translation>設定高優先度或低手續費的交易資料大小上限成多少位元組(預設值: %d)</translation>
@@ -3051,6 +3099,34 @@ alertnotify=echo %%s | mail -s "Bitcoin Alert" admin@foo.com</translation>
<source>This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit &lt;https://www.openssl.org/&gt; and cryptographic software written by Eric Young and UPnP software written by Thomas Bernard.</source>
<translation>此產品也包含了由 OpenSSL Project 所開發的 OpenSSL Toolkit 軟體 &lt;https://www.openssl.org/&gt;, 和由 Eric Young 撰寫的加解密軟體,以及由 Thomas Bernard 所撰寫的 UPnP 軟體。</translation>
</message>
<message>
<source>To use bitcoind, or the -server option to bitcoin-qt, you must set an rpcpassword in the configuration file:
%s
It is recommended you use the following random password:
rpcuser=bitcoinrpc
rpcpassword=%s
(you do not need to remember this password)
The username and password MUST NOT be the same.
If the file does not exist, create it with owner-readable-only file permissions.
It is also recommended to set alertnotify so you are notified of problems;
for example: alertnotify=echo %%s | mail -s "Bitcoin Alert" admin@foo.com
</source>
<translation>要使用 bitcoind, 或是對 bitcoin-qt 指定 -server 選項,你必須要在以下設定檔中設定 RPC 密碼(選項: rpcpassword):
%s
建議你使用以下隨機產生的密碼:
rpcuser=bitcoinrpc
rpcpassword=%s
(你不用記住這個密碼)
注意使用者名稱(rpcuser)和密碼(rpcpassword)不可以相同!
如果設定檔還不存在,請在新增時,設定檔案權限為"只有主人才能讀取"。
也建議你設定警示通知,這樣發生問題時你才會被通知到;
比如說設定: alertnotify=echo %%s | mail -s "Bitcoin Alert" admin@foo.com
</translation>
</message>
<message>
<source>Warning: -maxtxfee is set very high! Fees this large could be paid on a single transaction.</source>
<translation>警告: -maxtxfee 設定了很高的金額!這可是一次交易就有可能付出的最高手續費。</translation>
</message>
<message>
<source>Warning: Please check that your computer's date and time are correct! If your clock is wrong Bitcoin Core will not work properly.</source>
<translation>警告: 請檢查電腦日期和時間是否正確</translation>
@@ -3059,6 +3135,10 @@ alertnotify=echo %%s | mail -s "Bitcoin Alert" admin@foo.com</translation>
<source>Whitelisted peers cannot be DoS banned and their transactions are always relayed, even if they are already in the mempool, useful e.g. for a gateway</source>
<translation>使</translation>
</message>
<message>
<source>Accept public REST requests (default: %u)</source>
<translation>REST請求 (: %u)</translation>
</message>
<message>
<source>Cannot resolve -whitebind address: '%s'</source>
<translation> -whitebind : '%s'</translation>
@@ -3079,6 +3159,10 @@ alertnotify=echo %%s | mail -s "Bitcoin Alert" admin@foo.com</translation>
<source>Error loading wallet.dat: Wallet requires newer version of Bitcoin Core</source>
<translation> wallet.dat 檔案時發生錯誤: 這個錢包需要新版的位元幣核心</translation>
</message>
<message>
<source>Error reading from database, shutting down.</source>
<translation></translation>
</message>
<message>
<source>Error: Unsupported argument -tor found, use -onion.</source>
<translation>錯誤: 找到不再支援的 -tor -onion </translation>
@@ -3093,7 +3177,11 @@ alertnotify=echo %%s | mail -s "Bitcoin Alert" admin@foo.com</translation>
</message>
<message>
<source>Initialization sanity check failed. Bitcoin Core is shutting down.</source>
<translation></translation>
<translation></translation>
</message>
<message>
<source>Invalid amount for -maxtxfee=&lt;amount&gt;: '%s'</source>
<translation>-maxtxfee=&lt;amount&gt;: '%s' </translation>
</message>
<message>
<source>Invalid amount for -minrelaytxfee=&lt;amount&gt;: '%s'</source>
@@ -3111,10 +3199,6 @@ alertnotify=echo %%s | mail -s "Bitcoin Alert" admin@foo.com</translation>
<source>Invalid netmask specified in -whitelist: '%s'</source>
<translation> -whitelist : '%s'</translation>
</message>
<message>
<source>Keep at most &lt;n&gt; unconnectable blocks in memory (default: %u)</source>
<translation> &lt;n&gt; ( : %u)</translation>
</message>
<message>
<source>Keep at most &lt;n&gt; unconnectable transactions in memory (default: %u)</source>
<translation> &lt;n&gt; (: %u)</translation>
@@ -3127,10 +3211,6 @@ alertnotify=echo %%s | mail -s "Bitcoin Alert" admin@foo.com</translation>
<source>Node relay options:</source>
<translation>:</translation>
</message>
<message>
<source>Print block on startup, if found in block index</source>
<translation></translation>
</message>
<message>
<source>RPC SSL options: (see the Bitcoin Wiki for SSL setup instructions)</source>
<translation>RPC SSL : (SSL Bitcoin Wiki)</translation>
@@ -3139,6 +3219,10 @@ alertnotify=echo %%s | mail -s "Bitcoin Alert" admin@foo.com</translation>
<source>RPC server options:</source>
<translation>RPC :</translation>
</message>
<message>
<source>RPC support for HTTP persistent connections (default: %d)</source>
<translation>RPC HTTP (: %d)</translation>
</message>
<message>
<source>Randomly drop 1 of every &lt;n&gt; network messages</source>
<translation> &lt;n&gt; </translation>
@@ -3179,6 +3263,10 @@ alertnotify=echo %%s | mail -s "Bitcoin Alert" admin@foo.com</translation>
<source>Transaction amounts must be positive</source>
<translation></translation>
</message>
<message>
<source>Transaction too large for fee policy</source>
<translation></translation>
</message>
<message>
<source>Transaction too large</source>
<translation></translation>
@@ -3275,10 +3363,6 @@ alertnotify=echo %%s | mail -s "Bitcoin Alert" admin@foo.com</translation>
<source>How thorough the block verification of -checkblocks is (0-4, default: %u)</source>
<translation>使 -checkblocks (0 4: %u)</translation>
</message>
<message>
<source>If paytxfee is not set, include enough fee so transactions are confirmed on average within n blocks (default: %u)</source>
<translation> paytxfee n (: %u)</translation>
</message>
<message>
<source>Log transaction priority and fee per kB when mining blocks (default: %u)</source>
<translation>(kB)(: %u)</translation>
@@ -3371,10 +3455,6 @@ alertnotify=echo %%s | mail -s "Bitcoin Alert" admin@foo.com</translation>
<source>Prepend debug output with timestamp (default: %u)</source>
<translation>(: %u)</translation>
</message>
<message>
<source>Print block tree on startup (default: %u)</source>
<translation>(: %u)</translation>
</message>
<message>
<source>Relay and mine data carrier transactions (default: %u)</source>
<translation>(: %u)</translation>
@@ -3451,10 +3531,6 @@ alertnotify=echo %%s | mail -s "Bitcoin Alert" admin@foo.com</translation>
<source>Invalid amount for -paytxfee=&lt;amount&gt;: '%s'</source>
<translation> -paytxfee=&lt;&gt; : '%s'</translation>
</message>
<message>
<source>Invalid amount</source>
<translation></translation>
</message>
<message>
<source>Insufficient funds</source>
<translation></translation>
@@ -3487,10 +3563,6 @@ alertnotify=echo %%s | mail -s "Bitcoin Alert" admin@foo.com</translation>
<source>Done loading</source>
<translation></translation>
</message>
<message>
<source>To use the %s option</source>
<translation>使 %s </translation>
</message>
<message>
<source>Error</source>
<translation></translation>