From 9e237be8417c305ca0c10d5405efa65e6d4d5c67 Mon Sep 17 00:00:00 2001 From: Christoph Atteneder Date: Tue, 8 Jan 2019 09:48:36 +0100 Subject: [PATCH] Update translations --- .../i18n/displayStrings_de.properties | 85 +- .../i18n/displayStrings_el.properties | 39 +- .../i18n/displayStrings_es.properties | 89 +- .../i18n/displayStrings_fa.properties | 1131 +++++++++-------- .../i18n/displayStrings_fr.properties | 207 +-- .../i18n/displayStrings_hu.properties | 29 +- .../i18n/displayStrings_pt.properties | 47 +- .../i18n/displayStrings_ro.properties | 27 +- .../i18n/displayStrings_ru.properties | 163 +-- .../i18n/displayStrings_sr.properties | 27 +- .../i18n/displayStrings_th.properties | 509 ++++---- .../i18n/displayStrings_vi.properties | 47 +- .../i18n/displayStrings_zh.properties | 27 +- 13 files changed, 1246 insertions(+), 1181 deletions(-) diff --git a/core/src/main/resources/i18n/displayStrings_de.properties b/core/src/main/resources/i18n/displayStrings_de.properties index 7e77fcfc1b..c757dd4f91 100644 --- a/core/src/main/resources/i18n/displayStrings_de.properties +++ b/core/src/main/resources/i18n/displayStrings_de.properties @@ -82,7 +82,7 @@ shared.tradeId=Handels-ID shared.offerId=Angebots-ID shared.bankName=Bankname shared.acceptedBanks=Akzeptierte Banken -shared.amountMinMax=Betrag (min - max) +shared.amountMinMax=Betrag (min - max) shared.amountHelp=Wurde für ein Angebot ein minimaler und maximaler Betrag gesetzt, können Sie jeden Betrag innerhalb dieses Bereiches handeln. shared.remove=Entfernen shared.goTo=Zu {0} gehen @@ -193,9 +193,9 @@ shared.all=Alle shared.edit=Bearbeiten shared.advancedOptions=Erweiterte Optionen shared.interval=Interval -shared.actions=Actions -shared.buyerUpperCase=Buyer -shared.sellerUpperCase=Seller +shared.actions=Aktionen +shared.buyerUpperCase=Käufer +shared.sellerUpperCase=Verkäufer #################################################################### # UI views @@ -299,6 +299,8 @@ market.trades.tooltip.candle.date=Datum: offerbook.createOffer=Angebot erstellen offerbook.takeOffer=Angebot annehmen +offerbook.takeOfferToBuy=Take offer to buy {0} +offerbook.takeOfferToSell=Take offer to sell {0} offerbook.trader=Händler offerbook.offerersBankId=Bankkennung des Erstellers (BIC/SWIFT): {0} offerbook.offerersBankName=Bankname des Erstellers: {0} @@ -536,7 +538,7 @@ portfolio.pending.step2_buyer.confirmStart.yes=Ja, ich habe die Zahlung begonnen portfolio.pending.step2_seller.waitPayment.headline=Auf Zahlung warten portfolio.pending.step2_seller.f2fInfo.headline=Kontaktinformation des Käufers portfolio.pending.step2_seller.waitPayment.msg=Die Kautionstransaktion hat mindestens eine Blockchain-Bestätigung.\nSie müssen warten bis der BTC-Käufer die {0}-Zahlung beginnt. -portfolio.pending.step2_seller.warn=The BTC buyer still has not done the {0} payment.\nYou need to wait until they have started the payment.\nIf the trade has not been completed on {1} the arbitrator will investigate. +portfolio.pending.step2_seller.warn=Der BTC-Käufer hat die {0}-Zahlung noch nicht getätigt.\nSie müssen warten bis die Zahlung begonnen wurde.\nWenn der Handel nicht bis {1} abgeschlossen wurde, wird der Vermittler diesen untersuchen. portfolio.pending.step2_seller.openForDispute=Der BTC-Käufer hat seine Zahlung noch nicht begonnen!\nDie maximale Handelsdauer wurde überschritten.\nSie können länger warten um dem Handelspartner mehr Zeit zu geben oder den Vermittler kontaktieren, um einen Konflikt zu öffnen. # suppress inspection "UnusedProperty" @@ -565,8 +567,8 @@ portfolio.pending.step3_seller.altcoin.explorer=in ihrem bevorzugten {0} Blockch portfolio.pending.step3_seller.altcoin.wallet=in ihrer {0} Brieftasche portfolio.pending.step3_seller.altcoin={0}Bitte überprüfen Sie mit Ihrem bevorzugten {1}-Blockchain-Explorer, ob die Transaktion zu Ihrer Empfangsadresse\n{2}\nschon genug Blockchain-Bestätigungen hat.\nDer Zahlungsbetrag muss {3} sein\n\nSie können Ihre {4}-Adresse vom Hauptbildschirm kopieren und woanders einfügen, nachdem dieser Dialog geschlossen wurde. portfolio.pending.step3_seller.postal={0}Bitte überprüfen Sie, ob Sie {1} per \"US Postal Money Order\" vom BTC-Käufer erhalten haben.\n\nDie Handels-ID (\"Verwendungszweck\") der Transaktion ist: \"{2}\" -portfolio.pending.step3_seller.bank=Ihr Handelspartner hat den Beginn der {0}-Zahlung bestätigt.\n\nBitte gehen Sie auf Ihre Online-Banking-Website und überprüfen Sie, ob Sie {1} vom BTC-Käufer erhalten haben.\n\nDie Handels-ID (\"Verwendungszweck\") der Transaktion ist: \"{2}\"\n -portfolio.pending.step3_seller.cash=Because the payment is done via Cash Deposit the BTC buyer has to write \"NO REFUND\" on the paper receipt, tear it in 2 parts and send you a photo by email.\n\nTo avoid chargeback risk, only confirm if you received the email and if you are sure the paper receipt is valid.\nIf you are not sure, {0} +portfolio.pending.step3_seller.bank=Ihr Handelspartner hat den Beginn der {0}-Zahlung bestätigt.\n\nBitte gehen Sie auf Ihre Online-Banking-Website und überprüfen Sie, ob Sie {1} vom BTC-Käufer erhalten haben.\n\nDie Handels-ID (\"Verwendungszweck\") der Transaktion ist: \"{2}\"\n\n +portfolio.pending.step3_seller.cash=Da die Zahlung per Cash Deposit ausgeführt wurde, muss der BTC-Käufer \"NO REFUND\" auf die Quittung schreiben, diese in 2 Teile reißen und Ihnen ein Foto per E-Mail schicken.\n\nUm die Gefahr einer Rückbuchung zu vermeiden bestätigen Sie nur, wenn Sie die E-Mail erhalten haben und Sie sicher sind, dass die Quittung gültig ist.\nWenn Sie nicht sicher sind, {0} portfolio.pending.step3_seller.moneyGram=Der Käufer muss Ihnen die Authorisierungs-Nummer und ein Foto der Quittung per E-Mail zusenden.\nDie Quittung muss deutlich Ihren vollständigen Namen, Ihr Land, Ihr Bundesland und den Betrag enthalten. Bitte überprüfen Sie Ihre E-Mail, wenn Sie die Authorisierungs-Nummer erhalten haben.\n\nNach dem Schließen dieses Pop-ups sehen Sie den Namen und die Adresse des BTC-Käufers, um das Geld von MoneyGram abzuholen.\n\nBestätigen Sie den Erhalt erst, nachdem Sie das Geld erfolgreich abgeholt haben! portfolio.pending.step3_seller.westernUnion=Der Käufer muss Ihnen die MTCN (Sendungsnummer) und ein Foto der Quittung per E-Mail zusenden.\nDie Quittung muss deutlich Ihren vollständigen Namen, Ihre Stadt, Ihr Land und den Betrag enthalten. Bitte überprüfen Sie Ihre E-Mail, wenn Sie die MTCN erhalten haben.\n\nNach dem Schließen dieses Pop-ups sehen Sie den Namen und die Adresse des BTC-Käufers, um das Geld von Western Union abzuholen.\n\nBestätigen Sie den Erhalt erst, nachdem Sie das Geld erfolgreich abgeholt haben! portfolio.pending.step3_seller.halCash=Der Käufer muss Ihnen den HalCash-Code als SMS zusenden. Außerdem erhalten Sie eine Nachricht von HalCash mit den erforderlichen Informationen, um EUR an einem HalCash-fähigen Geldautomaten abzuheben.\n\nNachdem Sie das Geld am Geldautomaten abgeholt haben, bestätigen Sie bitte hier den Zahlungseingang! @@ -721,7 +723,7 @@ funds.tx.noTxAvailable=Keine Transaktionen verfügbar funds.tx.revert=Umkehren funds.tx.txSent=Transaktion erfolgreich zu einer neuen Adresse in der lokalen Bisq-Brieftasche gesendet. funds.tx.direction.self=An Sie selbst senden -funds.tx.daoTxFee=Miner fee for DAO tx +funds.tx.daoTxFee=Mining-Gebühr für DAO Tx funds.tx.reimbursementRequestTxFee=Rückerstattungsantrag funds.tx.compensationRequestTxFee=Entlohnungsanfrage @@ -765,9 +767,9 @@ support.buyerOfferer=BTC-Käufer/Ersteller support.sellerOfferer=BTC-Verkäufer/Ersteller support.buyerTaker=BTC-Käufer/Abnehmer support.sellerTaker=BTC-Verkäufer/Abnehmer -support.backgroundInfo=Bisq is not a company, so it handles disputes differently.\n\nIf there are disputes in the trade process (e.g. one trader does not follow the trade protocol) the application will display an \"Open dispute\" button after the trade period is over for contacting the arbitrator.\n\nIf there is an issue with the application, the software will try to detect it and, if possible, display an \"Open support ticket\" button to contact the arbitrator who will forward the issue to the developers.\n\nIf you are having an issue and did not see the \"Open support ticket\" button, you can open a support ticket manually by selecting the trade causing issues under \"Portfolio/Open trades\" and hitting \"alt + o\" or \"option + o\". Please use this method only if you are sure that the software is not working as expected. If you have problems or questions, please review the FAQ on the bisq.network web page or post in the Bisq forum in the Support section. +support.backgroundInfo=Bisq ist keine Firma und betreibt keine Form von Kundendienst.\n\nFalls es während des Handelsprozess (z.B. ein Händler befolgt nicht das Handelsprotokoll) zu Konflikten kommen sollte, wird die Anwendung nach der Handelsdauer eine \"Konflikt öffnen\"-Schaltfläche anzeigen, um den Vermittler zu kontaktieren.\n\nIm Falle von Softwarefehlern oder anderen Problemen, die von der Anwendung entdeckt werden, wird eine \"Support-Ticket öffnen\" Schaltfläche angezeigt, um den Vermittler zu kontaktieren, der die Probleme an die Entwickler weiterleitet.\n\nFalls Sie ein Problem haben, aber die \"Support-Ticket öffnen\"-Schaltfläche nicht angezeigt wird, können Sie manuell ein Support-Ticket öffnen indem Sie den Probleme bereitende Handel unter \"Mappe/Offene Händel\" wählen und die Tastenkombination \"alt + o\" oder \"option + o\" drücken.. Bitte nutzen Sie diese nur, wenn Sie sicher sind, dass sich die Software nicht wie erwartet verhält. Falls Sie nicht wissen wie man Bisq verwendet oder andere Fragen haben, überprüfen Sie bitte die FAQ auf der bisq.io-Website oder erstellen Sie einen Post im Support-Abschnitt des Bisq-Forums. -support.initialInfo=Please note the basic rules for the dispute process:\n1. You need to respond to the arbitrator's requests within 2 days.\n2. The maximum period for a dispute is 14 days.\n3. You need to cooperate with the arbitrator and provide the information they request to make your case.\n4. You accepted the rules outlined in the wiki in the user agreement when you first started the application.\n\nPlease read more about the dispute process in our wiki:\nhttps://github.com/bisq-network/exchange/wiki/Arbitration-system +support.initialInfo=Bitte beachten Sie die grundlegenden Regeln für den Konfliktprozess:\n1. Sie müssen innerhalb von zwei Tagen auf die Anfrage des Vermittlers reagieren.\n2. Die maximale Dauer des Konflikts ist 14 Tage.\n3. Sie müssen befolgen, was der Vermittler von Ihnen verlangt, um Beweise für ihren Fall zu liefern.\n4. Sie haben beim ersten Start dieser Anwendung die Regeln akzeptiert, die im Wiki in den Nutzungsbedingungen zusammengefasst wurden.\n\nErfahren Sie mehr über den Konfliktprozess in unserem Wiki:\nhttps://github.com/bisq-network/exchange/wiki/Arbitration-system support.systemMsg=Systemnachricht: {0} support.youOpenedTicket=Sie haben eine Anfrage für Support geöffnet. support.youOpenedDispute=Sie haben eine Anfrage für einen Konflikt geöffnet.\n\n{0} @@ -836,8 +838,8 @@ settings.net.useCustomNodesRadio=Spezifische Bitcoin-Core-Knoten verwenden settings.net.warn.usePublicNodes=Falls Sie das öffentliche Bitcoin-Netzwerk verwenden sind Sie einem schwerwiegenden Datenschutzproblem ausgesetzt durch das fehlerhafte Design und Implementierung des Bloom Filters in SPV-Brieftaschen wie BitcoinJ (verwendet in Bisq). Jeder verbundene Bitcoin-Core-Knoten könnte herausfinden, dass alle Ihre Brieftaschen-Adressen einer Person gehören.\n\nBitte informieren Sie sich dazu auf folgender Seite: https://bisq.network/blog/privacy-in-bitsquare.\n\nSind Sie sicher, dass Sie öffentliche Knoten verwenden möchten? settings.net.warn.usePublicNodes.useProvided=Nein, bereitgestellte Knoten verwenden settings.net.warn.usePublicNodes.usePublic=Ja, öffentliches Netzwerk verwenden -settings.net.warn.useCustomNodes.B2XWarning=Please be sure that your Bitcoin node is a trusted Bitcoin Core node!\n\nConnecting to nodes which do not follow the Bitcoin Core consensus rules could corrupt your wallet and cause problems in the trade process.\n\nUsers who connect to nodes that violate consensus rules are responsible for any resulting damage. Any resulting disputes will be decided in favor of the other peer. No technical support will be given to users who ignore this warning and protection mechanisms! -settings.net.localhostBtcNodeInfo=(Background information: If you are running a local Bitcoin node (localhost) you can connect exclusively to it.) +settings.net.warn.useCustomNodes.B2XWarning=Bitte stellen Sie sicher, dass Sie sich mit einem vertrauenswürdigen Bitcoin-Core-Knoten verbinden!\n\nWenn Sie sich mit Knoten verbinden, die gegen die Bitcoin Core Konsensus-Regeln verstoßen, kann es zu Problemen in Ihrer Brieftasche und im Verlauf des Handelsprozesses kommen.\n\nBenutzer die sich zu oben genannten Knoten verbinden, sind für den verursachten Schaden verantwortlich. Dadurch entstandene Konflikte werden zugunsten des anderen Teilnehmers entschieden. Benutzer die unsere Warnungen und Sicherheitsmechanismen ignorieren wird keine technische Unterstützung geleistet! +settings.net.localhostBtcNodeInfo=(Hintergrundinformation: Falls Sie einen lokalen Bitcoin-Knoten einsetzen (localhost) werden Sie nur mit diesem verbunden.) settings.net.p2PPeersLabel=Verbundene Peers settings.net.onionAddressColumn=Onion-Adresse settings.net.creationDateColumn=Eingerichtet @@ -860,17 +862,17 @@ settings.net.inbound=eingehend settings.net.outbound=ausgehend settings.net.reSyncSPVChainLabel=SPV-Kette neu synchronisieren settings.net.reSyncSPVChainButton=SPV-Datei löschen und neu synchronisieren -settings.net.reSyncSPVSuccess=The SPV chain file will be deleted on the next startup. You need to restart your application now.\n\nAfter the restart it can take a while to resync with the network and you will only see all transactions once the resync is completed.\n\nPlease restart again after the resync has completed because there are sometimes inconsistencies that result in incorrect balances to display. -settings.net.reSyncSPVAfterRestart=The SPV chain file has been deleted. Please be patient. It can take a while to resync with the network. +settings.net.reSyncSPVSuccess=Die SPV-Kettendatei wird beim nächsten Start gelöscht. Sie müssen Ihre Anwendung jetzt neu starten.\n\nNach dem Neustart kann es eine Weile dauern bis alles mit dem Netzwerk synchronisiert wurde. Sie sehen alle Transaktionen erst, wenn fertig synchronisiert wurde.\n\nBitte starten Sie Ihre Anwendung nach Abschluss der Synchronisation neu, da es manchmal Inkonsistenzen gibt, die zum Anzeigen falscher Guthaben führen. +settings.net.reSyncSPVAfterRestart=Die SPV-Kettendatei wurde gelöscht. Haben Sie bitte Geduld, es kann eine Weile dauern mit dem Netzwerk neu zu synchronisieren. settings.net.reSyncSPVAfterRestartCompleted=Die erneute Synchronisation ist jetzt abgeschlossen. Bitte starten Sie die Anwendung neu. settings.net.reSyncSPVFailed=Konnte SPV-Kettendatei nicht löschen.\nFehler: {0} setting.about.aboutBisq=Über Bisq -setting.about.about=Bisq is open-source software which facilitates the exchange of bitcoin with national currencies (and other cryptocurrencies) through a decentralized peer-to-peer network in a way that strongly protects user privacy. Learn more about Bisq on our project web page. +setting.about.about=Bisq ist ein Open-Source-Projekt und ein dezentrales Netzwerk von Nutzern, die Bitcoins gegen nationale Währungen oder alternative Cryptowährungen auf einem Weg tauschen wollen, der die Privatsphäre schützt. Lernen Sie auf unser Projektwebsite mehr über Bisq. setting.about.web=Bisq-Website setting.about.code=Quellcode setting.about.agpl=AGPL-Lizenz setting.about.support=Bisq unterstützen -setting.about.def=Bisq is not a company—it is a project open to the community. If you want to participate or support Bisq please follow the links below. +setting.about.def=Bisq ist keine Firma, sondern ein Gemeinschaftsprojekt, das offen für Mitwirken ist. Wenn Sie an Bisq mitwirken oder das Projekt unterstützen wollen, folgen Sie bitte den unten stehenden Links. setting.about.contribute=Mitwirken setting.about.donate=Spenden setting.about.providers=Datenanbieter @@ -892,7 +894,7 @@ setting.about.subsystems.val=Netzwerkversion: {0}; P2P-Nachrichtenversion: {1}; account.tab.arbitratorRegistration=Vermittler-Registrierung account.tab.account=Konto account.info.headline=Willkommen in Ihrem Bisq-Konto -account.info.msg=Here you can add trading accounts for national currencies & altcoins, select arbitrators, and create a backup of your wallet & account data.\n\nA new Bitcoin wallet was created the first time you started Bisq.\n\nWe strongly recommend that you write down your Bitcoin wallet seed words (see tab on the top) and consider adding a password before funding. Bitcoin deposits and withdrawals are managed in the \"Funds\" section.\n\nPrivacy & security note: because Bisq is a decentralized exchange, all your data is kept on your computer. There are no servers, so we have no access to your personal info, your funds, or even your IP address. Data such as bank account numbers, altcoin & Bitcoin addresses, etc are only shared with your trading partner to fulfill trades you initiate (in case of a dispute the arbitrator will see the same data as your trading peer). +account.info.msg=Hier können Sie Handelskonten für nationale Währungen & Altcoins konfigurieren, Vermittler auswählen und Backups für Ihre Wallets & Kontodaten erstellen.\n\nEine leere Bitcoinwallet wurde erstellt, als Sie das erste Mal Bisq gestartet haben.\nWir empfehlen, dass Sie Ihre Bitcoin-Wallet-Keimwörter aufschreiben (siehe Schaltfläche links) und sich überlegen ein Passwort hinzuzufügen, bevor Sie einzahlen. Bitcoin-Kautionen und Abhebungen werden unter \"Gelder\" verwaltet.\n\nPrivatsphäre & Sicherheit:\nBisq ist ein dezentralisierte Börse, was bedeutet, dass all Ihre Daten auf ihrem Computer bleiben. Es gibt keine Server und wir haben keinen Zugriff auf Ihre persönlichen Informationen, Ihre Gelder oder selbst Ihre IP Adresse. Daten wie Bankkontonummern, Altcoin- & Bitcoinadressen, etc werden nur mit Ihrem Handelspartner geteilt, um Händel abzuschließen, die Sie gestartet haben (im Falle eines Konflikts wird der Vermittler die selben Daten sehen wie Ihr Handelspartner). account.menu.paymentAccount=Nationale Währungskonten account.menu.altCoinsAccountView=Altcoin-Konten @@ -905,7 +907,7 @@ account.arbitratorRegistration.pubKey=Öffentlicher Schlüssel account.arbitratorRegistration.register=Vermittler registrieren account.arbitratorRegistration.revoke=Registrierung widerrufen -account.arbitratorRegistration.info.msg=Please note that you need to stay available for 15 days after revoking as there might be trades which are using you as arbitrator. The max. allowed trade period is 8 days and the dispute process might take up to 7 days. +account.arbitratorRegistration.info.msg=Beachten Sie bitte, dass Sie nach dem Widerrufen für 15 Tage verfügbar bleiben müssen, da es Händel geben kann, die Sie als Vermittler nutzen. Die maximal erlaubte Handelsdauer ist 8 Tage und der Konfliktprozess kann bis zu 7 Tage dauern. account.arbitratorRegistration.warn.min1Language=Sie müssen wenigstens eine Sprache festlegen.\nWir haben Ihre Standardsprache für Sie hinzugefügt. account.arbitratorRegistration.removedSuccess=Sie haben Ihren Vermittler erfolgreich aus dem P2P-Netzwerk entfernt. account.arbitratorRegistration.removedFailed=Der Vermittler konnte nicht entfernt werden.{0} @@ -924,14 +926,14 @@ account.arbitratorSelection.noLang=Sie können nur Vermittler wählen, die wenig account.arbitratorSelection.minOne=Sie müssen wenigstens einen Vermittler auswählen. account.altcoin.yourAltcoinAccounts=Ihre Altcoin-Konten -account.altcoin.popup.wallet.msg=Please be sure that you follow the requirements for the usage of {0} wallets as described on the {1} web page.\nUsing wallets from centralized exchanges where (a) you don''t control your keys or (b) which don''t use compatible wallet software is risky: it can lead to loss of the traded funds!\nThe arbitrator is not a {2} specialist and cannot help in such cases. +account.altcoin.popup.wallet.msg=Bitte stellen Sie sicher, dass Sie die Anforderungen für die Nutzung von {0}-Brieftaschen befolgen, die auf der {1}-Website beschrieben werden.\nDie Verwendung von Brieftaschen zentraler Börsen, bei denen Sie (a) Ihre Schlüssel nicht selber verwalten, oder (b) das Nutzen inkompatibler Brieftasche-Software können zum Verlust der gehandelten Gelder führen!\nDer Vermittler ist kein {2}-Spezialist und kann Ihnen in einem solchen Fall nicht helfen. account.altcoin.popup.wallet.confirm=Ich verstehe und bestätige, dass ich weiß, welche Brieftasche ich benutzen muss. account.altcoin.popup.xmr.msg=Wenn Sie XMR auf Bisq handeln wollen, stellen Sie bitte sicher, dass Sie die folgenden Bedingungen verstehen und erfüllen:\n\nUm XMR zu senden, brauchen Sie entweder die offizielle Monero GUI Wallet oder die einfache Monero CLI Wallet mit aktivierter store-tx-info (Standard in neuen Versionen).\nStellen Sie bitte sicher, dass Sie auf den Tx-Schlüssel zugreifen können.\nmonero-wallet-cli: (nutzen Sie das get_tx_key Kommando)\nmonero-wallet-gui: (gehen sie zum Verlauf Tab und klicken Sie die (P) Schaltfläche um die Zahlungsbestätigung anzuzeigen)\n\nZusätzlich zum XMR checktx Werkzeug (https://xmr.llcoins.net/checktx.html) kann die Überprüfung auch innerhalb der Brieftasche durchgeführt werden. \nmonero-wallet-cli: verwenden Sie den Befehl (check_tx_key)\nmonero-wallet-gui: gehen Sie zur Erweitert > Beweisen/Prüfen-Seite\n\nIn normalen Blockexplorern ist die Übertragung nicht überprüfbar.\n\nIm Fall eines Konflikts müssen Sie dem Vermittler folgende Daten übergeben:\n- Den privaten Tx-Schlüssel\n- Den Transaktionshash\n- Die öffentliche Adresse des Empfängers\n\nSollten Sie die Daten nicht übergeben können oder eine inkompatible Wallet verwendet haben, werden Sie den Konflikt verlieren. Der XMR Sender ist in der Verantwortung die Übertragung der XMR gegenüber dem Vermittler im Falle eines Konflikts zu beweisen.\n\nEs wird keine Zahlungskennung benötigt, nur eine normale öffentliche Adresse.\n\nFalls Sie sich über diesen Prozess im Unklaren sind, besuchen Sie (https://www.getmonero.org/resources/user-guides/prove-payment.html) oder das Moneroforum (https://forum.getmonero.org) um weitere Informationen zu finden. -account.altcoin.popup.blur.msg=If you want to trade BLUR on Bisq please be sure you understand and fulfill the following requirements:\n\nTo send BLUR you must use the Blur Network CLI or GUI Wallet. \n\nIf you are using the CLI wallet, a transaction hash (tx ID) will be displayed after a transfer is sent. You must save this information. Immediately after sending the transfer, you must use the command 'get_tx_key' to retrieve the transaction private key. If you fail to perform this step, you may not be able to retrieve the key later. \n\nIf you are using the Blur Network GUI Wallet, the transaction private key and transaction ID can be found conveniently in the "History" tab. Immediately after sending, locate the transaction of interest. Click the "?" symbol in the lower-right corner of the box containing the transaction. You must save this information. \n\nIn the event that arbitration is necessary, you must present the following to an arbitrator: 1.) the transaction ID, 2.) the transaction private key, and 3.) the recipient's address. The arbitrator will then verify the BLUR transfer using the Blur Transaction Viewer (https://blur.cash/#tx-viewer).\n\nIf you cannot provide the required information to the arbitrator, you will lose the dispute. In all cases of dispute, the BLUR sender bears 100% of the burden of responsiblity in verifying transactions to an arbitrator. \n\nIf you do not understand these requirements, do not trade on Bisq. First, seek help at the Blur Network Discord (https://discord.gg/dMWaqVW). +account.altcoin.popup.blur.msg=Stellen Sie sicher, die folgenden Bedingungen verstanden zu haben, falls Sie BLUR auf Bisq handeln möchten:\n\nUm BLUR zu senden, müssen sie die Blur CLI Brieftasche (blur-wallte-cli) nutzen.\n\nNachdem dem Senden der Zahlung, wird die Brieftasche den Transaktions-Hash (tx ID). Diese müssen Sie speichern. Sie müssen auch das 'get_tx_key' Kommando ausführen um den privaten Transaktionschlüssel zu erhalten. Sie müssen beides im Falle eines Konflikts haben.\nIn diesem Fall müssen Sie beides mit der öffentlichen Adresse des Empfängers dem Vermittler geben,\nder dann die BLUR Übertragung mi dem Blur Transaction Viewer (https://blur.cash/#tx-viewer) bestätigt.\n\nSollten Sie die benötigten Daten nicht bereitstellen, verlieren Sie den Konflikt.\nDer BLUR Sender ist verantwortlich den BLUR Transfer dem Vermittler, im Falle eines Konflikts, zu beweisen.\n\nSollten Sie diese Bedingungen nicht verstehen, suchen Sie Hilfe im Blur Network Discord (https://discord.gg/dMWaqVW). account.altcoin.popup.ccx.msg=Stellen Sie sicher, die folgenden Bedingungen verstanden zu haben, falls Sie CCX auf Bisq handeln möchten:\n\nUm CCX zu senden, müssen sie eine offizielle Conceal Brieftasche nutzen, Cli oder GUI. Nachdem dem Senden\nder Zahlung, wird die Brieftasche den Transaktions-Hash (ID) und geheimen Schlüssel anzeigen. Sie müssen beides im Falle eines Konflikts haben.\nIn diesem Fall müssen Sie beides mit der öffentlichen Adresse des Empfängers dem Vermittler geben,\nder dann die CCX Übertragung mi dem Conceal Transaction Viewer (https://explorer.conceal.network/txviewer) bestätigt.\nWeil Conceal ein Privatsphären Coin ist, kann ein Blockforscher den Transfer nicht bestätigen.\n\nSollten Sie die benötigten Daten nicht bereitstellen können, verlieren Sie den Konflikt.\nWenn Sie den geheimen Schlüssel nicht sofort nach der CCX Transaktion speichern, kann dieser nicht wiederhergestellt werden.\nSollten Sie diese Bedingungen nicht verstehen, suchen Sie Hilfe im Conceal Discord (http://discord.conceal.network). account.altcoin.popup.drgl.msg=Trading Dragonglass on Bisq requires that you understand and fulfill the following requirements:\n\nBecause of the privacy Dragonglass provides a transaction is not verifyable on the public blockchain. If required you can prove your payment thru use of your TXN-Private-Key.\nThe TXN-Private Key is a one-time key automatically generated for every transaction that can only be accessed from within your DRGL wallet.\nEither by DRGL-wallet GUI (inside transaction details dialog) or by the Dragonglass CLI simplewallet (using command "get_tx_key").\n\nDRGL version 'Oathkeeper' and higher are REQUIRED for both.\n\nIn case of a dispute, you must provide the arbitrator the following data:\n- The TXN-Private key\n- The transaction hash\n- The recipient's public address\n\nVerification of payment can be made using the above data as inputs at \ (http://drgl.info/#check_txn).\n\nIf you cannot provide the above data or if you used an incompatible wallet it would result in losing the dispute case. The Dragonglass sender is responsible to be able to verify the DRGL transfer to the arbitrator in case of a dispute. Use of PaymentID is not required.\n\nIf you are unsure about any part of this process, visit Dragonglass on Discord (http://discord.drgl.info) for help. account.altcoin.popup.ZEC.msg=Wenn Sie {0} verwenden, können Sie nur die transparenten Adressen verwenden (diese beginnen mit t), nicht die z-Adressen (privat), da der Vermittler die Transaktionen mit z-Adressen nicht überprüfen könnte. -account.altcoin.popup.XZC.msg=Wenn Sie {0} verwenden, können Sie nur die transparenten (verfolgbaren) Adressen verwenden, nicht die unverfolgbaren, da der Vermittler Transaktionen mit unverfolgbaren Adressen in einem Blockforscher nicht überprüfen könnte. +account.altcoin.popup.XZC.msg=Wenn Sie {0} verwenden, können Sie nur die transparenten (verfolgbaren) Adressen verwenden, nicht die unverfolgbaren, da der Vermittler Transaktionen mit unverfolgbaren Adressen in einem Blockforscher nicht überprüfen könnte. account.altcoin.popup.bch=Bitcoin Cash und Bitcoin Clashic leiden unter Replay-Protection. Wenn Sie diese Coins benutzen, stellen Sie sicher, dass Sie ausreichend vorsorgen und die Konsequenzen verstehen. Sie können Verluste erleiden, wenn Sie einen Coin senden und ungewollt die gleichen Gelder in einer anderen Blockkette senden. Weil diese "airdrop coins" den gleichen Verlauf wie die Bitcoin Blockkette haben, gibt es auch Sicherheitsrisiken und beachtliche Risiken für die Privatsphären.\n\nLesen Sie bitte mehr über das Thema im Bisq-Forum: https://forum.bisq.io/t/airdrop-coins-information-thread-bch-btg-bchc account.altcoin.popup.btg=Weil Bitcoin Gold den Verlauf wie die Bitcoin Blockkette hat, kommt damit ein gewissen Sicherheitsrisiken und beachtlichen Risiken für die Privatsphäre. Wenn Sie Bitcoin Gold benutzen, stellen Sie sicher, dass Sie ausreichend vorsorgen und die Konsequenzen verstehen.\n\n\nLesen Sie bitte mehr über das Thema im Bisq-Forum: https://forum.bisq.io/t/airdrop-coins-information-thread-bch-btg-bchc @@ -952,14 +954,14 @@ account.password.removePw.button=Passwort entfernen account.password.removePw.headline=Passwortschutz Ihrer Brieftasche entfernen account.password.setPw.button=Passwort festlegen account.password.setPw.headline=Passwortschutz Ihrer Brieftasche einrichten -account.password.info=With password protection you'll need to enter your password at application startup, when withdrawing bitcoin out of your wallet, and when restoring your wallet from seed words. +account.password.info=Mit Passwortschutz müssen Sie Ihr Passwort eingeben, sowohl wenn Sie Bitcoins aus Ihrer Brieftasche abheben, wenn Sie Ihre Brieftasche einsehen oder aus den Seed-Wörtern wiederherstellen wollen, als auch beim Start der Anwendung. account.seed.backup.title=Backup der Seed-Wörter Ihrer Brieftasche erstellen -account.seed.info=Please write down both wallet seed words and the date! You can recover your wallet any time with seed words and the date.\nThe same seed words are used for the BTC and BSQ wallet.\n\nYou should write down the seed words on a sheet of paper. Do not save them on your computer.\n\nPlease note that the seed words are NOT a replacement for a backup.\nYou need to create a backup of the whole application directory from the \"Account/Backup\" screen to recover application state and data.\nImporting seed words is only recommended for emergency cases. The application will not be functional without a proper backup of the database files and keys! +account.seed.info=Bitte schreiben Sie die sowohl Seed-Wörter als auch das Datum auf! Mit diesen Seed-Wörtern und dem Datum können Sie Ihre Brieftasche jederzeit wiederherstellen.\nDie Seed-Wörter werden für die BTC- und BSQ-Brieftasche genutzt.\n\nSchreiben Sie die Seed-Wörter auf ein Blatt Papier schreiben und speichern Sie sie nicht auf Ihrem Computer.\n\nBitte beachten Sie, dass die Seed-Wörter KEIN Ersatz für ein Backup sind.\nSie müssen ein Backup des gesamten Anwendungsverzeichnisses unter \"Konto/Backup\" erstellen, um den ursprünglichen Zustand der Anwendung wiederherstellen zu können.\nDas Importieren der Seed-Wörter wird nur für Notfälle empfohlen. Die Anwendung wird ohne richtiges Backup der Datenbankdateien und Schlüssel nicht funktionieren! account.seed.warn.noPw.msg=Sie haben kein Brieftasche-Passwort festgelegt, was das Anzeigen der Seed-Wörter schützen würde.\n\nMöchten Sie die Seed-Wörter jetzt anzeigen? account.seed.warn.noPw.yes=Ja, und nicht erneut fragen account.seed.enterPw=Geben Sie Ihr Passwort ein um die Seed-Wörter zu sehen -account.seed.restore.info=Please make a backup before applying restore from seed words. Be aware that wallet restore is only for emergency cases and might cause problems with the internal wallet database.\nIt is not a way for applying a backup! Please use a backup from the application data directory for restoring a previous application state. +account.seed.restore.info=Erstellen Sie vor dem Wiederherstellen der Keimwörter eine Sicherung!\nBeachten Sie auch, dass Brieftasche-Wiederherstellung nur für Notfälle ist und Probleme mit der internen Brieftasche-Datenbank verursachen kann.\nEs ist kein Weg ein Backup anzuwenden! Bitte nutzen Sie ein Backup aus dem Anwendungsdatenordner um eine vorherigen Zustand wiederherzustellen. account.seed.restore.ok=Ok, ich verstehe und möchte wiederherstellen @@ -1274,7 +1276,7 @@ dao.bond.bondedRoleType.FORUM_OPERATOR=Betreiber des Forums # suppress inspection "UnusedProperty" dao.bond.bondedRoleType.SEED_NODE_OPERATOR=Seed-Knoten Betreiber # suppress inspection "UnusedProperty" -dao.bond.bondedRoleType.PRICE_NODE_OPERATOR=Preis-Netzknoten Betreiber +dao.bond.bondedRoleType.PRICE_NODE_OPERATOR=Preis-Netzknoten Betreiber # suppress inspection "UnusedProperty" dao.bond.bondedRoleType.BTC_NODE_OPERATOR=BTC Netzknoten Betreiber # suppress inspection "UnusedProperty" @@ -1322,7 +1324,7 @@ dao.assetState.REMOVED_BY_VOTING=Durch Abstimmung entfernt dao.proofOfBurn.header=Nachweis der Verbrennung dao.proofOfBurn.amount=Betrag dao.proofOfBurn.preImage=Vorabbild -dao.proofOfVerbrennen.burn=Verbrennen +dao.proofOfBurn.burn=Verbrennen dao.proofOfBurn.allTxs=Alle Transaktionen zum Nachweis der Verbrennung dao.proofOfBurn.myItems=Meine Transaktionen zum Nachweis der Verbrennung dao.proofOfBurn.date=Datum @@ -1330,7 +1332,7 @@ dao.proofOfBurn.hash=Hash dao.proofOfBurn.txs=Transaktionen dao.proofOfBurn.pubKey=Pubkey dao.proofOfBurn.signature.window.title=Nachricht mit Schlüssel vom Nachweis der Verbrennung unterzeichnen -dao.proofOfBurn.verify.window.title=Verify a message with key from proof or burn transaction +dao.proofOfBurn.verify.window.title=Verifizieren Sie eine Nachricht mit dem Schlüssel der Proof-Of-Burn Transaktion dao.proofOfBurn.copySig=Signatur in Zwischenablage kopieren dao.proofOfBurn.sign=Unterzeichnen dao.proofOfBurn.message=Nachricht @@ -1506,8 +1508,8 @@ dao.wallet.send.send=BSQ-Gelder senden dao.wallet.send.sendBtc=BTC-Gelder senden dao.wallet.send.sendFunds.headline=Abhebeanfrage bestätigen dao.wallet.send.sendFunds.details=Sende: {0}\nAn Empfangsadresse: {1}\nBenötigte Transaktionsgebühr ist: {2} ({3} Satoshis/Byte)\nTransaktionsgröße: {4} Kb\n\nDer Empfänger erhält: {5}\n\nSind Sie sicher, dass Sie diesen Betrag abheben wollen? -dao.wallet.chainHeightSynced=Latest verified block: {0} -dao.wallet.chainHeightSyncing=Awaiting blocks... Verified {0} blocks out of {1} +dao.wallet.chainHeightSynced=Synchronisiert bis Block: {0} +dao.wallet.chainHeightSyncing=Empfange Blöcke... Synchronisiere Block: {0} (letzter Block: {1}) dao.wallet.tx.type=Typ # suppress inspection "UnusedProperty" @@ -1578,13 +1580,13 @@ displayUpdateDownloadWindow.button.downloadLater=Später herunterladen displayUpdateDownloadWindow.button.ignoreDownload=Diese Version ignorieren displayUpdateDownloadWindow.headline=Ein neues Bisq-Update ist verfügbar! displayUpdateDownloadWindow.download.failed.headline=Download fehlgeschlagen -displayUpdateDownloadWindow.download.failed=Download fehlgeschlagen.\nBitte laden sie manuell von https://bisq.network/downloads herunter und überprüfen die Datei -displayUpdateDownloadWindow.installer.failed=Nicht möglich den korrekten Installer zu bestimmen. Bitte laden sie manuell von https://bisq.network/downloads herunter und überprüfen die Datei -displayUpdateDownloadWindow.verify.failed=Überprüfung fehlgeschlagen.\nBitte laden sie manuell von https://bisq.network/downloads herunter und Überprüfen die Datei +displayUpdateDownloadWindow.download.failed=Download fehlgeschlagen.\nBitte laden sie die Datei manuell von https://bisq.network/downloads herunter und überprüfen sie sie. +displayUpdateDownloadWindow.installer.failed=Der gewünschte Installer wurde nicht gefunden. Bitte laden sie die Datei manuell von https://bisq.network/downloads herunter und überprüfen sie sie. +displayUpdateDownloadWindow.verify.failed=Überprüfung fehlgeschlagen.\nBitte laden sie die Datei manuell von https://bisq.network/downloads herunter und überprüfen Sie sie. displayUpdateDownloadWindow.success=Die neue Version wurde erfolgreich heruntergeladen und die Signatur überprüft.\n\nBitte öffnen Sie das Downloadverzeichnis, schließen die Anwendung und installieren die neue Version. displayUpdateDownloadWindow.download.openDir=Downloadverzeichnis öffnen -disputeZusammenfassungWindow.title=Zusammenfassung +disputeSummaryWindow.title=Zusammenfassung disputeSummaryWindow.openDate=Erstellungsdatum des Tickets disputeSummaryWindow.role=Rolle des Händlers disputeSummaryWindow.evidence=Beweis @@ -1659,7 +1661,7 @@ offerDetailsWindow.makersOnion=Onion-Adresse des Erstellers qRCodeWindow.headline=QR-Code qRCodeWindow.msg=Bitte nutzen Sie diesen QR-Code zum Finanzieren Ihrer Bisq-Brieftasche von einer externen Brieftasche. -qRCodeWindow.request=Payment request:\n{0} +qRCodeWindow.request=Zahlungsanfrage:\n{0} selectDepositTxWindow.headline=Kautionstransaktion für Konflikt auswählen selectDepositTxWindow.msg=Die Kautionstransaktion wurde nicht im Handel gespeichert.\nBitte wählen Sie die existierenden MultiSig-Transaktionen aus Ihrer Brieftasche, die die Kautionstransaktion für den fehlgeschlagenen Handel war.\n\nSie können die korrekte Transaktion finden, indem Sie das Handelsdetail-Fenster öffnen (klicken Sie auf die Handels-ID in der Liste) und dem Transaktions-Output der Handelsgebührenzahlung zur nächsten Transaktion folgen, wo Sie die MultiSig-Kautionstransaktion sehen (die Adresse beginnt mit einer 3). Diese Transaktions-ID sollte in der dargestellten Liste auftauchen. Sobald Sie die korrekte Transaktion gefunden haben, wählen Sie diese Transaktion hier aus und fahren fort.\n\nEntschuldigen Sie die Unannehmlichkeiten, aber dieser Fehler sollte sehr selten auftreten und wir werden in Zukunft versuchen bessere Wege zu finden, ihn zu lösen. @@ -1746,7 +1748,7 @@ popup.headline.error=Fehler popup.doNotShowAgain=Nicht erneut anzeigen popup.reportError.log=Protokolldatei öffnen popup.reportError.gitHub=Auf GitHub-Issue-Tracker melden -popup.reportError={0}\n\nTo help us to improve the software please report the bug on our issue tracker on GitHub (https://github.com/bisq-network/bisq-desktop/issues).\nThe error message will be copied to the clipboard when you click a button below.\nIt will make debugging easier if you can attach the bisq.log file as well. +popup.reportError={0}\n\nUm uns bei der Verbesserung der Software zu helfen, erstellen Sie bitte einen Fehlerbericht auf unserem Issue-Tracker auf GitHub (https://github.com/bisq-network/bisq/issues).\nDie Fehlermeldung wird in die Zwischenablage kopiert, wenn Sie auf die Schaltflächen unten klicken.\nEs wird das Debuggen einfacher machen, wenn Sie die bisq.log Datei anfügen. popup.error.tryRestart=Versuchen Sie bitte Ihre Anwendung neu zu starten und überprüfen Sie Ihre Netzwerkverbindung um zu sehen, ob Sie das Problem beheben können. popup.error.takeOfferRequestFailed=Es ist ein Fehler aufgetreten, als jemand versuchte eins Ihrer Angebote anzunehmen:\n{0} @@ -1781,9 +1783,9 @@ popup.warning.lockedUpFunds=Sie haben eingesperrte Gelder von einem fehlgeschlag popup.warning.nodeBanned=Einer der {0} Knoten wurde gebannt. Bitte starten Sie die Anwendung neu, um sicher zu sein, nicht mit gebannten Knoten verbunden zu werden. popup.warning.priceRelay=Preisrelais -popup.warning.Seed=Seed +popup.warning.seed=Seed -popup.info.securityDepositInfo=To ensure both traders follow the trade protocol, both traders need to pay a security deposit.\n\nThis deposit is kept in your trade wallet until your trade has been successfully completed, and then it's refunded to you.\n\nPlease note: if you're creating a new offer, Bisq needs to be running for another trader to take it. To keep your offers online, keep Bisq running and make sure this computer remains online too (i.e., make sure it doesn't switch to standby mode...monitor standby is fine). +popup.info.securityDepositInfo=Um sicherzustellen, dass beide Händler dem Handelsprotokoll folgen, müssen diese eine Kaution zahlen.\n\nDie Kaution bleibt in Ihrer lokalen Brieftasche, bis das Angebot von einem anderen Händler angenommen wurde.\nSie wird Ihnen zurückerstattet, nachdem der Handel erfolgreich abgeschlossen wurde.\n\nBitte beachten Sie, dass Sie die Anwendung laufen lassen müssen, wenn Sie ein offenes Angebot haben.\nWenn ein anderer Händler Ihr Angebot annehmen möchte ist es notwendig, dass Ihre Anwendung online ist und reagieren kann.\nStellen Sie sicher, dass Sie den Ruhezustand deaktiviert haben, da dieser Ihren Client vom Netzwerk trennen würde (Der Ruhezustand des Monitors ist kein Problem). popup.info.cashDepositInfo=Stellen Sie sicher, dass eine Bank-Filiale in Ihrer Nähe befindet, um die Bargeld Kaution zu zahlen.\nDie Bankkennung (BIC/SWIFT) der Bank des Verkäufers ist: {0}. popup.info.cashDepositInfo.confirm=Ich bestätige, dass ich die Kaution zahlen kann @@ -1805,6 +1807,9 @@ popup.attention.forTradeWithId=Der Handel mit der ID {0} benötigt Ihre Aufmerks popup.roundedFiatValues.headline=Neues Privatsphären Feature: Gerundete fiat Beträge popup.roundedFiatValues.msg=Um die Privatsphäre Ihres Handels zu erhöhen, wurde der {0} Betrag gerundet.\n\nAbhängig von der Version des Clients, werden Sie Beträge mit Nachkommastellen oder gerundet erhalten.\n\nBeide Beträge erfüllen von nun an das Handelsprotokoll.\n\nBeachten Sie auch, dass die BTC Beträge automatisch angepasst werden, um dem gerundeten fiat Betrag so genau wie möglich übereinzustimmen. +popup.info.multiplePaymentAccounts.headline=Multiple payment accounts available +popup.info.multiplePaymentAccounts.msg=You have multiple payment accounts available for this offer. Please make sure you've picked the right one. + #################################################################### # Notifications @@ -2059,7 +2064,7 @@ payment.national.account.id.AR=CBU Nummer #new payment.altcoin.address.dyn={0} Adresse -payment.altcoin.receiver.address=Receiver's altcoin address +payment.altcoin.receiver.address=Altcoin Adresse des Empfängers payment.accountNr=Kontonummer payment.emailOrMobile=E-Mail oder Telefonnr. payment.useCustomAccountName=Spezifischen Kontonamen nutzen @@ -2085,7 +2090,7 @@ payment.clearXchange.info=\tStellen Sie bitte sicher, dass Sie die Voraussetzung payment.moneyGram.info=Wenn MoneyGram verwendet wird, muss der BTC Käufer die MoneyGram und ein Foto der Quittung per E-Mail an den BTC-Verkäufer senden. Die Quittung muss den vollständigen Namen, das Land, das Bundesland des Verkäufers und den Betrag deutlich zeigen. Der Käufer bekommt die E-Mail-Adresse des Verkäufers im Handelsprozess angezeigt. payment.westernUnion.info=Wenn Western Union verwendet wird, muss der BTC Käufer die MTCN (Tracking-Nummer) und ein Foto der Quittung per E-Mail an den BTC-Verkäufer senden. Die Quittung muss den vollständigen Namen, die Stadt, das Land des Verkäufers und den Betrag deutlich zeigen. Der Käufer bekommt die E-Mail-Adresse des Verkäufers im Handelsprozess angezeigt. -payment.halCash.info=Bei Verwendung von HalCash muss der BTC-Käufer dem BTC-Verkäufer den HalCash-Code per SMS vom Mobiltelefon senden.\n\nBitte achten Sie darauf, dass Sie den maximalen Betrag, den Sie bei Ihrer Bank mit HalCash versenden dürfen, nicht überschreiten. Der Mindestbetrag pro Auszahlung beträgt 10 EUR und der Höchstbetrag 600 EUR. Bei wiederholten Abhebungen sind es 3000 EUR pro Empfänger pro Tag und 6000 EUR pro Empfänger pro Monat. Bitte überprüfen Sie diese Limits bei Ihrer Bank, um sicherzustellen, dass sie die gleichen Limits wie hier angegeben verwenden.\n\nDer Auszahlungsbetrag muss ein Vielfaches von 10 EUR betragen, da Sie keine anderen Beträge an einem Geldautomaten abheben können. Die Benutzeroberfläche beim Erstellen und Annehmen eines Angebots passt den BTC-Betrag so an, dass der EUR-Betrag korrekt ist. Sie können keinen marktbasierten Preis verwenden, da sich der EUR-Betrag bei sich ändernden Preisen ändern würde.\n\n\nIm Streitfall muss der BTC-Käufer den Nachweis erbringen, dass er die EUR geschickt hat. +payment.halCash.info=Bei Verwendung von HalCash muss der BTC-Käufer dem BTC-Verkäufer den HalCash-Code per SMS vom Mobiltelefon senden.\n\nBitte achten Sie darauf, dass Sie den maximalen Betrag, den Sie bei Ihrer Bank mit HalCash versenden dürfen, nicht überschreiten. Der Mindestbetrag pro Auszahlung beträgt 10 EUR und der Höchstbetrag 600 EUR. Bei wiederholten Abhebungen sind es 3000 EUR pro Empfänger pro Tag und 6000 EUR pro Empfänger pro Monat. Bitte überprüfen Sie diese Limits bei Ihrer Bank, um sicherzustellen, dass sie die gleichen Limits wie hier angegeben verwenden.\n\nDer Auszahlungsbetrag muss ein Vielfaches von 10 EUR betragen, da Sie keine anderen Beträge an einem Geldautomaten abheben können. Die Benutzeroberfläche beim Erstellen und Annehmen eines Angebots passt den BTC-Betrag so an, dass der EUR-Betrag korrekt ist. Sie können keinen marktbasierten Preis verwenden, da sich der EUR-Betrag bei sich ändernden Preisen ändern würde.\n\nIm Streitfall muss der BTC-Käufer den Nachweis erbringen, dass er die EUR geschickt hat. payment.limits.info=Beachten Sie bitte, dass alle Banküberweisungen ein gewisses Rückbuchungsrisiko mitbringen.\n\nUm diese Risiko zu minimieren, setzt Bisq vor-Handel Grenzen basierend auf zwei Faktoren:\n\n1. Das erwartete Rückbuchungsrisiko für die genutzte Zahlungsmethode\n2. Das Alter des Kontos für diese Zahlungsmethode\n\nDas Konto, das Sie jetzt erstellen, ist neu und sein Alter ist null. So wie Ihr Konto über zwei Monate altert, wächst auch Ihre vor-Handel Grenze:\n\n● Während des 1sten Monats, ist Ihre vor-Handel Grenze {0}\n● Während des 2ten Monats, ist Ihre vor-Handel Grenze {1}\n● Nach dem 2ten Monat, ist Ihre vor-Handel Grenze {2}\n\nBeachten Sie bitte, dass es keine Grenze, wie oft Sie handeln können. payment.cashDeposit.info=Bitte bestätigen Sie, dass Ihre Bank Bareinzahlungen in Konten von anderen Personen erlaubt. Zum Beispiel werden diese Einzahlungen bei der Bank of America und Wells Fargo nicht mehr erlaubt. @@ -2280,4 +2285,4 @@ validation.amountBelowDust=Beträge unter dem Dust-Limit von {0} sind nicht erl validation.length=Die Länge muss zwischen {0} und {1} sein validation.pattern=Die Eingabe muss im Format {0} sein validation.noHexString=Die Eingabe ist nicht im HEX-Format. -validation.advancedCash.invalidFormat=Must be a valid email or wallet id of format: X000000000000 +validation.advancedCash.invalidFormat=Gültige E-Mail-Adresse oder Brieftaschen ID vom Format "X000000000000" benötigt diff --git a/core/src/main/resources/i18n/displayStrings_el.properties b/core/src/main/resources/i18n/displayStrings_el.properties index a0d271dafb..0201fe7aad 100644 --- a/core/src/main/resources/i18n/displayStrings_el.properties +++ b/core/src/main/resources/i18n/displayStrings_el.properties @@ -221,7 +221,7 @@ mainView.marketPriceWithProvider.label=Market price by {0} mainView.marketPrice.bisqInternalPrice=Τιμή τελευταίας συναλλαγής Bisq mainView.marketPrice.tooltip.bisqInternalPrice=Δεν υπάρχει διαθέσιμη τιμή αγοράς από εξωτερική πηγή.\nΗ εμφανιζόμενη τιμή είναι η τελευταία τιμή συναλλαγής αυτού του νομίσματος στο Bisq. mainView.marketPrice.tooltip=Η τιμή αγοράς παρέχεται από το {0}{1}\nΤελευταία ενημέρωση: {2}\nΚόμβος URL παρόχου τιμής: {3} -mainView.marketPrice.tooltip.altcoinExtra=Εάν το altcoin δεν διατίθεται στο Poloniex, χρησιμοποιούμε το https://coinmarketcap.com +mainView.marketPrice.tooltip.altcoinExtra=Εάν το altcoin δεν διατίθεται στο Poloniex, χρησιμοποιούμε το https://coinmarketcap.com mainView.balance.available=Διαθέσιμο υπόλοιπο mainView.balance.reserved=Δεσμευμένα σε προσφορές mainView.balance.locked=Κλειδωμένα σε συναλλαγές @@ -299,6 +299,8 @@ market.trades.tooltip.candle.date=Ημερομηνία: offerbook.createOffer=Δημιουργία προσφοράς offerbook.takeOffer=Αποδοχή προσφοράς +offerbook.takeOfferToBuy=Take offer to buy {0} +offerbook.takeOfferToSell=Take offer to sell {0} offerbook.trader=Συναλλασσόμενος offerbook.offerersBankId=Ταυτότητα τράπεζας Maker (BIC/SWIFT): {0} offerbook.offerersBankName=Όνομα τράπεζας Maker: {0} @@ -365,7 +367,7 @@ createOffer.fundsBox.title=Χρηματοδότησε την προσφορά σ createOffer.fundsBox.offerFee=Προμήθεια συναλλαγής createOffer.fundsBox.networkFee=Mining fee createOffer.fundsBox.placeOfferSpinnerInfo=Κοινοποίηση προσφοράς σε εξέλιξη... -createOffer.fundsBox.paymentLabel=Συναλλαγή Bisq με ταυτότητα {0} +createOffer.fundsBox.paymentLabel=Συναλλαγή Bisq με ταυτότητα {0} createOffer.fundsBox.fundsStructure=({0} ποσό εγγύησης, {1} προμήθεια συναλλαγής, {2} αμοιβή εξόρυξης) createOffer.success.headline=Η προσφορά σου έχει κοινοποιηθεί createOffer.success.info=Μπορείς να διαχειριστείς τις ανοιχτές προσφορές σου στο \"Χαρτοφυλάκιο/Οι τρέχουσες προσφορές μου\". @@ -424,7 +426,7 @@ takeOffer.fundsBox.tradeAmount=Amount to sell takeOffer.fundsBox.offerFee=Προμήθεια συναλλαγής takeOffer.fundsBox.networkFee=Total mining fees takeOffer.fundsBox.takeOfferSpinnerInfo=Αποδοχή προσφοράς σε εξέλιξη... -takeOffer.fundsBox.paymentLabel=Συναλλαγή Bisq με ταυτότητα {0} +takeOffer.fundsBox.paymentLabel=Συναλλαγή Bisq με ταυτότητα {0} takeOffer.fundsBox.fundsStructure=({0} ποσό εγγύησης, {1} προμήθεια συναλλαγής, {2} αμοιβή εξόρυξης) takeOffer.success.headline=Αποδέχτηκες επιτυχώς μία προσφορά. takeOffer.success.info=Μπορείς να δεις την κατάσταση της συναλλαγής στο \"Χαρτοφυλάκιο/Τρέχουσες συναλλαγές\". @@ -553,19 +555,19 @@ message.state.ACKNOWLEDGED=Ο συναλλασσόμενος επιβεβαίω message.state.FAILED=Αποτυχία αποστολής μηνύματος portfolio.pending.step3_buyer.wait.headline=Αναμονή για την επιβεβαίωση της πληρωμής από τον πωλητή BTC -portfolio.pending.step3_buyer.wait.info=Αναμονή για την επιβεβαίωση της απόδειξης της πληρωμής {0} από τον πωλητή BTC. +portfolio.pending.step3_buyer.wait.info=Αναμονή για την επιβεβαίωση της απόδειξης της πληρωμής {0} από τον πωλητή BTC. portfolio.pending.step3_buyer.wait.msgStateInfo.label=Payment started message status portfolio.pending.step3_buyer.warn.part1a=στο blockchain {0} portfolio.pending.step3_buyer.warn.part1b=στον πάροχο υπηρεσιών πληρωμής (π.χ. τράπεζα) portfolio.pending.step3_buyer.warn.part2=Ο πωλητής BTC δεν έχει επιβεβαιώσει ακόμα την πληρωμή σου!\nΈλεγξε {0} αν υπήρξε επιτυχής πληρωμή.\nΑν ο πωλητής BTC δεν επιβεβαιώσει την απόδειξη της πληρωμής σου μέχρι την {1}, η συναλλαγή θα διερευνηθεί από τον διαμεσολαβητή. portfolio.pending.step3_buyer.openForDispute=Ο πωλητής BTC δεν επιβεβαίωσε την πληρωμή σου!\nΗ μέγιστη χρονική περίοδος συναλλαγής παρήλθε.\nΜπορείς να περιμένεις περισσότερο και να δώσεις επιπλέον χρόνο στον έτερο συναλλασσόμενο ή μπορείς να επικοινωνήσεις με τον διαμεσολαβητή και να ξεκινήσεις επίλυση διένεξης. # suppress inspection "TrailingSpacesInProperty" -portfolio.pending.step3_seller.part=Ο συναλλασσόμενος επιβεβαίωσε πως ξεκίνησε την πληρωμή {0}.\n\n +portfolio.pending.step3_seller.part=Your trading partner has confirmed that they have initiated the {0} payment.\n\n portfolio.pending.step3_seller.altcoin.explorer=on your favorite {0} blockchain explorer portfolio.pending.step3_seller.altcoin.wallet=at your {0} wallet portfolio.pending.step3_seller.altcoin={0}Please check {1} if the transaction to your receiving address\n{2}\nhas already sufficient blockchain confirmations.\nThe payment amount has to be {3}\n\nYou can copy & paste your {4} address from the main screen after closing that popup. portfolio.pending.step3_seller.postal={0}Έλεγξε αν παρέλαβες {1} μέσω \"US Postal Money Order\" από τον αγοραστή BTC.\n\nΗ ταυτότητα (ID) συναλλαγής (πεδίο \"reason for payment\") είναι: \"{2}\" -portfolio.pending.step3_seller.bank=Ο έτερος συναλλασσόμενος επιβεβαίωσε την έναρξη της πληρωμής {0}.\n\nΣυνδέσου στον e-banking λογαριασμό σου και έλεγξε αν έχεις παραλάβει {1} από τον αγοραστή BTC.\n\nΗ ταυτότητα συναλλαγής (πεδίο \"reason for payment\") στη συναλλαγή είναι: \"{2}\"\n +portfolio.pending.step3_seller.bank=Your trading partner has confirmed that they have initiated the {0} payment.\n\nPlease go to your online banking web page and check if you have received {1} from the BTC buyer.\n\nThe trade ID (\"reason for payment\" text) of the transaction is: \"{2}\"\n\n portfolio.pending.step3_seller.cash=Because the payment is done via Cash Deposit the BTC buyer has to write \"NO REFUND\" on the paper receipt, tear it in 2 parts and send you a photo by email.\n\nTo avoid chargeback risk, only confirm if you received the email and if you are sure the paper receipt is valid.\nIf you are not sure, {0} portfolio.pending.step3_seller.moneyGram=Ο αγοραστής θα πρέπει να σου στείλει τον αριθμό Έγκρισης (Authorisation) και μία φωτογραφία της απόδειξης μέσω email.\nΣτην απόδειξη θα πρέπει να διακρίνεται καθαρά το πλήρες όνομά σου, η χώρα, η πόλη και το ποσό. Έλεγξε αν στα email σου έχεις λάβει τον αριθμό Έγκρισης.\n\nΑφού κλείσεις αυτό το αναδυόμενο παράθυρο θα δεις το όνομα και τη διεύθυνση του αγοραστή BTC, ώστε να λάβεις τα χρήματα από την MoneyGram.\n\nΕπιβεβαίωσε την απόδειξη μονάχα αφού εισπράξεις τα χρήματα! portfolio.pending.step3_seller.westernUnion=Ο αγοραστής θα πρέπει να σου στείλει τον αριθμό MTCN (αριθμός εντοπισμού) και μία φωτογραφία της απόδειξης μέσω email.\nΣτην απόδειξη θα πρέπει να διακρίνεται καθαρά το πλήρες όνομά σου, η πόλη, η χώρα και το ποσό. Έλεγξε αν στα email σου έχεις λάβει το MTCN.\n\nΑφού κλείσεις αυτό το αναδυόμενο παράθυρο θα δεις το όνομα και τη διεύθυνση του αγοραστή BTC, ώστε να λάβεις τα χρήματα από την Western Union.\n\nΕπιβεβαίωσε την απόδειξη μονάχα αφού εισπράξεις τα χρήματα! @@ -685,7 +687,7 @@ funds.withdrawal.feeExcluded=Το ποσό δεν περιλαμβάνει τη funds.withdrawal.feeIncluded=Το ποσό περιλαμβάνει την αμοιβή εξόρυξης funds.withdrawal.fromLabel=Withdraw from address funds.withdrawal.toLabel=Withdraw to address -funds.withdrawal.withdrawButton=Επιλέχθηκε η ανάληψη +funds.withdrawal.withdrawButton=Επιλέχθηκε η ανάληψη funds.withdrawal.noFundsAvailable=Δεν υπάρχουν διαθέσιμα κεφάλαια προς ανάληψη funds.withdrawal.confirmWithdrawalRequest=Επιβεβαίωση αίτησης ανάληψης funds.withdrawal.withdrawMultipleAddresses=Ανάληψη από πολλαπλές διευθύνσεις ({0}) @@ -859,7 +861,7 @@ settings.net.peer=Peer settings.net.inbound=εισερχόμενα settings.net.outbound=εξερχόμενα settings.net.reSyncSPVChainLabel=Επανασυγχρονισμός αλυσίδας SPV -settings.net.reSyncSPVChainButton=Διάγραψε το αρχείο SPV και επανασυγχρονίσου +settings.net.reSyncSPVChainButton=Διάγραψε το αρχείο SPV και επανασυγχρονίσου settings.net.reSyncSPVSuccess=The SPV chain file will be deleted on the next startup. You need to restart your application now.\n\nAfter the restart it can take a while to resync with the network and you will only see all transactions once the resync is completed.\n\nPlease restart again after the resync has completed because there are sometimes inconsistencies that result in incorrect balances to display. settings.net.reSyncSPVAfterRestart=The SPV chain file has been deleted. Please be patient. It can take a while to resync with the network. settings.net.reSyncSPVAfterRestartCompleted=Ο επανασυγχρονισμός ολοκληρώθηκε. Επανεκκίνησε την εφαρμογή. @@ -926,10 +928,10 @@ account.arbitratorSelection.minOne=Πρέπει να επιλέξεις τουλ account.altcoin.yourAltcoinAccounts=Your altcoin accounts account.altcoin.popup.wallet.msg=Please be sure that you follow the requirements for the usage of {0} wallets as described on the {1} web page.\nUsing wallets from centralized exchanges where (a) you don''t control your keys or (b) which don''t use compatible wallet software is risky: it can lead to loss of the traded funds!\nThe arbitrator is not a {2} specialist and cannot help in such cases. account.altcoin.popup.wallet.confirm=Κατανοώ και επιβεβαιώνω πως γνωρίζω ποιο πορτοφόλι πρέπει να χρησιμοποιήσω. -account.altcoin.popup.xmr.msg=If you want to trade XMR on Bisq please be sure you understand and fulfill the following requirements:\n\nFor sending XMR you need to use either the official Monero GUI wallet or Monero CLI wallet with the store-tx-info flag enabled (default in new versions). Please be sure you can access the tx key as that would be required in case of a dispute.\nmonero-wallet-cli (use the command get_tx_key)\nmonero-wallet-gui (go to history tab and click on the (P) button for payment proof)\n\nIn addition to XMR checktx tool (https://xmr.llcoins.net/checktx.html) verification can also be accomplished in-wallet.\nmonero-wallet-cli : using command (check_tx_key).\nmonero-wallet-gui : on the Advanced > Prove/Check page.\nAt normal block explorers the transfer is not verifiable.\n\nYou need to provide the arbitrator the following data in case of a dispute:\n- The tx private key\n- The transaction hash\n- The recipient's public address\n\nIf you cannot provide the above data or if you used an incompatible wallet it would result in losing the dispute case. The XMR sender is responsible to be able to verify the XMR transfer to the arbitrator in case of a dispute.\n\nThere is no payment ID required, just the normal public address.\nIf you are not sure about that process visit (https://www.getmonero.org/resources/user-guides/prove-payment.html) or the Monero forum (https://forum.getmonero.org) to find more information. -account.altcoin.popup.blur.msg=If you want to trade BLUR on Bisq please be sure you understand and fulfill the following requirements:\n\nTo send BLUR you must use the Blur Network CLI or GUI Wallet. \n\nIf you are using the CLI wallet, a transaction hash (tx ID) will be displayed after a transfer is sent. You must save this information. Immediately after sending the transfer, you must use the command 'get_tx_key' to retrieve the transaction private key. If you fail to perform this step, you may not be able to retrieve the key later. \n\nIf you are using the Blur Network GUI Wallet, the transaction private key and transaction ID can be found conveniently in the "History" tab. Immediately after sending, locate the transaction of interest. Click the "?" symbol in the lower-right corner of the box containing the transaction. You must save this information. \n\nIn the event that arbitration is necessary, you must present the following to an arbitrator: 1.) the transaction ID, 2.) the transaction private key, and 3.) the recipient's address. The arbitrator will then verify the BLUR transfer using the Blur Transaction Viewer (https://blur.cash/#tx-viewer).\n\nIf you cannot provide the required information to the arbitrator, you will lose the dispute. In all cases of dispute, the BLUR sender bears 100% of the burden of responsiblity in verifying transactions to an arbitrator. \n\nIf you do not understand these requirements, do not trade on Bisq. First, seek help at the Blur Network Discord (https://discord.gg/dMWaqVW). -account.altcoin.popup.ccx.msg=If you want to trade CCX on Bisq please be sure you understand the following requirements:\n\nTo send CCX you must use an official Conceal wallet, either CLI or GUI. After sending a transfer payment, the wallets\ndisplay the transaction secret key. You must save it along with the transaction hash (ID) and the recipient's public\naddress in case arbitration is necessary. In such a case, you must give all three to the arbitrator, who will then\nverify the CCX transfer using the Conceal Transaction Viewer (https://explorer.conceal.network/txviewer).\nBecause Conceal is a privacy coin, block explorers cannot verify transfers.\n\nIf you cannot provide the required data to the arbitrator, you will lose the dispute case.\nIf you do not save the transaction secret key immediately after transferring CCX, it cannot be recovered later.\nIf you do not understand these requirements, seek help at the Conceal discord (http://discord.conceal.network). -account.altcoin.popup.drgl.msg=Trading Dragonglass on Bisq requires that you understand and fulfill the following requirements:\n\nBecause of the privacy Dragonglass provides a transaction is not verifyable on the public blockchain. If required you can prove your payment thru use of your TXN-Private-Key.\nThe TXN-Private Key is a one-time key automatically generated for every transaction that can only be accessed from within your DRGL wallet.\nEither by DRGL-wallet GUI (inside transaction details dialog) or by the Dragonglass CLI simplewallet (using command "get_tx_key").\n\nDRGL version 'Oathkeeper' and higher are REQUIRED for both.\n\nIn case of a dispute, you must provide the arbitrator the following data:\n- The TXN-Private key\n- The transaction hash\n- The recipient's public address\n\nVerification of payment can be made using the above data as inputs at \ (http://drgl.info/#check_txn).\n\nIf you cannot provide the above data or if you used an incompatible wallet it would result in losing the dispute case. The Dragonglass sender is responsible to be able to verify the DRGL transfer to the arbitrator in case of a dispute. Use of PaymentID is not required.\n\nIf you are unsure about any part of this process, visit Dragonglass on Discord (http://discord.drgl.info) for help. +account.altcoin.popup.xmr.msg=Trading XMR on Bisq requires that you understand and fulfill the following requirements:\n\nFor sending XMR, you need to use either the official Monero GUI wallet or Monero CLI wallet with the store-tx-info flag enabled (default in new versions). Please be sure you can access the tx key as that would be required in case of a dispute.\nmonero-wallet-cli (use the command get_tx_key)\nmonero-wallet-gui (go to history tab and click on the (P) button for payment proof)\n\nIn addition to XMR checktx tool (https://xmr.llcoins.net/checktx.html) verification can also be accomplished in-wallet.\nmonero-wallet-cli : using command (check_tx_key).\nmonero-wallet-gui : on the Advanced > Prove/Check page.\nAt normal block explorers the transfer is not verifiable.\n\nYou need to provide the arbitrator the following data in case of a dispute:\n- The tx private key\n- The transaction hash\n- The recipient's public address\n\nFailure to provide the above data, or if you used an incompatible wallet, will result in losing the dispute case. The XMR sender is responsible for providing verification of the XMR transfer to the arbitrator in case of a dispute.\n\nThere is no payment ID required, just the normal public address.\nIf you are not sure about that process visit (https://www.getmonero.org/resources/user-guides/prove-payment.html) or the Monero forum (https://forum.getmonero.org) to find more information. +account.altcoin.popup.blur.msg=Trading BLUR on Bisq requires that you understand and fulfill the following requirements:\n\nTo send BLUR you must use the Blur Network CLI or GUI Wallet. \n\nIf you are using the CLI wallet, a transaction hash (tx ID) will be displayed after a transfer is sent. You must save this information. Immediately after sending the transfer, you must use the command 'get_tx_key' to retrieve the transaction private key. If you fail to perform this step, you may not be able to retrieve the key later. \n\nIf you are using the Blur Network GUI Wallet, the transaction private key and transaction ID can be found conveniently in the "History" tab. Immediately after sending, locate the transaction of interest. Click the "?" symbol in the lower-right corner of the box containing the transaction. You must save this information. \n\nIn the event that arbitration is necessary, you must present the following to an arbitrator: 1.) the transaction ID, 2.) the transaction private key, and 3.) the recipient's address. The arbitrator will then verify the BLUR transfer using the Blur Transaction Viewer (https://blur.cash/#tx-viewer).\n\nFailure to provide the required information to the arbitrator will result in losing the dispute case. In all cases of dispute, the BLUR sender bears 100% of the burden of responsibility in verifying transactions to an arbitrator. \n\nIf you do not understand these requirements, do not trade on Bisq. First, seek help at the Blur Network Discord (https://discord.gg/dMWaqVW). +account.altcoin.popup.ccx.msg=Trading CCX on Bisq requires that you understand the following requirements:\n\nTo send CCX you must use an official Conceal wallet, either CLI or GUI. After sending a transfer payment, the wallets\ndisplay the transaction secret key. You must save it along with the transaction hash (ID) and the recipient's public\naddress in case arbitration is necessary. In such a case, you must give all three to the arbitrator, who will then\nverify the CCX transfer using the Conceal Transaction Viewer (https://explorer.conceal.network/txviewer).\nBecause Conceal is a privacy coin, block explorers cannot verify transfers.\n\nFailure to provide the required data to the arbitrator will result in losing the dispute case.\nIf you do not save the transaction secret key immediately after transferring CCX, it cannot be recovered later.\nIf you do not understand these requirements, seek help at the Conceal discord (http://discord.conceal.network). +account.altcoin.popup.drgl.msg=Trading Dragonglass on Bisq requires that you understand and fulfill the following requirements:\n\nBecause of the privacy Dragonglass provides, a transaction is not verifiable on the public blockchain. If required, you can prove your payment through the use of your TXN-Private-Key.\nThe TXN-Private Key is a one-time key automatically generated for every transaction that can only be accessed from within your DRGL wallet.\nEither by DRGL-wallet GUI (inside transaction details dialog) or by the Dragonglass CLI simplewallet (using command "get_tx_key").\n\nDRGL version 'Oathkeeper' and higher are REQUIRED for both.\n\nIn case of a dispute, you must provide the arbitrator the following data:\n- The TXN-Private key\n- The transaction hash\n- The recipient's public address\n\nVerification of payment can be made using the above data as inputs at (http://drgl.info/#check_txn).\n\nFailure to provide the above data, or if you used an incompatible wallet, will result in losing the dispute case. The Dragonglass sender is responsible for providing verification of the DRGL transfer to the arbitrator in case of a dispute. Use of PaymentID is not required.\n\nIf you are unsure about any part of this process, visit Dragonglass on Discord (http://discord.drgl.info) for help. account.altcoin.popup.ZEC.msg=Όταν χρησιμοποιείς {0} μπορείς να χρησιμοποιήσεις μονάχα τη διάφανη διεύθυνση (ξεκινά με t), και όχι την z διεύθυνση (ιδιωτική), καθώς ο διαμεσολαβητής δεν θα μπορεί να επαληθεύσει τη συναλλαγή μέσω της z διεύθυνσης. account.altcoin.popup.XZC.msg=Όταν χρησιμοποιείς {0} μπορείς να χρησιμοποιήσεις μονάχα τη διάφανη (ανιχνεύσιμη) διεύθυνση, και όχι τη μη ανιχνεύσιμη διεύθυνση, καθώς ο διαμεσολαβητής δεν θα μπορεί να επαληθεύσει τη συναλλαγή με μη ανιχνεύσιμες διευθύνσεις στον block explorer. account.altcoin.popup.bch=Τα Bitcoin Cash και Bitcoin Clashic δεν διαθέτουν προστασία επανάληψης (replay protection). Αν χρησιμοποιείς αυτά τα νομίσματα απαιτείται να λάβεις επαρκείς προφυλάξεις και να κατανοείς όλες τις πιθανές επιπτώσεις. Η ακούσια αποστολή σε άλλο blockchain κατά την μετακίνηση νομισμάτων, ενδέχεται να οδηγήσει σε απώλειες κεφαλαίων. Καθώς αυτά τα νομίσματα μοιράζονται το ίδιο ιστορικό με το blockchain του Bitcoin, εμπεριέχουν κινδύνους ασφαλείας και απώλειας εχεμύθειας.\n\nΔιάβασε περισσότερα στο φόρουμ του Bisq: https://forum.bisq.io/t/airdrop-coins-information-thread-bch-btg-bchc @@ -1306,7 +1308,7 @@ dao.burnBsq.assets.lookBackPeriod=Verification period dao.burnBsq.assets.trialFee=Fee for trial period dao.burnBsq.assets.totalFee=Total fees paid dao.burnBsq.assets.days={0} days -dao.burnBsq.assets.toFewDays=The asset fee is too low. The min. amount of days for the trial perios is {0}. +dao.burnBsq.assets.toFewDays=The asset fee is too low. The min. amount of days for the trial period is {0}. # suppress inspection "UnusedProperty" dao.assetState.UNDEFINED=Ακαθόριστο @@ -1584,7 +1586,7 @@ displayUpdateDownloadWindow.verify.failed=Αποτυχία επαλήθευση displayUpdateDownloadWindow.success=Η νέα έκδοση αποθηκεύτηκε επιτυχώς και η υπογραφή επαληθεύτηκε.\n\nΆνοιξε το φάκελο αποθήκευσης, κλείσε την εφαρμογή και εγκατάστησε τη νέα έκδοση. displayUpdateDownloadWindow.download.openDir=Άνοιγμα καταλόγου λήψης -disputeΠερίληψηWindow.title=Περίληψη +disputeSummaryWindow.title=Περίληψη disputeSummaryWindow.openDate=Ticket opening date disputeSummaryWindow.role=Trader's role disputeSummaryWindow.evidence=Evidence @@ -1746,7 +1748,7 @@ popup.headline.error=Σφάλμα popup.doNotShowAgain=Ακύρωση επανεμφάνισης popup.reportError.log=Άνοιγμα αρχείου log popup.reportError.gitHub=Ανάφερε στο GitHub issue tracker -popup.reportError={0}\n\nTo help us to improve the software please report the bug on our issue tracker on GitHub (https://github.com/bisq-network/bisq-desktop/issues).\nThe error message will be copied to the clipboard when you click a button below.\nIt will make debugging easier if you can attach the bisq.log file as well. +popup.reportError={0}\n\nTo help us to improve the software please report this bug by opening a new issue at https://github.com/bisq-network/bisq/issues.\nThe above error message will be copied to the clipboard when you click either of the buttons below.\nIt will make debugging easier if you include the bisq.log file by pressing "Open log file", saving a copy, and attaching it to your bug report. popup.error.tryRestart=Επανεκκίνησε την εφαρμογή και έλεγξε τη σύνδεση δικτύου, ώστε να επιλυθεί το πρόβλημα. popup.error.takeOfferRequestFailed=Προέκυψε σφάλμα κατά την αποδοχή της προσφοράς σου.\n\n{0} @@ -1805,6 +1807,9 @@ popup.attention.forTradeWithId=Απαιτείται προσοχή σχετικ popup.roundedFiatValues.headline=New privacy feature: Rounded fiat values popup.roundedFiatValues.msg=To increase privacy of your trade the {0} amount was rounded.\n\nDepending on the client version you''ll pay or receive either values with decimals or rounded ones.\n\nBoth values do comply from now on with the trade protocol.\n\nAlso be aware that BTC values are changed automatically to match the rounded fiat amount as close as possible. +popup.info.multiplePaymentAccounts.headline=Multiple payment accounts available +popup.info.multiplePaymentAccounts.msg=You have multiple payment accounts available for this offer. Please make sure you've picked the right one. + #################################################################### # Notifications @@ -2085,7 +2090,7 @@ payment.clearXchange.info=Please be sure that you fulfill the requirements for t payment.moneyGram.info=Όταν χρησιμοποιείς MoneyGram, ο αγοραστής BTC πρέπει να στείλει μέσω email αριθμό Έγκρισης (Authorisation) και φωτογραφία της απόδειξης στον πωλητή. Στην απόδειξη θα πρέπει να διακρίνεται καθαρά Στην απόδειξη θα πρέπει να διακρίνεται καθαρά το πλήρες όνομα του πωλητή, η χώρα, η πόλη και το ποσό. Το email του πωλητή θα δοθεί στον αγοραστή κατά τη διαδικασία συναλλαγής. payment.westernUnion.info=Όταν χρησιμοποιείς Western Union, ο αγοραστής BTC πρέπει να στείλει μέσω email το MTCN (αριθμός εντοπισμού) και φωτογραφία της απόδειξης στον πωλητή. Στην απόδειξη θα πρέπει να διακρίνεται καθαρά Στην απόδειξη θα πρέπει να διακρίνεται καθαρά το πλήρες όνομα του πωλητή, η χώρα, η πόλη και το ποσό. Το email του πωλητή θα δοθεί στον αγοραστή κατά τη διαδικασία συναλλαγής. -payment.halCash.info=When using HalCash the BTC buyer need to send the BTC seller the HalCash code via a text message from the mobile phone.\n\nPlease make sure to not exceed the maximum amount your bank allows you to send with HalCash. The min. amount per withdrawal is 10 EUR and the max. amount is 600 EUR. For repeated withdrawals it is 3000 EUR per receiver per day and 6000 EUR per receiver per month. Please cross check those limits with your bank to be sure they use the same limits as stated here.\n\nThe withdrawal amount must be a multiple of 10 EUR as you cannot withdraw other amounts from an ATM. The UI in the create-offer and take-offer screen will adjust the BTC amount so that the EUR amount is correct. You cannot use market based price as the EUR amount would be changing with changing prices.\n\nIn case of a dispute the BTC buyer need to provide the proof that he sent the EUR. +payment.halCash.info=When using HalCash the BTC buyer needs to send the BTC seller the HalCash code via a text message from their mobile phone.\n\nPlease make sure to not exceed the maximum amount your bank allows you to send with HalCash. The min. amount per withdrawal is 10 EUR and the max. amount is 600 EUR. For repeated withdrawals it is 3000 EUR per receiver per day and 6000 EUR per receiver per month. Please cross check those limits with your bank to be sure they use the same limits as stated here.\n\nThe withdrawal amount must be a multiple of 10 EUR as you cannot withdraw other amounts from an ATM. The UI in the create-offer and take-offer screen will adjust the BTC amount so that the EUR amount is correct. You cannot use market based price as the EUR amount would be changing with changing prices.\n\nIn case of a dispute the BTC buyer needs to provide the proof that they sent the EUR. payment.limits.info=Λάβε υπόψιν πως όλες οι συναλλαγές μέσω τραπεζών περιέχουν ρίσκο αντιλογισμού χρέωσης.\n\nΓια να μετριάσει το ρίσκο, το Bisq θέτει όρια ανά συναλλαγή βασισμένα σε δύο παράγοντες:\n\n1. Τις πιθανότητες να συμβεί αντιλογισμός χρέωσης για τη μέθοδο πληρωμής που χρησιμοποιείται\n2. Την ηλικία λογαριασμού για αυτή τη μέθοδο πληρωμής.\n\nΟ λογαριασμός που δημιουργείς τώρα είναι καινούργιος και η ηλικία του είναι μηδέν. Καθώς η ηλικία του λογαριασμού σου θα μεγαλώνει, τα όρια ανά συναλλαγή θα αυξάνονται ως εξής:\n\n● Κατά τον 1ο μήνα το όριο ανά συναλλαγή θα είναι {0}\n● Κατά το 2ο μήνα το όριο ανά συναλλαγή θα είναι {1}\n● Μετά το 2ο μήνα το όριο ανά συναλλαγή θα είναι {2}\n\nΣημείωσε πως δεν υπάρχει όριο στο συνολικό πλήθος συναλλαγών. payment.cashDeposit.info=Please confirm your bank allows you to send cash deposits into other peoples' accounts. For example, Bank of America and Wells Fargo no longer allow such deposits. @@ -2098,7 +2103,7 @@ payment.f2f.optionalExtra=Προαιρετικές πρόσθετες πληρο payment.f2f.extra=Πρόσθετες πληροφορίες payment.f2f.extra.prompt=Ο maker μπορεί να ορίσει "όρους και προϋποθέσεις" ή να συμπεριλάβει κάποια πληροφορία επαφής. Αυτά θα εμφανιστούν στην προσφορά. -payment.f2f.info="Κατά πρόσωπο" συναλλαγές διέπονται από διαφορετικούς κανόνες και ενέχουν διαφορετικούς κινδύνους από διαδικτυακές συναλλαγές.\n\nΟι βασικές διαφορές είναι:\n\n● Οι συναλλασσόμενοι απαιτείται να ανταλλάξουν πληροφορίες σχετικές με το σημείο και την ώρα συνάντησης μέσω των παρεχόμενων στοιχείων επικοινωνίας.\n● Οι συναλλασσόμενοι απαιτείται να φέρουν τους φορητούς τους υπολογιστές και να προβούν σε επιβεβαίωση της αποστολής και λήψης πληρωμής στο σημείο συνάντησης.\n● Αν ο maker έχει ειδικούς "όρους και προϋποθέσεις", απαιτείται να τους δηλώσει στο πεδίο "Πρόσθετες πληροφορίες" του λογαριασμού.\n● Αποδεχόμενος μια προσφορά ο taker συμφωνεί με τους δηλωμένους "όρους και προϋποθέσεις" του maker.\n● Σε περίπτωση διένεξης ο διαμεσολαβητής δεν μπορεί να βοηθήσει σημαντικά, καθώς είναι δύσκολο να λάβει αδιάσειστα στοιχεία του τι συνέβη κατά τη συνάντηση. Σε αυτές τις περιπτώσεις τα κεφάλαια BTC ίσως κλειδωθούν δια παντός ή έως ότου οι συναλλασσόμενοι έρθουν σε συμφωνία.\n\nΣιγουρέψου πως κατανοείς πλήρως τις διαφορές των "κατά πρόσωπο" συναλλαγών μέσω των οδηγιών και των προτάσεων στο: 'https://docs.bisq.network/trading-rules.html#f2f-trading' +payment.f2f.info='Face to Face' trades have different rules and come with different risks than online transactions.\n\nThe main differences are:\n● The trading peers need to exchange information about the meeting location and time by using their provided contact details.\n● The trading peers need to bring their laptops and do the confirmation of 'payment sent' and 'payment received' at the meeting place.\n● If a maker has special 'terms and conditions' they must state those in the 'Additional information' text field in the account.\n● By taking an offer the taker agrees to the maker's stated 'terms and conditions'.\n● In case of a dispute the arbitrator cannot help much as it is usually hard to get tamper proof evidence of what happened at the meeting. In such cases the BTC funds might get locked indefinitely or until the trading peers come to an agreement.\n\nTo be sure you fully understand the differences with 'Face to Face' trades please read the instructions and recommendations at: 'https://docs.bisq.network/trading-rules.html#f2f-trading' payment.f2f.info.openURL=Άνοιγμα ιστοσελίδας payment.f2f.offerbook.tooltip.countryAndCity=Νομός και πόλη: {0} / {1} payment.f2f.offerbook.tooltip.extra=Πρόσθετες πληροφορίες: {0} diff --git a/core/src/main/resources/i18n/displayStrings_es.properties b/core/src/main/resources/i18n/displayStrings_es.properties index 6adfe42b9e..b7832a6325 100644 --- a/core/src/main/resources/i18n/displayStrings_es.properties +++ b/core/src/main/resources/i18n/displayStrings_es.properties @@ -46,7 +46,7 @@ shared.buyingCurrency=comprando {0} (Vendiendo BTC) shared.sellingCurrency=Vendiendo {0} (comprando BTC) shared.buy=comprar shared.sell=vender -shared.buying=Comprando +shared.buying=Comprando shared.selling=Vendiendo shared.P2P=P2P shared.oneOffer=oferta @@ -73,11 +73,11 @@ shared.details=Detalles shared.address=Dirección shared.balanceWithCur=Balance en {0} shared.txId=ID de la transacción -shared.confirmations=Confirmaciones +shared.confirmations=Confirmaciones shared.revert=Revertir Tx shared.select=Seleccionar shared.usage=Uso -shared.state=Estado +shared.state=Estado shared.tradeId=ID de intercambio shared.offerId=ID de oferta shared.bankName=Nombre del banco @@ -106,7 +106,7 @@ shared.enterPercentageValue=Introduzca valor % shared.OR=ó shared.notEnoughFunds=No tiene suficientes fondos en su monedero Bisq.\nNecesita {0} pero tiene sólo {1} en su monedero Bisq.\n\nPor favor deposite desde un monedero Bitcoin externo o agregue fondos a su monedero Bisq en \"Fondos/Depositar fondos\". shared.waitingForFunds=Esperando fondos... -shared.depositTransactionId=ID deposito de la transacción +shared.depositTransactionId=ID deposito de la transacción shared.TheBTCBuyer=El comprador de BTC shared.You=Usted shared.reasonForPayment=Concepto de pago @@ -193,9 +193,9 @@ shared.all=Todos shared.edit=Editar shared.advancedOptions=Opciones avanzadas shared.interval=Intervalo -shared.actions=Actions -shared.buyerUpperCase=Buyer -shared.sellerUpperCase=Seller +shared.actions=Acciones +shared.buyerUpperCase=Comprador +shared.sellerUpperCase=Vendedor #################################################################### # UI views @@ -233,7 +233,7 @@ mainView.footer.localhostBitcoinNode=(localhost) mainView.footer.btcInfo=Pares de red Bitcoin: {0} / {1} {2} mainView.footer.btcInfo.initializing=Iniciando mainView.footer.btcInfo.synchronizedWith=Sincronizado con -mainView.footer.btcInfo.connectingTo=Conectando a +mainView.footer.btcInfo.connectingTo=Conectando a mainView.footer.btcInfo.connectionFailed=Conexión fallida mainView.footer.p2pInfo=Pares de red P2P: {0} @@ -299,6 +299,8 @@ market.trades.tooltip.candle.date=Fecha: offerbook.createOffer=Crear oferta offerbook.takeOffer=Tomar oferta +offerbook.takeOfferToBuy=Take offer to buy {0} +offerbook.takeOfferToSell=Take offer to sell {0} offerbook.trader=Trader offerbook.offerersBankId=ID del banco del creador (BIC/SWIFT): {0} offerbook.offerersBankName=Nombre del banco del creador: {0} @@ -400,7 +402,7 @@ createOffer.resetToDefault=No, restablecer al valor por defecto createOffer.useLowerValue=Sí, usar mi valor más bajo createOffer.priceOutSideOfDeviation=El precio que ha introducido está fuera de la máxima desviación permitida en relación al precio de mercado.\nLa desviación máxima permitida es {0} y puede ajustarse en las preferencias. createOffer.changePrice=Cambiar precio -createOffer.tac=Al colocar esta oferta estoy de acuerdo en comerciar con cualquier comerciante que cumpla con las condiciones definidas anteriormente. +createOffer.tac=Al colocar esta oferta estoy de acuerdo en comerciar con cualquier comerciante que cumpla con las condiciones definidas anteriormente. createOffer.currencyForFee=Tasa de transacción createOffer.setDeposit=Establecer depósito de seguridad del comprador @@ -531,12 +533,12 @@ portfolio.pending.step2_buyer.halCashInfo.msg=Necesita enviar un mensaje de text portfolio.pending.step2_buyer.fasterPaymentsHolderNameInfo=Algunos bancos pueden requerir el nombre del receptor. El sort code de UK y el número de cuenta es suficiente para una transferecnia Faster Payment y el nombre del receptor no es verificado por ninguno de los bancos. portfolio.pending.step2_buyer.confirmStart.headline=Confirme que ha comenzado el pago. portfolio.pending.step2_buyer.confirmStart.msg=Ha iniciado el pago de {0} a su par de intercambio? -portfolio.pending.step2_buyer.confirmStart.yes=Sí, lo he iniciado. +portfolio.pending.step2_buyer.confirmStart.yes=Sí, lo he iniciado. portfolio.pending.step2_seller.waitPayment.headline=Esperar al pago. portfolio.pending.step2_seller.f2fInfo.headline=Información de contacto del comprador portfolio.pending.step2_seller.waitPayment.msg=La transacción del depósito tiene al menos una confirmación en la cadena de bloques.\nTien que esperar hasta que el comprador de BTC comience el pago de {0}. -portfolio.pending.step2_seller.warn=The BTC buyer still has not done the {0} payment.\nYou need to wait until they have started the payment.\nIf the trade has not been completed on {1} the arbitrator will investigate. +portfolio.pending.step2_seller.warn=El comprador de BTC aún no ha realizado el pago de {0}.\nNecesita esperar hasta que el pago comience.\nSi el intercambio aún no se ha completado el {1} el árbitro procederá a investigar. portfolio.pending.step2_seller.openForDispute=El comprador de BTC no ha comenzado su pago!\nEl periodo máximo permitido ha finalizado.\nPuede esperar más y dar más tiempo a la otra parte o contactar con el árbitro para abrir una disputa. # suppress inspection "UnusedProperty" @@ -565,7 +567,7 @@ portfolio.pending.step3_seller.altcoin.explorer=en su explorador de cadena de bl portfolio.pending.step3_seller.altcoin.wallet=en su monedero {0} portfolio.pending.step3_seller.altcoin={0}Por favor compruebe {1} si la transacción a su dirección de recepción\n{2}\ntiene suficientes confirmaciones en la cadena de bloques.\nLa cantidad a pagar tiene que ser {3}\n\nPuede copiar y pegar su dirección {4} desde la pantalla principal después de cerrar este popup. portfolio.pending.step3_seller.postal={0}Por favor, compruebe si ha recibido {1} con \"US Postal Money Order\"desde el comprador de BTC.\n\nLa ID de intercambio (el texto \"reason for payment\") de la transacción es: \"{2}\" -portfolio.pending.step3_seller.bank=Su compañero en intercambio ha confirmado que inició el pago de {0}.\n\nPor favor vaya a su página web de banco en línea y verifique si recibió {1} del comprador de BTC.\n\nEl ID de transacción (\"reason for payment\" text) es: \"{2}\"\n +portfolio.pending.step3_seller.bank=Su par de intercambio ha confirmado haber iniciado el pago de {0}.\n\nPor favor, vaya a la web de su banco y compruebe si ha recibido {1} desde la cuenta del comprador de BTC.\nLa ID de intercambio (texto \"razón de pago\") de la transacción es: \"{2}\" portfolio.pending.step3_seller.cash=Debido a que el pago se hecho vía depósito en efectivo el comprador de BTC tiene que escribir \"SIN REEMBOLSO\" en el recibo de papel, dividirlo en 2 partes y enviarte una foto por e-mail.\n\nPara impedir el riesgo de chargeback, confirme que todo está bien sólo si ha recibido el e-mail y si está seguro de que el recibo es válido.\nSi no está seguro, {0} portfolio.pending.step3_seller.moneyGram=El comprador tiene que enviarle el número de autorización y una foto del recibo por correo electrónico.\n\nEl recibo debe mostrar claramente el monto, asi como su nombre completo, país y demarcación (departamento,estado, etc.). Por favor revise su correo electrónico si recibió el número de autorización.\n\nDespués de cerrar esa ventana emergente (popup), verá el nombre y la dirección del comprador de BTC para retirar el dinero de MoneyGram.\n\n¡Solo confirme el recibo de transacción después de haber obtenido el dinero con éxito! portfolio.pending.step3_seller.westernUnion=El comprador htiene que enviarle el MTCN (número de seguimiento) y una foto de el recibo por email.\nEl recibo debe mostrar claramente su nombre completo, ciudad, país y la cantidad. Por favor compruebe su email y si ha recibido el MTCN.\n\nDespués de cerrar ese popup verá el nombre del comprador de BTC y la dirección para recoger el dinero de Western Union.\n\nConfirme el recibo después de haber recogido satisfactoriamente el dinero! @@ -721,7 +723,7 @@ funds.tx.noTxAvailable=Sin transacciones disponibles funds.tx.revert=Revertir funds.tx.txSent=La transacción se ha enviado exitosamente a una nueva dirección en la billetera Bisq local. funds.tx.direction.self=Enviado a usted mismo -funds.tx.daoTxFee=Miner fee for DAO tx +funds.tx.daoTxFee=Tasa de minaod para la tx DAO funds.tx.reimbursementRequestTxFee=Requerimiento de reembolso funds.tx.compensationRequestTxFee=Petición de compensación @@ -765,9 +767,9 @@ support.buyerOfferer= comprador/creador BTC support.sellerOfferer=vendedor/creador BTC support.buyerTaker=comprador/Tomador BTC support.sellerTaker=vendedor/Tomador BTC -support.backgroundInfo=Bisq is not a company, so it handles disputes differently.\n\nIf there are disputes in the trade process (e.g. one trader does not follow the trade protocol) the application will display an \"Open dispute\" button after the trade period is over for contacting the arbitrator.\n\nIf there is an issue with the application, the software will try to detect it and, if possible, display an \"Open support ticket\" button to contact the arbitrator who will forward the issue to the developers.\n\nIf you are having an issue and did not see the \"Open support ticket\" button, you can open a support ticket manually by selecting the trade causing issues under \"Portfolio/Open trades\" and hitting \"alt + o\" or \"option + o\". Please use this method only if you are sure that the software is not working as expected. If you have problems or questions, please review the FAQ on the bisq.network web page or post in the Bisq forum in the Support section. +support.backgroundInfo=Bisq no es una compañía, con lo que maneja las disputas de una forma diferente.\n\nSi hay disputas en el proceso de intercambio (v.g. un trader no sigue el protocolo de intercambio) la aplicación mostrará un botón de \"Abrir disputa\" después de que el periodo de intecambio haya finalizado para contactar con el árbitro.\n\nSi hay algún problema con la aplicación, el software intentará detectarlo y, si es posible, mostrará el botón \"Abrir ticket de soporte\" para contactar con el árbitro, que enviará el problema a los desarrolladores.\n\nSi tiene algún problema y no ve el botón \"Abrir ticket de soporte\" puede abrir un ticket de soporte manualmente seleccionando el intercambio causante de problemas en \"Portafolio/Intercambios Abiertos\" y pulsando \"alt + o\" o \"option + o\". Por favor use este método solo si está muy seguro de que el software no está funcionando como debería. Si tiene problemas o preguntas, por favor consulte las FAQ en la web bisq.network o postee en el forum Bisq en la sección de Soporte. -support.initialInfo=Please note the basic rules for the dispute process:\n1. You need to respond to the arbitrator's requests within 2 days.\n2. The maximum period for a dispute is 14 days.\n3. You need to cooperate with the arbitrator and provide the information they request to make your case.\n4. You accepted the rules outlined in the wiki in the user agreement when you first started the application.\n\nPlease read more about the dispute process in our wiki:\nhttps://github.com/bisq-network/exchange/wiki/Arbitration-system +support.initialInfo="Por favor, tenga en cuenta las reglas básicas del proceso de disputa:\n1. Necesita responder a los requerimientos del árbitro en 2 días.\n2. El periodo máximo para la disputa es de 14 días.\n3. Necesita cooperar con el árbitro y entregar la información que pueda requerir para su caso.\n4. Acepta las reglas mostradas en la wiki de acuerdo de usuario cuando inició la aplicación por primera vez.\n\nPor favor lea más en detalle acerca del proceso de disputa en nuestra wiki:\nhttps://github.com/bisq-network/exchange/wiki/Arbitration-system support.systemMsg=Mensaje de sistema: {0} support.youOpenedTicket=Ha abierto una solicitud de soporte. support.youOpenedDispute=Ha abierto una solicitud de disputa.\n\n{0} @@ -836,8 +838,8 @@ settings.net.useCustomNodesRadio=Utilizar nodos Bitcoin Core personalizados settings.net.warn.usePublicNodes=Si usa una red pública de Bitcoin está expuesto a problemas de seguridad causados por el fallo en el diseño y la implementación del filtro bloom que se utiliza para carteras SPV como BitcoinJ (usado en Bisq). Cualquier nodo completo al que esté conectado podría conocer que todas las direcciones del monedero pertenecen a una entidad.\n\nPor favor, lea más sobre los detalles en: https://bisq.network/blog/privacy-in-bitsquare.\n\n¿Está seguro de que quiere utilizar los nodos públicos? settings.net.warn.usePublicNodes.useProvided=No, utilizar nodos proporcionados settings.net.warn.usePublicNodes.usePublic=Sí, utilizar la red pública -settings.net.warn.useCustomNodes.B2XWarning=Please be sure that your Bitcoin node is a trusted Bitcoin Core node!\n\nConnecting to nodes which do not follow the Bitcoin Core consensus rules could corrupt your wallet and cause problems in the trade process.\n\nUsers who connect to nodes that violate consensus rules are responsible for any resulting damage. Any resulting disputes will be decided in favor of the other peer. No technical support will be given to users who ignore this warning and protection mechanisms! -settings.net.localhostBtcNodeInfo=(Background information: If you are running a local Bitcoin node (localhost) you can connect exclusively to it.) +settings.net.warn.useCustomNodes.B2XWarning=¡Por favor, asegúrese de que su nodo Bitcoin es un nodo de confianza Bitcoin Core!\n\nConectar a nodos que no siguen las reglas de consenso puede causar perjuicios a su cartera y causar problemas en el proceso de intercambio.\n\nLos usuarios que se conecten a los nodos que violan las reglas de consenso son responsables de cualquier daño que estos creen. Las disputas causadas por ello se decidirán en favor del otro participante. No se dará soporte técnico a usuarios que ignoren esta advertencia y los mecanismos de protección! +settings.net.localhostBtcNodeInfo=(Información complementaria: Si está ejecutando un nodo Bitcoin local (localhost) puede conectarse exclusivamente a él) settings.net.p2PPeersLabel=Pares conectados settings.net.onionAddressColumn=Dirección onion settings.net.creationDateColumn=Establecido @@ -860,17 +862,17 @@ settings.net.inbound=entrante settings.net.outbound=saliente settings.net.reSyncSPVChainLabel=Resincronizar cadena SPV settings.net.reSyncSPVChainButton=Borrar archivo SPV y resincronizar -settings.net.reSyncSPVSuccess=The SPV chain file will be deleted on the next startup. You need to restart your application now.\n\nAfter the restart it can take a while to resync with the network and you will only see all transactions once the resync is completed.\n\nPlease restart again after the resync has completed because there are sometimes inconsistencies that result in incorrect balances to display. -settings.net.reSyncSPVAfterRestart=The SPV chain file has been deleted. Please be patient. It can take a while to resync with the network. +settings.net.reSyncSPVSuccess=El archivo de cadena SPV se borrará en el siguiente inicio. Puede reiniciar la aplicación ahora.\n\nDespués del reinicio puede llevar un rato resincronizar con la red y verá todas las transacciones una vez completada la resincronización.\n\nPor favor haga otro reinicio después de resincronizar porque a veces hay inconsistencias que llevan a un balance mostrado incorrecto. +settings.net.reSyncSPVAfterRestart=La cadena SPV ha sido borrada. Por favor, sea paciente. Puede llevar un tiempo resincronizar con la red. settings.net.reSyncSPVAfterRestartCompleted=La resincronización se ha completado. Por favor, reinicie la aplicación. settings.net.reSyncSPVFailed=No se pudo borrar el archivo de cadena SPV\nError: {0} setting.about.aboutBisq=Acerca de Bisq -setting.about.about=Bisq is open-source software which facilitates the exchange of bitcoin with national currencies (and other cryptocurrencies) through a decentralized peer-to-peer network in a way that strongly protects user privacy. Learn more about Bisq on our project web page. +setting.about.about=Bisq es un software open-source que facilita el intercambio de bitcoin y monedas nacionales (y otras criptomonedas) a través de una red decentralizada peer-to-peer de modo que se proteja fuertemente la privacidad del usuario. Aprenda más acerca de Bisq en la página web del proyecto. setting.about.web=Página web de Bisq setting.about.code=código fuente setting.about.agpl=Licencia AGPL setting.about.support=Apoye Bisq -setting.about.def=Bisq is not a company—it is a project open to the community. If you want to participate or support Bisq please follow the links below. +setting.about.def=bisq no es una compañía, sino un proyecto abierto a la comunidad. Si quiere participar o ayudar a Bisq por favor siga los links de abajo. setting.about.contribute=Contribuir setting.about.donate=Donar setting.about.providers=Proveedores de datos @@ -892,7 +894,7 @@ setting.about.subsystems.val=Versión de red: {0}; Versión de mensajes P2P: {1} account.tab.arbitratorRegistration=Registro de árbitro account.tab.account=Cuenta account.info.headline=Bienvenido a su cuenta Bisq -account.info.msg=Here you can add trading accounts for national currencies & altcoins, select arbitrators, and create a backup of your wallet & account data.\n\nA new Bitcoin wallet was created the first time you started Bisq.\n\nWe strongly recommend that you write down your Bitcoin wallet seed words (see tab on the top) and consider adding a password before funding. Bitcoin deposits and withdrawals are managed in the \"Funds\" section.\n\nPrivacy & security note: because Bisq is a decentralized exchange, all your data is kept on your computer. There are no servers, so we have no access to your personal info, your funds, or even your IP address. Data such as bank account numbers, altcoin & Bitcoin addresses, etc are only shared with your trading partner to fulfill trades you initiate (in case of a dispute the arbitrator will see the same data as your trading peer). +account.info.msg=Aquí puede añadir cuentas de intercambio para monedas nacionales y altcoins, seleccionar árbitros y crear una copia de seguridad de la cartera y datos de cuenta.\n\nSe ha creado una cartera vacía de Bitcoin la primera vez que inició Bisq.\n\nRecomendamos encarecidamente que anote las palabras semilla de la cartera (ver botón superior) y considere añadir una contraseña antes de enviar fondos. Los depósitos y retiros de Bitcoin se controlan en la sección \"Fondos\".\n\nPrivacidad y Seguridad:\nComo Bisq es un exchange descentralizado, todos los datos se mantienen en su ordenador. No hay servidores y no tenemos acceso a su información personal, sus fondos ni su dirección IP. Datos como números de cuenta bancaria, direcciones Bitcoin y altcoin, etc sólo se comparten con el par de intercambio para completar los intercambios iniciados (en caso de disputa, el árbitro verá los mismos datos que el par de intercambio). account.menu.paymentAccount=Cuentas de moneda nacional account.menu.altCoinsAccountView=Cuentas de altcoi @@ -905,7 +907,7 @@ account.arbitratorRegistration.pubKey=Clave pública account.arbitratorRegistration.register=Registro de árbitro account.arbitratorRegistration.revoke=Revocar registro -account.arbitratorRegistration.info.msg=Please note that you need to stay available for 15 days after revoking as there might be trades which are using you as arbitrator. The max. allowed trade period is 8 days and the dispute process might take up to 7 days. +account.arbitratorRegistration.info.msg=Por favor, tenga en cuenta que necesita estar disponible durante 15 días después de la revocación porque podría haber intercambios en los que esté envuelto como árbitro. El periodo máximo de intercambio es de 8 días y el proceso de disputa puede llevar hasta 7 días. account.arbitratorRegistration.warn.min1Language=Necesita introducir al menos 1 idioma.\nHemos añadido el idioma por defecto para usted. account.arbitratorRegistration.removedSuccess=Ha eliminado su árbitro de la red P2P satisfactoriamente. account.arbitratorRegistration.removedFailed=No se pudo eliminar el árbitro. {0} @@ -924,12 +926,12 @@ account.arbitratorSelection.noLang=Puede seleccionar solamente árbitros que hab account.arbitratorSelection.minOne=Necesita tener al menos un árbitro seleccionado. account.altcoin.yourAltcoinAccounts=Sus cuentas de altcoin -account.altcoin.popup.wallet.msg=Please be sure that you follow the requirements for the usage of {0} wallets as described on the {1} web page.\nUsing wallets from centralized exchanges where (a) you don''t control your keys or (b) which don''t use compatible wallet software is risky: it can lead to loss of the traded funds!\nThe arbitrator is not a {2} specialist and cannot help in such cases. +account.altcoin.popup.wallet.msg=Por favor, asegúrese de que sigue los requerimientos para el uso de carteras {0} tal como se describe en la página web {1}.\n¡Usar carteras desde casas de cambio centralizadas donde (a) no tiene control sobre las claves o (b) no usan un compatible es arriesgado: puede llevar a la pérdida de los fondos intercambiados!\nEl árbitro no es un especialista {2} y no puede ayudar en tales casos. account.altcoin.popup.wallet.confirm=Entiendo y confirmo que sé qué monedero tengo que utilizar. -account.altcoin.popup.xmr.msg=Si quiere comerciar XMR en Bisq, por favor asegúrese de que entiende y cumple todos los requerimientos.\n\nPara enviar XMR necesita usar o el monedero oficial Monero GUI o el monedero Monero simple con la bandera store-tx-info habilitada (por defecto en las nuevas versiones).\nPor favor asegúrese de que puede acceder a la tx key (usar el comando get_tx_key en simplewallet) porque podría requerirse en caso de disputa.\n\nmonero-wallet-cli (use el comando get_tx_key)\nmonero-wallet-gui (vaya a la pestaña de historia y clique en el botón (P) para prueba de pago)\n\nAdemás de la herramienta XMR checktx (https://xmr.llcoins.net/checktx.html) la verificación también se puede cumplir dentro del monedero.\nmonero-wallet-cli : usando el comando (check_tx_key).\nmonero-wallet-gui : en Avanzado > Probar/Comprobar página.\nEn exploradores de bloque normales la transferencia no es verificable.\n\nNecesita entregar al árbitro la siguiente información en caso de disputa:\n- La clave privada de transacción (tx private key).\n- El hash de transacción.\n- La dirección pública del receptor.\n\nSi no puede proveer la información o si ha usado un monedero incompatible resultaría en la pérdida del caso de disputa. El emisor de XMR es responsable de ser capaz de verificar la transacción XMR a el árbitro en caso de disputa.\n\nNo se requiere la ID de pago, sólo la dirección pública normal.\n\nSi no está seguro del proceso visite (https://www.getmonero.org/resources/user-guides/prove-payment.html) o el foro Monero (https://forum.getmonero.org) para más información. -account.altcoin.popup.blur.msg=If you want to trade BLUR on Bisq please be sure you understand and fulfill the following requirements:\n\nTo send BLUR you must use the Blur Network CLI or GUI Wallet. \n\nIf you are using the CLI wallet, a transaction hash (tx ID) will be displayed after a transfer is sent. You must save this information. Immediately after sending the transfer, you must use the command 'get_tx_key' to retrieve the transaction private key. If you fail to perform this step, you may not be able to retrieve the key later. \n\nIf you are using the Blur Network GUI Wallet, the transaction private key and transaction ID can be found conveniently in the "History" tab. Immediately after sending, locate the transaction of interest. Click the "?" symbol in the lower-right corner of the box containing the transaction. You must save this information. \n\nIn the event that arbitration is necessary, you must present the following to an arbitrator: 1.) the transaction ID, 2.) the transaction private key, and 3.) the recipient's address. The arbitrator will then verify the BLUR transfer using the Blur Transaction Viewer (https://blur.cash/#tx-viewer).\n\nIf you cannot provide the required information to the arbitrator, you will lose the dispute. In all cases of dispute, the BLUR sender bears 100% of the burden of responsiblity in verifying transactions to an arbitrator. \n\nIf you do not understand these requirements, do not trade on Bisq. First, seek help at the Blur Network Discord (https://discord.gg/dMWaqVW). -account.altcoin.popup.ccx.msg=Si quiere intercambiar CCX en Bisq poar favor asegúrese de que entiende los siguientes requerimientos:\n\nPara enviar CCX debe usar un monedero ofcial Conceal, ya sea CLI o GUI. Después de enviar el pago, los monederos\nmuestran la clave secreta de la transacción. Debe guardarla junto con el hash de la transacción (ID) y la dirección\npública en caso de que sea necesario arbitraje. En tal caso, debe dar las tres al árbitro, quien\nverificará la transferencia CCX usando el Visor de Transacciones Conceal (https://explorer.conceal.network/txviewer).\nDebido a que Conceal es una moneda de privacidad, los exploradores de bloques no pueden verificar transferencias.\n\nSi no puede entregar los datos requeridos al árbitro, perderá el caso de disputa.\nSi no guarda la clave secreta de la transacción inmediatamente después de transferir CCX, no se podrá recuperar luego.\nSi no entiende estos requerimientos, busque ayuda en el discord Conceal (http://discord.conceal.network). -account.altcoin.popup.drgl.msg=Trading Dragonglass on Bisq requires that you understand and fulfill the following requirements:\n\nBecause of the privacy Dragonglass provides a transaction is not verifyable on the public blockchain. If required you can prove your payment thru use of your TXN-Private-Key.\nThe TXN-Private Key is a one-time key automatically generated for every transaction that can only be accessed from within your DRGL wallet.\nEither by DRGL-wallet GUI (inside transaction details dialog) or by the Dragonglass CLI simplewallet (using command "get_tx_key").\n\nDRGL version 'Oathkeeper' and higher are REQUIRED for both.\n\nIn case of a dispute, you must provide the arbitrator the following data:\n- The TXN-Private key\n- The transaction hash\n- The recipient's public address\n\nVerification of payment can be made using the above data as inputs at \ (http://drgl.info/#check_txn).\n\nIf you cannot provide the above data or if you used an incompatible wallet it would result in losing the dispute case. The Dragonglass sender is responsible to be able to verify the DRGL transfer to the arbitrator in case of a dispute. Use of PaymentID is not required.\n\nIf you are unsure about any part of this process, visit Dragonglass on Discord (http://discord.drgl.info) for help. +account.altcoin.popup.xmr.msg=Intercambiar XMR en Bisq, requiere entender y cumplir los siguientes requisitos\n\nPara enviar XMR necesita usar o el monedero oficial Monero GUI o el monedero Monero simple con la bandera store-tx-info habilitada (por defecto en las nuevas versiones). Por favor asegúrese de que puede acceder a la tx key (usar el comando get_tx_key en simplewallet) porque podría requerirse en caso de disputa.\nmonero-wallet-cli (use el comando get_tx_key)\nmonero-wallet-gui (vaya a la pestaña de historia y clique en el botón (P) para prueba de pago)\n\nAdemás de la herramienta XMR checktx (https://xmr.llcoins.net/checktx.html) la verificación también se puede cumplir dentro del monedero.\nmonero-wallet-cli : usando el comando (check_tx_key).\nmonero-wallet-gui : en Avanzado > Probar/Comprobar página.\nEn exploradores de bloque normales la transferencia no es verificable.\n\nNecesita entregar al árbitro la siguiente información en caso de disputa:\n- La clave privada de transacción (tx private key).\n- El hash de transacción.\n- La dirección pública del receptor.\n\nSi no puede proveer la información o si ha usado un monedero incompatible resultaría en la pérdida del caso de disputa. El emisor de XMR es responsable de ser capaz de verificar la transacción XMR a el árbitro en caso de disputa.\n\nNo se requiere la ID de pago, sólo la dirección pública normal.\nSi no está seguro del proceso visite (https://www.getmonero.org/resources/user-guides/prove-payment.html) o el foro Monero (https://forum.getmonero.org) para más información. +account.altcoin.popup.blur.msg=Trading BLUR on Bisq requires that you understand and fulfill the following requirements:\n\nTo send BLUR you must use the Blur Network CLI or GUI Wallet. \n\nIf you are using the CLI wallet, a transaction hash (tx ID) will be displayed after a transfer is sent. You must save this information. Immediately after sending the transfer, you must use the command 'get_tx_key' to retrieve the transaction private key. If you fail to perform this step, you may not be able to retrieve the key later. \n\nIf you are using the Blur Network GUI Wallet, the transaction private key and transaction ID can be found conveniently in the "History" tab. Immediately after sending, locate the transaction of interest. Click the "?" symbol in the lower-right corner of the box containing the transaction. You must save this information. \n\nIn the event that arbitration is necessary, you must present the following to an arbitrator: 1.) the transaction ID, 2.) the transaction private key, and 3.) the recipient's address. The arbitrator will then verify the BLUR transfer using the Blur Transaction Viewer (https://blur.cash/#tx-viewer).\n\nFailure to provide the required information to the arbitrator will result in losing the dispute case. In all cases of dispute, the BLUR sender bears 100% of the burden of responsibility in verifying transactions to an arbitrator. \n\nIf you do not understand these requirements, do not trade on Bisq. First, seek help at the Blur Network Discord (https://discord.gg/dMWaqVW). +account.altcoin.popup.ccx.msg=Trading CCX on Bisq requires that you understand the following requirements:\n\nTo send CCX you must use an official Conceal wallet, either CLI or GUI. After sending a transfer payment, the wallets\ndisplay the transaction secret key. You must save it along with the transaction hash (ID) and the recipient's public\naddress in case arbitration is necessary. In such a case, you must give all three to the arbitrator, who will then\nverify the CCX transfer using the Conceal Transaction Viewer (https://explorer.conceal.network/txviewer).\nBecause Conceal is a privacy coin, block explorers cannot verify transfers.\n\nFailure to provide the required data to the arbitrator will result in losing the dispute case.\nIf you do not save the transaction secret key immediately after transferring CCX, it cannot be recovered later.\nIf you do not understand these requirements, seek help at the Conceal discord (http://discord.conceal.network). +account.altcoin.popup.drgl.msg=Trading Dragonglass on Bisq requires that you understand and fulfill the following requirements:\n\nBecause of the privacy Dragonglass provides, a transaction is not verifiable on the public blockchain. If required, you can prove your payment through the use of your TXN-Private-Key.\nThe TXN-Private Key is a one-time key automatically generated for every transaction that can only be accessed from within your DRGL wallet.\nEither by DRGL-wallet GUI (inside transaction details dialog) or by the Dragonglass CLI simplewallet (using command "get_tx_key").\n\nDRGL version 'Oathkeeper' and higher are REQUIRED for both.\n\nIn case of a dispute, you must provide the arbitrator the following data:\n- The TXN-Private key\n- The transaction hash\n- The recipient's public address\n\nVerification of payment can be made using the above data as inputs at (http://drgl.info/#check_txn).\n\nFailure to provide the above data, or if you used an incompatible wallet, will result in losing the dispute case. The Dragonglass sender is responsible for providing verification of the DRGL transfer to the arbitrator in case of a dispute. Use of PaymentID is not required.\n\nIf you are unsure about any part of this process, visit Dragonglass on Discord (http://discord.drgl.info) for help. account.altcoin.popup.ZEC.msg=Cuando use {0} sólo puede usar direcciones transparentes (que empiecen por t) y no las direcciones-z (privadas), porque el árbitro no sería capaz de verificar la transacción con direcciones-z. account.altcoin.popup.XZC.msg=Al usar {0} puede solamente usar direcciones transparentes (trazables), porque el árbitro no sería capaz de verificar la transacciones no trazables en el explorador de bloques. account.altcoin.popup.bch=Bitcoin cash and Bitcoin Clashic sufren de replay protection. Si usa una de estas monedes aseguŕese de que toma suficientes precauciones y entiende las implicaciones. Puede sufrir pérdidas enviando una moneda sin querer enviar las mismas monedeas a la otra cadena de bloques. Debido a que estos "airdrops" comparten la misma historia con la cadena de bloques de Bitcoin hay también riesgos de seguridad y un riesgo considerable de pérdida de privacidad.\n\nPor favor lea en el foro Bisq más acerca de este tema: https://forum.bisq.io/t/airdrop-coins-information-thread-bch-btg-bch @@ -952,14 +954,14 @@ account.password.removePw.button=Eliminar password account.password.removePw.headline=Eliminar protección por password del monedero account.password.setPw.button=Establecer password account.password.setPw.headline=Establecer protección por password del monedero -account.password.info=With password protection you'll need to enter your password at application startup, when withdrawing bitcoin out of your wallet, and when restoring your wallet from seed words. +account.password.info=Con protección por password necesitará introducir su password en el arranque de la aplicación, cuando retire bitcoin de su monedero, y cuando restaure su monedero desde las palabras semilla. account.seed.backup.title=Copia de seguridad de palabras semilla del monedero -account.seed.info=Please write down both wallet seed words and the date! You can recover your wallet any time with seed words and the date.\nThe same seed words are used for the BTC and BSQ wallet.\n\nYou should write down the seed words on a sheet of paper. Do not save them on your computer.\n\nPlease note that the seed words are NOT a replacement for a backup.\nYou need to create a backup of the whole application directory from the \"Account/Backup\" screen to recover application state and data.\nImporting seed words is only recommended for emergency cases. The application will not be functional without a proper backup of the database files and keys! +account.seed.info=Por favor apunte en un papel tanto las palabras semilla del monedero como la fecha! Puede recuperar su monedero en cualquier momento con las palabras semilla y la fecha.\nLas mismas palabras semilla se usan para el monedero BTC como BSQ\n\nDebe apuntar las palabras semillas en una hoja de papel. No la guarde en su computadora.\n\nPor favor, tenga en cuenta que las palabras semilla no son un sustituto de la copia de seguridad.\nNecesita hacer la copia de seguridad de todo el directorio de aplicación en la pantalla \"Cuenta/Copia de Seguridad\" para recuperar un estado de aplicación válido y los datos.\nImportar las palabras semilla solo se recomienda para casos de emergencia. La aplicación no será funcional sin una buena copia de seguridad de los archivos de la base de datos y las claves! account.seed.warn.noPw.msg=No ha establecido una contraseña de cartera que proteja la visualización de las palabras semilla.\n\n¿Quiere que se muestren las palabras semilla? account.seed.warn.noPw.yes=Sí, y no preguntar de nuevo account.seed.enterPw=Introducir password para ver las palabras semilla -account.seed.restore.info=Please make a backup before applying restore from seed words. Be aware that wallet restore is only for emergency cases and might cause problems with the internal wallet database.\nIt is not a way for applying a backup! Please use a backup from the application data directory for restoring a previous application state. +account.seed.restore.info=Por favor haga una copia de seguridad antes de aplicar la restauración desde las palabras semilla. Tenga en cuenta que la restauración de cartera solo es para casos de emergencia y puede causar problemas con la base de datos interna del monedero.\nNo es el modo de aplicar una restauración de copia de seguridad! Por favor use una copia de seguridad desde el archivo de directorio de la aplicación para restaurar un estado de aplicación anterior. account.seed.restore.ok=Ok, entiendo y quiero restaurar @@ -1322,7 +1324,7 @@ dao.assetState.REMOVED_BY_VOTING=Eliminados por votación dao.proofOfBurn.header=Prueba de quemado dao.proofOfBurn.amount=Cantidad dao.proofOfBurn.preImage=Pre-imagen -dao.proofOfQuemar.burn=Quemar +dao.proofOfBurn.burn=Quemar dao.proofOfBurn.allTxs=Todas las transacciones de prueba de quemado dao.proofOfBurn.myItems=Mis transacciones de prueba de quemado dao.proofOfBurn.date=Fecha @@ -1483,8 +1485,8 @@ dao.wallet.dashboard.totalUnlockingAmount=Desbloqueando BSQ de bonos dao.wallet.dashboard.totalUnlockedAmount=BSQ desbloqueados de bonos dao.wallet.dashboard.totalConfiscatedAmount=BSQ confiscados de bonos dao.wallet.dashboard.allTx=Número de todas las transacciones BSQ -dao.wallet.dashboard.utxo=Número de todos los outputs de transacciones no gastadas -dao.wallet.dashboard.compensationIssuanceTx=Número de todas las transacciones emitidas de solicitudes de compensación +dao.wallet.dashboard.utxo=Número de todos los outputs de transacciones no gastadas +dao.wallet.dashboard.compensationIssuanceTx=Número de todas las transacciones emitidas de solicitudes de compensación dao.wallet.dashboard.reimbursementIssuanceTx=Número de todas las transacciones emitidas de solicitud de reembolso dao.wallet.dashboard.burntTx=Número de todas las transacciones de tasa de pago dao.wallet.dashboard.price=Último precio intercambio BSQ/BTC (en Bisq) @@ -1506,8 +1508,8 @@ dao.wallet.send.send=Enviar fondos BSQ dao.wallet.send.sendBtc=Enviar fondos BTC dao.wallet.send.sendFunds.headline=Confirme la petición de retiro dao.wallet.send.sendFunds.details=Enviando: {0}\nA la dirección receptora: {1}.\nLa tasa de transacción requerida es: {2} ({3} Satoshis/byte)\nTamaño de la transacción: {4} Kb\n\nEl receptor recibirá: {5}\n\nSeguro que quiere retirar esta cantidad? -dao.wallet.chainHeightSynced=Latest verified block: {0} -dao.wallet.chainHeightSyncing=Awaiting blocks... Verified {0} blocks out of {1} +dao.wallet.chainHeightSynced=Último bloque verificado: {0} +dao.wallet.chainHeightSyncing=Esperando bloques... {0} bloques verificados de {1} dao.wallet.tx.type=Tipo # suppress inspection "UnusedProperty" @@ -1584,7 +1586,7 @@ displayUpdateDownloadWindow.verify.failed=Verificación fallida./nPor favor desc displayUpdateDownloadWindow.success=La nueva versión ha sido descargada con éxito y la firma verificada./n/nPor favor abra el directorio de descargas, cierre la aplicación e instale la nueva versión. displayUpdateDownloadWindow.download.openDir=Abrir directorio de descargas -disputeResumenWindow.title=Resumen +disputeSummaryWindow.title=Resumen disputeSummaryWindow.openDate=Fecha de apertura de ticket disputeSummaryWindow.role=Rol del trader disputeSummaryWindow.evidence=Evidencia @@ -1746,7 +1748,7 @@ popup.headline.error=Error popup.doNotShowAgain=No mostrar de nuevo popup.reportError.log=Abrir archivo de registro popup.reportError.gitHub=Reportar al rastreador de problemas de Github -popup.reportError={0}\n\nTo help us to improve the software please report the bug on our issue tracker on GitHub (https://github.com/bisq-network/bisq-desktop/issues).\nThe error message will be copied to the clipboard when you click a button below.\nIt will make debugging easier if you can attach the bisq.log file as well. +popup.reportError={0}\n\nTo help us to improve the software please report this bug by opening a new issue at https://github.com/bisq-network/bisq/issues.\nThe above error message will be copied to the clipboard when you click either of the buttons below.\nIt will make debugging easier if you include the bisq.log file by pressing "Open log file", saving a copy, and attaching it to your bug report. popup.error.tryRestart=Por favor pruebe a reiniciar la aplicación y comprobar su conexión a la red para ver si puede resolver el problema. popup.error.takeOfferRequestFailed=Un error ocurrió cuando alguien intentó tomar una de sus ofertas:/n{0} @@ -1783,7 +1785,7 @@ popup.warning.nodeBanned=Uno de los nodos {0} ha sido baneado. Por favor reinici popup.warning.priceRelay=retransmisión de precios popup.warning.seed=Semilla -popup.info.securityDepositInfo=To ensure both traders follow the trade protocol, both traders need to pay a security deposit.\n\nThis deposit is kept in your trade wallet until your trade has been successfully completed, and then it's refunded to you.\n\nPlease note: if you're creating a new offer, Bisq needs to be running for another trader to take it. To keep your offers online, keep Bisq running and make sure this computer remains online too (i.e., make sure it doesn't switch to standby mode...monitor standby is fine). +popup.info.securityDepositInfo=Para asegurarse de que ambos comerciantes siguen el protocolo de intercambio, necesitan pagar un depósito de seguridad.\n\nEl depósito se guarda en el monedor de intercambio hasta que el intercambio se complete, y entonces se devuelve.\n\nPor favor, tenga en cuenta que al crear una nueva oferta, Bisq necesita estar en ejecución para que otro comerciante la tome. Para mantener sus ofertas online, mantenga Bisq funcionando y asegúrese de que su computadora está online también (v.g. asegúrese de que no pasa a modo standby...el monitor en standby no es problema!) popup.info.cashDepositInfo=Por favor asegúrese de que tiene una oficina bancaria donde pueda hacer el depósito de efectivo.\nEl banco con ID (BIC/SWIFT) de el banco del vendedor es: {0} popup.info.cashDepositInfo.confirm=Confirmo que puedo hacer el depósito @@ -1805,6 +1807,9 @@ popup.attention.forTradeWithId=Se requiere atención para el intercambio con ID popup.roundedFiatValues.headline=Nueva característica de privacidad: Valores redondeados a fiat popup.roundedFiatValues.msg=Para incrementar la privacidad de sus intercambios la cantidad de {0} se redondeó.\n\nDependiendo de la versión del cliente pagará o recibirá valores con decimales o redondeados.\n\nAmbos valores serán cumplirán con el protocolo de intercambio.\n\nTambién tenga en cuenta que los valores BTC cambian automáticamente para igualar la cantidad fiat redondeada tan ajustada como sea posible. +popup.info.multiplePaymentAccounts.headline=Multiple payment accounts available +popup.info.multiplePaymentAccounts.msg=You have multiple payment accounts available for this offer. Please make sure you've picked the right one. + #################################################################### # Notifications @@ -2085,7 +2090,7 @@ payment.clearXchange.info=Por favor asegúrese de que cumple los requisitos para payment.moneyGram.info=Al utilizar MoneyGram, el comprador de BTC tiene que enviar el número de autorización y una foto del recibo al vendedor de BTC por correo electrónico. El recibo debe mostrar claramente el monto, asi como el nombre completo, país y demarcación (departamento,estado, etc.) del vendedor. Al comprador se le mostrará el correo electrónico del vendedor en el proceso de transacción. payment.westernUnion.info=Al utilizar Western Union, el comprador de BTC tiene que enviar el número de autorización y una foto del recibo al vendedor de BTC por correo electrónico. El recibo debe mostrar claramente el monto, asi como el nombre completo, país y demarcación (departamento,estado, etc.) del vendedor. Al comprador se le mostrará el correo electrónico del vendedor en el proceso de transacción. -payment.halCash.info=Al usar HalCash el comprador de BTC necesita enviar al vendedor de BTC el código HalCash a través de un mensaje de texto desde el teléfono móvil.\n\nPor favor asegúrese de que no excede la cantidad máxima que su banco le permite enviar con HalCash. La cantidad mínima por retirada es de 10 EUR y el máximo son 600 EUR. Para retiros frecuentes es 3000 por receptor al día y 6000 por receptor al mes. Por favor compruebe estos límites con su banco y asegúrese que son los mismos que aquí expuestos.\n\nLa cantidad de retir debe ser un múltiplo de 10 EUR ya que no se puede retirar otras cantidades desde el cajero automático. La Interfaz de Usuario en la pantalla crear oferta y tomar oferta ajustará la cantidad de BTC para que la cantidad de EUR sea correcta. No puede usar precios basados en el mercado ya que la cantidad de EUR cambiaría con el cambio de precios.\n\nEn caso de disputa el comprador de BTC necesita proveer la prueba de que ha enviado EUR. +payment.halCash.info=Al usar HalCash el comprador de BTC necesita enviar al vendedor de BTC el código HalCash a través de un mensaje de texto desde el teléfono móvil.\n\nPor favor asegúrese de que no excede la cantidad máxima que su banco le permite enviar con HalCash. La cantidad mínima por retirada es de 10 EUR y el máximo son 600 EUR. Para retiros frecuentes es 3000 por receptor al día y 6000 por receptor al mes. Por favor compruebe estos límites con su banco y asegúrese que son los mismos que aquí expuestos.\n\nLa cantidad de retiro debe ser un múltiplo de 10 EUR ya que no se puede retirar otras cantidades desde el cajero automático. La Interfaz de Usuario en la pantalla crear oferta y tomar oferta ajustará la cantidad de BTC para que la cantidad de EUR sea correcta. No puede usar precios basados en el mercado ya que la cantidad de EUR cambiaría con el cambio de precios.\n\nEn caso de disputa el comprador de BTC necesita proveer la prueba de que ha enviado EUR. payment.limits.info=Por favor, tenga en cuenta que todas las transferencias bancarias tienen cierto riesgo de chargeback.\n\nPara disminuir este riesgo, Bisq establece límites por intecambio basándose en dos factores:\n\n1. El nivel estimado de riesgo de chargeback para el método de pago usado\n2. La edad de su cuenta para ese método de pago\n\nLa cuenta que está creando ahora es nueva y su edad es cero. A medida que su cuenta gane edad en un periodo de dos meses, también aumentará el límite por transacción.\n\n● Durante el primer mes, el límite será {0}\n● Durante el segundo mes, el límite será {1}\n● Después del segundo mes, el límite será {2}\n\nTenga en cuenta que no hay límites en el total de transacciones que puede realizar. payment.cashDeposit.info=por favor confirme que su banco permite enviar depósitos de efectivo a cuentas de otras personas. Por ejemplo, Bank of America y Wells Fargo ya no permiten estos depósitos. @@ -2098,7 +2103,7 @@ payment.f2f.optionalExtra=Información adicional opcional payment.f2f.extra=Información adicional payment.f2f.extra.prompt=El creador puede definir los 'términos y condiciones' o añadir información de contacto pública. Será mostrada junto con la oferta. -payment.f2f.info=Los intercambios 'Cara a Cara' (F2F) tienen diferentes reglas y riesgos que las transacciones online.\n\nLas principales diferencias son:\n● Los pares de intercambio necesitan intercambiar información acerca del punto de reunión y la hora usando los detalles de contacto proporcionados.\n● Los pares de intercambio tienen que traer sus portátiles y hacer la confirmación de 'pago enviado' y 'pago recibido' en el lugar de reunión.\nSi un creador tiene 'términos y condiciones' especiales necesita declararlos en el campo de texto 'información adicional' en la cuenta.\n● Tomando una oferta el tomador está de acuerdo con los 'términos y condiciones' declarados por el creador.\n● En caso de disputa el árbitro no puede ayudar mucho ya que normalmente es complicado obtener evidencias no manipulables de lo que ha pasado en una reunión. En estos casos los fondos BTC pueden bloquearse indefinidamente o hasta que los pares lleguen a un acuerdo.\n\nPara asegurarse de que comprende las diferencias con los intercambios 'Cara a Cara' por favor lea las instrucciones y recomendaciones en: 'https://docs.bisq.network/trading-rules.html#f2f-trading' +payment.f2f.info=Los intercambios 'Cara a Cara' (F2F) tienen diferentes reglas y riesgos que las transacciones online.\n\nLas principales diferencias son:\n● Los pares de intercambio necesitan intercambiar información acerca del punto de reunión y la hora usando los detalles de contacto proporcionados.\n● Los pares de intercambio tienen que traer sus portátiles y hacer la confirmación de 'pago enviado' y 'pago recibido' en el lugar de reunión.\n● Si un creador tiene 'términos y condiciones' especiales necesita declararlos en el campo de texto 'información adicional' en la cuenta.\n● Tomando una oferta el tomador está de acuerdo con los 'términos y condiciones' declarados por el creador.\n● En caso de disputa el árbitro no puede ayudar mucho ya que normalmente es complicado obtener evidencias no manipulables de lo que ha pasado en una reunión. En estos casos los fondos BTC pueden bloquearse indefinidamente o hasta que los pares lleguen a un acuerdo.\n\nPara asegurarse de que comprende las diferencias con los intercambios 'Cara a Cara' por favor lea las instrucciones y recomendaciones en: 'https://docs.bisq.network/trading-rules.html#f2f-trading' payment.f2f.info.openURL=Abrir paǵina web payment.f2f.offerbook.tooltip.countryAndCity=Provincia y ciudad: {0} / {1} payment.f2f.offerbook.tooltip.extra=Información adicional: {0} @@ -2227,7 +2232,7 @@ ADVANCED_CASH_SHORT=Advanced Cash validation.empty=No se permiten entradas vacías validation.NaN=El valor introducido no es válido -validation.notAnInteger=El valor introducido no es entero +validation.notAnInteger=El valor introducido no es entero validation.zero=El 0 no es un valor permitido. validation.negative=No se permiten entradas negativas. validation.fiat.toSmall=No se permite introducir un valor menor que el mínimo posible diff --git a/core/src/main/resources/i18n/displayStrings_fa.properties b/core/src/main/resources/i18n/displayStrings_fa.properties index 7432f8685e..2eb7b028bd 100644 --- a/core/src/main/resources/i18n/displayStrings_fa.properties +++ b/core/src/main/resources/i18n/displayStrings_fa.properties @@ -36,7 +36,7 @@ shared.iUnderstand=فهمیدم shared.na=بدون پاسخ shared.shutDown=خاموش shared.reportBug=گزاش باگ در GitHub  -shared.buyBitcoin=بیتکوین بخرید +shared.buyBitcoin=خرید بیتکوین shared.sellBitcoin=بیتکوین بفروشید shared.buyCurrency=خرید {0} shared.sellCurrency=فروش {0} @@ -299,6 +299,8 @@ market.trades.tooltip.candle.date=تاریخ: offerbook.createOffer=ایجاد پیشنهاد offerbook.takeOffer=برداشتن پیشنهاد +offerbook.takeOfferToBuy=Take offer to buy {0} +offerbook.takeOfferToSell=Take offer to sell {0} offerbook.trader=معامله‌گر offerbook.offerersBankId=شناسه بانک سفارش‌گذار (BIC/SWIFT): {0} offerbook.offerersBankName= نام بانک سفارش‌گذار : {0} @@ -346,7 +348,7 @@ offerbook.info.sellAboveMarketPrice={0} بیشتر از قیمت روز فعلی offerbook.info.buyBelowMarketPrice={0} کمتر از قیمت روز فعلی بازار، پرداخت خواهید کرد (به روز رسانی در هر دقیقه). offerbook.info.buyAtFixedPrice=با این قیمت مقطوع خرید خواهید کرد. offerbook.info.sellAtFixedPrice=با این قیمت مقطوع، خواهید فروخت. -offerbook.info.noArbitrationInUserLanguage=در صورت اختلاف، لطفا توجه داشته باشید که داوری برای این پیشنهاد در {0} مدیریت خواهد شد. زبان در حال حاضر به {1} تنظیم شده است. +offerbook.info.noArbitrationInUserLanguage=در صورت اختلاف، لطفا توجه داشته باشید که داوری برای این پیشنهاد در {0} مدیریت خواهد شد. زبان در حال حاضر {1} تنظیم شده است. offerbook.info.roundedFiatVolume=مقدار برای حفظ حریم خصوصی شما گرد شده است. #################################################################### @@ -362,8 +364,8 @@ createOffer.amountPriceBox.sell.volumeDescription=مقدار در {0} به من createOffer.amountPriceBox.minAmountDescription=حداقل مقدار بیتکوین createOffer.securityDeposit.prompt=سپرده‌ی اطمینان در بیتکوین createOffer.fundsBox.title=پیشنهاد خود را تامین وجه نمایید -createOffer.fundsBox.offerFee=هزینه‌ی معامله -createOffer.fundsBox.networkFee=هرینه استخراج +createOffer.fundsBox.offerFee=کارمزد معامله +createOffer.fundsBox.networkFee=کارمزد استخراج createOffer.fundsBox.placeOfferSpinnerInfo=انتشار پیشنهاد در حال انجام است ... createOffer.fundsBox.paymentLabel=معامله Bisq با شناسه‌ی {0} createOffer.fundsBox.fundsStructure=({0} سپرده‌ی اطمینان، {1} هزینه‌ی معامله، {2} هزینه‌ی تراکنش شبکه) @@ -375,7 +377,7 @@ createOffer.info.sellAboveMarketPrice=شما همیشه {0}% بیشتر از ن createOffer.info.buyBelowMarketPrice=شما همیشه {0}% کمتر از نرخ روز فعلی بازار پرداخت خواهید کرد، زیرا قیمت پیشنهادتان به طور مداوم به روز رسانی خواهد شد. createOffer.warning.sellBelowMarketPrice=شما همیشه {0}% کمتر از نرخ روز فعلی بازار دریافت خواهید کرد، زیرا قیمت پیشنهادتان به طور مداوم به روز رسانی خواهد شد. createOffer.warning.buyAboveMarketPrice=شما همیشه {0}% کمتر از نرخ روز فعلی بازار پرداخت خواهید کرد، زیرا قیمت پیشنهادتان به طور مداوم به روز رسانی خواهد شد. -createOffer.tradeFee.descriptionBTCOnly=هزینه‌ی معامله +createOffer.tradeFee.descriptionBTCOnly=کارمزد معامله createOffer.tradeFee.descriptionBSQEnabled=انتخاب ارز برای کارمزد معامله createOffer.tradeFee.fiatAndPercent=≈ {1} / {0} از مبلغ معامله @@ -421,8 +423,8 @@ takeOffer.validation.amountLargerThanOfferAmountMinusFee=مقدار ورودی، takeOffer.fundsBox.title=معامله خود را تأمین وجه نمایید takeOffer.fundsBox.isOfferAvailable=بررسی کنید آیا پیشنهاد در دسترس است... takeOffer.fundsBox.tradeAmount=مبلغ فروش -takeOffer.fundsBox.offerFee=هزینه‌ی معامله -takeOffer.fundsBox.networkFee=کل هزینه استخراج +takeOffer.fundsBox.offerFee=کارمزد معامله +takeOffer.fundsBox.networkFee=کل کارمزد استخراج takeOffer.fundsBox.takeOfferSpinnerInfo=برداشتن پیشنهاد در حال انجام است... takeOffer.fundsBox.paymentLabel=معامله Bisq با شناسه‌ی {0} takeOffer.fundsBox.fundsStructure=({0} سپرده‌ی اطمینان، {1} هزینه‌ی معامله، {2} هزینه تراکنش شبکه) @@ -512,7 +514,7 @@ portfolio.pending.step2_buyer.westernUnion.extra=مورد الزامی مهم:\n portfolio.pending.step2_buyer.postal=لطفاً {0} را توسط \"US Postal Money Order\" به فروشنده‌ی بیتکوین پرداخت کنید.\n\n # suppress inspection "TrailingSpacesInProperty" portfolio.pending.step2_buyer.bank=لطفاً به صفحه‌ی وبسایت بانکداری آنلاین خود رفته و {0} را فروشنده‌ی بیتکوین پرداخت کنید.\n\n -portfolio.pending.step2_buyer.f2f=لطفا با استفاده از راه‌های ارتباطی ارائه شده توسط فروشنده با وی تماس بگیرید و قرار ملاقاتی را برای پرداخت {0} بیتکوین تنظیم کنید.\n +portfolio.pending.step2_buyer.f2f=لطفا با استفاده از راه‌های ارتباطی ارائه شده توسط فروشنده با وی تماس بگیرید و قرار ملاقاتی را برای پرداخت {0} تنظیم کنید.\n portfolio.pending.step2_buyer.startPaymentUsing=آغاز پرداخت با استفاده از {0} portfolio.pending.step2_buyer.amountToTransfer=مبلغ انتقال portfolio.pending.step2_buyer.sellersAddress=آدرس {0} فروشنده @@ -526,9 +528,9 @@ portfolio.pending.step2_buyer.moneyGramMTCNInfo.headline=شماره و رسید portfolio.pending.step2_buyer.moneyGramMTCNInfo.msg=شما باید شماره مجوز و یک عکس از رسید را با ایمیل به فروشنده‌ی بیتکوین ارسال نمایید.\nرسید باید به طور واضح نام کامل، کشور، ایالت فروشنده و مقدار را نشان دهد. ایمیل فروشنده: {0}.\nآیا شماره مجوز و قرارداد را برای فروشنده فرستادید؟ portfolio.pending.step2_buyer.westernUnionMTCNInfo.headline=MTCN و رسید را ارسال کنید portfolio.pending.step2_buyer.westernUnionMTCNInfo.msg=شما باید MTCN (شماره پیگیری) و یک عکس از رسید را با ایمیل به فروشنده‌ی بیتکوین ارسال نمایید.\nرسید باید به طور واضح نام کامل، کشور، ایالت فروشنده و مقدار را نشان دهد. ایمیل فروشنده: {0}.\n\nآیا MTCN و قرارداد را برای فروشنده فرستادید؟ -portfolio.pending.step2_buyer.halCashInfo.headline=کد HalCash را بفرستید +portfolio.pending.step2_buyer.halCashInfo.headline=ارسال کد HalCash portfolio.pending.step2_buyer.halCashInfo.msg=باید کد HalCash و شناسه‌ی معامله ({0}) را به فروشنده بیتکوین پیامک بفرستید. شماره موبایل فروشنده بیتکوین {1} است. آیا کد را برای فروشنده فرستادید؟ -portfolio.pending.step2_buyer.fasterPaymentsHolderNameInfo=بعضی از بانک‌ها ممکن است نیاز به نام دریافت کننده داشته باشند. کد ترتیب (sort) UK و شماره حساب برای انتقال سریع‌تر کفایت می‌کند و نام دریافت کننده صحت‌سنجی نمی‌شود. +portfolio.pending.step2_buyer.fasterPaymentsHolderNameInfo=ممکن است بعضی از بانک‌ها نیاز به نام دریافت کننده داشته باشند. کد UK sort و شماره حساب برای انتقال سریع‌تر کفایت می‌کند و نام دریافت کننده صحت‌سنجی نمی‌شود. portfolio.pending.step2_buyer.confirmStart.headline=تأیید کنید که پرداخت را آغاز کرده‌اید portfolio.pending.step2_buyer.confirmStart.msg=آیا شما پرداخت {0} را به شریک معاملاتی خود آغاز کردید؟ portfolio.pending.step2_buyer.confirmStart.yes=بلی، پرداخت را آغاز کرده‌ام @@ -536,7 +538,7 @@ portfolio.pending.step2_buyer.confirmStart.yes=بلی، پرداخت را آغا portfolio.pending.step2_seller.waitPayment.headline=برای پرداخت منتظر باشید portfolio.pending.step2_seller.f2fInfo.headline=اطلاعات تماس خریدار portfolio.pending.step2_seller.waitPayment.msg=تراکنش سپرده، حداقل یک تأییدیه بلاکچین دارد.شما\nباید تا آغاز پرداخت {0} از جانب خریدار بیتکوین، صبر نمایید. -portfolio.pending.step2_seller.warn=خریدار بیتکوین هنوز پرداخت {0} را انجام نداده است.\nشما باید تا آغاز پرداخت از جانب او، صبر نمایید.\nاگر معامله روی {1} تکمیل نشده است، داور بررسی خواهد کرد. +portfolio.pending.step2_seller.warn=خریدار بیت‌کوین هنوز پرداخت {0} را انجام نداده است.\nشما باید تا آغاز پرداخت از جانب او، صبر نمایید.\nاگر معامله تا {1} تکمیل نشد، داور بررسی خواهد کرد. portfolio.pending.step2_seller.openForDispute=خریدار بیتکوین پرداخت خود را آغاز نکرده است.\nحداکثر دوره‌ی زمانی مجاز برای معامله به پایان رسیده است.\nشما می توانید بیشتر صبر کرده و به همتای معامله زمان بیشتری بدهید یا برای بازگشایی یک مناقشه، با داور تماس بگیرید. # suppress inspection "UnusedProperty" @@ -554,7 +556,7 @@ message.state.FAILED=ارسال پیام ناموفق بود portfolio.pending.step3_buyer.wait.headline=برای تأییدیه‌ی پرداخت فروشنده‌ی بیتکوین منتظر باشید portfolio.pending.step3_buyer.wait.info=برای تأییدیه رسید پرداخت {0} از جانب فروشنده‌ی بیتکوین، منتظر باشید -portfolio.pending.step3_buyer.wait.msgStateInfo.label=وضعیت پیام پرداخت آغاز شد +portfolio.pending.step3_buyer.wait.msgStateInfo.label=وضعیت پیام آغاز شدن پرداخت portfolio.pending.step3_buyer.warn.part1a=بر بلاکچین {0} portfolio.pending.step3_buyer.warn.part1b=در ارائه دهنده‌ی پرداخت شما (برای مثال بانک) portfolio.pending.step3_buyer.warn.part2=فروشنده‌ی بیتکوین هنوز پرداخت شما را تأیید نکرده است.\nلطفاً {0} را بررسی کنید اگر ارسال پرداخت موفقیت آمیز بوده است.\nاگر فروشنده‌ی بیتکوین رسید پرداخت شما را تا {1} تأیید نکند، معامله توسط داور مورد بررسی قرار خواهد گرفت. @@ -562,14 +564,14 @@ portfolio.pending.step3_buyer.openForDispute=فروشنده‌ی بیتکوین # suppress inspection "TrailingSpacesInProperty" portfolio.pending.step3_seller.part=شریک معاملاتی شما تأیید کرده که پرداخت {0} را آغاز نموده است.\n\n portfolio.pending.step3_seller.altcoin.explorer=در کاوشگر بلاکچین محبوبتان {0} -portfolio.pending.step3_seller.altcoin.wallet=در والت {0} شما +portfolio.pending.step3_seller.altcoin.wallet=در کیف‌پول {0} شما portfolio.pending.step3_seller.altcoin={0} لطفا بررسی کنید {1} که آیا تراکنش مربوط به آدرس شما\n{2}\n تعداد تاییدیه‌های کافی بر روی بلاکچین دریافت کرده است یا خیر.\nمبلغ پرداخت باید {3} باشد\nشما می‌توانید آدرس {4} خود را پس از بستن پنجره از صفحه اصلی کپی کنید. portfolio.pending.step3_seller.postal={0}لطفاً بررسی کنید که آیا {1} را با \"US Postal Money Order\" از خریدار بیتکوین دریافت کرده‌اید یا خیر.\n\nشناسه معامله (متن \"دلیل پرداخت\") تراکنش: \"{2}\" -portfolio.pending.step3_seller.bank=شریک معاملاتی شما تأیید کرده که پرداخت {0} را آغاز نموده است.\n\nلطفاً به صفحه‌ی وبسایت بانکداری آنلاین خود رفته و بررسی کنید که آیا {1} را از خریدار بیتکوین دریافته کرده‌اید یا خیر.\n\nشناسه معامله (متن \"دلیل پرداخت\") تراکنش: \"{2}\"\n\n +portfolio.pending.step3_seller.bank=شریک معاملاتی شما تأیید کرده که پرداخت {0} را آغاز نموده است.\n\nلطفاً به صفحه وبسایت بانکداری آنلاین خود رفته و بررسی کنید که آیا {1} را از خریدار BTC دریافته کرده‌اید یا خیر.\n\nشناسه معامله (متن \"دلیل پرداخت\") تراکنش: \"{2}\"\n\n portfolio.pending.step3_seller.cash=چون پرداخت از طریق سپرده‌ی نقدی انجام شده است، خریدار BTC باید عبارت \"غیر قابل استرداد\" را روی رسید کاغذی بنویسد، آن را به 2 قسمت پاره کند و از طریق ایمیل به شما یک عکس ارسال کند.\n\nبه منظور اجتناب از استرداد وجه، تنها در صورتی تایید کنید که ایمیل را دریافت کرده باشید و از صحت رسید کاغذی مطمئن باشید.\nاگر مطمئن نیستید، {0} portfolio.pending.step3_seller.moneyGram=خریدار باید شماره مجوز و عکسی از رسید را به ایمیل شما ارسال کند.\nرسید باید به طور واضح نام کامل شما ، کشور، ایالت فروشنده و مقدار را نشان دهد. لطفاً ایمیل خود را بررسی کنید که آیا شماره مجوز را دریافت کرده‌اید یا خیر.\n\nپس از بستن پنجره، نام و آدرس خریدار بیتکوین را برای برداشت پول از مانی‌گرام خواهید دید.\n\nتنها پس از برداشت موفقیت آمیز پول، رسید را تأیید کنید! portfolio.pending.step3_seller.westernUnion=خریدار باید MTCN (شماره پیگیری) و عکسی از رسید را به ایمیل شما ارسال کند.\nرسید باید به طور واضح نام کامل شما، کشور، ایالت فروشنده و مقدار را نشان دهد. لطفاً ایمیل خود را بررسی کنید که آیا MTCN را دریافت کرده اید یا خیر.\nپس از بستن پنجره، نام و آدرس خریدار بیتکوین را برای برداشت پول از Western Union خواهید دید.\nتنها پس از برداشت موفقیت آمیز پول، رسید را تأیید کنید! -portfolio.pending.step3_seller.halCash=خریدار باید کد HalCash را برای شما با پیامک بفرستد. علاه‌برآن شما از HalCash پیامی را محتوی اطلاعات موردنیاز برای برداشت EUR از خودپردازهای پشتیبان HalCash دریافت خواهید کرد.\n\nپس از اینکه پول را از دستگاه خودپرداز دریافت کردید، لطفا در اینجا رسید پرداخت را تایید کنید. +portfolio.pending.step3_seller.halCash=خریدار باید کد HalCash را برای شما با پیامک بفرستد. علاوه‌ برآن شما از HalCash پیامی را محتوی اطلاعات موردنیاز برای برداشت EUR از خودپردازهای پشتیبان HalCash دریافت خواهید کرد.\n\nپس از اینکه پول را از دستگاه خودپرداز دریافت کردید، لطفا در اینجا رسید پرداخت را تایید کنید. portfolio.pending.step3_seller.bankCheck=\n\nلطفاً همچنین تأیید کنید که نام فرستنده در اظهارنامه بانک شما، با نام فرستنده در قرارداد معامله مطابقت دارد:\nنام فرستنده: {0}\nاگر نام مذکور همان نامی نیست که در اینجا نشان داده شده است، {1} portfolio.pending.step3_seller.openDispute=لطفاً تأیید نکنید بلکه یک مناقشه را با وارد کردن \"alt + o\" یا \"option + o\" باز کنید. @@ -598,9 +600,9 @@ portfolio.pending.step3_seller.onPaymentReceived.confirm.headline=تأیید ک portfolio.pending.step3_seller.onPaymentReceived.confirm.yes=بله وجه را دریافت کرده‌ام portfolio.pending.step5_buyer.groupTitle=خلاصه‌ای از معامله‌ی کامل شده -portfolio.pending.step5_buyer.tradeFee=هزینه‌ی معامله -portfolio.pending.step5_buyer.makersMiningFee=هرینه استخراج -portfolio.pending.step5_buyer.takersMiningFee=کل هزینه استخراج +portfolio.pending.step5_buyer.tradeFee=کارمزد معامله +portfolio.pending.step5_buyer.makersMiningFee=کارمزد استخراج +portfolio.pending.step5_buyer.takersMiningFee=کل کارمزد استخراج portfolio.pending.step5_buyer.refunded=سپرده اطمینان مسترد شده portfolio.pending.step5_buyer.withdrawBTC=برداشت بیتکوین شما portfolio.pending.step5_buyer.amount=مبلغ قابل برداشت @@ -613,10 +615,10 @@ portfolio.pending.step5_buyer.amountTooLow=مقدار مورد انتقال کم portfolio.pending.step5_buyer.withdrawalCompleted.headline=برداشت تکمیل شد portfolio.pending.step5_buyer.withdrawalCompleted.msg=معاملات تکمیل شده‌ی شما در \"سبد سهام/تاریخچه\" ذخیره شده است.\nشما میتوانید تمام تراکنش‌های بیتکوین خود را در \"وجوه/تراکنش‌ها\" مرور کنید. portfolio.pending.step5_buyer.bought=شما خریده‌اید -portfolio.pending.step5_buyer.paid=شما پرداخت کرده‌اید +portfolio.pending.step5_buyer.paid=پرداخت کرده‌اید -portfolio.pending.step5_seller.sold=شما فروخته‌اید -portfolio.pending.step5_seller.received=شما دریافت کرده‌اید +portfolio.pending.step5_seller.sold=فروخته‌اید +portfolio.pending.step5_seller.received=دریافت کرده‌اید tradeFeedbackWindow.title=تبریک، معامله شما کامل شد. tradeFeedbackWindow.msg.part1=دوست داریم تجربه شما را بشنویم. این امر به ما کمک می کند تا نرم افزار را بهبود بخشیم و مشکلات را حل کنیم. اگر می خواهید بازخوردی ارائه کنید، لطفا این نظرسنجی کوتاه (بدون نیاز به ثبت نام) را در زیر پر کنید: @@ -652,7 +654,7 @@ portfolio.pending.removeFailedTrade=اگر داور نتواند آن معامل portfolio.closed.completed=تکمیل شده portfolio.closed.ticketClosed=تیکت بسته شده است portfolio.closed.canceled=لغو شده است -portfolio.failed.ناموفق=ناموفق +portfolio.failed.Failed=ناموفق #################################################################### @@ -671,7 +673,7 @@ funds.deposit.fundBisqWallet=تأمین مالی کیف پول Bisq  funds.deposit.noAddresses=آدرس‌هایی برای سپرده ایجاد نشده است funds.deposit.fundWallet=تأمین مالی کیف پول شما funds.deposit.withdrawFromWallet=ارسال وجه از کیف‌پول -funds.deposit.amount=Amount in BTC (optional) +funds.deposit.amount=مبلغ به BTC (اختیاری) funds.deposit.generateAddress=ایجاد آدرس جدید funds.deposit.selectUnused=لطفاً به جای ایجاد یک آدرس جدید، یک آدرس استفاده نشده را از جدول بالا انتخاب کنید. @@ -683,7 +685,7 @@ funds.withdrawal.receiverAmount=مقدار گیرنده funds.withdrawal.senderAmount=مقدار فرستنده funds.withdrawal.feeExcluded=این مبلغ کارمزد تراکنش در شبکه را شامل نمی‌شود funds.withdrawal.feeIncluded=این مبلغ کارمزد تراکنش در شبکه را شامل می‌شود -funds.withdrawal.fromLabel=Withdraw from address +funds.withdrawal.fromLabel=برداشت از آدرس funds.withdrawal.toLabel=برداشت به آدرس funds.withdrawal.withdrawButton=برداشت انتخاب شد funds.withdrawal.noFundsAvailable=وجهی برای برداشت وجود ندارد @@ -705,8 +707,8 @@ funds.locked.locked=قفل شده به صورت چند امضایی برای م funds.tx.direction.sentTo=ارسال به: funds.tx.direction.receivedWith=دریافت با: -funds.tx.direction.genesisTx=از تراکنش بلاک Genesis: -funds.tx.txFeePaymentForBsqTx=Miner fee for BSQ tx +funds.tx.direction.genesisTx=از تراکنش پیدایش: +funds.tx.txFeePaymentForBsqTx=کارمزد استخراج برای تراکنش BSQ funds.tx.createOfferFee=سفارش‌گذار و هزینه تراکنش: {0} funds.tx.takeOfferFee=پذیرنده و هزینه تراکنش: {0} funds.tx.multiSigDeposit=سپرده چند امضایی: {0} @@ -721,8 +723,8 @@ funds.tx.noTxAvailable=هیچ تراکنشی موجود نیست funds.tx.revert=عودت funds.tx.txSent=تراکنش به طور موفقیت آمیز به یک آدرس جدید در کیف پول محلی Bisq ارسال شد. funds.tx.direction.self=ارسال شده به خودتان -funds.tx.daoTxFee=Miner fee for DAO tx -funds.tx.reimbursementRequestTxFee=Reimbursement request +funds.tx.daoTxFee=کارمزد اسخراج برای تراکنش DAO +funds.tx.reimbursementRequestTxFee=درخواست بازپرداخت funds.tx.compensationRequestTxFee=درخواست خسارت @@ -733,7 +735,7 @@ funds.tx.compensationRequestTxFee=درخواست خسارت support.tab.support=تیکت‌های پشتیبانی support.tab.ArbitratorsSupportTickets=تیکت‌های پشتیبانی داور support.tab.TradersSupportTickets=تیکت‌های پشتیبانی معامله گر -support.filter=Filter list +support.filter=لیست فیلتر support.noTickets=هیچ تیکتی به صورت باز وجود ندارد support.sendingMessage=در حال ارسال پیام ... support.receiverNotOnline=گیرنده آنلاین نیست. پیام در صندوق پستی او ذخیره شد. @@ -765,9 +767,9 @@ support.buyerOfferer=خریدار/سفارش گذار بیتکوین support.sellerOfferer=فروشنده/سفارش گذار بیتکوین support.buyerTaker=خریدار/پذیرنده‌ی بیتکوین support.sellerTaker=فروشنده/پذیرنده‌ی بیتکوین -support.backgroundInfo=Bisq is not a company, so it handles disputes differently.\n\nIf there are disputes in the trade process (e.g. one trader does not follow the trade protocol) the application will display an \"Open dispute\" button after the trade period is over for contacting the arbitrator.\n\nIf there is an issue with the application, the software will try to detect it and, if possible, display an \"Open support ticket\" button to contact the arbitrator who will forward the issue to the developers.\n\nIf you are having an issue and did not see the \"Open support ticket\" button, you can open a support ticket manually by selecting the trade causing issues under \"Portfolio/Open trades\" and hitting \"alt + o\" or \"option + o\". Please use this method only if you are sure that the software is not working as expected. If you have problems or questions, please review the FAQ on the bisq.network web page or post in the Bisq forum in the Support section. +support.backgroundInfo=Bisq یک شرکت نیست، درنتیجه روش مواجه آن با احتلافات متفاوت است.\n\nاگر اختلافی در روند معامله به وجود بیاید (مثلا یکی از معامله گران از پروتکل معامله پیروی نکند) نرم‌افزار، بعد از اتمام زمان معامله، دکمه \"ایجاد اختلاف\" را برای تماس با داور معامله نمایش می‌دهد.\n\nاگر مشکلی برای خود نرم‌افزار به وجود بیاید، خودش سعی می‌کند آن را شناسایی کند و اگر امکانش باشد دکمه \"ایجاد تیکت پشتیبانی\" را برای تماس با داور معامله نمایش می‌دهد تا او مشکل را به توسعه‌دهندگان منتقل کند.\n\nاگر مشکلی برای نرم‌افزار به وجود آمد و شما دکمه \"ایجاد تیکت پشتیبانی\" را ندیدید، برای ایجاد یک تیکت پشتیبانی به صورت دستی، معامله‌ای که ایجاد مشکل کرده است را از طریق \"سبد سهام/معاملات باز\" و فشردن کلیدهای \"alt + o\" یا \"option + o\" انتخاب کنید. لطفا تنها در صورتی از این روش استفاده کنید که مطمئن هستید نرم‌افزار آنگونه که باید عمل نکرده است. اگر مشکل یا سوالی دارید، لطفا بخش سوالات متداول را در سایت bisq.network بررسی کنید و یا آن را در تالار گفتگوی Bisq در بخش پشتیبانی مطرح کنید. -support.initialInfo=Please note the basic rules for the dispute process:\n1. You need to respond to the arbitrator's requests within 2 days.\n2. The maximum period for a dispute is 14 days.\n3. You need to cooperate with the arbitrator and provide the information they request to make your case.\n4. You accepted the rules outlined in the wiki in the user agreement when you first started the application.\n\nPlease read more about the dispute process in our wiki:\nhttps://github.com/bisq-network/exchange/wiki/Arbitration-system +support.initialInfo=لطفا این قوانین پایه‌ای را برای فرآیند اختلاف در نظر داشته باشید:\n1. شما باید حداکثر تا ۲ روز به درخواست داور پاسخ بدهید.\n2. حدکاثر دوره زمانی یک اختلاف 14 روز است.\n3. شما باید با تحویل شواهد خودتان، آنچه را که داور درخواست می‌کند برآورده سازید.\n4. هنگامی که شما برای اولین بار اقدام به استفاده از نرم‌افزار کردید، قوانین ذکر شده در ویکی در موافقتنامه کاربر را پذیرفته‌اید.\n\nلطفا جزئیات بیشتر در مورد فرآیند اختلاف را در ویکی ما بخوانید:\nhttps://github.com/bisq-network/exchange/wiki/Arbitration-system support.systemMsg=پیغام سیستم: {0} support.youOpenedTicket=درخواستی برای پشتیبانی باز کردید. support.youOpenedDispute=درخواستی برای مناقشه باز کردید.\n\n{0} @@ -783,66 +785,66 @@ settings.tab.network=اطلاعات شبکه settings.tab.about=درباره setting.preferences.general=اولویت‌های عمومی -setting.preferences.explorer=Bitcoin block explorer -setting.preferences.deviation=Max. deviation from market price -setting.preferences.avoidStandbyMode=Avoid standby mode +setting.preferences.explorer=کاوشگر بلاک بیت‌کوین +setting.preferences.deviation=حداکثر تفاوت از قیمت روز بازار +setting.preferences.avoidStandbyMode=حالت «آماده باش» را نادیده بگیر setting.preferences.deviationToLarge=مقادیر بزرگتر از {0}% مجاز نیست. -setting.preferences.txFee=Withdrawal transaction fee (satoshis/byte) +setting.preferences.txFee=کارمزد تراکنش برداشت (ساتوشی/بایت) setting.preferences.useCustomValue=استفاده از ارزش سفارشی setting.preferences.txFeeMin=کارمزد تراکنش حداقل باید {0} ساتوشی/بایت باشد setting.preferences.txFeeTooLarge=ورودی شما بالاتر از مقدار معقول (> 5000 ساتوشی/بایت) است. هزینه تراکنش معمولا در محدوده 50-400 ساتوشی / بایت است. -setting.preferences.ignorePeers=Ignore peers with onion address (comma sep.) -setting.preferences.refererId=Referral ID +setting.preferences.ignorePeers=همتایان با آدرس Onion را نادیده بگیر (جدا شده با ویرگول) +setting.preferences.refererId=شناسه ارجاع setting.preferences.refererId.prompt=شناسه ارجاع اختیاری setting.preferences.currenciesInList=ارزها در لیست قیمت روز بازار -setting.preferences.prefCurrency=Preferred currency -setting.preferences.displayFiat=Display national currencies +setting.preferences.prefCurrency=ارز مطلوب +setting.preferences.displayFiat=نمایش ارزهای ملی setting.preferences.noFiat=هیچ ارز ملی انتخاب نشده است setting.preferences.cannotRemovePrefCurrency=شما نمی‌توانید ارز مطلوب انتخاب شده‌ی خود را حذف کنید -setting.preferences.displayAltcoins=نمایش آلتکوین‌ها: +setting.preferences.displayAltcoins=نمایش آلت‌کوین‌ها setting.preferences.noAltcoins=هیچ آلتکوینی انتخاب نشده است setting.preferences.addFiat=افزودن ارز ملی setting.preferences.addAltcoin=افزودن آلتکوین setting.preferences.displayOptions=نمایش گزینه‌ها -setting.preferences.showOwnOffers=نمایش پیشنهادهای من در دفتر پیشنهاد: -setting.preferences.useAnimations=استفاده از انیمیشن‌ها: -setting.preferences.sortWithNumOffers=مرتب سازی لیست‌های بازار با تعداد معاملات/پیشنهادها: -setting.preferences.resetAllFlags=تنظیم مجدد تمام پرچم‌های \"دوباره نشان نده\": +setting.preferences.showOwnOffers=نمایش پیشنهادهای من در دفتر پیشنهاد +setting.preferences.useAnimations=استفاده از انیمیشن‌ها +setting.preferences.sortWithNumOffers=مرتب سازی لیست‌ها با تعداد معاملات/پیشنهادها +setting.preferences.resetAllFlags=تنظیم مجدد تمام پرچم‌های \"دوباره نشان نده\" setting.preferences.reset=تنظیم مجدد settings.preferences.languageChange=اعمال تغییر زبان به تمام صفحات مستلزم یک راه‌اندازی مجدد است. -settings.preferences.arbitrationLanguageWarning=در صورت اختلاف، لطفا توجه داشته باشید که داوری در {0} پردازش شده است. -settings.preferences.selectCurrencyNetwork=Select network -setting.preferences.daoOptions=DAO options -setting.preferences.dao.resync.label=Rebuild DAO state from genesis tx -setting.preferences.dao.resync.button=Resync -setting.preferences.dao.resync.popup=After an application restart the BSQ consensus state will be rebuilt from the genesis transaction. -setting.preferences.dao.isDaoFullNode=Run Bisq as DAO full node -setting.preferences.dao.rpcUser=RPC username -setting.preferences.dao.rpcPw=RPC password -setting.preferences.dao.fullNodeInfo=For running Bisq as DAO full node you need to have Bitcoin Core locally running and configured with RPC and other requirements which are documented in ''{0}''. -setting.preferences.dao.fullNodeInfo.ok=Open docs page -setting.preferences.dao.fullNodeInfo.cancel=No, I stick with lite node mode +settings.preferences.arbitrationLanguageWarning=در صورت بروز اختلاف، لطفا توجه داشته باشید که داوری در {0} انجام خواهد شد. +settings.preferences.selectCurrencyNetwork=انتخاب شبکه +setting.preferences.daoOptions=گزینه‌های DAO +setting.preferences.dao.resync.label=بازسازی وضعیت DAO از تراکنش پیدایش +setting.preferences.dao.resync.button=همگام‌سازی دوباره +setting.preferences.dao.resync.popup=بعد از راه‌اندازی مجدد نرم‌افزار، وضعیت اجماع BSQ از تراکنش پیدایش بازسازی می‌شود. +setting.preferences.dao.isDaoFullNode=Bisq را به عنوان یک گره کامل DAO اجرا کن +setting.preferences.dao.rpcUser=نام کاربری RPC +setting.preferences.dao.rpcPw=رمزعبور RPC +setting.preferences.dao.fullNodeInfo=برای اجرای Bisq به عنوان یک گره کامل DAO باید نرم‌افزار Bitcoin Core به صورت محلی اجرا شده باشد و RPC آن فعال باشد و طبق دیگر پیشنیازهایی که در مستندات ''{0}'' ذکر شده پیکربندی شده باشد. +setting.preferences.dao.fullNodeInfo.ok=باز کردن صفحه مستندات +setting.preferences.dao.fullNodeInfo.cancel=خیر، من با حالت «گره سبک» ادامه می‌دهم settings.net.btcHeader=شبکه بیتکوین settings.net.p2pHeader=شبکه همتا به همتا P2P -settings.net.onionAddressLabel=My onion address -settings.net.btcNodesLabel= استفاده از نودهای بیتکوین اختصاصی -settings.net.bitcoinPeersLabel=Connected peers -settings.net.useTorForBtcJLabel=Use Tor for Bitcoin network -settings.net.bitcoinNodesLabel=Bitcoin Core nodes to connect to +settings.net.onionAddressLabel=آدرس onion من +settings.net.btcNodesLabel=استفاده از گره‌های Bitcoin Core اختصاصی +settings.net.bitcoinPeersLabel=همتایان متصل +settings.net.useTorForBtcJLabel=استفاده از Tor برای شبکه بیت‌کوین +settings.net.bitcoinNodesLabel=گره‌های Bitcoin Core در دسترس settings.net.useProvidedNodesRadio=استفاده از نودهای بیتکوین ارائه شده settings.net.usePublicNodesRadio=استفاده از شبکه بیتکوین عمومی settings.net.useCustomNodesRadio= استفاده از نودهای بیتکوین اختصاصی settings.net.warn.usePublicNodes=اگر از شبکه عمومی بیتکوین استفاده می‌کنید، حریم خصوصی شما در معرض نودهای شبکه بیتکوین قرار می‌گیرد. این نقص ناشی از طراحی و پیاده‌سازی معیوب تکنولوژی Bloom Filter است که در کیف پول های SPV مانند BitcoinJ (که در Bisq هم استفاده می‌شود) وجود دارد. هر نود کامل بیتکوین که به آن متصل باشید می‌تواند هویت شما را با آدرس‌های کیف‌پول‌شما مرتبط بداند و این می‌تواند باعث برملا شدن هویت شما به نودهای شبکه بیتکوین شود.\nلطفاً جزئیات بیشتر را در این لینک بخوانید: https://bisq.network/blog/privacy-in-bitsquare.\n\nآیا مطمئن هستید که می‌خواهید از نودهای عمومی استفاده کنید؟ settings.net.warn.usePublicNodes.useProvided=خیر، از نودهای فراهم شده استفاده کنید. settings.net.warn.usePublicNodes.usePublic=بلی، از شبکه عمومی استفاده کنید. -settings.net.warn.useCustomNodes.B2XWarning=Please be sure that your Bitcoin node is a trusted Bitcoin Core node!\n\nConnecting to nodes which do not follow the Bitcoin Core consensus rules could corrupt your wallet and cause problems in the trade process.\n\nUsers who connect to nodes that violate consensus rules are responsible for any resulting damage. Any resulting disputes will be decided in favor of the other peer. No technical support will be given to users who ignore this warning and protection mechanisms! -settings.net.localhostBtcNodeInfo=(Background information: If you are running a local Bitcoin node (localhost) you can connect exclusively to it.) -settings.net.p2PPeersLabel=Connected peers +settings.net.warn.useCustomNodes.B2XWarning=لطفا مطمئن شوید که گره بیت‌کوین شما یک گره مورد اعتماد Bitcoin Core است!\n\nمتصل شدن به گره‌هایی که از قوانین مورد اجماع موجود در Bitcoin Core پیروی نمی‌کنند می‌تواند باعث خراب شدن کیف پول شما شود و در فرآیند معامله مشکلاتی را به وجود بیاورد.\n\nکاربرانی که از گره‌های ناقض قوانین مورد اجماع استفاده می‌کند مسئول هر گونه آسیب ایجاد شده هستند. اگر هر گونه اختلافی به وجود بیاید به نفع دیگر گره‌هایی که از قوانین مورد اجماع پیروی می‌کنند درمورد آن تصمیم گیری خواهد شد. به کاربرانی که این هشدار و سازوکار محافظتی را نادیده می‌گیرند هیچ‌گونه پشتیبانی فنی ارائه نخواهد شد! +settings.net.localhostBtcNodeInfo=(اطلاعات پیش زمینه: اگر شما یک گره محلی بیتکوین (localhost) را اجرا می‌کنید، می‌توانید به صورت انحصاری به آن متصل شوید.) +settings.net.p2PPeersLabel=همتایان متصل settings.net.onionAddressColumn=آدرس Onion settings.net.creationDateColumn=تثبیت شده settings.net.connectionTypeColumn=درون/بیرون -settings.net.totalTrafficLabel=Total traffic +settings.net.totalTrafficLabel=مجموع ترافیک settings.net.roundTripTimeColumn=تاخیر چرخشی settings.net.sentBytesColumn=ارسال شده settings.net.receivedBytesColumn=دریافت شده @@ -860,28 +862,28 @@ settings.net.inbound=وارد شونده settings.net.outbound=خارج شونده settings.net.reSyncSPVChainLabel=همگام سازی مجدد زنجیره SPV  settings.net.reSyncSPVChainButton=حذف فایل SPV  و همگام سازی مجدد -settings.net.reSyncSPVSuccess=The SPV chain file will be deleted on the next startup. You need to restart your application now.\n\nAfter the restart it can take a while to resync with the network and you will only see all transactions once the resync is completed.\n\nPlease restart again after the resync has completed because there are sometimes inconsistencies that result in incorrect balances to display. -settings.net.reSyncSPVAfterRestart=The SPV chain file has been deleted. Please be patient. It can take a while to resync with the network. +settings.net.reSyncSPVSuccess=فایل زنجیره SPV در راه اندازی بعدی حذف خواهد شد. حالا باید نرم افزار را مجدداً راه اندازی کنید.\n\nبعد از راه اندازی مجدد، همگام سازی با شبکه کمی طول می کشد و زمانی که همگام سازی مجدد تکمیل شد می‌توانید تمام تراکنش‌ها را ببینید.\n\nلطفاً پس از تکمیل همگام سازی مجدد، برنامه را باز هم راه اندازی مجدد کنید زیرا گاهی اوقات ناهماهنگی هایی وجود دارد که منجر به نمایش نادرست موجودی‌ها می‌شود. +settings.net.reSyncSPVAfterRestart=فایل زنجیره SPV حذف شده است. لطفاً صبور باشید، همگام سازی مجدد با شبکه کمی طول خواهد کشید. settings.net.reSyncSPVAfterRestartCompleted=همگام سازی مجدد هم اکنون تکمیل شده است. لطفاً برنامه را مجدداً راه اندازی نمایید. settings.net.reSyncSPVFailed=حذف فایل زنجیره SPV امکان پذیر نیست. \nخطا: {0} setting.about.aboutBisq=درباره Bisq -setting.about.about=Bisq is open-source software which facilitates the exchange of bitcoin with national currencies (and other cryptocurrencies) through a decentralized peer-to-peer network in a way that strongly protects user privacy. Learn more about Bisq on our project web page. +setting.about.about=Bisq یک پروژه منبع باز و یک شبکه غیر متمرکز از کاربرانی است که می‌خواهند بیت‌کوین را با ارزهای ملی (یا رمزارزهای جایگزین) به روشی امن تبادل کنند. در وب سایت ما با Bisq بیشتر آشنا شوید. setting.about.web=صفحه وب Bisq setting.about.code=کد منبع setting.about.agpl=مجوز AGPL setting.about.support=پشتیبانی از Bisq -setting.about.def=Bisq is not a company—it is a project open to the community. If you want to participate or support Bisq please follow the links below. +setting.about.def=Bisq یک شرکت نیست — یک پروژه اجتماعی است و برای مشارکت آزاد است. اگر می‌خواهید در آن مشارکت کنید یا از آن حمایت نمایید، لینک‌‌های زیر را دنبال کنید. setting.about.contribute=مشارکت setting.about.donate=اهدا setting.about.providers=ارائه دهندگان داده setting.about.apisWithFee=Bisq از APIهای شخص ثالث 3rd party برای قیمت های روز فیات و آلت کوین و همچنین برای برآورد هزینه تراکنش شبکه استفاده می کند. setting.about.apis=Bisq از APIهای شخص ثالث 3rd party برای قیمت های روز فیات و آلت کوین استفاده می کند. -setting.about.pricesProvided=Market prices provided by +setting.about.pricesProvided=قیمت‌های بازار ارائه شده توسط setting.about.pricesProviders={0}, {1} و {2} -setting.about.feeEstimation.label=Mining fee estimation provided by +setting.about.feeEstimation.label=برآورد کارمزد استخراج ارائه شده توسط setting.about.versionDetails=جزئیات نسخه -setting.about.version=Application version -setting.about.subsystems.label=Versions of subsystems +setting.about.version=نسخه برنامه +setting.about.subsystems.label=نسخه‌های زیرسیستم‌ها setting.about.subsystems.val=نسخه ی شبکه: {0}; نسخه ی پیام همتا به همتا: {1}; نسخه ی Local DB: {2}; نسخه پروتکل معامله: {3} @@ -892,20 +894,20 @@ setting.about.subsystems.val=نسخه ی شبکه: {0}; نسخه ی پیام ه account.tab.arbitratorRegistration=ثبت نام داور account.tab.account=حساب account.info.headline=به حساب Bisq خود خوش آمدید -account.info.msg=Here you can add trading accounts for national currencies & altcoins, select arbitrators, and create a backup of your wallet & account data.\n\nA new Bitcoin wallet was created the first time you started Bisq.\n\nWe strongly recommend that you write down your Bitcoin wallet seed words (see tab on the top) and consider adding a password before funding. Bitcoin deposits and withdrawals are managed in the \"Funds\" section.\n\nPrivacy & security note: because Bisq is a decentralized exchange, all your data is kept on your computer. There are no servers, so we have no access to your personal info, your funds, or even your IP address. Data such as bank account numbers, altcoin & Bitcoin addresses, etc are only shared with your trading partner to fulfill trades you initiate (in case of a dispute the arbitrator will see the same data as your trading peer). +account.info.msg=در اینجا شما می توانید حساب‌های معاملاتی برای ارزهای ملی و رمزارزها تنظیم کنید، داوران را انتخاب نموده و از کیف پول و اطلاعات حساب خود پشتیبان بگیرید.\n\nاولین بار که Bisq را اجرا کردید، یک کیف پول خالی بیت‌کوین ایجاد شد.\n\nما توصیه می‌کنیم که کلمات seed کیف پول بیت کوین خود را در جایی یادداشت کنید (دکمه سمت چپ را ببینید) و درنظر بگیرید که قبل ازانتقال وجه یک رمزعبور تنظیم نمایید. سپرده‌ها و برداشت‌های بیت‌کوین در بخش \"وجوه\" مدیریت می‌شوند.\n\nحریم خصوصی و امنیت: Bisq یک صرافی غیرمتمرکز است - به این معنی که تمام داده‌های شما بر روی کامپیوتر شما نگهداری می‌شود، هیچ سروری وجود ندارد و ما به اطلاعات شخصی شما، وجوه شما یا حتی آدرس IP شما دسترسی نداریم. داده‌هایی مانند شماره حساب‌های بانکی، آدرس‌های رمزارزها و بیت‌کوین و ... فقط با شریک تجاری شما برای انجام معاملاتتان به اشتراک گذاشته می‌شود (در صورت بروزاختلاف، داور اطلاعاتی مانند همتای معامله شما، مشاهده خواهد کرد). account.menu.paymentAccount=حساب های ارز ملی account.menu.altCoinsAccountView=حساب های آلت کوین account.menu.password=رمز کیف پول account.menu.seedWords=رمز پشتیبان کیف پول account.menu.backup=پشتیبان -account.menu.notifications=Notifications +account.menu.notifications=اعلان‌ها -account.arbitratorRegistration.pubKey=Public key +account.arbitratorRegistration.pubKey=کلید عمومی account.arbitratorRegistration.register=ثبت نام داور account.arbitratorRegistration.revoke=لغو ثبت نام -account.arbitratorRegistration.info.msg=Please note that you need to stay available for 15 days after revoking as there might be trades which are using you as arbitrator. The max. allowed trade period is 8 days and the dispute process might take up to 7 days. +account.arbitratorRegistration.info.msg=لطفاً توجه داشته باشید که شما باید تا 15 روز پس از لغو کردن دردسترس باشید زیرا ممکن است معاملاتی وجود داشته باشند که شما داورشان باشید. حداکثر دوره زمانی مجاز برای معامله 8 روز است و فرآیند اختلاف ممکن است تا 7 روز طول بکشد. account.arbitratorRegistration.warn.min1Language=شما باید حداقل 1 زبان را انتخاب کنید.\nما زبان پیشفرض را برای شما اضافه کردیم. account.arbitratorRegistration.removedSuccess=شما با موفقیت داورتان را از شبکه ی P2P حذف کردید. account.arbitratorRegistration.removedFailed=حذف داور امکانپذیر نیست.{0} @@ -923,22 +925,22 @@ account.arbitratorSelection.noMatchingLang=زبان مطابقی وجود ندا account.arbitratorSelection.noLang=شما می توانید داورانی را انتخاب کنید که حداقل به 1 زبان متداول صحبت می کنند. account.arbitratorSelection.minOne=شما باید حداقل یک داور را انتخاب کنید. -account.altcoin.yourAltcoinAccounts=Your altcoin accounts -account.altcoin.popup.wallet.msg=Please be sure that you follow the requirements for the usage of {0} wallets as described on the {1} web page.\nUsing wallets from centralized exchanges where (a) you don''t control your keys or (b) which don''t use compatible wallet software is risky: it can lead to loss of the traded funds!\nThe arbitrator is not a {2} specialist and cannot help in such cases. +account.altcoin.yourAltcoinAccounts=حساب‌های آلت‌کوین شما +account.altcoin.popup.wallet.msg=لطفا مطمئن شوید که الزامات استفاده از کیف پول {0} را همان طور که در صفحه {1} شرح داده شده است، رعایت می‌کنید.\nاستفاده از کیف‌پول صرافی‌های متمرکز که در آن (الف) کلید های خود را تحت کنترل ندارید و یا (ب) از یک نرم افزار کیف پول ناسازگار می‌کند می تواند منجر به از دست رفتن وجوه معامله شده شود!\nداور یک متخصص {2} نیست و در چنین مواردی نمی تواند کمک کند. account.altcoin.popup.wallet.confirm=من می فهمم و تأیید می کنم که می دانم از کدام کیف پول باید استفاده کنم. -account.altcoin.popup.xmr.msg=If you want to trade XMR on Bisq please be sure you understand and fulfill the following requirements:\n\nFor sending XMR you need to use either the official Monero GUI wallet or Monero CLI wallet with the store-tx-info flag enabled (default in new versions). Please be sure you can access the tx key as that would be required in case of a dispute.\nmonero-wallet-cli (use the command get_tx_key)\nmonero-wallet-gui (go to history tab and click on the (P) button for payment proof)\n\nIn addition to XMR checktx tool (https://xmr.llcoins.net/checktx.html) verification can also be accomplished in-wallet.\nmonero-wallet-cli : using command (check_tx_key).\nmonero-wallet-gui : on the Advanced > Prove/Check page.\nAt normal block explorers the transfer is not verifiable.\n\nYou need to provide the arbitrator the following data in case of a dispute:\n- The tx private key\n- The transaction hash\n- The recipient's public address\n\nIf you cannot provide the above data or if you used an incompatible wallet it would result in losing the dispute case. The XMR sender is responsible to be able to verify the XMR transfer to the arbitrator in case of a dispute.\n\nThere is no payment ID required, just the normal public address.\nIf you are not sure about that process visit (https://www.getmonero.org/resources/user-guides/prove-payment.html) or the Monero forum (https://forum.getmonero.org) to find more information. -account.altcoin.popup.blur.msg=If you want to trade BLUR on Bisq please be sure you understand and fulfill the following requirements:\n\nTo send BLUR you must use the Blur Network CLI or GUI Wallet. \n\nIf you are using the CLI wallet, a transaction hash (tx ID) will be displayed after a transfer is sent. You must save this information. Immediately after sending the transfer, you must use the command 'get_tx_key' to retrieve the transaction private key. If you fail to perform this step, you may not be able to retrieve the key later. \n\nIf you are using the Blur Network GUI Wallet, the transaction private key and transaction ID can be found conveniently in the "History" tab. Immediately after sending, locate the transaction of interest. Click the "?" symbol in the lower-right corner of the box containing the transaction. You must save this information. \n\nIn the event that arbitration is necessary, you must present the following to an arbitrator: 1.) the transaction ID, 2.) the transaction private key, and 3.) the recipient's address. The arbitrator will then verify the BLUR transfer using the Blur Transaction Viewer (https://blur.cash/#tx-viewer).\n\nIf you cannot provide the required information to the arbitrator, you will lose the dispute. In all cases of dispute, the BLUR sender bears 100% of the burden of responsiblity in verifying transactions to an arbitrator. \n\nIf you do not understand these requirements, do not trade on Bisq. First, seek help at the Blur Network Discord (https://discord.gg/dMWaqVW). -account.altcoin.popup.ccx.msg=If you want to trade CCX on Bisq please be sure you understand the following requirements:\n\nTo send CCX you must use an official Conceal wallet, either CLI or GUI. After sending a transfer payment, the wallets\ndisplay the transaction secret key. You must save it along with the transaction hash (ID) and the recipient's public\naddress in case arbitration is necessary. In such a case, you must give all three to the arbitrator, who will then\nverify the CCX transfer using the Conceal Transaction Viewer (https://explorer.conceal.network/txviewer).\nBecause Conceal is a privacy coin, block explorers cannot verify transfers.\n\nIf you cannot provide the required data to the arbitrator, you will lose the dispute case.\nIf you do not save the transaction secret key immediately after transferring CCX, it cannot be recovered later.\nIf you do not understand these requirements, seek help at the Conceal discord (http://discord.conceal.network). -account.altcoin.popup.drgl.msg=Trading Dragonglass on Bisq requires that you understand and fulfill the following requirements:\n\nBecause of the privacy Dragonglass provides a transaction is not verifyable on the public blockchain. If required you can prove your payment thru use of your TXN-Private-Key.\nThe TXN-Private Key is a one-time key automatically generated for every transaction that can only be accessed from within your DRGL wallet.\nEither by DRGL-wallet GUI (inside transaction details dialog) or by the Dragonglass CLI simplewallet (using command "get_tx_key").\n\nDRGL version 'Oathkeeper' and higher are REQUIRED for both.\n\nIn case of a dispute, you must provide the arbitrator the following data:\n- The TXN-Private key\n- The transaction hash\n- The recipient's public address\n\nVerification of payment can be made using the above data as inputs at \ (http://drgl.info/#check_txn).\n\nIf you cannot provide the above data or if you used an incompatible wallet it would result in losing the dispute case. The Dragonglass sender is responsible to be able to verify the DRGL transfer to the arbitrator in case of a dispute. Use of PaymentID is not required.\n\nIf you are unsure about any part of this process, visit Dragonglass on Discord (http://discord.drgl.info) for help. +account.altcoin.popup.xmr.msg=اگر میخواهید XMR را در Bisq معامله کنید، لطفا مطمئن شوید که شرایط زیر را درک کرده و انجام می دهید:\n\nبرای ارسال XMR، شما باید یا از کیف پول Monero GUI یا کیف پول Monero CLI که store-tx-info در آن فعال است (به طور پیش فرض در نسخه‌های جدید فعال است) استفاده کنید. لطفا مطمئن شوید که به کلید تراکنش دسترسی دارید چرا که در صورت بروز اختلاف به آن نیاز دارید.\nدر monero-wallet-cli از دستور(get_tx_key) استفاده کنید\n در monero-wallet-gui برای دیدن اثبات پرداخت به برگه (تاریخچه) بروید و روی دکمه (P) بزنید\nعلاوه بر ابزار XMR checktx به آدرس (https://xmr.llcoins.net/checktx.html)  تایید تراکنش از داخل کیف‌پول هم قابل انجام است.\nدر monero-wallet-cli از طریق دستور (check_tx_key) \nدر monero-wallet-gui از طریق منوی Advanced > Prove/Check\nدر کاوشگرهای بلاک عادی، انتقال قابل تایید نیست.\n\nدر صورت بروز اختلاف، باید داده های زیر را در اختیار داور بگذارید:\n- کلید خصوصی تراکنش\n- هش تراکنش\n- آدرس عمومی گیرنده\n\nاگر شما نمی توانید داده های بالا را ارائه نموده یا اگر از کیف پول ناسازگار استفاده کرده اید، این موضوع می تواند منجر به محکوم شدن در یک اختلاف شود. فرستنده ی XMR باید بتواند در صورت بروز اختلاف انتقال XMR را به داوراثبات کند.\n\nشناسه پرداخت لازم نیست، فقط آدرس عمومی معمولی.\n\nاگر شما درباره این فرآیند مطمئن نیستید به (https://www.getmonero.org/resources/user-guides/prove-payment.html) سر بزنید و یا برای کسب اطلاعات بیشتر به تالار گفتگوی مونرو (https://forum.getmonero.org) مراجعه نمایید. +account.altcoin.popup.blur.msg=اگر می‌خواهید BLUR را در Bisq معامله کنید لطفا مطمئن شوید که پیشنیازهای زیر را می‌فهمید و آنها را انجام داده‌اید:\n\nبرای ارسال BLUR باید از کیف‌پول CLI یا GUI مربوط به Blur Network استفاده کنید.\n\nاگر از یک کیف‌پول CLI استفاده می‌کنید، بعد از یک انتقال یک هش تراکنش (شناسه تراکنش) برای شما به نمایش در می‌آید. شما باید این اطلاعات را ذخیره کنید. بلافاصله بعد از ارسال یک انتقال، باید با دستور 'get_tx_key' کلید خصوصی تراکنش را بدست بیاورید. اگر موفق به انجام این مرحله نشوید، بعدا نمی‌توانید کلید را بدست بیاورید.\n\nاگر از کیف پول Blur Network GUI استفاده می‌کنید، کلید خصوصی تراکنش و شناسه تراکنش به راحتی در برگه «تاریخچه» در دسترس هستند. بلافاصله بعد از ارسال، تراکنش مورد نظر را پیدا کنید و روی نماد «؟» ذر گوشه جعبه نمایشی حاوی تراکنش کلیک کنید.\n\nاگر زمانی داوری مورد نیاز بود، باید اطلاعات زیر را به داور ارائه بدهید: 1.) شناسه تراکنش، 2.) کلید خصوصی تراکنش و 3.) آدرس گیرنده. بعد از آن، داور، انتقال را از طریق نمایشگر تراکنش Blur به آدرس (https://blur.cash/#tx-viewer) تایید می‌کند.\n\nاگر نتوانید اطلاعات مورد نیاز را به داور ارائه دهید، اختلاف به وجود آمده به ضرر شما تمام خواهد شد. در هر نوعی اختلافی که به وجود بیاید، 100% مسئولیت تایید کردن تراکنش به عهده ارسال کننده BLUR می‌باشد.\n\nاگر از این پیشنیازها سر در نمی‌آورید در Bisq معامله انجام ندهید. قبل از هر چیز در Blur Network Discord به آدرس (https://discord.gg/dMWaqVW) کمک بگیرید. +account.altcoin.popup.ccx.msg=اگر می‌خواهید CCX را در Bisq معامله کنید لطفا مطمئن شوید که پیشنیازهای زیر را متوجه شده‌اید:\n\nبرای ارسال CCX باید از یک کیف‌پول رسمی Conceal استفاده کنید که یا به صورت CLI است و یا به صورت GUI. بعد از انجام یک پرداخت، کیف‌پول‌ها کلید محرمانه تراکنش را نمایش می‌دهند.\nشما باید این کلید را به همراه هش تراکنش (شناسه) و آدرس عمومی گیرنده در جایی ذخیره کنید تا در صورت بروز اختلاف از آن استفاده کنید.\n در صورت بروز اختلاف باید هر سه این اطلاعات را به داور ارسال کنید\nتا او به کمک نمایشگر تراکنش Conceal به آدرس (https://explorer.conceal.network/txviewer) بتواند انتقال CCX را تایید کند.\nاز آنجایی که Conceal یک کوین است که سعی در حفظ حریم خصوصی دارد، کاوشگرهای بلاک قادر به تایید انتقال‌های آن نیستند.\n\nاگر نتوانید اطلاعات مورد نیاز را در اختیار داور بگذارید، در صورت بروز اختلاف، به ضرر شما تمام خواهد شد.\nاگر کلید محرمانه تراکنش را بلافاصله بعد از انتقال CCX در جایی ذخیره نکنید بعدا نمی‌توانید آن را بازیابی کنید.\nاگر از این پیشنیازها سر در نمی‌آورید از Conceal Discord به آدرس (http://discord.conceal.network) کمک بگیرید. +account.altcoin.popup.drgl.msg=معامله Dragonglass در Bisq نیازمند این است که پیشنیازهای زیر را بفهمید و انجام دهید:\n\nبا توجه به ویژگی‌های حریم خصوصی که Dragonglass در اختیار می‌گذارد تراکنش‌ها قابل تایید بر روی بلاکچین عمومی نیستند. اگر نیازبه این کار داشتید می‌توانید پرداحت خود را از طریق کلید خصوصی TXN اثبات کنید.\nکلید خصوصی TXN کلیدی است که فقط یکبار به صورت خودکار برای هر تراکنش ساخته می‌شود و فقط می‌توانید از طریق کیف پول DRGL به آن دسترسی پیدا کنید.\nیا از طریق کیف پول DRGL GUI (داخل پنجره جزئیات تراکنش) و یا از طریق کیف‌پول Dragonglass CLI simplewallet (از طریق دستور "get_tx_key").\n\nنسخه 'Oathkeeper' مربوط به DRGL یا بالاتر در هر دوی کیف‌پول‌ها مورد نیاز است.\n\nدر صورت بروز اختلاف، شما باید اطلاعات زیر را به داور ارائه بدهید:\n- کلید خصوصی TXN\n- هش تراکنش \n- آدرس عمومی گیرنده\n\nتایید پرداخت با استفاده از اطلاعات بالا از طریق (http://drgl.info/#check_txn) امکان پذیر است.\n\nاگر نتوانید اطلاعات بالا را به داور ارائه بدهید و یا اینکه از یک کیف‌پول غیر سازگار استفاده کرده باشید، اگر اختلافی رخ بدهد به ضرر شما تمام خواهد شد. فرستنده Dragonglass مسئول این است که بتواند در صورت بروز اختلاف، انتقال را به داور اثبات کند. نیازی به استفاده از PaymentID نیست.\n\nاگر در مورد هر بخش از این فرآیند مطمئن نیستید از Dragonglass درDiscord به آدرس (http://discord.drgl.info) کمک بگیرید. account.altcoin.popup.ZEC.msg=هنگام استفاده از {0} شما فقط می توانید آدرس های شفاف (که با t شروع می شوند) و نه z-addresses (خصوصی) را استفاده کنید، زیرا داور قادر به تأیید معامله با z-addresses نخواهد بود. account.altcoin.popup.XZC.msg=هنگام استفاده از {0} شما فقط می توانید از آدرس های شفاف (قابل ردیابی) استفاده کنید نه آدرس های بی نشان، زیرا داور قادر نخواهد بود تا معامله را با آدرس های غیر قابل کشف در یک مرورگر مسدود تأیید کند. account.altcoin.popup.bch=Bitcoin Cash و Bitcoin Clasics در معرض حملات بازپخش هستند. اگر از این کوین ها استفاده می کنید حتما اقدامات احتیاطی لازم را انجام دهید و همه پیامدها را متوجه شوید. شما می توانید از طریق ارسال یک کوین و ارسال ناخواسته کوین های مشابه در بلاک چین دیگر، متحمل ضرر شوید. از آنجایی که کوین های ایردراپ یا همان جایزه سابقه مشابهی با بلاک چین بیتکوین دارند، باز هم خطرات امنیتی و یک ریسک قابل ملاحظه برای از دست دادن حریم خصوصی وجود دارد.\n\nلطفا در مورد این موضوع در تالار گفتگو Bisq بیشتر بخوانید: https://forum.bisq.io/t/airdrop-coins-information-thread-bch-btg-bchc account.altcoin.popup.btg=از آنجایی که Bitcoin Gold سابقه مشابهی با بلاک چین بیتکوین دارند، باز هم خطرات امنیتی و یک ریسک قابل ملاحظه برای از دست دادن حریم خصوصی وجود دارد. اگر شما از Bitcoin Gold استفاده می کنید حتما اقدامات احتیاطی لازم را انجام دهید و همه پیامدها را متوجه شوید. \n\nلطفا در مورد این موضوع در تالار گفتگو Bisq بیشتر بخوانید: https://forum.bisq.io/t/airdrop-coins-information-thread-bch-btg-bchc -account.fiat.yourFiatAccounts=Your national currency accounts +account.fiat.yourFiatAccounts=حساب‌های ارزهای ملی شما account.backup.title=کیف پول پشتیبان -account.backup.location=Backup location +account.backup.location=محل پشتیبان‌گیری account.backup.selectLocation=انتخاب محل پشتیبان گیری account.backup.backupNow=پشتیبان گیری در حال حاضر (پشتیبان رمزگذاری نشده است!) account.backup.appDir=راهنمای داده های برنامه @@ -952,14 +954,14 @@ account.password.removePw.button=حذف رمز account.password.removePw.headline=حذف رمز محافظ برای کیف پول account.password.setPw.button=تنظیم رمز account.password.setPw.headline=تنظیم رمز محافظ برای کیف پول -account.password.info=With password protection you'll need to enter your password at application startup, when withdrawing bitcoin out of your wallet, and when restoring your wallet from seed words. +account.password.info=با محافظت رمزعبوری شما باید با هر بار اجرای برنامه، برداشت بیت‌کوین از کیف‌پول و یا بازگردانی کیف‌پول از طریق کلمات seed رمزعبور خود را وارد کنید. account.seed.backup.title=پشتیبان گیری از کلمات رمز خصوصی کیف های پول شما -account.seed.info=Please write down both wallet seed words and the date! You can recover your wallet any time with seed words and the date.\nThe same seed words are used for the BTC and BSQ wallet.\n\nYou should write down the seed words on a sheet of paper. Do not save them on your computer.\n\nPlease note that the seed words are NOT a replacement for a backup.\nYou need to create a backup of the whole application directory from the \"Account/Backup\" screen to recover application state and data.\nImporting seed words is only recommended for emergency cases. The application will not be functional without a proper backup of the database files and keys! +account.seed.info=لطفا هم کلمات seed و هم تاریخ را یادداشت کنید! شما هر زمانی که بخواهید می‌توانید کیف‌پولتان را با استفاده از کلمات seed و تاریخ بازیابی کنید.\nهمین کلمات seed برای کیف‌پول‌های BTC و BSQ هم استفاده می‌شود.\n\nشما باید کلمات seed را روی یک برگ کاغذ یادداشت کنید. آنها را روی کامپیوتر خودتان ذخیره نکنید.\n\nلطفا توجه کنید که کلمات seed جایگزینی برای یک پشتیبان نیستند.\nبرای بازیابی وضعیت و داده‌های برنامه باید از طریق صفحه \"Account/Backup\" از کل پوشه برنامه پشتیبان بسازید.\nوارد کردن کلمات seed فقط در موارد اورژانسی توصیه می‌شود. برنامه بدون پشتیبان از پایگاه داده و کلیدهای مناسب درست عمل نخواهد کرد! account.seed.warn.noPw.msg=شما یک رمز عبور کیف پول تنظیم نکرده اید که از نمایش کلمات رمز خصوصی محافظت کند.\n\nآیا می خواهید کلمات رمز خصوصی نشان داده شود؟ account.seed.warn.noPw.yes=بلی، و دوباره از من نپرس account.seed.enterPw=وارد کردن رمز عبور به منظور مشاهده ی کلمات رمز خصوصی -account.seed.restore.info=Please make a backup before applying restore from seed words. Be aware that wallet restore is only for emergency cases and might cause problems with the internal wallet database.\nIt is not a way for applying a backup! Please use a backup from the application data directory for restoring a previous application state. +account.seed.restore.info=لطفا قبل از اجرای بازگردانی از طریق کلمات seed یک نسخه پشتیبان تهیه کنید. در نظر داشته باشید بازگردانی کیف‌پول فقط برای موارد اضطراری است و ممکن است باعث به وجود آمدن مشکلاتی در پایگاه داده داخلی شود.\nبا این روش یک پشتیبان را برنگردانید! لطفا از نسخه پشتیبان از پوشه داده‌های برنامه برای بازگردانی وضعیت قبلی برنامه استفاده کنید. account.seed.restore.ok=خوب، من می فهمم و می خواهم بازگردانی کنم @@ -967,64 +969,64 @@ account.seed.restore.ok=خوب، من می فهمم و می خواهم بازگ # Mobile notifications #################################################################### -account.notifications.setup.title=Setup -account.notifications.download.label=Download mobile app -account.notifications.download.button=Download -account.notifications.waitingForWebCam=Waiting for webcam... -account.notifications.webCamWindow.headline=Scan QR-code from phone -account.notifications.webcam.label=Use webcam -account.notifications.webcam.button=Scan QR code -account.notifications.noWebcam.button=I don't have a webcam -account.notifications.testMsg.label=Send test notification -account.notifications.testMsg.title=Test -account.notifications.erase.label=Clear notifications on phone -account.notifications.erase.title=Clear notifications -account.notifications.email.label=Pairing token -account.notifications.email.prompt=Enter pairing token you received by email +account.notifications.setup.title=آماده سازی +account.notifications.download.label=بارگزاری برنامه موبایل +account.notifications.download.button=بارگزاری +account.notifications.waitingForWebCam=منتظر دوربین... +account.notifications.webCamWindow.headline=اسکن کد QR از طریق تلفن +account.notifications.webcam.label=استفاده از دوربین +account.notifications.webcam.button=اسکن کد QR +account.notifications.noWebcam.button=دوربین ندارم +account.notifications.testMsg.label=ارسال اعلان امتحانی +account.notifications.testMsg.title=امتحان کردن +account.notifications.erase.label=پاک کردن اعلان‌ها در تلفن +account.notifications.erase.title=پاک کردن اعلان‌ها +account.notifications.email.label=توکن جفت سازی +account.notifications.email.prompt=توکن جفت سازی که از طریق ایمیل دریافت کرده‌اید را وارد کنید account.notifications.settings.title=تنظیمات -account.notifications.useSound.label=Play notification sound on phone -account.notifications.trade.label=Receive trade messages -account.notifications.market.label=Receive offer alerts -account.notifications.price.label=Receive price alerts -account.notifications.priceAlert.title=Price alerts -account.notifications.priceAlert.high.label=Notify if BTC price is above -account.notifications.priceAlert.low.label=Notify if BTC price is below -account.notifications.priceAlert.setButton=Set price alert -account.notifications.priceAlert.removeButton=Remove price alert -account.notifications.trade.message.title=Trade state changed -account.notifications.trade.message.msg.conf=The deposit transaction for the trade with ID {0} is confirmed. Please open your Bisq application and start the payment. -account.notifications.trade.message.msg.started=The BTC buyer has started the payment for the trade with ID {0}. -account.notifications.trade.message.msg.completed=The trade with ID {0} is completed. -account.notifications.offer.message.title=Your offer was taken -account.notifications.offer.message.msg=Your offer with ID {0} was taken -account.notifications.dispute.message.title=New dispute message -account.notifications.dispute.message.msg=You received a dispute message for trade with ID {0} +account.notifications.useSound.label=پخش کردن صدای اعلان روی تلفن +account.notifications.trade.label=دریافت پیام‌های معامله +account.notifications.market.label=دریافت هشدارهای مربوط به پیشنهادها +account.notifications.price.label=دریافت هشدارهای مربوط به قیمت +account.notifications.priceAlert.title=هشدارهای قیمت +account.notifications.priceAlert.high.label=با خبر کردن در صورتی که قیمت BTC بالاتر باشد +account.notifications.priceAlert.low.label=با خبر کردن در صورتی که قیمت BTC پایین‌تر باشد +account.notifications.priceAlert.setButton=تنظیم هشدار قیمت +account.notifications.priceAlert.removeButton=حذف هشدار قیمت +account.notifications.trade.message.title=تغییر وضعیت معامله +account.notifications.trade.message.msg.conf=تراکنش سپرده برای معامله با شناسه {0} تایید شده است. لطفا برنامه Bisq خود را بازکنید و پرداخت را شروع کنید. +account.notifications.trade.message.msg.started=خریدار BTC پرداخت با شناسه {0} را آغاز کرده است. +account.notifications.trade.message.msg.completed=معامله با شناسه {0} انجام شد. +account.notifications.offer.message.title=پیشنهاد شما پذیرفته شد +account.notifications.offer.message.msg=پیشنهاد شما با شناسه {0} پذیرفته شد +account.notifications.dispute.message.title=پیغام جدید مربوط به اختلاف +account.notifications.dispute.message.msg=شما یک پیغام مرتبط با اختلاف برای معامله با شناسه {0} دریافت کردید -account.notifications.marketAlert.title=Offer alerts -account.notifications.marketAlert.selectPaymentAccount=Offers matching payment account -account.notifications.marketAlert.offerType.label=Offer type I am interested in -account.notifications.marketAlert.offerType.buy=Buy offers (I want to sell BTC) -account.notifications.marketAlert.offerType.sell=Sell offers (I want to buy BTC) -account.notifications.marketAlert.trigger=Offer price distance (%) -account.notifications.marketAlert.trigger.info=With a price distance set, you will only receive an alert when an offer that meets (or exceeds) your requirements is published. Example: you want to sell BTC, but you will only sell at a 2% premium to the current market price. Setting this field to 2% will ensure you only receive alerts for offers with prices that are 2% (or more) above the current market price. -account.notifications.marketAlert.trigger.prompt=Percentage distance from market price (e.g. 2.50%, -0.50%, etc) -account.notifications.marketAlert.addButton=Add offer alert -account.notifications.marketAlert.manageAlertsButton=Manage offer alerts -account.notifications.marketAlert.manageAlerts.title=Manage offer alerts -account.notifications.marketAlert.manageAlerts.label=Offer alerts -account.notifications.marketAlert.manageAlerts.item=Offer alert for {0} offer with trigger price {1} and payment account {2} -account.notifications.marketAlert.manageAlerts.header.paymentAccount=Payment account -account.notifications.marketAlert.manageAlerts.header.trigger=Trigger price +account.notifications.marketAlert.title=هشدارهای مربوط به پیشنهادها +account.notifications.marketAlert.selectPaymentAccount=پیشنهادهای مرتبط با حساب پرداخت +account.notifications.marketAlert.offerType.label=نوع پیشنهادهایی که من به آنها علاقمندم +account.notifications.marketAlert.offerType.buy=پیشنهادهای خرید (می‌خواهم BTC بفروشم) +account.notifications.marketAlert.offerType.sell=پیشنهادهای فروش (می‌خواهم BTC بخرم) +account.notifications.marketAlert.trigger=فاصله قیمتی پیشنهاد (%) +account.notifications.marketAlert.trigger.info=با تنظیم یک فاصله قیمتی، تنها در صورتی هشدار دریافت می‌کنید که پیشنهادی با پیشنیازهای شما (یا بهتر از آن) منتشر بشود. برای مثال: شما می‌خواهید BTC بفروشید، ولی می‌خواهید با 2% حق صراف نسبت به قیمت بازار آن را بفروشید. تنظیم این فیلد روی 2% به شما این اطمینان را می‌دهد که تنها بابت پیشنهادهایی هشدار دریافت کنید که حداقل 2% (یا بیشتر) بالای قیمت فعلی بازار هستند. +account.notifications.marketAlert.trigger.prompt=درصد فاصله از قیمت بازار (برای مثال 2.50%, -0.50%) +account.notifications.marketAlert.addButton=اضافه کردن هشدار برای پیشنهادها +account.notifications.marketAlert.manageAlertsButton=مدیریت هشدارهای مربوط به پیشنهادها +account.notifications.marketAlert.manageAlerts.title=مدیریت هشدارهای مربوط به پیشنهادها +account.notifications.marketAlert.manageAlerts.label=هشدارهای مربوط به پیشنهادها +account.notifications.marketAlert.manageAlerts.item=هشدار مربوط به پیشنهاد {0} با قیمت نشان‌شده {1} و حساب پرداخت {2} +account.notifications.marketAlert.manageAlerts.header.paymentAccount=حساب پرداخت +account.notifications.marketAlert.manageAlerts.header.trigger=قیمت نشان‌شده account.notifications.marketAlert.manageAlerts.header.offerType=نوع پیشنهاد -account.notifications.marketAlert.message.title=Offer alert -account.notifications.marketAlert.message.msg.below=below -account.notifications.marketAlert.message.msg.above=above -account.notifications.marketAlert.message.msg=A new ''{0} {1}'' offer with price {2} ({3} {4} market price) and payment method ''{5}'' was published to the Bisq offerbook.\nOffer ID: {6}. -account.notifications.priceAlert.message.title=Price alert for {0} -account.notifications.priceAlert.message.msg=Your price alert got triggered. The current {0} price is {1} {2} -account.notifications.noWebCamFound.warning=No webcam found.\n\nPlease use the email option to send the token and encryption key from your mobile phone to the Bisq application. -account.notifications.priceAlert.warning.highPriceTooLow=The higher price must be larger than the lower price. -account.notifications.priceAlert.warning.lowerPriceTooHigh=The lower price must be lower than the higher price. +account.notifications.marketAlert.message.title=هشدار پیشنهاد +account.notifications.marketAlert.message.msg.below=پایین +account.notifications.marketAlert.message.msg.above=بالای +account.notifications.marketAlert.message.msg=پیشنهاد جدید ''{0} {1}'' با قیمت {2} ({3} {4} قیمت بازار) و روش پرداخت ''{5}'' در دفتر پیشنهادات Bisq منتشر شده است.\nشناسه پیشنهاد: {6}. +account.notifications.priceAlert.message.title=هشدار قیمت برای {0} +account.notifications.priceAlert.message.msg=هشدار قیمت شما فعال شده است. قیمت {0} فعلی {1} {2} است +account.notifications.noWebCamFound.warning=دوبین پیدا نشد.\n\nلطفا از گزینه ایمیل برای ارسال توکن و کلید رمزنگاری از تلفن همراهتان به برنامه Bisq استفاده کنید. +account.notifications.priceAlert.warning.highPriceTooLow=قیمت بالاتر باید از قیمت پایین‌تر بزرگتر باشد. +account.notifications.priceAlert.warning.lowerPriceTooHigh=قیمت پایین‌تر باید از قیمت بالاتر کوچکتر باشد. @@ -1034,480 +1036,480 @@ account.notifications.priceAlert.warning.lowerPriceTooHigh=The lower price must #################################################################### dao.tab.bsqWallet=کیف پول BSQ  -dao.tab.proposals=Governance -dao.tab.bonding=Bonding -dao.tab.proofOfBurn=Asset listing fee/Proof of burn +dao.tab.proposals=حکمرانی +dao.tab.bonding=ضمانت +dao.tab.proofOfBurn=کارمزد ثبت دارایی/اثبات امحا dao.paidWithBsq=پرداخت شده با BSQ -dao.availableBsqBalance=Available -dao.availableNonBsqBalance=Available non-BSQ balance (BTC) -dao.unverifiedBsqBalance=Unverified (awaiting block confirmation) -dao.lockedForVoteBalance=Used for voting -dao.lockedInBonds=Locked in bonds -dao.totalBsqBalance=تراز BSQ مجموع +dao.availableBsqBalance=در دسترس +dao.availableNonBsqBalance=موجودی غیر BSQ در دسترس (BTC) +dao.unverifiedBsqBalance=تایید نشده (منتظر تاییدیه بر اساس بلاک) +dao.lockedForVoteBalance=در حال استفاده برای رای دادن +dao.lockedInBonds=قفل شده در ضمانت +dao.totalBsqBalance=مجموع موجودی BSQ dao.tx.published.success=تراکنش شما به طور موفقیت آمیز منتشر شد. dao.proposal.menuItem.make=ارائه ی پیشنهاد -dao.proposal.menuItem.browse=Browse open proposals -dao.proposal.menuItem.vote=Vote on proposals -dao.proposal.menuItem.result=Vote results -dao.cycle.headline=Voting cycle -dao.cycle.overview.headline=Voting cycle overview -dao.cycle.currentPhase=Current phase -dao.cycle.currentBlockHeight=Current block height -dao.cycle.proposal=Proposal phase -dao.cycle.blindVote=Blind vote phase -dao.cycle.voteReveal=Vote reveal phase -dao.cycle.voteResult=Vote result -dao.cycle.phaseDuration={0} blocks (≈{1}); Block {2} - {3} (≈{4} - ≈{5}) +dao.proposal.menuItem.browse=مرور طرح‌های پیشنهادی باز +dao.proposal.menuItem.vote=رای دادن به طرح‌های پیشنهادی +dao.proposal.menuItem.result=تنایج رای‌گیری +dao.cycle.headline=دوره رای‌گیری +dao.cycle.overview.headline=مرور دوره رای‌گیری +dao.cycle.currentPhase=مرحله فعلی +dao.cycle.currentBlockHeight=طول بلاک فعلی +dao.cycle.proposal=مرحله طرح پیشنهادی +dao.cycle.blindVote=مرحله رای‌گیری ناشناس +dao.cycle.voteReveal=مرحله آشکار کردن رای +dao.cycle.voteResult=تنیجه را‌ی‌گیری +dao.cycle.phaseDuration={0} بلاک (≈{1})؛ بلاک {2} - {3} (≈{4} - ≈{5}) -dao.results.cycles.header=Cycles -dao.results.cycles.table.header.cycle=Cycle -dao.results.cycles.table.header.numProposals=پیشنهادها +dao.results.cycles.header=دوره‌ها +dao.results.cycles.table.header.cycle=دوره +dao.results.cycles.table.header.numProposals=طرح‌های پیشنهادی dao.results.cycles.table.header.numVotes=آرا -dao.results.cycles.table.header.voteWeight=Vote weight +dao.results.cycles.table.header.voteWeight=وزن رای dao.results.cycles.table.header.issuance=صدور -dao.results.results.table.item.cycle=Cycle {0} started: {1} +dao.results.results.table.item.cycle=دوره {0} شروع شد: {1} -dao.results.proposals.header=Proposals of selected cycle +dao.results.proposals.header=طرح‌های پیشنهادی دوره انتخاب شده dao.results.proposals.table.header.proposalOwnerName=نام dao.results.proposals.table.header.details=جزئیات -dao.results.proposals.table.header.myVote=My vote -dao.results.proposals.table.header.result=Vote result +dao.results.proposals.table.header.myVote=رای من +dao.results.proposals.table.header.result=تنیجه را‌ی‌گیری -dao.results.proposals.voting.detail.header=Vote results for selected proposal +dao.results.proposals.voting.detail.header=نتایج رای‌گیری برای طرح پیشنهادی انتخاب شده # suppress inspection "UnusedProperty" dao.param.UNDEFINED=تعریف نشده # suppress inspection "UnusedProperty" -dao.param.DEFAULT_MAKER_FEE_BSQ=BSQ maker fee +dao.param.DEFAULT_MAKER_FEE_BSQ=کارمزد BSQ سفارش‌گذار # suppress inspection "UnusedProperty" -dao.param.DEFAULT_TAKER_FEE_BSQ=BSQ taker fee +dao.param.DEFAULT_TAKER_FEE_BSQ=کارمزد BSQ پذیرنده # suppress inspection "UnusedProperty" -dao.param.MIN_MAKER_FEE_BSQ=Min. BSQ maker fee +dao.param.MIN_MAKER_FEE_BSQ=حداقل کارمزد BSQ سفارش‌گذار # suppress inspection "UnusedProperty" -dao.param.MIN_TAKER_FEE_BSQ=Min. BSQ taker fee +dao.param.MIN_TAKER_FEE_BSQ=حداقل کارمزد BSQ پذیرنده # suppress inspection "UnusedProperty" -dao.param.DEFAULT_MAKER_FEE_BTC=BTC maker fee +dao.param.DEFAULT_MAKER_FEE_BTC=کارمزد BTC سفارش‌گذار # suppress inspection "UnusedProperty" -dao.param.DEFAULT_TAKER_FEE_BTC=BTC taker fee +dao.param.DEFAULT_TAKER_FEE_BTC=کارمزد BTC پذیرنده # suppress inspection "UnusedProperty" # suppress inspection "UnusedProperty" -dao.param.MIN_MAKER_FEE_BTC=Min. BTC maker fee +dao.param.MIN_MAKER_FEE_BTC=حداقل کارمزد BTC سفارش‌گذار # suppress inspection "UnusedProperty" -dao.param.MIN_TAKER_FEE_BTC=Min. BTC taker fee +dao.param.MIN_TAKER_FEE_BTC=حداقل کارمزد BTC پذیرنده # suppress inspection "UnusedProperty" # suppress inspection "UnusedProperty" -dao.param.PROPOSAL_FEE=Proposal fee in BSQ +dao.param.PROPOSAL_FEE=کارمزد طرح پیشنهادی به BSQ # suppress inspection "UnusedProperty" -dao.param.BLIND_VOTE_FEE=Voting fee in BSQ +dao.param.BLIND_VOTE_FEE=کارمزد رای دادن به BSQ # suppress inspection "UnusedProperty" -dao.param.COMPENSATION_REQUEST_MIN_AMOUNT=Compensation request min. BSQ amount +dao.param.COMPENSATION_REQUEST_MIN_AMOUNT=حداقل مقدار BSQ برای درخواست خسارت # suppress inspection "UnusedProperty" -dao.param.COMPENSATION_REQUEST_MAX_AMOUNT=Compensation request max. BSQ amount +dao.param.COMPENSATION_REQUEST_MAX_AMOUNT=حداکثر مقدار BSQ برای درخواست خسارت # suppress inspection "UnusedProperty" -dao.param.REIMBURSEMENT_MIN_AMOUNT=Reimbursement request min. BSQ amount +dao.param.REIMBURSEMENT_MIN_AMOUNT=حداقل مقدار BSQ برای درخواست بازپرداخت # suppress inspection "UnusedProperty" -dao.param.REIMBURSEMENT_MAX_AMOUNT=Reimbursement request max. BSQ amount +dao.param.REIMBURSEMENT_MAX_AMOUNT=حداکثر مقدار BSQ برای درخواست بازپرداخت # suppress inspection "UnusedProperty" -dao.param.QUORUM_GENERIC=Required quorum in BSQ for generic proposal +dao.param.QUORUM_GENERIC=حدنصاب مورد نیاز به BSQ برای طرح پیشنهادی کلی # suppress inspection "UnusedProperty" -dao.param.QUORUM_COMP_REQUEST=Required quorum in BSQ for compensation request +dao.param.QUORUM_COMP_REQUEST=حدنصاب مورد نیاز به BSQ برای درخواست خسارت # suppress inspection "UnusedProperty" -dao.param.QUORUM_REIMBURSEMENT=Required quorum in BSQ for reimbursement request +dao.param.QUORUM_REIMBURSEMENT=حدنصاب مورد نیاز به BSQ برای درخواست بازپرداخت # suppress inspection "UnusedProperty" -dao.param.QUORUM_CHANGE_PARAM=Required quorum in BSQ for changing a parameter +dao.param.QUORUM_CHANGE_PARAM=حدنصاب مورد نیاز به BSQ برای تغییر یک پارامتر # suppress inspection "UnusedProperty" -dao.param.QUORUM_REMOVE_ASSET=Required quorum in BSQ for removing an asset +dao.param.QUORUM_REMOVE_ASSET=حدنصاب موردنیاز به BSQ برای حذف کردن یک دارایی # suppress inspection "UnusedProperty" -dao.param.QUORUM_CONFISCATION=Required quorum in BSQ for a confiscation request +dao.param.QUORUM_CONFISCATION=حدنصاب مورد نیاز به BSQ برای درخواست یک مصادره # suppress inspection "UnusedProperty" -dao.param.QUORUM_ROLE=Required quorum in BSQ for bonded role requests +dao.param.QUORUM_ROLE=حدنصاب مورد نیاز به BSQ برای درخواست‌های نقش ضامن # suppress inspection "UnusedProperty" -dao.param.THRESHOLD_GENERIC=Required threshold in % for generic proposal +dao.param.THRESHOLD_GENERIC=آستانه مورد نیاز به % برای طرح پیشنهادی کلی # suppress inspection "UnusedProperty" -dao.param.THRESHOLD_COMP_REQUEST=Required threshold in % for compensation request +dao.param.THRESHOLD_COMP_REQUEST=آستانه مورد نیاز به % برای درخوسات خسارت # suppress inspection "UnusedProperty" -dao.param.THRESHOLD_REIMBURSEMENT=Required threshold in % for reimbursement request +dao.param.THRESHOLD_REIMBURSEMENT=آستانه مورد نیاز به % برای درخواست بازپرداخت # suppress inspection "UnusedProperty" -dao.param.THRESHOLD_CHANGE_PARAM=Required threshold in % for changing a parameter +dao.param.THRESHOLD_CHANGE_PARAM=آستانه مورد نیاز به % برای تغییر یک پارامتر # suppress inspection "UnusedProperty" -dao.param.THRESHOLD_REMOVE_ASSET=Required threshold in % for removing an asset +dao.param.THRESHOLD_REMOVE_ASSET=آستانه مورد نیاز به % برای حذف یک دارایی # suppress inspection "UnusedProperty" -dao.param.THRESHOLD_CONFISCATION=Required threshold in % for a confiscation request +dao.param.THRESHOLD_CONFISCATION=آستانه مورد نیاز به % برای درخواست یک مصادره # suppress inspection "UnusedProperty" -dao.param.THRESHOLD_ROLE=Required threshold in % for bonded role requests +dao.param.THRESHOLD_ROLE=آستانه مورد نیاز به % برای درخواست‌های نقش ضامن # suppress inspection "UnusedProperty" -dao.param.RECIPIENT_BTC_ADDRESS=Recipient BTC address +dao.param.RECIPIENT_BTC_ADDRESS=آدرس BTC گیرنده # suppress inspection "UnusedProperty" -dao.param.ASSET_LISTING_FEE_PER_DAY=Asset listing fee per day +dao.param.ASSET_LISTING_FEE_PER_DAY=کارمزد ثبت دارایی در روز # suppress inspection "UnusedProperty" -dao.param.ASSET_MIN_VOLUME=Min. trade volume +dao.param.ASSET_MIN_VOLUME=حداقل حجم معامله -dao.param.currentValue=Current value: {0} -dao.param.blocks={0} blocks +dao.param.currentValue=مقدار فعلی: {0} +dao.param.blocks={0} بلاک # suppress inspection "UnusedProperty" -dao.results.cycle.duration.label=Duration of {0} +dao.results.cycle.duration.label=زمان {0} # suppress inspection "UnusedProperty" -dao.results.cycle.duration.value={0} block(s) +dao.results.cycle.duration.value={0} بلاک # suppress inspection "UnusedProperty" -dao.results.cycle.value.postFix.isDefaultValue=(default value) +dao.results.cycle.value.postFix.isDefaultValue=(مقدار پیش‌فرض) # suppress inspection "UnusedProperty" -dao.results.cycle.value.postFix.hasChanged=(has been changed in voting) +dao.results.cycle.value.postFix.hasChanged=(در رای گیری تغییر کرده است) # suppress inspection "UnusedProperty" dao.phase.PHASE_UNDEFINED=تعریف نشده # suppress inspection "UnusedProperty" -dao.phase.PHASE_PROPOSAL=Proposal phase +dao.phase.PHASE_PROPOSAL=مرحله طرح پیشنهادی # suppress inspection "UnusedProperty" -dao.phase.PHASE_BREAK1=Break 1 +dao.phase.PHASE_BREAK1=وقفه 1 # suppress inspection "UnusedProperty" -dao.phase.PHASE_BLIND_VOTE=Blind vote phase +dao.phase.PHASE_BLIND_VOTE=مرحله رای‌گیری ناشناس # suppress inspection "UnusedProperty" -dao.phase.PHASE_BREAK2=Break 2 +dao.phase.PHASE_BREAK2=وقفه 2 # suppress inspection "UnusedProperty" -dao.phase.PHASE_VOTE_REVEAL=Vote reveal phase +dao.phase.PHASE_VOTE_REVEAL=مرحله آشکار کردن رای # suppress inspection "UnusedProperty" -dao.phase.PHASE_BREAK3=Break 3 +dao.phase.PHASE_BREAK3=وقفه 3 # suppress inspection "UnusedProperty" -dao.phase.PHASE_RESULT=Result phase +dao.phase.PHASE_RESULT=نتیجه مرحله -dao.results.votes.table.header.stakeAndMerit=Vote weight +dao.results.votes.table.header.stakeAndMerit=وزن رای dao.results.votes.table.header.stake=سهام -dao.results.votes.table.header.merit=Earned +dao.results.votes.table.header.merit=کسب شده dao.results.votes.table.header.vote=رأی -dao.bond.menuItem.bondedRoles=Bonded roles -dao.bond.menuItem.reputation=Bonded reputation -dao.bond.menuItem.bonds=Bonds +dao.bond.menuItem.bondedRoles=نقش‌های ضمانتی +dao.bond.menuItem.reputation=اعتبار ضمانتی +dao.bond.menuItem.bonds=ضمانت‌ها -dao.bond.dashboard.bondsHeadline=Bonded BSQ -dao.bond.dashboard.lockupAmount=Lockup funds -dao.bond.dashboard.unlockingAmount=Unlocking funds (wait until lock time is over) +dao.bond.dashboard.bondsHeadline=BSQ ضمانت شده +dao.bond.dashboard.lockupAmount=وجوه قفل شده +dao.bond.dashboard.unlockingAmount=رها کردن وجوه (صبر کن تا زمان قفل بودن به پایان برسد) -dao.bond.reputation.header=Lockup a bond for reputation -dao.bond.reputation.table.header=My reputation bonds -dao.bond.reputation.amount=Amount of BSQ to lockup -dao.bond.reputation.time=Unlock time in blocks -dao.bond.reputation.salt=Salt -dao.bond.reputation.hash=Hash -dao.bond.reputation.lockupButton=Lockup -dao.bond.reputation.lockup.headline=Confirm lockup transaction -dao.bond.reputation.lockup.details=Lockup amount: {0}\nLockup time: {1} block(s)\n\nAre you sure you want to proceed? -dao.bond.reputation.unlock.headline=Confirm unlock transaction -dao.bond.reputation.unlock.details=Unlock amount: {0}\nLockup time: {1} block(s)\n\nAre you sure you want to proceed? +dao.bond.reputation.header=ضمانتی را برای اعتبار قفل کن +dao.bond.reputation.table.header=ضمانت‌های اعتبار من +dao.bond.reputation.amount=مقدار BSQ برای قفل کردن +dao.bond.reputation.time=زمان رها شدن به بلاک +dao.bond.reputation.salt=داده تصادفی +dao.bond.reputation.hash=تابع درهم ساز (هش) +dao.bond.reputation.lockupButton=قفل کردن +dao.bond.reputation.lockup.headline=تایید تراکنش قفل کردن وجه +dao.bond.reputation.lockup.details=مقدار وجه قفل شده: {0}\nمدت زمان قفل ماندن: ({1}) بلاک\n\nآیا از ادامه دادن مطمئنید؟ +dao.bond.reputation.unlock.headline=تایید تراکنش رها کردن وجه +dao.bond.reputation.unlock.details=مقدار رها شدن وجه: {0}\nمدت زمان قفل شدن: ({1}) بلاک\n\nآیا از ادامه دادن مطمئنید؟ -dao.bond.allBonds.header=All bonds +dao.bond.allBonds.header=همه ضمانت‌ها -dao.bond.bondedReputation=Bonded Reputation -dao.bond.bondedRoles=Bonded roles +dao.bond.bondedReputation=اعتبار ضمانت شده +dao.bond.bondedRoles=نقش‌های ضمانت شده -dao.bond.details.header=Role details +dao.bond.details.header=جزئیات نقش dao.bond.details.role=نقش -dao.bond.details.requiredBond=Required BSQ bond -dao.bond.details.unlockTime=Unlock time in blocks -dao.bond.details.link=Link to role description -dao.bond.details.isSingleton=Can be taken by multiple role holders -dao.bond.details.blocks={0} blocks +dao.bond.details.requiredBond=ضمانت BSQ مورد نیاز +dao.bond.details.unlockTime=زمان رها شدن به بلاک +dao.bond.details.link=پیوند اینترنتی به توضیحات نقش +dao.bond.details.isSingleton=می‌تواند توسط چند نقش آفرین گرفته شود +dao.bond.details.blocks={0} بلاک dao.bond.table.column.name=نام -dao.bond.table.column.link=Link -dao.bond.table.column.bondType=Bond type +dao.bond.table.column.link=پیوند +dao.bond.table.column.bondType=نوع ضمانت dao.bond.table.column.details=جزئیات -dao.bond.table.column.lockupTxId=Lockup Tx ID -dao.bond.table.column.bondState=Bond state -dao.bond.table.column.lockTime=Lock time -dao.bond.table.column.lockupDate=Lockup date +dao.bond.table.column.lockupTxId=شناسه تراکنش قفل وجوه +dao.bond.table.column.bondState=وضعیت ضمانت +dao.bond.table.column.lockTime=زمان قفل شدن +dao.bond.table.column.lockupDate=تاریخ قفل کردن وجه -dao.bond.table.button.lockup=Lockup +dao.bond.table.button.lockup=قفل کردن dao.bond.table.button.unlock=باز کردن -dao.bond.table.button.revoke=Revoke +dao.bond.table.button.revoke=ابطال # suppress inspection "UnusedProperty" -dao.bond.bondState.READY_FOR_LOCKUP=Not bonded yet +dao.bond.bondState.READY_FOR_LOCKUP=هنوز ضمانت نشده # suppress inspection "UnusedProperty" -dao.bond.bondState.LOCKUP_TX_PENDING=Lockup pending +dao.bond.bondState.LOCKUP_TX_PENDING=در انتظار قفل کردن # suppress inspection "UnusedProperty" -dao.bond.bondState.LOCKUP_TX_CONFIRMED=Bond locked up +dao.bond.bondState.LOCKUP_TX_CONFIRMED=ضمانت قفل شده # suppress inspection "UnusedProperty" -dao.bond.bondState.UNLOCK_TX_PENDING=Unlock pending +dao.bond.bondState.UNLOCK_TX_PENDING=در انتظار رها شدن # suppress inspection "UnusedProperty" -dao.bond.bondState.UNLOCK_TX_CONFIRMED=Unlock tx confirmed +dao.bond.bondState.UNLOCK_TX_CONFIRMED=تراکنش رها شدن وجه تایید شده # suppress inspection "UnusedProperty" -dao.bond.bondState.UNLOCKING=Bond unlocking +dao.bond.bondState.UNLOCKING=رها کردن وجه ضمانتی # suppress inspection "UnusedProperty" -dao.bond.bondState.UNLOCKED=Bond unlocked +dao.bond.bondState.UNLOCKED=وجه ضمانت شده رها شده # suppress inspection "UnusedProperty" -dao.bond.bondState.CONFISCATED=Bond confiscated +dao.bond.bondState.CONFISCATED=ضمانت مصادره شده # suppress inspection "UnusedProperty" -dao.bond.lockupReason.BONDED_ROLE=Bonded role +dao.bond.lockupReason.BONDED_ROLE=نقش ضمانت شده # suppress inspection "UnusedProperty" -dao.bond.lockupReason.REPUTATION=Bonded reputation +dao.bond.lockupReason.REPUTATION=اعتبار ضمانت شده # suppress inspection "UnusedProperty" -dao.bond.bondedRoleType.GITHUB_ADMIN=Github admin +dao.bond.bondedRoleType.GITHUB_ADMIN=مدیر Github # suppress inspection "UnusedProperty" -dao.bond.bondedRoleType.FORUM_ADMIN=Forum admin +dao.bond.bondedRoleType.FORUM_ADMIN=مدیر تالار # suppress inspection "UnusedProperty" -dao.bond.bondedRoleType.TWITTER_ADMIN=Twitter admin +dao.bond.bondedRoleType.TWITTER_ADMIN=مدیر توئیتر # suppress inspection "UnusedProperty" -dao.bond.bondedRoleType.ROCKET_CHAT_ADMIN=Rocket chat admin +dao.bond.bondedRoleType.ROCKET_CHAT_ADMIN=مدیر Rocket chat # suppress inspection "UnusedProperty" -dao.bond.bondedRoleType.YOUTUBE_ADMIN=Youtube admin +dao.bond.bondedRoleType.YOUTUBE_ADMIN=مدیر یوتیوب # suppress inspection "UnusedProperty" -dao.bond.bondedRoleType.BISQ_MAINTAINER=Bisq maintainer +dao.bond.bondedRoleType.BISQ_MAINTAINER=نگهدارنده Bisq # suppress inspection "UnusedProperty" -dao.bond.bondedRoleType.WEBSITE_OPERATOR=Website operator +dao.bond.bondedRoleType.WEBSITE_OPERATOR=گرداننده سایت # suppress inspection "UnusedProperty" -dao.bond.bondedRoleType.FORUM_OPERATOR=Forum operator +dao.bond.bondedRoleType.FORUM_OPERATOR=گرداننده تالار # suppress inspection "UnusedProperty" -dao.bond.bondedRoleType.SEED_NODE_OPERATOR=Seed node operator +dao.bond.bondedRoleType.SEED_NODE_OPERATOR=گرداننده گره seed # suppress inspection "UnusedProperty" -dao.bond.bondedRoleType.PRICE_NODE_OPERATOR=Price node operator +dao.bond.bondedRoleType.PRICE_NODE_OPERATOR=گرداننده گره قیمت # suppress inspection "UnusedProperty" -dao.bond.bondedRoleType.BTC_NODE_OPERATOR=Btc node operator +dao.bond.bondedRoleType.BTC_NODE_OPERATOR=گرداننده گره BTC # suppress inspection "UnusedProperty" -dao.bond.bondedRoleType.MARKETS_OPERATOR=Markets operator +dao.bond.bondedRoleType.MARKETS_OPERATOR=گرداننده بازارها # suppress inspection "UnusedProperty" -dao.bond.bondedRoleType.BSQ_EXPLORER_OPERATOR=BSQ explorer operator +dao.bond.bondedRoleType.BSQ_EXPLORER_OPERATOR=گرداننده کاوشگر BSQ # suppress inspection "UnusedProperty" -dao.bond.bondedRoleType.DOMAIN_NAME_HOLDER=Domain name holder +dao.bond.bondedRoleType.DOMAIN_NAME_HOLDER=صاحب نام دامنه # suppress inspection "UnusedProperty" -dao.bond.bondedRoleType.DNS_ADMIN=DNS admin +dao.bond.bondedRoleType.DNS_ADMIN=مدیر DNS # suppress inspection "UnusedProperty" -dao.bond.bondedRoleType.MEDIATOR=Mediator +dao.bond.bondedRoleType.MEDIATOR=واسط # suppress inspection "UnusedProperty" -dao.bond.bondedRoleType.ARBITRATOR=Arbitrator +dao.bond.bondedRoleType.ARBITRATOR=داور -dao.burnBsq.assetFee=Asset listing fee -dao.burnBsq.menuItem.assetFee=Asset listing fee -dao.burnBsq.menuItem.proofOfBurn=Proof of burn -dao.burnBsq.header=Fee for asset listing -dao.burnBsq.selectAsset=Select Asset -dao.burnBsq.fee=Fee -dao.burnBsq.trialPeriod=Trial period -dao.burnBsq.payFee=Pay fee -dao.burnBsq.allAssets=All assets -dao.burnBsq.assets.nameAndCode=Asset name +dao.burnBsq.assetFee=کارمزد ثبت دارایی +dao.burnBsq.menuItem.assetFee=کارمزد ثبت دارایی +dao.burnBsq.menuItem.proofOfBurn=اثبات امحا +dao.burnBsq.header=کارمزد ثبت دارایی +dao.burnBsq.selectAsset=انتخاب دارایی +dao.burnBsq.fee=کارمزد +dao.burnBsq.trialPeriod=دوره زمانی امتحانی +dao.burnBsq.payFee=کارمزد پرداخت +dao.burnBsq.allAssets=همه دارایی‌ها +dao.burnBsq.assets.nameAndCode=نام دارایی dao.burnBsq.assets.state=حالت dao.burnBsq.assets.tradeVolume=حجم معامله -dao.burnBsq.assets.lookBackPeriod=Verification period -dao.burnBsq.assets.trialFee=Fee for trial period -dao.burnBsq.assets.totalFee=Total fees paid -dao.burnBsq.assets.days={0} days -dao.burnBsq.assets.toFewDays=The asset fee is too low. The min. amount of days for the trial perios is {0}. +dao.burnBsq.assets.lookBackPeriod=دوره زمانی تایید +dao.burnBsq.assets.trialFee=کارمزد دوره زمانی امتحانی +dao.burnBsq.assets.totalFee=مجموع کارمزدهای پرداختی +dao.burnBsq.assets.days={0} روز +dao.burnBsq.assets.toFewDays=کارمزد دارایی کافی نیست. حداقل مقدار برای دوره زمانی امتحانی {0} است. # suppress inspection "UnusedProperty" dao.assetState.UNDEFINED=تعریف نشده # suppress inspection "UnusedProperty" -dao.assetState.IN_TRIAL_PERIOD=In trial period +dao.assetState.IN_TRIAL_PERIOD=در دوره زمانی امتحانی # suppress inspection "UnusedProperty" -dao.assetState.ACTIVELY_TRADED=Actively traded +dao.assetState.ACTIVELY_TRADED=فعالانه در حال معامله # suppress inspection "UnusedProperty" -dao.assetState.DE_LISTED=De-listed due to inactivity +dao.assetState.DE_LISTED=حذف شده به دلیل عدم فعالیت # suppress inspection "UnusedProperty" -dao.assetState.REMOVED_BY_VOTING=Removed by voting +dao.assetState.REMOVED_BY_VOTING=حذف شده به واسطه رای گیری -dao.proofOfBurn.header=Proof of burn +dao.proofOfBurn.header=اثبات امحا dao.proofOfBurn.amount=مقدار -dao.proofOfBurn.preImage=Pre-image -dao.proofOfBurn.burn=Burn -dao.proofOfBurn.allTxs=All proof of burn transactions -dao.proofOfBurn.myItems=My proof of burn transactions +dao.proofOfBurn.preImage=پیش نسخه +dao.proofOfBurn.burn=امحا +dao.proofOfBurn.allTxs=تمام تراکنش‌های اثبات امحا +dao.proofOfBurn.myItems=تراکنش‌های اثبات امحا من dao.proofOfBurn.date=تاریخ -dao.proofOfBurn.hash=Hash +dao.proofOfBurn.hash=هش dao.proofOfBurn.txs=تراکنش‌ها -dao.proofOfBurn.pubKey=Pubkey -dao.proofOfBurn.signature.window.title=Sign a message with key from proof or burn transaction -dao.proofOfBurn.verify.window.title=Verify a message with key from proof or burn transaction -dao.proofOfBurn.copySig=Copy signature to clipboard -dao.proofOfBurn.sign=Sign -dao.proofOfBurn.message=Message -dao.proofOfBurn.sig=Signature -dao.proofOfBurn.verify=Verify -dao.proofOfBurn.verify.header=Verify message with key from proof or burn transaction -dao.proofOfBurn.verificationResult.ok=Verification succeeded -dao.proofOfBurn.verificationResult.failed=Verification failed +dao.proofOfBurn.pubKey=کلید عمومی +dao.proofOfBurn.signature.window.title=امضا کردن یک با کلید تراکنش اثبات امحا +dao.proofOfBurn.verify.window.title=تایید کردن یک با کلید تراکنش اثبات امحا +dao.proofOfBurn.copySig=کپی کردن امضا به حافظه موقت +dao.proofOfBurn.sign=امضا کردن +dao.proofOfBurn.message=پیام +dao.proofOfBurn.sig=امضا +dao.proofOfBurn.verify=تایید کردن +dao.proofOfBurn.verify.header=پیام را با کلید تراکنش اثبات امحا تایید کنید +dao.proofOfBurn.verificationResult.ok=تایید با موفقیت انجام شد +dao.proofOfBurn.verificationResult.failed=تایید نا موفق بود # suppress inspection "UnusedProperty" dao.phase.UNDEFINED=تعریف نشده # suppress inspection "UnusedProperty" -dao.phase.PROPOSAL=Proposal phase +dao.phase.PROPOSAL=مرحله طرح پیشنهادی # suppress inspection "UnusedProperty" -dao.phase.BREAK1=Break before blind vote phase +dao.phase.BREAK1=وقفه قبل از مرحله رای‌گیری ناشناس # suppress inspection "UnusedProperty" -dao.phase.BLIND_VOTE=Blind vote phase +dao.phase.BLIND_VOTE=مرحله رای‌گیری ناشناس # suppress inspection "UnusedProperty" -dao.phase.BREAK2=Break before vote reveal phase +dao.phase.BREAK2=وقفه قبل از مرحله آشکارسازی رای # suppress inspection "UnusedProperty" -dao.phase.VOTE_REVEAL=Vote reveal phase +dao.phase.VOTE_REVEAL=مرحله آشکار کردن رای # suppress inspection "UnusedProperty" -dao.phase.BREAK3=Break before result phase +dao.phase.BREAK3=وقفه قبل از مرحله اعلام نتایج # suppress inspection "UnusedProperty" -dao.phase.RESULT=Vote result phase +dao.phase.RESULT=مرحله نتایج رای‌گیری # suppress inspection "UnusedProperty" -dao.phase.separatedPhaseBar.PROPOSAL=Proposal phase +dao.phase.separatedPhaseBar.PROPOSAL=مرحله طرح پیشنهادی # suppress inspection "UnusedProperty" -dao.phase.separatedPhaseBar.BLIND_VOTE=Blind vote +dao.phase.separatedPhaseBar.BLIND_VOTE=رای ناشناس # suppress inspection "UnusedProperty" dao.phase.separatedPhaseBar.VOTE_REVEAL=آشکارسازی رأی # suppress inspection "UnusedProperty" -dao.phase.separatedPhaseBar.RESULT=Vote result +dao.phase.separatedPhaseBar.RESULT=تنیجه را‌ی‌گیری # suppress inspection "UnusedProperty" dao.proposal.type.COMPENSATION_REQUEST=درخواست خسارت # suppress inspection "UnusedProperty" -dao.proposal.type.REIMBURSEMENT_REQUEST=Reimbursement request +dao.proposal.type.REIMBURSEMENT_REQUEST=درخواست بازپرداخت # suppress inspection "UnusedProperty" -dao.proposal.type.BONDED_ROLE=Proposal for a bonded role +dao.proposal.type.BONDED_ROLE=طرح پیشنهادی برای یک نقش ضمانتی # suppress inspection "UnusedProperty" -dao.proposal.type.REMOVE_ASSET=Proposal for removing an asset +dao.proposal.type.REMOVE_ASSET=طرح پیشنهادی برای حذف کردن یک دارایی # suppress inspection "UnusedProperty" -dao.proposal.type.CHANGE_PARAM=پیشنهاد برای تغییر یک پارامتر +dao.proposal.type.CHANGE_PARAM=طرح پیشنهادی برای تغییر یک پارامتر # suppress inspection "UnusedProperty" dao.proposal.type.GENERIC=پیشنهاد عمومی # suppress inspection "UnusedProperty" -dao.proposal.type.CONFISCATE_BOND=Proposal for confiscating a bond +dao.proposal.type.CONFISCATE_BOND=طرح پیشنهادی برای مصادره کردن یک ضمانت # suppress inspection "UnusedProperty" dao.proposal.type.short.COMPENSATION_REQUEST=درخواست خسارت # suppress inspection "UnusedProperty" -dao.proposal.type.short.REIMBURSEMENT_REQUEST=Reimbursement request +dao.proposal.type.short.REIMBURSEMENT_REQUEST=درخواست بازپرداخت # suppress inspection "UnusedProperty" -dao.proposal.type.short.BONDED_ROLE=Bonded role +dao.proposal.type.short.BONDED_ROLE=نقش ضمانت شده # suppress inspection "UnusedProperty" -dao.proposal.type.short.REMOVE_ASSET=Removing an altcoin +dao.proposal.type.short.REMOVE_ASSET=حذف یک آلت‌کوین # suppress inspection "UnusedProperty" -dao.proposal.type.short.CHANGE_PARAM=Changing a parameter +dao.proposal.type.short.CHANGE_PARAM=تغییر یک پارامتر # suppress inspection "UnusedProperty" -dao.proposal.type.short.GENERIC=پیشنهاد عمومی +dao.proposal.type.short.GENERIC=پیشنهاد کلی # suppress inspection "UnusedProperty" -dao.proposal.type.short.CONFISCATE_BOND=Confiscating a bond +dao.proposal.type.short.CONFISCATE_BOND=مصادره کردن یک ضمانت dao.proposal.details=جزئیات پیشنهاد dao.proposal.selectedProposal=پیشنهادهای انتخاب شده -dao.proposal.active.header=Proposals of current cycle -dao.proposal.active.remove.confirm=Are you sure you want to remove that proposal?\nThe already paid proposal fee will be lost. -dao.proposal.active.remove.doRemove=Yes, remove my proposal +dao.proposal.active.header=طرح‌های پیشنهادی برای دوره فعلی +dao.proposal.active.remove.confirm=آیا از حذف کردن آن طرح پیشنهادی مطمئنید؟\nکارمزد طرح پیشنهادی که قبلا پرداخت شده است از بین خواهد رفت. +dao.proposal.active.remove.doRemove=بله، طرح پیشنهادی من را حذف کن dao.proposal.active.remove.failed=نمی توان پیشنهاد را حذف کرد. dao.proposal.myVote.accept=قبول پیشنهاد dao.proposal.myVote.reject=رد پیشنهاد -dao.proposal.myVote.removeMyVote=Ignore proposal -dao.proposal.myVote.merit=Vote weight from earned BSQ -dao.proposal.myVote.stake=Vote weight from stake -dao.proposal.myVote.blindVoteTxId=Blind vote transaction ID -dao.proposal.myVote.revealTxId=Vote reveal transaction ID -dao.proposal.myVote.stake.prompt=Max. available balance for voting: {0} -dao.proposal.votes.header=رأی به تمام پیشنهادها -dao.proposal.votes.header.voted=My vote +dao.proposal.myVote.removeMyVote=نادیده گرفتن طرح پیشنهادی +dao.proposal.myVote.merit=وزن رای به سبب مقدار BSQ بدست آورده +dao.proposal.myVote.stake=وزن رای به سبب سهام +dao.proposal.myVote.blindVoteTxId=شناسه تراکنش رای ناشناس +dao.proposal.myVote.revealTxId=شناسه تراکنش آشکاری سازی رای +dao.proposal.myVote.stake.prompt=حداکثر موجودی در دسترس برای رای دادن: {0} +dao.proposal.votes.header=رأی به تمام طرح‌های پیشنهادی +dao.proposal.votes.header.voted=رای من dao.proposal.myVote.button=رأی به تمام پیشنهادها dao.proposal.create.selectProposalType=انتخاب نوع پیشنهاد dao.proposal.create.proposalType=نوع پیشنهاد dao.proposal.create.createNew=ارائه ی پیشنهاد جدید dao.proposal.create.create.button=ارائه ی پیشنهاد -dao.proposal=proposal -dao.proposal.display.type=نوع پیشنهاد -dao.proposal.display.name=Name/nickname -dao.proposal.display.link=Link to detail info -dao.proposal.display.link.prompt=Link to Github issue -dao.proposal.display.requestedBsq=Requested amount in BSQ -dao.proposal.display.bsqAddress=BSQ address -dao.proposal.display.txId=Proposal transaction ID -dao.proposal.display.proposalFee=Proposal fee -dao.proposal.display.myVote=My vote -dao.proposal.display.voteResult=Vote result summary -dao.proposal.display.bondedRoleComboBox.label=Bonded role type -dao.proposal.display.requiredBondForRole.label=Required bond for role -dao.proposal.display.tickerSymbol.label=Ticker Symbol -dao.proposal.display.option=Option +dao.proposal=طرح پیشنهادی +dao.proposal.display.type=نوع طرح پیشنهادی +dao.proposal.display.name=نام/نام مستعار +dao.proposal.display.link=پیوند به اطلاعات جزئی +dao.proposal.display.link.prompt=پیوند به Github issue +dao.proposal.display.requestedBsq=مبلغ درخواستی به BSQ +dao.proposal.display.bsqAddress=آدرس BSQ +dao.proposal.display.txId=شناسه تراکنش طرح پیشنهادی +dao.proposal.display.proposalFee=کارمزد طرح پیشنهادی +dao.proposal.display.myVote=رای من +dao.proposal.display.voteResult=خلاصه نتایج رای‌گیری +dao.proposal.display.bondedRoleComboBox.label=نوع نقش ضمانت شده +dao.proposal.display.requiredBondForRole.label=ضمانت مورد نیاز برای نقش +dao.proposal.display.tickerSymbol.label=نماد +dao.proposal.display.option=گزینه -dao.proposal.table.header.proposalType=نوع پیشنهاد -dao.proposal.table.header.link=Link -dao.proposal.table.header.myVote=My vote +dao.proposal.table.header.proposalType=نوع طرح پیشنهادی +dao.proposal.table.header.link=پیوند +dao.proposal.table.header.myVote=رای من dao.proposal.table.header.remove=حذف -dao.proposal.table.icon.tooltip.removeProposal=Remove my proposal -dao.proposal.table.icon.tooltip.changeVote=Current vote: ''{0}''. Change vote to: ''{1}'' +dao.proposal.table.icon.tooltip.removeProposal=طرح پیشنهادی من را حذف کن +dao.proposal.table.icon.tooltip.changeVote=رای فعلی: ''{0}''. تغییر رای به: ''{1}'' -dao.proposal.display.myVote.accepted=Accepted -dao.proposal.display.myVote.rejected=Rejected -dao.proposal.display.myVote.ignored=Ignored -dao.proposal.myVote.summary=Voted: {0}; Vote weight: {1} (earned: {2} + stake: {3}); +dao.proposal.display.myVote.accepted=قبول شده +dao.proposal.display.myVote.rejected=رد شده +dao.proposal.display.myVote.ignored=نادیده گرفته شده +dao.proposal.myVote.summary=رای: {0}؛ وزن رای: {1} (بدست آمده: {2} + سهام: {3})؛ -dao.proposal.voteResult.success=Accepted -dao.proposal.voteResult.failed=Rejected -dao.proposal.voteResult.summary=Result: {0}; Threshold: {1} (required > {2}); Quorum: {3} (required > {4}) +dao.proposal.voteResult.success=قبول شده +dao.proposal.voteResult.failed=رد شده +dao.proposal.voteResult.summary=نتیجه: {0}؛ آستانه: {1} (مورد نیاز > {2})؛ حدنصاب: {3} (مورد نیاز > {4}) -dao.proposal.display.paramComboBox.label=Select parameter to change -dao.proposal.display.paramValue=Parameter value +dao.proposal.display.paramComboBox.label=پارامتری برای تغییر انتخاب کنید +dao.proposal.display.paramValue=مقدار پارامتر -dao.proposal.display.confiscateBondComboBox.label=Choose bond -dao.proposal.display.assetComboBox.label=Asset to remove +dao.proposal.display.confiscateBondComboBox.label=انتخاب ضمانت +dao.proposal.display.assetComboBox.label=دارایی مورد حذف -dao.blindVote=blind vote +dao.blindVote=رای ناشناس -dao.blindVote.startPublishing=Publishing blind vote transaction... -dao.blindVote.success=Your blind vote has been successfully published. +dao.blindVote.startPublishing=در حال انتشار تراکنش رای ناشناس... +dao.blindVote.success=رای ناشناس شما با موفقیت منتشر شد. dao.wallet.menuItem.send=ارسال dao.wallet.menuItem.receive=دریافت dao.wallet.menuItem.transactions=تراکنش ها -dao.wallet.dashboard.myBalance=My wallet balance -dao.wallet.dashboard.distribution=Distribution of all BSQ -dao.wallet.dashboard.locked=Global state of locked BSQ -dao.wallet.dashboard.market=Market data -dao.wallet.dashboard.genesis=تراکنش جنسیس -dao.wallet.dashboard.txDetails=BSQ transactions statistics -dao.wallet.dashboard.genesisBlockHeight=Genesis block height -dao.wallet.dashboard.genesisTxId=Genesis transaction ID -dao.wallet.dashboard.genesisIssueAmount=BSQ issued at genesis transaction -dao.wallet.dashboard.compRequestIssueAmount=BSQ issued for compensation requests -dao.wallet.dashboard.reimbursementAmount=BSQ issued for reimbursement requests -dao.wallet.dashboard.availableAmount=Total available BSQ -dao.wallet.dashboard.burntAmount=Burned BSQ (fees) -dao.wallet.dashboard.totalLockedUpAmount=Locked up in bonds -dao.wallet.dashboard.totalUnlockingAmount=Unlocking BSQ from bonds -dao.wallet.dashboard.totalUnlockedAmount=Unlocked BSQ from bonds -dao.wallet.dashboard.totalConfiscatedAmount=Confiscated BSQ from bonds -dao.wallet.dashboard.allTx=No. of all BSQ transactions -dao.wallet.dashboard.utxo=No. of all unspent transaction outputs -dao.wallet.dashboard.compensationIssuanceTx=No. of all compensation request issuance transactions -dao.wallet.dashboard.reimbursementIssuanceTx=No. of all reimbursement request issuance transactions -dao.wallet.dashboard.burntTx=No. of all fee payments transactions -dao.wallet.dashboard.price=Latest BSQ/BTC trade price (in Bisq) -dao.wallet.dashboard.marketCap=Market capitalisation (based on trade price) +dao.wallet.dashboard.myBalance=موجودی کیف‌پول من +dao.wallet.dashboard.distribution=توزیع تمام BSQ +dao.wallet.dashboard.locked=وضعیت جهانی BSQ های قفل شده +dao.wallet.dashboard.market=داده‌های بازار +dao.wallet.dashboard.genesis=تراکنش پیدایش +dao.wallet.dashboard.txDetails=آمار تراکنش‌های BSQ +dao.wallet.dashboard.genesisBlockHeight=طول بلاک پیدایش +dao.wallet.dashboard.genesisTxId=شناسه تراکنش پیدایش +dao.wallet.dashboard.genesisIssueAmount=BSQ صادر شده در تراکنش پیدایش +dao.wallet.dashboard.compRequestIssueAmount=BSQ صادر شده برای درخواست‌های مصادره +dao.wallet.dashboard.reimbursementAmount=BSQ صادر شده برای درخواست‌های بازپرداخت +dao.wallet.dashboard.availableAmount=مجموع BSQ در دسترس +dao.wallet.dashboard.burntAmount=BSQ امحا شده (کارمزدها) +dao.wallet.dashboard.totalLockedUpAmount=قفل شده در ضمانت‌ها +dao.wallet.dashboard.totalUnlockingAmount=رها کردن BSQ از ضمانت‌ها +dao.wallet.dashboard.totalUnlockedAmount=BSQ رها شده از ضمانت‌ها +dao.wallet.dashboard.totalConfiscatedAmount=BSQ مصادره شده از ضمانت‌ها +dao.wallet.dashboard.allTx=تعداد تمام تراکنش‌های BSQ +dao.wallet.dashboard.utxo=تعداد تمام خروجی تراکنش‌های خرج نشده +dao.wallet.dashboard.compensationIssuanceTx=تعداد تمام تراکنش‌های صدور درخواست مصادره +dao.wallet.dashboard.reimbursementIssuanceTx=تعداد تمام تراکنش‌های صدور درخواست بازپرداخت +dao.wallet.dashboard.burntTx=تعداد تمام تراکنش‌های کارمزد پرداخت +dao.wallet.dashboard.price=آخرین قیمت معاملاتی BSQ/BTC (به Bisq) +dao.wallet.dashboard.marketCap=ارزش بازار (بر مبنای قیمت معاملاتی) dao.wallet.receive.fundYourWallet=تأمین مالی کیف پول BSQ خودتان -dao.wallet.receive.bsqAddress=BSQ wallet address +dao.wallet.receive.bsqAddress=آدرس کیف‌پول BSQ dao.wallet.send.sendFunds=ارسال وجوه -dao.wallet.send.sendBtcFunds=Send non-BSQ funds (BTC) -dao.wallet.send.amount=Amount in BSQ -dao.wallet.send.btcAmount=Amount in BTC (non-BSQ funds) +dao.wallet.send.sendBtcFunds=ارسال وجوه غیر BSQ (به BTC) +dao.wallet.send.amount=مقدار به BSQ +dao.wallet.send.btcAmount=مقدار به BTC (وجوه غیر BSQ) dao.wallet.send.setAmount=تعیین مبلغ به منظور برداشت (حداقل مبلغ {0} است) -dao.wallet.send.setBtcAmount=Set amount in BTC to withdraw (min. amount is {0}) -dao.wallet.send.receiverAddress=Receiver's BSQ address -dao.wallet.send.receiverBtcAddress=Receiver's BTC address +dao.wallet.send.setBtcAmount=تنظیم مقدار برداشت به BTC (حداقل مقدار {0} است) +dao.wallet.send.receiverAddress=آدرس BSQ گیرنده +dao.wallet.send.receiverBtcAddress=آدرس BTC گیرنده dao.wallet.send.setDestinationAddress=آدرس مقصد خود را پر کنید dao.wallet.send.send=ارسال وجوه BSQ  -dao.wallet.send.sendBtc=Send BTC funds +dao.wallet.send.sendBtc=ارسال وجوه BTC dao.wallet.send.sendFunds.headline=تأیید درخواست برداشت dao.wallet.send.sendFunds.details=در حال ارسال: {0} به آدرس گیرنده ی: {1} . \nهزینه لازم برای معامله عبارت است از: {2} ({3} ساتوشی/ بایت)\nاندازه تراکنش: {4} کیلوبایت\n\n دریافت کننده {5} دریافت خواهد کرد\n\n آیا شما مطمئن هستید که می خواهید این مبلغ را برداشت کنید؟ -dao.wallet.chainHeightSynced=Latest verified block: {0} -dao.wallet.chainHeightSyncing=Awaiting blocks... Verified {0} blocks out of {1} +dao.wallet.chainHeightSynced=آخرین بلاک تایید شده: {0} +dao.wallet.chainHeightSyncing=منتظر بلاک‌ها... {0} تا از {1} بلاک تایید شده است dao.wallet.tx.type=نوع # suppress inspection "UnusedProperty" @@ -1529,29 +1531,29 @@ dao.tx.type.enum.PAY_TRADE_FEE=هزینه ی معامله # suppress inspection "UnusedProperty" dao.tx.type.enum.COMPENSATION_REQUEST=هزینه برای درخواست خسارت # suppress inspection "UnusedProperty" -dao.tx.type.enum.REIMBURSEMENT_REQUEST=Fee for reimbursement request +dao.tx.type.enum.REIMBURSEMENT_REQUEST=کارمزد درخواست بازپرداخت # suppress inspection "UnusedProperty" dao.tx.type.enum.PROPOSAL=هزینه برای پیشنهاد # suppress inspection "UnusedProperty" -dao.tx.type.enum.BLIND_VOTE=هزینه برای رأی کور +dao.tx.type.enum.BLIND_VOTE=کارمزد برای رای ناشناس # suppress inspection "UnusedProperty" dao.tx.type.enum.VOTE_REVEAL=آشکارسازی رأی # suppress inspection "UnusedProperty" -dao.tx.type.enum.LOCKUP=Lock up bond +dao.tx.type.enum.LOCKUP=قفل کردن ضمانت # suppress inspection "UnusedProperty" -dao.tx.type.enum.UNLOCK=Unlock bond +dao.tx.type.enum.UNLOCK=رها سازی ضمانت # suppress inspection "UnusedProperty" -dao.tx.type.enum.ASSET_LISTING_FEE=Asset listing fee +dao.tx.type.enum.ASSET_LISTING_FEE=کارمزد ثبت دارایی # suppress inspection "UnusedProperty" -dao.tx.type.enum.PROOF_OF_BURN=Proof of burn +dao.tx.type.enum.PROOF_OF_BURN=اثبات امحا dao.tx.issuanceFromCompReq=درخواست/صدور خسارت -dao.tx.issuanceFromCompReq.tooltip=درخواست خسارت که منجر به یک صدور BSQ جدید می شود.\nتاریخ صدور: {0} -dao.tx.issuanceFromReimbursement=Reimbursement request/issuance -dao.tx.issuanceFromReimbursement.tooltip=Reimbursement request which led to an issuance of new BSQ.\nIssuance date: {0} +dao.tx.issuanceFromCompReq.tooltip=درخواست خسارت که منجر به صدور BSQ جدید می‌شود.\nتاریخ صدور: {0} +dao.tx.issuanceFromReimbursement=درخواست/صدور بازپرداخت +dao.tx.issuanceFromReimbursement.tooltip=درخواست بازپرداختی که منجر به صدور BSQ جدید می‌شود.\nتاریخ صدور: {0} dao.proposal.create.missingFunds=شما وجوه کافی برای ایجاد پیشنهاد را ندارید.\nمقدار مورد نیاز: {0} -dao.feeTx.confirm=Confirm {0} transaction -dao.feeTx.confirm.details={0} fee: {1}\nMining fee: {2} ({3} Satoshis/byte)\nTransaction size: {4} Kb\n\nAre you sure you want to publish the {5} transaction? +dao.feeTx.confirm=تایید {0} تراکنش +dao.feeTx.confirm.details=کارمزد {0}: {1}\nکارمزد استخراج: {2} ({3} ساتوشی بر بایت)\nاندازه تراکنش: {4} Kb\n\nآیا از انتشار تراکنش {5} اطمینان دارید؟ #################################################################### @@ -1559,11 +1561,11 @@ dao.feeTx.confirm.details={0} fee: {1}\nMining fee: {2} ({3} Satoshis/byte)\nTra #################################################################### contractWindow.title=جزئیات مناقشه -contractWindow.dates=Offer date / Trade date -contractWindow.btcAddresses=Bitcoin address BTC buyer / BTC seller -contractWindow.onions=Network address BTC buyer / BTC seller -contractWindow.numDisputes=No. of disputes BTC buyer / BTC seller -contractWindow.contractHash=Contract hash +contractWindow.dates=تاریخ پیشنهاد / تاریخ معامله +contractWindow.btcAddresses=آدرس بیت‌کوین خریدار BTC / فروشنده BTC +contractWindow.onions=آدرس شبکه خریدار BTC / فروشنده BTC +contractWindow.numDisputes=تعداد اختلافات خریدار BTC / فروشنده BTC +contractWindow.contractHash=هش قرارداد displayAlertMessageWindow.headline=اطلاعات مهم! displayAlertMessageWindow.update.headline=اطلاعات به روز مهم! @@ -1585,21 +1587,21 @@ displayUpdateDownloadWindow.success=نسخه ی جدید به طور موفقی displayUpdateDownloadWindow.download.openDir=باز کردن راهنمای دانلود disputeSummaryWindow.title=خلاصه -disputeSummaryWindow.openDate=Ticket opening date -disputeSummaryWindow.role=Trader's role -disputeSummaryWindow.evidence=Evidence +disputeSummaryWindow.openDate=تاریخ ایجاد تیکت +disputeSummaryWindow.role=نقش معامله گر +disputeSummaryWindow.evidence=شواهد disputeSummaryWindow.evidence.tamperProof=شواهد اثبات رشوه: disputeSummaryWindow.evidence.id=اعتبارسنجی شناسه disputeSummaryWindow.evidence.video=ویدئو/ فیلم از صفحه -disputeSummaryWindow.payout=Trade amount payout +disputeSummaryWindow.payout=پرداختی مقدار معامله disputeSummaryWindow.payout.getsTradeAmount=BTC {0} پرداختی مبلغ معامله را دریافت می کند disputeSummaryWindow.payout.getsAll=BTC {0} همه را دریافت می کند disputeSummaryWindow.payout.custom=پرداخت سفارشی disputeSummaryWindow.payout.adjustAmount=مقدار وارد شده بیش از مقدار موجود {0} است. \nما این بخش ورودی را به حداکثر مقدار ممکن تنظیم می کنیم. -disputeSummaryWindow.payoutAmount.buyer=Buyer's payout amount -disputeSummaryWindow.payoutAmount.seller=Seller's payout amount -disputeSummaryWindow.payoutAmount.invert=Use loser as publisher -disputeSummaryWindow.reason=Reason of dispute +disputeSummaryWindow.payoutAmount.buyer=مقدار پرداختی خریدار +disputeSummaryWindow.payoutAmount.seller=مقدار پرداختی فروشنده +disputeSummaryWindow.payoutAmount.invert=استفاده از بازنده به عنوان منتشر کننده +disputeSummaryWindow.reason=دلیل اختلاف disputeSummaryWindow.reason.bug=اشکال disputeSummaryWindow.reason.usability=قابلیت استفاده disputeSummaryWindow.reason.protocolViolation=نقض پروتکل @@ -1607,18 +1609,18 @@ disputeSummaryWindow.reason.noReply=بدون پاسخ disputeSummaryWindow.reason.scam=کلاهبرداری disputeSummaryWindow.reason.other=سایر disputeSummaryWindow.reason.bank=بانک -disputeSummaryWindow.summaryNotes=Summary notes +disputeSummaryWindow.summaryNotes=نکات خلاصه disputeSummaryWindow.addSummaryNotes=افزودن نکات خلاصه disputeSummaryWindow.close.button=بستن تیکت disputeSummaryWindow.close.msg=تیکت در {0} بسته شد.\n\nخلاصه:\n{1} شواهد اثبات رشوه را تحویل داد: {2}\n{3} اعتبارسنجی شناسه را انجام داد: {4}\n{5} یک ویدئو یا اسکرین کست انجام داد: {6}\nمبلغ پرداختی برای خریدار بیتکوین: {7}\nمبلغ پرداختی برای فروشنده بیتکوین: {8}\n\nنکات خلاصه:\n{9} disputeSummaryWindow.close.closePeer=شما باید همچنین تیکت همتایان معامله را هم ببندید! -emptyWalletWindow.headline={0} emergency wallet tool +emptyWalletWindow.headline=ابزار اضطراری کیف پول {0} emptyWalletWindow.info=لطفاً تنها در مورد اضطراری از آن استفاده کنید اگر نمی توانید به وجه خود از UI دسترسی داشته باشید.\n\nلطفاً توجه داشته باشید که تمام معاملات باز به طور خودکار در هنگام استفاده از این ابزار، بسته خواهد شد.\n\nقبل از به کار گیری این ابزار، از راهنمای داده ی خود پشتیبان بگیرید. می توانید این کار را در \"حساب/پشتیبان\" انجام دهید.\n\nلطفاً مشکل خود را به ما گزارش کنید و گزارش مشکل را در GitHub یا تالار گفتگوی Bisq بایگانی کنید تا ما بتوانیم منشأ مشکل را بررسی نماییم. -emptyWalletWindow.balance=Your available wallet balance -emptyWalletWindow.bsq.btcBalance=Balance of non-BSQ Satoshis +emptyWalletWindow.balance=موجودی در دسترس کیف‌پول شما +emptyWalletWindow.bsq.btcBalance=موجودی غیر BSQ بر اساس ساتوشی -emptyWalletWindow.address=Your destination address +emptyWalletWindow.address=آدرس مقصد شما emptyWalletWindow.button=ارسال تمام وجوه emptyWalletWindow.openOffers.warn=شما معاملات بازی دارید که اگر کیف پول را خالی کنید، حذف خواهند شد.\nآیا شما مطمئن هستید که می خواهید کیف پول را خالی کنید؟ emptyWalletWindow.openOffers.yes=بله، مطمئن هستم @@ -1627,39 +1629,39 @@ emptyWalletWindow.sent.success=تراز کیف پول شما به طور موف enterPrivKeyWindow.headline=ثبت نام فقط برای داوران دعوت شده، باز است filterWindow.headline=ویرایش لیست فیلتر -filterWindow.offers=Filtered offers (comma sep.) -filterWindow.onions=Filtered onion addresses (comma sep.) +filterWindow.offers=پیشنهادهای فیلتر شده (جدا شده با ویرگول) +filterWindow.onions=آدرس های Onion فیلتر شده (جدا شده با ویرگول) filterWindow.accounts=داده های حساب معاملاتی فیلترشده:\nفرمت: لیست جدا شده با ویرگول [شناسه روش پرداخت، زمینه داده، ارزش] -filterWindow.bannedCurrencies=Filtered currency codes (comma sep.) -filterWindow.bannedPaymentMethods=Filtered payment method IDs (comma sep.) -filterWindow.arbitrators=Filtered arbitrators (comma sep. onion addresses) -filterWindow.seedNode=Filtered seed nodes (comma sep. onion addresses) -filterWindow.priceRelayNode=Filtered price relay nodes (comma sep. onion addresses) -filterWindow.btcNode=Filtered Bitcoin nodes (comma sep. addresses + port) -filterWindow.preventPublicBtcNetwork=Prevent usage of public Bitcoin network +filterWindow.bannedCurrencies=کدهای ارز فیلترشده (جدا شده با ویرگول) +filterWindow.bannedPaymentMethods=شناسه‌های روش پرداخت فیلتر شده (جدا شده با ویرگول) +filterWindow.arbitrators=داوران فیلتر شده (آدرس های Onion جدا شده با ویرگول) +filterWindow.seedNode=گره های seed فیلتر شده (آدرس های Onion جدا شده با ویرگول) +filterWindow.priceRelayNode=گره های رله قیمت فیلترشده (آدرس های Onion جدا شده با ویرگول) +filterWindow.btcNode=گره‌های بیت‌کوین فیلترشده (آدرس + پورت جدا شده با ویرگول) +filterWindow.preventPublicBtcNetwork=جلوگیری از استفاده ازشبکه عمومی بیت‌کوین filterWindow.add=افزودن فیلتر filterWindow.remove=حذف فیلتر -offerDetailsWindow.minBtcAmount=Min. BTC amount +offerDetailsWindow.minBtcAmount=حداقل مقدار BTC offerDetailsWindow.min=(حداقل {0}) offerDetailsWindow.distance=(فاصله از قیمت روز بازار: {0}) -offerDetailsWindow.myTradingAccount=My trading account -offerDetailsWindow.offererBankId=(maker's bank ID/BIC/SWIFT) +offerDetailsWindow.myTradingAccount=حساب معاملاتی من +offerDetailsWindow.offererBankId=(/BIC/SWIFT/شناسه بانک سفارش گذار) offerDetailsWindow.offerersBankName=(نام بانک سفارش گذار) -offerDetailsWindow.bankId=Bank ID (e.g. BIC or SWIFT) -offerDetailsWindow.countryBank=Maker's country of bank -offerDetailsWindow.acceptedArbitrators=Accepted arbitrators +offerDetailsWindow.bankId=شناسه بانک (برای مثال BIC یا SWIFT) +offerDetailsWindow.countryBank=کشور بانک سفارش‌گذار +offerDetailsWindow.acceptedArbitrators=داوران پذیرفته شده offerDetailsWindow.commitment=تعهد offerDetailsWindow.agree=من موافقم -offerDetailsWindow.tac=Terms and conditions +offerDetailsWindow.tac=شرایط و الزامات offerDetailsWindow.confirm.maker=تأیید: پیشنهاد را به {0} بگذارید offerDetailsWindow.confirm.taker=تأیید: پیشنهاد را به {0} بپذیرید -offerDetailsWindow.creationDate=Creation date -offerDetailsWindow.makersOnion=Maker's onion address +offerDetailsWindow.creationDate=تاریخ ایجاد +offerDetailsWindow.makersOnion=آدرس Onion سفارش گذار qRCodeWindow.headline=QR-Code qRCodeWindow.msg=لطفاً از آن QR-Code برای تأمین وجه کیف پول Bisq از کیف پول خارجی خود استفاده کنید. -qRCodeWindow.request=Payment request:\n{0} +qRCodeWindow.request=درخواست پرداخت:\n{0} selectDepositTxWindow.headline=تراکنش سپرده را برای مناقشه انتخاب کنید selectDepositTxWindow.msg=تراکنش سپرده در معامله ذخیره نشده بود.\nلطفاً یکی از تراکنش های چندامضایی موجود از کیف پول خود را انتخاب کنید که تراکنش سپرده در معامله ی ناموفق، استفاده شده بود.\n\nشما می توانید تراکنش صحیح را با باز کردن پنجره جزئیات معامله (با کلیک بر روی شناسه معامله در لیست) و دنبال کردن خروجی تراکنش پرداخت هزینه معامله تا تراکنش بعدی که در آن شما می توانید تراکنش سپرده ی چند امضایی را ببینید (آدرس با 3 شروع می شود)، پیدا کنید. آن شناسه تراکنش باید در لیست ارائه شده در اینجا قابل مشاهده باشد. هنگامی که تراکنش صحیح را یافتید، آن تراکنش را در اینجا انتخاب نموده و ادامه دهید.\n\nبا عرض پوزش برای این مشکل، اما این خطا ندرتاً رخ دهد و در آینده ما سعی خواهیم کرد راه های بهتری برای حل آن پیدا کنیم. @@ -1670,20 +1672,20 @@ selectBaseCurrencyWindow.msg=بازار پیشفرض انتخاب شده، {0} selectBaseCurrencyWindow.select=انتخاب ارز پایه sendAlertMessageWindow.headline=ارسال اطلاع رسانی جهانی -sendAlertMessageWindow.alertMsg=Alert message +sendAlertMessageWindow.alertMsg=پیام هشدار sendAlertMessageWindow.enterMsg=وارد کردن پیام -sendAlertMessageWindow.isUpdate=Is update notification -sendAlertMessageWindow.version=New version no. +sendAlertMessageWindow.isUpdate=اعلان بروز رسانی باشد +sendAlertMessageWindow.version=شماره نسخه جدید sendAlertMessageWindow.send=ارسال اطلاع رسانی sendAlertMessageWindow.remove=حذف اطلاع رسانی sendPrivateNotificationWindow.headline=ارسال پیام اختصاصی -sendPrivateNotificationWindow.privateNotification=Private notification +sendPrivateNotificationWindow.privateNotification=اعلان خصوصی sendPrivateNotificationWindow.enterNotification=وارد کردن اعلان sendPrivateNotificationWindow.send=ارسال اطلاع رسانی خصوصی showWalletDataWindow.walletData=داده های کیف پول -showWalletDataWindow.includePrivKeys=Include private keys +showWalletDataWindow.includePrivKeys=شامل کلیدهای خصوصی # We do not translate the tac because of the legal nature. We would need translations checked by lawyers # in each language which is too expensive atm. @@ -1695,9 +1697,9 @@ tacWindow.arbitrationSystem=سیستم داوری tradeDetailsWindow.headline=معامله tradeDetailsWindow.disputedPayoutTxId=شناسه تراکنش پرداختی مورد مناقشه: tradeDetailsWindow.tradeDate=تاریخ معامله -tradeDetailsWindow.txFee=هرینه استخراج +tradeDetailsWindow.txFee=کارمزد استخراج tradeDetailsWindow.tradingPeersOnion=آدرس Onion همتایان معامله: -tradeDetailsWindow.tradeState=Trade state +tradeDetailsWindow.tradeState=وضعیت معامله walletPasswordWindow.headline=وارد کردن رمز عبور به منظور باز کردن @@ -1705,12 +1707,12 @@ torNetworkSettingWindow.header=تنظیمات شبکه Tor  torNetworkSettingWindow.noBridges=از پل ها استفاده نکنید torNetworkSettingWindow.providedBridges=اتصال با پل های ارائه شده torNetworkSettingWindow.customBridges=وارد کردن پل های سفارشی -torNetworkSettingWindow.transportType=Transport type +torNetworkSettingWindow.transportType=نوع انتقال torNetworkSettingWindow.obfs3=obfs3 torNetworkSettingWindow.obfs4=obfs4 (توصیه شده) torNetworkSettingWindow.meekAmazon=meek-amazon torNetworkSettingWindow.meekAzure=meek-azure -torNetworkSettingWindow.enterBridge=Enter one or more bridge relays (one per line) +torNetworkSettingWindow.enterBridge=یک یا چند رله وارد کنید (یکی در هر خط) torNetworkSettingWindow.enterBridgePrompt=نوع آدرس:پورت torNetworkSettingWindow.restartInfo=برای اعمال تغییرات باید برنامه را مجدداً راه اندازی کنید. torNetworkSettingWindow.openTorWebPage=صفحه وب پروژه ی Tor را باز کنید @@ -1724,7 +1726,7 @@ torNetworkSettingWindow.bridges.info=اگر Tor توسط ارائه دهنده feeOptionWindow.headline=انتخاب ارز برای پرداخت هزینه معامله feeOptionWindow.info=شما می توانید انتخاب کنید که هزینه معامله را در BSQ یا در BTC بپردازید. اگر BSQ را انتخاب می کنید، از تخفیف هزینه معامله برخوردار می شوید. -feeOptionWindow.optionsLabel=انتخاب ارز برای پرداخت هزینه معامله +feeOptionWindow.optionsLabel=انتخاب ارز برای پرداخت کارمزد معامله feeOptionWindow.useBTC=استفاده از BTC feeOptionWindow.fee={0} (≈ {1}) @@ -1746,7 +1748,7 @@ popup.headline.error=خطا popup.doNotShowAgain=دوباره نشان نده popup.reportError.log=باز کردن فایل گزارش popup.reportError.gitHub=گزارش به پیگیر مسائل GitHub  -popup.reportError={0}\n\nTo help us to improve the software please report the bug on our issue tracker on GitHub (https://github.com/bisq-network/bisq-desktop/issues).\nThe error message will be copied to the clipboard when you click a button below.\nIt will make debugging easier if you can attach the bisq.log file as well. +popup.reportError={0}\n\nTo help us to improve the software please report this bug by opening a new issue at https://github.com/bisq-network/bisq/issues.\nThe above error message will be copied to the clipboard when you click either of the buttons below.\nIt will make debugging easier if you include the bisq.log file by pressing "Open log file", saving a copy, and attaching it to your bug report. popup.error.tryRestart=لطفاً سعی کنید برنامه را مجدداً راه اندازی کنید و اتصال شبکه خود را بررسی کنید تا ببینید آیا می توانید مشکل را حل کنید یا خیر. popup.error.takeOfferRequestFailed=وقتی کسی تلاش کرد تا یکی از پیشنهادات شما را بپذیرد خطایی رخ داد:\n{0} @@ -1763,7 +1765,7 @@ popup.warning.tradePeriod.halfReached=معامله شما با شناسه {0} ن popup.warning.tradePeriod.ended=معامله شما با شناسه {0} به حداکثر مجاز دوره زمانی معامله رسیده و کامل نشده است.\n\n دوره معامله در {1} به پایان رسیده است.\n\n لطفا معامله خود را در \"سبد سهام/معاملات باز\" برای تماس با داور بررسی کنید. popup.warning.noTradingAccountSetup.headline=شما یک حساب معاملاتی را راه اندازی نکرده اید popup.warning.noTradingAccountSetup.msg=قبل از اینکه بتوانید یک پیشنهاد ایجاد کنید، باید یک ارز ملی یا حساب کاربری آلت کوین را تنظیم کنید. \nآیا می خواهید یک حساب کاربری را راه اندازی کنید؟ -popup.warning.noArbitratorsAvailable=There are no arbitrators available. +popup.warning.noArbitratorsAvailable=هیچ داوری در دسترس نیست. popup.warning.notFullyConnected=شما باید منتظر بمانید تا به طور کامل به شبکه متصل شوید. \nاین ممکن است در هنگام راه اندازی حدود 2 دقیقه طول بکشد. popup.warning.notSufficientConnectionsToBtcNetwork=شما باید منتظر بمانید تا حداقل {0} اتصال به شبکه بیتکوین داشته باشید. popup.warning.downloadNotComplete=شما باید منتظر بمانید تا بارگیری بلاک های بیتکوین باقیمانده کامل شود. @@ -1772,10 +1774,10 @@ popup.warning.tooLargePercentageValue=شما نمیتوانید درصد 100٪ popup.warning.examplePercentageValue=لطفا یک عدد درصد مانند \"5.4\" برای 5.4% وارد کنید popup.warning.noPriceFeedAvailable=برای این ارز هیچ خوراک قیمتی وجود ندارد. شما نمیتوانید از یک درصد بر اساس قیمت استفاده کنید. \nلطفا قیمت مقطوع را انتخاب کنید. popup.warning.sendMsgFailed=ارسال پیام به شریک معاملاتی شما ناموفق بود. \nلطفا دوباره امتحان کنید و اگر همچنان ناموفق بود، گزارش یک اشکال را ارسال کنید. -popup.warning.insufficientBtcFundsForBsqTx=You don''t have sufficient BTC funds for paying the miner fee for that transaction.\nPlease fund your BTC wallet.\nMissing funds: {0} +popup.warning.insufficientBtcFundsForBsqTx=شما BTC کافی برای پرداخت کارمزد استخراج آن تراکنش BSQ را ندارید.\nلطفاً کیف پول BTC خود را شارژ نموده تا قادر به انتقال BSQ باشید.\nBTC موردنیاز: {0} -popup.warning.insufficientBsqFundsForBtcFeePayment=You don''t have sufficient BSQ funds for paying the trade fee in BSQ. You can pay the fee in BTC or you need to fund your BSQ wallet. You can buy BSQ in Bisq.\n\nMissing BSQ funds: {0} -popup.warning.noBsqFundsForBtcFeePayment=Your BSQ wallet does not have sufficient funds for paying the trade fee in BSQ. +popup.warning.insufficientBsqFundsForBtcFeePayment=شما BTC کافی برای پرداخت کارمزد معامله آن تراکنش BSQ را ندارید. می‌توانید کارمزد را با BTC پرداخت کنید و یا اینکه کیف پول BSQ خود را شارژ کنید. می‌توانید از Bisq اقدام به خرید BSQ کنید.\n\nBSQ موردنیاز: {0} +popup.warning.noBsqFundsForBtcFeePayment=کیف‌پول BSQ شما BSQ کافی برای پرداخت کارمزد معامله به BSQ را ندارد. popup.warning.messageTooLong=پیام شما بیش از حداکثر اندازه مجاز است. لطفا آن را در چند بخش ارسال کنید یا آن را در یک سرویس مانند https://pastebin.com آپلود کنید. popup.warning.lockedUpFunds=شما مبلغی را از یک معامله ی ناموفق قفل کرده اید.\n تراز قفل شده: {0} \nآدرس تراکنش سپرده: {1}\n شناسه معامله: {2} .\n\n لطفا یک تیکت پشتیبانی را با انتخاب معامله در صفحه معاملات در انتظار باز کنید و \"alt + o\" or \"option + o\" را بگیرید. @@ -1783,11 +1785,11 @@ popup.warning.nodeBanned=یکی از گره های {0} مسدود شده است. popup.warning.priceRelay=رله قیمت popup.warning.seed=دانه -popup.info.securityDepositInfo=To ensure both traders follow the trade protocol, both traders need to pay a security deposit.\n\nThis deposit is kept in your trade wallet until your trade has been successfully completed, and then it's refunded to you.\n\nPlease note: if you're creating a new offer, Bisq needs to be running for another trader to take it. To keep your offers online, keep Bisq running and make sure this computer remains online too (i.e., make sure it doesn't switch to standby mode...monitor standby is fine). +popup.info.securityDepositInfo=برای اطمینان از اینکه هر دو معامله گر پروتکل معامله را رعایت می‌کنند، هر دو معامله گر باید مبلغی را تحت عنوان سپرده اطمینان پرداخت کنند.\n\nاین سپرده در کیف‌پول معامله شما نگهداری می‌شود و زمانی که معامله شما با موفقیت انجام شد به خود شما بازگردانده خواهد شد.\n\nلطفا توجه کنید: اگر می‌خواهید یک پیشنهاد جدید ایجاد کنید، Bisq باید برای در سمت معامله دیگر اجرا باشد تا بتوانند آن را بپذیرد. برای اینکه پیشنهادات شما برخط بمانند، بگذارید Bisq در حال اجرابماند و همچنین مطمئن شوید که این کامپیوتر به اینترنت متصل است. (به عنوان مثال مطمئن شوید که به حالت آماده باش نمی‌رود.. البته حالت آماده باش برای نمایشگر ایرادی ندارد). popup.info.cashDepositInfo=لطفا مطمئن شوید که شما یک شعبه بانک در منطقه خود دارید تا بتوانید سپرده نقدی را بپردازید. شناسه بانکی (BIC/SWIFT) بانک فروشنده: {0}. popup.info.cashDepositInfo.confirm=تأیید می کنم که می توانم سپرده را ایجاد کنم -popup.info.shutDownWithOpenOffers=Bisq is being shut down, but there are open offers. \n\nThese offers won't be available on the P2P network while Bisq is shut down, but they will be re-published to the P2P network the next time you start Bisq.\n\nTo keep your offers online, keep Bisq running and make sure this computer remains online too (i.e., make sure it doesn't go into standby mode...monitor standby is not a problem). +popup.info.shutDownWithOpenOffers=Bisq در حال خاموش شدن است ولی پیشنهاداتی وجود دارند که باز هستند.\n\nزمانی که Bisq بسته باشد این پیشنهادات در شبکه P2P در دسترس نخواهند بود، ولی هر وقت دوباره Bisq را باز کنید این پیشنهادات دوباره در شبکه P2P منتشر خواهند شد.\n\n برای اینکه پیشنهادات شما برخط بمانند، بگذارید Bisq در حال اجرابماند و همچنین مطمئن شوید که این کامپیوتر به اینترنت متصل است. (به عنوان مثال مطمئن شوید که به حالت آماده باش نمی‌رود.. البته حالت آماده باش برای نمایشگر ایرادی ندارد). popup.privateNotification.headline=اعلان خصوصی مهم! @@ -1802,8 +1804,11 @@ popup.shutDownInProgress.msg=خاتمه دادن به برنامه می توان popup.attention.forTradeWithId=توجه الزامی برای معامله با شناسه {0} -popup.roundedFiatValues.headline=New privacy feature: Rounded fiat values -popup.roundedFiatValues.msg=To increase privacy of your trade the {0} amount was rounded.\n\nDepending on the client version you''ll pay or receive either values with decimals or rounded ones.\n\nBoth values do comply from now on with the trade protocol.\n\nAlso be aware that BTC values are changed automatically to match the rounded fiat amount as close as possible. +popup.roundedFiatValues.headline=ویژگی جدید حریم خصوصی: مقادیرگرد شده برای فیات‌ها +popup.roundedFiatValues.msg=برای محافظت از حریم خصوصی معامله شما، مقدار {0} گرد شده است.\n\nبسته به نسخه کلاینت، مقادیرپرداختی یا دریافتی به صورت گرد شده یا با خرده اعشاری خواهند بود.\n\nاز این به بعد، هر دوی این مقادیر در پروتکل معامله پذیرفته شده محسوب می‌شوند.\n\nهمچنین توجه داشته باشید که مقادیر BTC به صورت خودکار به عددی تغییر خواهند کرد که متناسب با مقدار فیات گرد شده بشود. + +popup.info.multiplePaymentAccounts.headline=Multiple payment accounts available +popup.info.multiplePaymentAccounts.msg=You have multiple payment accounts available for this offer. Please make sure you've picked the right one. #################################################################### @@ -1889,10 +1894,10 @@ confidence.confirmed=تأیید شده در {0} بلاک(s) confidence.invalid=تراکنش نامعتبر است peerInfo.title=اطلاعات همتا -peerInfo.nrOfTrades=Number of completed trades +peerInfo.nrOfTrades=تعداد معاملات انجام شده peerInfo.notTradedYet=شما تاکنون با آن کاربر معامله نداشته اید. -peerInfo.setTag=Set tag for that peer -peerInfo.age=Payment account age +peerInfo.setTag=تنظیم برچسب برای آن همتا +peerInfo.age=عمر حساب پرداخت peerInfo.unknownAge=عمر شناخته شده نیست addressTextField.openWallet=باز کردن کیف پول بیتکوین پیشفرضتان @@ -1980,8 +1985,8 @@ time.minutes=دقائق time.seconds=ثانیه ها -password.enterPassword=Enter password -password.confirmPassword=Confirm password +password.enterPassword=رمز عبور +password.confirmPassword=تایید رمز عبور password.tooLong=رمز عبور باید کمتر از 500 کاراکتر باشد. password.deriveKey=کلید را از رمز عبور استنتاج کنید password.walletDecrypted=کیف پول با موفقیت رمزگشایی شد و حفاظت با رمز عبور حذف شد. @@ -1993,12 +1998,12 @@ password.forgotPassword=رمز عبور را فراموش کرده اید؟ password.backupReminder=لطفا توجه داشته باشید که هنگام تنظیم یک رمز عبور کیف پول، تمام پشتیبان های خودکار از کیف پول رمزگذاری نشده حذف خواهد شد.\n\n توصیه می شود که نسخه پشتیبان از دایرکتوری نرم برنامه را تهیه کنید و قبل از تنظیم رمز عبور، کلمات رمز خصوصی خود را بنویسید! password.backupWasDone=من قبلا یک نسخه پشتیبان تهیه کرده ام -seed.seedWords=Wallet seed words -seed.enterSeedWords=Enter wallet seed words -seed.date=Wallet date +seed.seedWords=کلمات seed کیف‌پول +seed.enterSeedWords=کلمات seed کیف‌پول را وارد کنید +seed.date=تاریخ کیف‌پول seed.restore.title=بازگرداندن کیف های پول از کلمات رمز خصوصی seed.restore=بازگرداندن کیف های پول -seed.creationDate=Creation date +seed.creationDate=تاریخ ایجاد seed.warn.walletNotEmpty.msg=کیف پول بیتکوین شما خالی نیست.\n\n شما باید قبل از تلاش برای بازگرداندن یک کیف پول قدیمی تر، این کیف پول را خالی کنید، زیرا ترکیب کیف پول ها با هم می تواند به پشتیبان گیری های نامعتبر منجر شود.\n\n لطفا معاملات خود را نهایی کنید، تمام پیشنهادهای باز را ببندید و برای برداشتن بیتکوین به قسمت وجوه بروید.\n در صورت عدم دسترسی به بیتکوین شما میتوانید از ابزار اضطراری برای خالی کردن کیف پول استفاده کنید.\n برای باز کردن این ابزار اضطراری، دکمه \"alt + e\" یا \"option + e\" را بزنید. seed.warn.walletNotEmpty.restore=میخواهم به هر حال بازگردانی کنم seed.warn.walletNotEmpty.emptyWallet=من ابتدا کیف پول هایم را خالی می کنم @@ -2012,13 +2017,13 @@ seed.restore.error=هنگام بازگرداندن کیف پول با کلمات #################################################################### payment.account=حساب -payment.account.no=Account no. -payment.account.name=Account name +payment.account.no=شماره حساب +payment.account.name=نام حساب payment.account.owner=نام کامل مالک حساب payment.account.fullName=نام کامل (اول، وسط، آخر) -payment.account.state=State/Province/Region -payment.account.city=City -payment.bank.country=Country of bank +payment.account.state=ایالت/استان/ناحیه +payment.account.city=شهر +payment.bank.country=کشور بانک payment.account.name.email=نام کامل/ایمیل مالک حساب payment.account.name.emailAndHolderId=نام کامل/ایمیل/{0} مالک حساب payment.bank.name=نام بانک @@ -2028,80 +2033,80 @@ payment.select.country=انتخاب کشور payment.select.bank.country=انتخاب کشور بانک payment.foreign.currency=آیا مطمئن هستید که می خواهید ارزی به جز ارز پیش فرض کشور انتخاب کنید؟ payment.restore.default=خیر، ارز پیشفرض را تعیین کن -payment.email=Email +payment.email=ایمیل payment.country=کشور -payment.extras=Extra requirements -payment.email.mobile=Email or mobile no. -payment.altcoin.address=Altcoin address -payment.altcoin=Altcoin +payment.extras=الزامات اضافی +payment.email.mobile=ایمیل یا شماره موبایل +payment.altcoin.address=آدرس آلت‌کوین +payment.altcoin=آلت‌کوین payment.select.altcoin=انتخاب یا جستجوی آلت کوین -payment.secret=Secret question -payment.answer=Answer -payment.wallet=Wallet ID -payment.uphold.accountId=Username or email or phone no. +payment.secret=سوال محرمانه +payment.answer=پاسخ +payment.wallet=شناسه کیف پول +payment.uphold.accountId=نام کاربری یا ایمیل یا شماره تلفن payment.cashApp.cashTag=$Cashtag -payment.moneyBeam.accountId=Email or phone no. -payment.venmo.venmoUserName=Venmo username -payment.popmoney.accountId=Email or phone no. -payment.revolut.accountId=Email or phone no. -payment.promptPay.promptPayId=Citizen ID/Tax ID or phone no. -payment.supportedCurrencies=Supported currencies -payment.limitations=Limitations -payment.salt=Salt for account age verification +payment.moneyBeam.accountId=ایمیل یا شماره تلفن +payment.venmo.venmoUserName=نام کاربری Venmo +payment.popmoney.accountId=ایمیل یا شماره تلفن +payment.revolut.accountId=ایمیل یا شماره تلفن +payment.promptPay.promptPayId=شناسه شهروندی/شناسه مالیاتی یا شماره تلفن +payment.supportedCurrencies=ارزهای مورد حمایت +payment.limitations=محدودیت‌ها +payment.salt=داده‌های تصافی برای اعتبارسنجی سن حساب payment.error.noHexSalt=داده تصادفی باید در فرمت HEX باشد.\n اگر بخواهید داده تصادفی را از یک حساب قدیمی برای حفظ سن حساب خود منتقل کنید، فقط توصیه می شود که فیلد داده تصادفی را ویرایش کنید. عمر حساب با استفاده از داده تصادفی حساب و شناسایی دادههای تصادفی (به عنوان مثال IBAN) تأیید شده است. -payment.accept.euro=Accept trades from these Euro countries -payment.accept.nonEuro=Accept trades from these non-Euro countries -payment.accepted.countries=Accepted countries -payment.accepted.banks=Accepted banks (ID) -payment.mobile=Mobile no. -payment.postal.address=Postal address -payment.national.account.id.AR=CBU number +payment.accept.euro=پذیرش معاملات از این کشورهای Euro ای +payment.accept.nonEuro=پذیرش معاملات از کشورهای غیر Euro ای +payment.accepted.countries=کشورهای پذیرفته شده +payment.accepted.banks=بانک های پذیرفته شده (شناسه) +payment.mobile=شماره موبایل +payment.postal.address=آدرس پستی +payment.national.account.id.AR=شماره CBU #new -payment.altcoin.address.dyn={0} address -payment.altcoin.receiver.address=Receiver's altcoin address -payment.accountNr=Account number -payment.emailOrMobile=Email or mobile nr +payment.altcoin.address.dyn=آدرس {0} +payment.altcoin.receiver.address=آدرس آلت‌کوین گیرنده +payment.accountNr=شماره حساب +payment.emailOrMobile=ایمیل یا شماره موبایل payment.useCustomAccountName=استفاده از نام حساب سفارشی -payment.maxPeriod=Max. allowed trade period +payment.maxPeriod=حداکثر دوره ی زمانی مجاز معامله payment.maxPeriodAndLimit=حداکثر طول مدت معامله: {0} / حداکثر حد معامله: {1} / عمر حساب: {2} -payment.maxPeriodAndLimitCrypto=Max. trade duration: {0} / Max. trade limit: {1} +payment.maxPeriodAndLimitCrypto=حداکثر طول مدت معامله: {0} / حداکثر معامله: {1} payment.currencyWithSymbol=ارز: {0} payment.nameOfAcceptedBank=نام بانک پذیرفته شده payment.addAcceptedBank=افزودن بانک پذیرفته شده payment.clearAcceptedBanks=پاک کردن بانک های پذیرفته شده -payment.bank.nameOptional=Bank name (optional) -payment.bankCode=Bank code +payment.bank.nameOptional=نام بانک (اختیاری) +payment.bankCode=کد بانک payment.bankId=شناسه بانک (BIC/SWIFT) -payment.bankIdOptional=Bank ID (BIC/SWIFT) (optional) -payment.branchNr=Branch no. -payment.branchNrOptional=Branch no. (optional) -payment.accountNrLabel=Account no. (IBAN) -payment.accountType=Account type +payment.bankIdOptional=شناسه بانک (BIC/SWIFT) (اختیاری) +payment.branchNr=شماره شعبه +payment.branchNrOptional=شماره شعبه (اختیاری) +payment.accountNrLabel=شماره حساب (IBAN) +payment.accountType=نوع حساب payment.checking=بررسی payment.savings=اندوخته ها -payment.personalId=Personal ID -payment.clearXchange.info=Please be sure that you fulfill the requirements for the usage of Zelle (ClearXchange).\n\n1. You need to have your Zelle (ClearXchange) account verified on their platform before starting a trade or creating an offer.\n\n2. You need to have a bank account at one of the following member banks:\n\t● Bank of America\n\t● Capital One P2P Payments\n\t● Chase QuickPay\n\t● FirstBank Person to Person Transfers\n\t● Frost Send Money\n\t● U.S. Bank Send Money\n\t● TD Bank\n\t● Citibank\n\t● Wells Fargo SurePay\n\n3. You need to be sure to not exceed the daily or monthly Zelle (ClearXchange) transfer limits.\n\nPlease use Zelle (ClearXchange) only if you fulfill all those requirements, otherwise it is very likely that the Zelle (ClearXchange) transfer fails and the trade ends up in a dispute.\nIf you have not fulfilled the above requirements you will lose your security deposit.\n\nPlease also be aware of a higher chargeback risk when using Zelle (ClearXchange).\nFor the {0} seller it is highly recommended to get in contact with the {1} buyer by using the provided email address or mobile number to verify that he or she is really the owner of the Zelle (ClearXchange) account. +payment.personalId=شناسه شخصی +payment.clearXchange.info=لطفا مطمئن شوید که الزامات استفاده از Zelle (ClearXchange) را برآورده می کنید.\n\n1. قبل از شروع یک معامله یا ایجاد یک پیشنهاد، باید حساب Zelle (ClearXchange) خود را بر روی پلت فرم آن ها تأیید کنید.\n\n2. شما باید یک حساب بانکی در یکی از بانک های عضو زیر داشته باشید:\n\t● Bank of America\n\t● Capital One P2P Payments\n\t● Chase QuickPay\n\t● FirstBank Person to Person Transfers\n\t● Frost Send Money\n\t● U.S. Bank Send Money\n\t● TD Bank\n\t● Wells Fargo SurePay\n\n3. شما باید مطمئن باشید که از محدودیت های انتقال روزانه یا ماهانه یZelle (ClearXchange) تجاوز نمی کنید.\n\nلطفا فقط وقتی از Zelle (ClearXchange) استفاده کنید که تمام الزامات را برآورده کرده باشید، در غیر این صورت احتمالا انتقال Zelle (ClearXchange) انجام نخواهد شد و معامله با بروز یک اختلاف به پایان می‌رسد.\nاگر شما الزامات فوق را دارا نباشید، سپرده‌های اطمینان خود را از دست خواهید داد.\n\nهمچنین هنگام استفاده از Zelle (ClearXchange)، از ریسک بالاتر استرداد وجه آگاه باشید.\nبرای فروشنده {0} بسیار توصیه می شود که با استفاده از آدرس ایمیل یا شماره تلفن ارائه شده در ارتباط با {1} خریدار باشد تا تأیید کند که آیا او واقعا صاحب حساب Zelle (ClearXchange) است یا خیر. payment.moneyGram.info=هنگام استفاده از MoneyGram، خریدار BTC باید شماره مجوز و عکس رسید را از طریق ایمیل به فروشنده BTC ارسال کند. رسید باید به وضوح نام کامل فروشنده، کشور، دولت و مبلغ را نشان دهد. ایمیل فروشنده در فرآیند معامله به خریدار نشان داده می شود. payment.westernUnion.info=هنگام استفاده از Western Union، خریدار BTC باید شماره MTCN (شماره پیگیری) را از طریق ایمیل به فروشنده BTC ارسال کند. رسید باید به وضوح نام کامل فروشنده، کشور، دولت و مبلغ را نشان دهد. ایمیل فروشنده در فرآیند معامله به خریدار نشان داده می شود. -payment.halCash.info=When using HalCash the BTC buyer need to send the BTC seller the HalCash code via a text message from the mobile phone.\n\nPlease make sure to not exceed the maximum amount your bank allows you to send with HalCash. The min. amount per withdrawal is 10 EUR and the max. amount is 600 EUR. For repeated withdrawals it is 3000 EUR per receiver per day and 6000 EUR per receiver per month. Please cross check those limits with your bank to be sure they use the same limits as stated here.\n\nThe withdrawal amount must be a multiple of 10 EUR as you cannot withdraw other amounts from an ATM. The UI in the create-offer and take-offer screen will adjust the BTC amount so that the EUR amount is correct. You cannot use market based price as the EUR amount would be changing with changing prices.\n\nIn case of a dispute the BTC buyer need to provide the proof that he sent the EUR. +payment.halCash.info=زمانی که از HalCash استفاده می‌کنید، خریدار باید کد HalCash را از طریق پیام کوتاه موبایل به فروشنده BTC ارسال کند.\n\nلطفا مطمئن شوید که از حداکثر میزانی که بانک شما برای انتقال از طریق HalCash مجاز می‌داند تجاوز نکرده‌اید. حداقل مقداردر هر برداشت معادل 10 یورو و حداکثر مقدار 600 یورو می‌باشد. این محدودیت برای برداشت‌های تکراری برای هر گیرنده در روز 3000 یورو و در ماه 6000 یورو می‌باشد. لطفا این محدودیت‌ها را با بانک خود مطابقت دهید و مطمئن شوید که آنها هم همین محدودی‌ها را دارند.\n\nمقدار برداشت باید شریبی از 10 یورو باشد چرا که مقادیر غیر از این را نمی‌توانید از طریق ATM برداشت کنید. رابط کاربری در صفحه ساخت پینشهاد و پذیرش پیشنهاد مقدار BTC را به گونه‌ای تنظیم می‌کنند که مقدار EUR درست باشد. شما نمی‌توانید از قیمت بر مبنای بازار استفاده کنید چون مقدار یورو با تغییر قیمت‌ها عوض خواهد شد.\n\nدر صورت بروز اختلاف خریدار BTC باید شواهد مربوط به ارسال یورو را ارائه دهد. payment.limits.info=لطفا توجه داشته باشید که تمام انتقال های بانکی مقدار مشخصی از ریسک استرداد وجه را تقبل می کنند. برای کاهش این ریسک، Bisq محدودیت به ازای هر معامله را بر اساس دو عامل تعیین می کند: \n\n1. میزان برآورد ریسک استرداد وجه برای روش پرداخت استفاده شده.\n\n2. عمر حساب کاربری شما برای این روش پرداخت\n\n حسابی که اکنون ایجاد می کنید، جدید است و عمر آن صفر است. همانطور که عمر حساب شما در طول یک دوره دو ماهه رشد می کند، محدودیت به ازای هر معامله ی شما نیز با آن رشد می کند:\n\n ● در ماه اول، میزان محدودیت به ازای هر معامله شما {0} خواهد بود\n ● در طول ماه دوم محدودیت شما {1} خواهد بود\n ● پس از ماه دوم، محدودیت شما {2} خواهد بود \n\n لطفا توجه داشته باشید که هیچ محدودیتی در کل تعداد دفعاتی که می توانید معامله کنید، وجود ندارد. -payment.cashDeposit.info=Please confirm your bank allows you to send cash deposits into other peoples' accounts. For example, Bank of America and Wells Fargo no longer allow such deposits. +payment.cashDeposit.info=لطفا مطمئن شوید که بانک شما اجازه پرداخت سپرده نفد به حساب دیگر افراد را می‌دهد. برای مثال، Bank of America و Wells Fargo دیگر اجازه چنین پرداخت‌هایی را نمی‌دهند. -payment.f2f.contact=Contact info -payment.f2f.contact.prompt=How you want to get contacted by the trading peer? (email address, phone number,...) -payment.f2f.city=City for 'Face to face' meeting -payment.f2f.city.prompt=The city will be displayed with the offer -payment.f2f.optionalExtra=Optional additional information -payment.f2f.extra=Additional information +payment.f2f.contact=اطلاعات تماس +payment.f2f.contact.prompt=از چه طریقی می‌خواهید توسط همتای معاملاتی با شما تماس حاصل شود؟ (آدرس ایمیل، شماره تلفن، ...) +payment.f2f.city=شهر جهت ملاقات 'رو در رو' +payment.f2f.city.prompt=نام شهر به همراه پیشنهاد نمایش داده خواهد شد +payment.f2f.optionalExtra=اطلاعات اضافی اختیاری +payment.f2f.extra=اطلاعات اضافی -payment.f2f.extra.prompt=The maker can define 'terms and conditions' or add a public contact information. It will be displayed with the offer. -payment.f2f.info='Face to Face' trades have different rules and come with different risks than online transactions.\n\nThe main differences are:\n● The trading peers need to exchange information about the meeting location and time by using their provided contact details.\n● The trading peers need to bring their laptops and do the confirmation of 'payment sent' and 'payment received' at the meeting place.\n● If a maker has special 'terms and conditions' he needs to state those in the 'Addition information' text field in the account.\n● By taking an offer the taker agrees to the maker's stated 'terms and conditions'.\n● In case of a dispute the arbitrator cannot help much as it is usually hard to get tamper proof evidence of what happened at the meeting. In such cases the BTC funds might get locked indefinitely or until the trading peers come to an agreement.\n\nTo be sure you fully understand the differences with 'Face to Face' trades please read the instructions and recommendations at: 'https://docs.bisq.network/trading-rules.html#f2f-trading' -payment.f2f.info.openURL=Open web page -payment.f2f.offerbook.tooltip.countryAndCity=County and city: {0} / {1} -payment.f2f.offerbook.tooltip.extra=Additional information: {0} +payment.f2f.extra.prompt=سفارش‌گذار می‌تواند متن 'شرایط و الزامات' را تعیین کند و یا اطلاعات تماس عمومی را تنظیم کند. این اطلاعات به همراه پیشنهاد نمایش داده خواهد شد. +payment.f2f.info=معاملات 'رو در رو' قوانین متفاوتی دارند و در نتیجه مخاطرات متفاوتی نسبت به تراکنش‌های بر خط دارند.\n\nتفاوت‌های اصلی اینها هستند:\n● دو طرف معامله باید اطلاعات مربوط به مکان و زمان ملاقات را به یکدیگر از طریق اطلاعات تماسشان اطلاع دهند.\n● دو طرف معامله باید لپ تاپ هایشان را به همراه داشته باشند تا در محل ملاقات 'تاییدیه پرداخت' و 'تاییدیه دریافت' را انجام دهند.\n● اگر سفارش گذار 'شرایط و الزامات' خاصی دارد باید آن را در محل 'اطلاعات اضافی' حسابش قرار داده باشد.\n● با پذیرفتن یک پیشنهاد در واقع پذیرنده 'شرایط و الزامات' سفارش گذار را پذیرفته است.\n● در صورت بروز اختلاف، داور کمک خاصی نمی‌تواند بکند چرا که شواهد قابل استنادی وجود ندارد که دقیقا در محل ملاقات چه اتفاقی افتاده است. در چنین مواقعی ممکن است وجوه BTC برای همیشه قفل بشوند تا اینکه طرفین معامله به یک توافق برسند.\n\nبرای مطمئن شوید که تمام تفاوت‌های معاملات 'رو در رو' را فهمیده‌اید لطفا دستورالعمل و پیشنهادات زیر را مطالعه کنید: 'https://docs.bisq.network/trading-rules.html#f2f-trading' +payment.f2f.info.openURL=باز کردن صفحه وب +payment.f2f.offerbook.tooltip.countryAndCity=کشور و شهر: {0} / {1} +payment.f2f.offerbook.tooltip.extra=اطلاعات اضافی: {0} # We use constants from the code so we do not use our normal naming convention @@ -2115,7 +2120,7 @@ US_POSTAL_MONEY_ORDER=US Postal Money Order CASH_DEPOSIT=سپرده ی نقدی MONEY_GRAM=مانی گرام WESTERN_UNION=Western Union -F2F=Face to face (in person) +F2F=رو در رو (به طور فیزیکی) # suppress inspection "UnusedProperty" NATIONAL_BANK_SHORT=بانک های ملی @@ -2132,7 +2137,7 @@ MONEY_GRAM_SHORT=مانی گرام # suppress inspection "UnusedProperty" WESTERN_UNION_SHORT=Western Union # suppress inspection "UnusedProperty" -F2F_SHORT=F2F +F2F_SHORT=رو در رو # Do not translate brand names # suppress inspection "UnusedProperty" @@ -2227,7 +2232,7 @@ ADVANCED_CASH_SHORT=Advanced Cash validation.empty=ورودی خالی مجاز نیست. validation.NaN=ورودی، یک عدد معتبر نیست. -validation.notAnInteger=Input is not an integer value. +validation.notAnInteger=ورودی یک مقدار صحیح نیست. validation.zero=ورودی 0 مجاز نیست. validation.negative=یک مقدار منفی مجاز نیست. validation.fiat.toSmall=ورودی کوچکتر از حداقل مقدار ممکن مجاز نیست. @@ -2246,8 +2251,8 @@ validation.accountNrChars=عدد حساب باید متشکل از {0} کارا validation.btc.invalidAddress=آدرس درست نیست. لطفا فرمت آدرس را بررسی کنید validation.integerOnly=لطفا فقط اعداد صحیح را وارد کنید. validation.inputError=ورودی شما یک خطا ایجاد کرد: {0} -validation.bsq.insufficientBalance=Your available balance is {0}. -validation.btc.exceedsMaxTradeLimit=Your trade limit is {0}. +validation.bsq.insufficientBalance=موجودی در دسترس شما {0} است. +validation.btc.exceedsMaxTradeLimit=حدمعامله شما {0} است. validation.bsq.amountBelowMinAmount=مقدار حداقل {0} است validation.nationalAccountId={0} باید شامل {1} عدد باشد. @@ -2272,12 +2277,12 @@ validation.iban.checkSumInvalid=سرجمع IBAN نامعتبر است validation.iban.invalidLength=شماره باید طولی به اندازه ی 15 تا 34 کاراکتر داشته باشد. validation.interacETransfer.invalidAreaCode=کد ناحیه غیر کانادایی validation.interacETransfer.invalidPhone=فرمت شماره تلفن نامعتبر است و نه یک آدرس ایمیل -validation.interacETransfer.invalidQuestion=Must contain only letters, numbers, spaces and/or the symbols ' _ , . ? - -validation.interacETransfer.invalidAnswer=Must be one word and contain only letters, numbers, and/or the symbol - -validation.inputTooLarge=Input must not be larger than {0} -validation.inputTooSmall=Input has to be larger than {0} -validation.amountBelowDust=The amount below the dust limit of {0} is not allowed. -validation.length=Length must be between {0} and {1} -validation.pattern=Input must be of format: {0} -validation.noHexString=The input is not in HEX format. -validation.advancedCash.invalidFormat=Must be a valid email or wallet id of format: X000000000000 +validation.interacETransfer.invalidQuestion=باید فقط شامل حروف، اعداد، فاصله و یا نمادهای ' _ , . ? - باشد +validation.interacETransfer.invalidAnswer=باید یک کلمه باشد و فقط شامل حروف، اعداد و یا نماد - باشد +validation.inputTooLarge=ورودی نباید بزرگتر از {0} باشد +validation.inputTooSmall=ورودی باید بزرگتر از {0} باشد +validation.amountBelowDust=مقادیر کمتر از {0} مجاز نیستند. +validation.length=طول باید بین {0} و {1} باشد +validation.pattern=ورودی باید در این قالب باشد: {0} +validation.noHexString=ورودی در قالب HEX نیست +validation.advancedCash.invalidFormat=باید یک ایمیل درست باشد و یا یک شناسه کیف‌پول در قالب: X000000000000 diff --git a/core/src/main/resources/i18n/displayStrings_fr.properties b/core/src/main/resources/i18n/displayStrings_fr.properties index 4c04a5dd39..5baa7938f9 100644 --- a/core/src/main/resources/i18n/displayStrings_fr.properties +++ b/core/src/main/resources/i18n/displayStrings_fr.properties @@ -299,6 +299,8 @@ market.trades.tooltip.candle.date=Date: offerbook.createOffer=Créer une offre offerbook.takeOffer=Prendre une offre +offerbook.takeOfferToBuy=Take offer to buy {0} +offerbook.takeOfferToSell=Take offer to sell {0} offerbook.trader=Trader offerbook.offerersBankId=ID de la banque du maker (BIC/SWIFT): {0} offerbook.offerersBankName=Nom de la banque du maker : {0} @@ -503,97 +505,97 @@ portfolio.pending.step2_buyer.altcoin=Merci de transférer de votre portefeuille # suppress inspection "TrailingSpacesInProperty" portfolio.pending.step2_buyer.cash=Rendez vous à une banque et payer {0} au vendeur de BTC.\n\n portfolio.pending.step2_buyer.cash.extra=CRITÈRES IMPORTANTS: \nAprès avoir effectuer le paiement veuillez écrire sur le reçu papier : PAS DE REMBOURSEMENT.\nPuis déchirer le en 2, prenez en une photo et envoyer le à l'adresse email du vendeur de BTC. -portfolio.pending.step2_buyer.moneyGram=Please pay {0} to the BTC seller by using MoneyGram.\n\n -portfolio.pending.step2_buyer.moneyGram.extra=IMPORTANT REQUIREMENT:\nAfter you have done the payment send the Authorisation number and a photo of the receipt by email to the BTC seller.\nThe receipt must clearly show the seller''s full name, country, state and the amount. The seller''s email is: {0}. -portfolio.pending.step2_buyer.westernUnion=Please pay {0} to the BTC seller by using Western Union.\n\n -portfolio.pending.step2_buyer.westernUnion.extra=IMPORTANT REQUIREMENT:\nAfter you have done the payment send the MTCN (tracking number) and a photo of the receipt by email to the BTC seller.\nThe receipt must clearly show the seller''s full name, city, country and the amount. The seller''s email is: {0}. +portfolio.pending.step2_buyer.moneyGram=Veuillez s'il vous plaît payer {0} au vendeur de BTC en utilisant MoneyGram.\n\n +portfolio.pending.step2_buyer.moneyGram.extra=CONDITION REQUISE IMPORTANTE:\nAprès avoir effectué le paiement envoyez le numéro d'Autorisation et une photo du reçu par e-mail au vendeur de BTC.\nLe reçu doit faire clairement figurer le nom complet du vendeur, son pays, son état et le montant. L'e-mail du vendeur est: {0}. +portfolio.pending.step2_buyer.westernUnion=Veuillez s'il vous plaît payer {0} au vendeur de BTC en utilisant Western Union.\n\n +portfolio.pending.step2_buyer.westernUnion.extra=CONDITION REQUISE IMPORTANTE:\nAprès avoir effectué le paiement envoyez le MTCN (numéro de suivi) et une photo du reçu par e-mail au vendeur de BTC.\nLe reçu doit faire clairement figurer le nom complet du vendeur, son pays, son état et le montant. L'e-mail du vendeur est: {0}. # suppress inspection "TrailingSpacesInProperty" portfolio.pending.step2_buyer.postal=Merci d'envoyer {0} par \"US Postal Money Order\" au vendeur de BTC.\n\n # suppress inspection "TrailingSpacesInProperty" portfolio.pending.step2_buyer.bank=Merci de vous rendre sur votre site de banque en ligne et payer {0} au vendeur de BTC.\n\n -portfolio.pending.step2_buyer.f2f=Please contact the BTC seller by the provided contact and arrange a meeting to pay {0}.\n\n +portfolio.pending.step2_buyer.f2f=Veuillez s'il vous plaît contacter le vendeur de BTC avec le moyen de contact fourni, et planifier une entrevue pour payer {0}.\n\n portfolio.pending.step2_buyer.startPaymentUsing=Initier le paiement en utilisant {0} -portfolio.pending.step2_buyer.amountToTransfer=Amount to transfer -portfolio.pending.step2_buyer.sellersAddress=Seller''s {0} address -portfolio.pending.step2_buyer.buyerAccount=Your payment account to be used +portfolio.pending.step2_buyer.amountToTransfer=Montant à transférer +portfolio.pending.step2_buyer.sellersAddress=Adresse {0} du vendeur +portfolio.pending.step2_buyer.buyerAccount=Votre compte de paiement à utiliser portfolio.pending.step2_buyer.paymentStarted=Paiement initié portfolio.pending.step2_buyer.warn=Vous n'avez toujours pas effectué votre paiement {0}!\nVeuillez noter que cette transaction doit être effectuée avant {1} sinon la transaction sera inspectée par un arbitre. portfolio.pending.step2_buyer.openForDispute=Vous n'avez toujours pas effectué votre paiement!\nLa période max pour cette transaction est terminée.\n\nMerci de contacter l'arbitre afin d'ouvrir une dispute. portfolio.pending.step2_buyer.paperReceipt.headline=Avez-vous envoyé le preuve d'achat au vendeur de BTC? portfolio.pending.step2_buyer.paperReceipt.msg=Rappelez-vous: \nVous devez écrire sur le reçu papier: PAS DE REMBOURSEMENT.\nEnsuite, le déchirer en deux, faire une photo et l'envoyer à l'adresse email du vendeur. -portfolio.pending.step2_buyer.moneyGramMTCNInfo.headline=Send Authorisation number and receipt -portfolio.pending.step2_buyer.moneyGramMTCNInfo.msg=You need to send the Authorisation number and a photo of the receipt by email to the BTC seller.\nThe receipt must clearly show the seller''s full name, country, state and the amount. The seller''s email is: {0}.\n\nDid you send the Authorisation number and contract to the seller? -portfolio.pending.step2_buyer.westernUnionMTCNInfo.headline=Send MTCN and receipt -portfolio.pending.step2_buyer.westernUnionMTCNInfo.msg=You need to send the MTCN (tracking number) and a photo of the receipt by email to the BTC seller.\nThe receipt must clearly show the seller''s full name, city, country and the amount. The seller''s email is: {0}.\n\nDid you send the MTCN and contract to the seller? -portfolio.pending.step2_buyer.halCashInfo.headline=Send HalCash code -portfolio.pending.step2_buyer.halCashInfo.msg=You need to send a text message with the HalCash code as well as the trade ID ({0}) to the BTC seller.\nThe seller''s mobile nr. is {1}.\n\nDid you send the code to the seller? -portfolio.pending.step2_buyer.fasterPaymentsHolderNameInfo=Some banks might require the receiver's name. The UK sort code and account number is sufficient for a Faster Payment transfer and the receivers name is not verified by any of the banks. +portfolio.pending.step2_buyer.moneyGramMTCNInfo.headline=Envoyer numéro d'Autorisation et reçu +portfolio.pending.step2_buyer.moneyGramMTCNInfo.msg=Vous devez envoyez le numéro d'Autorisation et une photo du reçu par e-mail au vendeur de BTC.\nLe reçu doit faire clairement figurer le nom complet du vendeur, son pays, son état et le montant. L'e-mail du vendeur est: {0}.\n\nAvez-vous envoyé le numéro d'Autorisation et le contrat au vendeur ? +portfolio.pending.step2_buyer.westernUnionMTCNInfo.headline=Envoyer MTCN et reçu +portfolio.pending.step2_buyer.westernUnionMTCNInfo.msg=Vous devez envoyez le MTCN (numéro de suivi) et une photo du reçu par e-mail au vendeur de BTC.\nLe reçu doit faire clairement figurer le nom complet du vendeur, son pays, son état et le montant. L'e-mail du vendeur est: {0}.\n\nAvez-vous envoyé le MTCN et le contrat au vendeur ? +portfolio.pending.step2_buyer.halCashInfo.headline=Envoyer le code HalCash +portfolio.pending.step2_buyer.halCashInfo.msg=Vous devez envoyez un message texte avec le code HalCash ainsi que l'ID de la transaction ({0}) au vendeur de BTC.\nLe numéro de mobile du vendeur est {1}.\n\nAvez-vous envoyé le code au vendeur ? +portfolio.pending.step2_buyer.fasterPaymentsHolderNameInfo=Certaines banques peuvent exiger le nom du bénéficiaire. Au Royaume-Uni, le sort code avec le numéro de compte est suffisant pour un transfert Faster Payment et le nom du bénéficiaire n'est vérifié par aucune banque. portfolio.pending.step2_buyer.confirmStart.headline=Confirmez que vous avez initié le paiement portfolio.pending.step2_buyer.confirmStart.msg=Avez-vous initié le {0} paiement à votre partenaire commercial? portfolio.pending.step2_buyer.confirmStart.yes=Oui, j'ai initié le paiement portfolio.pending.step2_seller.waitPayment.headline=En attente du paiement -portfolio.pending.step2_seller.f2fInfo.headline=Buyer's contact information +portfolio.pending.step2_seller.f2fInfo.headline=Fiche de contact acheteur portfolio.pending.step2_seller.waitPayment.msg=La transaction de dépôt a au moins une confirmation de la blockchain.\nVous devez attendre que l'acheteur de BTC débute le {0} payment. -portfolio.pending.step2_seller.warn=The BTC buyer still has not done the {0} payment.\nYou need to wait until they have started the payment.\nIf the trade has not been completed on {1} the arbitrator will investigate. -portfolio.pending.step2_seller.openForDispute=The BTC buyer has not started his payment!\nThe max. allowed period for the trade has elapsed.\nYou can wait longer and give the trading peer more time or contact the arbitrator for opening a dispute. +portfolio.pending.step2_seller.warn=L'acheteur de BTC n'a toujours pas effectué le paiement {0}.\nVeuillez attendre qu'il effectue celui-ci.\nSi la transaction n'est pas effectuée le {1}, un arbitre enquêtera. +portfolio.pending.step2_seller.openForDispute=L'acheteur de BTC n'a pas démarré son paiement!\nLe temps max. alloué pour la transaction est écoulé.\nVous pouvez attendre encore pour laisser plus de temps à l'autre participant, ou contacter l'arbitre pour ouvrir une dispute. # suppress inspection "UnusedProperty" -message.state.UNDEFINED=Undefined +message.state.UNDEFINED=Indéfini # suppress inspection "UnusedProperty" -message.state.SENT=Message sent +message.state.SENT=Message envoyé # suppress inspection "UnusedProperty" -message.state.ARRIVED=Message arrived at peer +message.state.ARRIVED=Message reçu par le destinataire # suppress inspection "UnusedProperty" -message.state.STORED_IN_MAILBOX=Message stored in mailbox +message.state.STORED_IN_MAILBOX=Message stocké dans la boîte de réception # suppress inspection "UnusedProperty" -message.state.ACKNOWLEDGED=Peer confirmed message receipt +message.state.ACKNOWLEDGED=Le destinataire a accusé réception du message # suppress inspection "UnusedProperty" -message.state.FAILED=Sending message failed +message.state.FAILED=Echec de l'envoi du message portfolio.pending.step3_buyer.wait.headline=En attente de la confirmation de paiement du vendeur BTC portfolio.pending.step3_buyer.wait.info=Nous attendons que le vendeur confirme le preuve d'achat du paiement {0} . -portfolio.pending.step3_buyer.wait.msgStateInfo.label=Payment started message status +portfolio.pending.step3_buyer.wait.msgStateInfo.label=Statut du message de paiement initié portfolio.pending.step3_buyer.warn.part1a=sur la {0} blockchain portfolio.pending.step3_buyer.warn.part1b=chez votre fournisseur de services bancaires portfolio.pending.step3_buyer.warn.part2=Le vendeur de BTC n'a toujours pas confirmé votre paiement!\nVeuillez vérifier {0} si l'envoi du paiement a été effectuer.\nSi le vendeur ne confirme pas la réception du paiement avant {1} la transaction fera l'objet d'une enquête par l'arbitre. -portfolio.pending.step3_buyer.openForDispute=The BTC seller has not confirmed your payment!\nThe max. period for the trade has elapsed.\nYou can wait longer and give the trading peer more time or contact the arbitrator for opening a dispute. +portfolio.pending.step3_buyer.openForDispute=Le vendeur de BTC n'a pas confirmé votre paiement!\nLe temps max. alloué pour la transaction est écoulé.\nVous pouvez attendre encore pour laisser plus de temps à l'autre participant, ou contacter l'arbitre pour ouvrir une dispute. # suppress inspection "TrailingSpacesInProperty" -portfolio.pending.step3_seller.part=Votre partenaire d'échange a confirmé qu'il a commencé à vous payer {0}.\n -portfolio.pending.step3_seller.altcoin.explorer=on your favorite {0} blockchain explorer -portfolio.pending.step3_seller.altcoin.wallet=at your {0} wallet -portfolio.pending.step3_seller.altcoin={0}Please check {1} if the transaction to your receiving address\n{2}\nhas already sufficient blockchain confirmations.\nThe payment amount has to be {3}\n\nYou can copy & paste your {4} address from the main screen after closing that popup. -portfolio.pending.step3_seller.postal={0}Please check if you have received {1} with \"US Postal Money Order\" from the BTC buyer.\n\nThe trade ID (\"reason for payment\" text) of the transaction is: \"{2}\" -portfolio.pending.step3_seller.bank=Your trading partner has confirmed that he initiated the {0} payment.\n\nPlease go to your online banking web page and check if you have received {1} from the BTC buyer.\n\nThe trade ID (\"reason for payment\" text) of the transaction is: \"{2}\"\n\n -portfolio.pending.step3_seller.cash=Because the payment is done via Cash Deposit the BTC buyer has to write \"NO REFUND\" on the paper receipt, tear it in 2 parts and send you a photo by email.\n\nTo avoid chargeback risk, only confirm if you received the email and if you are sure the paper receipt is valid.\nIf you are not sure, {0} -portfolio.pending.step3_seller.moneyGram=The buyer has to send you the Authorisation number and a photo of the receipt by email.\nThe receipt must clearly show your full name, country, state and the amount. Please check your email if you received the Authorisation number.\n\nAfter closing that popup you will see the BTC buyer's name and address for picking up the money from MoneyGram.\n\nOnly confirm receipt after you have successfully picked up the money! -portfolio.pending.step3_seller.westernUnion=The buyer has to send you the MTCN (tracking number) and a photo of the receipt by email.\nThe receipt must clearly show your full name, city, country and the amount. Please check your email if you received the MTCN.\n\nAfter closing that popup you will see the BTC buyer's name and address for picking up the money from Western Union.\n\nOnly confirm receipt after you have successfully picked up the money! -portfolio.pending.step3_seller.halCash=The buyer has to send you the HalCash code as text message. Beside that you will receive a message from HalCash with the required information to withdraw the EUR from a HalCash supporting ATM.\n\nAfter you have picked up the money from the ATM please confirm here the receipt of the payment! +portfolio.pending.step3_seller.part=Your trading partner has confirmed that they have initiated the {0} payment.\n\n +portfolio.pending.step3_seller.altcoin.explorer=dans votre explorateur de blockchain {0} favorite +portfolio.pending.step3_seller.altcoin.wallet=à votre portefeuille {0} +portfolio.pending.step3_seller.altcoin={0}Veuillez s'il vous plaît vérifier {1} si la transaction vers votre adresse de réception\n{2}\na suffisament de confirmations pour la blockchain.\nLe montant du paiment doit être {3}\n\nVous pouver copier & coller votre adresse {4} à partir de l'écran principal après avoir fermé ce popup. +portfolio.pending.step3_seller.postal={0}Veuillez s'il vous plaît vérifier si vous avez reçu {1} avec \"US Postal Money Order\" de la part de l'acheteur de BTC.\n\nL'ID de la transaction (indiqué dans \"reason for payment\") est: \"{2}\" +portfolio.pending.step3_seller.bank=Your trading partner has confirmed that they have initiated the {0} payment.\n\nPlease go to your online banking web page and check if you have received {1} from the BTC buyer.\n\nThe trade ID (\"reason for payment\" text) of the transaction is: \"{2}\"\n\n +portfolio.pending.step3_seller.cash=Comme le paiement est réalisé via Cash Deposit l'acheteur de BTC doit inscrire \"NO REFUND\" sur le reçu papier, le déchirer en 2 parties et vous envoyer une photo par e-mail.\n\nPour éviter un risque de rétrofacturation, ne confirmez que si vous recevez le mail et que vous êtes sûr que le reçu papier est valide.\nSi vous n'êtes pas sûr, {0} +portfolio.pending.step3_seller.moneyGram=L'acheteur doit vous envoyer le numéro d'Autorisation et une photo du reçu par e-mail .\nLe reçu doit faire clairement figurer votre nom complet, votre pays, votre état et le montant. Veuillez s'il vous plaît vérifier si vous avez reçu par e-mail le numéro d'Autorisation.\n\nAprès avoir fermé ce popup vous verrez le nom de l'acheteur de BTC et l'adresse où retirer l'argent depuis MoneyGram.\n\nN'accusez réception qu'après avoir retiré l'argent avec succès! +portfolio.pending.step3_seller.westernUnion=L'acheteur doit vous envoyer le MTCN (numéro de suivi) et une photo du reçu par e-mail .\nLe reçu doit faire clairement figurer votre nom complet, votre pays, votre état et le montant. Veuillez s'il vous plaît vérifier si vous avez reçu par e-mail le MTCN.\n\nAprès avoir fermé ce popup vous verrez le nom de l'acheteur de BTC et l'adresse où retirer l'argent depuis Western Union.\n\nN'accusez réception qu'après avoir retiré l'argent avec succès! +portfolio.pending.step3_seller.halCash=L'acheteur doit vous envoyer le code HalCash en message texte. Par ailleurs, vous recevrez un message de la part d'HalCash avec les informations nécessaires pour retirer les EUR depuis un Guichet Automatique Bancaire supportant HalCash.\n\nAprès avoir retiré l'argent du guichet, veuillez ici s'il vous plaît accuser réception du paiement! -portfolio.pending.step3_seller.bankCheck=\n\nPlease also verify that the sender's name in your bank statement matches that one from the trade contract:\nSender's name: {0}\n\nIf the name is not the same as the one displayed here, {1} -portfolio.pending.step3_seller.openDispute=please don't confirm but open a dispute by entering \"alt + o\" or \"option + o\". +portfolio.pending.step3_seller.bankCheck=\n\nVérifiez aussi s'il vous plaît que le nom de l'émetteur sur votre récapitulatif bancaire correspond à celui du contrat de la transaction:\nNom de l'émetteur: {0}\n\nSi le nom n'est pas le même que celui indiqué ici, {1} +portfolio.pending.step3_seller.openDispute=ne confirmez pas s'il vous plaît, mais entamez plutôt une dispute en tapant \"alt + o\" ou \"option + o\". portfolio.pending.step3_seller.confirmPaymentReceipt=Confirmez le preuve d'achat -portfolio.pending.step3_seller.amountToReceive=Amount to receive -portfolio.pending.step3_seller.yourAddress=Your {0} address -portfolio.pending.step3_seller.buyersAddress=Buyers {0} address -portfolio.pending.step3_seller.yourAccount=Your trading account -portfolio.pending.step3_seller.buyersAccount=Buyers trading account +portfolio.pending.step3_seller.amountToReceive=Montant à recevoir +portfolio.pending.step3_seller.yourAddress=Votre adresse {0} +portfolio.pending.step3_seller.buyersAddress=Adresse {0} de l'acheteur +portfolio.pending.step3_seller.yourAccount=Votre compte de transaction +portfolio.pending.step3_seller.buyersAccount=Compte de transaction de l'acheteur portfolio.pending.step3_seller.confirmReceipt=Confirmez le preuve d'achat portfolio.pending.step3_seller.buyerStartedPayment=L'acheteur BTC a commencé le {0} paiement.\n{1} -portfolio.pending.step3_seller.buyerStartedPayment.altcoin=Check for blockchain confirmations at your altcoin wallet or block explorer and confirm the payment when you have sufficient blockchain confirmations. -portfolio.pending.step3_seller.buyerStartedPayment.fiat=Check at your trading account (e.g. bank account) and confirm when you have received the payment. +portfolio.pending.step3_seller.buyerStartedPayment.altcoin=Surveillez les confirmations de la blockchain depuis votre portefeuille altcoin ou depuis un explorateur de blocs, et confirmez le paiement quand vous aurez suffisamment de confirmations de la blockchain. +portfolio.pending.step3_seller.buyerStartedPayment.fiat=Surveillez votre compte de transaction (par exemple votre compte bancaire) et confirmez quand vous aurez reçu le paiement. portfolio.pending.step3_seller.warn.part1a=sur la {0} blockchain portfolio.pending.step3_seller.warn.part1b=chez votre fournisseur de services bancaires -portfolio.pending.step3_seller.warn.part2=You still have not confirmed the receipt of the payment!\nPlease check {0} if you have received the payment.\nIf you don''t confirm receipt by {1} the trade will be investigated by the arbitrator. -portfolio.pending.step3_seller.openForDispute=You have not confirmed the receipt of the payment!\nThe max. period for the trade has elapsed.\nPlease confirm or contact the arbitrator for opening a dispute. +portfolio.pending.step3_seller.warn.part2=Vous n'avez toujours pas accusé réception du paiement!\nVeuillez vérifier {0} si vous avez reçu le paiement.\nSi vous n'accusez pas réception avant {1} la transaction fera l'objet d'une enquête par l'arbitre. +portfolio.pending.step3_seller.openForDispute=Vous n'avez pas accusé réception du paiement!\nLe temps max. alloué pour la transaction est écoulé.\nVeuillez s'il vous plaît confirmer ou contacter l'arbitre pour ouvrir une dispute. # suppress inspection "TrailingSpacesInProperty" portfolio.pending.step3_seller.onPaymentReceived.part1=Avez-vous reçu le paiement {0} de votre partenaire d'échange?\n\n # suppress inspection "TrailingSpacesInProperty" -portfolio.pending.step3_seller.onPaymentReceived.fiat=The trade ID (\"reason for payment\" text) of the transaction is: \"{0}\"\n\n +portfolio.pending.step3_seller.onPaymentReceived.fiat=L'ID de la transaction (le texte \"reason for payment\") est: \"{0}\"\n\n # suppress inspection "TrailingSpacesInProperty" -portfolio.pending.step3_seller.onPaymentReceived.name=Please also verify that the sender's name in your bank statement matches that one from the trade contract:\nSender's name: {0}\n\nIf the name is not the same as the one displayed here, please don't confirm but open a dispute by entering \"alt + o\" or \"option + o\".\n\n -portfolio.pending.step3_seller.onPaymentReceived.note=Please note, that as soon you have confirmed the receipt, the locked trade amount will be released to the BTC buyer and the security deposit will be refunded. +portfolio.pending.step3_seller.onPaymentReceived.name=Vérifiez aussi s'il vous plaît que le nom de l'émetteur sur votre récapitulatif bancaire correspond à celui du contrat de la transaction:\nNom de l'émetteur: {0}\n\nSi le nom n'est pas le même que celui indiqué ici, veuillez s'il vous plaît ne pas confirmer et ouvrez une dispute en tapant \"alt + o\" ou \"option + o\".\n\n +portfolio.pending.step3_seller.onPaymentReceived.note=Tenez s'il vous plaît compte du fait que, aussitôt que vous accusez réception, le montant bloqué de la transaction sera transmis à l'acheteur de BTC et que le dépôt de garantie sera remboursé. portfolio.pending.step3_seller.onPaymentReceived.confirm.headline=Confirmez que vous avez reçu le paiement portfolio.pending.step3_seller.onPaymentReceived.confirm.yes=Oui, j'ai reçu le paiement @@ -601,40 +603,40 @@ portfolio.pending.step5_buyer.groupTitle=Résumé de l'échange complet portfolio.pending.step5_buyer.tradeFee=Frais de transaction portfolio.pending.step5_buyer.makersMiningFee=Frais de minage portfolio.pending.step5_buyer.takersMiningFee=Total des frais de minage -portfolio.pending.step5_buyer.refunded=Refunded security deposit +portfolio.pending.step5_buyer.refunded=Dépôt de garantie remboursé portfolio.pending.step5_buyer.withdrawBTC=Retirer vos bitcoins -portfolio.pending.step5_buyer.amount=Amount to withdraw -portfolio.pending.step5_buyer.withdrawToAddress=Withdraw to address +portfolio.pending.step5_buyer.amount=Montant à retirer +portfolio.pending.step5_buyer.withdrawToAddress=Retirer à l'adresse portfolio.pending.step5_buyer.moveToBisqWallet=Transférer les fonds au portefeuille bisq portfolio.pending.step5_buyer.withdrawExternal=Retrait à un portefeuille externe portfolio.pending.step5_buyer.alreadyWithdrawn=Vos fonds ont déjà été retirés. Merci de vérifier votre historique de transactions. portfolio.pending.step5_buyer.confirmWithdrawal=Confirmer la demande de retrait -portfolio.pending.step5_buyer.amountTooLow=The amount to transfer is lower than the transaction fee and the min. possible tx value (dust). +portfolio.pending.step5_buyer.amountTooLow=Le montant à transférer est plus bas que les frais de transaction et que la valeur min. possible pour une tx (poussière). portfolio.pending.step5_buyer.withdrawalCompleted.headline=Retrait effectué -portfolio.pending.step5_buyer.withdrawalCompleted.msg=Your completed trades are stored under \"Portfolio/History\".\nYou can review all your bitcoin transactions under \"Funds/Transactions\" -portfolio.pending.step5_buyer.bought=You have bought -portfolio.pending.step5_buyer.paid=You have paid +portfolio.pending.step5_buyer.withdrawalCompleted.msg=Vos transactions effectuées sont stockées dans /"Historique du portefeuille\".\nVous pouvez retrouver toutes vos transactions de bitcoin dans \"Transactions de fonds\" +portfolio.pending.step5_buyer.bought=Vous avez acheté +portfolio.pending.step5_buyer.paid=Vous avez payé -portfolio.pending.step5_seller.sold=You have sold -portfolio.pending.step5_seller.received=You have received +portfolio.pending.step5_seller.sold=Vous avez vendu +portfolio.pending.step5_seller.received=Vous avez reçu -tradeFeedbackWindow.title=Congratulations on completing your trade -tradeFeedbackWindow.msg.part1=We'd love to hear back from you about your experience. It'll help us to improve the software and to smooth out any rough edges. If you'd like to provide feedback, please fill out this short survey (no registration required) at: -tradeFeedbackWindow.msg.part2=If you have any questions, or experienced any problems, please get in touch with other users and contributors via the Bisq forum at: -tradeFeedbackWindow.msg.part3=Thanks for using Bisq! +tradeFeedbackWindow.title=Félicitations pour avoir achevé votre transaction +tradeFeedbackWindow.msg.part1=Nous aimerions votre retour à propos de votre expérience. Cela nous aiderait à améliorer le logiciel et éventuellement à arrondir les angles. Si vous souhaitez transmettre une réaction, remplissez s'il vous plaît ce rapide questionnaire (pas d'inscription nécessaire) à: +tradeFeedbackWindow.msg.part2=Si vous avez la moindre question, ou rencontrez le moindre problème, veuillez s'il vous plaît vous mettre en relation avec les autres utilisateurs et contributeurs via le Bisq forum à: +tradeFeedbackWindow.msg.part3=Merci d'utiliser Bisq! portfolio.pending.role=Mon rôle portfolio.pending.tradeInformation=Information de l'échange portfolio.pending.remainingTime=Temps restant -portfolio.pending.remainingTimeDetail={0} (until {1}) -portfolio.pending.tradePeriodInfo=After the first blockchain confirmation, the trade period starts. Based on the payment method used, a different maximum allowed trade period is applied. -portfolio.pending.tradePeriodWarning=If the period is exceeded both traders can open a dispute. +portfolio.pending.remainingTimeDetail={0} (jusqu'au {1}) +portfolio.pending.tradePeriodInfo=Après la première confirmation de la blockchain, la période de transaction débute. Selon la méthode de paiement utilisée, une période maximum allouée à la transaction est appliquée. +portfolio.pending.tradePeriodWarning=Si la période est écoulée, l'un ou l'autre des participants de la transaction peut ouvrir une dispute. portfolio.pending.tradeNotCompleted=Le trade n'est pas terminé à temps (jusqu'à {0}) portfolio.pending.tradeProcess=Processus de transaction -portfolio.pending.openAgainDispute.msg=If you are not sure that the message to the arbitrator arrived (e.g. if you did not get a response after 1 day) feel free to open a dispute again. +portfolio.pending.openAgainDispute.msg=Si vous n'êtes pas sûr que le message adressé à l'arbitre soit arrivé (par exemple si vous n'avez pas reçu de réponse au bout d'1 journée) n'hésitez pas à ouvrir une dispute à nouveau. portfolio.pending.openAgainDispute.button=Rouvrir la dispute portfolio.pending.openSupportTicket.headline=Ouvrir un ticket d'assistance -portfolio.pending.openSupportTicket.msg=Please use that only in emergency case if you don't get displayed a \"Open support\" or \"Open dispute\" button.\n\nWhen you open a support ticket the trade will be interrupted and handled by the arbitrator +portfolio.pending.openSupportTicket.msg=Merci de ne procéder à cela qu'en cas d'urgence si les boutons \"Obtenir un soutien\" ou \"Ouvrir une dispute\" ne s'affichent pas.\n\nQuand vous ouvrez un ticket de soutien la transaction est interrompue et prise en charge par l'arbitre portfolio.pending.notification=Notification portfolio.pending.openDispute=Déclencher une dispute portfolio.pending.disputeOpened=Dispute ouverte @@ -648,7 +650,7 @@ portfolio.pending.disputeOpenedMyUser=Vous avez déjà ouvert une dispute.\n{0} portfolio.pending.disputeOpenedByPeer=L'autre trader a ouvert une dispute\n{0} portfolio.pending.supportTicketOpenedByPeer=L'autre trader a ouvert un ticket d'assistance.\n{0} portfolio.pending.noReceiverAddressDefined=Aucune adresse de destinataire définie -portfolio.pending.removeFailedTrade=If the arbitrator could not close that trade you can move it yourself to the failed trades screen.\nDo you want to remove that failed trade from the Pending trades screen? +portfolio.pending.removeFailedTrade=Si l'arbitre ne peut clore la transaction, vous pouvez vous-même la déplacer dans le panneau des transactions échouées.\nVoulez-vous supprimer cette transaction échouée du panneau des transactions en attente ? portfolio.closed.completed=Terminé portfolio.closed.ticketClosed=Ticket fermé portfolio.closed.canceled=Annulé @@ -670,8 +672,8 @@ funds.deposit.usedInTx=Utilisé dans {0} transaction(s) funds.deposit.fundBisqWallet=Alimenter votre portefeuille funds.deposit.noAddresses=Aucune adresse de dépôt n'a encore été générée funds.deposit.fundWallet=Alimenter votre portefeuille -funds.deposit.withdrawFromWallet=Send funds from wallet -funds.deposit.amount=Amount in BTC (optional) +funds.deposit.withdrawFromWallet=Transférer des fonds depuis le portefeuille +funds.deposit.amount=Montant en BTC (optionnel) funds.deposit.generateAddress=Générer une nouvelle adresse funds.deposit.selectUnused=Merci de sélectionner une adresse inutilisée dans le tableau ci-dessus plutôt que d'en générer une nouvelle. @@ -681,10 +683,10 @@ funds.withdrawal.useAllInputs=Utilisez toutes les entrées disponibles funds.withdrawal.useCustomInputs=Utiliser des entrées personnalisées funds.withdrawal.receiverAmount=Montant du destinataire funds.withdrawal.senderAmount=Montant de l'expéditeur -funds.withdrawal.feeExcluded=Amount excludes mining fee -funds.withdrawal.feeIncluded=Amount includes mining fee -funds.withdrawal.fromLabel=Withdraw from address -funds.withdrawal.toLabel=Withdraw to address +funds.withdrawal.feeExcluded=Montant hormis frais de minage +funds.withdrawal.feeIncluded=Montant incluant frais de minage +funds.withdrawal.fromLabel=Retirer depuis l'adresse +funds.withdrawal.toLabel=Retirer vers l'adresse funds.withdrawal.withdrawButton=Envoyer les fonds funds.withdrawal.noFundsAvailable=Aucun fond disponible à retirer funds.withdrawal.confirmWithdrawalRequest=Confirmer la requête de retrait @@ -695,22 +697,22 @@ funds.withdrawal.selectAddress=Sélectionnez une adresse source depuis le tablea funds.withdrawal.setAmount=Définir le montant à retirer funds.withdrawal.fillDestAddress=Complétez votre adresse de destination funds.withdrawal.warn.noSourceAddressSelected=Vous devez sélectionner une adresse source dans le tableau ci-dessus. -funds.withdrawal.warn.amountExceeds=You don't have sufficient funds available from the selected address.\nConsider to select multiple addresses in the table above or change the fee toggle to include the miner fee. +funds.withdrawal.warn.amountExceeds=Vous ne disposez pas de suffisamment de fonds aux adresses selectionnées.\nConsidérez une multiple sélection d'adresses dans la table ci-dessus ou changez la position de la bascule de frais de manière à inclure les frais de minage. funds.reserved.noFunds=Aucun fonds n'est utilisé dans des offres. funds.reserved.reserved=Bloqué dans votre portefeuille local pour l'offre avec l'ID : {0} funds.locked.noFunds=Aucun fonds n'est bloqué dans des transactions. -funds.locked.locked=Locked in multisig for trade with ID: {0} +funds.locked.locked=Vérouillés en multisig pour la transaction d'ID: {0} funds.tx.direction.sentTo=Envoyer à: funds.tx.direction.receivedWith=Recevoir avec: -funds.tx.direction.genesisTx=From Genesis tx: -funds.tx.txFeePaymentForBsqTx=Miner fee for BSQ tx +funds.tx.direction.genesisTx=Genesis tx référente: +funds.tx.txFeePaymentForBsqTx=Frais de minage pour la tx BSQ funds.tx.createOfferFee=Frais maker et réseau : {0} funds.tx.takeOfferFee=Frais taker et réseau : {0} -funds.tx.multiSigDeposit=Multisig deposit: {0} -funds.tx.multiSigPayout=Multisig payout: {0} +funds.tx.multiSigDeposit=Dépôt multisig: {0} +funds.tx.multiSigPayout=Paiement multisig: {0} funds.tx.disputePayout=Remboursement dispute: {0} funds.tx.disputeLost=Dossier de dispute perdus: {0} funds.tx.unknown=Raison inconnue: {0} @@ -720,9 +722,9 @@ funds.tx.withdrawnFromWallet=Retiré depuis le portefeuille funds.tx.noTxAvailable=Aucune transaction disponible funds.tx.revert=Défaire funds.tx.txSent=Transaction envoyée avec succès à la nouvelle adresse dans le portefeuille local bisq. -funds.tx.direction.self=Sent to yourself -funds.tx.daoTxFee=Miner fee for DAO tx -funds.tx.reimbursementRequestTxFee=Reimbursement request +funds.tx.direction.self=Envoyés à vous-même +funds.tx.daoTxFee=Frais de mineur pour la tx DAO +funds.tx.reimbursementRequestTxFee=Demande de remboursement funds.tx.compensationRequestTxFee=Requête de compensation @@ -733,11 +735,11 @@ funds.tx.compensationRequestTxFee=Requête de compensation support.tab.support=Tickets d'assistance support.tab.ArbitratorsSupportTickets=Ticket de support arbitre support.tab.TradersSupportTickets=Ticket de support Trader -support.filter=Filter list +support.filter=Liste de filtre support.noTickets=Il n'y a aucun ticket ouvert support.sendingMessage=Envoi du message... support.receiverNotOnline=Le destinataire n'est pas connecté. Le message est envoyé à sa boîte de réception. -support.sendMessageError=Sending message failed. Error: {0} +support.sendMessageError=Échec de l'envoi du message. Erreur: {0} support.wrongVersion=The offer in that dispute has been created with an older version of Bisq.\nYou cannot close that dispute with your version of the application.\n\nPlease use an older version with protocol version {0} support.openFile=Open file to attach (max. file size: {0} kb) support.attachmentTooLarge=The total size of your attachments is {0} kb and is exceeding the max. allowed message size of {1} kB. @@ -926,10 +928,10 @@ account.arbitratorSelection.minOne=Vous devez sélectionner un arbitre. account.altcoin.yourAltcoinAccounts=Your altcoin accounts account.altcoin.popup.wallet.msg=Please be sure that you follow the requirements for the usage of {0} wallets as described on the {1} web page.\nUsing wallets from centralized exchanges where (a) you don''t control your keys or (b) which don''t use compatible wallet software is risky: it can lead to loss of the traded funds!\nThe arbitrator is not a {2} specialist and cannot help in such cases. account.altcoin.popup.wallet.confirm=Je comprends et confirme que je sais quel portefeuille je dois utiliser. -account.altcoin.popup.xmr.msg=If you want to trade XMR on Bisq please be sure you understand and fulfill the following requirements:\n\nFor sending XMR you need to use either the official Monero GUI wallet or Monero CLI wallet with the store-tx-info flag enabled (default in new versions). Please be sure you can access the tx key as that would be required in case of a dispute.\nmonero-wallet-cli (use the command get_tx_key)\nmonero-wallet-gui (go to history tab and click on the (P) button for payment proof)\n\nIn addition to XMR checktx tool (https://xmr.llcoins.net/checktx.html) verification can also be accomplished in-wallet.\nmonero-wallet-cli : using command (check_tx_key).\nmonero-wallet-gui : on the Advanced > Prove/Check page.\nAt normal block explorers the transfer is not verifiable.\n\nYou need to provide the arbitrator the following data in case of a dispute:\n- The tx private key\n- The transaction hash\n- The recipient's public address\n\nIf you cannot provide the above data or if you used an incompatible wallet it would result in losing the dispute case. The XMR sender is responsible to be able to verify the XMR transfer to the arbitrator in case of a dispute.\n\nThere is no payment ID required, just the normal public address.\nIf you are not sure about that process visit (https://www.getmonero.org/resources/user-guides/prove-payment.html) or the Monero forum (https://forum.getmonero.org) to find more information. -account.altcoin.popup.blur.msg=If you want to trade BLUR on Bisq please be sure you understand and fulfill the following requirements:\n\nTo send BLUR you must use the Blur Network CLI or GUI Wallet. \n\nIf you are using the CLI wallet, a transaction hash (tx ID) will be displayed after a transfer is sent. You must save this information. Immediately after sending the transfer, you must use the command 'get_tx_key' to retrieve the transaction private key. If you fail to perform this step, you may not be able to retrieve the key later. \n\nIf you are using the Blur Network GUI Wallet, the transaction private key and transaction ID can be found conveniently in the "History" tab. Immediately after sending, locate the transaction of interest. Click the "?" symbol in the lower-right corner of the box containing the transaction. You must save this information. \n\nIn the event that arbitration is necessary, you must present the following to an arbitrator: 1.) the transaction ID, 2.) the transaction private key, and 3.) the recipient's address. The arbitrator will then verify the BLUR transfer using the Blur Transaction Viewer (https://blur.cash/#tx-viewer).\n\nIf you cannot provide the required information to the arbitrator, you will lose the dispute. In all cases of dispute, the BLUR sender bears 100% of the burden of responsiblity in verifying transactions to an arbitrator. \n\nIf you do not understand these requirements, do not trade on Bisq. First, seek help at the Blur Network Discord (https://discord.gg/dMWaqVW). -account.altcoin.popup.ccx.msg=If you want to trade CCX on Bisq please be sure you understand the following requirements:\n\nTo send CCX you must use an official Conceal wallet, either CLI or GUI. After sending a transfer payment, the wallets\ndisplay the transaction secret key. You must save it along with the transaction hash (ID) and the recipient's public\naddress in case arbitration is necessary. In such a case, you must give all three to the arbitrator, who will then\nverify the CCX transfer using the Conceal Transaction Viewer (https://explorer.conceal.network/txviewer).\nBecause Conceal is a privacy coin, block explorers cannot verify transfers.\n\nIf you cannot provide the required data to the arbitrator, you will lose the dispute case.\nIf you do not save the transaction secret key immediately after transferring CCX, it cannot be recovered later.\nIf you do not understand these requirements, seek help at the Conceal discord (http://discord.conceal.network). -account.altcoin.popup.drgl.msg=Trading Dragonglass on Bisq requires that you understand and fulfill the following requirements:\n\nBecause of the privacy Dragonglass provides a transaction is not verifyable on the public blockchain. If required you can prove your payment thru use of your TXN-Private-Key.\nThe TXN-Private Key is a one-time key automatically generated for every transaction that can only be accessed from within your DRGL wallet.\nEither by DRGL-wallet GUI (inside transaction details dialog) or by the Dragonglass CLI simplewallet (using command "get_tx_key").\n\nDRGL version 'Oathkeeper' and higher are REQUIRED for both.\n\nIn case of a dispute, you must provide the arbitrator the following data:\n- The TXN-Private key\n- The transaction hash\n- The recipient's public address\n\nVerification of payment can be made using the above data as inputs at \ (http://drgl.info/#check_txn).\n\nIf you cannot provide the above data or if you used an incompatible wallet it would result in losing the dispute case. The Dragonglass sender is responsible to be able to verify the DRGL transfer to the arbitrator in case of a dispute. Use of PaymentID is not required.\n\nIf you are unsure about any part of this process, visit Dragonglass on Discord (http://discord.drgl.info) for help. +account.altcoin.popup.xmr.msg=Trading XMR on Bisq requires that you understand and fulfill the following requirements:\n\nFor sending XMR, you need to use either the official Monero GUI wallet or Monero CLI wallet with the store-tx-info flag enabled (default in new versions). Please be sure you can access the tx key as that would be required in case of a dispute.\nmonero-wallet-cli (use the command get_tx_key)\nmonero-wallet-gui (go to history tab and click on the (P) button for payment proof)\n\nIn addition to XMR checktx tool (https://xmr.llcoins.net/checktx.html) verification can also be accomplished in-wallet.\nmonero-wallet-cli : using command (check_tx_key).\nmonero-wallet-gui : on the Advanced > Prove/Check page.\nAt normal block explorers the transfer is not verifiable.\n\nYou need to provide the arbitrator the following data in case of a dispute:\n- The tx private key\n- The transaction hash\n- The recipient's public address\n\nFailure to provide the above data, or if you used an incompatible wallet, will result in losing the dispute case. The XMR sender is responsible for providing verification of the XMR transfer to the arbitrator in case of a dispute.\n\nThere is no payment ID required, just the normal public address.\nIf you are not sure about that process visit (https://www.getmonero.org/resources/user-guides/prove-payment.html) or the Monero forum (https://forum.getmonero.org) to find more information. +account.altcoin.popup.blur.msg=Trading BLUR on Bisq requires that you understand and fulfill the following requirements:\n\nTo send BLUR you must use the Blur Network CLI or GUI Wallet. \n\nIf you are using the CLI wallet, a transaction hash (tx ID) will be displayed after a transfer is sent. You must save this information. Immediately after sending the transfer, you must use the command 'get_tx_key' to retrieve the transaction private key. If you fail to perform this step, you may not be able to retrieve the key later. \n\nIf you are using the Blur Network GUI Wallet, the transaction private key and transaction ID can be found conveniently in the "History" tab. Immediately after sending, locate the transaction of interest. Click the "?" symbol in the lower-right corner of the box containing the transaction. You must save this information. \n\nIn the event that arbitration is necessary, you must present the following to an arbitrator: 1.) the transaction ID, 2.) the transaction private key, and 3.) the recipient's address. The arbitrator will then verify the BLUR transfer using the Blur Transaction Viewer (https://blur.cash/#tx-viewer).\n\nFailure to provide the required information to the arbitrator will result in losing the dispute case. In all cases of dispute, the BLUR sender bears 100% of the burden of responsibility in verifying transactions to an arbitrator. \n\nIf you do not understand these requirements, do not trade on Bisq. First, seek help at the Blur Network Discord (https://discord.gg/dMWaqVW). +account.altcoin.popup.ccx.msg=Trading CCX on Bisq requires that you understand the following requirements:\n\nTo send CCX you must use an official Conceal wallet, either CLI or GUI. After sending a transfer payment, the wallets\ndisplay the transaction secret key. You must save it along with the transaction hash (ID) and the recipient's public\naddress in case arbitration is necessary. In such a case, you must give all three to the arbitrator, who will then\nverify the CCX transfer using the Conceal Transaction Viewer (https://explorer.conceal.network/txviewer).\nBecause Conceal is a privacy coin, block explorers cannot verify transfers.\n\nFailure to provide the required data to the arbitrator will result in losing the dispute case.\nIf you do not save the transaction secret key immediately after transferring CCX, it cannot be recovered later.\nIf you do not understand these requirements, seek help at the Conceal discord (http://discord.conceal.network). +account.altcoin.popup.drgl.msg=Trading Dragonglass on Bisq requires that you understand and fulfill the following requirements:\n\nBecause of the privacy Dragonglass provides, a transaction is not verifiable on the public blockchain. If required, you can prove your payment through the use of your TXN-Private-Key.\nThe TXN-Private Key is a one-time key automatically generated for every transaction that can only be accessed from within your DRGL wallet.\nEither by DRGL-wallet GUI (inside transaction details dialog) or by the Dragonglass CLI simplewallet (using command "get_tx_key").\n\nDRGL version 'Oathkeeper' and higher are REQUIRED for both.\n\nIn case of a dispute, you must provide the arbitrator the following data:\n- The TXN-Private key\n- The transaction hash\n- The recipient's public address\n\nVerification of payment can be made using the above data as inputs at (http://drgl.info/#check_txn).\n\nFailure to provide the above data, or if you used an incompatible wallet, will result in losing the dispute case. The Dragonglass sender is responsible for providing verification of the DRGL transfer to the arbitrator in case of a dispute. Use of PaymentID is not required.\n\nIf you are unsure about any part of this process, visit Dragonglass on Discord (http://discord.drgl.info) for help. account.altcoin.popup.ZEC.msg=When using {0} you can only use the transparent addresses (starting with t) not the z-addresses (private), because the arbitrator would not be able to verify the transaction with z-addresses. account.altcoin.popup.XZC.msg=When using {0} you can only use the transparent (traceable) addresses not the untraceable addresses, because the arbitrator would not be able to verify the transaction with untraceable addresses at a block explorer. account.altcoin.popup.bch=Bitcoin Cash and Bitcoin Clashic suffer from replay protection. If you use those coins be sure you take sufficient precautions and understand all implications.You can suffer losses by sending one coin and unintentionally send the same coins on the other block chain.Because those "airdrop coins" share the same history with the Bitcoin blockchain there are also security risks and a considerable risk for losing privacy.\n\nPlease read at the Bisq Forum more about that topic: https://forum.bisq.io/t/airdrop-coins-information-thread-bch-btg-bchc @@ -1079,7 +1081,7 @@ dao.results.proposals.table.header.result=Vote result dao.results.proposals.voting.detail.header=Vote results for selected proposal # suppress inspection "UnusedProperty" -dao.param.UNDEFINED=Undefined +dao.param.UNDEFINED=Indéfini # suppress inspection "UnusedProperty" dao.param.DEFAULT_MAKER_FEE_BSQ=BSQ maker fee @@ -1165,7 +1167,7 @@ dao.results.cycle.value.postFix.isDefaultValue=(default value) dao.results.cycle.value.postFix.hasChanged=(has been changed in voting) # suppress inspection "UnusedProperty" -dao.phase.PHASE_UNDEFINED=Undefined +dao.phase.PHASE_UNDEFINED=Indéfini # suppress inspection "UnusedProperty" dao.phase.PHASE_PROPOSAL=Proposal phase # suppress inspection "UnusedProperty" @@ -1306,10 +1308,10 @@ dao.burnBsq.assets.lookBackPeriod=Verification period dao.burnBsq.assets.trialFee=Fee for trial period dao.burnBsq.assets.totalFee=Total fees paid dao.burnBsq.assets.days={0} days -dao.burnBsq.assets.toFewDays=The asset fee is too low. The min. amount of days for the trial perios is {0}. +dao.burnBsq.assets.toFewDays=The asset fee is too low. The min. amount of days for the trial period is {0}. # suppress inspection "UnusedProperty" -dao.assetState.UNDEFINED=Undefined +dao.assetState.UNDEFINED=Indéfini # suppress inspection "UnusedProperty" dao.assetState.IN_TRIAL_PERIOD=In trial period # suppress inspection "UnusedProperty" @@ -1341,7 +1343,7 @@ dao.proofOfBurn.verificationResult.ok=Verification succeeded dao.proofOfBurn.verificationResult.failed=Verification failed # suppress inspection "UnusedProperty" -dao.phase.UNDEFINED=Undefined +dao.phase.UNDEFINED=Indéfini # suppress inspection "UnusedProperty" dao.phase.PROPOSAL=Proposal phase # suppress inspection "UnusedProperty" @@ -1369,7 +1371,7 @@ dao.phase.separatedPhaseBar.RESULT=Vote result # suppress inspection "UnusedProperty" dao.proposal.type.COMPENSATION_REQUEST=Requête de compensation # suppress inspection "UnusedProperty" -dao.proposal.type.REIMBURSEMENT_REQUEST=Reimbursement request +dao.proposal.type.REIMBURSEMENT_REQUEST=Demande de remboursement # suppress inspection "UnusedProperty" dao.proposal.type.BONDED_ROLE=Proposal for a bonded role # suppress inspection "UnusedProperty" @@ -1384,7 +1386,7 @@ dao.proposal.type.CONFISCATE_BOND=Proposal for confiscating a bond # suppress inspection "UnusedProperty" dao.proposal.type.short.COMPENSATION_REQUEST=Requête de compensation # suppress inspection "UnusedProperty" -dao.proposal.type.short.REIMBURSEMENT_REQUEST=Reimbursement request +dao.proposal.type.short.REIMBURSEMENT_REQUEST=Demande de remboursement # suppress inspection "UnusedProperty" dao.proposal.type.short.BONDED_ROLE=Bonded role # suppress inspection "UnusedProperty" @@ -1584,7 +1586,7 @@ displayUpdateDownloadWindow.verify.failed=Verification failed.\nPlease download displayUpdateDownloadWindow.success=The new version has been successfully downloaded and the signature verified.\n\nPlease open the download directory, shut down the application and install the new version. displayUpdateDownloadWindow.download.openDir=Open download directory -disputeRésuméWindow.title=Résumé +disputeSummaryWindow.title=Résumé disputeSummaryWindow.openDate=Ticket opening date disputeSummaryWindow.role=Trader's role disputeSummaryWindow.evidence=Evidence @@ -1746,7 +1748,7 @@ popup.headline.error=Erreur popup.doNotShowAgain=Ne plus me montrer popup.reportError.log=Open log file popup.reportError.gitHub=Report to GitHub issue tracker -popup.reportError={0}\n\nTo help us to improve the software please report the bug on our issue tracker on GitHub (https://github.com/bisq-network/bisq-desktop/issues).\nThe error message will be copied to the clipboard when you click a button below.\nIt will make debugging easier if you can attach the bisq.log file as well. +popup.reportError={0}\n\nTo help us to improve the software please report this bug by opening a new issue at https://github.com/bisq-network/bisq/issues.\nThe above error message will be copied to the clipboard when you click either of the buttons below.\nIt will make debugging easier if you include the bisq.log file by pressing "Open log file", saving a copy, and attaching it to your bug report. popup.error.tryRestart=Please try to restart your application and check your network connection to see if you can resolve the issue. popup.error.takeOfferRequestFailed=An error occurred when someone tried to take one of your offers:\n{0} @@ -1805,6 +1807,9 @@ popup.attention.forTradeWithId=Veuillez consulter votre échange ID {0} popup.roundedFiatValues.headline=New privacy feature: Rounded fiat values popup.roundedFiatValues.msg=To increase privacy of your trade the {0} amount was rounded.\n\nDepending on the client version you''ll pay or receive either values with decimals or rounded ones.\n\nBoth values do comply from now on with the trade protocol.\n\nAlso be aware that BTC values are changed automatically to match the rounded fiat amount as close as possible. +popup.info.multiplePaymentAccounts.headline=Multiple payment accounts available +popup.info.multiplePaymentAccounts.msg=You have multiple payment accounts available for this offer. Please make sure you've picked the right one. + #################################################################### # Notifications @@ -2085,7 +2090,7 @@ payment.clearXchange.info=Please be sure that you fulfill the requirements for t payment.moneyGram.info=When using MoneyGram the BTC buyer has to send the Authorisation number and a photo of the receipt by email to the BTC seller. The receipt must clearly show the seller's full name, country, state and the amount. The buyer will get displayed the seller's email in the trade process. payment.westernUnion.info=When using Western Union the BTC buyer has to send the MTCN (tracking number) and a photo of the receipt by email to the BTC seller. The receipt must clearly show the seller's full name, city, country and the amount. The buyer will get displayed the seller's email in the trade process. -payment.halCash.info=When using HalCash the BTC buyer need to send the BTC seller the HalCash code via a text message from the mobile phone.\n\nPlease make sure to not exceed the maximum amount your bank allows you to send with HalCash. The min. amount per withdrawal is 10 EUR and the max. amount is 600 EUR. For repeated withdrawals it is 3000 EUR per receiver per day and 6000 EUR per receiver per month. Please cross check those limits with your bank to be sure they use the same limits as stated here.\n\nThe withdrawal amount must be a multiple of 10 EUR as you cannot withdraw other amounts from an ATM. The UI in the create-offer and take-offer screen will adjust the BTC amount so that the EUR amount is correct. You cannot use market based price as the EUR amount would be changing with changing prices.\n\nIn case of a dispute the BTC buyer need to provide the proof that he sent the EUR. +payment.halCash.info=When using HalCash the BTC buyer needs to send the BTC seller the HalCash code via a text message from their mobile phone.\n\nPlease make sure to not exceed the maximum amount your bank allows you to send with HalCash. The min. amount per withdrawal is 10 EUR and the max. amount is 600 EUR. For repeated withdrawals it is 3000 EUR per receiver per day and 6000 EUR per receiver per month. Please cross check those limits with your bank to be sure they use the same limits as stated here.\n\nThe withdrawal amount must be a multiple of 10 EUR as you cannot withdraw other amounts from an ATM. The UI in the create-offer and take-offer screen will adjust the BTC amount so that the EUR amount is correct. You cannot use market based price as the EUR amount would be changing with changing prices.\n\nIn case of a dispute the BTC buyer needs to provide the proof that they sent the EUR. payment.limits.info=Please be aware that all bank transfers carry a certain amount of chargeback risk.\n\nTo mitigate this risk, Bisq sets per-trade limits based on two factors:\n\n1. The estimated level of chargeback risk for the payment method used\n2. The age of your account for that payment method\n\nThe account you are creating now is new and its age is zero. As your account grows in age over a two-month period, your per-trade limits will grow along with it:\n\n● During the 1st month, your per-trade limit will be {0}\n● During the 2nd month, your per-trade limit will be {1}\n● After the 2nd month, your per-trade limit will be {2}\n\nPlease note that there are no limits on the total number of times you can trade. payment.cashDeposit.info=Please confirm your bank allows you to send cash deposits into other peoples' accounts. For example, Bank of America and Wells Fargo no longer allow such deposits. @@ -2098,7 +2103,7 @@ payment.f2f.optionalExtra=Optional additional information payment.f2f.extra=Additional information payment.f2f.extra.prompt=The maker can define 'terms and conditions' or add a public contact information. It will be displayed with the offer. -payment.f2f.info='Face to Face' trades have different rules and come with different risks than online transactions.\n\nThe main differences are:\n● The trading peers need to exchange information about the meeting location and time by using their provided contact details.\n● The trading peers need to bring their laptops and do the confirmation of 'payment sent' and 'payment received' at the meeting place.\n● If a maker has special 'terms and conditions' he needs to state those in the 'Addition information' text field in the account.\n● By taking an offer the taker agrees to the maker's stated 'terms and conditions'.\n● In case of a dispute the arbitrator cannot help much as it is usually hard to get tamper proof evidence of what happened at the meeting. In such cases the BTC funds might get locked indefinitely or until the trading peers come to an agreement.\n\nTo be sure you fully understand the differences with 'Face to Face' trades please read the instructions and recommendations at: 'https://docs.bisq.network/trading-rules.html#f2f-trading' +payment.f2f.info='Face to Face' trades have different rules and come with different risks than online transactions.\n\nThe main differences are:\n● The trading peers need to exchange information about the meeting location and time by using their provided contact details.\n● The trading peers need to bring their laptops and do the confirmation of 'payment sent' and 'payment received' at the meeting place.\n● If a maker has special 'terms and conditions' they must state those in the 'Additional information' text field in the account.\n● By taking an offer the taker agrees to the maker's stated 'terms and conditions'.\n● In case of a dispute the arbitrator cannot help much as it is usually hard to get tamper proof evidence of what happened at the meeting. In such cases the BTC funds might get locked indefinitely or until the trading peers come to an agreement.\n\nTo be sure you fully understand the differences with 'Face to Face' trades please read the instructions and recommendations at: 'https://docs.bisq.network/trading-rules.html#f2f-trading' payment.f2f.info.openURL=Open web page payment.f2f.offerbook.tooltip.countryAndCity=County and city: {0} / {1} payment.f2f.offerbook.tooltip.extra=Additional information: {0} diff --git a/core/src/main/resources/i18n/displayStrings_hu.properties b/core/src/main/resources/i18n/displayStrings_hu.properties index 758d9ff075..3b232ffb5a 100644 --- a/core/src/main/resources/i18n/displayStrings_hu.properties +++ b/core/src/main/resources/i18n/displayStrings_hu.properties @@ -299,6 +299,8 @@ market.trades.tooltip.candle.date=Dátum: offerbook.createOffer=Ajánlat létrehozása offerbook.takeOffer=Ajánlatot elfogadása +offerbook.takeOfferToBuy=Take offer to buy {0} +offerbook.takeOfferToSell=Take offer to sell {0} offerbook.trader=Kereskedő offerbook.offerersBankId=Ajánló bankazonosítója: {0} offerbook.offerersBankName=Ajánló bank neve: {0} @@ -560,12 +562,12 @@ portfolio.pending.step3_buyer.warn.part1b=a fizetési szolgáltatódnál (péld portfolio.pending.step3_buyer.warn.part2=A BTC eladó még mindig nem konfirmálta kifizetését!\nKérjük ellenőrizze ha a {0} átutálása sikeres volt.\nHa a BTC eladó nem igazolja a kifizetés beérkezését {1}-ig, a tranzakció a bíróhoz kerül vizsgálatra. portfolio.pending.step3_buyer.openForDispute=A BTC vevő még nem konfirmálta fizetését!\nA tranzakció maximális megengedett időtartama lejárt.\nVárakozhat hosszabb ideig, ezennel több időt adhatna váltótársának vagy kapcsolatba léphet a bíróval egy vita megnyitásához. # suppress inspection "TrailingSpacesInProperty" -portfolio.pending.step3_seller.part=Váltótársa visszaigazolta, hogy kezdeményezte a {0} kifizetést.\n\n +portfolio.pending.step3_seller.part=Your trading partner has confirmed that they have initiated the {0} payment.\n\n portfolio.pending.step3_seller.altcoin.explorer=on your favorite {0} blockchain explorer portfolio.pending.step3_seller.altcoin.wallet=at your {0} wallet portfolio.pending.step3_seller.altcoin={0}Please check {1} if the transaction to your receiving address\n{2}\nhas already sufficient blockchain confirmations.\nThe payment amount has to be {3}\n\nYou can copy & paste your {4} address from the main screen after closing that popup. portfolio.pending.step3_seller.postal={0}Kérjük ellenőrizze, hogy megkapta-e a {1} \"US Posta Pénz Rendeléssen\" keresztül a BTC vevőjétől.\n\nA tranzakció azonosítója (\"fizetés indoka\" szövege): \"{2}\" -portfolio.pending.step3_seller.bank=Your trading partner has confirmed that he initiated the {0} payment.\n\nPlease go to your online banking web page and check if you have received {1} from the BTC buyer.\n\nThe trade ID (\"reason for payment\" text) of the transaction is: \"{2}\"\n\n +portfolio.pending.step3_seller.bank=Your trading partner has confirmed that they have initiated the {0} payment.\n\nPlease go to your online banking web page and check if you have received {1} from the BTC buyer.\n\nThe trade ID (\"reason for payment\" text) of the transaction is: \"{2}\"\n\n portfolio.pending.step3_seller.cash=Because the payment is done via Cash Deposit the BTC buyer has to write \"NO REFUND\" on the paper receipt, tear it in 2 parts and send you a photo by email.\n\nTo avoid chargeback risk, only confirm if you received the email and if you are sure the paper receipt is valid.\nIf you are not sure, {0} portfolio.pending.step3_seller.moneyGram=The buyer has to send you the Authorisation number and a photo of the receipt by email.\nThe receipt must clearly show your full name, country, state and the amount. Please check your email if you received the Authorisation number.\n\nAfter closing that popup you will see the BTC buyer's name and address for picking up the money from MoneyGram.\n\nOnly confirm receipt after you have successfully picked up the money! portfolio.pending.step3_seller.westernUnion=A vevőnek el kell küldenie az MTCN-t (nyomon követési számot) és egy átvételről készült fényképet e-mailen keresztül.\nAz átvételi elismervényen egyértelműen meg kell jelennie a teljes neve, városa, országa illetve az összeg. Kérjük ellenőrizze e-mailjét, hogy megkapta-e az MTCN-t.\n\nMiután lezárta a felugró ablakot, látni fogja a BTC vásárló nevét és címét, hogy felemelhesse Western Uniótól a pénzt.\n\nCsak azután fogadja el a kézhezvételt, miután sikeresen felemelte a pénzt! @@ -926,10 +928,10 @@ account.arbitratorSelection.minOne=Legalább egy bírót kell választania. account.altcoin.yourAltcoinAccounts=Your altcoin accounts account.altcoin.popup.wallet.msg=Please be sure that you follow the requirements for the usage of {0} wallets as described on the {1} web page.\nUsing wallets from centralized exchanges where (a) you don''t control your keys or (b) which don''t use compatible wallet software is risky: it can lead to loss of the traded funds!\nThe arbitrator is not a {2} specialist and cannot help in such cases. account.altcoin.popup.wallet.confirm=Megértem és alátámasztom, hogy tudom, melyik pénztárcát kell használnom. -account.altcoin.popup.xmr.msg=If you want to trade XMR on Bisq please be sure you understand and fulfill the following requirements:\n\nFor sending XMR you need to use either the official Monero GUI wallet or Monero CLI wallet with the store-tx-info flag enabled (default in new versions). Please be sure you can access the tx key as that would be required in case of a dispute.\nmonero-wallet-cli (use the command get_tx_key)\nmonero-wallet-gui (go to history tab and click on the (P) button for payment proof)\n\nIn addition to XMR checktx tool (https://xmr.llcoins.net/checktx.html) verification can also be accomplished in-wallet.\nmonero-wallet-cli : using command (check_tx_key).\nmonero-wallet-gui : on the Advanced > Prove/Check page.\nAt normal block explorers the transfer is not verifiable.\n\nYou need to provide the arbitrator the following data in case of a dispute:\n- The tx private key\n- The transaction hash\n- The recipient's public address\n\nIf you cannot provide the above data or if you used an incompatible wallet it would result in losing the dispute case. The XMR sender is responsible to be able to verify the XMR transfer to the arbitrator in case of a dispute.\n\nThere is no payment ID required, just the normal public address.\nIf you are not sure about that process visit (https://www.getmonero.org/resources/user-guides/prove-payment.html) or the Monero forum (https://forum.getmonero.org) to find more information. -account.altcoin.popup.blur.msg=If you want to trade BLUR on Bisq please be sure you understand and fulfill the following requirements:\n\nTo send BLUR you must use the Blur Network CLI or GUI Wallet. \n\nIf you are using the CLI wallet, a transaction hash (tx ID) will be displayed after a transfer is sent. You must save this information. Immediately after sending the transfer, you must use the command 'get_tx_key' to retrieve the transaction private key. If you fail to perform this step, you may not be able to retrieve the key later. \n\nIf you are using the Blur Network GUI Wallet, the transaction private key and transaction ID can be found conveniently in the "History" tab. Immediately after sending, locate the transaction of interest. Click the "?" symbol in the lower-right corner of the box containing the transaction. You must save this information. \n\nIn the event that arbitration is necessary, you must present the following to an arbitrator: 1.) the transaction ID, 2.) the transaction private key, and 3.) the recipient's address. The arbitrator will then verify the BLUR transfer using the Blur Transaction Viewer (https://blur.cash/#tx-viewer).\n\nIf you cannot provide the required information to the arbitrator, you will lose the dispute. In all cases of dispute, the BLUR sender bears 100% of the burden of responsiblity in verifying transactions to an arbitrator. \n\nIf you do not understand these requirements, do not trade on Bisq. First, seek help at the Blur Network Discord (https://discord.gg/dMWaqVW). -account.altcoin.popup.ccx.msg=If you want to trade CCX on Bisq please be sure you understand the following requirements:\n\nTo send CCX you must use an official Conceal wallet, either CLI or GUI. After sending a transfer payment, the wallets\ndisplay the transaction secret key. You must save it along with the transaction hash (ID) and the recipient's public\naddress in case arbitration is necessary. In such a case, you must give all three to the arbitrator, who will then\nverify the CCX transfer using the Conceal Transaction Viewer (https://explorer.conceal.network/txviewer).\nBecause Conceal is a privacy coin, block explorers cannot verify transfers.\n\nIf you cannot provide the required data to the arbitrator, you will lose the dispute case.\nIf you do not save the transaction secret key immediately after transferring CCX, it cannot be recovered later.\nIf you do not understand these requirements, seek help at the Conceal discord (http://discord.conceal.network). -account.altcoin.popup.drgl.msg=Trading Dragonglass on Bisq requires that you understand and fulfill the following requirements:\n\nBecause of the privacy Dragonglass provides a transaction is not verifyable on the public blockchain. If required you can prove your payment thru use of your TXN-Private-Key.\nThe TXN-Private Key is a one-time key automatically generated for every transaction that can only be accessed from within your DRGL wallet.\nEither by DRGL-wallet GUI (inside transaction details dialog) or by the Dragonglass CLI simplewallet (using command "get_tx_key").\n\nDRGL version 'Oathkeeper' and higher are REQUIRED for both.\n\nIn case of a dispute, you must provide the arbitrator the following data:\n- The TXN-Private key\n- The transaction hash\n- The recipient's public address\n\nVerification of payment can be made using the above data as inputs at \ (http://drgl.info/#check_txn).\n\nIf you cannot provide the above data or if you used an incompatible wallet it would result in losing the dispute case. The Dragonglass sender is responsible to be able to verify the DRGL transfer to the arbitrator in case of a dispute. Use of PaymentID is not required.\n\nIf you are unsure about any part of this process, visit Dragonglass on Discord (http://discord.drgl.info) for help. +account.altcoin.popup.xmr.msg=Trading XMR on Bisq requires that you understand and fulfill the following requirements:\n\nFor sending XMR, you need to use either the official Monero GUI wallet or Monero CLI wallet with the store-tx-info flag enabled (default in new versions). Please be sure you can access the tx key as that would be required in case of a dispute.\nmonero-wallet-cli (use the command get_tx_key)\nmonero-wallet-gui (go to history tab and click on the (P) button for payment proof)\n\nIn addition to XMR checktx tool (https://xmr.llcoins.net/checktx.html) verification can also be accomplished in-wallet.\nmonero-wallet-cli : using command (check_tx_key).\nmonero-wallet-gui : on the Advanced > Prove/Check page.\nAt normal block explorers the transfer is not verifiable.\n\nYou need to provide the arbitrator the following data in case of a dispute:\n- The tx private key\n- The transaction hash\n- The recipient's public address\n\nFailure to provide the above data, or if you used an incompatible wallet, will result in losing the dispute case. The XMR sender is responsible for providing verification of the XMR transfer to the arbitrator in case of a dispute.\n\nThere is no payment ID required, just the normal public address.\nIf you are not sure about that process visit (https://www.getmonero.org/resources/user-guides/prove-payment.html) or the Monero forum (https://forum.getmonero.org) to find more information. +account.altcoin.popup.blur.msg=Trading BLUR on Bisq requires that you understand and fulfill the following requirements:\n\nTo send BLUR you must use the Blur Network CLI or GUI Wallet. \n\nIf you are using the CLI wallet, a transaction hash (tx ID) will be displayed after a transfer is sent. You must save this information. Immediately after sending the transfer, you must use the command 'get_tx_key' to retrieve the transaction private key. If you fail to perform this step, you may not be able to retrieve the key later. \n\nIf you are using the Blur Network GUI Wallet, the transaction private key and transaction ID can be found conveniently in the "History" tab. Immediately after sending, locate the transaction of interest. Click the "?" symbol in the lower-right corner of the box containing the transaction. You must save this information. \n\nIn the event that arbitration is necessary, you must present the following to an arbitrator: 1.) the transaction ID, 2.) the transaction private key, and 3.) the recipient's address. The arbitrator will then verify the BLUR transfer using the Blur Transaction Viewer (https://blur.cash/#tx-viewer).\n\nFailure to provide the required information to the arbitrator will result in losing the dispute case. In all cases of dispute, the BLUR sender bears 100% of the burden of responsibility in verifying transactions to an arbitrator. \n\nIf you do not understand these requirements, do not trade on Bisq. First, seek help at the Blur Network Discord (https://discord.gg/dMWaqVW). +account.altcoin.popup.ccx.msg=Trading CCX on Bisq requires that you understand the following requirements:\n\nTo send CCX you must use an official Conceal wallet, either CLI or GUI. After sending a transfer payment, the wallets\ndisplay the transaction secret key. You must save it along with the transaction hash (ID) and the recipient's public\naddress in case arbitration is necessary. In such a case, you must give all three to the arbitrator, who will then\nverify the CCX transfer using the Conceal Transaction Viewer (https://explorer.conceal.network/txviewer).\nBecause Conceal is a privacy coin, block explorers cannot verify transfers.\n\nFailure to provide the required data to the arbitrator will result in losing the dispute case.\nIf you do not save the transaction secret key immediately after transferring CCX, it cannot be recovered later.\nIf you do not understand these requirements, seek help at the Conceal discord (http://discord.conceal.network). +account.altcoin.popup.drgl.msg=Trading Dragonglass on Bisq requires that you understand and fulfill the following requirements:\n\nBecause of the privacy Dragonglass provides, a transaction is not verifiable on the public blockchain. If required, you can prove your payment through the use of your TXN-Private-Key.\nThe TXN-Private Key is a one-time key automatically generated for every transaction that can only be accessed from within your DRGL wallet.\nEither by DRGL-wallet GUI (inside transaction details dialog) or by the Dragonglass CLI simplewallet (using command "get_tx_key").\n\nDRGL version 'Oathkeeper' and higher are REQUIRED for both.\n\nIn case of a dispute, you must provide the arbitrator the following data:\n- The TXN-Private key\n- The transaction hash\n- The recipient's public address\n\nVerification of payment can be made using the above data as inputs at (http://drgl.info/#check_txn).\n\nFailure to provide the above data, or if you used an incompatible wallet, will result in losing the dispute case. The Dragonglass sender is responsible for providing verification of the DRGL transfer to the arbitrator in case of a dispute. Use of PaymentID is not required.\n\nIf you are unsure about any part of this process, visit Dragonglass on Discord (http://discord.drgl.info) for help. account.altcoin.popup.ZEC.msg=A {0} használatakor csak átlátható címeket használhat (t-vel kezdődve) nem pedig a z-címeket (privát), mivel hogy a bíró nem tudja ellenőrizni a z-címekkel kezdődő tranzakciókat. account.altcoin.popup.XZC.msg=A {0} használatakor csak átlátható (nyomon követhető) címeket használhat, nem pedig lenyomozhatatlan címeket, mivel hogy a bíró nem tudja ellenőrizni a tranzakciót lenyomozhatatlan címmel a blokkböngészőben. account.altcoin.popup.bch=Bitcoin Cash és Bitcoin Clashic ismételt védelemben részesül. Ha ezeket az érméket használja, győződjön meg róla, hogy elegendő óvintézkedést és minden következtetést megért. Veszteségeket szenvedhet úgy, hogy egy érmét küld és szándék nélkül ugyanazokat az érméket küldi a másik blokkláncon. Mivel ezek a "légpénzes érmék" ugyanazt a történelmet osztják a Bitcoin blokkhálózattal, szintén vannak biztonsági kockázatok és jelentős rizikót jelent a magánélet elvesztését illetően.\n\nKérjük olvasson többet erről a témáról a Bisq fórumon: https://forum.bisq.io/t/airdrop-coins-information-thread-bch-btg-bchc @@ -1306,7 +1308,7 @@ dao.burnBsq.assets.lookBackPeriod=Verification period dao.burnBsq.assets.trialFee=Fee for trial period dao.burnBsq.assets.totalFee=Total fees paid dao.burnBsq.assets.days={0} days -dao.burnBsq.assets.toFewDays=The asset fee is too low. The min. amount of days for the trial perios is {0}. +dao.burnBsq.assets.toFewDays=The asset fee is too low. The min. amount of days for the trial period is {0}. # suppress inspection "UnusedProperty" dao.assetState.UNDEFINED=Határozatlan @@ -1584,7 +1586,7 @@ displayUpdateDownloadWindow.verify.failed=Sikertelen ellenőrzés.\nKérjük tö displayUpdateDownloadWindow.success=Az új verziót sikeresen letöltötték és az aláírást ellenőrizték.\n\nKérjük nyissa meg a letöltési könyvtárat, állítsa le az alkalmazást és telepítse az új verziót. displayUpdateDownloadWindow.download.openDir=Letöltési könyvtár megnyitása -disputeÖsszefoglóWindow.title=Összefogló +disputeSummaryWindow.title=Összefogló disputeSummaryWindow.openDate=Ticket opening date disputeSummaryWindow.role=Trader's role disputeSummaryWindow.evidence=Evidence @@ -1746,7 +1748,7 @@ popup.headline.error=Hiba popup.doNotShowAgain=Ne mutasd ezt újra popup.reportError.log=Naplófájl nyitása popup.reportError.gitHub=Jelentés a Github kibocsátás-követőhöz -popup.reportError={0}\n\nTo help us to improve the software please report the bug on our issue tracker on GitHub (https://github.com/bisq-network/bisq-desktop/issues).\nThe error message will be copied to the clipboard when you click a button below.\nIt will make debugging easier if you can attach the bisq.log file as well. +popup.reportError={0}\n\nTo help us to improve the software please report this bug by opening a new issue at https://github.com/bisq-network/bisq/issues.\nThe above error message will be copied to the clipboard when you click either of the buttons below.\nIt will make debugging easier if you include the bisq.log file by pressing "Open log file", saving a copy, and attaching it to your bug report. popup.error.tryRestart=Próbálja meg újraindítani az alkalmazást, és ellenőrizze a hálózati kapcsolatot, hogy meg tudja-e oldani a problémát. popup.error.takeOfferRequestFailed=Hiba történt amikor valaki megpróbálta felvenni ajánlatát:\n{0} @@ -1805,6 +1807,9 @@ popup.attention.forTradeWithId=Figyelem szükséges a {0} azonosítóval rendelk popup.roundedFiatValues.headline=New privacy feature: Rounded fiat values popup.roundedFiatValues.msg=To increase privacy of your trade the {0} amount was rounded.\n\nDepending on the client version you''ll pay or receive either values with decimals or rounded ones.\n\nBoth values do comply from now on with the trade protocol.\n\nAlso be aware that BTC values are changed automatically to match the rounded fiat amount as close as possible. +popup.info.multiplePaymentAccounts.headline=Multiple payment accounts available +popup.info.multiplePaymentAccounts.msg=You have multiple payment accounts available for this offer. Please make sure you've picked the right one. + #################################################################### # Notifications @@ -1875,7 +1880,7 @@ table.placeholder.noData=Jelenleg nincs adat peerInfoIcon.tooltip.tradePeer=Váltótársak peerInfoIcon.tooltip.maker=Ajánló peerInfoIcon.tooltip.trade.traded={0} Onion cím: {1}\nMár {2} alkalommal üzletelt ezzel a felhasználóval\n{3} -peerInfoIcon.tooltip.trade.notTraded={0} Onion cím: {1}\nMég nem üzletelt eddig ezzel a felhasználóval.\n{3} +peerInfoIcon.tooltip.trade.notTraded={0} Onion cím: {1}\nMég nem üzletelt eddig ezzel a felhasználóval.\n{2} peerInfoIcon.tooltip.age=Fizetési fiók létrehozva {0} ezelőtt. peerInfoIcon.tooltip.unknownAge=Fizetési számla kora nem ismert. @@ -2085,7 +2090,7 @@ payment.clearXchange.info=Please be sure that you fulfill the requirements for t payment.moneyGram.info=When using MoneyGram the BTC buyer has to send the Authorisation number and a photo of the receipt by email to the BTC seller. The receipt must clearly show the seller's full name, country, state and the amount. The buyer will get displayed the seller's email in the trade process. payment.westernUnion.info=When using Western Union the BTC buyer has to send the MTCN (tracking number) and a photo of the receipt by email to the BTC seller. The receipt must clearly show the seller's full name, city, country and the amount. The buyer will get displayed the seller's email in the trade process. -payment.halCash.info=When using HalCash the BTC buyer need to send the BTC seller the HalCash code via a text message from the mobile phone.\n\nPlease make sure to not exceed the maximum amount your bank allows you to send with HalCash. The min. amount per withdrawal is 10 EUR and the max. amount is 600 EUR. For repeated withdrawals it is 3000 EUR per receiver per day and 6000 EUR per receiver per month. Please cross check those limits with your bank to be sure they use the same limits as stated here.\n\nThe withdrawal amount must be a multiple of 10 EUR as you cannot withdraw other amounts from an ATM. The UI in the create-offer and take-offer screen will adjust the BTC amount so that the EUR amount is correct. You cannot use market based price as the EUR amount would be changing with changing prices.\n\nIn case of a dispute the BTC buyer need to provide the proof that he sent the EUR. +payment.halCash.info=When using HalCash the BTC buyer needs to send the BTC seller the HalCash code via a text message from their mobile phone.\n\nPlease make sure to not exceed the maximum amount your bank allows you to send with HalCash. The min. amount per withdrawal is 10 EUR and the max. amount is 600 EUR. For repeated withdrawals it is 3000 EUR per receiver per day and 6000 EUR per receiver per month. Please cross check those limits with your bank to be sure they use the same limits as stated here.\n\nThe withdrawal amount must be a multiple of 10 EUR as you cannot withdraw other amounts from an ATM. The UI in the create-offer and take-offer screen will adjust the BTC amount so that the EUR amount is correct. You cannot use market based price as the EUR amount would be changing with changing prices.\n\nIn case of a dispute the BTC buyer needs to provide the proof that they sent the EUR. payment.limits.info=Kérjük vegye figyelembe, hogy minden banki átutalás bizonyos mértékű visszaterhelési kockázatot hordoz.\n\nE kockázat enyhítése érdekében Bisq két tényező alapján határozza meg a tranzakciók korlátozását:\n\n1. Az alkalmazott fizetési módra vonatkozó visszavásárlási kockázat becsült szintje\n2. Fiókja kora az adott fizetési mód esetében\n\nA most létrehozott fiókja új és kora nulla. Mivel fiókja egy két hónapos időszakon keresztül növekszik, a tranzakciós korlátaival együtt fog növekedni:\n\n● Az első hónap folyamán a tranzakció korláta {0}\n● A második hónapban folyamán a tranzakció korláta {1}\n● A második hónap elmúltja után a tranzakció korláta {2}\n\nKérjük vegye figyelembe, hogy nincs korlátozás az összes tranzakcióra vonatkozóan. payment.cashDeposit.info=Please confirm your bank allows you to send cash deposits into other peoples' accounts. For example, Bank of America and Wells Fargo no longer allow such deposits. @@ -2098,7 +2103,7 @@ payment.f2f.optionalExtra=Optional additional information payment.f2f.extra=Additional information payment.f2f.extra.prompt=The maker can define 'terms and conditions' or add a public contact information. It will be displayed with the offer. -payment.f2f.info='Face to Face' trades have different rules and come with different risks than online transactions.\n\nThe main differences are:\n● The trading peers need to exchange information about the meeting location and time by using their provided contact details.\n● The trading peers need to bring their laptops and do the confirmation of 'payment sent' and 'payment received' at the meeting place.\n● If a maker has special 'terms and conditions' he needs to state those in the 'Addition information' text field in the account.\n● By taking an offer the taker agrees to the maker's stated 'terms and conditions'.\n● In case of a dispute the arbitrator cannot help much as it is usually hard to get tamper proof evidence of what happened at the meeting. In such cases the BTC funds might get locked indefinitely or until the trading peers come to an agreement.\n\nTo be sure you fully understand the differences with 'Face to Face' trades please read the instructions and recommendations at: 'https://docs.bisq.network/trading-rules.html#f2f-trading' +payment.f2f.info='Face to Face' trades have different rules and come with different risks than online transactions.\n\nThe main differences are:\n● The trading peers need to exchange information about the meeting location and time by using their provided contact details.\n● The trading peers need to bring their laptops and do the confirmation of 'payment sent' and 'payment received' at the meeting place.\n● If a maker has special 'terms and conditions' they must state those in the 'Additional information' text field in the account.\n● By taking an offer the taker agrees to the maker's stated 'terms and conditions'.\n● In case of a dispute the arbitrator cannot help much as it is usually hard to get tamper proof evidence of what happened at the meeting. In such cases the BTC funds might get locked indefinitely or until the trading peers come to an agreement.\n\nTo be sure you fully understand the differences with 'Face to Face' trades please read the instructions and recommendations at: 'https://docs.bisq.network/trading-rules.html#f2f-trading' payment.f2f.info.openURL=Open web page payment.f2f.offerbook.tooltip.countryAndCity=County and city: {0} / {1} payment.f2f.offerbook.tooltip.extra=Additional information: {0} diff --git a/core/src/main/resources/i18n/displayStrings_pt.properties b/core/src/main/resources/i18n/displayStrings_pt.properties index 001ccd478b..63b928d4f8 100644 --- a/core/src/main/resources/i18n/displayStrings_pt.properties +++ b/core/src/main/resources/i18n/displayStrings_pt.properties @@ -299,6 +299,8 @@ market.trades.tooltip.candle.date=Data: offerbook.createOffer=Criar oferta offerbook.takeOffer=Aceitar +offerbook.takeOfferToBuy=Take offer to buy {0} +offerbook.takeOfferToSell=Take offer to sell {0} offerbook.trader=Trader offerbook.offerersBankId=ID do banco do ofertante (BIC/SWIFT): {0} offerbook.offerersBankName=Nome do banco do ofertante: {0} @@ -346,7 +348,7 @@ offerbook.info.sellAboveMarketPrice=Você irá receber {0} a mais do que o atual offerbook.info.buyBelowMarketPrice=Você irá pagar {0} a menos do que o atual preço de mercado (atualizado a cada minuto). offerbook.info.buyAtFixedPrice=Você irá comprar nesse preço fixo. offerbook.info.sellAtFixedPrice=Você irá vender neste preço fixo. -offerbook.info.noArbitrationInUserLanguage=O idioma do Bisq atualmente está definido para {1}. No entanto, em caso de disputa, a arbitragem para essa oferta será realizada em {0}. +offerbook.info.noArbitrationInUserLanguage=O idioma do Bisq atualmente está definido para {1}. No entanto, em caso de disputa, a arbitragem para essa oferta será realizada em {0}. offerbook.info.roundedFiatVolume=O montante foi arredondado para aumentar a privacidade do seu comércio. #################################################################### @@ -506,7 +508,7 @@ portfolio.pending.step2_buyer.cash.extra=REQUESITO IMPORTANTE:\nApós executar o portfolio.pending.step2_buyer.moneyGram=Por favor, pague {0} ao vendedor de BTC usando MoneyGram.\n\n portfolio.pending.step2_buyer.moneyGram.extra=IMPORTANTE:\nApós você ter feito o pagamento, envie o número de autorização e uma foto do recibo por e-mail para o vendedor de BTC.\nO recibo deve exibir claramente o nome completo, o país e o estado do vendedor, assim como a quantia. O e-mail do vendedor é: {0}. portfolio.pending.step2_buyer.westernUnion=Por favor, pague {0} ao vendedor de BTC através da Western Union.\n\n -portfolio.pending.step2_buyer.westernUnion.extra=IMPORTANT REQUIREMENT:\nAfter you have done the payment send the MTCN (tracking number) and a photo of the receipt by email to the BTC seller.\nThe receipt must clearly show the seller''s full name, city, country and the amount. The seller''s email is: {0}. +portfolio.pending.step2_buyer.westernUnion.extra=IMPORTANTE:\nApós você ter feito o pagamento, envie o número de rastreamento (MTCN) e uma foto do recibo por e-mail para o vendedor de BTC.\nO recibo deve exibir claramente o nome completo, o país e o estado do vendedor, assim como a quantia. O e-mail do vendedor é: {0}. # suppress inspection "TrailingSpacesInProperty" portfolio.pending.step2_buyer.postal=Envie {0} através de \"US Postal Money Order\" para o vendedor de BTC.\n\n @@ -560,12 +562,12 @@ portfolio.pending.step3_buyer.warn.part1b=com seu provedor de pagamentos (por ex portfolio.pending.step3_buyer.warn.part2=O vendedor de BTC ainda não confirmou o pagamento!\nPor favor, verifique em {0} se o pagamento foi enviado com sucesso.\nCaso o vendedor não confirme o recebimento do pagamento até {1}, a negociação será investigada pelo árbitro. portfolio.pending.step3_buyer.openForDispute=O vendedor de BTC não confirmou o seu pagamento!\nO período máximo para essa negociação expirou..\nVocê pode aguardar mais um pouco, dando mais tempo para o seu parceiro de negociação, ou você pode entrar em contato com um árbitro para abrir uma disputa. # suppress inspection "TrailingSpacesInProperty" -portfolio.pending.step3_seller.part=Seu parceiro de negociação confirmou que iniciou o pagamento de {0}.\n\n +portfolio.pending.step3_seller.part=Your trading partner has confirmed that they have initiated the {0} payment.\n\n portfolio.pending.step3_seller.altcoin.explorer=em seu explorador preferido da blockchain do {0} portfolio.pending.step3_seller.altcoin.wallet=em sua carteira {0} portfolio.pending.step3_seller.altcoin={0}Verifique em {1} se a transação para o seu endereço de recebimento\n{2}\njá tem confirmações suficientes na blockchain.\nA quantia do pagamento deve ser {3}\n\nVocê pode copiar e colar seu endereço {4} na janela principal, após fechar aquele popup. portfolio.pending.step3_seller.postal={0}Por gentileza verifique se recebeu {1} como \"US Postal Money Order\" do comprador de BTC.\n\nO ID de negociação (texto \"razão do pagamento\") da transação é: \"{2}\" -portfolio.pending.step3_seller.bank=Seu parceiro de negociação confirmou que ele já iniciou o pagamento de {0}.\n\nAcesse sua conta bancária online e verifique se você recebeu {1} do comprador de BTC.\n\nO ID de negociação (texto \"razão do pagamento\") da transação é: \"{2}\" +portfolio.pending.step3_seller.bank=Your trading partner has confirmed that they have initiated the {0} payment.\n\nPlease go to your online banking web page and check if you have received {1} from the BTC buyer.\n\nThe trade ID (\"reason for payment\" text) of the transaction is: \"{2}\"\n\n portfolio.pending.step3_seller.cash=\n\nComo o pagamento é realizado através de depósito de dinheiro, o comprador de BTC deve escrever \"SEM RESTITUIÇÃO\" no recibo de papel, rasgá-lo em duas partes e enviar uma foto do recibo para você por e-mail.\n\nPara evitar risco de restituição, apenas confirme caso você tenha recebido o e-mail e tem certeza de que o recibo é válido.\nSe não tiver certeza, {0} portfolio.pending.step3_seller.moneyGram=The buyer has to send you the Authorisation number and a photo of the receipt by email.\nThe receipt must clearly show your full name, country, state and the amount. Please check your email if you received the Authorisation number.\n\nAfter closing that popup you will see the BTC buyer's name and address for picking up the money from MoneyGram.\n\nOnly confirm receipt after you have successfully picked up the money! portfolio.pending.step3_seller.westernUnion=The buyer has to send you the MTCN (tracking number) and a photo of the receipt by email.\nThe receipt must clearly show your full name, city, country and the amount. Please check your email if you received the MTCN.\n\nAfter closing that popup you will see the BTC buyer's name and address for picking up the money from Western Union.\n\nOnly confirm receipt after you have successfully picked up the money! @@ -667,7 +669,7 @@ funds.tab.transactions=Transações funds.deposit.unused=Não utilizado funds.deposit.usedInTx=Utilizado em {0} transações -funds.deposit.fundBisqWallet=Depósito em carteira Bisq +funds.deposit.fundBisqWallet=Deposito em carteira Bisq funds.deposit.noAddresses=Nenhum endereço de depósito foi gerado ainda funds.deposit.fundWallet=Financiar sua carteira funds.deposit.withdrawFromWallet=Enviar fundos da carteira @@ -858,10 +860,10 @@ settings.net.directPeer=Par (direto) settings.net.peer=Par settings.net.inbound=entrante settings.net.outbound=sainte -settings.net.reSyncSPVChainLabel=Resincronizar SPV chain -settings.net.reSyncSPVChainButton=Remover arquivo SPV e resincronizar -settings.net.reSyncSPVSuccess=The SPV chain file will be deleted at the next startup. You need to restart your application now.\n\nAfter the restart it can take a while for resyncing with the network and you will only see all transactions once the resync is completed.\n\nPlease make another restart after the resync has completed because there are sometimes inconsistencies leading to incorrect balance display. -settings.net.reSyncSPVAfterRestart=O arquivo SPV chain foi removido. Favor tenha paciencia, pois pode demorar para resincronizar à rede. +settings.net.reSyncSPVChainLabel=Ressincronizar SPV chain +settings.net.reSyncSPVChainButton=Remover arquivo SPV e ressincronizar +settings.net.reSyncSPVSuccess=The SPV chain file will be deleted on the next startup. You need to restart your application now.\n\nAfter the restart it can take a while to resync with the network and you will only see all transactions once the resync is completed.\n\nPlease restart again after the resync has completed because there are sometimes inconsistencies that result in incorrect balances to display. +settings.net.reSyncSPVAfterRestart=The SPV chain file has been deleted. Please be patient. It can take a while to resync with the network. settings.net.reSyncSPVAfterRestartCompleted=A resincronização concluiu. Favor reiniciar o programa. settings.net.reSyncSPVFailed=Não foi possível apagar o arquivo da SPV chain.\nErro: {0} setting.about.aboutBisq=Sobre Bisq @@ -926,10 +928,10 @@ account.arbitratorSelection.minOne=Você precisa selecionar ao menos um árbitro account.altcoin.yourAltcoinAccounts=Suas contas de altcoins account.altcoin.popup.wallet.msg=Please be sure that you follow the requirements for the usage of {0} wallets as described on the {1} web page.\nUsing wallets from centralized exchanges where (a) you don''t control your keys or (b) which don''t use compatible wallet software is risky: it can lead to loss of the traded funds!\nThe arbitrator is not a {2} specialist and cannot help in such cases. account.altcoin.popup.wallet.confirm=Eu entendo e confirmo que eu sei qual carteira que preciso usar. -account.altcoin.popup.xmr.msg=Para negociar XMR no Bisq, certifique-se de que você entende e satisfaz os seguintes requisitos:\n\nPara enviar XMR você precisa usar uma carteira oficial do Monero (a carteira GUI ou a carteira CLI) com a flag store-tx-info habilitada (esta flag já vem habilitada por padrão nas novas versões). Certifique-se de que você consegue acessar a chave de transação (tx key), pois ela será necessária caso alguma disputa seja aberta.\nCarteira CLI (linha de comando): use o comando get_tx_key\nCarteira GUI: entre na aba Histórico e clique no botão (P) para provar um pagamento\n\nVocê pode conferir/verificar a transação através da ferramenta XMR checktx tool (https://xmr.llcoins.net/checktx.html) ou através da própria carteira.\nCarteira CLI: usando o comando (check_tx_key).\nCarteira GUI: na aba Avançado > Provar/Conferir.\nNormalmente as transferências não podem ser verificadas nos sites exploradores da blockchain do Monero\n\nCaso surja uma disputa, você precisará prover ao árbitro os seguintes dados:\n- A chave privada da transação\n- O hash da transação\n- O endereço público do recipiente\n\nSe você não conseguir prover os dados acima para o árbitro, ou se tiver usado uma carteira que não fornece estes dados, você irá perder a disputa. Nas negociações de Monero no Bisq, o remetente de XMR é a pessoa que é responsável por conseguir verificar a transferência de XMR para o árbitro em caso de disputa.\n\nO ID do pagamento não é necessário.\nSe você ainda tiver dúvidas sobre como funciona o processo, visite (https://www.getmonero.org/resources/user-guides/prove-payment.html) ou o fórum do Monero (https://forum.getmonero.org) para obter maiores informações. -account.altcoin.popup.blur.msg=If you want to trade BLUR on Bisq please be sure you understand and fulfill the following requirements:\n\nTo send BLUR you must use the Blur Network CLI or GUI Wallet. \n\nIf you are using the CLI wallet, a transaction hash (tx ID) will be displayed after a transfer is sent. You must save this information. Immediately after sending the transfer, you must use the command 'get_tx_key' to retrieve the transaction private key. If you fail to perform this step, you may not be able to retrieve the key later. \n\nIf you are using the Blur Network GUI Wallet, the transaction private key and transaction ID can be found conveniently in the "History" tab. Immediately after sending, locate the transaction of interest. Click the "?" symbol in the lower-right corner of the box containing the transaction. You must save this information. \n\nIn the event that arbitration is necessary, you must present the following to an arbitrator: 1.) the transaction ID, 2.) the transaction private key, and 3.) the recipient's address. The arbitrator will then verify the BLUR transfer using the Blur Transaction Viewer (https://blur.cash/#tx-viewer).\n\nIf you cannot provide the required information to the arbitrator, you will lose the dispute. In all cases of dispute, the BLUR sender bears 100% of the burden of responsiblity in verifying transactions to an arbitrator. \n\nIf you do not understand these requirements, do not trade on Bisq. First, seek help at the Blur Network Discord (https://discord.gg/dMWaqVW). -account.altcoin.popup.ccx.msg=If you want to trade CCX on Bisq please be sure you understand the following requirements:\n\nTo send CCX you must use an official Conceal wallet, either CLI or GUI. After sending a transfer payment, the wallets\ndisplay the transaction secret key. You must save it along with the transaction hash (ID) and the recipient's public\naddress in case arbitration is necessary. In such a case, you must give all three to the arbitrator, who will then\nverify the CCX transfer using the Conceal Transaction Viewer (https://explorer.conceal.network/txviewer).\nBecause Conceal is a privacy coin, block explorers cannot verify transfers.\n\nIf you cannot provide the required data to the arbitrator, you will lose the dispute case.\nIf you do not save the transaction secret key immediately after transferring CCX, it cannot be recovered later.\nIf you do not understand these requirements, seek help at the Conceal discord (http://discord.conceal.network). -account.altcoin.popup.drgl.msg=Trading Dragonglass on Bisq requires that you understand and fulfill the following requirements:\n\nBecause of the privacy Dragonglass provides a transaction is not verifyable on the public blockchain. If required you can prove your payment thru use of your TXN-Private-Key.\nThe TXN-Private Key is a one-time key automatically generated for every transaction that can only be accessed from within your DRGL wallet.\nEither by DRGL-wallet GUI (inside transaction details dialog) or by the Dragonglass CLI simplewallet (using command "get_tx_key").\n\nDRGL version 'Oathkeeper' and higher are REQUIRED for both.\n\nIn case of a dispute, you must provide the arbitrator the following data:\n- The TXN-Private key\n- The transaction hash\n- The recipient's public address\n\nVerification of payment can be made using the above data as inputs at \ (http://drgl.info/#check_txn).\n\nIf you cannot provide the above data or if you used an incompatible wallet it would result in losing the dispute case. The Dragonglass sender is responsible to be able to verify the DRGL transfer to the arbitrator in case of a dispute. Use of PaymentID is not required.\n\nIf you are unsure about any part of this process, visit Dragonglass on Discord (http://discord.drgl.info) for help. +account.altcoin.popup.xmr.msg=Trading XMR on Bisq requires that you understand and fulfill the following requirements:\n\nFor sending XMR, you need to use either the official Monero GUI wallet or Monero CLI wallet with the store-tx-info flag enabled (default in new versions). Please be sure you can access the tx key as that would be required in case of a dispute.\nmonero-wallet-cli (use the command get_tx_key)\nmonero-wallet-gui (go to history tab and click on the (P) button for payment proof)\n\nIn addition to XMR checktx tool (https://xmr.llcoins.net/checktx.html) verification can also be accomplished in-wallet.\nmonero-wallet-cli : using command (check_tx_key).\nmonero-wallet-gui : on the Advanced > Prove/Check page.\nAt normal block explorers the transfer is not verifiable.\n\nYou need to provide the arbitrator the following data in case of a dispute:\n- The tx private key\n- The transaction hash\n- The recipient's public address\n\nFailure to provide the above data, or if you used an incompatible wallet, will result in losing the dispute case. The XMR sender is responsible for providing verification of the XMR transfer to the arbitrator in case of a dispute.\n\nThere is no payment ID required, just the normal public address.\nIf you are not sure about that process visit (https://www.getmonero.org/resources/user-guides/prove-payment.html) or the Monero forum (https://forum.getmonero.org) to find more information. +account.altcoin.popup.blur.msg=Trading BLUR on Bisq requires that you understand and fulfill the following requirements:\n\nTo send BLUR you must use the Blur Network CLI or GUI Wallet. \n\nIf you are using the CLI wallet, a transaction hash (tx ID) will be displayed after a transfer is sent. You must save this information. Immediately after sending the transfer, you must use the command 'get_tx_key' to retrieve the transaction private key. If you fail to perform this step, you may not be able to retrieve the key later. \n\nIf you are using the Blur Network GUI Wallet, the transaction private key and transaction ID can be found conveniently in the "History" tab. Immediately after sending, locate the transaction of interest. Click the "?" symbol in the lower-right corner of the box containing the transaction. You must save this information. \n\nIn the event that arbitration is necessary, you must present the following to an arbitrator: 1.) the transaction ID, 2.) the transaction private key, and 3.) the recipient's address. The arbitrator will then verify the BLUR transfer using the Blur Transaction Viewer (https://blur.cash/#tx-viewer).\n\nFailure to provide the required information to the arbitrator will result in losing the dispute case. In all cases of dispute, the BLUR sender bears 100% of the burden of responsibility in verifying transactions to an arbitrator. \n\nIf you do not understand these requirements, do not trade on Bisq. First, seek help at the Blur Network Discord (https://discord.gg/dMWaqVW). +account.altcoin.popup.ccx.msg=Trading CCX on Bisq requires that you understand the following requirements:\n\nTo send CCX you must use an official Conceal wallet, either CLI or GUI. After sending a transfer payment, the wallets\ndisplay the transaction secret key. You must save it along with the transaction hash (ID) and the recipient's public\naddress in case arbitration is necessary. In such a case, you must give all three to the arbitrator, who will then\nverify the CCX transfer using the Conceal Transaction Viewer (https://explorer.conceal.network/txviewer).\nBecause Conceal is a privacy coin, block explorers cannot verify transfers.\n\nFailure to provide the required data to the arbitrator will result in losing the dispute case.\nIf you do not save the transaction secret key immediately after transferring CCX, it cannot be recovered later.\nIf you do not understand these requirements, seek help at the Conceal discord (http://discord.conceal.network). +account.altcoin.popup.drgl.msg=Trading Dragonglass on Bisq requires that you understand and fulfill the following requirements:\n\nBecause of the privacy Dragonglass provides, a transaction is not verifiable on the public blockchain. If required, you can prove your payment through the use of your TXN-Private-Key.\nThe TXN-Private Key is a one-time key automatically generated for every transaction that can only be accessed from within your DRGL wallet.\nEither by DRGL-wallet GUI (inside transaction details dialog) or by the Dragonglass CLI simplewallet (using command "get_tx_key").\n\nDRGL version 'Oathkeeper' and higher are REQUIRED for both.\n\nIn case of a dispute, you must provide the arbitrator the following data:\n- The TXN-Private key\n- The transaction hash\n- The recipient's public address\n\nVerification of payment can be made using the above data as inputs at (http://drgl.info/#check_txn).\n\nFailure to provide the above data, or if you used an incompatible wallet, will result in losing the dispute case. The Dragonglass sender is responsible for providing verification of the DRGL transfer to the arbitrator in case of a dispute. Use of PaymentID is not required.\n\nIf you are unsure about any part of this process, visit Dragonglass on Discord (http://discord.drgl.info) for help. account.altcoin.popup.ZEC.msg=Quando usar {0} você pode apenas utilizar endereços transparentes (começando com t) não os endereços z (privados), pois o árbitro não conseguiria verificar a transação com endereços z. account.altcoin.popup.XZC.msg=Ao usar {0}, você obrigatoriamente precisa usar endereços transparentes (rastreáveis), caso contrário o árbitro não conseguiria verificar em um explorador de blocos uma transação com endereço privado (irrastreável). account.altcoin.popup.bch=Bitcoin Cash and Bitcoin Clashic suffer from replay protection. If you use those coins be sure you take sufficient precautions and understand all implications.You can suffer losses by sending one coin and unintentionally send the same coins on the other block chain.Because those "airdrop coins" share the same history with the Bitcoin blockchain there are also security risks and a considerable risk for losing privacy.\n\nPlease read at the Bisq Forum more about that topic: https://forum.bisq.io/t/airdrop-coins-information-thread-bch-btg-bchc @@ -1019,7 +1021,7 @@ account.notifications.marketAlert.manageAlerts.header.offerType=Tipo de oferta account.notifications.marketAlert.message.title=Alerta de oferta account.notifications.marketAlert.message.msg.below=abaixo account.notifications.marketAlert.message.msg.above=acima -account.notifications.marketAlert.message.msg=A new ''{0} {1}'' offer with price {2} ({3} {4} market price) and payment method ''{5}'' was published to the Bisq offerbook.\nOffer ID: {6}. +account.notifications.marketAlert.message.msg=Uma nova ''{0} {1}'' oferta com preço {2} ({3} {4} preço de mercado) e com o método de pagamento ''{5}'' foi publicada no livro de ofertas do Bisq.\nID da oferta: {6}. account.notifications.priceAlert.message.title=Alerta de preço para {0} account.notifications.priceAlert.message.msg=O seu preço de alerta foi atingido. O preço atual da {0} é {1} {2} account.notifications.noWebCamFound.warning=Nenhuma webcam foi encontrada.\n\nPor favor, use a opção e-mail para enviar o token e a chave de criptografia do seu celular para o Bisq @@ -1306,7 +1308,7 @@ dao.burnBsq.assets.lookBackPeriod=Verification period dao.burnBsq.assets.trialFee=Fee for trial period dao.burnBsq.assets.totalFee=Total de taxas pagas dao.burnBsq.assets.days={0} dias -dao.burnBsq.assets.toFewDays=The asset fee is too low. The min. amount of days for the trial perios is {0}. +dao.burnBsq.assets.toFewDays=The asset fee is too low. The min. amount of days for the trial period is {0}. # suppress inspection "UnusedProperty" dao.assetState.UNDEFINED=Indefinido @@ -1322,7 +1324,7 @@ dao.assetState.REMOVED_BY_VOTING=Removed by voting dao.proofOfBurn.header=Proof of burn dao.proofOfBurn.amount=Quantia dao.proofOfBurn.preImage=Pre-image -dao.proofOfQueimar.burn=Queimar +dao.proofOfBurn.burn=Queimar dao.proofOfBurn.allTxs=All proof of burn transactions dao.proofOfBurn.myItems=My proof of burn transactions dao.proofOfBurn.date=Data @@ -1584,7 +1586,7 @@ displayUpdateDownloadWindow.verify.failed=Falha durante a verificação.\nPor fa displayUpdateDownloadWindow.success=A nova versão foi baixada com sucesso e teve a sua assinatura verificada.\n\nPara usá-la, abra a pasta de downloads, feche o programa e instale a nova versão. displayUpdateDownloadWindow.download.openDir=Abrir pasta de download -disputeResumoWindow.title=Resumo +disputeSummaryWindow.title=Resumo disputeSummaryWindow.openDate=Data da abertura do ticket disputeSummaryWindow.role=Trader's role disputeSummaryWindow.evidence=Evidence @@ -1746,7 +1748,7 @@ popup.headline.error=Erro popup.doNotShowAgain=Não mostrar novamente popup.reportError.log=Abrir arquivo de log popup.reportError.gitHub=Relatar à lista de problemas do GitHub -popup.reportError={0}\n\nTo help us to improve the software please report the bug on our issue tracker on GitHub (https://github.com/bisq-network/bisq-desktop/issues).\nThe error message will be copied to the clipboard when you click a button below.\nIt will make debugging easier if you can attach the bisq.log file as well. +popup.reportError={0}\n\nTo help us to improve the software please report this bug by opening a new issue at https://github.com/bisq-network/bisq/issues.\nThe above error message will be copied to the clipboard when you click either of the buttons below.\nIt will make debugging easier if you include the bisq.log file by pressing "Open log file", saving a copy, and attaching it to your bug report. popup.error.tryRestart=Por favor, reinicie o aplicativo e verifique sua conexão de Internet para ver se o problema foi resolvido. popup.error.takeOfferRequestFailed=Um erro ocorreu quando alguém tentou aceitar uma de suas ofertas:\n{0} @@ -1805,6 +1807,9 @@ popup.attention.forTradeWithId=Atenção para a negociação com ID {0} popup.roundedFiatValues.headline=Nova funcionalidade de privacidade: valores arredondados em moeda fiduciária popup.roundedFiatValues.msg=Para aumentar a privacidade da sua transação, a quantia {0} foi arredondada.\n\nDependendo da versão do cliente, você irá pagar ou receber valores com decimais ou valores arredondados.\n\nAmbos os valores se enquadram no protocolo de negociação.\n\nPerceba também que os valores em BTC são modificados automaticamente para corresponder o mais próximo possível à quantia em fiat arredondada. +popup.info.multiplePaymentAccounts.headline=Multiple payment accounts available +popup.info.multiplePaymentAccounts.msg=You have multiple payment accounts available for this offer. Please make sure you've picked the right one. + #################################################################### # Notifications @@ -1817,7 +1822,7 @@ notification.trade.accepted=Sua oferta foi aceita por um {0} BTC. notification.trade.confirmed=Sua negociação tem ao menos uma confirmação da blockchain.\nVocê pode iniciar o pagamento agora. notification.trade.paymentStarted=O comprador BTC iniciou o pagamento notification.trade.selectTrade=Selecionar negociação -notification.trade.peerOpenedDispute=Seu parceiro de negociação +notification.trade.peerOpenedDispute=Seu parceiro de negociação abriu um {0}. notification.trade.disputeClosed=A {0} foi fechada. notification.walletUpdate.headline=Update da carteira de negociação notification.walletUpdate.msg=Sua carteira Bisq tem saldo suficiente.\nQuantia: {0} @@ -2085,7 +2090,7 @@ payment.clearXchange.info=Please be sure that you fulfill the requirements for t payment.moneyGram.info=When using MoneyGram the BTC buyer has to send the Authorisation number and a photo of the receipt by email to the BTC seller. The receipt must clearly show the seller's full name, country, state and the amount. The buyer will get displayed the seller's email in the trade process. payment.westernUnion.info=When using Western Union the BTC buyer has to send the MTCN (tracking number) and a photo of the receipt by email to the BTC seller. The receipt must clearly show the seller's full name, city, country and the amount. The buyer will get displayed the seller's email in the trade process. -payment.halCash.info=When using HalCash the BTC buyer need to send the BTC seller the HalCash code via a text message from the mobile phone.\n\nPlease make sure to not exceed the maximum amount your bank allows you to send with HalCash. The min. amount per withdrawal is 10 EUR and the max. amount is 600 EUR. For repeated withdrawals it is 3000 EUR per receiver per day and 6000 EUR per receiver per month. Please cross check those limits with your bank to be sure they use the same limits as stated here.\n\nThe withdrawal amount must be a multiple of 10 EUR as you cannot withdraw other amounts from an ATM. The UI in the create-offer and take-offer screen will adjust the BTC amount so that the EUR amount is correct. You cannot use market based price as the EUR amount would be changing with changing prices.\n\nIn case of a dispute the BTC buyer need to provide the proof that he sent the EUR. +payment.halCash.info=When using HalCash the BTC buyer needs to send the BTC seller the HalCash code via a text message from their mobile phone.\n\nPlease make sure to not exceed the maximum amount your bank allows you to send with HalCash. The min. amount per withdrawal is 10 EUR and the max. amount is 600 EUR. For repeated withdrawals it is 3000 EUR per receiver per day and 6000 EUR per receiver per month. Please cross check those limits with your bank to be sure they use the same limits as stated here.\n\nThe withdrawal amount must be a multiple of 10 EUR as you cannot withdraw other amounts from an ATM. The UI in the create-offer and take-offer screen will adjust the BTC amount so that the EUR amount is correct. You cannot use market based price as the EUR amount would be changing with changing prices.\n\nIn case of a dispute the BTC buyer needs to provide the proof that they sent the EUR. payment.limits.info=Por favor, esteja ciente de que todas as transferências bancárias possuem um certo risco de serem estornadas.\n\nPara reduzir esse risco, o Bisq definite limites por transação, que são baseados em dois fatores:\n\n1. O nível estimado de risco de estorno para o método de pagamento utilizado\n2. A idade da sua conta para aquele método de pagamento\n\nA conta que você está criando agora é considerada nova, e portanto tem uma idade de zero. À medida que a idade da sua conta for aumentando, os seus limites também irão aumentar:\n\n● Durante o 1º mês, o seu limite por negociação será de {0}\n● Durante o 2º mês, o seu limite por negociação será de {1}\n● Após o 2º mês, o seu limite por negociação será de {2}\n\nNote que esses limites são para cada negociação. Não existem limites no número total de negociações que você pode realizar. payment.cashDeposit.info=Certifique-se de que o seu banco permite a realização de depósitos em espécie na conta de terceiros. @@ -2098,7 +2103,7 @@ payment.f2f.optionalExtra=Informações adicionais opcionais payment.f2f.extra=Informações adicionais payment.f2f.extra.prompt=The maker can define 'terms and conditions' or add a public contact information. It will be displayed with the offer. -payment.f2f.info='Face to Face' trades have different rules and come with different risks than online transactions.\n\nThe main differences are:\n● The trading peers need to exchange information about the meeting location and time by using their provided contact details.\n● The trading peers need to bring their laptops and do the confirmation of 'payment sent' and 'payment received' at the meeting place.\n● If a maker has special 'terms and conditions' he needs to state those in the 'Addition information' text field in the account.\n● By taking an offer the taker agrees to the maker's stated 'terms and conditions'.\n● In case of a dispute the arbitrator cannot help much as it is usually hard to get tamper proof evidence of what happened at the meeting. In such cases the BTC funds might get locked indefinitely or until the trading peers come to an agreement.\n\nTo be sure you fully understand the differences with 'Face to Face' trades please read the instructions and recommendations at: 'https://docs.bisq.network/trading-rules.html#f2f-trading' +payment.f2f.info='Face to Face' trades have different rules and come with different risks than online transactions.\n\nThe main differences are:\n● The trading peers need to exchange information about the meeting location and time by using their provided contact details.\n● The trading peers need to bring their laptops and do the confirmation of 'payment sent' and 'payment received' at the meeting place.\n● If a maker has special 'terms and conditions' they must state those in the 'Additional information' text field in the account.\n● By taking an offer the taker agrees to the maker's stated 'terms and conditions'.\n● In case of a dispute the arbitrator cannot help much as it is usually hard to get tamper proof evidence of what happened at the meeting. In such cases the BTC funds might get locked indefinitely or until the trading peers come to an agreement.\n\nTo be sure you fully understand the differences with 'Face to Face' trades please read the instructions and recommendations at: 'https://docs.bisq.network/trading-rules.html#f2f-trading' payment.f2f.info.openURL=Abrir site payment.f2f.offerbook.tooltip.countryAndCity=Estado e cidade: {0} / {1} payment.f2f.offerbook.tooltip.extra=Informações adicionais: {0} diff --git a/core/src/main/resources/i18n/displayStrings_ro.properties b/core/src/main/resources/i18n/displayStrings_ro.properties index b756fbe1d1..6efcf95dfa 100644 --- a/core/src/main/resources/i18n/displayStrings_ro.properties +++ b/core/src/main/resources/i18n/displayStrings_ro.properties @@ -299,6 +299,8 @@ market.trades.tooltip.candle.date=Data: offerbook.createOffer=Creează oferta: offerbook.takeOffer=Acceptă oferta: +offerbook.takeOfferToBuy=Take offer to buy {0} +offerbook.takeOfferToSell=Take offer to sell {0} offerbook.trader=Comerciant offerbook.offerersBankId=Codul băncii ofertantului: {0} offerbook.offerersBankName=Numele băncii ofertantului: {0} @@ -560,12 +562,12 @@ portfolio.pending.step3_buyer.warn.part1b=la furnizorul tău de plăți (ex: ban portfolio.pending.step3_buyer.warn.part2=Vânzătorul de BTC încă nu ți-a confirmat plata!\nVerifică {0} dacă plata a fost executată cu succes.\nDacă vânzătorul de BTC nu confirmă primirea plății până la data de {1} tranzacția va fi investigată de arbitru. portfolio.pending.step3_buyer.openForDispute=Vânzătorul de BTC înca nu ți-a confirmat plata!\nPerioada maximă de timp pentru tranzacționare a expirat.\nPoți aștepta mai mult astfel acordând mai mult timp partenerului de tranzacționare sau poți contacta arbitrul în vederea deschiderii unei dispute. # suppress inspection "TrailingSpacesInProperty" -portfolio.pending.step3_seller.part=Partenerul tău de tranzacționare a confirmat că a inițiat plata {0}.\n\n +portfolio.pending.step3_seller.part=Your trading partner has confirmed that they have initiated the {0} payment.\n\n portfolio.pending.step3_seller.altcoin.explorer=on your favorite {0} blockchain explorer portfolio.pending.step3_seller.altcoin.wallet=at your {0} wallet portfolio.pending.step3_seller.altcoin={0}Please check {1} if the transaction to your receiving address\n{2}\nhas already sufficient blockchain confirmations.\nThe payment amount has to be {3}\n\nYou can copy & paste your {4} address from the main screen after closing that popup. portfolio.pending.step3_seller.postal={0}Verifică dacă ai primit {1} prin \"Ordin de plată poștală SUA\" de la cumpărătorul BTC.\n\nCodul tranzacției (\"motivul plății\") este: \"{2}\" -portfolio.pending.step3_seller.bank=Your trading partner has confirmed that he initiated the {0} payment.\n\nPlease go to your online banking web page and check if you have received {1} from the BTC buyer.\n\nThe trade ID (\"reason for payment\" text) of the transaction is: \"{2}\"\n\n +portfolio.pending.step3_seller.bank=Your trading partner has confirmed that they have initiated the {0} payment.\n\nPlease go to your online banking web page and check if you have received {1} from the BTC buyer.\n\nThe trade ID (\"reason for payment\" text) of the transaction is: \"{2}\"\n\n portfolio.pending.step3_seller.cash=Because the payment is done via Cash Deposit the BTC buyer has to write \"NO REFUND\" on the paper receipt, tear it in 2 parts and send you a photo by email.\n\nTo avoid chargeback risk, only confirm if you received the email and if you are sure the paper receipt is valid.\nIf you are not sure, {0} portfolio.pending.step3_seller.moneyGram=The buyer has to send you the Authorisation number and a photo of the receipt by email.\nThe receipt must clearly show your full name, country, state and the amount. Please check your email if you received the Authorisation number.\n\nAfter closing that popup you will see the BTC buyer's name and address for picking up the money from MoneyGram.\n\nOnly confirm receipt after you have successfully picked up the money! portfolio.pending.step3_seller.westernUnion=Cumpărătorul trebuie să îți trimită numărul MTCN (numărul de urmărire) și o fotografie a chitanței prin e-mail.\nPe chitanță trebuie să apară în mod clar numele tău complet, orașul, țara și suma. Verifică-ți adresa de e-mail dacă primești MTCN-ul.\n\nDupă închiderea acestei ferestre vei vedea numele și adresa cumpărătorului de BTC pentru a ridica banii prin Western Union.\n\nConfirmă primirea numai după ce ai ridicat banii! @@ -926,10 +928,10 @@ account.arbitratorSelection.minOne=Trebuie să ai ales cel puțin un arbitru. account.altcoin.yourAltcoinAccounts=Your altcoin accounts account.altcoin.popup.wallet.msg=Please be sure that you follow the requirements for the usage of {0} wallets as described on the {1} web page.\nUsing wallets from centralized exchanges where (a) you don''t control your keys or (b) which don''t use compatible wallet software is risky: it can lead to loss of the traded funds!\nThe arbitrator is not a {2} specialist and cannot help in such cases. account.altcoin.popup.wallet.confirm=Înțeleg și confirm că știu ce portofel trebuie să folosesc. -account.altcoin.popup.xmr.msg=If you want to trade XMR on Bisq please be sure you understand and fulfill the following requirements:\n\nFor sending XMR you need to use either the official Monero GUI wallet or Monero CLI wallet with the store-tx-info flag enabled (default in new versions). Please be sure you can access the tx key as that would be required in case of a dispute.\nmonero-wallet-cli (use the command get_tx_key)\nmonero-wallet-gui (go to history tab and click on the (P) button for payment proof)\n\nIn addition to XMR checktx tool (https://xmr.llcoins.net/checktx.html) verification can also be accomplished in-wallet.\nmonero-wallet-cli : using command (check_tx_key).\nmonero-wallet-gui : on the Advanced > Prove/Check page.\nAt normal block explorers the transfer is not verifiable.\n\nYou need to provide the arbitrator the following data in case of a dispute:\n- The tx private key\n- The transaction hash\n- The recipient's public address\n\nIf you cannot provide the above data or if you used an incompatible wallet it would result in losing the dispute case. The XMR sender is responsible to be able to verify the XMR transfer to the arbitrator in case of a dispute.\n\nThere is no payment ID required, just the normal public address.\nIf you are not sure about that process visit (https://www.getmonero.org/resources/user-guides/prove-payment.html) or the Monero forum (https://forum.getmonero.org) to find more information. -account.altcoin.popup.blur.msg=If you want to trade BLUR on Bisq please be sure you understand and fulfill the following requirements:\n\nTo send BLUR you must use the Blur Network CLI or GUI Wallet. \n\nIf you are using the CLI wallet, a transaction hash (tx ID) will be displayed after a transfer is sent. You must save this information. Immediately after sending the transfer, you must use the command 'get_tx_key' to retrieve the transaction private key. If you fail to perform this step, you may not be able to retrieve the key later. \n\nIf you are using the Blur Network GUI Wallet, the transaction private key and transaction ID can be found conveniently in the "History" tab. Immediately after sending, locate the transaction of interest. Click the "?" symbol in the lower-right corner of the box containing the transaction. You must save this information. \n\nIn the event that arbitration is necessary, you must present the following to an arbitrator: 1.) the transaction ID, 2.) the transaction private key, and 3.) the recipient's address. The arbitrator will then verify the BLUR transfer using the Blur Transaction Viewer (https://blur.cash/#tx-viewer).\n\nIf you cannot provide the required information to the arbitrator, you will lose the dispute. In all cases of dispute, the BLUR sender bears 100% of the burden of responsiblity in verifying transactions to an arbitrator. \n\nIf you do not understand these requirements, do not trade on Bisq. First, seek help at the Blur Network Discord (https://discord.gg/dMWaqVW). -account.altcoin.popup.ccx.msg=If you want to trade CCX on Bisq please be sure you understand the following requirements:\n\nTo send CCX you must use an official Conceal wallet, either CLI or GUI. After sending a transfer payment, the wallets\ndisplay the transaction secret key. You must save it along with the transaction hash (ID) and the recipient's public\naddress in case arbitration is necessary. In such a case, you must give all three to the arbitrator, who will then\nverify the CCX transfer using the Conceal Transaction Viewer (https://explorer.conceal.network/txviewer).\nBecause Conceal is a privacy coin, block explorers cannot verify transfers.\n\nIf you cannot provide the required data to the arbitrator, you will lose the dispute case.\nIf you do not save the transaction secret key immediately after transferring CCX, it cannot be recovered later.\nIf you do not understand these requirements, seek help at the Conceal discord (http://discord.conceal.network). -account.altcoin.popup.drgl.msg=Trading Dragonglass on Bisq requires that you understand and fulfill the following requirements:\n\nBecause of the privacy Dragonglass provides a transaction is not verifyable on the public blockchain. If required you can prove your payment thru use of your TXN-Private-Key.\nThe TXN-Private Key is a one-time key automatically generated for every transaction that can only be accessed from within your DRGL wallet.\nEither by DRGL-wallet GUI (inside transaction details dialog) or by the Dragonglass CLI simplewallet (using command "get_tx_key").\n\nDRGL version 'Oathkeeper' and higher are REQUIRED for both.\n\nIn case of a dispute, you must provide the arbitrator the following data:\n- The TXN-Private key\n- The transaction hash\n- The recipient's public address\n\nVerification of payment can be made using the above data as inputs at \ (http://drgl.info/#check_txn).\n\nIf you cannot provide the above data or if you used an incompatible wallet it would result in losing the dispute case. The Dragonglass sender is responsible to be able to verify the DRGL transfer to the arbitrator in case of a dispute. Use of PaymentID is not required.\n\nIf you are unsure about any part of this process, visit Dragonglass on Discord (http://discord.drgl.info) for help. +account.altcoin.popup.xmr.msg=Trading XMR on Bisq requires that you understand and fulfill the following requirements:\n\nFor sending XMR, you need to use either the official Monero GUI wallet or Monero CLI wallet with the store-tx-info flag enabled (default in new versions). Please be sure you can access the tx key as that would be required in case of a dispute.\nmonero-wallet-cli (use the command get_tx_key)\nmonero-wallet-gui (go to history tab and click on the (P) button for payment proof)\n\nIn addition to XMR checktx tool (https://xmr.llcoins.net/checktx.html) verification can also be accomplished in-wallet.\nmonero-wallet-cli : using command (check_tx_key).\nmonero-wallet-gui : on the Advanced > Prove/Check page.\nAt normal block explorers the transfer is not verifiable.\n\nYou need to provide the arbitrator the following data in case of a dispute:\n- The tx private key\n- The transaction hash\n- The recipient's public address\n\nFailure to provide the above data, or if you used an incompatible wallet, will result in losing the dispute case. The XMR sender is responsible for providing verification of the XMR transfer to the arbitrator in case of a dispute.\n\nThere is no payment ID required, just the normal public address.\nIf you are not sure about that process visit (https://www.getmonero.org/resources/user-guides/prove-payment.html) or the Monero forum (https://forum.getmonero.org) to find more information. +account.altcoin.popup.blur.msg=Trading BLUR on Bisq requires that you understand and fulfill the following requirements:\n\nTo send BLUR you must use the Blur Network CLI or GUI Wallet. \n\nIf you are using the CLI wallet, a transaction hash (tx ID) will be displayed after a transfer is sent. You must save this information. Immediately after sending the transfer, you must use the command 'get_tx_key' to retrieve the transaction private key. If you fail to perform this step, you may not be able to retrieve the key later. \n\nIf you are using the Blur Network GUI Wallet, the transaction private key and transaction ID can be found conveniently in the "History" tab. Immediately after sending, locate the transaction of interest. Click the "?" symbol in the lower-right corner of the box containing the transaction. You must save this information. \n\nIn the event that arbitration is necessary, you must present the following to an arbitrator: 1.) the transaction ID, 2.) the transaction private key, and 3.) the recipient's address. The arbitrator will then verify the BLUR transfer using the Blur Transaction Viewer (https://blur.cash/#tx-viewer).\n\nFailure to provide the required information to the arbitrator will result in losing the dispute case. In all cases of dispute, the BLUR sender bears 100% of the burden of responsibility in verifying transactions to an arbitrator. \n\nIf you do not understand these requirements, do not trade on Bisq. First, seek help at the Blur Network Discord (https://discord.gg/dMWaqVW). +account.altcoin.popup.ccx.msg=Trading CCX on Bisq requires that you understand the following requirements:\n\nTo send CCX you must use an official Conceal wallet, either CLI or GUI. After sending a transfer payment, the wallets\ndisplay the transaction secret key. You must save it along with the transaction hash (ID) and the recipient's public\naddress in case arbitration is necessary. In such a case, you must give all three to the arbitrator, who will then\nverify the CCX transfer using the Conceal Transaction Viewer (https://explorer.conceal.network/txviewer).\nBecause Conceal is a privacy coin, block explorers cannot verify transfers.\n\nFailure to provide the required data to the arbitrator will result in losing the dispute case.\nIf you do not save the transaction secret key immediately after transferring CCX, it cannot be recovered later.\nIf you do not understand these requirements, seek help at the Conceal discord (http://discord.conceal.network). +account.altcoin.popup.drgl.msg=Trading Dragonglass on Bisq requires that you understand and fulfill the following requirements:\n\nBecause of the privacy Dragonglass provides, a transaction is not verifiable on the public blockchain. If required, you can prove your payment through the use of your TXN-Private-Key.\nThe TXN-Private Key is a one-time key automatically generated for every transaction that can only be accessed from within your DRGL wallet.\nEither by DRGL-wallet GUI (inside transaction details dialog) or by the Dragonglass CLI simplewallet (using command "get_tx_key").\n\nDRGL version 'Oathkeeper' and higher are REQUIRED for both.\n\nIn case of a dispute, you must provide the arbitrator the following data:\n- The TXN-Private key\n- The transaction hash\n- The recipient's public address\n\nVerification of payment can be made using the above data as inputs at (http://drgl.info/#check_txn).\n\nFailure to provide the above data, or if you used an incompatible wallet, will result in losing the dispute case. The Dragonglass sender is responsible for providing verification of the DRGL transfer to the arbitrator in case of a dispute. Use of PaymentID is not required.\n\nIf you are unsure about any part of this process, visit Dragonglass on Discord (http://discord.drgl.info) for help. account.altcoin.popup.ZEC.msg=Atunci când folosești {0}, poți utiliza doar adresele transparente (începând cu t) nu adresele z (private), deoarece arbitrul nu va putea verifica tranzacția cu adrese z. account.altcoin.popup.XZC.msg=Când folosești {0}, poți folosi numai adresele transparente (ce pot fi urmărite), nu adresele indetectabile, deoarece arbitrul nu va putea verifica tranzacția executată cu adrese ce nu pot fi citite de către un explorator de bloc. account.altcoin.popup.bch=Bitcoin Cash și Bitcoin Clashic suferă de protecție împotriva reluării. Dacă folosești aceste monede, asigură-te că ai luat măsurile necesare de precauție și înțelegi toate implicațiile. Poți suferi pierderi prin trimiterea unei monezi și neintenționat să trimiți aceeași monedă pe celălalt blockchain. Deoarece acele "monede airdrop" au aceeași istorie cu blockchainul Bitcoin există și riscuri de securitate cât și un risc considerabil în pierderea confidențialității.\n\nTe invităm să citești mai multe despre acest subiect pe forumul Bisq: https://forum.bisq.io/t/airdrop-coins-information-thread-bch-btg-bchc @@ -1306,7 +1308,7 @@ dao.burnBsq.assets.lookBackPeriod=Verification period dao.burnBsq.assets.trialFee=Fee for trial period dao.burnBsq.assets.totalFee=Total fees paid dao.burnBsq.assets.days={0} days -dao.burnBsq.assets.toFewDays=The asset fee is too low. The min. amount of days for the trial perios is {0}. +dao.burnBsq.assets.toFewDays=The asset fee is too low. The min. amount of days for the trial period is {0}. # suppress inspection "UnusedProperty" dao.assetState.UNDEFINED=Nedefinit @@ -1584,7 +1586,7 @@ displayUpdateDownloadWindow.verify.failed=Verficare eșuată.\nTe rugăm descarc displayUpdateDownloadWindow.success=Noua versiune a fost descărcată cu succes iar semnătura a fost verificată.\n\nDeschide directorul de descărcare, închide aplicația și instalează noua versiune. displayUpdateDownloadWindow.download.openDir=Deschide directorul descărcărilor -disputeRezumatWindow.title=Rezumat +disputeSummaryWindow.title=Rezumat disputeSummaryWindow.openDate=Ticket opening date disputeSummaryWindow.role=Trader's role disputeSummaryWindow.evidence=Evidence @@ -1746,7 +1748,7 @@ popup.headline.error=Eroare popup.doNotShowAgain=Nu arăta din nou popup.reportError.log=Deschide fișierul jurnal popup.reportError.gitHub=Reclamare către Github -popup.reportError={0}\n\nTo help us to improve the software please report the bug on our issue tracker on GitHub (https://github.com/bisq-network/bisq-desktop/issues).\nThe error message will be copied to the clipboard when you click a button below.\nIt will make debugging easier if you can attach the bisq.log file as well. +popup.reportError={0}\n\nTo help us to improve the software please report this bug by opening a new issue at https://github.com/bisq-network/bisq/issues.\nThe above error message will be copied to the clipboard when you click either of the buttons below.\nIt will make debugging easier if you include the bisq.log file by pressing "Open log file", saving a copy, and attaching it to your bug report. popup.error.tryRestart=Încearcă să repornești aplicația și să verifici conexiunea la rețea pentru a vedea dacă poți remedia astfel problema. popup.error.takeOfferRequestFailed=A intervenit o eroare când cineva a încercat să îți preia una din oferte:\n{0} @@ -1805,6 +1807,9 @@ popup.attention.forTradeWithId=Atenție solicitată pentru tranzacția cu codul popup.roundedFiatValues.headline=New privacy feature: Rounded fiat values popup.roundedFiatValues.msg=To increase privacy of your trade the {0} amount was rounded.\n\nDepending on the client version you''ll pay or receive either values with decimals or rounded ones.\n\nBoth values do comply from now on with the trade protocol.\n\nAlso be aware that BTC values are changed automatically to match the rounded fiat amount as close as possible. +popup.info.multiplePaymentAccounts.headline=Multiple payment accounts available +popup.info.multiplePaymentAccounts.msg=You have multiple payment accounts available for this offer. Please make sure you've picked the right one. + #################################################################### # Notifications @@ -2085,7 +2090,7 @@ payment.clearXchange.info=Please be sure that you fulfill the requirements for t payment.moneyGram.info=When using MoneyGram the BTC buyer has to send the Authorisation number and a photo of the receipt by email to the BTC seller. The receipt must clearly show the seller's full name, country, state and the amount. The buyer will get displayed the seller's email in the trade process. payment.westernUnion.info=When using Western Union the BTC buyer has to send the MTCN (tracking number) and a photo of the receipt by email to the BTC seller. The receipt must clearly show the seller's full name, city, country and the amount. The buyer will get displayed the seller's email in the trade process. -payment.halCash.info=When using HalCash the BTC buyer need to send the BTC seller the HalCash code via a text message from the mobile phone.\n\nPlease make sure to not exceed the maximum amount your bank allows you to send with HalCash. The min. amount per withdrawal is 10 EUR and the max. amount is 600 EUR. For repeated withdrawals it is 3000 EUR per receiver per day and 6000 EUR per receiver per month. Please cross check those limits with your bank to be sure they use the same limits as stated here.\n\nThe withdrawal amount must be a multiple of 10 EUR as you cannot withdraw other amounts from an ATM. The UI in the create-offer and take-offer screen will adjust the BTC amount so that the EUR amount is correct. You cannot use market based price as the EUR amount would be changing with changing prices.\n\nIn case of a dispute the BTC buyer need to provide the proof that he sent the EUR. +payment.halCash.info=When using HalCash the BTC buyer needs to send the BTC seller the HalCash code via a text message from their mobile phone.\n\nPlease make sure to not exceed the maximum amount your bank allows you to send with HalCash. The min. amount per withdrawal is 10 EUR and the max. amount is 600 EUR. For repeated withdrawals it is 3000 EUR per receiver per day and 6000 EUR per receiver per month. Please cross check those limits with your bank to be sure they use the same limits as stated here.\n\nThe withdrawal amount must be a multiple of 10 EUR as you cannot withdraw other amounts from an ATM. The UI in the create-offer and take-offer screen will adjust the BTC amount so that the EUR amount is correct. You cannot use market based price as the EUR amount would be changing with changing prices.\n\nIn case of a dispute the BTC buyer needs to provide the proof that they sent the EUR. payment.limits.info=Rețineți că toate transferurile bancare au un anumit risc de rambursare.\n\nPentru a diminua acest risc, Bisq stabilește limite de tranzacționare bazate pe doi factori:\n\n1. Nivelul estimat al riscului de rambursare pentru metoda de plată utilizată\n2. Vechimea contului tău pentru metodă de plată aleasă\n\nContul pe care îl creezi acum este nou iar vechimea acestuia este zero. Pe măsură ce contul tău avansează în vechime pe parcursul unei perioade de două luni, limitele per-tranzacție vor crește împreună cu vechimea:\n\n● În prima lună, limita ta per-tranzacție va fi {0}\n● În cea de-a doua lună, limita ta per-tranzacție va fi {1}\n● După cea de-a doua lună, limita ta per-tranzacție va fi {2}\n\nReține că nu sunt impuse limite privind numărul total de ocazii în care poți tranzacționa. payment.cashDeposit.info=Please confirm your bank allows you to send cash deposits into other peoples' accounts. For example, Bank of America and Wells Fargo no longer allow such deposits. @@ -2098,7 +2103,7 @@ payment.f2f.optionalExtra=Optional additional information payment.f2f.extra=Additional information payment.f2f.extra.prompt=The maker can define 'terms and conditions' or add a public contact information. It will be displayed with the offer. -payment.f2f.info='Face to Face' trades have different rules and come with different risks than online transactions.\n\nThe main differences are:\n● The trading peers need to exchange information about the meeting location and time by using their provided contact details.\n● The trading peers need to bring their laptops and do the confirmation of 'payment sent' and 'payment received' at the meeting place.\n● If a maker has special 'terms and conditions' he needs to state those in the 'Addition information' text field in the account.\n● By taking an offer the taker agrees to the maker's stated 'terms and conditions'.\n● In case of a dispute the arbitrator cannot help much as it is usually hard to get tamper proof evidence of what happened at the meeting. In such cases the BTC funds might get locked indefinitely or until the trading peers come to an agreement.\n\nTo be sure you fully understand the differences with 'Face to Face' trades please read the instructions and recommendations at: 'https://docs.bisq.network/trading-rules.html#f2f-trading' +payment.f2f.info='Face to Face' trades have different rules and come with different risks than online transactions.\n\nThe main differences are:\n● The trading peers need to exchange information about the meeting location and time by using their provided contact details.\n● The trading peers need to bring their laptops and do the confirmation of 'payment sent' and 'payment received' at the meeting place.\n● If a maker has special 'terms and conditions' they must state those in the 'Additional information' text field in the account.\n● By taking an offer the taker agrees to the maker's stated 'terms and conditions'.\n● In case of a dispute the arbitrator cannot help much as it is usually hard to get tamper proof evidence of what happened at the meeting. In such cases the BTC funds might get locked indefinitely or until the trading peers come to an agreement.\n\nTo be sure you fully understand the differences with 'Face to Face' trades please read the instructions and recommendations at: 'https://docs.bisq.network/trading-rules.html#f2f-trading' payment.f2f.info.openURL=Open web page payment.f2f.offerbook.tooltip.countryAndCity=County and city: {0} / {1} payment.f2f.offerbook.tooltip.extra=Additional information: {0} diff --git a/core/src/main/resources/i18n/displayStrings_ru.properties b/core/src/main/resources/i18n/displayStrings_ru.properties index d155957819..525fe1f430 100644 --- a/core/src/main/resources/i18n/displayStrings_ru.properties +++ b/core/src/main/resources/i18n/displayStrings_ru.properties @@ -299,9 +299,11 @@ market.trades.tooltip.candle.date=Дата: offerbook.createOffer=Создать предложение offerbook.takeOffer=Принять предложение +offerbook.takeOfferToBuy=Take offer to buy {0} +offerbook.takeOfferToSell=Take offer to sell {0} offerbook.trader=Трейдер -offerbook.offerersBankId=Идентификатор(BIC/SWIFT) банка создателя предложения: {0} -offerbook.offerersBankName=Название банка создателя предложения: {0} +offerbook.offerersBankId=Идент. банка (BIC/SWIFT) создателя: {0} +offerbook.offerersBankName=Название банка создателя: {0} offerbook.offerersBankSeat=Местоположение банка создателя предложения: {0} offerbook.offerersAcceptedBankSeatsEuro=Признанные страны банков (получателя): Все страны Еврозоны offerbook.offerersAcceptedBankSeats=Признанные страны банков (получателя):\n {0} @@ -357,7 +359,7 @@ createOffer.amount.prompt=Введите сумму в ВТС createOffer.price.prompt=Введите курс createOffer.volume.prompt=Введите сумму в {0} createOffer.amountPriceBox.amountDescription=Количество BTC {0} -createOffer.amountPriceBox.buy.volumeDescription=Сумма расхода в {0} +createOffer.amountPriceBox.buy.volumeDescription=Сумма расхода в {0} createOffer.amountPriceBox.sell.volumeDescription=Сумма поступления в {0} createOffer.amountPriceBox.minAmountDescription=Мин. количество ВТС createOffer.securityDeposit.prompt=Залоговый депозит в ВТС @@ -376,7 +378,7 @@ createOffer.info.buyBelowMarketPrice=Вы всегда заплатите {0}% createOffer.warning.sellBelowMarketPrice=Вы всегда получите {0}% меньше текущей рыночной цены, так как курс вашего предложения будет постоянно обновляться. createOffer.warning.buyAboveMarketPrice=Вы всегда заплатите {0}% больше текущей рыночной цены, так как курс вашего предложения будет постоянно обновляться. createOffer.tradeFee.descriptionBTCOnly=Торговый сбор -createOffer.tradeFee.descriptionBSQEnabled=Выбрать валюту сбора +createOffer.tradeFee.descriptionBSQEnabled=Выбрать валюту сбора за сделку createOffer.tradeFee.fiatAndPercent=≈ {0} / {1} от суммы сделки # new entries @@ -385,7 +387,7 @@ createOffer.alreadyFunded=Вы уже обеспечили это предлож createOffer.createOfferFundWalletInfo.headline=Обеспечить своё предложение # suppress inspection "TrailingSpacesInProperty" createOffer.createOfferFundWalletInfo.tradeAmount=- Сумма сделки: {0} \n -createOffer.createOfferFundWalletInfo.msg=Вы должны внести {0} для обеспечения этого предложения.\n\nЭти средства выделяются в Вашем локальном кошельке, и будут заперты в депозитном адресе multisig, когда кто-то примет Ваше предложение.\n\nСумма состоит из:\n{1}- Вашего залогового депозита: {2}\n- Торгового сбора: {3}\n- Общей комиссии майнера: {4}\n\n\nВы можете выбрать один из двух вариантов обеспечения сделки:\n - Использовать свой Bisq кошелёк (удобо, но связь между сделками может быть вычислена посторонними) ИЛИ\n - Перевод с внешнего кошелька (потенциально более анонимно)\n\nВы увидите все варианты обеспечения и подробности после закрытия этого окна. +createOffer.createOfferFundWalletInfo.msg=Вы должны внести {0} для обеспечения этого предложения.\n\nЭти средства зарезервированы в Вашем локальном кошельке, и будут заперты в депозитном адресе multisig, когда кто-то примет Ваше предложение.\n\nСумма состоит из:\n{1}- Вашего залогового депозита: {2}\n- Торгового сбора: {3}\n- Общей комиссии майнера: {4}\n\nВы можете выбрать один из двух вариантов финасирования сделки:\n - Использовать свой Bisq кошелёк (удобно, но связь между сделками может быть вычислена посторонними) ИЛИ\n - Перевести из внешнего кошелька (потенциально более анонимно)\n\nВы увидите все варианты обеспечения и подробности после закрытия этого окна. # only first part "An error occurred when placing the offer:" has been used before. We added now the rest (need update in existing translations!) createOffer.amountPriceBox.error.message=Сбой создания предложения:\n\n{0}\n\nВаши средства остались в кошельке.\nПросьба перезагрузить приложение и проверить связь с интернет. @@ -400,7 +402,7 @@ createOffer.resetToDefault=Нет, сбросить до значения по createOffer.useLowerValue=Да, использовать моё низшее значение createOffer.priceOutSideOfDeviation=Введенный курс превышает максимальное отклонение от рыночного.\nМаксимально дозволенное отклонение {0} и регулируется в настройках. createOffer.changePrice=Изменить курс -createOffer.tac=Опубликовав предложение, я согласен торговать с любым трейдером, совместимым по условиям обозначенным на экране. +createOffer.tac=Опубликовав предложение, я согласен торговать с любым трейдером, совместимым по условиям обозначенным на экране. createOffer.currencyForFee=Оплата сделки createOffer.setDeposit=Установить залоговый депозит покупателя @@ -437,7 +439,7 @@ takeOffer.alreadyFunded.movedFunds=Вы уже обеспечили это пр takeOffer.takeOfferFundWalletInfo.headline=Обеспечить Вашу сделку # suppress inspection "TrailingSpacesInProperty" takeOffer.takeOfferFundWalletInfo.tradeAmount=- Сумма сделки: {0} \n -takeOffer.takeOfferFundWalletInfo.msg=Для принятия этого предложения необходимо внести депозит {0}.\n\nДепозит является суммой:\n{1}\n- Вашего залогового депозита: {2}\n- Торгового сбора: {3}\n- Общей комиссии майнера: {4}\n\nВам можно выбрать из двух вариантов финансирования сделки:\n- Использовать свой Bisq кошелёк (удобно, но связь между сделками может быть вычислена посторонними) ИЛИ\n- Перевод из внешнего кошелька (потенциально более анонимно)\n\nВы увидите все варианты финансирования и подробности после закрытия этого окна. +takeOffer.takeOfferFundWalletInfo.msg=Для принятия этого предложения необходимо внести депозит {0}.\n\nДепозит является суммой:\n{1}- Вашего залогового депозита: {2}\n- Торгового сбора: {3}\n- Общей комиссии майнера: {4}\n\nВам можно выбрать из двух вариантов финансирования сделки:\n- Использовать свой Bisq кошелёк (удобно, но связь между сделками может быть вычислена посторонними) ИЛИ\n- Перевести из внешнего кошелька (потенциально более анонимно)\n\nВы увидите все варианты финансирования и подробности после закрытия этого окна. takeOffer.alreadyPaidInFunds=Если Вы уже внесли средства, их можно снять в разделе \"Средства/Отправить средства\". takeOffer.paymentInfo=Информация о платеже takeOffer.setAmountPrice=Задайте сумму @@ -527,7 +529,7 @@ portfolio.pending.step2_buyer.moneyGramMTCNInfo.msg=Вам необходимо portfolio.pending.step2_buyer.westernUnionMTCNInfo.headline=Отправить MTCN и квитанцию portfolio.pending.step2_buyer.westernUnionMTCNInfo.msg=Вам необходимо отправить по э-почте продавцу BTC MTCN (номер отслеживания) и фотографию квитанции.\nВ квитанции должно быть четко указано полное имя продавца, город, страна и сумма. Адрес э-почты продавца: {0}. \n\nВы отправили MTCN и контракт продавцу? portfolio.pending.step2_buyer.halCashInfo.headline=Послать код HalCash -portfolio.pending.step2_buyer.halCashInfo.msg=Отклонение в процентах от рыночной цены (например, 2.50%, -0.50% и т. д.) +portfolio.pending.step2_buyer.halCashInfo.msg=Вам нужно отправить сообщение с кодом HalCash и идентификатором сделки ({0}) к торговцу BTC.\nНомер мобильного тел. торговца {1}\n\nВы отправили код торговцу? portfolio.pending.step2_buyer.fasterPaymentsHolderNameInfo=Некоторые банки требуют имя получателя. Код сортировки Великобритании и номер счета достаточны для перевода Faster Payment, и имя получателя не проверяется ни одним из банков. portfolio.pending.step2_buyer.confirmStart.headline=Подтвердите начало платежа portfolio.pending.step2_buyer.confirmStart.msg=Вы начали {0} оплату Вашему контрагенту? @@ -535,7 +537,7 @@ portfolio.pending.step2_buyer.confirmStart.yes=Да, я начал оплату portfolio.pending.step2_seller.waitPayment.headline=Ожидайте платеж portfolio.pending.step2_seller.f2fInfo.headline=Контактная информация покупателя -portfolio.pending.step2_seller.waitPayment.msg=Поступило как минимум одно подтверждение депозита.\nВам необходимо ждать до тех пор когда покупатель BTC начнет оплату {0}. +portfolio.pending.step2_seller.waitPayment.msg=Поступило как минимум одно подтверждение транзакции депозита.\nВам необходимо ждать до тех пор когда покупатель BTC начнет оплату {0}. portfolio.pending.step2_seller.warn=Покупатель BTC все еще не завершил оплату {0}.\nВам необходимо ждать начала оплаты.\nЕсли сделка не завершилась {1}, арбитр начнет расследование. portfolio.pending.step2_seller.openForDispute=Покупатель BTC не приступил к оплате!\nМаксимальный срок сделки истёк.\nВы в праве подождать, и дать контрагенту больше времени, или связаться с арбитром и начать спор. @@ -562,11 +564,11 @@ portfolio.pending.step3_buyer.openForDispute=Продавец BTC не подт # suppress inspection "TrailingSpacesInProperty" portfolio.pending.step3_seller.part=Ваш контрагент подтвердил начало {0} оплаты.\n\n portfolio.pending.step3_seller.altcoin.explorer=на Вашем любимом обозревателе блокцепи {0} -portfolio.pending.step3_seller.altcoin.wallet=в Вашем кошельке {0} -portfolio.pending.step3_seller.altcoin={0}Проверьте {1} получила ли транзакция на Ваш адрес\n{2}\nдостаточно подтверждений блокципи.\nНеобходимая сумма платежа {3}\n\n Вы можете скопировать и вставить свой адрес {4} из главного окна после закрытия этого окна. +portfolio.pending.step3_seller.altcoin.wallet=в Вашем кошельке {0} +portfolio.pending.step3_seller.altcoin={0}Проверьте {1} получила ли транзакция на Ваш адрес\n{2}\nдостаточно подтверждений блокцепи.\nНеобходимая сумма платежа должна быть {3}\n\n Вы можете скопировать и вставить свой адрес {4} из главного окна после закрытия этого окна. portfolio.pending.step3_seller.postal={0}Просьба проверить, получили ли Вы {1} \"Почтового чека США\" от покупателя BTC.\n\nИдентификатор сделки (\"Назначение платежа\" текст) транзакции: \"{2}\" -portfolio.pending.step3_seller.bank=Ваш контрагент подтвердил, что начат платеж {0}.\n\nПросьба зайти на веб-страницу Вашего интернет-банка и проверить, получили ли Вы {1} от покупателя BTC.\n\nИдентификатор сделки (\"причина платежа \" текст) транзакции: \"{2}\"\n\n -portfolio.pending.step3_seller.cash=Так как оплата осуществляется наличными на счёт, покупатель BTC должен написать \"НЕ ПОДЛЕЖИТ ВОЗВРАТУ\" на квитанции, разорвать на 2 части, и послать Вам фото квитанции по э-почте.\n\nЧтоб исключить возвратный платёж, подтверждайте его только получив это фото, и если Вы уверенны, что квитанция действительна.\nЕсли Вы не уверенны, {0} +portfolio.pending.step3_seller.bank=Ваш контрагент подтвердил, что начат платеж {0}.\n\nПросьба зайти на веб-страницу Вашего интернет-банка и проверить, получили ли Вы {1} от покупателя BTC.\n\nИдентификатор сделки (\"причина платежа\" текст) транзакции: \"{2}\"\n\n +portfolio.pending.step3_seller.cash=Так как оплата осуществляется наличными на счёт, покупатель BTC должен написать \"НЕ ПОДЛЕЖИТ ВОЗВРАТУ\" на квитанции, разорвать на 2 части, и послать Вам фото квитанции по э-почте.\n\nЧтобы избежать возвратный платёж, подтверждайте его только получив это фото, и если Вы уверены, что квитанция действительна.\nЕсли Вы не уверены, {0} portfolio.pending.step3_seller.moneyGram=Покупатель обязан отправить Вам по электронной почте номер авторизации и фотографию квитанции.\nВ квитанции должно быть четко указано Ваше полное имя, страна, штат и сумма. Пожалуйста, проверьте свою электронную почту, и получение номера авторизации. \n\nПосле закрытия этого всплывающего окна Вы увидите имя и адрес покупателя BTC для получения денег от MoneyGram.\n\nПодтверждайте получение только после того как Вы успешно забрали деньги! portfolio.pending.step3_seller.westernUnion=Покупатель обязан отправить Вам по электронной почте MTCN (номер отслеживания) и фотографию квитанции.\nВ квитанции должно быть четко указано Ваше полное имя, город, страна и сумма. Пожалуйста, проверьте свою электронную почту, и получение MTCN.\n\nПосле закрытия этого всплывающего окна Вы увидите имя и адрес покупателя BTC для получения денег от Western Union. \n\nПодтверждайте получение только после того как Вы успешно забрали деньги! portfolio.pending.step3_seller.halCash=Покупатель должен отправить Вам код HalCash в текстовом сообщении. Кроме этого, Вы получите сообщение от HalCash с информацией, необходимой для снятия EUR в банкомате, поддерживающем HalCash.\n\nПосле того, как Вы забрали деньги из банкомата, просьба подтвердить здесь квитанцию об оплате! @@ -595,7 +597,7 @@ portfolio.pending.step3_seller.onPaymentReceived.fiat=Идентификатор portfolio.pending.step3_seller.onPaymentReceived.name=Просьба, удостоверьтесь, что имя отправителя в Вашем банковском отчете соответствует имени Вашего контрагента в сделке.:\nИмя отправителя: {0}\n\nЕсли имя не соответствует указанному здесь, просьба не подтверждать, а открыть спор, нажав "alt + o\" или \"option + o\".\n\n portfolio.pending.step3_seller.onPaymentReceived.note=Учтите, что как только Вы подтвердите получение оплаты, запертая сумма сделки будет отпущена покупателю BTC и залоговая сумма будет возвращена. portfolio.pending.step3_seller.onPaymentReceived.confirm.headline=Подтвердите, что вы получили платеж -portfolio.pending.step3_seller.onPaymentReceived.confirm.yes=Да, я получил платёж +portfolio.pending.step3_seller.onPaymentReceived.confirm.yes=Да, я получил(а) платёж portfolio.pending.step5_buyer.groupTitle=Итоги завершённой сделки portfolio.pending.step5_buyer.tradeFee=Торговый сбор @@ -676,7 +678,7 @@ funds.deposit.generateAddress=Создать новый адрес funds.deposit.selectUnused=Просьба выбрать неиспользованный адрес из таблицы выше, вместо создания нового. funds.withdrawal.arbitrationFee=Комиссия арбитра -funds.withdrawal.inputs=Выбор ресурсов +funds.withdrawal.inputs=Выбор ресурсов funds.withdrawal.useAllInputs=Использовать все доступные ресурсы funds.withdrawal.useCustomInputs=Использовать выбранные ресурсы funds.withdrawal.receiverAmount=Сумма получателя @@ -718,7 +720,7 @@ funds.tx.noFundsFromDispute=Без возмещения от спора funds.tx.receivedFunds=Полученные средства funds.tx.withdrawnFromWallet=Выведено из кошелька funds.tx.noTxAvailable=Транзакции недоступны -funds.tx.revert=Возврат +funds.tx.revert=Возвратить funds.tx.txSent=Транзакция успешно отправлена на новый адрес локального кошелька Bisq. funds.tx.direction.self=Транзакция внутри кошелька funds.tx.daoTxFee=Комиссия майнера за трансакцию DAO @@ -765,9 +767,9 @@ support.buyerOfferer=Покупатель ВТС/Создатель support.sellerOfferer=Продавец ВТС/Создатель support.buyerTaker=Покупатель ВТС/Получатель support.sellerTaker=Продавец BTC/Получатель -support.backgroundInfo=Bisq is not a company, so it handles disputes differently.\n\nIf there are disputes in the trade process (e.g. one trader does not follow the trade protocol) the application will display an \"Open dispute\" button after the trade period is over for contacting the arbitrator.\n\nIf there is an issue with the application, the software will try to detect it and, if possible, display an \"Open support ticket\" button to contact the arbitrator who will forward the issue to the developers.\n\nIf you are having an issue and did not see the \"Open support ticket\" button, you can open a support ticket manually by selecting the trade causing issues under \"Portfolio/Open trades\" and hitting \"alt + o\" or \"option + o\". Please use this method only if you are sure that the software is not working as expected. If you have problems or questions, please review the FAQ on the bisq.network web page or post in the Bisq forum in the Support section. +support.backgroundInfo=Bisq не является компанией, и поэтому справляется со спорами по другому.\n\n Если в процессе торговли возникают споры (напр. трейдер не соблюдает торговый протокол) приложение покажет кнопку \"Открыть спор\" для обращения к арбитру после окончания торгового срока.\n\nВ случае неполадок с приложением, оно попытается их обнаружить, и если это возможно, покажет кнопку \"Открыть билет поддержки\" чтобы связаться с арбитром который передаст проблему разработчикам. \n\nЕсли у Вас возникли проблемы и не появилась кнопка \"Открыть билет поддержки\", откройте его вручную выбрав данную сделку в разделе \"Папка/Текущие сделки\" и нажав \"alt + o\" или \"option + o\". Просьба использовать это только если Вы уверены что приложение не работает как следует. Если у Вас возникли проблемы или вопросы, просьба пересмотреть Часто Задаваемые Вопросы на странице bisq.network или спросить на Bisq форуме в разделе поддержки. -support.initialInfo=Учтите основные правила процесса рассмотрения спора:\n1. Вы обязаны ответитть на запросы арбитра в течении 2 дней.\n2. Максимальный срок отведенный на спор 14 дней.\n3. Вы обязаны содействовать арбитру, и предоставлять запрашиваемую информацию по Вашему делу.\n4. Вы согласились с правилами указанными в wiki в соглашении пользователя, когда первый раз запускали приложение.\n\nПросьба прочесть детали процесса спора в нашем wiki:\nhttps://github.com/bisq-network/exchange/wiki/Arbitration-system +support.initialInfo=Учтите основные правила процесса рассмотрения спора:\n1. Вы обязаны ответитть на запросы арбитра в течении 2 дней.\n2. Максимальный срок отведенный на спор: 14 дней.\n3. Вы обязаны содействовать арбитру, и предоставлять запрашиваемую информацию по Вашему делу.\n4. Вы согласились с правилами указанными в wiki в соглашении пользователя, когда первый раз запускали приложение.\n\nПросьба прочесть детали процесса спора в нашем wiki:\nhttps://github.com/bisq-network/exchange/wiki/Arbitration-system support.systemMsg=Системное сообщение: {0} support.youOpenedTicket=Вы открыли запрос поддержки. support.youOpenedDispute=Вы запросили начать спор.\n\n{0} @@ -790,7 +792,7 @@ setting.preferences.deviationToLarge=Значения выше 30 % не раз setting.preferences.txFee=Комиссия за снятие средств (сатоши/байт) setting.preferences.useCustomValue=Задать своё значение setting.preferences.txFeeMin=Комиссия транзакции должна быть хотя бы {0} сатоши/байт -setting.preferences.txFeeTooLarge=Введённый параметр слишком высок (>5000 сатоши/байт). Комиссия транзакции обычно намного ниже. +setting.preferences.txFeeTooLarge=Введённый параметр слишком высок (>5000 сатоши/байт). Комиссия транзакции обычно намного ниже, в пределе 50-400 сатоши/байт. setting.preferences.ignorePeers=Игнорировать трейдеров с onion-адресами (через запят.) setting.preferences.refererId=Реферальный идентификатор setting.preferences.refererId.prompt=Дополнительный реферальный идентификатор @@ -825,18 +827,18 @@ setting.preferences.dao.fullNodeInfo.cancel=Нет, останусь в режи settings.net.btcHeader=Сеть Биткойн settings.net.p2pHeader=Сеть Р2Р -settings.net.onionAddressLabel=Мой onion(Tor) адрес +settings.net.onionAddressLabel=Мой onion (Tor) адрес settings.net.btcNodesLabel=Использовать особые узлы Bitcoin Core settings.net.bitcoinPeersLabel=Подключенные пэры settings.net.useTorForBtcJLabel=Использовать Tor для сети Биткойн -settings.net.bitcoinNodesLabel=Подключиться к узлам Bitcoin Core +settings.net.bitcoinNodesLabel=Узлы Bitcoin Core для подключения settings.net.useProvidedNodesRadio=Использовать предоставленные узлы Bitcoin Core settings.net.usePublicNodesRadio=Использовать общедоступную сеть Bitcoin settings.net.useCustomNodesRadio=Использовать особые узлы Bitcoin Core settings.net.warn.usePublicNodes=Если Вы используете общедоступную сеть Bitcoin, Вы подвергаетесь серьезной угрозе конфиденциальности, вызванной несовершенным дизайном и реализацией фильтра bloom, который используется в кошельках SPV, таких как BitcoinJ (который используется в Bisq). Любой самостоятельный узел, к которому Вы подключены, может вычислить, что все Ваши адреса кошельков принадлежат одному лицу.\n\nПросьба осведомиться о подробностях на: https://bisq.network/blog/privacy-in-bitsquare.\n\nИспользовать общедоступные узлы? settings.net.warn.usePublicNodes.useProvided=Нет, использовать предусмотренные узлы settings.net.warn.usePublicNodes.usePublic=Да, использовать общедоступную сеть -settings.net.warn.useCustomNodes.B2XWarning=Просьба убедиться, что Ваш Биткойн узел является доверенным Bitcoin Core узлом! \n\nПодключение к узлам не следующим правилам консенсуса Bitcoin Core, может повредить Ваш кошелек и вызвать проблемы в процессе торговли.\n\nПользователи подключающиеся к узлам, нарушающим правила консенсуса, несут ответственность за любой причиненный ущерб. Вытекающие споры будут решаться в пользу контрагента. Никакая техническая поддержка не будет предоставлена пользователям, которые игнорируют это предупреждения и механизмы защиты! +settings.net.warn.useCustomNodes.B2XWarning=Просьба убедиться, что Ваш Биткойн узел является доверенным Bitcoin Core узлом! \n\nПодключение к узлам не следующим правилам консенсуса Bitcoin Core может повредить Ваш кошелек и вызвать проблемы в процессе торговли.\n\nПользователи подключающиеся к узлам, нарушающим правила консенсуса, несут ответственность за любой причиненный ущерб. Вытекающие споры будут решаться в пользу контрагента. Никакая техническая поддержка не будет предоставлена пользователям, которые игнорируют это предупреждения и механизмы защиты! settings.net.localhostBtcNodeInfo=(Справка: если Вы используете локальный узел Биткойн (localhost), Вы можете подключаться исключительно к нему.) settings.net.p2PPeersLabel=Подключенные пэры settings.net.onionAddressColumn=Onion/Tor адрес @@ -859,8 +861,8 @@ settings.net.peer=Пэр settings.net.inbound=входящий settings.net.outbound=выходящий settings.net.reSyncSPVChainLabel=Синхронизировать цепь SPV заново -settings.net.reSyncSPVChainButton=Удалить файл SPV и синхронизировать повторно -settings.net.reSyncSPVSuccess=Файл цепи SPV удалится при перезагрузке. Необходимо перезапустить приложение.\n\nПосле перезагрузки, потребуется некоторое время для повторной синхронизации с сетью и Вы увидите все транзакции только после её завершения.\n\nПросьба повторить перезагрузку после завершения повторной синхронизации, поскольку иногда возникают несоответствия, ведущие к неверному балансу. +settings.net.reSyncSPVChainButton=Удалить файл SPV и синхронизировать повторно +settings.net.reSyncSPVSuccess=Файл цепи SPV удалится при перезагрузке. Необходимо перезапустить приложение сейчас.\n\nПосле перезагрузки, потребуется некоторое время для повторной синхронизации с сетью и Вы увидите все транзакции только после её завершения.\n\nПросьба повторить перезагрузку после завершения повторной синхронизации, поскольку иногда возникают несоответствия, ведущие к неверному балансу. settings.net.reSyncSPVAfterRestart=Файл цепи SPV удален. Просьба потерпеть. Повторная синхронизации с сетью может занять некоторое время. settings.net.reSyncSPVAfterRestartCompleted=Повторная синхронизация завершена. Просьба перезагрузить приложение. settings.net.reSyncSPVFailed=Не удалось удалить файл цепи SPV.\nСбой: {0} @@ -892,7 +894,7 @@ setting.about.subsystems.val=Версия сети: {0}; Версия P2P соо account.tab.arbitratorRegistration=Регистрация арбитра account.tab.account=Счёт account.info.headline=Добро пожаловать в Ваш Bisq Счёт -account.info.msg=Here you can add trading accounts for national currencies & altcoins, select arbitrators, and create a backup of your wallet & account data.\n\nA new Bitcoin wallet was created the first time you started Bisq.\n\nWe strongly recommend that you write down your Bitcoin wallet seed words (see tab on the top) and consider adding a password before funding. Bitcoin deposits and withdrawals are managed in the \"Funds\" section.\n\nPrivacy & security note: because Bisq is a decentralized exchange, all your data is kept on your computer. There are no servers, so we have no access to your personal info, your funds, or even your IP address. Data such as bank account numbers, altcoin & Bitcoin addresses, etc are only shared with your trading partner to fulfill trades you initiate (in case of a dispute the arbitrator will see the same data as your trading peer). +account.info.msg=Здесь можно добавить свои торговые счета для нац. валют и алткойнов, выбрать арбитров, создать резервные копии своего кошелька и данных счетов.\n\nНовый кошелёк Биткойн был создан, когда Вы впервые запустили Bisq.\nНастоятельно рекомендуем Вам записать кодовые слова кошелька (смотрите вкладку вверху) и добавить пароль до ввода средств. Ввод и вывод биткойнов проводят в разделе \"Средства\".\n\nО безопасности и конфиденциальности:\nТак как Bisq - децентрализованный обменник, Ваши данные хранятся только на Вашем компьютере. Серверов нет, и нам не доступы Ваши личные данные, средства и даже IP адрес. Данные, как номера банковских счетов, адреса электронных кошельков, итп, сообщаются только Вашему контрагенту для обеспечения Ваших сделок (в случае спора, арбитр увидит те же данные, что и контрагент). account.menu.paymentAccount=Счета в нац. валюте account.menu.altCoinsAccountView=Алткойн-счета @@ -926,10 +928,10 @@ account.arbitratorSelection.minOne=Необходимо выбрать хотя account.altcoin.yourAltcoinAccounts=Ваши алткойн-счета account.altcoin.popup.wallet.msg=Убедитесь, что соблюдаете требования пользования кошельками {0}, описанных на веб-странице {1}.\nИспользование кошельков централизованных обменников рискованно, где (а) Ваши ключи не под Вашим контролем, или (б) используют несовместимый кошелёк; может привести к потере Ваших торговых средств!\nАрбитр не является специалистом {2} и не может помочь в таких случаях. account.altcoin.popup.wallet.confirm=Я понимаю и подтверждаю, что знаю какой кошелёк нужно использовать. -account.altcoin.popup.xmr.msg=Для обмена XMR на Bisq, просьба понять и следовать следующим правилам:\n\nДля отправления XMR необходимы кошельки официальный Monero GUI или Monero CLI с включённым флажком store-tx-info (в новейших версиях по умолчанию). Удостоверьтесь, что доступен ключ транзакций необходимый в случае спора.\nmonero-wallet-cli (используйте команду get_tx_key)\nmonero-wallet-gui (перейдите в раздел history и нажмите на кнопку (P) для подтверждения оплаты)\n\n В дополнение к инструменту проверки XMR (https://xmr.llcoins.net/checktx.html), верификация также может быть выполнена в кошельке.\nmonero-wallet-cli: используя команду (check_tx_key).\nmonero-wallet-gui: разделе Advanced > Prove/Check.\nОбычным исследователем блоков переводы не проверяются.\n\nЕсли возникнет спора, арбитру потребуются от Вас следующие данные:\n- Ключ транзакции\n- Хэш(hash) транзакции\n- Публичный адрес получателя\n\nЕсли Вы не предоставите эти данные, либо используете несоответствующие кошельки, Вы проиграете спор. Посылающий XMR ответственен перед арбитром за подтверждение перевода XMR в случае спора.\n\nИдентификатор оплаты не нужен - только нормальный публичный адрес.\nЕсли Вам не знаком этот процесс, посетите (https://www.getmonero.org/resources/user-guides/prove-payment.html) или осведомитесь на форуме Monero (https://forum.getmonero.org). -account.altcoin.popup.blur.msg=Если вы хотите торговать BLUR на Bisq, вам нужно понять и выполнить следующие требования:\n\nЧтобы послать BLUR, вы должны использовать кошелёк Blur Network CLI или кошелёк GUI.\n\nЕсли вы используете кошелёк CLI, хэш сделки (tx ID) будет показан после отправки перевoда. Вы должны сохранить эту информацию. Немедленно после отправки перевода, используйте команду 'get_tx_key' для получения секретного ключа сделки. Если вы не выполните этот акт, вы не сможете получить ключ позже.\n\nЕсли вы используете кошелёк Blur Network GUI, вы можете найти частный ключ и идентификацию (ID) сделки во вкладке "История". Немедленно после отправки, найдите интересуемую сделку. Нажмите на символ "?" в нижне-правом углу окна содержащего сделку. Вы должны сохранить эту информацию.\n\nВ случае необходимости арбитража, вы должны предоставить следующее арбитру: 1.) идентификацию (ID) сделки, 2.) частный ключ сделки, и 3.) адрес получателя. Арбитр затем проверит перевод BLUR пользуясь Просмотрщиком сделок Blur или Blur Transaction Viewer (https://blur.cash/#tx-viewer).\n\nЕсли вы не сможете предоставить требованную информацию арбитру, вы проиграете спор. Во всех случаях спора, отправитель несёт 100% ответственности за подтверждение сделок арбитру.\n\nЕсли вы не понимаете эти требования, не торгуйте на Bisq. Сначала, ищите помощь в Споре Сети Blur или Blur Network Discord (https://discord.gg/dMWaqVW). -account.altcoin.popup.ccx.msg=Если Вы хотите торговать CCX на Bisq, просьба убедиться, что Вы понимаете следующие требования:\n\nДля отправки ccx вы должны использовать официальный кошелек - либо CLI, либо GUI. После отправки перевода, кошельки\nпоказывают секретный ключ транзакции. Вы должны сохранить его вместе с хэшем транзакции (ID) и общедоступным\nадресом получателя на случай возникновения спора. В таком случае Вы должны предоставить все три арбитру,\nдля проверки перевода CCX с помощью Обозревателя Скрытых Транзакций (https://explorer.скрывать.network/txviewer).\nТак как Conceal монета конфиденциальности, блок обозреватели не могут проверить переводы.\n\nЕсли Вы не сможете предоставить необходимые данные арбитру, Вы проиграете спор.\nЕсли Вы не сохраните секретный ключ транзакции сразу после передачи CCX, его нельзя будет восстановить позже.\nЕсли Вы не понимаете этих требований, обратитесь за помощью в Conceal discord (http://discord.conceal.network). -account.altcoin.popup.drgl.msg=\nЧтобы торговать Dragonglass на Bisq, вы должны понять и выполнить следующие треобования:\n\nТак как Dragonglass предоставляет конфиденциальность, сделку невозможно подтвердить в общественном блокчейне. Вам необходимо доказать вашу оплату пользуясь вашим частным ключом TXN (TXN-Private-Key).\nЧастный ключ TXN - это одноразовый ключ который автоматически создан при каждой сделке и только доступен изнутри вашего кошелька DRGL.\nИли через GUI (графический интерфейс пользователя) кошелька DRGL (внутри диалога деталей сделок) или через Dragonglass CLI simplewallet (пользуясь командой "get_tx_key").\n\nДля обоих НЕОБХОДИМЫ версия DRGL "Oathkeeper" и новее.\n\nВ случае спора, вы должны предоставить следующую информацию арбитру: \n- Частный ключ TXN\n- Хэш сделки\n- Публичный адрес получателя\n\nПодтверждение оплаты может быть выполнено используя приведённые выше данные в качестве входных данных в (http://drgl.info/#check_txn). \n\nЕсли вы не можете предоставить приведённые выше данные или вы использовали несовместимый кошелёк, это приведёт к потере спора. Отправитель Dragonglass имеет ответственность за подтвердение перевода DRGL арбитру в случае спора. Использование PaymentID не требуется.\n\nЕсли вы не уверены в какой-либо части этого процесса, посетите Dragonglass о споре (http://discord.drgl.info) для услуг. +account.altcoin.popup.xmr.msg=Для торговли XMR на Bisq, Вам необходимо понять и следовать следующим требованиям:\n\nДля отправления XMR, необходимы официальные кошельки Monero GUI или Monero CLI с включённым флажком store-tx-info (включено в новых версиях). Удостоверьтесь, что Вам доступен ключ транзакций, необходимый в случае спора.\nmonero-wallet-cli (используйте команду get_tx_key)\nmonero-wallet-gui (перейдите в раздел history и нажмите на кнопку (P) для подтверждения оплаты)\n\n В дополнение к инструменту проверки XMR (https://xmr.llcoins.net/checktx.html), верификация также может быть выполнена в кошельке.\nmonero-wallet-cli: используя команду (check_tx_key).\nmonero-wallet-gui: разделе Advanced > Prove/Check.\nПереводы не проверяются обычными исследователями блоков.\n\nЕсли возникнет спор, арбитру потребуются от Вас следующие данные:\n- Личный ключ транзакции\n- Хеш(hash) транзакции\n- Публичный адрес получателя\n\nЕсли Вы не предоставите эти данные, либо используете несоответствующие кошельки, Вы проиграете спор. Посылающий XMR ответственен перед арбитром за подтверждение перевода XMR в случае спора.\n\nИдентификатор оплаты не нужен - только обычный публичный адрес.\nЕсли Вам не знаком этот процесс, посетите (https://www.getmonero.org/resources/user-guides/prove-payment.html) или осведомитесь на форуме Monero (https://forum.getmonero.org). +account.altcoin.popup.blur.msg=Trading BLUR on Bisq requires that you understand and fulfill the following requirements:\n\nTo send BLUR you must use the Blur Network CLI or GUI Wallet. \n\nIf you are using the CLI wallet, a transaction hash (tx ID) will be displayed after a transfer is sent. You must save this information. Immediately after sending the transfer, you must use the command 'get_tx_key' to retrieve the transaction private key. If you fail to perform this step, you may not be able to retrieve the key later. \n\nIf you are using the Blur Network GUI Wallet, the transaction private key and transaction ID can be found conveniently in the "History" tab. Immediately after sending, locate the transaction of interest. Click the "?" symbol in the lower-right corner of the box containing the transaction. You must save this information. \n\nIn the event that arbitration is necessary, you must present the following to an arbitrator: 1.) the transaction ID, 2.) the transaction private key, and 3.) the recipient's address. The arbitrator will then verify the BLUR transfer using the Blur Transaction Viewer (https://blur.cash/#tx-viewer).\n\nFailure to provide the required information to the arbitrator will result in losing the dispute case. In all cases of dispute, the BLUR sender bears 100% of the burden of responsibility in verifying transactions to an arbitrator. \n\nIf you do not understand these requirements, do not trade on Bisq. First, seek help at the Blur Network Discord (https://discord.gg/dMWaqVW). +account.altcoin.popup.ccx.msg=Trading CCX on Bisq requires that you understand the following requirements:\n\nTo send CCX you must use an official Conceal wallet, either CLI or GUI. After sending a transfer payment, the wallets\ndisplay the transaction secret key. You must save it along with the transaction hash (ID) and the recipient's public\naddress in case arbitration is necessary. In such a case, you must give all three to the arbitrator, who will then\nverify the CCX transfer using the Conceal Transaction Viewer (https://explorer.conceal.network/txviewer).\nBecause Conceal is a privacy coin, block explorers cannot verify transfers.\n\nFailure to provide the required data to the arbitrator will result in losing the dispute case.\nIf you do not save the transaction secret key immediately after transferring CCX, it cannot be recovered later.\nIf you do not understand these requirements, seek help at the Conceal discord (http://discord.conceal.network). +account.altcoin.popup.drgl.msg=Trading Dragonglass on Bisq requires that you understand and fulfill the following requirements:\n\nBecause of the privacy Dragonglass provides, a transaction is not verifiable on the public blockchain. If required, you can prove your payment through the use of your TXN-Private-Key.\nThe TXN-Private Key is a one-time key automatically generated for every transaction that can only be accessed from within your DRGL wallet.\nEither by DRGL-wallet GUI (inside transaction details dialog) or by the Dragonglass CLI simplewallet (using command "get_tx_key").\n\nDRGL version 'Oathkeeper' and higher are REQUIRED for both.\n\nIn case of a dispute, you must provide the arbitrator the following data:\n- The TXN-Private key\n- The transaction hash\n- The recipient's public address\n\nVerification of payment can be made using the above data as inputs at (http://drgl.info/#check_txn).\n\nFailure to provide the above data, or if you used an incompatible wallet, will result in losing the dispute case. The Dragonglass sender is responsible for providing verification of the DRGL transfer to the arbitrator in case of a dispute. Use of PaymentID is not required.\n\nIf you are unsure about any part of this process, visit Dragonglass on Discord (http://discord.drgl.info) for help. account.altcoin.popup.ZEC.msg=При использовании {0} допустимо использовать только прозрачные адреса (начиная с t) а не z-адреса (личные), потому что арбитр не сможет проверить транзакцию с z-адресами. account.altcoin.popup.XZC.msg=При использовании {0} можно использовать только прозрачные (отслеживаемые) адреса, а не неотслеживаемые адреса, поскольку арбитр не сможет проверить транзакцию с неотслеживаемыми адресами в обозревателе блоков цепи / вlockchain. account.altcoin.popup.bch=Bitcoin Cash и Bitcoin Classic страдают отсутствием защиты воспроизведения. Если вы используете эти монеты, убедитесь, что вы принимаете достаточные меры предосторожности и понимаете все последствия. Возможно понести убытки, отправив одну монету и непреднамеренно отправить те же монеты на другую блокцепь. Поскольку эти монеты были выпущены процессом "airdrop" и разделяют исторические данные с блокчейном Биткойн, существует также риск безопасности и значительный риск потери конфиденциальности. \n\nПросьба прочесть подробнее на форуме Bisq: https://forum.bisq.io/t/airdrop-coins-information-thread-bch-btg-bchc @@ -1006,8 +1008,8 @@ account.notifications.marketAlert.offerType.label=Тип предложения account.notifications.marketAlert.offerType.buy=Предложения купить (хочу продать BTC) account.notifications.marketAlert.offerType.sell=Предложения продать (хочу купить BTC) account.notifications.marketAlert.trigger=Отклонение курса предложения (%) -account.notifications.marketAlert.trigger.info=Если задано отклонение от цены, Вы получите оповещение только когда предложение соответствует (или превышает) Вашим требованиям. Пример: Вы хотите продать BTC, но только с надбавкой 2% к текущей рыночной цене. Указав 2% в этом поле, Вы получите оповещение только от предложений с ценами, которые на 2% (или более) выше текущей рыночной цены. -account.notifications.marketAlert.trigger.prompt=Отклонение в процентах от рыночной цены (например, 2.50%, -0.50% и т. д.) +account.notifications.marketAlert.trigger.info=Если задано отклонение от цены, Вы получите оповещение только когда предложение соответствует (или превышает) Вашим требованиям. Пример: Вы хотите продать BTC, но только с надбавкой 2% к текущей рыночной цене. Указав 2% в этом поле, Вы получите оповещение только от предложений с ценами, которые на 2% (или более) выше текущей рыночной цены. +account.notifications.marketAlert.trigger.prompt=Отклонение в процентах от рыночной цены (напр. 2.50%, -0.50% и т. д.) account.notifications.marketAlert.addButton=Добавить оповещение о предложении account.notifications.marketAlert.manageAlertsButton=Управление оповещениями о предложениях account.notifications.marketAlert.manageAlerts.title=Управление оповещениями о предложениях @@ -1021,7 +1023,7 @@ account.notifications.marketAlert.message.msg.below=ниже account.notifications.marketAlert.message.msg.above=выше account.notifications.marketAlert.message.msg=Новое предложение "{0} {1} " с ценой {2} ({3} {4} рыночная цена) и способом оплаты "{5}" было опубликовано в книге предложений Bisq.\nИдент. предложения: {6}. account.notifications.priceAlert.message.title=Оповещение о цене для {0} -account.notifications.priceAlert.message.msg=Ваше оповещение о цене сработало. Текущая цена {0} {1} {2} +account.notifications.priceAlert.message.msg=Ваше оповещение о цене сработало. Текущая {0} цена {1} {2} account.notifications.noWebCamFound.warning=Веб-камера не найдена.\n\nПросьба применить э-почту для отправки токена и ключа шифрования с Вашего мобильного телефона на приложение Bisq. account.notifications.priceAlert.warning.highPriceTooLow=Более высокая цена должна быть больше чем более низкая цена. account.notifications.priceAlert.warning.lowerPriceTooHigh=Нижняя цена должна быть ниже чем более высокая цена. @@ -1059,7 +1061,7 @@ dao.cycle.proposal=Этап предложения dao.cycle.blindVote=Этап слепого голосования dao.cycle.voteReveal=Этап выявления голосов dao.cycle.voteResult=Результат голосования -dao.cycle.phaseDuration={0} блока (≈{1}); Блок {2} - {3} (≈{4} - ≈{5}) +dao.cycle.phaseDuration={0} блоков (≈{1}); Блок {2} - {3} (≈{4} - ≈{5}) dao.results.cycles.header=Цыклы dao.results.cycles.table.header.cycle=Цыкл @@ -1106,11 +1108,11 @@ dao.param.PROPOSAL_FEE=Сбор BSQ за предложение dao.param.BLIND_VOTE_FEE=Сбор BSQ за голосование # suppress inspection "UnusedProperty" -dao.param.COMPENSATION_REQUEST_MIN_AMOUNT=Мин. сумма запроса BSQ компенсации +dao.param.COMPENSATION_REQUEST_MIN_AMOUNT=Мин. сумма запроса BSQ компенсации # suppress inspection "UnusedProperty" -dao.param.COMPENSATION_REQUEST_MAX_AMOUNT=Макс. сумма запроса BSQ компенсации +dao.param.COMPENSATION_REQUEST_MAX_AMOUNT=Макс. сумма запроса BSQ компенсации # suppress inspection "UnusedProperty" -dao.param.REIMBURSEMENT_MIN_AMOUNT=Мин. сумма запроса BSQ возмещения +dao.param.REIMBURSEMENT_MIN_AMOUNT=Мин. сумма запроса BSQ возмещения # suppress inspection "UnusedProperty" dao.param.REIMBURSEMENT_MAX_AMOUNT=Макс. сумма запроса BSQ возмещения @@ -1200,7 +1202,7 @@ dao.bond.reputation.table.header=Мои залоговые депозиты ре dao.bond.reputation.amount=Запереть BSQ на сумму dao.bond.reputation.time=Срок разблокировки в блоках dao.bond.reputation.salt=Соль -dao.bond.reputation.hash=Хэш +dao.bond.reputation.hash=Хеш dao.bond.reputation.lockupButton=Запереть dao.bond.reputation.lockup.headline=Подтвердить транзакцию блокировки dao.bond.reputation.lockup.details=Запереть сумму: {0}\nВремя блокировки: {1} блок(ов) \n\nДействительно желаете продолжить? @@ -1224,7 +1226,7 @@ dao.bond.table.column.name=Имя dao.bond.table.column.link=Ссылка dao.bond.table.column.bondType=Тип гарантийного депозита dao.bond.table.column.details=Подробности -dao.bond.table.column.lockupTxId=Транз. идент. блокировки +dao.bond.table.column.lockupTxId=Идент. транз. блокировки dao.bond.table.column.bondState=Состояние гарантийного депозита dao.bond.table.column.lockTime=Время блокировки dao.bond.table.column.lockupDate=Дата блокировки @@ -1290,10 +1292,10 @@ dao.bond.bondedRoleType.MEDIATOR=Посредник # suppress inspection "UnusedProperty" dao.bond.bondedRoleType.ARBITRATOR=Арбитр -dao.burnBsq.assetFee=Сбор за листинг астива -dao.burnBsq.menuItem.assetFee=Сбор за листинг астива +dao.burnBsq.assetFee=Сбор за листинг актива +dao.burnBsq.menuItem.assetFee=Сбор за листинг актива dao.burnBsq.menuItem.proofOfBurn=Proof of burn -dao.burnBsq.header=Сбор за листинг астива +dao.burnBsq.header=Сбор за листинг актива dao.burnBsq.selectAsset=Выбрать актив dao.burnBsq.fee=Сбор dao.burnBsq.trialPeriod=Испытательный срок @@ -1306,7 +1308,7 @@ dao.burnBsq.assets.lookBackPeriod=Период проверки dao.burnBsq.assets.trialFee=Сбор за испытательный срок dao.burnBsq.assets.totalFee=Итого уплачен сбор dao.burnBsq.assets.days={0} дней -dao.burnBsq.assets.toFewDays=Сбор за актив слишком низок. Мин. количество дней пробного периода {0}. +dao.burnBsq.assets.toFewDays=Взнос за актив слишком низок. Мин. количество дней пробного периода {0}. # suppress inspection "UnusedProperty" dao.assetState.UNDEFINED=Неопределено @@ -1322,11 +1324,11 @@ dao.assetState.REMOVED_BY_VOTING=Удалён голосованием dao.proofOfBurn.header=Proof of burn dao.proofOfBurn.amount=Количество dao.proofOfBurn.preImage=Pre-image -dao.proofOfСжечь.burn=Сжечь +dao.proofOfBurn.burn=Сжечь dao.proofOfBurn.allTxs=Все транзакции proof of burn dao.proofOfBurn.myItems=Мои транзакции proof of burn dao.proofOfBurn.date=Дата -dao.proofOfBurn.hash=Хэш +dao.proofOfBurn.hash=Хеш dao.proofOfBurn.txs=Транзакции dao.proofOfBurn.pubKey=Общедоступный ключ dao.proofOfBurn.signature.window.title=Подписать сообщение ключом из транзакции proof or burn @@ -1362,7 +1364,7 @@ dao.phase.separatedPhaseBar.PROPOSAL=Этап предложения # suppress inspection "UnusedProperty" dao.phase.separatedPhaseBar.BLIND_VOTE=Слепое голосование # suppress inspection "UnusedProperty" -dao.phase.separatedPhaseBar.VOTE_REVEAL=Показать голосование +dao.phase.separatedPhaseBar.VOTE_REVEAL=Показать голосование # suppress inspection "UnusedProperty" dao.phase.separatedPhaseBar.RESULT=Результат голосования @@ -1408,8 +1410,8 @@ dao.proposal.myVote.reject=Отклонить предложение dao.proposal.myVote.removeMyVote=Игнорировать предложение dao.proposal.myVote.merit=Вес голоса от заслуженного BSQ dao.proposal.myVote.stake=Вес голоса от доли -dao.proposal.myVote.blindVoteTxId=Транз. идент. слепого голосования -dao.proposal.myVote.revealTxId=Транз. идент. выявления голоса +dao.proposal.myVote.blindVoteTxId=Идент. транзакции слепого голосования +dao.proposal.myVote.revealTxId=Идент. транзакции выявления голоса dao.proposal.myVote.stake.prompt=Макс. доступный баланс для голосования: {0} dao.proposal.votes.header=Голосование по всем предложениям dao.proposal.votes.header.voted=Мой голос @@ -1423,16 +1425,16 @@ dao.proposal.display.type=Тип предложения dao.proposal.display.name=Имя/ник dao.proposal.display.link=Ссылка на подробности dao.proposal.display.link.prompt=Ссылка о неисправности на Github -dao.proposal.display.requestedBsq=Запрос средств в BSQ +dao.proposal.display.requestedBsq=Запрашиваемая сумма в BSQ dao.proposal.display.bsqAddress=BSQ-адрес -dao.proposal.display.txId= Идент. транз. предложения +dao.proposal.display.txId=Идент. транзакции предложения dao.proposal.display.proposalFee=Сбор за предложение dao.proposal.display.myVote=Мой голос dao.proposal.display.voteResult=Сводка итогов голосования dao.proposal.display.bondedRoleComboBox.label=Тип обеспеченной роли dao.proposal.display.requiredBondForRole.label=Необходимый гарантийный депозит роли dao.proposal.display.tickerSymbol.label=Тикер -dao.proposal.display.option=Параметр +dao.proposal.display.option=Вариант dao.proposal.table.header.proposalType=Тип предложения dao.proposal.table.header.link=Ссылка @@ -1459,7 +1461,7 @@ dao.proposal.display.assetComboBox.label=Актив для удаления dao.blindVote=слепое голосование dao.blindVote.startPublishing=Транзакция слепого голосования публикуется... -dao.blindVote.success=Ваша транзакция слепого голосования успешно опубликована. +dao.blindVote.success=Ваш слепой голос успешно опубликован. dao.wallet.menuItem.send=Послать dao.wallet.menuItem.receive=Получить @@ -1469,11 +1471,11 @@ dao.wallet.dashboard.myBalance=Баланс моего кошелька dao.wallet.dashboard.distribution=Распределение всего BSQ dao.wallet.dashboard.locked=Глобальное состояние запертого BSQ dao.wallet.dashboard.market=Данные рынка -dao.wallet.dashboard.genesis=Genesis транзакция +dao.wallet.dashboard.genesis=Исходная транзакция dao.wallet.dashboard.txDetails=Статистика транзакций BSQ dao.wallet.dashboard.genesisBlockHeight=Номер исходного блока dao.wallet.dashboard.genesisTxId=Идент. исходной транзакции -dao.wallet.dashboard.genesisIssueAmount=BSQ выданные в исходной транзакции +dao.wallet.dashboard.genesisIssueAmount=BSQ выданные в исходной транзакции dao.wallet.dashboard.compRequestIssueAmount=BSQ выданные на запросы компенсации dao.wallet.dashboard.reimbursementAmount=BSQ выданные на запросы возмещения dao.wallet.dashboard.availableAmount=Итого доступных BSQ @@ -1482,7 +1484,7 @@ dao.wallet.dashboard.totalLockedUpAmount=Заперто в гарантийны dao.wallet.dashboard.totalUnlockingAmount=Разблокировка BSQ из гарантийных депозитов dao.wallet.dashboard.totalUnlockedAmount=BSQ разблокировано из гарантийных депозитов dao.wallet.dashboard.totalConfiscatedAmount=BSQ конфисковано из гарантийных депозитов -dao.wallet.dashboard.allTx=Общее число транзакции BSQ +dao.wallet.dashboard.allTx=Общее количество транзакций BSQ dao.wallet.dashboard.utxo=Общее кол-во неизрасходованных (UTXO) dao.wallet.dashboard.compensationIssuanceTx=Общее кол-во транзакций выдачи запроса компенсации dao.wallet.dashboard.reimbursementIssuanceTx=Общее кол-во транзакций выдачи запроса возмещения @@ -1535,13 +1537,13 @@ dao.tx.type.enum.PROPOSAL=Сбор за предложение # suppress inspection "UnusedProperty" dao.tx.type.enum.BLIND_VOTE=Сбор за голосование вслепую # suppress inspection "UnusedProperty" -dao.tx.type.enum.VOTE_REVEAL=Показать голосование +dao.tx.type.enum.VOTE_REVEAL=Показать голосование # suppress inspection "UnusedProperty" dao.tx.type.enum.LOCKUP=Запереть гарантийный депозит # suppress inspection "UnusedProperty" dao.tx.type.enum.UNLOCK=Отпереть гарантийный депозит # suppress inspection "UnusedProperty" -dao.tx.type.enum.ASSET_LISTING_FEE=Сбор за листинг астива +dao.tx.type.enum.ASSET_LISTING_FEE=Сбор за листинг актива # suppress inspection "UnusedProperty" dao.tx.type.enum.PROOF_OF_BURN=Proof of burn @@ -1582,9 +1584,9 @@ displayUpdateDownloadWindow.download.failed=Сбой загрузки.\nПожа displayUpdateDownloadWindow.installer.failed=Не удалось определить правильный установщик. Пожалуйста, скачайте и проверьте вручную на https://bisq.network/downloads displayUpdateDownloadWindow.verify.failed=Проверка не удалась.\nПожалуйста, скачайте и проверьте вручную на https://bisq.network/downloads displayUpdateDownloadWindow.success=Новая версия успешно скачалась и подпись проверена.\n\nПожалуйста, откройте директорию загрузки, закройте приложение и установите новую версию. -displayUpdateDownloadWindow.download.openDir=Открыть директорию для загрузки +displayUpdateDownloadWindow.download.openDir=Открыть директорию для загрузки -disputeСводкаWindow.title=Сводка +disputeSummaryWindow.title=Сводка disputeSummaryWindow.openDate=Дата открытия билета поддержки disputeSummaryWindow.role=Роль трейдера disputeSummaryWindow.evidence=Доказательство @@ -1592,8 +1594,8 @@ disputeSummaryWindow.evidence.tamperProof=Подтверждение доказ disputeSummaryWindow.evidence.id=Проверка идентификации disputeSummaryWindow.evidence.video=Видео/Экранная демонстрация disputeSummaryWindow.payout=Выплата суммы сделки -disputeSummaryWindow.payout.getsTradeAmount=BTC {0} получение выплаты суммы сделки -disputeSummaryWindow.payout.getsAll=BTC {0} Получить всё +disputeSummaryWindow.payout.getsTradeAmount=BTC {0} получит выплату суммы сделки +disputeSummaryWindow.payout.getsAll=BTC {0} получит всё disputeSummaryWindow.payout.custom=Пользовательская выплата disputeSummaryWindow.payout.adjustAmount=Введенная сумма превышает доступное количество {0}. \nМы введём максимально возможное значение. disputeSummaryWindow.payoutAmount.buyer=Сумма выплаты покупателю @@ -1610,7 +1612,7 @@ disputeSummaryWindow.reason.bank=Банк disputeSummaryWindow.summaryNotes=Краткие заметки disputeSummaryWindow.addSummaryNotes=Добавить краткие заметки disputeSummaryWindow.close.button=Закрыть билет поддержки -disputeSummaryWindow.close.msg=Билет поддержки закрыт {0}\n\nИтог:\n{1} представил защищённое от подделки доказательство: {2}\n{3} подтвердил личность: {4}\n{5} сделал видео или скринкаст: {6}\nСумма выплаты покупателю BTC: {7}\nСумма выплаты продавцу BTC {8}\n\nЗаметки:\n{9} +disputeSummaryWindow.close.msg=Билет поддержки закрыт {0}\n\nИтог:\n{1} предoставил(a) защищённое от подделки доказательство: {2}\n{3} подтвердил(a) личность: {4}\n{5} сделал(a) видео или скринкаст: {6}\nСумма выплаты покупателю BTC: {7}\nСумма выплаты продавцу BTC {8}\n\nЗаметки:\n{9} disputeSummaryWindow.close.closePeer=Вам необходимо также закрыть билет контрагента! emptyWalletWindow.headline={0} аварийный инструмент кошелька @@ -1663,7 +1665,7 @@ qRCodeWindow.request=Запрос платежа:\n{0} selectDepositTxWindow.headline=Выберите транзакцию ввода средств для включения в спор selectDepositTxWindow.msg=Транзакция перевода на счет не сохраненилась в сделке.\nВыберите в своём кошельке одну из существующих транзакций типа multisig перевода на счет, использованной в неудавшейся сделке.\n\nМожно найти правильную транзакцию, открыв окно сведений о сделке (щелкните на идентификаторе торговли в списке) и после вывода транзакции с оплатой сделки на следующую транзакцию, где вы увидите мультиподписную транзакцию перевода на счет (адрес начинается с 3). Этот идентификатор транзакции должен быть виден в представленном здесь списке. После того, как найдёте правильную транзакцию, выберите эту транзакцию тут и продолжайте.\n\nИзвините за неудобство. Такие сбои редки, и мы попытаемся улучшить способы решения. -selectDepositTxWindow.select=Выберите транзакцию положить на счёт +selectDepositTxWindow.select=Выберите транзакцию депозита selectBaseCurrencyWindow.headline=Выбор рынка selectBaseCurrencyWindow.msg=Выбранный рынок по умолчанию - {0}.\n\nЕсли желаете изменить базовую валюту, выберите её в раскрывающемся списке.\nТакже возможно изменить базовую валюту в разделе \"Настройки/Информация сети\". @@ -1683,7 +1685,7 @@ sendPrivateNotificationWindow.enterNotification=Введите уведомле sendPrivateNotificationWindow.send=Отправить личное уведомление showWalletDataWindow.walletData=Данные кошелька -showWalletDataWindow.includePrivKeys=Добавить личные ключи +showWalletDataWindow.includePrivKeys=Включить личные ключи # We do not translate the tac because of the legal nature. We would need translations checked by lawyers # in each language which is too expensive atm. @@ -1720,7 +1722,7 @@ torNetworkSettingWindow.deleteFiles.button=Удалить устаревшие torNetworkSettingWindow.deleteFiles.progress=Tor завершает работу torNetworkSettingWindow.deleteFiles.success=Устаревшие файлы Tor успешно удалены. Пожалуйста, перезапустите приложение. torNetworkSettingWindow.bridges.header=Tor сеть заблокирована? -torNetworkSettingWindow.bridges.info=Если Tor заблокирована Вашим интернет-провайдером или страной, попробуйте использовать Tor bridges.\nПосетите веб-страницу Tor по адресу: https://bridges.torproject.org/bridges чтобы узнать больше о bridges и pluggable transports. +torNetworkSettingWindow.bridges.info=Если Tor заблокирован Вашим интернет-провайдером или страной, попробуйте использовать мосты Tor (bridges).\nПосетите веб-страницу Tor по адресу: https://bridges.torproject.org/bridges чтобы узнать больше о мостах и подключаемых транспортах. feeOptionWindow.headline=Выберите валюту для оплаты торгового сбора feeOptionWindow.info=Вы можете оплатить торговый сбор в BSQ или BTC. Если Вы выбираете BSQ, то увеличиваете уценку торгового сбора. @@ -1746,7 +1748,7 @@ popup.headline.error=Ошибка popup.doNotShowAgain=Не показывать снова popup.reportError.log=Открыть файл журнала popup.reportError.gitHub=Сообщить проблему на Github в раздел 'issues' -popup.reportError={0}\n\nчтобы помочь нам улучшить приложение, просьба сообщить о неисправности на нашем баг-трекере на GitHub (https://github.com/bisq-network/bisq-desktop/issues).\nСообщение о неисправности будет скопировано в буфер обмена при нажатии кнопки ниже.\nНам облегчит отладку, если Вы прикрепите также bisq.log файл. +popup.reportError={0}\n\nЧтобы помочь нам улучшить приложение, просьба сообщить о неисправности, открыв новую тему на https://github.com/bisq-network/bisq/issues. \nСообщение о неисправности будет скопировано в буфер обмена при нажатии любой из кнопок ниже.\nНам облегчит отладку, если Вы включите bisq.log файл журнала, нажав "открыть файл журнала", сохраните копию и прикрепите ее к отчету о неисправности. popup.error.tryRestart=Пожалуйста, попробуйте перезагрузить ваше приложение и проверьте подключение к сети, чтобы узнать, можете ли вы решить проблему. popup.error.takeOfferRequestFailed=Произошёл сбой, когда контрагент попытался принять одно из Ваших предложений:\n{0} @@ -1756,14 +1758,14 @@ error.deleteAddressEntryListFailed=Не удалось удалить AddressEnt popup.warning.walletNotInitialized=Кошелёк ещё не инициализирован popup.warning.wrongVersion=У Вас вероятно установлена не та версия Bisq.\nАрхитектура Вашего компьютера: {0}.\nУстановленные у Вас файлы: {1}.\nПожалуйста переустановите соответствующую версию ({2}). -popup.warning.incompatibleDB=Обнаружены несовместимые файлы базы данных!\nБазы данных этого файла(ов) несовместимы с нашей текущей базой кода:\n{0}\n\nМы сделали резервную копию поврежденного файла(ов) и применили значения по умолчанию к новой версии базы данных.\n\nРезервная копия находится по адресу:\n{1}/db/backup_of_corrupted_data.\n\nПроверьте, установлена ли новейшая версия Bisq.\nВы можете скачать ее по адресу:\nhttps://bisq.network/downloads\n\nПросьба перезагрузить приложение. +popup.warning.incompatibleDB=Обнаружены несовместимые файлы базы данных!\nБазы данных этих файлов несовместимы с нашей текущей базой кода:\n{0}\n\nМы сделали резервную копию поврежденных файлов и применили значения по умолчанию к новой версии базы данных.\n\nРезервная копия находится по адресу:\n{1}/db/backup_of_corrupted_data.\n\nПроверьте, установлена ли новейшая версия Bisq.\nВы можете скачать ее по адресу:\nhttps://bisq.network/downloads\n\nПросьба перезапустить приложение. popup.warning.startupFailed.twoInstances=Bisq уже запущен. Нельзя запустить два экземпляра Bisq. popup.warning.cryptoTestFailed=Кажется, Вы используете самокомпилированный двоичный файл, и не следуете инструкциям сборки в https://github.com/bisq-network/exchange/blob/master/doc/build.md#7-enable-unlimited-strength-for-cryptographic-keys.\n\nЕсли это не так, и Вы используете официальный бинарный Bisq, просьба отправить отчет о сбое на страницу Github.\nСбой={0} popup.warning.tradePeriod.halfReached=Ваша сделка с идентификатором {0} достигла половины макс. допустимого торгового периода, и до сих пор не завершена.\n\nТекущий период заканчивается {1}\n\nПросьба просмотреть дополнительную информацию о состоянии сделки в разделе \"Папка/Текущие сделки\" . popup.warning.tradePeriod.ended=Ваша сделка с идентификатором {0} достигла макс. допустимого торгового срока и не завершилась.\n\nТорговый период закончился {1}\n\nПросьба просмотреть свою сделку в разделе \"Папка/Текущие сделки\" для обращения к арбитру. popup.warning.noTradingAccountSetup.headline=Вы не настроили торговый счёт popup.warning.noTradingAccountSetup.msg=Прежде чем создать предложение, следует настроить счета национальной валюты или алткойна. \nЖелаете настроить счёт? -popup.warning.noArbitratorsAvailable= Нет доступных арбитров. +popup.warning.noArbitratorsAvailable=Нет доступных арбитров. popup.warning.notFullyConnected=Необходимо подождать, пока завершается подключение к сети.\nЭто может занять до 2 минут при запуске. popup.warning.notSufficientConnectionsToBtcNetwork=Необходимо подождать, пока образуется по меньшей мере {0} соединений с сетью Биткойн. popup.warning.downloadNotComplete=Необходимо подождать до завершения загрузки недостающих блоков цепи Биткойн. @@ -1772,18 +1774,18 @@ popup.warning.tooLargePercentageValue=Нельзя установить проц popup.warning.examplePercentageValue=Введите процентное число, например \"5.4\" для 5.4% popup.warning.noPriceFeedAvailable=Источник рыночного курса этой валюты отсутствует. Невозможно использовать процентный курс.\nПросьба указать фиксированный курс. popup.warning.sendMsgFailed=Не удалось отправить сообщение Вашему контрагенту .\nПопробуйте еще раз, и если неисправность повторится, сообщите о ней. -popup.warning.insufficientBtcFundsForBsqTx=У вас недостаточно средств BTC для оплаты комиссии майнера этой транзакции.\nПросьба пополнить свой кошелек BTC.\nНедостаёт средств: {0} +popup.warning.insufficientBtcFundsForBsqTx=У вас недостаточно средств BTC для оплаты комиссии майнера за этy транзакцию.\nПросьба пополнить свой кошелек BTC.\nНедостаёт средств: {0} popup.warning.insufficientBsqFundsForBtcFeePayment=У Вас недостаточно BSQ для оплаты торг. сбора в BSQ. Вы можете заплатить в BTC, или Вам необходимо пополнить свой кошелёк BSQ. BSQ можно купить в Bisq.\nНедостаёт BSQ: {0} popup.warning.noBsqFundsForBtcFeePayment=В Вашем кошельке BSQ недостаточно средств для оплаты торг. сбора в BSQ. -popup.warning.messageTooLong=Ваше сообщение превышает макс. Разрешенный размер. Пожалуйста, отправьте его в нескольких частях или загрузите в службу, например https://pastebin.com. +popup.warning.messageTooLong=Ваше сообщение превышает макс. разрешенный размер. Пожалуйста, отправьте его в нескольких частях или загрузите в службу, например https://pastebin.com. popup.warning.lockedUpFunds=У Вас есть запертые средства от неудачной сделки.\nЗапертый баланс: {0}\nАдрес транзакции депозита: {1}\nИдентификатор сделки {2}.\nПросьба создать билет поддержки, выбрав сделку в разделе незавершенных сделок и нажав \"alt + o\" или \"option + o\"." popup.warning.nodeBanned=Один из узлов {0} был запрещен/забанен. Перезапустите приложение, чтобы убедиться, что оно не подключено к запрещенному узлу. popup.warning.priceRelay=ретранслятор курса popup.warning.seed=кодовые слова -popup.info.securityDepositInfo=Чтобы гарантировать следование торговому протоколу трейдерами, необходим залоговый депозит.\n\nОн поступит на Ваш счёт и останется в Вашем торговом кошельке до успешного завершения сделки, и затем будет возвращен Вам.\n\nУчтите, что если Вы создаёте новое предложение, Bisq должно быть подключено к сети для принятия предложения другими трейдерами. Чтобы Ваши предложения были доступны в сети, компьютер и Bisq должны быть включёны и подключены к сети. (т. е. убедитесь, что компьютер не впал в режим ожидания...монитор в режиме ожидания не проблема). +popup.info.securityDepositInfo=Чтобы гарантировать следование торговому протоколу трейдерами, обоим необходимо заплатить залоговый депозит.\n\nДепозит остаётся в Вашем торговом кошельке до успешного завершения сделки, и затем будет возвращен Вам.\n\nУчтите, что если Вы создаёте новое предложение, Bisq должен быть подключён к сети для принятия предложения другими трейдерами. Чтобы Ваши предложения были доступны в сети, компьютер и Bisq должны быть включёны и подключены к сети. (т. е. убедитесь, что компьютер не впал в режим ожидания...монитор в режиме ожидания не проблема). popup.info.cashDepositInfo=Просьба убедиться, что в Вашем районе существует отделение банка, где возможно внести депозит наличными.\nИдентификатор (BIC/SWIFT) банка продавца: {0}. popup.info.cashDepositInfo.confirm=Я подтверждаю, что могу внести депозит @@ -1797,7 +1799,7 @@ popup.securityRecommendation.msg=Напоминаем и рекомендуем popup.bitcoinLocalhostNode.msg=Bisq обнаружил локально работающий узел Bitcoin Core (на локальном узле).\nПеред запуском Биск убедитесь, что этот узел полностью синхронизирован с сетью Биткойн и не работает в режиме обрезки данных "pruning". -popup.shutDownInProgress.headline=Работа завершается +popup.shutDownInProgress.headline=Работа завершается popup.shutDownInProgress.msg=Завершение работы приложения может занять несколько секунд.\nПросьба не прерывать этот процесс. popup.attention.forTradeWithId=Обратите внимание на сделку с идентификатором {0} @@ -1805,6 +1807,9 @@ popup.attention.forTradeWithId=Обратите внимание на сделк popup.roundedFiatValues.headline=Новая функция конфиденциальности: Округленные значения нац. валют popup.roundedFiatValues.msg=Для повышения конфиденциальности Вашей сделки, сумма {0} была округлена.\n\nВ зависимости от версии приложения, Вы заплатите или получите либо значения с десятичными знаками, либо округленные.\n\nОтныне, оба значения соответствуют торговому протоколу.\n\nТакже имейте в виду, что значения BTC изменяются автоматически, чтобы предельно соответствовать округленной сумме нац. валюты. +popup.info.multiplePaymentAccounts.headline=Multiple payment accounts available +popup.info.multiplePaymentAccounts.msg=You have multiple payment accounts available for this offer. Please make sure you've picked the right one. + #################################################################### # Notifications @@ -1874,7 +1879,7 @@ table.placeholder.noData=Сейчас данные недоступны peerInfoIcon.tooltip.tradePeer=контрагента peerInfoIcon.tooltip.maker=Создателя -peerInfoIcon.tooltip.trade.traded=Onion/Tor адрес {0}: {1}\nВы уже торговали {2} раз(a) с данным трейдером\n{3} +peerInfoIcon.tooltip.trade.traded=Onion/Tor адрес {0}: {1}\nВы уже торговали {2} раз(a) с данным трейдером\n{3} peerInfoIcon.tooltip.trade.notTraded=Onion/Tor адрес {0}: {1}\nВы ещё не торговали с этим трейдером.\n {2} peerInfoIcon.tooltip.age=Платёжный счёт создан {0} назад. peerInfoIcon.tooltip.unknownAge=Срок существования платёжного счёта неизвестен. @@ -2048,7 +2053,7 @@ payment.promptPay.promptPayId=Удостовер. гражданства / на payment.supportedCurrencies=Поддерживаемые валюты payment.limitations=Ограничения payment.salt=Модификатор/Соль для подтверждения срока существования счёта -payment.error.noHexSalt=Соль должна быть в HEX/шестнадцатеричном формате.\nРекомендуется редактировать поле соль, только при переносе её из старого счёта, чтобы сохранить его срок существования. Срок проверяется с помощью соли и опознающих данных счёта (напр. IBAN). +payment.error.noHexSalt=Соль должна быть в HEX/шестнадцатеричном формате.\nРекомендуется редактировать поле соли только при переносе её из старого счёта, чтобы сохранить его срок существования. Срок проверяется с помощью соли и опознающих данных счёта (напр. IBAN). payment.accept.euro=Принять сделки из этих стран ЕUR payment.accept.nonEuro=Принять сделки из этих не-ЕUR стран payment.accepted.countries=Приемлемые страны @@ -2085,20 +2090,20 @@ payment.clearXchange.info=Убедитесь, что выполняете тре payment.moneyGram.info=При использовании MoneyGram покупатель BTC должен отправить по э-почте продавцу BTC номер авторизации и фотографию квитанции. В квитанции должно быть четко указано полное имя продавца, страна, штат и сумма. В процессе сделки, покупателю будет показан адрес э-почты продавца. payment.westernUnion.info=При использовании Western Union покупатель BTC обязан отправить продавцу BTC по э-почте MTCN (номер отслеживания) и фотографию квитанции. В квитанции должно быть четко указано полное имя продавца, город, страна и сумма. В процессе сделки, покупателю будет показан адрес э-почты продавца. -payment.halCash.info=Используя HalCash, покупатель BTC обязан отправить продавцу BTC код HalCash через СМС с мобильного телефона.\n\nПросьба убедиться, что не превышена макс. сумма, которую Ваш банк позволяет отправить с HalCash. Мин. сумма каждого вывода составляет 10 EUR, и макс. 600 EUR. При повторном выводе - 3000 EUR на получателя в день и 6000 EUR на получателя в месяц. Просьба сверить эти лимиты с Вашим банком, и убедиться, что используются те же.\n\nСумма должна быть кратна 10 EUR, так как невозможно снять другие суммы с банкомата. В приложении, диалог "создать-предложение" и "принять-предложение" отрегулирует правильную сумму BTC. Нельзя использовать рыночную цену, так как сумма в EUR будет меняться с курсом.\n\nВ случае спора, покупателю BTC необходимо предоставить доказательство отправки EUR. +payment.halCash.info=Используя HalCash, покупатель BTC обязан отправить продавцу BTC код HalCash через СМС с мобильного телефона.\n\nПросьба убедиться, что не превышена макс. сумма, которую Ваш банк позволяет отправить с HalCash. Мин. сумма каждого вывода составляет 10 EUR, и макс. 600 EUR. При повторном выводе - 3000 EUR на получателя в день и 6000 EUR на получателя в месяц. Просьба сверить эти лимиты с Вашим банком, и убедиться, что используются те же.\n\nСумма должна быть кратна 10 EUR, так как невозможно снять другие суммы с банкомата. В приложении, диалог "создать-предложение" и "принять-предложение" отрегулирует правильную сумму BTC. Нельзя использовать рыночный курс, так как сумма в EUR будет меняться с курсом.\n\nВ случае спора, покупателю BTC необходимо предоставить доказательство отправки EUR. payment.limits.info=Учтите, что все банковские переводы несут определенный риск возвратного платежа.\n\nЧтобы снизить этот риск, Bisq ограничивает суммы сделок, на основе двух факторов: \n\n1. Расчёт уровня риска возвратного платежа данного метода оплаты \n2. Срок существования Вашего счета, созданного Вами в Bisq для этого метода оплаты\n\nСрок существования нового счёта создаваемый Вами сейчас равен нулю. С ростом этого срока в течении двух месяцев, предел сумм сделок будет расти:\n\n● В течении 1-го месяца, предел каждой сделки будет {0}\n● В течении 2-го месяца, предел будет {1}\n● После 2-го месяца, предел будет {2}\n\nУчтите, что нет никаких ограничений на общее количество Ваших сделок. payment.cashDeposit.info=Просьба удостовериться, что Ваш банк позволяет отправлять денежные депозиты на счета других. Например, Bank of America и Wells Fargo больше не разрешают такие депозиты. payment.f2f.contact=Контактная информация payment.f2f.contact.prompt=Как Вы хотите связаться с контрагентом? (адрес электронной почты, номер телефона...) -payment.f2f.city=Город для встречи "лицом к лицу" +payment.f2f.city=Город для встречи "лицом к лицу" payment.f2f.city.prompt=Город будет назван в предложении payment.f2f.optionalExtra=Дополнительная необязательная информация payment.f2f.extra=Дополнительная информация payment.f2f.extra.prompt=Создатель в праве определить "условия", или добавить общедоступную контактную информацию. Это будет показано в предложении. -payment.f2f.info=В сделках F2F 'лицом к лицу' особые правила и риск, в отличии от транзакций онлайн. \n\nОсновные различия:\n● Контрагенты вынуждены обмениваться информацией о месте и времени встречи, используя предоставленные ими контактные данные.\n● Контрагенты вынуждены приносить свои ноутбуки, и подтверждать отправку и получение платежа при встрече.\n● Если создатель определяет особые 'условия', он обязан указать их в поле 'Дополнительная информация' при создании счёта.\n● Принимая предложение, получатель соглашается с заявленными создателем 'условиями'.\n● В случае возникновения спора, арбитр не способен помочь, так как затруднительно получить неопровержимые доказательства того, что произошло при встрече. В таких случаях BTC могут быть заперты навсегда, или до тех пор, пока контрагенты не достигнут согласия.\n\nДля полной уверенности, что Вы понимаете особенности сделок 'лицом к лицу', просьба прочесть инструкции и рекомендации по ссылке: 'https://docs.bisq.network/trading-rules.html#f2f-trading' +payment.f2f.info=В сделках F2F 'лицом к лицу' есть особые правила и риски, в отличии от транзакций онлайн. \n\nОсновные различия:\n● Контрагентам нужно обмениваться информацией о месте и времени встречи, используя предоставленные ими контактные данные.\n● Контрагентам нужно принести свои ноутбуки, и подтвердить отправку и получение платежа при встрече.\n● Если создатель определяет особые 'условия', он обязан указать их в поле 'Дополнительная информация' при создании счёта.\n● Принимая предложение, получатель соглашается с заявленными создателем 'условиями'.\n● В случае возникновения спора, арбитр не способен помочь, так как затруднительно получить неопровержимые доказательства того, что произошло при встрече. В таких случаях BTC могут быть заперты навсегда, или до тех пор, когда контрагенты достигнут согласия.\n\nДля полной уверенности, что Вы понимаете особенности сделок 'лицом к лицу', просьба прочесть инструкции и рекомендации на ссылке: 'https://docs.bisq.network/trading-rules.html#f2f-trading' payment.f2f.info.openURL=Открыть веб-страницу payment.f2f.offerbook.tooltip.countryAndCity=Страна и город: {0} / {1} payment.f2f.offerbook.tooltip.extra=Дополнительная информация: {0} @@ -2132,7 +2137,7 @@ MONEY_GRAM_SHORT=MoneyGram # suppress inspection "UnusedProperty" WESTERN_UNION_SHORT=Western Union # suppress inspection "UnusedProperty" -F2F_SHORT=Лицом к лицу +F2F_SHORT=Лицом к лицу # Do not translate brand names # suppress inspection "UnusedProperty" @@ -2273,11 +2278,11 @@ validation.iban.invalidLength=Номер должен быть от 15 до 34 validation.interacETransfer.invalidAreaCode=Код не Канадского региона validation.interacETransfer.invalidPhone=Неверный формат номера телефона или адрес электронной почты validation.interacETransfer.invalidQuestion=Должно содержать только буквы, цифры, пробелы и/или символы ' _ , . ? - -validation.interacETransfer.invalidAnswer=Необходимо одно слово, содержащее только буквы, цифры и символ - +validation.interacETransfer.invalidAnswer=Должно быть одно слово, содержащее только буквы, цифры и/или символ - validation.inputTooLarge=Данные должны быть не более {0} validation.inputTooSmall=Данные должны быть более {0} validation.amountBelowDust=Сумма ниже предела ("пыли") {0} не допускается. validation.length=Длина должна быть между {0} и {1} validation.pattern=Данные должны быть в формате: {0} validation.noHexString=Данные не в шестнадцатеричном формате. -validation.advancedCash.invalidFormat=Необходим действительный идент. э-почты или кошелька в формате: x000000000000 +validation.advancedCash.invalidFormat=Должен быть действительный идент. э-почты или кошелька в формате: x000000000000 diff --git a/core/src/main/resources/i18n/displayStrings_sr.properties b/core/src/main/resources/i18n/displayStrings_sr.properties index 10374ef9db..6c56e7263b 100644 --- a/core/src/main/resources/i18n/displayStrings_sr.properties +++ b/core/src/main/resources/i18n/displayStrings_sr.properties @@ -299,6 +299,8 @@ market.trades.tooltip.candle.date=Datum: offerbook.createOffer=Napravite ponudu offerbook.takeOffer=Prihvatite ponudu +offerbook.takeOfferToBuy=Take offer to buy {0} +offerbook.takeOfferToSell=Take offer to sell {0} offerbook.trader=Trgovac offerbook.offerersBankId=ID banke tvorca ponude: {0} offerbook.offerersBankName=Ime banke tvorca ponude: {0} @@ -560,12 +562,12 @@ portfolio.pending.step3_buyer.warn.part1b=kod vašeg platnog provajdera (npr. ba portfolio.pending.step3_buyer.warn.part2=The BTC seller still has not confirmed your payment!\nPlease check {0} if the payment sending was successful.\nIf the BTC seller does not confirm the receipt of your payment until {1} the trade will be investigated by the arbitrator. portfolio.pending.step3_buyer.openForDispute=The BTC seller has not confirmed your payment!\nThe max. period for the trade has elapsed.\nPlease contact the arbitrator for opening a dispute. # suppress inspection "TrailingSpacesInProperty" -portfolio.pending.step3_seller.part=Your trading partner has confirmed that he initiated the {0} payment.\n\n +portfolio.pending.step3_seller.part=Your trading partner has confirmed that they have initiated the {0} payment.\n\n portfolio.pending.step3_seller.altcoin.explorer=on your favorite {0} blockchain explorer portfolio.pending.step3_seller.altcoin.wallet=at your {0} wallet portfolio.pending.step3_seller.altcoin={0}Please check {1} if the transaction to your receiving address\n{2}\nhas already sufficient blockchain confirmations.\nThe payment amount has to be {3}\n\nYou can copy & paste your {4} address from the main screen after closing that popup. portfolio.pending.step3_seller.postal={0}Please check if you have received {1} with \"US Postal Money Order\" from the BTC buyer.\n\nThe trade ID (\"reason for payment\" text) of the transaction is: \"{2}\" -portfolio.pending.step3_seller.bank=Your trading partner has confirmed that he initiated the {0} payment.\n\nPlease go to your online banking web page and check if you have received {1} from the BTC buyer.\n\nThe trade ID (\"reason for payment\" text) of the transaction is: \"{2}\"\n\n +portfolio.pending.step3_seller.bank=Your trading partner has confirmed that they have initiated the {0} payment.\n\nPlease go to your online banking web page and check if you have received {1} from the BTC buyer.\n\nThe trade ID (\"reason for payment\" text) of the transaction is: \"{2}\"\n\n portfolio.pending.step3_seller.cash=Because the payment is done via Cash Deposit the BTC buyer has to write \"NO REFUND\" on the paper receipt, tear it in 2 parts and send you a photo by email.\n\nTo avoid chargeback risk, only confirm if you received the email and if you are sure the paper receipt is valid.\nIf you are not sure, {0} portfolio.pending.step3_seller.moneyGram=The buyer has to send you the Authorisation number and a photo of the receipt by email.\nThe receipt must clearly show your full name, country, state and the amount. Please check your email if you received the Authorisation number.\n\nAfter closing that popup you will see the BTC buyer's name and address for picking up the money from MoneyGram.\n\nOnly confirm receipt after you have successfully picked up the money! portfolio.pending.step3_seller.westernUnion=The buyer has to send you the MTCN (tracking number) and a photo of the receipt by email.\nThe receipt must clearly show your full name, city, country and the amount. Please check your email if you received the MTCN.\n\nAfter closing that popup you will see the BTC buyer's name and address for picking up the money from Western Union.\n\nOnly confirm receipt after you have successfully picked up the money! @@ -926,10 +928,10 @@ account.arbitratorSelection.minOne=Potrebno je da imate bar jednog arbitra izabr account.altcoin.yourAltcoinAccounts=Your altcoin accounts account.altcoin.popup.wallet.msg=Please be sure that you follow the requirements for the usage of {0} wallets as described on the {1} web page.\nUsing wallets from centralized exchanges where (a) you don''t control your keys or (b) which don''t use compatible wallet software is risky: it can lead to loss of the traded funds!\nThe arbitrator is not a {2} specialist and cannot help in such cases. account.altcoin.popup.wallet.confirm=Razumem i potvrđujem da znam koji novčanik trebam da koristim. -account.altcoin.popup.xmr.msg=If you want to trade XMR on Bisq please be sure you understand and fulfill the following requirements:\n\nFor sending XMR you need to use either the official Monero GUI wallet or Monero CLI wallet with the store-tx-info flag enabled (default in new versions). Please be sure you can access the tx key as that would be required in case of a dispute.\nmonero-wallet-cli (use the command get_tx_key)\nmonero-wallet-gui (go to history tab and click on the (P) button for payment proof)\n\nIn addition to XMR checktx tool (https://xmr.llcoins.net/checktx.html) verification can also be accomplished in-wallet.\nmonero-wallet-cli : using command (check_tx_key).\nmonero-wallet-gui : on the Advanced > Prove/Check page.\nAt normal block explorers the transfer is not verifiable.\n\nYou need to provide the arbitrator the following data in case of a dispute:\n- The tx private key\n- The transaction hash\n- The recipient's public address\n\nIf you cannot provide the above data or if you used an incompatible wallet it would result in losing the dispute case. The XMR sender is responsible to be able to verify the XMR transfer to the arbitrator in case of a dispute.\n\nThere is no payment ID required, just the normal public address.\nIf you are not sure about that process visit (https://www.getmonero.org/resources/user-guides/prove-payment.html) or the Monero forum (https://forum.getmonero.org) to find more information. -account.altcoin.popup.blur.msg=If you want to trade BLUR on Bisq please be sure you understand and fulfill the following requirements:\n\nTo send BLUR you must use the Blur Network CLI or GUI Wallet. \n\nIf you are using the CLI wallet, a transaction hash (tx ID) will be displayed after a transfer is sent. You must save this information. Immediately after sending the transfer, you must use the command 'get_tx_key' to retrieve the transaction private key. If you fail to perform this step, you may not be able to retrieve the key later. \n\nIf you are using the Blur Network GUI Wallet, the transaction private key and transaction ID can be found conveniently in the "History" tab. Immediately after sending, locate the transaction of interest. Click the "?" symbol in the lower-right corner of the box containing the transaction. You must save this information. \n\nIn the event that arbitration is necessary, you must present the following to an arbitrator: 1.) the transaction ID, 2.) the transaction private key, and 3.) the recipient's address. The arbitrator will then verify the BLUR transfer using the Blur Transaction Viewer (https://blur.cash/#tx-viewer).\n\nIf you cannot provide the required information to the arbitrator, you will lose the dispute. In all cases of dispute, the BLUR sender bears 100% of the burden of responsiblity in verifying transactions to an arbitrator. \n\nIf you do not understand these requirements, do not trade on Bisq. First, seek help at the Blur Network Discord (https://discord.gg/dMWaqVW). -account.altcoin.popup.ccx.msg=If you want to trade CCX on Bisq please be sure you understand the following requirements:\n\nTo send CCX you must use an official Conceal wallet, either CLI or GUI. After sending a transfer payment, the wallets\ndisplay the transaction secret key. You must save it along with the transaction hash (ID) and the recipient's public\naddress in case arbitration is necessary. In such a case, you must give all three to the arbitrator, who will then\nverify the CCX transfer using the Conceal Transaction Viewer (https://explorer.conceal.network/txviewer).\nBecause Conceal is a privacy coin, block explorers cannot verify transfers.\n\nIf you cannot provide the required data to the arbitrator, you will lose the dispute case.\nIf you do not save the transaction secret key immediately after transferring CCX, it cannot be recovered later.\nIf you do not understand these requirements, seek help at the Conceal discord (http://discord.conceal.network). -account.altcoin.popup.drgl.msg=Trading Dragonglass on Bisq requires that you understand and fulfill the following requirements:\n\nBecause of the privacy Dragonglass provides a transaction is not verifyable on the public blockchain. If required you can prove your payment thru use of your TXN-Private-Key.\nThe TXN-Private Key is a one-time key automatically generated for every transaction that can only be accessed from within your DRGL wallet.\nEither by DRGL-wallet GUI (inside transaction details dialog) or by the Dragonglass CLI simplewallet (using command "get_tx_key").\n\nDRGL version 'Oathkeeper' and higher are REQUIRED for both.\n\nIn case of a dispute, you must provide the arbitrator the following data:\n- The TXN-Private key\n- The transaction hash\n- The recipient's public address\n\nVerification of payment can be made using the above data as inputs at \ (http://drgl.info/#check_txn).\n\nIf you cannot provide the above data or if you used an incompatible wallet it would result in losing the dispute case. The Dragonglass sender is responsible to be able to verify the DRGL transfer to the arbitrator in case of a dispute. Use of PaymentID is not required.\n\nIf you are unsure about any part of this process, visit Dragonglass on Discord (http://discord.drgl.info) for help. +account.altcoin.popup.xmr.msg=Trading XMR on Bisq requires that you understand and fulfill the following requirements:\n\nFor sending XMR, you need to use either the official Monero GUI wallet or Monero CLI wallet with the store-tx-info flag enabled (default in new versions). Please be sure you can access the tx key as that would be required in case of a dispute.\nmonero-wallet-cli (use the command get_tx_key)\nmonero-wallet-gui (go to history tab and click on the (P) button for payment proof)\n\nIn addition to XMR checktx tool (https://xmr.llcoins.net/checktx.html) verification can also be accomplished in-wallet.\nmonero-wallet-cli : using command (check_tx_key).\nmonero-wallet-gui : on the Advanced > Prove/Check page.\nAt normal block explorers the transfer is not verifiable.\n\nYou need to provide the arbitrator the following data in case of a dispute:\n- The tx private key\n- The transaction hash\n- The recipient's public address\n\nFailure to provide the above data, or if you used an incompatible wallet, will result in losing the dispute case. The XMR sender is responsible for providing verification of the XMR transfer to the arbitrator in case of a dispute.\n\nThere is no payment ID required, just the normal public address.\nIf you are not sure about that process visit (https://www.getmonero.org/resources/user-guides/prove-payment.html) or the Monero forum (https://forum.getmonero.org) to find more information. +account.altcoin.popup.blur.msg=Trading BLUR on Bisq requires that you understand and fulfill the following requirements:\n\nTo send BLUR you must use the Blur Network CLI or GUI Wallet. \n\nIf you are using the CLI wallet, a transaction hash (tx ID) will be displayed after a transfer is sent. You must save this information. Immediately after sending the transfer, you must use the command 'get_tx_key' to retrieve the transaction private key. If you fail to perform this step, you may not be able to retrieve the key later. \n\nIf you are using the Blur Network GUI Wallet, the transaction private key and transaction ID can be found conveniently in the "History" tab. Immediately after sending, locate the transaction of interest. Click the "?" symbol in the lower-right corner of the box containing the transaction. You must save this information. \n\nIn the event that arbitration is necessary, you must present the following to an arbitrator: 1.) the transaction ID, 2.) the transaction private key, and 3.) the recipient's address. The arbitrator will then verify the BLUR transfer using the Blur Transaction Viewer (https://blur.cash/#tx-viewer).\n\nFailure to provide the required information to the arbitrator will result in losing the dispute case. In all cases of dispute, the BLUR sender bears 100% of the burden of responsibility in verifying transactions to an arbitrator. \n\nIf you do not understand these requirements, do not trade on Bisq. First, seek help at the Blur Network Discord (https://discord.gg/dMWaqVW). +account.altcoin.popup.ccx.msg=Trading CCX on Bisq requires that you understand the following requirements:\n\nTo send CCX you must use an official Conceal wallet, either CLI or GUI. After sending a transfer payment, the wallets\ndisplay the transaction secret key. You must save it along with the transaction hash (ID) and the recipient's public\naddress in case arbitration is necessary. In such a case, you must give all three to the arbitrator, who will then\nverify the CCX transfer using the Conceal Transaction Viewer (https://explorer.conceal.network/txviewer).\nBecause Conceal is a privacy coin, block explorers cannot verify transfers.\n\nFailure to provide the required data to the arbitrator will result in losing the dispute case.\nIf you do not save the transaction secret key immediately after transferring CCX, it cannot be recovered later.\nIf you do not understand these requirements, seek help at the Conceal discord (http://discord.conceal.network). +account.altcoin.popup.drgl.msg=Trading Dragonglass on Bisq requires that you understand and fulfill the following requirements:\n\nBecause of the privacy Dragonglass provides, a transaction is not verifiable on the public blockchain. If required, you can prove your payment through the use of your TXN-Private-Key.\nThe TXN-Private Key is a one-time key automatically generated for every transaction that can only be accessed from within your DRGL wallet.\nEither by DRGL-wallet GUI (inside transaction details dialog) or by the Dragonglass CLI simplewallet (using command "get_tx_key").\n\nDRGL version 'Oathkeeper' and higher are REQUIRED for both.\n\nIn case of a dispute, you must provide the arbitrator the following data:\n- The TXN-Private key\n- The transaction hash\n- The recipient's public address\n\nVerification of payment can be made using the above data as inputs at (http://drgl.info/#check_txn).\n\nFailure to provide the above data, or if you used an incompatible wallet, will result in losing the dispute case. The Dragonglass sender is responsible for providing verification of the DRGL transfer to the arbitrator in case of a dispute. Use of PaymentID is not required.\n\nIf you are unsure about any part of this process, visit Dragonglass on Discord (http://discord.drgl.info) for help. account.altcoin.popup.ZEC.msg=Tokom korišćenja {0} možete koristiti samo transparentne adrese (počinju sa t) a ne z-adrese (privatne), jer arbitar ne bi bio u stanju da proveri transakciju sa z-adresom. account.altcoin.popup.XZC.msg=When using {0} you can only use the transparent (traceable) addresses not the untraceable addresses, because the arbitrator would not be able to verify the transaction with untraceable addresses at a block explorer. account.altcoin.popup.bch=Bitcoin Cash and Bitcoin Clashic suffer from replay protection. If you use those coins be sure you take sufficient precautions and understand all implications.You can suffer losses by sending one coin and unintentionally send the same coins on the other block chain.Because those "airdrop coins" share the same history with the Bitcoin blockchain there are also security risks and a considerable risk for losing privacy.\n\nPlease read at the Bisq Forum more about that topic: https://forum.bisq.io/t/airdrop-coins-information-thread-bch-btg-bchc @@ -1306,7 +1308,7 @@ dao.burnBsq.assets.lookBackPeriod=Verification period dao.burnBsq.assets.trialFee=Fee for trial period dao.burnBsq.assets.totalFee=Total fees paid dao.burnBsq.assets.days={0} days -dao.burnBsq.assets.toFewDays=The asset fee is too low. The min. amount of days for the trial perios is {0}. +dao.burnBsq.assets.toFewDays=The asset fee is too low. The min. amount of days for the trial period is {0}. # suppress inspection "UnusedProperty" dao.assetState.UNDEFINED=Undefined @@ -1584,7 +1586,7 @@ displayUpdateDownloadWindow.verify.failed=Verification failed.\nPlease download displayUpdateDownloadWindow.success=The new version has been successfully downloaded and the signature(s) verified.\n\nPlease open the download directory, shut down the application and install the new version. displayUpdateDownloadWindow.download.openDir=Open download directory -disputeRezimeWindow.title=Rezime +disputeSummaryWindow.title=Rezime disputeSummaryWindow.openDate=Ticket opening date disputeSummaryWindow.role=Trader's role disputeSummaryWindow.evidence=Evidence @@ -1746,7 +1748,7 @@ popup.headline.error=Greška popup.doNotShowAgain=Ne prikazuj opet popup.reportError.log=Open log file popup.reportError.gitHub=Prijavi Github pratiocu problema -popup.reportError={0}\n\nTo help us to improve the software please report the bug on our issue tracker on GitHub (https://github.com/bisq-network/bisq-desktop/issues).\nThe error message will be copied to the clipboard when you click a button below.\nIt will make debugging easier if you can attach the bisq.log file as well. +popup.reportError={0}\n\nTo help us to improve the software please report this bug by opening a new issue at https://github.com/bisq-network/bisq/issues.\nThe above error message will be copied to the clipboard when you click either of the buttons below.\nIt will make debugging easier if you include the bisq.log file by pressing "Open log file", saving a copy, and attaching it to your bug report. popup.error.tryRestart=Molimo pokušajte da ponovo pokrenete vašu aplikaciju i proverite vašu mrežnu konekciju da vidite da li možete da rešite problem. popup.error.takeOfferRequestFailed=An error occurred when someone tried to take one of your offers:\n{0} @@ -1805,6 +1807,9 @@ popup.attention.forTradeWithId=Potrebna pažnja za trgovinu sa ID {0} popup.roundedFiatValues.headline=New privacy feature: Rounded fiat values popup.roundedFiatValues.msg=To increase privacy of your trade the {0} amount was rounded.\n\nDepending on the client version you''ll pay or receive either values with decimals or rounded ones.\n\nBoth values do comply from now on with the trade protocol.\n\nAlso be aware that BTC values are changed automatically to match the rounded fiat amount as close as possible. +popup.info.multiplePaymentAccounts.headline=Multiple payment accounts available +popup.info.multiplePaymentAccounts.msg=You have multiple payment accounts available for this offer. Please make sure you've picked the right one. + #################################################################### # Notifications @@ -2085,7 +2090,7 @@ payment.clearXchange.info=Please be sure that you fulfill the requirements for t payment.moneyGram.info=When using MoneyGram the BTC buyer has to send the Authorisation number and a photo of the receipt by email to the BTC seller. The receipt must clearly show the seller's full name, country, state and the amount. The buyer will get displayed the seller's email in the trade process. payment.westernUnion.info=When using Western Union the BTC buyer has to send the MTCN (tracking number) and a photo of the receipt by email to the BTC seller. The receipt must clearly show the seller's full name, city, country and the amount. The buyer will get displayed the seller's email in the trade process. -payment.halCash.info=When using HalCash the BTC buyer need to send the BTC seller the HalCash code via a text message from the mobile phone.\n\nPlease make sure to not exceed the maximum amount your bank allows you to send with HalCash. The min. amount per withdrawal is 10 EUR and the max. amount is 600 EUR. For repeated withdrawals it is 3000 EUR per receiver per day and 6000 EUR per receiver per month. Please cross check those limits with your bank to be sure they use the same limits as stated here.\n\nThe withdrawal amount must be a multiple of 10 EUR as you cannot withdraw other amounts from an ATM. The UI in the create-offer and take-offer screen will adjust the BTC amount so that the EUR amount is correct. You cannot use market based price as the EUR amount would be changing with changing prices.\n\nIn case of a dispute the BTC buyer need to provide the proof that he sent the EUR. +payment.halCash.info=When using HalCash the BTC buyer needs to send the BTC seller the HalCash code via a text message from their mobile phone.\n\nPlease make sure to not exceed the maximum amount your bank allows you to send with HalCash. The min. amount per withdrawal is 10 EUR and the max. amount is 600 EUR. For repeated withdrawals it is 3000 EUR per receiver per day and 6000 EUR per receiver per month. Please cross check those limits with your bank to be sure they use the same limits as stated here.\n\nThe withdrawal amount must be a multiple of 10 EUR as you cannot withdraw other amounts from an ATM. The UI in the create-offer and take-offer screen will adjust the BTC amount so that the EUR amount is correct. You cannot use market based price as the EUR amount would be changing with changing prices.\n\nIn case of a dispute the BTC buyer needs to provide the proof that they sent the EUR. payment.limits.info=Please be aware that all bank transfers carry a certain amount of chargeback risk.\n\nTo mitigate this risk, Bisq sets per-trade limits based on two factors:\n\n1. The estimated level of chargeback risk for the payment method used\n2. The age of your account for that payment method\n\nThe account you are creating now is new and its age is zero. As your account grows in age over a two-month period, your per-trade limits will grow along with it:\n\n● During the 1st month, your per-trade limit will be {0}\n● During the 2nd month, your per-trade limit will be {1}\n● After the 2nd month, your per-trade limit will be {2}\n\nPlease note that there are no limits on the total number of times you can trade. payment.cashDeposit.info=Please confirm your bank allows you to send cash deposits into other peoples' accounts. For example, Bank of America and Wells Fargo no longer allow such deposits. @@ -2098,7 +2103,7 @@ payment.f2f.optionalExtra=Optional additional information payment.f2f.extra=Additional information payment.f2f.extra.prompt=The maker can define 'terms and conditions' or add a public contact information. It will be displayed with the offer. -payment.f2f.info='Face to Face' trades have different rules and come with different risks than online transactions.\n\nThe main differences are:\n● The trading peers need to exchange information about the meeting location and time by using their provided contact details.\n● The trading peers need to bring their laptops and do the confirmation of 'payment sent' and 'payment received' at the meeting place.\n● If a maker has special 'terms and conditions' he needs to state those in the 'Addition information' text field in the account.\n● By taking an offer the taker agrees to the maker's stated 'terms and conditions'.\n● In case of a dispute the arbitrator cannot help much as it is usually hard to get tamper proof evidence of what happened at the meeting. In such cases the BTC funds might get locked indefinitely or until the trading peers come to an agreement.\n\nTo be sure you fully understand the differences with 'Face to Face' trades please read the instructions and recommendations at: 'https://docs.bisq.network/trading-rules.html#f2f-trading' +payment.f2f.info='Face to Face' trades have different rules and come with different risks than online transactions.\n\nThe main differences are:\n● The trading peers need to exchange information about the meeting location and time by using their provided contact details.\n● The trading peers need to bring their laptops and do the confirmation of 'payment sent' and 'payment received' at the meeting place.\n● If a maker has special 'terms and conditions' they must state those in the 'Additional information' text field in the account.\n● By taking an offer the taker agrees to the maker's stated 'terms and conditions'.\n● In case of a dispute the arbitrator cannot help much as it is usually hard to get tamper proof evidence of what happened at the meeting. In such cases the BTC funds might get locked indefinitely or until the trading peers come to an agreement.\n\nTo be sure you fully understand the differences with 'Face to Face' trades please read the instructions and recommendations at: 'https://docs.bisq.network/trading-rules.html#f2f-trading' payment.f2f.info.openURL=Open web page payment.f2f.offerbook.tooltip.countryAndCity=County and city: {0} / {1} payment.f2f.offerbook.tooltip.extra=Additional information: {0} diff --git a/core/src/main/resources/i18n/displayStrings_th.properties b/core/src/main/resources/i18n/displayStrings_th.properties index 9e4facc43d..209f0b9e46 100644 --- a/core/src/main/resources/i18n/displayStrings_th.properties +++ b/core/src/main/resources/i18n/displayStrings_th.properties @@ -74,7 +74,7 @@ shared.address=ที่อยู่ shared.balanceWithCur=ยอดคงเหลือใน {0} shared.txId=เลขอ้างอิงการทำธุรกรรม shared.confirmations=การยืนยัน -shared.revert=ย้อนกลับ Tx +shared.revert=ย้อนกลับสู่การทำธุรกรรม shared.select=เลือก shared.usage=การใช้งาน shared.state=สถานะ @@ -187,13 +187,13 @@ shared.securityDepositBox.description=เงินประกันสำหร shared.iConfirm=ฉันยืนยัน shared.tradingFeeInBsqInfo=เทียบเท่า {0} ใช้เป็นค่าธรรมเนียมการขุด shared.openURL=เปิด {0} -shared.fiat=Fiat -shared.crypto=Crypto -shared.all=All -shared.edit=Edit -shared.advancedOptions=Advanced options -shared.interval=Interval -shared.actions=Actions +shared.fiat=คำสั่ง +shared.crypto=คริปโต +shared.all=ทั้งหมด +shared.edit=แก้ไข +shared.advancedOptions=ทางเลือกขั้นสูง +shared.interval=ระยะห่าง +shared.actions=การปฏิบัติการ shared.buyerUpperCase=ผู้ซื้อ shared.sellerUpperCase=ผู้ขาย @@ -215,9 +215,9 @@ mainView.menu.settings=ตั้งค่า mainView.menu.account=บัญชี mainView.menu.dao=DAO -mainView.marketPrice.provider=Price by -mainView.marketPrice.label=Market price -mainView.marketPriceWithProvider.label=Market price by {0} +mainView.marketPrice.provider=ราคาโดย +mainView.marketPrice.label=ราคาตลาด +mainView.marketPriceWithProvider.label=ราคาตลาดโดย {0} mainView.marketPrice.bisqInternalPrice=ราคาของการซื้อขาย Bisq ล่าสุด mainView.marketPrice.tooltip.bisqInternalPrice=ไม่มีราคาตลาดจากผู้ให้บริการด้านราคาภายนอก\nราคาที่แสดงเป็นราคาล่าสุดของ Bisq สำหรับสกุลเงินนั้น mainView.marketPrice.tooltip=ราคาตลาดจัดทำโดย {0} {1} \nอัปเดตล่าสุด: {2} \nnode URL ของผู้ให้บริการ: {3} @@ -225,8 +225,8 @@ mainView.marketPrice.tooltip.altcoinExtra=หาก altcoin ไม่สาม mainView.balance.available=ยอดคงเหลือที่พร้อมใช้งาน mainView.balance.reserved=ข้อเสนอได้รับการจองแล้ว mainView.balance.locked=ล็อคในการซื้อขาย -mainView.balance.reserved.short=Reserved -mainView.balance.locked.short=Locked +mainView.balance.reserved.short=จองแล้ว +mainView.balance.locked.short=ถูกล็อคไว้ mainView.footer.usingTor=(ใช้งาน Tor) mainView.footer.localhostBitcoinNode=(แม่ข่ายเฉพาะที่) @@ -299,6 +299,8 @@ market.trades.tooltip.candle.date=วันที่: offerbook.createOffer=สร้างข้อเสนอ offerbook.takeOffer=รับข้อเสนอ +offerbook.takeOfferToBuy=Take offer to buy {0} +offerbook.takeOfferToSell=Take offer to sell {0} offerbook.trader=Trader (เทรดเดอร์) offerbook.offerersBankId=รหัสธนาคารของผู้สร้าง (BIC / SWIFT): {0} offerbook.offerersBankName=ชื่อธนาคารของผู้สร้าง: {0} @@ -323,7 +325,7 @@ offerbook.removeOffer.success=นำข้อเสนอออกเรีย offerbook.removeOffer.failed=เกิดข้อผิดพลาดในการลบข้อเสนอ:\n{0} offerbook.deactivateOffer.failed=เกิดข้อผิดพลาดในการยกเลิกข้อเสนอ: \n{0} offerbook.activateOffer.failed=การเผยแพร่ข้อเสนอล้มเหลว: \n{0} -offerbook.withdrawFundsHint=คุณสามารถถอนเงินที่คุณชำระมาได้จาก {0} หน้าจอ +offerbook.withdrawFundsHint=คุณสามารถถอนเงินที่คุณชำระมาได้จาก {0} หน้าจอ offerbook.warning.noTradingAccountForCurrency.headline=ไม่มีบัญชีการซื้อขายสำหรับสกุลเงินที่เลือก offerbook.warning.noTradingAccountForCurrency.msg=คุณไม่มีบัญชีการค้าสำหรับสกุลเงินที่เลือก\nคุณต้องการสร้างข้อเสนอกับบัญชีซื้อขายที่มีอยู่ของคุณหรือไม่? @@ -335,7 +337,7 @@ offerbook.warning.offerBlocked=ข้อเสนอดังกล่าวถ offerbook.warning.currencyBanned=สกุลเงินที่ใช้ในข้อเสนอนั้นถูกบล็อกโดยนักพัฒนา Bisq\nสามารถอ่านข้อมูลเพิ่มเติมได้ที่ฟอรั่มของ Bisq offerbook.warning.paymentMethodBanned=วิธีการชำระเงินที่ใช้ในข้อเสนอนั้นถูกบล็อกโดยนักพัฒนา Bisq\nกรุณาเข้าไปอ่านที่ Forum ของ Bisq สำหรับข้อมูลเพิ่มเติม offerbook.warning.nodeBlocked=ที่อยู่ onion ของผู้ซื้อขายรายนั้นถูกบล็อกโดยนักพัฒนา Bisq\nอาจมีข้อบกพร่องที่ไม่ได้รับการจัดการ ซึ่งก่อให้เกิดปัญหาเมื่อรับข้อเสนอจากผู้ซื้อขายรายนั้น -offerbook.warning.tradeLimitNotMatching=บัญชีการชำระเงินของคุณถูกสร้างขึ้นเมื่อ {0} วันก่อน ขีดจำกัดทางการซื้อขายของคุณขึ้นอยู่กับอายุการใช้งานของบัญชีและนั่นทำให้การชำระเงินทางบัญชีของคุณไม่มีผล\n\nขีดจำกัด ทางการซื้อขายของคุณคือ: {1} \nข้อกำหนดทางการซื้อขายของข้อเสนอคือ: {2} .\n\nคุณไม่สามารถรับข้อเสนอนั้นได้ ณ ขณะนี้ คุณจะสามารถซื้อขายได้เมื่อบัญชีของคุณมีอายุนานเกินกว่า 2 เดือน +offerbook.warning.tradeLimitNotMatching=บัญชีการชำระเงินของคุณถูกสร้างขึ้นเมื่อ {0} วันก่อน ขีดจำกัดทางการซื้อขายของคุณขึ้นอยู่กับอายุการใช้งานของบัญชีและนั่นทำให้การชำระเงินทางบัญชีของคุณไม่มีผล\n\nขีดจำกัด ทางการซื้อขายของคุณคือ: {1} \nข้อกำหนดทางการซื้อขายของข้อเสนอคือ: {2} .\n\nคุณไม่สามารถรับข้อเสนอนั้นได้ ณ ขณะนี้ คุณจะสามารถซื้อขายได้เมื่อบัญชีของคุณมีอายุนานเกินกว่า 2 เดือน offerbook.info.sellAtMarketPrice=คุณจะขายในราคาตลาด (อัปเดตทุกนาที) @@ -376,8 +378,8 @@ createOffer.info.buyBelowMarketPrice=คุณจะจ่าย {0}% น้อ createOffer.warning.sellBelowMarketPrice=คุณจะได้รับ {0}% น้อยกว่าราคาตลาดในปัจจุบันเนื่องจากราคาข้อเสนอของคุณจะได้รับการอัพเดตอย่างต่อเนื่อง createOffer.warning.buyAboveMarketPrice=คุณจะต้องจ่ายเงิน {0}% มากกว่าราคาตลาดในปัจจุบันเนื่องจากราคาข้อเสนอของคุณจะได้รับการอัพเดตอย่างต่อเนื่อง createOffer.tradeFee.descriptionBTCOnly=ค่าธรรมเนียมการซื้อขาย -createOffer.tradeFee.descriptionBSQEnabled=Select trade fee currency -createOffer.tradeFee.fiatAndPercent=≈ {0} / {1} of trade amount +createOffer.tradeFee.descriptionBSQEnabled=เลือกสกุลเงินค่าธรรมเนียมในการเทรด +createOffer.tradeFee.fiatAndPercent=≈ {0} / {1} จำนวนการเทรด # new entries createOffer.placeOfferButton=รีวิว: ใส่ข้อเสนอไปยัง {0} บิตคอย @@ -516,7 +518,7 @@ portfolio.pending.step2_buyer.f2f=กรุณาติดต่อผู้ข portfolio.pending.step2_buyer.startPaymentUsing=เริ่มต้นการชำระเงินโดยใช้ {0} portfolio.pending.step2_buyer.amountToTransfer=จำนวนเงินที่จะโอน portfolio.pending.step2_buyer.sellersAddress=ที่อยู่ของผู้ขาย {0} -portfolio.pending.step2_buyer.buyerAccount=Your payment account to be used +portfolio.pending.step2_buyer.buyerAccount=บัญชีการชำระเงินที่ต้องการใข้งาน portfolio.pending.step2_buyer.paymentStarted=การชำระเงินเริ่มต้นแล้ว portfolio.pending.step2_buyer.warn=คุณยังไม่ได้ทำ {0} การชำระเงินของคุณ! \nโปรดทราบว่าการซื้อขายจะต้องดำเนินการโดย {1} มิฉะนั้นการค้าจะถูกตรวจสอบโดยผู้ไกล่เกลี่ย portfolio.pending.step2_buyer.openForDispute=การชำระเงินของคุณยังไม่เสร็จสิ้น!\nระยะเวลาสูงสุดสำหรับการซื้อขายได้ผ่านไปแล้ว\n\nโปรดติดต่ออนุญาผู้ไกล่เกลี่ยเพื่อเปิดข้อพิพาท @@ -528,13 +530,13 @@ portfolio.pending.step2_buyer.westernUnionMTCNInfo.headline=ส่ง MTCN (ห portfolio.pending.step2_buyer.westernUnionMTCNInfo.msg=คุณต้องส่ง MTCN (หมายเลขติดตาม) และรูปใบเสร็จรับเงินทางอีเมลไปยังผู้ขาย BTC \nใบเสร็จจะต้องแสดงชื่อเต็ม เมือง ประเทศ และจำนวนเงินทั้งหมดของผู้ขาย อีเมลของผู้ขายคือ: {0} .\n\nคุณได้ส่ง MTCN และทำสัญญากับผู้ขายหรือไม่ portfolio.pending.step2_buyer.halCashInfo.headline=ส่งรหัส HalCash portfolio.pending.step2_buyer.halCashInfo.msg=คุณต้องส่งข้อความที่มีรหัส HalCash พร้อมกับ IDการค้า ({0}) ไปยังผู้ขาย BTC \nเบอร์โทรศัพท์มือถือของผู้ขาย คือ {1}\n\nคุณได้ส่งรหัสให้กับผู้ขายหรือยัง? -portfolio.pending.step2_buyer.fasterPaymentsHolderNameInfo=Some banks might require the receiver's name. The UK sort code and account number is sufficient for a Faster Payment transfer and the receivers name is not verified by any of the banks. +portfolio.pending.step2_buyer.fasterPaymentsHolderNameInfo=บางธนาคารอาจมีความประสงค์ขอชื่อผู้รับ รหัสอ้างอิงการจัดเรียงรหัสธนาคารในสหราชอาณาจักร (UK Sort Code) และเลขแอคเคาน์นั้นเพียงพอสำหรับการโอน Faster Payment และชื่อผู้รับจะไม่ได้รับการตรวจสอบจากธนาคารใดๆ portfolio.pending.step2_buyer.confirmStart.headline=ยืนยันว่าคุณได้เริ่มต้นการชำระเงินแล้ว portfolio.pending.step2_buyer.confirmStart.msg=คุณได้เริ่มต้นการ {0} การชำระเงินให้กับคู่ค้าของคุณแล้วหรือยัง portfolio.pending.step2_buyer.confirmStart.yes=ใช่ฉันได้เริ่มต้นการชำระเงินแล้ว portfolio.pending.step2_seller.waitPayment.headline=รอการชำระเงิน -portfolio.pending.step2_seller.f2fInfo.headline=Buyer's contact information +portfolio.pending.step2_seller.f2fInfo.headline=ข้อมูลการติดต่อของผู้ซื้อ portfolio.pending.step2_seller.waitPayment.msg=ธุรกรรมการฝากเงินมีการยืนยันบล็อกเชนอย่างน้อยหนึ่งรายการ\nคุณต้องรอจนกว่าผู้ซื้อ BTC จะเริ่มการชำระเงิน {0} portfolio.pending.step2_seller.warn=ผู้ซื้อ BTC ยังไม่ได้ทำ {0} การชำระเงิน\nคุณต้องรอจนกว่าผู้ซื้อจะเริ่มชำระเงิน\nหากการซื้อขายยังไม่เสร็จสิ้นในวันที่ {1} ผู้ไกล่เกลี่ยจะดำเนินการตรวจสอบ portfolio.pending.step2_seller.openForDispute=ผู้ซื้อของ BTC ยังไม่ได้ชำระเงิน! \nระยะเวลาสูงสุดที่อนุญาตสำหรับการซื้อขายผ่านไปแล้ว\nคุณสามารถรอต่อไปก่อนและให้เวลาซื้อขายเพิ่มขึ้นหรือติดต่อผู้ไกล่เกลี่ยเพื่อเปิดข้อพิพาท @@ -560,12 +562,12 @@ portfolio.pending.step3_buyer.warn.part1b=ที่ผู้ให้บริ portfolio.pending.step3_buyer.warn.part2=ผู้ขาย BTC ยังไม่ยืนยันการชำระเงินของคุณ\nโปรดตรวจสอบ {0} หากการส่งการชำระเงินสำเร็จแล้ว\nหากผู้ขาย BTC ไม่ยืนยันการรับเงินโดย {1} การซื้อขายจะถูกตรวจสอบโดยผู้ไกล่เกลี่ย portfolio.pending.step3_buyer.openForDispute=ผู้ขาย BTC ไม่ยืนยันการชำระเงินของคุณ! \nระยะเวลาสูงสุดสำหรับการซื้อขายได้ผ่านไปแล้ว\nคุณสามารถรอต่อไปอีกหน่อยและให้เวลาการซื้อขายเพิ่มขึ้นหรือติดต่อผู้ไกล่เกลี่ยเพื่อเปิดข้อพิพาท # suppress inspection "TrailingSpacesInProperty" -portfolio.pending.step3_seller.part=พันธมิตรการค้าของคุณยืนยันว่าเขาเป็นผู้ริเริ่ม {0} การชำระเงิน -portfolio.pending.step3_seller.altcoin.explorer=on your favorite {0} blockchain explorer -portfolio.pending.step3_seller.altcoin.wallet=at your {0} wallet -portfolio.pending.step3_seller.altcoin={0}Please check {1} if the transaction to your receiving address\n{2}\nhas already sufficient blockchain confirmations.\nThe payment amount has to be {3}\n\nYou can copy & paste your {4} address from the main screen after closing that popup. +portfolio.pending.step3_seller.part=พันธมิตรทางการค้าของคุณได้ยืนยันว่าพวกเขาได้เริ่มต้น {0} การชำระเงิน\n\n +portfolio.pending.step3_seller.altcoin.explorer=ผู้สำรวจบล็อกเชน {0} ที่ถูกใจของคุณ +portfolio.pending.step3_seller.altcoin.wallet=ณ กระเป๋าสตางค์ {0} ของคุณ +portfolio.pending.step3_seller.altcoin={0}โปรดตรวจสอบ {1} หากการทำธุรกรรมส่วนที่อยู่รับของคุณ\n{2}\nมีการยืนยันบล็อกเชนแล้วเรียบร้อย\nยอดการชำระเงินต้องเป็น {3}\n\nคุณสามารถคัดลอกและวาง {4} ข้อมูลที่อยู่ของคุณได้จากหน้าจอหลักหลังจากปิดหน้าต่างป๊อปอัพ portfolio.pending.step3_seller.postal={0} โปรดตรวจสอบว่าคุณได้รับ {1} ธนาณัติ \"US Postal Money Order \" จากผู้ซื้อ BTC แล้วหรือไม่ "\n\nID การซื้อขาย (\"เหตุผลในการชำระเงิน \"ข้อความ) ของธุรกรรมคือ: \"{2} \" -portfolio.pending.step3_seller.bank=พันธมิตรการค้าของคุณยืนยันว่าเขาเป็นผู้ริเริ่ม {0} การชำระเงิน\n\nโปรดไปที่หน้าธนาคารออนไลน์ของคุณและตรวจสอบว่าคุณได้รับ {1} จากผู้ซื้อ BTC แล้วหรือไม่ "\n\n ID การซื้อขาย (\"เหตุผลในการชำระเงิน \") ของธุรกรรมคือ: \"{2} \" \n +portfolio.pending.step3_seller.bank=พันธมิตรทางการค้าของคุณได้ยืนยันว่าพวกเขาได้เริ่มต้น {0} การชำระเงิน\n\nโปรดไปที่หน้าธนาคารออนไลน์ของคุณและตรวจสอบว่าคุณได้รับ {1} จากผู้ซื้อ BTC \n\nเลข ID การเทรด (\"เหตุผลในการชำระเงิน\" ข้อความ) ของการทำธุรกรรมคือ: \"{2}\"\n\n portfolio.pending.step3_seller.cash=เนื่องจากการชำระเงินผ่าน Cash Deposit (ฝากเงินสด) ผู้ซื้อ BTC จะต้องเขียน \"NO REFUND \" ในใบเสร็จรับเงินและให้แบ่งออกเป็น 2 ส่วนและส่งรูปถ่ายทางอีเมล\n\nเพื่อหลีกเลี่ยงความเสี่ยงจากการปฏิเสธการชำระเงิน ให้ยืนยันเฉพาะถ้าคุณได้รับอีเมลและหากคุณแน่ใจว่าใบเสร็จถูกต้องแล้ว\nถ้าคุณไม่แน่ใจ {0} portfolio.pending.step3_seller.moneyGram=ผู้ซื้อต้องส่งหมายเลขอนุมัติและรูปใบเสร็จรับเงินทางอีเมล\nใบเสร็จรับเงินต้องแสดงชื่อเต็มของคุณ ประเทศ รัฐ และจำนวนเงิน โปรดตรวจสอบอีเมลของคุณหากคุณได้รับหมายเลขการให้สิทธิ์\n\nหลังจากปิดป๊อปอัปคุณจะเห็นชื่อและที่อยู่ของผู้ซื้อ BTC เพื่อรับเงินจาก MoneyGram\n\nยืนยันเฉพาะใบเสร็จหลังจากที่คุณได้รับเงินเรียบร้อยแล้ว! portfolio.pending.step3_seller.westernUnion=ผู้ซื้อต้องส่ง MTCN (หมายเลขติดตาม) และรูปใบเสร็จรับเงินทางอีเมล\nใบเสร็จรับเงินต้องแสดงชื่อ เมือง ประเทศ และจำนวนเงินทั้งหมดไว้อย่างชัดเจน โปรดตรวจสอบอีเมลของคุณหากคุณได้รับ MTCN\n\nหลังจากปิดป๊อปอัปคุณจะเห็นชื่อและที่อยู่ของผู้ซื้อ BTC สำหรับการขอรับเงินจาก Western Union \n\nยืนยันเฉพาะใบเสร็จหลังจากที่คุณได้รับเงินเรียบร้อยแล้ว! @@ -609,7 +611,7 @@ portfolio.pending.step5_buyer.moveToBisqWallet=ย้ายเงินไปท portfolio.pending.step5_buyer.withdrawExternal=ถอนไปยัง wallet ภายนอก portfolio.pending.step5_buyer.alreadyWithdrawn=เงินทุนของคุณถูกถอนออกไปแล้ว\nโปรดตรวจสอบประวัติการทำธุรกรรม portfolio.pending.step5_buyer.confirmWithdrawal=ยืนยันคำขอถอนเงิน -portfolio.pending.step5_buyer.amountTooLow=จำนวนเงินที่โอนจะต่ำกว่าค่าธรรมเนียมการทำธุรกรรมและมูลค่า tx ที่เป็นไปได้ขั้นต่ำ (dust หน่วยเล็กสุดของ bitcoin) +portfolio.pending.step5_buyer.amountTooLow=จำนวนเงินที่โอนจะต่ำกว่าค่าธรรมเนียมการทำธุรกรรมและมูลค่าต่ำกว่าที่น่าจะเป็น (dust หน่วยเล็กสุดของ bitcoin) portfolio.pending.step5_buyer.withdrawalCompleted.headline=การถอนเสร็จสิ้น portfolio.pending.step5_buyer.withdrawalCompleted.msg=การซื้อขายที่เสร็จสิ้นของคุณจะถูกเก็บไว้ภายใต้ \"Portfolio (แฟ้มผลงาน) / ประวัติ\" \nคุณสามารถตรวจสอบการทำธุรกรรม Bitcoin ทั้งหมดภายใต้ \"เงิน / ธุรกรรม \" portfolio.pending.step5_buyer.bought=คุณได้ซื้อ @@ -670,7 +672,7 @@ funds.deposit.usedInTx=ใช้ใน {0} ธุรกรรม(ต่าง funds.deposit.fundBisqWallet=เติมเงิน Bisq wallet funds.deposit.noAddresses=ยังไม่มีการสร้างที่อยู่ของเงินฝาก funds.deposit.fundWallet=เติมเงินใน wallet ของคุณ -funds.deposit.withdrawFromWallet=Send funds from wallet +funds.deposit.withdrawFromWallet=ส่งเงินทุนจากกระเป๋าสตางค์ของคุณ funds.deposit.amount=จำนวนเงินใน BTC (ตัวเลือก) funds.deposit.generateAddress=สร้างที่อยู่ใหม่ funds.deposit.selectUnused=โปรดเลือกที่อยู่ที่ไม่ได้ใช้จากตารางด้านบนแทนที่จะสร้างที่อยู่ใหม่ @@ -705,10 +707,10 @@ funds.locked.locked=ถูกล็อคใน multisig สำหรับก funds.tx.direction.sentTo=ส่งไปยัง: funds.tx.direction.receivedWith=ได้รับโดย: -funds.tx.direction.genesisTx=จากจุดเริ่มต้น Genesis tx : -funds.tx.txFeePaymentForBsqTx=Miner fee for BSQ tx -funds.tx.createOfferFee=ผู้สร้างและค่าธรรมเนียม tx: {0} -funds.tx.takeOfferFee=ค่าธรรมเนียมผู้รับและ tx: {0} +funds.tx.direction.genesisTx=จากการทำธุรกรรมทั่วไป : +funds.tx.txFeePaymentForBsqTx=ค่าธรรมเนียมของนักขุดบิทคอยน์สำหรับการทำธุรกรรม BSQ +funds.tx.createOfferFee=ผู้สร้างและค่าธรรมเนียมการทำธุรกรรม: {0} +funds.tx.takeOfferFee=ค่าธรรมเนียมของผู้รับและการทำธุรกรรม: {0} funds.tx.multiSigDeposit=เงินฝาก Multisig (การรองรับหลายลายเซ็น): {0} funds.tx.multiSigPayout=การจ่ายเงิน Multisig (การรองรับหลายลายเซ็น): {0} funds.tx.disputePayout=การจ่ายเงินข้อพิพาท: {0} @@ -721,8 +723,8 @@ funds.tx.noTxAvailable=ไม่มีธุรกรรมใด ๆ funds.tx.revert=กลับสู่สภาพเดิม funds.tx.txSent=ธุรกรรมถูกส่งสำเร็จไปยังที่อยู่ใหม่ใน Bisq wallet ท้องถิ่นแล้ว funds.tx.direction.self=ส่งถึงตัวคุณเอง -funds.tx.daoTxFee=Miner fee for DAO tx -funds.tx.reimbursementRequestTxFee=Reimbursement request +funds.tx.daoTxFee=ค่าธรรมเนียมนักขุดสำหรับธุรกรรม DAO +funds.tx.reimbursementRequestTxFee=ยื่นคำขอการชำระเงินคืน funds.tx.compensationRequestTxFee=คำขอค่าสินไหมทดแทน @@ -785,7 +787,7 @@ settings.tab.about=เกี่ยวกับ setting.preferences.general=การตั้งค่าทั่วไป setting.preferences.explorer=ตัวค้นหาบล็อก Bitcoin setting.preferences.deviation=สูงสุด ส่วนเบี่ยงเบนจากราคาตลาด -setting.preferences.avoidStandbyMode=Avoid standby mode +setting.preferences.avoidStandbyMode=หลีกเลี่ยงโหมดแสตนบายด์ setting.preferences.deviationToLarge=ค่าที่สูงกว่า {0}% ไม่ได้รับอนุญาต setting.preferences.txFee=ค่าธรรมเนียมการทำรายการถอนเงิน (satoshis / byte) setting.preferences.useCustomValue=ใช้ค่าที่กำหนดเอง @@ -811,17 +813,17 @@ setting.preferences.resetAllFlags=รีเซ็ตทั้งหมด \"ไ setting.preferences.reset=ตั้งค่าใหม่ settings.preferences.languageChange=หากต้องการเปลี่ยนภาษากับทุกหน้าต้องทำการรีสตาร์ท settings.preferences.arbitrationLanguageWarning=ในกรณีที่มีข้อพิพาทโปรดทราบว่ากระบวนการผู้ไกล่เกลี่ยมีบทบาทในการจัดการ {0} -settings.preferences.selectCurrencyNetwork=Select network -setting.preferences.daoOptions=DAO options -setting.preferences.dao.resync.label=Rebuild DAO state from genesis tx -setting.preferences.dao.resync.button=Resync -setting.preferences.dao.resync.popup=After an application restart the BSQ consensus state will be rebuilt from the genesis transaction. -setting.preferences.dao.isDaoFullNode=Run Bisq as DAO full node -setting.preferences.dao.rpcUser=RPC username -setting.preferences.dao.rpcPw=RPC password -setting.preferences.dao.fullNodeInfo=For running Bisq as DAO full node you need to have Bitcoin Core locally running and configured with RPC and other requirements which are documented in ''{0}''. -setting.preferences.dao.fullNodeInfo.ok=Open docs page -setting.preferences.dao.fullNodeInfo.cancel=No, I stick with lite node mode +settings.preferences.selectCurrencyNetwork=เลือกเครือข่าย +setting.preferences.daoOptions=ตัวเลือก DAO +setting.preferences.dao.resync.label=สร้างสถานะ DAO ใหม่จากธุรกรรมต้นกำเนิด +setting.preferences.dao.resync.button=รีซิงค์ (Resync) +setting.preferences.dao.resync.popup=หลังจากแอพพลิเคชั่นรีสตาร์ทสถานะเอกฉันท์ BSQ จะถูกสร้างขึ้นมาใหม่จากการทำธุรกรรมในตอนต้น +setting.preferences.dao.isDaoFullNode=ใช้งาน Bisq ในแบบโหนด DAO full node +setting.preferences.dao.rpcUser=ชื่อผู้ใช้ RPC +setting.preferences.dao.rpcPw=รหัส RPC +setting.preferences.dao.fullNodeInfo=สำหรับการใช้งาน Bisq ในแบบโหนด DAO full node คุณจำเป็นต้องมี Bitcoin Core ในการใช้งานสำหรับพื้นที่เฉพาะ และกำหนดค่าด้วย RPC และข้อกำหนดอื่นๆ ซึงมีการบันทึกเอกสารใน ''{0}'' +setting.preferences.dao.fullNodeInfo.ok=เปิดหน้าเอกสาร +setting.preferences.dao.fullNodeInfo.cancel=ไม่ ฉันติดกับไลท์โหนดโหมด (lite node mode) settings.net.btcHeader=เครือข่าย Bitcoin settings.net.p2pHeader=เครือข่าย P2P @@ -865,7 +867,7 @@ settings.net.reSyncSPVAfterRestart=ไฟล์ SPV chain ถูกลบแล settings.net.reSyncSPVAfterRestartCompleted=การซิงค์เสร็จสมบูรณ์แล้ว โปรดรีสตาร์ทแอ็พพลิเคชั่น settings.net.reSyncSPVFailed=ไม่สามารถลบไฟล์ SPV chain ได้\nข้อผิดพลาด: {0} setting.about.aboutBisq=เกี่ยวกับ Bisq -setting.about.about=Bisq เป็นโครงการอิสระและเครือข่ายกระจายอำนาจของผู้ใช้ที่ต้องการแลกเงินบิตคอยกับสกุลเงินของประเทศหรือสกุลเงินดิจิตอลอื่นในรูปแบบการปกป้องข้อมูลส่วนบุคคล เรียนรู้เพิ่มเติมเกี่ยวกับ Bisq ในหน้าเว็บของโปรเจคของเรา +setting.about.about=Bisq เป็นโครงการอิสระโดยอำนวยความสะดวกในการแลกเงินบิตคอยน์กับสกุลเงินของประเทศต่างๆ (และสกุลเงินดิจิตอลอื่นๆ) ผ่านเครือข่ายเข้าถึงกระจายอำนาจอย่างถัดเทียมในรูปแบบการปกป้องข้อมูลส่วนบุคคล เรียนรู้เพิ่มเติมเกี่ยวกับ Bisq ในหน้าเว็บของโปรเจคของเรา setting.about.web=หน้าเว็บ Bisq setting.about.code=โค๊ดแหล่งที่มา setting.about.agpl=ใบอนุญาต AGPL @@ -892,12 +894,12 @@ setting.about.subsystems.val=เวอร์ชั่นของเครือ account.tab.arbitratorRegistration=การลงทะเบียนผู้ไกล่เกลี่ย account.tab.account=บัญชี account.info.headline=ยินดีต้อนรับสู่บัญชี Bisq ของคุณ -account.info.msg=ที่นี่คุณสามารถตั้งค่าบัญชีการซื้อขายสกุลเงินประจำชาติและ altcoins (เหรียญทางเลือก) และเลือกผู้ไกล่เกลี่ย และสำรองข้อมูล wallet และบัญชีของคุณได้\n\nกระเป๋าสตางค์ Bitcoin ที่ว่างเปล่าถูกสร้างขึ้นในครั้งแรก ณ. ตอนที่คุณเริ่มต้นใช้งาน Bisq\nเราขอแนะนำให้คุณป้อนรหัสโค้ดการแบล็กอัพข้อมูลของ กระเป๋าสตางค์ Bitcoin (ดูปุ่มด้านซ้าย) และเพิ่มรหัสผ่านก่อนการป้อนเงิน การฝากและถอนเงินของ Bitcoin จะอยู่ในส่วนของ \ "เงิน \"\n\nความเป็นส่วนตัวและความปลอดภัย: \nBisq คือการแลกเปลี่ยนแบบกระจายอำนาจซึ่งหมายความว่าข้อมูลทั้งหมดของคุณจะถูกเก็บไว้ในคอมพิวเตอร์ของคุณไม่มีเซิร์ฟเวอร์และเราไม่มีสิทธิ์เข้าถึงข้อมูลส่วนบุคคล เงินทุนหรือแม้กระทั่งที่อยู่ IP ของคุณ และข้อมูล เช่น หมายเลขบัญชีธนาคาร altcoin (เหรียญทางเลือก) และที่อยู่ Bitcoin ฯลฯ ข้อมูลนั้นจะใช้ร่วมกับคู่ค้าของคุณเพื่อตอบสนองธุรกิจการซื้อขายที่คุณดำเนินการเท่านั้น (ในกรณีที่มีข้อพิพาทผู้ไกล่เกลี่ยจะเห็นข้อมูลเช่นเดียวกับ ผู้ค้าของคุณ) +account.info.msg=ที่นี่คุณสามารถตั้งค่าบัญชีการซื้อขายสกุลเงินประจำชาติและ altcoins (เหรียญทางเลือก) และเลือกผู้ไกล่เกลี่ย และสำรองข้อมูล wallet และบัญชีของคุณได้\n\nกระเป๋าสตางค์ Bitcoin ที่ว่างเปล่าถูกสร้างขึ้นในครั้งแรก ณ. ตอนที่คุณเริ่มต้นใช้งาน Bisq\nเราขอแนะนำให้คุณป้อนรหัสโค้ดการแบล็กอัพข้อมูลของ กระเป๋าสตางค์ Bitcoin (ดูปุ่มด้านซ้าย) และเพิ่มรหัสผ่านก่อนการป้อนเงิน การฝากและถอนเงินของ Bitcoin จะอยู่ในส่วนของ \"เงิน \"\n\nความเป็นส่วนตัวและความปลอดภัย: \nBisq คือการแลกเปลี่ยนแบบกระจายอำนาจซึ่งหมายความว่าข้อมูลทั้งหมดของคุณจะถูกเก็บไว้ในคอมพิวเตอร์ของคุณไม่มีเซิร์ฟเวอร์และเราไม่มีสิทธิ์เข้าถึงข้อมูลส่วนบุคคล เงินทุนหรือแม้กระทั่งที่อยู่ IP ของคุณ และข้อมูล เช่น หมายเลขบัญชีธนาคาร altcoin (เหรียญทางเลือก) และที่อยู่ Bitcoin ฯลฯ ข้อมูลนั้นจะใช้ร่วมกับคู่ค้าของคุณเพื่อตอบสนองธุรกิจการซื้อขายที่คุณดำเนินการเท่านั้น (ในกรณีที่มีข้อพิพาทผู้ไกล่เกลี่ยจะเห็นข้อมูลเช่นเดียวกับ ผู้ค้าของคุณ) account.menu.paymentAccount=บัญชีสกุลเงินของประเทศ account.menu.altCoinsAccountView=บัญชี Altcoin (เหรียญทางเลือก) account.menu.password=รหัส Wallet -account.menu.seedWords=รหัสลับ Wallet +account.menu.seedWords=รหัสลับ Wallet account.menu.backup=การสำรองข้อมูล account.menu.notifications=การแจ้งเตือน @@ -926,10 +928,10 @@ account.arbitratorSelection.minOne=คุณต้องมีผู้ไกล account.altcoin.yourAltcoinAccounts=บัญชี altcoin (เหรียญทางเลือก) ของคุณ account.altcoin.popup.wallet.msg=โปรดตรวจสอบว่าคุณทำตามข้อกำหนดสำหรับการใช้ {0} wallet ตามที่อธิบายไว้ใน {1} หน้าเว็บเพจ\nการใช้ wallet จากการแลกเปลี่ยนแบบส่วนกลางที่คุณไม่ได้รับคีย์ภายใต้การควบคุมของคุณ หรือ ใช้ซอฟต์แวร์ wallet ที่ไม่สามารถใช้งานร่วมกันได้อาจทำให้สูญเสียเงินได้!\nผู้ไกล่เกลี่ยไม่ได้เป็น {2} ผู้เชี่ยวชาญและไม่สามารถช่วยในกรณีดังกล่าวได้ account.altcoin.popup.wallet.confirm=ฉันเข้าใจและยืนยันว่าฉันรู้ว่า wallet ใดที่ฉันต้องการใช้ -account.altcoin.popup.xmr.msg=หากคุณต้องการซื้อขาย XMR (เหรียญ Monero) ใน Bisq โปรดตรวจสอบให้แน่ใจว่าคุณเข้าใจและปฏิบัติตามข้อกำหนดต่อไปนี้:\n\nสำหรับการส่ง XMR คุณจำเป็นต้องใช้ wallet ของ Monero GUI อย่างเป็นทางการหรือ Monero wallet แบบธรรมดา พร้อมกับเปิดใช้งานการเก็บค่าสถานะการเก็บข้อมูล - tx-info ไว้ (ค่าเริ่มต้นในเวอร์ชั่นใหม่) \nโปรดตรวจสอบว่าคุณสามารถเข้าถึงคีย์ tx (ใช้คำสั่ง get_tx_key ใน simplewallet) ตามที่ต้องการในกรณีของข้อพิพาทเพื่อให้อนุญาโตตุลาการ ตรวจสอบการถ่ายโอน XMR ด้วยเครื่องมือ checktx XMR (http://xmr.llcoins.net/checktx.html) .\nที่ตามปกติแล้วนักสำรวจบล็อกจะไม่สามารถตรวจสอบการโอนได้\n\nคุณจำเป็นต้องให้ข้อมูลแก่ผู้ไกล่เกลี่ยดังต่อไปนี้ในกรณีที่เกิดข้อพิพาท: \n- คีย์ส่วนตัว tx\n- การทำธุรกรรม hash (ฟังก์ชันแฮช)\n- ที่อยู่สาธารณะของผู้รับ\n\nหากคุณไม่สามารถให้ข้อมูลข้างต้นหรือหากคุณใช้ wallet ที่เข้ากันไม่ได้อาจทำให้เกิดกรณีการสูญเสียการพิพาท หรือยกฟ้องการพิพาทไป ผู้ส่ง XMR มีหน้าที่รับผิดชอบในการตรวจสอบการส่ง XMR ไปยังผู้ัไกล่เกลี่ยในกรณีที่มีข้อพิพาท\n\nไม่จำเป็นต้องมี ID การชำระเงิน เพียงแค่ที่อยู่สาธารณะตามปกติก็สามารถดำเนินการได้\n\nหากคุณไม่แน่ใจเกี่ยวกับกระบวนการดังกล่าวโปรดไปที่ฟอรัม Monero (https://forum.getmonero.org) เพื่อหาข้อมูลเพิ่มเติม -account.altcoin.popup.blur.msg=If you want to trade BLUR on Bisq please be sure you understand and fulfill the following requirements:\n\nTo send BLUR you must use the Blur Network CLI or GUI Wallet. \n\nIf you are using the CLI wallet, a transaction hash (tx ID) will be displayed after a transfer is sent. You must save this information. Immediately after sending the transfer, you must use the command 'get_tx_key' to retrieve the transaction private key. If you fail to perform this step, you may not be able to retrieve the key later. \n\nIf you are using the Blur Network GUI Wallet, the transaction private key and transaction ID can be found conveniently in the "History" tab. Immediately after sending, locate the transaction of interest. Click the "?" symbol in the lower-right corner of the box containing the transaction. You must save this information. \n\nIn the event that arbitration is necessary, you must present the following to an arbitrator: 1.) the transaction ID, 2.) the transaction private key, and 3.) the recipient's address. The arbitrator will then verify the BLUR transfer using the Blur Transaction Viewer (https://blur.cash/#tx-viewer).\n\nIf you cannot provide the required information to the arbitrator, you will lose the dispute. In all cases of dispute, the BLUR sender bears 100% of the burden of responsiblity in verifying transactions to an arbitrator. \n\nIf you do not understand these requirements, do not trade on Bisq. First, seek help at the Blur Network Discord (https://discord.gg/dMWaqVW). -account.altcoin.popup.ccx.msg=ถ้าคุณต้องการซื้อขาย CCX บน Bisq โปรดแน่ใจว่าคุณเข้าใจข้อกำหนดต่อไปนี้:\n\nในการส่ง CCX คุณต้องใช้กระเป๋าสตางค์ลับ (Conceal) อย่างเป็นทางการทั้ง CLI หรือ GUI หลังจากส่งการชำระเงินโอนแล้วกระเป๋าสตางค์\nแสดงคีย์ลับการทำธุรกรรม คุณต้องบันทึกข้อมูลพร้อมกับแฮชธุรกรรม (ID) และที่อยู่สาธารณะของผู้รับ\nในกรณีที่จำเป็นสำหรับอนุญาโตตุลาการ ในกรณีเช่นนี้คุณต้องให้ทั้งสามคนกับผู้ชี้ขาด\nยืนยันการถ่ายโอนข้อมูล CCX โดยใช้ Conceal Transaction Viewer (https://explorer.conceal.network/txviewer)\nเนื่องจาก Conceal เป็นเหรียญความเป็นส่วนตัว ผู้สำรวจบล็อคไม่สามารถยืนยันการโอนได้\n\nหากคุณไม่สามารถให้ข้อมูลที่จำเป็นแก่ผู้ไกล่เกลี่ยได้คุณจะสูญเสียกรณีโต้แย้ง\nหากคุณไม่บันทึกคีย์ลับธุรกรรมไว้ในทันทีหลังจากที่โอน CCX แล้ว มันจะไม่สามารถกู้คืนได้ในภายหลัง\nหากคุณไม่เข้าใจข้อกำหนดเหล่านี้ โปรดขอความช่วยเหลือที่ความ Conceal discord (http://discord.conceal.network) -account.altcoin.popup.drgl.msg=Trading Dragonglass on Bisq requires that you understand and fulfill the following requirements:\n\nBecause of the privacy Dragonglass provides a transaction is not verifyable on the public blockchain. If required you can prove your payment thru use of your TXN-Private-Key.\nThe TXN-Private Key is a one-time key automatically generated for every transaction that can only be accessed from within your DRGL wallet.\nEither by DRGL-wallet GUI (inside transaction details dialog) or by the Dragonglass CLI simplewallet (using command "get_tx_key").\n\nDRGL version 'Oathkeeper' and higher are REQUIRED for both.\n\nIn case of a dispute, you must provide the arbitrator the following data:\n- The TXN-Private key\n- The transaction hash\n- The recipient's public address\n\nVerification of payment can be made using the above data as inputs at \ (http://drgl.info/#check_txn).\n\nIf you cannot provide the above data or if you used an incompatible wallet it would result in losing the dispute case. The Dragonglass sender is responsible to be able to verify the DRGL transfer to the arbitrator in case of a dispute. Use of PaymentID is not required.\n\nIf you are unsure about any part of this process, visit Dragonglass on Discord (http://discord.drgl.info) for help. +account.altcoin.popup.xmr.msg=การซื้อขาย XMR บน Bisq ประสงค์ให้คุณเข้าใจและปฏิบัติตามข้อกำหนดดังต่อไปนี้:\n\nสำหรับการส่ง XMR, คุณจำเป็นต้องใช้กระเป๋าสตางค์ทางการ Monero GUI wallet หรือกระเป๋าสตางค์ Monero CLI ด้วย store-tx-info flag (ตั้งค่าในเวอร์ชั่นใหม่). โปรดมั่นใจว่าคุณสามารถเข้าถึงคีย์ธุรกรรมในกรณีเกิดเหตุการณ์ข้อพิพาท\nmonero-wallet-cli (ใข้คำสั่ง get_tx_key)\nmonero-wallet-gui (ไปที่หน้าประวัติและคลิกบนปุ่ม (P) สำหรับหลักฐานการชำระเงิน)\n\nนอกจากนี้ การใช้วิธีการทำธุรกรรม XMR ในการพิสูจน์หลักฐาน (https://xmr.llcoins.net/checktx.html) ยังสามารถทำด้วยวิธีกระเป๋าสตางค์ภายใน in-wallet ได้เช่นกัน\nmonero-wallet-cli : กำลังใช้คำสั่ง (check_tx_key).\nmonero-wallet-gui : บน the Advanced > หน้าพิสูจน์/ตรวจสอบ\nสำหรับผู้สำรวจบล็อกทั่วไป การโอนเงินไม่สามารถพิสูจน์หลักฐานได้ \n\nคุณสามารถนำข้อมูลดังต่อไปนี้ยื่นให้แก่ผู้ไกล่เกลี่ยในกรณีข้อพิพาทได้:\n- คีย์ส่วนตัวของการทำธุรกรรม\n- แฮชของธุรกรรม\n- ที่อยู่สาธารณะของผู้รับ\n\nความล้มเหลวในการยื่นข้อมูลข้างต้น หรือเมื่อคุณใช้กระเป๋าสตางค์ที่ไม่เหมาะสมจะส่งผลให้คุณสูญเสียกรณีการพิพาทได้ ผู้ส่ง XMR มีหน้าที่ยื่นหลักฐานพิสูจน์การโอนเงิน XMR ให้กับผู้ไกล่เกลี่ยเมื่อมีกรณีข้อพิพาทเกิดขึ้น\n\nไม่จำเป็นต้องมี ID การชำระเงิน เพียงแค่ที่อยู่สาธารณะตามปกติก็สามารถดำเนินการได้หากคุณไม่แน่ใจเกี่ยวกับกระบวนการดังกล่าวโปรดไปที่ฟอรัม (https://www.getmonero.org/resources/user-guides/prove-payment.html) หรือฟอรัม Monero (https://forum.getmonero.org) เพื่อค้นหาข้อมูลเพิ่มเติม +account.altcoin.popup.blur.msg=หากคุณต้องการที่จะเทรด BLUR บน Bisq โปรดมั่นใจว่าคุณเข้าใจและทำตามข้อกำหนดดังกล่าว:ในการส่ง BLUR คุณต้องใช้ Blur Network CLI or GUI Wallet. หากคุณกำลังใช้งาน CLI wallet, แฮชธุรกรรม (tx ID) จะมีการแสดงผลหลังจากการโอนย้ายได้ถูกส่งแล้ว คุณต้องบันทึกข้อมูลนี้ไว้ และเมื่อคุณมีการโอนย้าย ณ เดี๋ยวนั้น คุณต้องใช้คำสั่ง 'get_tx_key' ในการเรียกคืนการทำธุรกรรมคีย์ส่วนตัว หากคุณไม่ได้ปฏิบัติในขั้นตอนนี้ คุณอาจไม่สามารถเรียกคืนข้อมูลดังกล่าวในภายหลังได้หากคุณกำลังใช้งาน Blur Network GUI Wallet, ธุรกรรม คีย์ส่วนตัวและธุรกรรม ID สามารถถูกค้นหาได้ง่ายในหน้า "ประวัติ" หลังจากที่ส่ง ณ เดี๋ยวนั้น ระบุตำแหน่งรายการที่น่าสนใจ คลิกสัญลักษณ์ "?" ในมุมขวาด้านล่างของกล่องที่มีรายการอยู่ และคุณต้องทำการบันทึกข้อมูลนี้ไว้ในรายการที่จำเป็นต้องมีการไกล่เกลี่ย คุณต้องเสนอรายการดังต่อไปนี้ต่อผู้ไกล่เกลี่ย: 1.) ID การทำธุรกรรม 2.) คีย์ส่วนตัวในการทำธุรกรรม และ 3.) ที่อยู่ของผู้รับ ผู้ไกล่เกลี่ยจะมีการตรวจสอบข้อมูลการโอนถ่ายโดยการใช้งาน Blur Transaction Viewer (https://blur.cash/#tx-viewer) หากคุณไม่สามารถปฏิบัติตามข้อกำหนดต่อผู้ไกล่เกลี่ย คุณอาจไม่สามารถชนะข้อพิพาทได้ ในกรณีเคสของการพิพาททั้งหมด ผู้ส่ง BLUR สามารถค้ำประกันให้ได้ถึง 100% ในการพิสูจน์หลักฐานทางธุรกรรมให้กับผู้ไกล่เกลี่ยหากคุณไม่เข้าใจในเรื่องข้อควรปฏิบัติเหล่านี้ ได้โปรดอย่าทำการเทรดบน Bisq อันดับแรก คุณสามารถรขอความช่วยเหลือได้ทาง Blur Network Discord (https://discord.gg/dMWaqVW). +account.altcoin.popup.ccx.msg=การค้า CCX บน Bisq ประสงค์ให้คุณเข้าใจและปฏิบัติตามข้อกำหนดดังต่อไปนี้:\n\nในการส่ง CCX คุณต้องใช้กระเป๋าสตางค์ทางการ Conceal หรือ CLI or GUI หลังจากการส่งการชำระเงินแล้ว กระเป๋าสตางค์\nแสดงให้เห็นคีย์ลับธุรกรรม คุณต้องใช้มันพร้อมกันแฮชธุรกรรม (ID) และที่อยู่สาธารณะของผู้รับ\nในกรณีเมื่อมีอนุญาโตตุลาการมาเกี่ยวข้อง ซึ่งคุณจะต้องใช้ข้อมูลทั้งสามอย่างแก่ผู้ไกล่เกลี่ยผู้ซึ่ง\nพิสูจน์การโอนเงิน CCX ภายหลังโดยการใช้การตรวจสอบ Conceal Transaction Viewer (https://explorer.conceal.network/txviewer).\nเนื่องจาก Conceal เป็นเหรียญส่วนตัว ผู้สำรวจบล็อกไม่สามารถพิสูจน์หลักฐานการโอนเงินได้\n\nหากไม่สามารถยื่นข้อมูลดังกล่าวต่อผู้ไกล่เกลี่ยจะส่งผลต่อการสูญเสียการชนะกรณีการพิพาท\nหากคุณไม่สามารถบันทึกคีย์ลับธุรกรรมในทันทีหลังจากการโอนถ่าย CCX มันจะไม่สามารถกู้คืนข้อมูลได้ในภายหลัง\nหากคุณไม่เข้าใจข้อกำหนดเหล่านี้ สามารถขอความช่วยเหลือได้ที่ Conceal discord (http://discord.conceal.network). +account.altcoin.popup.drgl.msg=การค้า Dragonglass บน Bisq ประสงค์ให้คุณเข้าใจและปฏิบัติตามข้อกำหนดดังต่อไปนี้:\n\nเนื่องจากความเป็นส่วนตัวของ Dragonglass ธุรกรรมจะไม่สามารถพิสูจน์หลักฐานได้บนบล็อกเชนสาธารณะ หากแต่มีความประสงค์ คุณสามารถตรวจสอบหลักฐานการชำระเงินของคุณได้โดยการใช้คีย์ส่วนตัว TXN\nคีย์ส่วนตัว TXN เป็นคีย์แบบใช้ครั้งเดียวอัตโนมัติที่สร้างขึ้นสำหรับทุกการทำธุรกรรมที่มีการเข้าใช้งานจากกระเป๋าสตางค์ DRGL ของคุณ\nไม่ว่าจะเป็นกระเป๋าสตางค์ DRGL-wallet GUI (ไดอาล็อกรายละเอียดการธุรกรรมที่อยู่ภายใน) หรือโดยกระเป๋าสตางค์แบบปกติอย่าง Dragonglass CLI (ใช้คำสั่งเดียวกัน "get_tx_key").\n\nเวอร์ชั่น DRGL 'Oathkeeper' และแบบขั้นกว่ามีความจำเป็นอย่างมาก\n\nในกรณีข้อพิพาท คุณต้องยื่นข้อมูลดังต่อไปนี้ต่อผู้ไกล่เกลี่ย:\n- คีย์ส่วนตัว TXN\n- แฮชธุรกรรม\n- ที่อยู่สาธารณะของผู้รับ\nการพิสูจน์หลักฐานการชำระเงินจะมีผลสมบูรณ์ได้โดยการใข้ข้อมูลข้างต้นในการป้องข้อมูลเข้าที่ (http://drgl.info/#check_txn).\n\nความล้มเหลวในการยื่นข้อมูลข้างตน หรือการใช้กระเป๋าสตางค์ที่ไม่เหมาะสม จะส่งผลให้คุณสูญเสียการชนะการพิพาทได้ ผู้ส่ง Dragonglass มีหน้าที่แสดงหลักฐานของการโอนเงิน DRGL ต่อผู้ไกล่เกลี่ยในกรณีเกิดข้อพิพาม ไม่เป็นต้องใช้งานการชำเงินแบบ PaymentID \n\nหากคุณมีคำถามหรือข้อสงสัยวิธีการการใช้งาน สามารถขอความช่วยเหลือได้ที่ Dragonglass on Discord (http://discord.drgl.info) account.altcoin.popup.ZEC.msg=เมื่อใช้ {0} คุณสามารถใช้ที่อยู่ที่ถูกทำให้มองไม่เห็น (เริ่มต้นด้วย t) ไม่ใช่ที่อยู่ z (ส่วนตัว) เนื่องจากผู้ไกล่เกลี่ยจะไม่สามารถตรวจสอบธุรกรรมกับที่อยู่ z ได้ account.altcoin.popup.XZC.msg=เมื่อใช้ {0} คุณสามารถใช้ที่อยู่ที่ถูกทำให้มองเห็น (สามารถตรวจสอบย้อนกลับได้) ไม่ใช่ที่อยู่ที่ไม่สามารถระบุได้เนื่องจากผู้ไกล่เกลี่ยจะไม่สามารถตรวจสอบการทำรายการกับที่อยู่ที่ไม่สามารถเข้าถึงได้ที่ block explorer (นักสำรวจบล็อก) account.altcoin.popup.bch=Bitcoin Cash และ Bitcoin Clashic ได้รับความเสียหายจากการป้องกันการเล่นซ้ำ หากคุณใช้เหรียญเหล่านี้ ให้แน่ใจว่าคุณใช้ความระมัดระวังเพียงพอและเข้าใจผลกระทบทั้งหมด คุณอาจเผชิญกับความสูญเสียโดยการส่งเหรียญหนึ่งเหรียญโดยไม่ได้ตั้งใจและส่งเหรียญเดียวกันในห่วงโซ่อุปทานอื่น ๆ เนื่องจากเหล่า "airdrop coins" ใช้ฐานประวัติเดียวกันกับ blockchain Bitcoin นอกจากนี้ยังมีความเสี่ยงด้านความปลอดภัยและความเสี่ยงที่จะสูญเสียความเป็นส่วนตัวมากขึ้น\n\nโปรดอ่านที่ Bisq Forum เพิ่มเติมเกี่ยวกับหัวข้อ: https://forum.bisq.io/t/airdrop-coins-information-thread-bch-btg-bchc @@ -938,7 +940,7 @@ account.altcoin.popup.btg=เนื่องจาก Bitcoin Gold ใช้ป account.fiat.yourFiatAccounts=บัญชีสกุลเงินของคุณ account.backup.title=สำรองข้อมูล wallet -account.backup.location=สำรองข้อมูลไปที่ +account.backup.location=ที่ตั้งการสำรองข้อมูล account.backup.selectLocation=เลือกตำแหน่งการสำรอง account.backup.backupNow=สำรองข้อมูลตอนนี้ (สำรองข้อมูลไม่ได้เข้ารหัส!) account.backup.appDir=สารบบข้อมูลแอ็พพลิเคชั่น @@ -952,14 +954,14 @@ account.password.removePw.button=ลบรหัสผ่าน account.password.removePw.headline=ลบรหัสผ่านการป้องกันสำหรับ wallet account.password.setPw.button=ตั้งรหัสผ่าน account.password.setPw.headline=ตั้งรหัสผ่านการป้องกันสำหรับ wallet -account.password.info=With password protection you'll need to enter your password at application startup, when withdrawing bitcoin out of your wallet, and when restoring your wallet from seed words. +account.password.info=ด้วยระบบป้องกันรหัสผ่าน คุณจะต้องป้อนรหัส ณ จุดเริ่มต้นในแอพพลิเคชั่น เมื่อมีการถอนบิทคอยน์ และการกู้คืนกระเป๋าสตางค์ของคุณจาก seed words account.seed.backup.title=สำรองข้อมูล wallet โค้ดของคุณ account.seed.info=โปรดเขียนรหัสสำรองข้อมูล wallet และวันที่! คุณสามารถกู้ข้อมูล wallet ของคุณได้ทุกเมื่อด้วย รหัสสำรองข้อมูล wallet และวันที่\nรหัสสำรองข้อมูล ใช้ทั้ง BTC และ BSQ wallet\n\nคุณควรเขียนรหัสสำรองข้อมูล wallet ลงบนแผ่นกระดาษและไม่บันทึกไว้ในคอมพิวเตอร์ของคุณ\n\nโปรดทราบว่า รหัสสำรองข้อมูล wallet ไม่ได้แทนการสำรองข้อมูล\nคุณจำเป็นต้องสำรองข้อมูลสารบบแอ็พพลิเคชั่นทั้งหมดที่หน้าจอ \"บัญชี / การสำรองข้อมูล \" เพื่อกู้คืนสถานะแอ็พพลิเคชั่นและข้อมูลที่ถูกต้อง\nการนำเข้ารหัสสำรองข้อมูล wallet เป็นคำแนะนำเฉพาะสำหรับกรณีฉุกเฉินเท่านั้น แอพพลิเคชั่นจะไม่สามารถใช้งานได้หากไม่มีไฟล์สำรองฐานข้อมูลและคีย์ที่ถูกต้อง! account.seed.warn.noPw.msg=คุณยังไม่ได้ตั้งรหัสผ่าน wallet ซึ่งจะช่วยป้องกันการแสดงผลของรหัสสำรองข้อมูล wallet \n\nคุณต้องการแสดงรหัสสำรองข้อมูล wallet หรือไม่ account.seed.warn.noPw.yes=ใช่ และไม่ต้องถามฉันอีก -account.seed.enterPw=ป้อนรหัสผ่านเพื่อดูรหัสสำรองข้อมูล wallet -account.seed.restore.info=Please make a backup before applying restore from seed words. Be aware that wallet restore is only for emergency cases and might cause problems with the internal wallet database.\nIt is not a way for applying a backup! Please use a backup from the application data directory for restoring a previous application state. +account.seed.enterPw=ป้อนรหัสผ่านเพื่อดูรหัสสำรองข้อมูล wallet +account.seed.restore.info=โปรดสร้างตัวสำรองข้อมูลก่อนกระทำการกู้ Seed words ควรพึงระวังว่าการกู้คืนจากกระเป๋าสตางค์ใช้ในกรณีฉุกเฉินเท่านั้น และอาจทำให้เกิดปัญหาหลายประการกับฐานข้อมูลกระเป๋าสตางค์ภายใน account.seed.restore.ok=ตกลง ฉันเข้าใจและต้องการกู้คืนข้อมูล @@ -1022,7 +1024,7 @@ account.notifications.marketAlert.message.msg.above=สูงกว่า account.notifications.marketAlert.message.msg=ข้อเสนอใหม่ '{0} {1}' 'ด้วยราคา {2} ({3} {4} ราคาตลาด) และวิธีการชำระเงิน' '{5}' 'ถูกเผยแพร่ลงในหนังสือข้อเสนอ Bisq\nรหัสข้อเสนอพิเศษ: {6} account.notifications.priceAlert.message.title=การแจ้งเตือนราคาสำหรับ {0} account.notifications.priceAlert.message.msg=คุณได้รับการแจ้งเตือนราคาของคุณ {0} ราคาปัจจุบันคือ {1} {2} -account.notifications.noWebCamFound.warning=ไม่พบเว็บแคม\n\nโปรดใช้ตัวเลือกอีเมลเพื่อส่งรหัสโทเค็น (รหัสเหรียญ) และคีย์เข้ารหัสจากโทรศัพท์มือถือของคุณไปยังแอ็พพลิเคชัน Bisq +account.notifications.noWebCamFound.warning=ไม่พบเว็บแคม\n\nโปรดใช้ตัวเลือกอีเมลเพื่อส่งรหัสโทเค็น (รหัสเหรียญ) และคีย์เข้ารหัสจากโทรศัพท์มือถือของคุณไปยังแอพพลิเคชัน Bisq account.notifications.priceAlert.warning.highPriceTooLow=ราคาที่สูงกว่าต้องเป็นจำนวนที่มากเหนือราคาที่ต่ำกว่า account.notifications.priceAlert.warning.lowerPriceTooHigh=ราคาที่ต่ำกว่าต้องต่ำกว่าราคาที่สูงขึ้น @@ -1033,18 +1035,18 @@ account.notifications.priceAlert.warning.lowerPriceTooHigh=ราคาที่ # DAO #################################################################### -dao.tab.bsqWallet=กระเป๋าสตางค์ BSQ +dao.tab.bsqWallet=กระเป๋าสตางค์ BSQ dao.tab.proposals=การกำกับดูแลกิจการ -dao.tab.bonding=การกู้ยืม -dao.tab.proofOfBurn=Asset listing fee/Proof of burn +dao.tab.bonding=ค้ำประกัน +dao.tab.proofOfBurn=ค่าธรรมเนียมในการลงบันทึกรายการทรัพย์สิน/หลักฐานในการทำลายทิ้ง dao.paidWithBsq=จ่ายโดย BSQ -dao.availableBsqBalance=Available -dao.availableNonBsqBalance=ยอดคงเหลือที่ไม่ใช่ BSQ (BTC) -dao.unverifiedBsqBalance=Unverified (awaiting block confirmation) -dao.lockedForVoteBalance=Used for voting -dao.lockedInBonds=ถูกล็อคไว้ในการกู้ยืม -dao.totalBsqBalance=ยอด BSQ คงเหลือทั้งหมด +dao.availableBsqBalance=พร้อมใช้งาน +dao.availableNonBsqBalance=ยอดคงเหลือที่ไม่ใช่ BSQ (BTC) ซึ่งใช้งานได้ +dao.unverifiedBsqBalance=ไม่ได้รับการตรวจสอบ (รอการยืนยันการบล็อก) +dao.lockedForVoteBalance=ถูกใช้สำหรับการโหวต +dao.lockedInBonds=ถูกล็อคไว้ในการค้ำประกัน +dao.totalBsqBalance=ยอด BSQ คงเหลือทั้งหมด dao.tx.published.success=การทำธุรกรรมของคุณได้รับการเผยแพร่เรียบร้อยแล้ว dao.proposal.menuItem.make=เสนอคำขอ @@ -1059,7 +1061,7 @@ dao.cycle.proposal=ระยะเสนอ dao.cycle.blindVote=ขั้นตอนการลงคะแนนเสียงแบบไม่ระบุตัวตน dao.cycle.voteReveal=ขั้นตอนการประกาศผลโหวต dao.cycle.voteResult=ผลโหวต -dao.cycle.phaseDuration={0} blocks (≈{1}); Block {2} - {3} (≈{4} - ≈{5}) +dao.cycle.phaseDuration={0} บล็อก (≈{1}); บล็อก {2} - {3} (≈{4} - ≈{5}) dao.results.cycles.header=รอบ dao.results.cycles.table.header.cycle=วงจร @@ -1082,77 +1084,77 @@ dao.results.proposals.voting.detail.header=ผลโหวตสำหรับ dao.param.UNDEFINED=ไม่ได้กำหนด # suppress inspection "UnusedProperty" -dao.param.DEFAULT_MAKER_FEE_BSQ=BSQ maker fee +dao.param.DEFAULT_MAKER_FEE_BSQ=ค่าธรรมเนียมของผู้สร้าง BSQ # suppress inspection "UnusedProperty" -dao.param.DEFAULT_TAKER_FEE_BSQ=BSQ taker fee +dao.param.DEFAULT_TAKER_FEE_BSQ=ค่าธรรมเนียมของผู้รับ BSQ # suppress inspection "UnusedProperty" -dao.param.MIN_MAKER_FEE_BSQ=Min. BSQ maker fee +dao.param.MIN_MAKER_FEE_BSQ=ค่าธรรมเนียมของผู้สร้าง BSQ ขั้นต่ำ # suppress inspection "UnusedProperty" -dao.param.MIN_TAKER_FEE_BSQ=Min. BSQ taker fee +dao.param.MIN_TAKER_FEE_BSQ=ค่าธรรมเนียมของผู้รับ BSQ ขั้นต่ำ # suppress inspection "UnusedProperty" -dao.param.DEFAULT_MAKER_FEE_BTC=BTC maker fee +dao.param.DEFAULT_MAKER_FEE_BTC=ค่าธรรมเนียมผู้สร้าง BTC # suppress inspection "UnusedProperty" -dao.param.DEFAULT_TAKER_FEE_BTC=BTC taker fee +dao.param.DEFAULT_TAKER_FEE_BTC=ค่าธรรมเนียมผู้รับ BTC # suppress inspection "UnusedProperty" # suppress inspection "UnusedProperty" -dao.param.MIN_MAKER_FEE_BTC=Min. BTC maker fee +dao.param.MIN_MAKER_FEE_BTC=ค่าธรรมเนียมของผู้สร้าง BTC ขั้นต่ำ # suppress inspection "UnusedProperty" -dao.param.MIN_TAKER_FEE_BTC=Min. BTC taker fee +dao.param.MIN_TAKER_FEE_BTC=ค่าธรรมเนียมของผู้รับ BTC ขั้นต่ำ # suppress inspection "UnusedProperty" # suppress inspection "UnusedProperty" -dao.param.PROPOSAL_FEE=Proposal fee in BSQ +dao.param.PROPOSAL_FEE=ค่าธรรมเนียมข้อเสนอ BSQ # suppress inspection "UnusedProperty" -dao.param.BLIND_VOTE_FEE=Voting fee in BSQ +dao.param.BLIND_VOTE_FEE=ค่าธรรมเนียมในการโหวต BSQ # suppress inspection "UnusedProperty" -dao.param.COMPENSATION_REQUEST_MIN_AMOUNT=Compensation request min. BSQ amount +dao.param.COMPENSATION_REQUEST_MIN_AMOUNT=ยอดรวม BSQ ขั้นต่ำในการยื่นคำร้องขอค่าชดเชย # suppress inspection "UnusedProperty" -dao.param.COMPENSATION_REQUEST_MAX_AMOUNT=Compensation request max. BSQ amount +dao.param.COMPENSATION_REQUEST_MAX_AMOUNT=ยอดรวม BSQ ขั้นสูงสุดในการยื่นคำร้องขอค่าชดเชย # suppress inspection "UnusedProperty" -dao.param.REIMBURSEMENT_MIN_AMOUNT=Reimbursement request min. BSQ amount +dao.param.REIMBURSEMENT_MIN_AMOUNT=ยอดรวม BSQ ขั้นต่ำในการยื่นคำร้องขอการชำระเงินคืน # suppress inspection "UnusedProperty" -dao.param.REIMBURSEMENT_MAX_AMOUNT=Reimbursement request max. BSQ amount +dao.param.REIMBURSEMENT_MAX_AMOUNT=ยอดรวม BSQ ขั้นสูงสุดในการยื่นคำร้องขอการชำระเงินคืน # suppress inspection "UnusedProperty" -dao.param.QUORUM_GENERIC=Required quorum in BSQ for generic proposal +dao.param.QUORUM_GENERIC=องค์ประกอบที่จำเป็นสำหรับข้อเสนอทั่วไปใน BSQ # suppress inspection "UnusedProperty" -dao.param.QUORUM_COMP_REQUEST=Required quorum in BSQ for compensation request +dao.param.QUORUM_COMP_REQUEST=องค์ประกอบที่จำเป็นสำหรับค่าชดเชยใน BSQ # suppress inspection "UnusedProperty" -dao.param.QUORUM_REIMBURSEMENT=Required quorum in BSQ for reimbursement request +dao.param.QUORUM_REIMBURSEMENT=องค์ประกอบที่จำเป็นสำหรับการชำระเงินคืนใน BSQ # suppress inspection "UnusedProperty" -dao.param.QUORUM_CHANGE_PARAM=Required quorum in BSQ for changing a parameter +dao.param.QUORUM_CHANGE_PARAM=องค์ประกอบที่จำเป็นสำหรับการเปลี่ยนพารามิเตอร์ใน BSQ # suppress inspection "UnusedProperty" -dao.param.QUORUM_REMOVE_ASSET=Required quorum in BSQ for removing an asset +dao.param.QUORUM_REMOVE_ASSET=องค์ประกอบที่จำเป็นสำหรับในการในถอดถอนทรัพย์สินใน BSQ # suppress inspection "UnusedProperty" -dao.param.QUORUM_CONFISCATION=Required quorum in BSQ for a confiscation request +dao.param.QUORUM_CONFISCATION=องค์ประกอบที่จำเป็นสำหรับในการยื่นคำร้องต่อการยึดทรัพย์ใน BSQ # suppress inspection "UnusedProperty" -dao.param.QUORUM_ROLE=Required quorum in BSQ for bonded role requests +dao.param.QUORUM_ROLE=องค์ประกอบที่จำเป็นสำหรับใน BSQ ในการยื่นคำขอรับประกัน # suppress inspection "UnusedProperty" -dao.param.THRESHOLD_GENERIC=Required threshold in % for generic proposal +dao.param.THRESHOLD_GENERIC=องค์ประกอบของเทรสโฮลด์คิดเป็น % สำหรับข้อเสนอทั่วไป # suppress inspection "UnusedProperty" -dao.param.THRESHOLD_COMP_REQUEST=Required threshold in % for compensation request +dao.param.THRESHOLD_COMP_REQUEST=องค์ประกอบของเทรสโฮลด์คิดเป็น % สำหรับการยื่นคำขอค่าชดเชย # suppress inspection "UnusedProperty" -dao.param.THRESHOLD_REIMBURSEMENT=Required threshold in % for reimbursement request +dao.param.THRESHOLD_REIMBURSEMENT=องค์ประกอบของเทรสโฮลด์คิดเป็น % สำหรับการชำระเงินคืน # suppress inspection "UnusedProperty" -dao.param.THRESHOLD_CHANGE_PARAM=Required threshold in % for changing a parameter +dao.param.THRESHOLD_CHANGE_PARAM=องค์ประกอบของเทรสโฮลด์คิดเป็น % สำหรับการเปลี่ยนพารามิเตอร์ # suppress inspection "UnusedProperty" -dao.param.THRESHOLD_REMOVE_ASSET=Required threshold in % for removing an asset +dao.param.THRESHOLD_REMOVE_ASSET=องค์ประกอบของเทรสโฮลด์คิดเป็น % สำหรับการถอดถอนสินทรัพย์ # suppress inspection "UnusedProperty" -dao.param.THRESHOLD_CONFISCATION=Required threshold in % for a confiscation request +dao.param.THRESHOLD_CONFISCATION=องค์ประกอบของเทรสโฮลด์คิดเป็น % สำหรับการยื่นคำร้องของการยึดทรัพย์ # suppress inspection "UnusedProperty" -dao.param.THRESHOLD_ROLE=Required threshold in % for bonded role requests +dao.param.THRESHOLD_ROLE=องค์ประกอบของเทรสโฮลด์คิดเป็น % สำหรับการร้องขอรับประกัน # suppress inspection "UnusedProperty" dao.param.RECIPIENT_BTC_ADDRESS=ที่อยู่ BTC ของผู้รับ: # suppress inspection "UnusedProperty" -dao.param.ASSET_LISTING_FEE_PER_DAY=Asset listing fee per day +dao.param.ASSET_LISTING_FEE_PER_DAY=ค่าธรรมเนียมในการลงบันทึกรายการทรัพย์สินต่อวัน # suppress inspection "UnusedProperty" -dao.param.ASSET_MIN_VOLUME=Min. trade volume +dao.param.ASSET_MIN_VOLUME=ขนาดการเทรดขั้นต่ำ -dao.param.currentValue=Current value: {0} +dao.param.currentValue=มูลค่าปัจจุบัน: {0} dao.param.blocks={0} บล็อก # suppress inspection "UnusedProperty" @@ -1186,20 +1188,20 @@ dao.results.votes.table.header.stake=Stake (เหรียญที่ล็อ dao.results.votes.table.header.merit=ที่ได้รับ dao.results.votes.table.header.vote=โหวต -dao.bond.menuItem.bondedRoles=บทบาทของการกู้ยืม -dao.bond.menuItem.reputation=ชื่อเสียงในการขอกู้ยืม -dao.bond.menuItem.bonds=Bonds +dao.bond.menuItem.bondedRoles=บทบาทของการประกัน +dao.bond.menuItem.reputation=กิตติศัพท์ในการค้ำประกัน +dao.bond.menuItem.bonds=สัญญาผูกมัด -dao.bond.dashboard.bondsHeadline=การกู้ของ BSQ +dao.bond.dashboard.bondsHeadline=การประกัน BSQ dao.bond.dashboard.lockupAmount=เงินทุนที่ล็อค dao.bond.dashboard.unlockingAmount=การปลดล็อกเงิน (รอจนกว่าเวลาล็อคหมด) -dao.bond.reputation.header=Lockup a bond for reputation -dao.bond.reputation.table.header=My reputation bonds +dao.bond.reputation.header=ล็อคหลักประกันสำหรับมาตรฐานกิตติศัพท์ความน่าเชื่อถือ +dao.bond.reputation.table.header=หลักประกันกิตติศัพท์ของฉัน dao.bond.reputation.amount=จำนวน BSQ เพื่อล็อคสิทธิ์ในการโหวต dao.bond.reputation.time=ปลดล็อกเวลาในบล็อก -dao.bond.reputation.salt=Salt +dao.bond.reputation.salt=ข้อมูลแบบสุ่ม dao.bond.reputation.hash=Hash dao.bond.reputation.lockupButton=ล็อค dao.bond.reputation.lockup.headline=ยืนยันล็อคการทำรายการ @@ -1207,14 +1209,14 @@ dao.bond.reputation.lockup.details=ล็อคจำนวน: {0}\nล็อ dao.bond.reputation.unlock.headline=ยืนยันการปลดล็อกธุรกรรม dao.bond.reputation.unlock.details=จำนวนที่ปลดล็อค: {0}\nเวลาในการล็อค: {1} บล็อก (s)\n\nคุณแน่ใจหรือไม่ว่าต้องการดำเนินการต่อ -dao.bond.allBonds.header=All bonds +dao.bond.allBonds.header=การค้ำประกันทั้งหมด -dao.bond.bondedReputation=ชื่อเสียงในการขอกู้ยืม -dao.bond.bondedRoles=บทบาทของการกู้ยืม +dao.bond.bondedReputation=กิตติศัพท์ในการค้ำประกัน +dao.bond.bondedRoles=ตำแหน่งในการค้ำประกัน dao.bond.details.header=รายละเอียดบทบาทและหน้าที่ dao.bond.details.role=บทบาท -dao.bond.details.requiredBond=ต้องได้รับการกู้ยืม BSQ +dao.bond.details.requiredBond=ต้องได้รับการประกัน BSQ dao.bond.details.unlockTime=ปลดล็อกเวลาในบล็อก dao.bond.details.link=เชื่อมโยงกับคำอธิบายหลัก dao.bond.details.isSingleton=สามารถรับได้ในจำนวนที่หลากหลายของผู้ถือหลัก @@ -1222,123 +1224,123 @@ dao.bond.details.blocks={0} บล็อก dao.bond.table.column.name=ชื่อ dao.bond.table.column.link=ลิงค์ -dao.bond.table.column.bondType=Bond type +dao.bond.table.column.bondType=ประเภทของการประกัน dao.bond.table.column.details=รายละเอียด -dao.bond.table.column.lockupTxId=ล็อค Tx ID -dao.bond.table.column.bondState=สถานะการกู้ยืม +dao.bond.table.column.lockupTxId=ล็อคการทำธุรกรรม ID +dao.bond.table.column.bondState=สถานะการประกัน dao.bond.table.column.lockTime=ล็อคเวลา -dao.bond.table.column.lockupDate=Lockup date +dao.bond.table.column.lockupDate=ล็อควันที่ dao.bond.table.button.lockup=ล็อค dao.bond.table.button.unlock=ปลดล็อค dao.bond.table.button.revoke=เพิกถอน # suppress inspection "UnusedProperty" -dao.bond.bondState.READY_FOR_LOCKUP=ยังไม่ได้กู้ยืม +dao.bond.bondState.READY_FOR_LOCKUP=ยังไม่ได้ประกัน # suppress inspection "UnusedProperty" -dao.bond.bondState.LOCKUP_TX_PENDING=Lockup pending +dao.bond.bondState.LOCKUP_TX_PENDING=รอดำเนินการล็อค # suppress inspection "UnusedProperty" -dao.bond.bondState.LOCKUP_TX_CONFIRMED=การกู้ยืมที่ล็อคไว้ +dao.bond.bondState.LOCKUP_TX_CONFIRMED=การประกันได้ล็อคไว้ # suppress inspection "UnusedProperty" -dao.bond.bondState.UNLOCK_TX_PENDING=Unlock pending +dao.bond.bondState.UNLOCK_TX_PENDING=รอปลดล็อค # suppress inspection "UnusedProperty" -dao.bond.bondState.UNLOCK_TX_CONFIRMED=Unlock tx confirmed +dao.bond.bondState.UNLOCK_TX_CONFIRMED=ปลดล็อคการดำเนินงานสำเร็จ # suppress inspection "UnusedProperty" dao.bond.bondState.UNLOCKING=กำลังปลดล็อกการกู้ยืม # suppress inspection "UnusedProperty" -dao.bond.bondState.UNLOCKED=ปลดล็อคการกู้ยืมแล้ว +dao.bond.bondState.UNLOCKED=การประกันปลดล็อคแล้ว # suppress inspection "UnusedProperty" -dao.bond.bondState.CONFISCATED=Bond confiscated +dao.bond.bondState.CONFISCATED=หลักค้ำประกันถูกยึด # suppress inspection "UnusedProperty" -dao.bond.lockupReason.BONDED_ROLE=บทบาทการกู้ยืม +dao.bond.lockupReason.BONDED_ROLE=บทบาทการประกัน # suppress inspection "UnusedProperty" -dao.bond.lockupReason.REPUTATION=ชื่อเสียงในการขอกู้ยืม +dao.bond.lockupReason.REPUTATION=กิตติศัพท์ในการประกัน # suppress inspection "UnusedProperty" -dao.bond.bondedRoleType.GITHUB_ADMIN=Github admin +dao.bond.bondedRoleType.GITHUB_ADMIN=แอดมิน Github # suppress inspection "UnusedProperty" -dao.bond.bondedRoleType.FORUM_ADMIN=Forum admin +dao.bond.bondedRoleType.FORUM_ADMIN=แอดมินฟอรั่ม # suppress inspection "UnusedProperty" -dao.bond.bondedRoleType.TWITTER_ADMIN=Twitter admin +dao.bond.bondedRoleType.TWITTER_ADMIN=แอดมินทวิตเตอร์ # suppress inspection "UnusedProperty" -dao.bond.bondedRoleType.ROCKET_CHAT_ADMIN=Rocket chat admin +dao.bond.bondedRoleType.ROCKET_CHAT_ADMIN=แอดมิน Rocket chat # suppress inspection "UnusedProperty" -dao.bond.bondedRoleType.YOUTUBE_ADMIN=Youtube admin +dao.bond.bondedRoleType.YOUTUBE_ADMIN=แอดมินยูทูป # suppress inspection "UnusedProperty" -dao.bond.bondedRoleType.BISQ_MAINTAINER=Bisq maintainer +dao.bond.bondedRoleType.BISQ_MAINTAINER=ผู้ดูแล Bisq # suppress inspection "UnusedProperty" -dao.bond.bondedRoleType.WEBSITE_OPERATOR=Website operator +dao.bond.bondedRoleType.WEBSITE_OPERATOR=ผู้ดำเนินงานของเว็บไซต์ # suppress inspection "UnusedProperty" -dao.bond.bondedRoleType.FORUM_OPERATOR=Forum operator +dao.bond.bondedRoleType.FORUM_OPERATOR=ผู้ดำเนินการฟอรั่ม # suppress inspection "UnusedProperty" dao.bond.bondedRoleType.SEED_NODE_OPERATOR=ตัวดำเนินการแหล่งข้อมูลในโหนด # suppress inspection "UnusedProperty" -dao.bond.bondedRoleType.PRICE_NODE_OPERATOR=Price node operator +dao.bond.bondedRoleType.PRICE_NODE_OPERATOR=ผู้ดำเนินการโหนดด้านราคา # suppress inspection "UnusedProperty" -dao.bond.bondedRoleType.BTC_NODE_OPERATOR=Btc node operator +dao.bond.bondedRoleType.BTC_NODE_OPERATOR=ผู้ดำเนินการโหนด BTC # suppress inspection "UnusedProperty" -dao.bond.bondedRoleType.MARKETS_OPERATOR=Markets operator +dao.bond.bondedRoleType.MARKETS_OPERATOR=ผู้ดำเนินการด้านตลาด # suppress inspection "UnusedProperty" -dao.bond.bondedRoleType.BSQ_EXPLORER_OPERATOR=BSQ explorer operator +dao.bond.bondedRoleType.BSQ_EXPLORER_OPERATOR=ผู้ดำเนินการส่วนสำรวจ BSQ # suppress inspection "UnusedProperty" dao.bond.bondedRoleType.DOMAIN_NAME_HOLDER=เจ้าของชื่อโดเมน # suppress inspection "UnusedProperty" -dao.bond.bondedRoleType.DNS_ADMIN=DNS admin +dao.bond.bondedRoleType.DNS_ADMIN=แอดมิน DNS # suppress inspection "UnusedProperty" -dao.bond.bondedRoleType.MEDIATOR=Mediator +dao.bond.bondedRoleType.MEDIATOR=ผู้ไกล่เกลี่ย # suppress inspection "UnusedProperty" dao.bond.bondedRoleType.ARBITRATOR=ผู้ไกล่เกลี่ย -dao.burnBsq.assetFee=Asset listing fee -dao.burnBsq.menuItem.assetFee=Asset listing fee -dao.burnBsq.menuItem.proofOfBurn=Proof of burn -dao.burnBsq.header=Fee for asset listing -dao.burnBsq.selectAsset=Select Asset -dao.burnBsq.fee=Fee -dao.burnBsq.trialPeriod=Trial period -dao.burnBsq.payFee=Pay fee -dao.burnBsq.allAssets=All assets -dao.burnBsq.assets.nameAndCode=Asset name +dao.burnBsq.assetFee=ค่าธรรมเนียมในการลงบันทึกรายการทรัพย์สิน +dao.burnBsq.menuItem.assetFee=ค่าธรรมเนียมในการลงบันทึกรายการทรัพย์สิน +dao.burnBsq.menuItem.proofOfBurn=พยานหลักฐานในการทำลายทิ้ง (Proof of burn) +dao.burnBsq.header=ค่าธรรมเนียมสำหรับการลงบันทึกรายการทรัพย์สิน +dao.burnBsq.selectAsset=เลือก Asset +dao.burnBsq.fee=ค่าธรรมเนียม +dao.burnBsq.trialPeriod=ระยะทดลองใช้ +dao.burnBsq.payFee=ชำระค่าธรรมเนียม +dao.burnBsq.allAssets=ทรัพย์สินทั้งหมด +dao.burnBsq.assets.nameAndCode=ชื่อของทรัพย์สิน dao.burnBsq.assets.state=สถานะ dao.burnBsq.assets.tradeVolume=ปริมาณการซื้อขาย -dao.burnBsq.assets.lookBackPeriod=Verification period -dao.burnBsq.assets.trialFee=Fee for trial period -dao.burnBsq.assets.totalFee=Total fees paid -dao.burnBsq.assets.days={0} days -dao.burnBsq.assets.toFewDays=The asset fee is too low. The min. amount of days for the trial perios is {0}. +dao.burnBsq.assets.lookBackPeriod=ระยะเวลาของการตรวจสอบ +dao.burnBsq.assets.trialFee=ค่าธรรมเนียมสำหรับระยะทดลองใช้ +dao.burnBsq.assets.totalFee=ค่าธรรมเนียมที่ชำระแล้วทั้งหมด +dao.burnBsq.assets.days={0} วัน +dao.burnBsq.assets.toFewDays=ค่าธรรมเนียมสินทรัพย์มีน้อยเกินไป จำนวนระยะเวลาสำหรับการทดลองใช้คือ {0} # suppress inspection "UnusedProperty" dao.assetState.UNDEFINED=ไม่ได้กำหนด # suppress inspection "UnusedProperty" -dao.assetState.IN_TRIAL_PERIOD=In trial period +dao.assetState.IN_TRIAL_PERIOD=ในช่วงระยะเวลาทดลองใช้ # suppress inspection "UnusedProperty" -dao.assetState.ACTIVELY_TRADED=Actively traded +dao.assetState.ACTIVELY_TRADED=ซื้อขายอย่างแข่งขัน # suppress inspection "UnusedProperty" -dao.assetState.DE_LISTED=De-listed due to inactivity +dao.assetState.DE_LISTED=ถูกถอนออกจากรายชื่อเนื่องจากไม่มีการเคลื่อนไหว # suppress inspection "UnusedProperty" -dao.assetState.REMOVED_BY_VOTING=Removed by voting +dao.assetState.REMOVED_BY_VOTING=ถูกลบออกจากการโหวต -dao.proofOfBurn.header=Proof of burn +dao.proofOfBurn.header=พยานหลักฐานในการทำลายทิ้ง (Proof of burn) dao.proofOfBurn.amount=จำนวน dao.proofOfBurn.preImage=Pre-image -dao.proofOfBurn.burn=Burn -dao.proofOfBurn.allTxs=All proof of burn transactions -dao.proofOfBurn.myItems=My proof of burn transactions +dao.proofOfBurn.burn=ทำลายทิ้ง (Burn) +dao.proofOfBurn.allTxs=หลักฐานทั้งหมดในธุรกรรมที่ทำลายทิ้ง +dao.proofOfBurn.myItems=หลักฐานการทำลายธุรกรรมทิ้งของฉัน dao.proofOfBurn.date=วันที่ -dao.proofOfBurn.hash=Hash +dao.proofOfBurn.hash=แฮช dao.proofOfBurn.txs=การทำธุรกรรม dao.proofOfBurn.pubKey=Pubkey -dao.proofOfBurn.signature.window.title=Sign a message with key from proof or burn transaction -dao.proofOfBurn.verify.window.title=Verify a message with key from proof or burn transaction -dao.proofOfBurn.copySig=Copy signature to clipboard -dao.proofOfBurn.sign=Sign -dao.proofOfBurn.message=Message -dao.proofOfBurn.sig=Signature -dao.proofOfBurn.verify=Verify -dao.proofOfBurn.verify.header=Verify message with key from proof or burn transaction -dao.proofOfBurn.verificationResult.ok=Verification succeeded -dao.proofOfBurn.verificationResult.failed=Verification failed +dao.proofOfBurn.signature.window.title=ลงนามข้อความด้วยคีย์จากหลักฐานที่พิสูจน์ได้ (key from proof) หรือธุรกรรมที่ทำลายทิ้ง (burn transaction) +dao.proofOfBurn.verify.window.title=ตรวจสอบข้อความด้วยคีย์จากหลักฐานที่พิสูจน์ได้ (key from proof) หรือธุรกรรมที่ทำลายทิ้ง (burn transaction) +dao.proofOfBurn.copySig=คัดลอกลายเซ็นไปยังคลิปบอร์ด +dao.proofOfBurn.sign=ลงนาม +dao.proofOfBurn.message=ข้อความ +dao.proofOfBurn.sig=ลายเซ็น +dao.proofOfBurn.verify=ยืนยัน +dao.proofOfBurn.verify.header=ตรวจสอบข้อความด้วยคีย์จากหลักฐานที่พิสูจน์ได้ (key from proof) หรือธุรกรรมที่ทำลายทิ้ง (burn transaction) +dao.proofOfBurn.verificationResult.ok=การตรวจสอบดำเนินการเรียบร้อยแล้ว +dao.proofOfBurn.verificationResult.failed=การตรวจสอบล้มเหลว # suppress inspection "UnusedProperty" dao.phase.UNDEFINED=ไม่ได้กำหนด @@ -1369,24 +1371,24 @@ dao.phase.separatedPhaseBar.RESULT=ผลโหวต # suppress inspection "UnusedProperty" dao.proposal.type.COMPENSATION_REQUEST=คำขอสำหรับค่าสินไหมตอบแทน # suppress inspection "UnusedProperty" -dao.proposal.type.REIMBURSEMENT_REQUEST=Reimbursement request +dao.proposal.type.REIMBURSEMENT_REQUEST=ยื่นคำขอการชำระเงินคืน # suppress inspection "UnusedProperty" -dao.proposal.type.BONDED_ROLE=ข้อเสนอสำหรับเกณฑ์การกู้ยืม +dao.proposal.type.BONDED_ROLE=ข้อเสนอสำหรับเกณฑ์การประกัน # suppress inspection "UnusedProperty" -dao.proposal.type.REMOVE_ASSET=Proposal for removing an asset +dao.proposal.type.REMOVE_ASSET=ข้อเสนอสำหรับการถอดถอนสินทรัพย์ # suppress inspection "UnusedProperty" dao.proposal.type.CHANGE_PARAM=ข้อเสนอสำหรับการเปลี่ยนข้อจำกัด # suppress inspection "UnusedProperty" dao.proposal.type.GENERIC=ข้อเสนอทั่วไป # suppress inspection "UnusedProperty" -dao.proposal.type.CONFISCATE_BOND=ข้อเสนอในการริบการกู้ยืม +dao.proposal.type.CONFISCATE_BOND=ข้อเสนอในการริบการประกัน # suppress inspection "UnusedProperty" dao.proposal.type.short.COMPENSATION_REQUEST=คำขอค่าสินไหมทดแทน # suppress inspection "UnusedProperty" -dao.proposal.type.short.REIMBURSEMENT_REQUEST=Reimbursement request +dao.proposal.type.short.REIMBURSEMENT_REQUEST=ยื่นคำขอการชำระเงินคืน # suppress inspection "UnusedProperty" -dao.proposal.type.short.BONDED_ROLE=บทบาทการกู้ยืม +dao.proposal.type.short.BONDED_ROLE=ตำแหน่งการประกัน # suppress inspection "UnusedProperty" dao.proposal.type.short.REMOVE_ASSET=กำลังลบ altcoin (เหรียญทางเลือก) # suppress inspection "UnusedProperty" @@ -1394,14 +1396,14 @@ dao.proposal.type.short.CHANGE_PARAM=การเปลี่ยนพารา # suppress inspection "UnusedProperty" dao.proposal.type.short.GENERIC=ข้อเสนอทั่วไป # suppress inspection "UnusedProperty" -dao.proposal.type.short.CONFISCATE_BOND=การยึดการกู้ยืม +dao.proposal.type.short.CONFISCATE_BOND=การริบตัวประกัน dao.proposal.details=รายละเอียดข้อเสนอ dao.proposal.selectedProposal=ข้อเสนอที่เลือก dao.proposal.active.header=ข้อเสนอของวงจรปัจจุบัน -dao.proposal.active.remove.confirm=Are you sure you want to remove that proposal?\nThe already paid proposal fee will be lost. -dao.proposal.active.remove.doRemove=Yes, remove my proposal +dao.proposal.active.remove.confirm=คุณแน่ใจหรือไม่ที่จะลบข้อเสนอนั้น ข้อเสนอดังกล่าวที่มีการชำระค่าธรรมเนียมแล้วจะสูญหายหลังจากการลบข้อเสนอ +dao.proposal.active.remove.doRemove=ใช่ ลบข้อเสนอของฉัน dao.proposal.active.remove.failed=ไม่สามารถลบข้อเสนอได้ dao.proposal.myVote.accept=รับข้อเสนอ dao.proposal.myVote.reject=ปฏิเสธข้อเสนอ @@ -1410,7 +1412,7 @@ dao.proposal.myVote.merit=น้ำหนักผลคะแนนเสีย dao.proposal.myVote.stake=น้ำหนักผลการลงคะแนนเสียงจาก Stake (เหรียญที่ล็อคไว้สำหรับสิทธิ์ในการโหวต) dao.proposal.myVote.blindVoteTxId=ID การทำธุรกรรมการลงคะแนนเสียงแบบไม่ระบุตัวตน dao.proposal.myVote.revealTxId=ID ธุรกรรมการแสดงผลการลงคะแนน -dao.proposal.myVote.stake.prompt=Max. available balance for voting: {0} +dao.proposal.myVote.stake.prompt=ยอดที่ใช้งานได้ขั้นสูงสุดสำหรับการโหวต: {0} dao.proposal.votes.header=โหวตในข้อเสนอทั้งหมด dao.proposal.votes.header.voted=การลงคะแนนของฉัน dao.proposal.myVote.button=โหวตในข้อเสนอทั้งหมด @@ -1422,24 +1424,24 @@ dao.proposal=ข้อเสนอ dao.proposal.display.type=ประเภทข้อเสนอ dao.proposal.display.name=ชื่อ / ชื่อเล่น dao.proposal.display.link=ลิงก์ไปยังรายละเอียดข้อมูล -dao.proposal.display.link.prompt=Link to Github issue +dao.proposal.display.link.prompt=เชื่อมต่อไปยังคำสั่ง Github dao.proposal.display.requestedBsq=จำนวนที่ต้องการใน BSQ dao.proposal.display.bsqAddress=ที่อยู่ BSQ dao.proposal.display.txId=รหัสธุรกรรมของข้อเสนอ dao.proposal.display.proposalFee=ค่าธรรมเนียมข้อเสนอ dao.proposal.display.myVote=การลงคะแนนของฉัน dao.proposal.display.voteResult=สรุปผลโหวต -dao.proposal.display.bondedRoleComboBox.label=Bonded role type -dao.proposal.display.requiredBondForRole.label=Required bond for role -dao.proposal.display.tickerSymbol.label=Ticker Symbol -dao.proposal.display.option=Option +dao.proposal.display.bondedRoleComboBox.label=ประเภทของตำแหน่งหลักประกัน +dao.proposal.display.requiredBondForRole.label=การประกันที่จำเป็นโดยหลักการ +dao.proposal.display.tickerSymbol.label=สัญลักษณ์เครื่องพิมพ์ราคาหุ้น (Ticker Symbol) +dao.proposal.display.option=ตัวเลือก dao.proposal.table.header.proposalType=ประเภทข้อเสนอ dao.proposal.table.header.link=ลิงค์ dao.proposal.table.header.myVote=การลงคะแนนของฉัน dao.proposal.table.header.remove=ลบออก -dao.proposal.table.icon.tooltip.removeProposal=Remove my proposal -dao.proposal.table.icon.tooltip.changeVote=Current vote: ''{0}''. Change vote to: ''{1}'' +dao.proposal.table.icon.tooltip.removeProposal=ลบข้อเสนอของฉัน +dao.proposal.table.icon.tooltip.changeVote=ผลโหวตปัจจุบัน: ''{0}''. เปลี่ยนโหวตไปยัง: ''{1}'' dao.proposal.display.myVote.accepted=ได้รับการยืนยัน dao.proposal.display.myVote.rejected=ปฏิเสธ @@ -1450,11 +1452,11 @@ dao.proposal.voteResult.success=ได้รับการยืนยัน dao.proposal.voteResult.failed=ปฏิเสธ dao.proposal.voteResult.summary=ผลลัพธ์: {0}; เกณฑ์: {1} (ที่กำหนดไว้ต้อง> {2}); องค์ประชุม: {3} (ที่กำหนดไว้ต้อง> {4}) -dao.proposal.display.paramComboBox.label=Select parameter to change +dao.proposal.display.paramComboBox.label=เลือกพารามิเตอร์เพื่อเปลี่ยนแปลง dao.proposal.display.paramValue=ค่าพารามิเตอร์ -dao.proposal.display.confiscateBondComboBox.label=เลือกรูปแบบการกู้ยืม -dao.proposal.display.assetComboBox.label=Asset to remove +dao.proposal.display.confiscateBondComboBox.label=เลือกรูปแบบการประกัน +dao.proposal.display.assetComboBox.label=ทรัพย์สินที่จะถอนออก dao.blindVote=การลงคะแนนเสียงแบบไม่ระบุตัวตน @@ -1465,40 +1467,40 @@ dao.wallet.menuItem.send=ส่ง dao.wallet.menuItem.receive=รับ dao.wallet.menuItem.transactions=การทำธุรกรรม -dao.wallet.dashboard.myBalance=My wallet balance -dao.wallet.dashboard.distribution=Distribution of all BSQ -dao.wallet.dashboard.locked=Global state of locked BSQ -dao.wallet.dashboard.market=Market data +dao.wallet.dashboard.myBalance=ยอดคงเหลือในกระเป๋าสตางค์ของฉัน +dao.wallet.dashboard.distribution=การแบ่งหน่วยของ BSQ ทั้งหมด +dao.wallet.dashboard.locked=สถานะทั่วโลกของ BSQ ที่ล็อกไว้ +dao.wallet.dashboard.market=ข้อมูลทางการตลาด dao.wallet.dashboard.genesis=ธุรกรรมต้นกำเนิด -dao.wallet.dashboard.txDetails=BSQ transactions statistics +dao.wallet.dashboard.txDetails=สถิติในการทำธุรกรรม BSQ dao.wallet.dashboard.genesisBlockHeight=ความสูงของบล็อกต้นกำเนิด (Genesis block) dao.wallet.dashboard.genesisTxId=ID การทำธุรกรรมต้นกำเนิด -dao.wallet.dashboard.genesisIssueAmount=BSQ issued at genesis transaction -dao.wallet.dashboard.compRequestIssueAmount=BSQ issued for compensation requests -dao.wallet.dashboard.reimbursementAmount=BSQ issued for reimbursement requests -dao.wallet.dashboard.availableAmount=Total available BSQ -dao.wallet.dashboard.burntAmount=Burned BSQ (fees) -dao.wallet.dashboard.totalLockedUpAmount=ถูกล็อคไว้ในการกู้ยืม -dao.wallet.dashboard.totalUnlockingAmount=Unlocking BSQ from bonds -dao.wallet.dashboard.totalUnlockedAmount=Unlocked BSQ from bonds -dao.wallet.dashboard.totalConfiscatedAmount=Confiscated BSQ from bonds +dao.wallet.dashboard.genesisIssueAmount=BSQ ที่ได้ดำเนินการในส่วนธุรกรรมทั่วไป +dao.wallet.dashboard.compRequestIssueAmount=BSQ ที่ได้ดำเนินการสำหรับการเรียกร้องค่าชดเชย +dao.wallet.dashboard.reimbursementAmount=BSQ ที่ได้ดำเนินการสำหรับการเรียกร้องการชำระเงินคืน +dao.wallet.dashboard.availableAmount=BSQ ที่ใช้งานได้ทั้งหมด +dao.wallet.dashboard.burntAmount=BSQ ที่ทำลายทิ้ง (ค่าธรรมเนียม) +dao.wallet.dashboard.totalLockedUpAmount=ถูกล็อคไว้ในการประกัน +dao.wallet.dashboard.totalUnlockingAmount=การปลดล็อค BSQ จากการประกัน +dao.wallet.dashboard.totalUnlockedAmount=ปลดล็อค BSQ จากการประกันไว้แล้ว +dao.wallet.dashboard.totalConfiscatedAmount=ยึด BSQ จากการประกันไว้แล้ว dao.wallet.dashboard.allTx=หมายเลขจำนวนธุรกรรม BSQ ทั้งหมด dao.wallet.dashboard.utxo=หมายเลขจำนวนธุรกรรมที่ยังใช้ไม่หมด (เงินทอน) -dao.wallet.dashboard.compensationIssuanceTx=No. of all compensation request issuance transactions -dao.wallet.dashboard.reimbursementIssuanceTx=No. of all reimbursement request issuance transactions -dao.wallet.dashboard.burntTx=No. of all fee payments transactions -dao.wallet.dashboard.price=Latest BSQ/BTC trade price (in Bisq) -dao.wallet.dashboard.marketCap=Market capitalisation (based on trade price) +dao.wallet.dashboard.compensationIssuanceTx=เลขที่ของการทำธุรกรรมสำหรับยื่นคำขอค่าตอบแทนทั้งหมด +dao.wallet.dashboard.reimbursementIssuanceTx=เลขที่ของการทำธุรกรรมสำหรับการยื่นคำขอการชำระเงินคืนทั้งหมด +dao.wallet.dashboard.burntTx=เลขที่การทำธุรกรรมของการชำระค่าธรรมเนียมทั้งหมด +dao.wallet.dashboard.price=ราคาเทรด BSQ/BTC ล่าสุด (in Bisq) +dao.wallet.dashboard.marketCap=โครงสร้างเงินทุนในตลาด (ขึ้นอยู่กับราคาเทรด) dao.wallet.receive.fundYourWallet=เติมเงินกระเป๋าสตางค์ BSQ ของคุณ -dao.wallet.receive.bsqAddress=BSQ wallet address +dao.wallet.receive.bsqAddress=ที่อยู่ของกระเป๋าสตางค์ BSQ dao.wallet.send.sendFunds=ส่งเงิน -dao.wallet.send.sendBtcFunds=Send non-BSQ funds (BTC) +dao.wallet.send.sendBtcFunds=ส่งเงินทุนที่ไม่ใช่เครือ BSQ (BTC) dao.wallet.send.amount=จำนวนเงินใน BSQ -dao.wallet.send.btcAmount=Amount in BTC (non-BSQ funds) +dao.wallet.send.btcAmount=ยอดรวมทั้งหมดใน BTC (เงินทุนที่ไม่ใช่ในเครือ BSQ) dao.wallet.send.setAmount=กำหนดจำนวนเงินที่จะถอน (จำนวนเงินขั้นต่ำคือ {0}) -dao.wallet.send.setBtcAmount=Set amount in BTC to withdraw (min. amount is {0}) +dao.wallet.send.setBtcAmount=ตั้งค่ายอดรวมใน BTC เพื่อถอนออก (จำนวนยอดรวมขั้นต่ำคือ {0}) dao.wallet.send.receiverAddress=ที่อยู่ BSQ ของผู้รับ dao.wallet.send.receiverBtcAddress=ที่อยู่ BTC ของผู้รับ dao.wallet.send.setDestinationAddress=กรอกที่อยู่ปลายทางของคุณ @@ -1506,8 +1508,8 @@ dao.wallet.send.send=ส่งเงิน BSQ dao.wallet.send.sendBtc=ส่งเงินทุน BTC dao.wallet.send.sendFunds.headline=ยืนยันคำขอถอนเงิน dao.wallet.send.sendFunds.details=กำลังส่ง: {0} \nไปยังที่อยู่ที่ได้รับ: {1} .\nค่าธรรมเนียมการทำธุรกรรมคือ: {2} ({3} satoshis / byte) \nขนาดการทำรายการ: {4} Kb\n\nผู้รับจะได้รับ: {5} \n\nคุณแน่ใจหรือไม่ว่าคุณต้องการถอนจำนวนเงินดังกล่าว -dao.wallet.chainHeightSynced=Latest verified block: {0} -dao.wallet.chainHeightSyncing=Awaiting blocks... Verified {0} blocks out of {1} +dao.wallet.chainHeightSynced=บล็อกที่ได้รับการพิสูจน์แล้วล่าสุด: {0} +dao.wallet.chainHeightSyncing=บล็อกที่กำลังรอดำเนินการ... ตรวจสอบแล้ว {0} จากบล็อกทั้งหมด {1} dao.wallet.tx.type=หมวด # suppress inspection "UnusedProperty" @@ -1529,7 +1531,7 @@ dao.tx.type.enum.PAY_TRADE_FEE=ค่าธรรมเนียมการซ # suppress inspection "UnusedProperty" dao.tx.type.enum.COMPENSATION_REQUEST=ค่าธรรมเนียมการขอค่าชดเชย # suppress inspection "UnusedProperty" -dao.tx.type.enum.REIMBURSEMENT_REQUEST=Fee for reimbursement request +dao.tx.type.enum.REIMBURSEMENT_REQUEST=ค่าธรรมเนียมสำหรับการยื่นคำร้องขอการชำระเงินคืน # suppress inspection "UnusedProperty" dao.tx.type.enum.PROPOSAL=ค่าธรรมเนียมสำหรับข้อเสนอ # suppress inspection "UnusedProperty" @@ -1537,18 +1539,18 @@ dao.tx.type.enum.BLIND_VOTE=ค่าธรรมเนียมการโห # suppress inspection "UnusedProperty" dao.tx.type.enum.VOTE_REVEAL=การประกาศผลโหวต # suppress inspection "UnusedProperty" -dao.tx.type.enum.LOCKUP=ล็อคสิทธิ์การกู้ยืมไว้ +dao.tx.type.enum.LOCKUP=ล็อคสิทธิ์ในการประกัน # suppress inspection "UnusedProperty" -dao.tx.type.enum.UNLOCK=ปลดล็อกสิทธิ์การกู้ยืม +dao.tx.type.enum.UNLOCK=ปลดล็อกสิทธิ์การประกัน # suppress inspection "UnusedProperty" -dao.tx.type.enum.ASSET_LISTING_FEE=Asset listing fee +dao.tx.type.enum.ASSET_LISTING_FEE=ค่าธรรมเนียมในการลงบันทึกรายการทรัพย์สิน # suppress inspection "UnusedProperty" -dao.tx.type.enum.PROOF_OF_BURN=Proof of burn +dao.tx.type.enum.PROOF_OF_BURN=การพิสูจน์หลักฐานในการทำลายทิ้ง (Proof of burn) dao.tx.issuanceFromCompReq=คำขอหรือการออกค่าสินไหมทดแทน dao.tx.issuanceFromCompReq.tooltip=คำขอค่าสินไหมทดแทน ซึ่งนำไปสู่การออก BSQ ใหม่\nวันที่ออก: {0} -dao.tx.issuanceFromReimbursement=Reimbursement request/issuance -dao.tx.issuanceFromReimbursement.tooltip=Reimbursement request which led to an issuance of new BSQ.\nIssuance date: {0} +dao.tx.issuanceFromReimbursement=การออกคำสั่ง/การยื่นคำร้องขอการชำระเงินคืน +dao.tx.issuanceFromReimbursement.tooltip=การเรียกร้องขอการชำระเงินคืนซึ่งเป็นคำสั่งภายใต้ BSQ ฉบับใหม่\nวันที่เริ่มทำการ: {0} dao.proposal.create.missingFunds=คุณไม่มีเงินเพียงพอสำหรับการสร้างข้อเสนอ\nขาดไป: {0} dao.feeTx.confirm=ยืนยันการทำรายการ {0} dao.feeTx.confirm.details={0} ค่าธรรมเนียม: {1}\nค่าธรรมเนียมการขุด: {2} ({3} Satoshis / byte)\nขนาดของธุรกรรม: {4} Kb\n\nคุณแน่ใจหรือไม่ว่าต้องการเผยแพร่ {5} ธุรกรรม? @@ -1584,7 +1586,7 @@ displayUpdateDownloadWindow.verify.failed=การยืนยันล้ม displayUpdateDownloadWindow.success=ดาวน์โหลดเวอร์ชั่นใหม่เรียบร้อยแล้วและได้รับการยืนยันลายเซ็นแล้ว\n\nโปรดเปิดสารบบดาวน์โหลด หลังจากนั้นปิดโปรแกรมและติดตั้งเวอร์ชั่นใหม่ displayUpdateDownloadWindow.download.openDir=เปิดสารบบดาวน์โหลด -disputeสรุปWindow.title=สรุป +disputeSummaryWindow.title=สรุป disputeSummaryWindow.openDate=วันที่ยื่นการเปิดคำขอและความช่วยเหลือ disputeSummaryWindow.role=บทบาทของผู้ค้า disputeSummaryWindow.evidence=หลักฐาน @@ -1738,7 +1740,7 @@ popup.headline.instruction=โปรดทราบ: popup.headline.attention=ฟังทางนี้ด้วย popup.headline.backgroundInfo=ข้อมูลพื้นฐาน popup.headline.feedback=เสร็จสิ้น -popup.headline.confirmation=การยืนยัน +popup.headline.confirmation=การยืนยัน popup.headline.information=ข้อมูล popup.headline.warning=คำเตือน popup.headline.error=ผิดพลาด @@ -1746,7 +1748,7 @@ popup.headline.error=ผิดพลาด popup.doNotShowAgain=ไม่ต้องแสดงอีกครั้ง popup.reportError.log=เปิดไฟล์ที่บันทึก popup.reportError.gitHub=รายงานไปที่ตัวติดตามปัญหา GitHub -popup.reportError={0} \n\nเพื่อช่วยในการปรับปรุงซอฟต์แวร์โปรดรายงานข้อผิดพลาดที่เครื่องมือติดตามปัญหาของเราที่ GitHub (https://github.com/bisq-network/bisq-desktop/issues).\nข้อความแสดงข้อผิดพลาดจะถูกคัดลอกไปยังคลิปบอร์ดเมื่อคุณคลิกปุ่มด้านล่าง\nจะทำให้การดีบั๊กง่ายขึ้นหากคุณสามารถแนบไฟล์ bisq.log ได้ด้วย +popup.reportError={0}\n\nTo help us to improve the software please report this bug by opening a new issue at https://github.com/bisq-network/bisq/issues.\nThe above error message will be copied to the clipboard when you click either of the buttons below.\nIt will make debugging easier if you include the bisq.log file by pressing "Open log file", saving a copy, and attaching it to your bug report. popup.error.tryRestart=โปรดลองเริ่มแอปพลิเคชั่นของคุณใหม่และตรวจสอบการเชื่อมต่อเครือข่ายของคุณเพื่อดูว่าคุณสามารถแก้ไขปัญหาได้หรือไม่ popup.error.takeOfferRequestFailed=เกิดข้อผิดพลาดขึ้นเมื่อมีคนพยายามรับข้อเสนอของคุณ: \n{0} @@ -1763,19 +1765,19 @@ popup.warning.tradePeriod.halfReached=การซื้อขายของค popup.warning.tradePeriod.ended=การซื้อขายของคุณที่มีรหัส ID {0} มีค่าสูงสุดแล้ว อนุญาตให้ซื้อขายได้และยังไม่สมบูรณ์\n\nช่วงเวลาการซื้อขายสิ้นสุดวันที่ {1}\n\nโปรดตรวจสอบการค้าของคุณที่ \"Portfolio (แฟ้มผลงาน) / เปิดการซื้อขาย \" เพื่อติดต่อกับผู้ไกล่เกลี่ย popup.warning.noTradingAccountSetup.headline=คุณยังไม่ได้ตั้งค่าบัญชีการซื้อขาย popup.warning.noTradingAccountSetup.msg=คุณต้องตั้งค่าสกุลเงินประจำชาติหรือบัญชี altcoin (เหรียญทางเลือก) ก่อนจึงจะสามารถสร้างข้อเสนอได้\nคุณต้องการตั้งค่าบัญชีหรือไม่ -popup.warning.noArbitratorsAvailable=There are no arbitrators available. +popup.warning.noArbitratorsAvailable=ไม่มีผู้ไกล่เกลี่ยสำหรับทำการ popup.warning.notFullyConnected=คุณต้องรอจนกว่าคุณจะเชื่อมต่อกับเครือข่ายอย่างสมบูรณ์\nอาจใช้เวลาประมาณ 2 นาทีเมื่อเริ่มต้น popup.warning.notSufficientConnectionsToBtcNetwork=คุณต้องรอจนกว่าจะมีการเชื่อมต่อกับเครือข่าย Bitcoin อย่างน้อย {0} รายการ popup.warning.downloadNotComplete=คุณต้องรอจนกว่าการดาวน์โหลดบล็อค Bitcoin ที่ขาดหายไปจะเสร็จสมบูรณ์ popup.warning.removeOffer=คุณแน่ใจหรือไม่ว่าต้องการนำข้อเสนอนั้นออก\nค่าธรรมเนียมของผู้สร้าง {0} จะสูญหายไปหากคุณนำข้อเสนอนั้นออก popup.warning.tooLargePercentageValue=คุณไม่สามารถกำหนดเปอร์เซ็นต์เป็น 100% หรือมากกว่าได้ -popup.warning.examplePercentageValue=โปรดป้อนตัวเลขเปอร์เซ็นต์เช่น \ "5.4 \" เป็น 5.4% +popup.warning.examplePercentageValue=โปรดป้อนตัวเลขเปอร์เซ็นต์เช่น \"5.4 \" เป็น 5.4% popup.warning.noPriceFeedAvailable=ไม่มีฟีดราคาสำหรับสกุลเงินดังกล่าว คุณไม่สามารถใช้ราคาตามเปอร์เซ็นต์ได้\nโปรดเลือกราคาที่ถูกกำหนดไว้แแล้ว popup.warning.sendMsgFailed=การส่งข้อความไปยังคู่ค้าของคุณล้มเหลว\nโปรดลองอีกครั้งและหากยังคงเกิดขึ้นขึ้นเนื่อง โปรดรายงานข้อผิดพลาดต่อไป popup.warning.insufficientBtcFundsForBsqTx=คุณไม่มีเงินทุน BTC เพียงพอสำหรับการจ่ายค่าธรรมเนียมขุดสำหรับการทำธุรกรรมดังกล่าว\nกรุณาใส่เงินในกระเป๋าสตางค์ BTC ของคุณ\nเงินขาดไป: {0} -popup.warning.insufficientBsqFundsForBtcFeePayment=You don''t have sufficient BSQ funds for paying the trade fee in BSQ. You can pay the fee in BTC or you need to fund your BSQ wallet. You can buy BSQ in Bisq.\n\nMissing BSQ funds: {0} -popup.warning.noBsqFundsForBtcFeePayment=Your BSQ wallet does not have sufficient funds for paying the trade fee in BSQ. +popup.warning.insufficientBsqFundsForBtcFeePayment=คุณไม่มีเงินทุน BSQ เพียงพอสำหรับการจ่ายค่าธรรมเนียมการเทรดใน BSQ คุณสามารถชำระได้ใน BTC หรือคุณสามารถใช้เงินทุนจากกระเป๋าสตางค์ BSQ ของคุณ คุณสามารถซื้อ BSQ ใน Bisq ได้ \n\nกองทุน BSQ ที่หายไป: {0} +popup.warning.noBsqFundsForBtcFeePayment=กระเป๋าสตางค์ BSQ ของคุณไม่มีจำนวนเงินทุนที่มากพอสำหรับการชำระการเทรดใน BSQ popup.warning.messageTooLong=ข้อความของคุณเกินขีดจำกัดสูงสุดที่อนุญาต โปรดแบ่งส่งเป็นหลายส่วนหรืออัปโหลดไปยังบริการเช่น https://pastebin.com popup.warning.lockedUpFunds=คุณล็อคเงินจากการซื้อขายที่ล้มเหลวแล้ว\nล็อคยอดคงเหลือ: {0} \nที่อยู่ฝากเงิน tx: {1} \nรหัส ID การซื้อขาย: {2} .\n\nโปรดเปิดศูนย์ช่วยเหลือสนับสนุนโดยการเลือกการซื้อขายในหน้าจอการซื้อขายที่ค้างอยู่และคลิก \"alt + o \" หรือ \"option + o \" @@ -1783,11 +1785,11 @@ popup.warning.nodeBanned=หนึ่งใน {0} โหนดถูกแบ popup.warning.priceRelay=ราคาผลัดเปลี่ยน popup.warning.seed=รหัสลับเพื่อกู้ข้อมูล -popup.info.securityDepositInfo=To ensure both traders follow the trade protocol, both traders need to pay a security deposit.\n\nThis deposit is kept in your trade wallet until your trade has been successfully completed, and then it's refunded to you.\n\nPlease note: if you're creating a new offer, Bisq needs to be running for another trader to take it. To keep your offers online, keep Bisq running and make sure this computer remains online too (i.e., make sure it doesn't switch to standby mode...monitor standby is fine). +popup.info.securityDepositInfo=เพื่อให้แน่ใจว่าเทรดเดอร์ทั้งคู่นั้นได้ปฏิบัติตามข้อสนธิสัญญาในการค้า เทรดเดอร์จำเป็นต้องทำการชำระค่าประกัน\n\nค่าประกันนี้คือถูกเก็บไว้ในกระเป๋าสตางค์การเทรดของคุณจนกว่าการเทรดของคุณจะดำเนินการสำเร็จ และคุณจะได้รับมันคืนหลังจากนั้น \n\nโปรดทราบ: หากคุณกำลังสร้างข้อเสนอขึ้นมาใหม่ Bisq จำเป็นที่ต้องดำเนินงานต่อเนื่องไปยังเทรดเดอร์รายอื่น และเพื่อที่สถานะข้อเสนอทางออนไลน์ของคุณจะยังคงอยู่ Bisq จะยังคงดำเนินงานต่อเนื่อง และโปรดมั่นใจว่าเครื่องคอมพิวเตอร์นี้กำลังออนไลน์อยู่ด้วยเช่นกัน (ยกตัวอย่างเช่น ตรวจเช็คว่าสวิทช์ไฟไม่ได้อยู่ในโหมดแสตนบายด์...หน้าจอแสตนบายด์คือปกติดี) popup.info.cashDepositInfo=โปรดตรวจสอบว่าคุณมีสาขาธนาคารในพื้นที่ของคุณเพื่อสามารถฝากเงินได้\nรหัสธนาคาร (BIC / SWIFT) ของธนาคารผู้ขายคือ: {0} popup.info.cashDepositInfo.confirm=ฉันยืนยันว่าฉันสามารถฝากเงินได้ -popup.info.shutDownWithOpenOffers=Bisq is being shut down, but there are open offers. \n\nThese offers won't be available on the P2P network while Bisq is shut down, but they will be re-published to the P2P network the next time you start Bisq.\n\nTo keep your offers online, keep Bisq running and make sure this computer remains online too (i.e., make sure it doesn't go into standby mode...monitor standby is not a problem). +popup.info.shutDownWithOpenOffers=Bisq คือกำลังจะปิดลง แต่ยังคงมีการเปิดขายข้อเสนอปกติ\nข้อเสนอเหล่านี้จะไม่ใข้งานได้บนเครือข่าย P2P network ในขณะที่ Bisq ปิดตัวลง แต่จะมีการเผยแพร่บนเครือข่าย P2P ครั้งถัดไปเมื่อคุณมีการเริ่มใช้งาน Bisq.\n\nในการคงสถานะข้อเสนอแบบออนไลน์ คือเปิดใข้งาน Bisq และทำให้มั่นใจว่าคอมพิวเตอร์เครื่องนี้กำลังออนไลน์อยู่ด้วยเช่นกัน (เช่น ตรวจสอบว่าคอมพิวเตอร์ไม่ได้อยู่ในโหมดแสตนบายด์...หน้าจอแสตนบายด์ไม่มีปัญหา) popup.privateNotification.headline=การแจ้งเตือนส่วนตัวที่สำคัญ! @@ -1795,7 +1797,7 @@ popup.privateNotification.headline=การแจ้งเตือนส่ว popup.securityRecommendation.headline=ข้อเสนอแนะด้านความปลอดภัยที่สำคัญ popup.securityRecommendation.msg=เราขอแจ้งเตือนให้คุณพิจารณาใช้การป้องกันด้วยรหัสผ่านสำหรับ wallet ของคุณ หากยังไม่ได้เปิดใช้งาน\n\nขอแนะนำให้เขียนรหัสลับป้องกัน wallet รหัสลับเหล่านี้เหมือนกับรหัสผ่านหลักสำหรับการกู้คืน Bitcoin wallet ของคุณ\nไปที่ \"กระเป๋าสตางค์ \" คุณจะพบข้อมูลเพิ่มเติม\n\nนอกจากนี้คุณควรสำรองโฟลเดอร์ข้อมูลแอ็พพลิเคชั่นทั้งหมดไว้ที่ส่วน \"สำรองข้อมูล \" -popup.bitcoinLocalhostNode.msg=Bisq ตรวจพบเฉพาะบิตโหนดหลักของ Bitcoin ที่ใช้งานอยู่ (ที่ localhost)\nโปรดตรวจสอบว่าโหนดนี้ได้รับการซิงค์อย่างสมบูรณ์ก่อนที่คุณจะเริ่ม Bisq และไม่ได้ทำงานในโหมด pruned +popup.bitcoinLocalhostNode.msg=Bisq ตรวจพบเฉพาะบิตโหนดหลักของ Bitcoin ที่ใช้งานอยู่ (ที่ localhost)\nโปรดตรวจสอบว่าโหนดนี้ได้รับการซิงค์อย่างสมบูรณ์ก่อนที่คุณจะเริ่ม Bisq และไม่ได้ทำงานในโหมด pruned popup.shutDownInProgress.headline=การปิดระบบอยู่ระหว่างดำเนินการ popup.shutDownInProgress.msg=การปิดแอพพลิเคชั่นอาจใช้เวลาสักครู่\nโปรดอย่าขัดจังหวะกระบวนการนี้ @@ -1805,6 +1807,9 @@ popup.attention.forTradeWithId=ต้องให้ความสำคัญ popup.roundedFiatValues.headline=คุณลักษณะความเป็นส่วนตัวใหม่: ค่าที่ได้รับการปัดเศษ popup.roundedFiatValues.msg=เพื่อเพิ่มความเป็นส่วนตัวของการค้าของคุณ {0} จำนวนถูกปัดเศษ\n\nขึ้นอยู่กับเวอร์ชั่นของลูกค้า คุณจะต้องจ่ายหรือรับค่าด้วยทศนิยมหรือแบบกลม\n\nทั้งสองค่าทำตามจากโปรโตคอลการค้า\n\nนอกจากนี้โปรดทราบว่าค่า BTC จะเปลี่ยนไปโดยอัตโนมัติเพื่อให้ตรงกับจำนวนเงินที่ปัดเศษให้ใกล้เคียงที่สุด +popup.info.multiplePaymentAccounts.headline=Multiple payment accounts available +popup.info.multiplePaymentAccounts.msg=You have multiple payment accounts available for this offer. Please make sure you've picked the right one. + #################################################################### # Notifications @@ -1854,7 +1859,7 @@ guiUtil.accountExport.exportFailed=การส่งออกไปยัง CS guiUtil.accountExport.selectExportPath=เลือกเส้นทางการส่งออก guiUtil.accountImport.imported=บัญชีการซื้อขายที่นำเข้าจากเส้นทาง: \n{0} \n\nบัญชีที่นำเข้า: \n{1} guiUtil.accountImport.noAccountsFound=ไม่พบบัญชีการค้าที่ส่งออกระหว่างทาง: {0} .\nชื่อไฟล์คือ {1} " -guiUtil.openWebBrowser.warning=คุณกำลังจะเปิดเว็บเพจในเว็บเบราเซอร์ของระบบ\nคุณต้องการเปิดเว็บเพจตอนนี้หรือไม่\n\nหากคุณไม่ได้ใช้ \ "Tor Browser \" เป็นเว็บเบราเซอร์ระบบเริ่มต้นของคุณ คุณจะเชื่อมต่อกับเว็บเพจโดยไม่ต้องแจ้งให้ทราบล่วงหน้า\n\nURL: \ "{0} \" +guiUtil.openWebBrowser.warning=คุณกำลังจะเปิดเว็บเพจในเว็บเบราเซอร์ของระบบ\nคุณต้องการเปิดเว็บเพจตอนนี้หรือไม่\n\nหากคุณไม่ได้ใช้ \"Tor Browser \" เป็นเว็บเบราเซอร์ระบบเริ่มต้นของคุณ คุณจะเชื่อมต่อกับเว็บเพจโดยไม่ต้องแจ้งให้ทราบล่วงหน้า\n\nURL: \"{0} \" guiUtil.openWebBrowser.doOpen=เปิดหน้าเว็บและไม่ต้องถามอีก guiUtil.openWebBrowser.copyUrl=คัดลอก URL และยกเลิก guiUtil.ofTradeAmount=ของปริมาณการซื้อขาย @@ -1990,11 +1995,11 @@ password.walletEncrypted=เปิดใช้งานกระเป๋าส password.walletEncryptionFailed=ไม่สามารถตั้งรหัสผ่านกระเป๋าสตางค์ได้ คุณอาจกรอกรหัสลับป้องกันกระเป๋าสตางค์ที่ไม่ตรงกับฐานข้อมูลโปรดติดต่อนักพัฒนาซอฟต์แวร์ในฟอรัม Bisq Forum password.passwordsDoNotMatch=รหัสผ่าน 2 รายการที่คุณป้อนไม่ตรงกัน password.forgotPassword=ลืมรหัสผ่านหรือเปล่า? -password.backupReminder=โปรดทราบว่าเมื่อตั้งค่ารหัสผ่านกระเป๋าสตางค์ที่สร้างขึ้นโดยอัตโนมัติทั้งหมดจาก wallet ที่ไม่ได้รับการเข้ารหัสจะถูกลบออก\n\nขอแนะนำให้ทำการสำรองข้อมูลของสารบบแอ็พพลิเคชั่นและเขียนรหัสลับป้องกันกระเป๋าสตางค์ก่อนที่จะตั้งรหัสผ่าน! +password.backupReminder=โปรดทราบว่าเมื่อตั้งค่ารหัสผ่านกระเป๋าสตางค์ที่สร้างขึ้นโดยอัตโนมัติทั้งหมดจาก wallet ที่ไม่ได้รับการเข้ารหัสจะถูกลบออก\n\nขอแนะนำให้ทำการสำรองข้อมูลของสารบบแอ็พพลิเคชั่นและเขียนรหัสลับป้องกันกระเป๋าสตางค์ก่อนที่จะตั้งรหัสผ่าน! password.backupWasDone=ฉันได้ทำสำรองไว้แล้ว seed.seedWords=รหัสลับป้องกันกระเป๋าสตางค์ -seed.enterSeedWords=Enter wallet seed words +seed.enterSeedWords=ป้อนรหัสลับกระเป๋าสตางค์ seed.date=วันที่ในกระเป๋าสตางค์ seed.restore.title=เรียกคืนกระเป๋าสตางค์จากรหัสลับ seed.restore=เรียกกระเป๋าสตางค์คืน @@ -2044,7 +2049,7 @@ payment.moneyBeam.accountId=อีเมลหรือหมายเลขโ payment.venmo.venmoUserName=ชื่อผู้ใช้ Venmo payment.popmoney.accountId=อีเมลหรือหมายเลขโทรศัพท์ payment.revolut.accountId=อีเมลหรือหมายเลขโทรศัพท์ -payment.promptPay.promptPayId=Citizen ID/Tax ID or phone no. +payment.promptPay.promptPayId=รหัสบัตรประชาชน/รหัสประจำตัวผู้เสียภาษี หรือเบอร์โทรศัพท์ payment.supportedCurrencies=สกุลเงินที่ได้รับการสนับสนุน payment.limitations=ข้อจำกัด payment.salt=ข้อมูลแบบสุ่มสำหรับการตรวจสอบอายุบัญชี @@ -2059,13 +2064,13 @@ payment.national.account.id.AR=หมายเลข CBU #new payment.altcoin.address.dyn={0} ที่อยู่ -payment.altcoin.receiver.address=Receiver's altcoin address +payment.altcoin.receiver.address=ที่อยู่เหรียญทางเลือกของผู้รับ payment.accountNr=หมายเลขบัญชี payment.emailOrMobile=หมายเลขโทรศัพท์มือถือหรืออีเมล payment.useCustomAccountName=ใช้ชื่อบัญชีที่กำหนดเอง payment.maxPeriod=ระยะเวลาสูงสุดการค้าที่อนุญาต payment.maxPeriodAndLimit=ระยะเวลาสูงสุดทางการค้า: {0} / ขีดจำกัดสูงสุดทางการค้า: {1} / อายุบัญชี: {2} -payment.maxPeriodAndLimitCrypto=ระยะเวลาสูงสุดทางการค้า: {0} / ขีดจำกัดสูงสุดทางการค้า: {1} +payment.maxPeriodAndLimitCrypto=ระยะเวลาสูงสุดทางการค้า: {0} / ขีดจำกัดสูงสุดทางการค้า: {1} payment.currencyWithSymbol=สกุลเงิน: {0} payment.nameOfAcceptedBank=ชื่อธนาคารที่ได้รับการยอมรับ payment.addAcceptedBank=เพิ่มธนาคารที่ได้รับการยอมรับ @@ -2081,14 +2086,14 @@ payment.accountType=ประเภทบัญชี payment.checking=การตรวจสอบ payment.savings=ออมทรัพย์ payment.personalId=รหัส ID ประจำตัวบุคคล -payment.clearXchange.info=โปรดดูให้แน่ใจว่าคุณปฏิบัติตามข้อกำหนดสำหรับการใช้ Zelle (ClearXchange)\n\n1. คุณจำเป็นต้องมีบัญชี Zelle (ClearXchange) ที่ได้รับการยืนยันบนแพลตฟอร์มของตนก่อนที่จะเริ่มทำการค้าหรือสร้างข้อเสนอ\n\n2. คุณต้องมีบัญชีธนาคารที่เป็นสมาชิกรายใดก็ได้ต่อไปนี้: \n● Bank of America\n\t● Capital One P2P Payments\n\t● Chase QuickPay\n\t● FirstBank Person to Person Transfers\n\t● Frost Send Money\n\t● U.S. Bank Send Money\n\t● TD Bank\n\t● Wells Fargo SurePay\n\n3. คุณต้องแน่ใจว่าจะไม่เกินขีด จำกัด การโอน Zelle (ClearXchange) รายวันหรือรายเดือน\n\nโปรดใช้ Zelle (ClearXchange) เฉพาะเมื่อคุณปฏิบัติตามข้อกำหนดเหล่านี้ มิฉะนั้นจะมีโอกาสมากที่การโอน Zelle (ClearXchange) จะล้มเหลวและการซื้อขายจะสิ้นสุดลงในข้อพิพาท\nหากคุณไม่ปฏิบัติตามข้อกำหนดข้างต้นคุณจะสูญเสียเงินประกัน\n\nนอกจากนี้โปรดทราบถึงความเสี่ยงในการเรียกเก็บเงินคืนเมื่อใช้ Zelle (ClearXchange)\nสำหรับ {0} ผู้ขายขอแนะนำให้ติดต่อกับ {1} ผู้ซื้อโดยใช้ที่อยู่อีเมลหรือหมายเลขโทรศัพท์มือถือที่ระบุเพื่อยืนยันว่าเขาเป็นเจ้าของบัญชี Zelle (ClearXchange) ตัวจริง +payment.clearXchange.info=โปรดดูให้แน่ใจว่าคุณปฏิบัติตามข้อกำหนดสำหรับการใช้ Zelle (ClearXchange)\n\n1. คุณจำเป็นต้องมีบัญชี Zelle (ClearXchange) ที่ได้รับการยืนยันบนแพลตฟอร์มของตนก่อนที่จะเริ่มทำการค้าหรือสร้างข้อเสนอ\n\n2. คุณต้องมีบัญชีธนาคารที่เป็นสมาชิกรายใดก็ได้ต่อไปนี้: \n● Bank of America\n\t● Capital One P2P Payments\n\t● Chase QuickPay\n\t● FirstBank Person to Person Transfers\n\t● Frost Send Money\n\t● U.S. Bank Send Money\n\t● TD Bank\n\t● Wells Fargo SurePay\n\n3. คุณต้องแน่ใจว่าการโอนด้วย Zelle (ClearXchange) รายวันหรือรายเดือนนั้นไม่เกินวงเงินที่จำกัดไว้\n\nโปรดใช้ Zelle (ClearXchange) เฉพาะเมื่อคุณปฏิบัติตามข้อกำหนดเหล่านี้ มิฉะนั้นจะมีโอกาสสูงที่การโอน Zelle (ClearXchange) จะล้มเหลวและการซื้อขายจะสิ้นสุดลงในข้อพิพาท\nหากคุณไม่ปฏิบัติตามข้อกำหนดข้างต้นคุณจะสูญเสียเงินประกัน\n\nนอกจากนี้โปรดทราบถึงความเสี่ยงในการเรียกเก็บเงินคืนเมื่อใช้ Zelle (ClearXchange)\nสำหรับ {0} ผู้ขายขอแนะนำให้ติดต่อกับ {1} ผู้ซื้อโดยใช้ที่อยู่อีเมลหรือหมายเลขโทรศัพท์มือถือที่ระบุเพื่อยืนยันว่าเขาเป็นเจ้าของบัญชี Zelle (ClearXchange) ตัวจริง payment.moneyGram.info=เมื่อใช้ MoneyGram ผู้ซื้อ BTC จะต้องส่งหมายเลขการอนุมัติและรูปใบเสร็จรับเงินทางอีเมลไปยังผู้ขาย BTC ใบเสร็จจะต้องแสดงชื่อเต็ม ประเทศ รัฐและจำนวนเงินทั้งหมดของผู้ขาย ผู้ซื้อจะได้รับอีเมลของผู้ขายในขั้นตอนการค้า payment.westernUnion.info=เมื่อใช้ Western Union ผู้ซื้อ BTC จะต้องส่ง MTCN (หมายเลขติดตาม) และรูปใบเสร็จรับเงินทางอีเมลไปยังผู้ขาย BTC ใบเสร็จรับเงินต้องแสดงชื่อเต็ม ประเทศ เมืองและจำนวนเงินทั้งหมดของผู้ขาย ผู้ซื้อจะได้รับอีเมลของผู้ขายในขั้นตอนการค้า -payment.halCash.info=เมื่อใช้ HalCash ผู้ซื้อ BTC จะต้องส่งรหัส HalCash ของ BTC ผ่านข้อความจากโทรศัพท์มือถือ\n\nโปรดตรวจสอบว่าไม่เกินจำนวนเงินสูงสุดที่ธนาคารของคุณอนุญาตให้คุณส่งด้วย HalCash จำนวนเงินขั้นต่ำในการเบิกถอนคือ 10 ยูโรและสูงสุดในจำนวนเงิน 600 ยูโร สำหรับการถอนซ้ำเป็น 3000 EUR ต่อผู้รับและต่อวัน และ 6000 EUR ต่อผู้รับและต่อเดือน โปรดตรวจสอบข้อจำกัด ดังกล่าวกับธนาคารของคุณเพื่อตรวจสอบว่าใช้ข้อจำกัดเดียวกับที่ระบุไว้ที่นี่\n\nจำนวนเงินที่ถอนจะต้องเป็นจำนวนเงินหลาย 10 ยูโรเนื่องจากคุณไม่สามารถถอนเงินอื่น ๆ ออกจากตู้เอทีเอ็มได้ UI ในหน้าจอสร้างข้อเสนอพิเศษและรับข้อเสนอพิเศษจะปรับจำนวนเงิน BTC เพื่อให้จำนวนเงิน EUR ถูกต้อง คุณไม่สามารถใช้ราคาตลาดเป็นจำนวนเงิน EUR ซึ่งจะเปลี่ยนแปลงไปตามราคาที่มีการปรับเปลี่ยน\n\nในกรณีที่มีข้อพิพาทผู้ซื้อ BTC ต้องแสดงหลักฐานว่าได้ส่ง EUR แล้ว +payment.halCash.info=เมื่อมีการใช้งาน HalCash ผู้ซื้อ BTC จำเป็นต้องส่งรหัส Halcash ให้กับผู้ขายทางข้อความโทรศัพท์มือถือ\n\nโปรดตรวจสอบว่าไม่เกินจำนวนเงินสูงสุดที่ธนาคารของคุณอนุญาตให้คุณส่งด้วย HalCash จำนวนเงินขั้นต่ำในการเบิกถอนคือ 10 EUR และสูงสุดในจำนวนเงิน 600 EUR สำหรับการถอนซ้ำเป็น 3000 EUR ต่อผู้รับและต่อวัน และ 6000 EUR ต่อผู้รับและต่อเดือน โปรดตรวจสอบข้อจำกัดจากทางธนาคารคุณเพื่อให้มั่นใจได้ว่าทางธนาคารได้มีการใช้มาตรฐานข้อกำหนดเดียวกันกับดังที่ระบุไว้ ณ ที่นี่\n\nจำนวนเงินที่ถอนจะต้องเป็นจำนวนเงินหลาย 10 EUR เนื่องจากคุณไม่สามารถถอนเงินอื่น ๆ ออกจากตู้เอทีเอ็มได้ UI ในหน้าจอสร้างข้อเสนอและรับข้อเสนอจะปรับจำนวนเงิน BTC เพื่อให้จำนวนเงิน EUR ถูกต้อง คุณไม่สามารถใช้ราคาตลาดเป็นจำนวนเงิน EUR ซึ่งจะเปลี่ยนแปลงไปตามราคาที่มีการปรับเปลี่ยน\n\nในกรณีที่มีข้อพิพาทผู้ซื้อ BTC ต้องแสดงหลักฐานว่าได้ส่ง EUR แล้ว payment.limits.info=โปรดทราบว่าการโอนเงินผ่านธนาคารทั้งหมดมีความเสี่ยงจากการเรียกเก็บเงินคืน\n\nเพื่อลดความเสี่ยงนี้ Bisq ตั้งค่าขีดจำกัดต่อการซื้อขายขึ้นอยู่กับสองปัจจัยคือ\n\n1. ระดับความเสี่ยงจากการเรียกเก็บเงินคืนโดยประเมินจากวิธีการชำระเงินที่ใช้\n2. อายุของบัญชีสำหรับวิธีการชำระเงินนั้น\n\nขณะนี้บัญชีที่คุณกำลังสร้างใหม่และยังไม่ได้เริ่มอายุการใช้งาน เนื่องจากบัญชีของคุณเติบโตขึ้นเมื่ออายุเกินกว่าระยะเวลาสองเดือน ขีดจำกัดต่อการซื้อขายของคุณจะเติบโตไปพร้อมเช่นกัน: \n\n●ในช่วง 1 เดือนขีดจำกัดต่อการซื้อขายของคุณจะเป็น {0} \n●ในช่วงเดือนที่ 2 ขีดจำกัดต่อการซื้อขายของคุณจะเป็น {1} \n●หลังจากเดือนที่ 2 ขีดจำกัดต่อการซื้อขายของคุณจะเป็น {2} \n\nโปรดทราบว่าไม่มีข้อจำกัดเกี่ยวกับจำนวนครั้งที่คุณสามารถซื้อขายได้ -payment.cashDeposit.info=Please confirm your bank allows you to send cash deposits into other peoples' accounts. For example, Bank of America and Wells Fargo no longer allow such deposits. +payment.cashDeposit.info=โปรดยืนยันว่าธนาคารของคุณได้อนุมัติให้คุณสามารถส่งเงินสดให้กับบัญชีบุคคลอื่นได้ ตัวอย่างเช่น บางธนาคารที่ไม่ได้มีการบริการถ่ายโอนเงินสดอย่าง Bank of America และ Wells Fargo payment.f2f.contact=ข้อมูลติดต่อ payment.f2f.contact.prompt=วิธีการที่คุณต้องการได้รับการติดต่อจากการค้าจากระบบ peer (ที่อยู่อีเมล , หมายเลขโทรศัพท์ ... ) @@ -2098,7 +2103,7 @@ payment.f2f.optionalExtra=ข้อมูลตัวเลือกเพิ่ payment.f2f.extra=ข้อมูลเพิ่มเติม payment.f2f.extra.prompt=ผู้สร้างสามารถกำหนด 'ข้อกำหนดในการให้บริการ' หรือเพิ่มข้อมูลการติดต่อสาธารณะได้ สิ่งเหล่านี้จะปรากฏพร้อมกับข้อเสนอ -payment.f2f.info=การค้าแบบ "Face to Face" (การเปิดเผยหน้าซึ่งกันและกัน) มีกฎแตกต่างกันและมีความเสี่ยงที่แตกต่างจากการทำธุรกรรมออนไลน์\n\nความแตกต่างหลักสำคัญคือ:\n●เพื่อนร่วมงานจำเป็นต้องแลกเปลี่ยนข้อมูลสถานที่และเวลาในการประชุมโดยใช้รายละเอียดการติดต่อที่ให้ไว้\n●คู่ค้าต้องนำแล็ปท็อปและยืนยันการชำระเงินที่ได้รับและการชำระเงินที่สถานที่นัดพบ\n●หากผู้ผลิตมี 'ข้อกำหนดในการให้บริการ' เป็นพิเศษเขาจะต้องระบุข้อมูลเหล่านั้นในช่องข้อความ 'ข้อมูลเพิ่มเติม' ในบัญชี\n●ในการรับข้อเสนอ ผู้รับข้อเสนอยอมรับข้อตกลงและเงื่อนไขของผู้สร้าง\n●ในกรณีที่มีข้อพิพาทผู้ไกล่เกลี่ยไม่สามารถช่วยได้มากนักเพราะมักยากที่จะได้รับหลักฐานพิสูจน์ว่าเกิดอะไรขึ้นในที่ประชุม ในกรณีเช่นนี้เงินทุน BTC อาจได้รับการล็อคอย่างไม่มีกำหนดหรือจนกว่าคู่ค้าการค้าจะทำข้อตกลง\n\nเพื่อให้มั่นใจว่าคุณเข้าใจรูปแบบที่แตกต่างของการซื้อขายแบบ "Face to Face" โปรดอ่านคำแนะนำและคำแนะนำที่: https://docs.bisq.network/trading-rules.html#f2f-trading ' +payment.f2f.info=การซื้อขายแบบตัวต่อตัวมีกฎระเบียบที่แตกต่างจากระบบออนไลน์ และมาพร้อมกับความเสี่ยงมากกว่าการธุรกรรมทางออนไลน์\n\nข้อแตกต่างคือ:\n● ผู้ที่กระทำการซื้อขายจำเป็นต้องมีการแลกเปลี่ยนข้อมูลเกี่ยวกับสถานที่นัดพบ และเวลาโดยการใช้ข้อมูลการติดต่อของพวกเขา\n● ผู้ที่กระทำการซื้อขายจำเป็นต้องนำคอมพิวเตอร์แล็ปท๊อป และทำการยืนยันข้อมูลของการ 'เงินโอนชำระ' และ 'เงินรับชำระ' ณ สถานที่นัดพบ\n● หากผู้สร้างมี 'ข้อกำหนดและเงื่อนไขอื่น' เพิ่มเติม จะต้องมีการแจ้งข้อมูลเพิ่มเติมส่วนนี้ใน 'ข้อมูลเพิ่มเติม' ในพื้นที่เพิ่มข้อความในแอคเคาวน์\n● ในการรับข้อเสนอ ผู้รับข้อเสนอยินยอมต่อผู้สร้างที่มีการกำหนดเงื่อนไขใน ''ข้อกำหนดและเงื่อนไขอื่น''\n● ในกรณีการพิพาท ผู้ไกล่เกลี่ยอาจสามารถช่วยเหลือในการเจรจาข้อพิพาทในบางส่วน เนื่องจากผู้ไกล่เกลี่ยไม่สามารถเป็นพยานชี้ชัดหลักฐานใดๆ ที่เกิดขึ้น ณ สถานที่จุดนัดพบของผู้ที่กระทำการซื้อขาย กรณีเช่นนี้การระดมทุน BTC อาจจะถูกล็อคโดยไม่มีข้อกำหนด หรือจนกว่าผู้กระทำการซื้อขายมีการตกลงยินยอมกัน\n\nเพื่อให้มั่นใจว่าคุณเข้าใจข้อแตกต่างในการซื้อขายแบบตัวต่อตัว โปรดอ่านวิธีการใช้งานและคำแนะนำได้ที่: 'https://docs.bisq.network/trading-rules.html#f2f-trading' payment.f2f.info.openURL=เปิดหน้าเว็บ payment.f2f.offerbook.tooltip.countryAndCity=ประเทศและเมือง: {0} / {1} payment.f2f.offerbook.tooltip.extra=ข้อมูลเพิ่มเติม: {0} @@ -2246,8 +2251,8 @@ validation.accountNrChars=หมายเลขบัญชีต้องปร validation.btc.invalidAddress=ที่อยู่ไม่ถูกต้อง โปรดตรวจสอบแบบฟอร์มที่อยู่ validation.integerOnly=โปรดป้อนตัวเลขจำนวนเต็มเท่านั้น validation.inputError=การป้อนข้อมูลของคุณเกิดข้อผิดพลาด: \n{0} -validation.bsq.insufficientBalance=Your available balance is {0}. -validation.btc.exceedsMaxTradeLimit=Your trade limit is {0}. +validation.bsq.insufficientBalance=ยอดคงเหลือของคุณ {0} +validation.btc.exceedsMaxTradeLimit=ขีดจำกัดการเทรดของคุณคือ {0} validation.bsq.amountBelowMinAmount=จำนวนเงินต่ำสุด {0} validation.nationalAccountId={0} ต้องประกอบด้วย {1} ตัวเลข @@ -2272,12 +2277,12 @@ validation.iban.checkSumInvalid=การตรวจสอบ IBAN ไม่ถ validation.iban.invalidLength=จำนวนต้องมีความยาว 15 ถึง 34 ตัวอักษร validation.interacETransfer.invalidAreaCode=รหัสพื้นที่ที่ไม่ใช่แคนาดา validation.interacETransfer.invalidPhone=รูปแบบหมายเลขโทรศัพท์ไม่ถูกต้อง และไม่ใช่ที่อยู่อีเมล -validation.interacETransfer.invalidQuestion=Must contain only letters, numbers, spaces and/or the symbols ' _ , . ? - -validation.interacETransfer.invalidAnswer=Must be one word and contain only letters, numbers, and/or the symbol - +validation.interacETransfer.invalidQuestion=ต้องประกอบด้วยตัวอักษร ตัวเลข เว้นวรรค และ/หรือ สัญลักษณ์ ' _ , . ? - +validation.interacETransfer.invalidAnswer=ต้องเป็นคำเดียว และประกอบด้วยตัวอักษร ตัวเลข และ/หรือ สัญลักษณ์ - เท่านั้น validation.inputTooLarge=ข้อมูลที่ป้อนต้องไม่เป็นจำนวนที่มากกว่า {0} -validation.inputTooSmall=Input has to be larger than {0} -validation.amountBelowDust=The amount below the dust limit of {0} is not allowed. -validation.length=Length must be between {0} and {1} -validation.pattern=Input must be of format: {0} -validation.noHexString=The input is not in HEX format. -validation.advancedCash.invalidFormat=Must be a valid email or wallet id of format: X000000000000 +validation.inputTooSmall=การป้อนเข้าจะต้องมีจำนวนมากกว่า {0} +validation.amountBelowDust=จำนวนยอดรวมต่ำกว่าข้อจำกัดของ Dust (dust หน่วยเล็กสุดของ bitcoin) ซึ่งเป็น {0} ไม่ได้รับการยินยอมให้ +validation.length=ความยาวจะต้องอยู่ระหว่าง {0} และ {1} +validation.pattern=การป้อนเข้าจะต้องเป็นรูปแบบ {0} +validation.noHexString=การป้อนเข้านั้นคือไม่ใช่รูปแบบของ HEX +validation.advancedCash.invalidFormat=จะต้องเป็นอีเมลหรือรหัสกระเป๋าสตางค์ที่ใช้งานได้: X000000000000 diff --git a/core/src/main/resources/i18n/displayStrings_vi.properties b/core/src/main/resources/i18n/displayStrings_vi.properties index fed9e470db..8ae18b0b2b 100644 --- a/core/src/main/resources/i18n/displayStrings_vi.properties +++ b/core/src/main/resources/i18n/displayStrings_vi.properties @@ -217,7 +217,7 @@ mainView.menu.dao=DAO mainView.marketPrice.provider=Giá theo mainView.marketPrice.label=Giá thị trường -mainView.marketPriceWithProvider.label=Giá thị trường theo {0} +mainView.marketPriceWithProvider.label=Giá thị trường theo {0} mainView.marketPrice.bisqInternalPrice=Giá giao dịch Bisq gần nhất mainView.marketPrice.tooltip.bisqInternalPrice=Không có giá thị trường từ nhà cung cấp bên ngoài.\nGiá hiển thị là giá giao dịch Bisq gần nhất với đồng tiền này. mainView.marketPrice.tooltip=Giá thị trường được cung cấp bởi {0}{1}\nCập nhật mới nhất: {2}\nURL nút nhà cung cấp: {3} @@ -299,6 +299,8 @@ market.trades.tooltip.candle.date=Ngày: offerbook.createOffer=Tạo chào giá offerbook.takeOffer=Nhận chào giá +offerbook.takeOfferToBuy=Take offer to buy {0} +offerbook.takeOfferToSell=Take offer to sell {0} offerbook.trader=Trader offerbook.offerersBankId=ID ngân hàng của người tạo (BIC/SWIFT): {0} offerbook.offerersBankName=Tên ngân hàng của người tạo: {0} @@ -441,7 +443,7 @@ takeOffer.takeOfferFundWalletInfo.msg=Bạn cần nộp {0} để nhận báo gi takeOffer.alreadyPaidInFunds=Bạn đã thanh toán, bạn có thể rút số tiền này tại màn hình \"Vốn/Gửi vốn\". takeOffer.paymentInfo=Thông tin thanh toán takeOffer.setAmountPrice=Cài đặt số tiền -takeOffer.alreadyFunded.askCancel=Bạn đã nộp tiền cho chào giá này.\nNếu bạn hủy bây giờ, số tiền của bạn sẽ được chuyển sang ví Bisq nội bộ của bạn và sẵn sàng để rút tại màn hình \Màn hình "Vốn/Gửi vốn\".\nBạn có chắc muốn hủy? +takeOffer.alreadyFunded.askCancel=Bạn đã nộp tiền cho chào giá này.\nNếu bạn hủy bây giờ, số tiền của bạn sẽ được chuyển sang ví Bisq nội bộ của bạn và sẵn sàng để rút tại màn hình Màn hình \"Vốn/Gửi vốn\".\nBạn có chắc muốn hủy? takeOffer.failed.offerNotAvailable=Nhận yêu cầu chào giá không thành công do chào giá không còn tồn tại. Có thể trong lúc chờ đợi, Thương gia khác đã nhận chào giá này. takeOffer.failed.offerTaken=Bạn không thể nhận chào giá này vì đã được nhận bởi Thương gia khác. takeOffer.failed.offerRemoved=Bạn không thể nhận chào giá này vì trong lúc chời đợi, chào giá này đã bị gỡ bỏ. @@ -528,7 +530,7 @@ portfolio.pending.step2_buyer.westernUnionMTCNInfo.headline=Gửi MTCN và biên portfolio.pending.step2_buyer.westernUnionMTCNInfo.msg=Bạn cần phải gửi MTCN (số theo dõi) và ảnh chụp giấy biên nhận bằng email cho người bán BTC.\nGiấy biên nhận phải nêu rõ họ tên, thành phố, quốc gia của người bán và số tiền. Địa chỉ email của người bán là: {0}.\n\nBạn đã gửi MTCN và hợp đồng cho người bán chưa? portfolio.pending.step2_buyer.halCashInfo.headline=Gửi mã HalCash portfolio.pending.step2_buyer.halCashInfo.msg=Bạn cần nhắn tin mã HalCash và mã giao dịch ({0}) tới người bán BTC. \nSố điện thoại của người bán là {1}.\n\nBạn đã gửi mã tới người bán chưa? -portfolio.pending.step2_buyer.fasterPaymentsHolderNameInfo=Một số ngân hàng có thể yêu cầu tên người nhận. Mã phân loại của Vương Quốc Anh và số tài khoản là đủ cho một giao dịch Chuyển Tiền Nhanh và tên người nhận không được ngân hàng nào xác minh. +portfolio.pending.step2_buyer.fasterPaymentsHolderNameInfo=Một số ngân hàng có thể yêu cầu tên người nhận. Mã phân loại của Vương Quốc Anh và số tài khoản là đủ cho một giao dịch Chuyển Tiền Nhanh và tên người nhận không được ngân hàng nào xác minh. portfolio.pending.step2_buyer.confirmStart.headline=Xác nhận rằng bạn đã bắt đầu thanh toán portfolio.pending.step2_buyer.confirmStart.msg=Bạn đã kích hoạt thanh toán {0} cho Đối tác giao dịch của bạn chưa? portfolio.pending.step2_buyer.confirmStart.yes=Có, tôi đã bắt đầu thanh toán @@ -560,12 +562,12 @@ portfolio.pending.step3_buyer.warn.part1b=tại nhà cung cấp thanh toán củ portfolio.pending.step3_buyer.warn.part2=Người bán BTC vẫn chưa xác nhận thanh toán của bạn!\nHãy kiểm tra xem {0} việc gửi thanh toán đi đã thành công chưa.\nNếu người bán BTC không xác nhận là đã nhận thanh toán của bạn trước {1} giao dịch sẽ bị điều tra bởi trọng tài. portfolio.pending.step3_buyer.openForDispute=Người bán BTC vẫn chưa xác nhận thanh toán của bạn!\nThời gian tối đa cho giao dịch đã hết.\nBạn có thể đợi lâu hơn và cho đối tác giao dịch thêm thời gian hoặc liên hệ trọng tài để mở khiếu nại. # suppress inspection "TrailingSpacesInProperty" -portfolio.pending.step3_seller.part=Đối tác giao dịch của bạn đã xác nhận rằng đã kích hoạt thanh toán {0}.\n\n +portfolio.pending.step3_seller.part=Your trading partner has confirmed that they have initiated the {0} payment.\n\n portfolio.pending.step3_seller.altcoin.explorer=Trên trình duyệt blockchain explorer {0} ưa thích của bạn portfolio.pending.step3_seller.altcoin.wallet=Trên ví {0} của bạn portfolio.pending.step3_seller.altcoin={0}Vui lòng kiểm tra {1} xem giao dịch tới địa chỉ nhận của bạn \n{2}\nđã nhận được đủ xác nhận blockchain hay chưa.\nSố tiền thanh toán phải là {3}\n\nBạn có thể copy & paste địa chỉ {4} của bạn từ màn hình chính sau khi đóng cửa sổ này. portfolio.pending.step3_seller.postal={0}Hãy kiểm tra xem bạn đã nhận được {1} \"Thư chuyển tiền US\" từ người mua BTC chưa.\n\nID giao dịch (nội dung \"lý do thanh toán\") của giao dịch là: \"{2}\" -portfolio.pending.step3_seller.bank=Đối tác giao dịch của bạn đã xác nhận rằng đã kích hoạt thanh toán {0}.\n\nHãy truy cập trang web ngân hàng online và kiểm tra xem bạn đã nhận được {1} từ người mua BTC chưa.\n\nID giao dịch (\"lý do thanh toán\" text) của giao dịch là: \"{2}\" +portfolio.pending.step3_seller.bank=Your trading partner has confirmed that they have initiated the {0} payment.\n\nPlease go to your online banking web page and check if you have received {1} from the BTC buyer.\n\nThe trade ID (\"reason for payment\" text) of the transaction is: \"{2}\"\n\n portfolio.pending.step3_seller.cash=Vì thanh toán được thực hiện qua Tiền gửi tiền mặt nên người mua BTC phải viết rõ \"KHÔNG HOÀN LẠI\" trên giấy biên nhận, xé làm 2 phần và gửi ảnh cho bạn qua email.\n\nĐể tránh bị đòi tiền lại, chỉ xác nhận bạn đã nhận được email và bạn chắc chắn giấy biên nhận là có hiệu lực.\nNếu bạn không chắc chắn, {0} portfolio.pending.step3_seller.moneyGram=Người mua phải gửi mã số xác nhận và ảnh chụp của hoá đơn qua email.\nHoá đơn cần ghi rõ họ tên đầy đủ, quốc gia, tiêu bang và số lượng. Vui lòng kiểm tra email nếu bạn nhận được số xác thực.\n\nSau khi popup đóng, bạn sẽ thấy tên người mua BTC và địa chỉ để nhận tiền từ MoneyGram.\n\nChỉ xác nhận hoá đơn sau khi bạn hoàn thành việc nhận tiền. portfolio.pending.step3_seller.westernUnion=Người mua phải gửi cho bạn MTCN (số theo dõi) và ảnh giấy biên nhận qua email.\nGiấy biên nhận phải ghi rõ họ tên của bạn, thành phố, quốc gia và số tiền. Hãy kiểm tra email xem bạn đã nhận được MTCN chưa.\n\nSau khi đóng cửa sổ này, bạn sẽ thấy tên và địa chỉ của người mua BTC để nhận tiền từ Western Union.\n\nChỉ xác nhận giấy biên nhận sau khi bạn đã nhận tiền thành công! @@ -620,7 +622,7 @@ portfolio.pending.step5_seller.received=Bạn đã nhận tradeFeedbackWindow.title=Chúc mừng giao dịch của bạn được hoàn thành. tradeFeedbackWindow.msg.part1=Chúng tôi rất vui lòng được nghe phản hồi của bạn. Điều đó sẽ giúp chúng tôi cải thiện phần mềm và hoàn thiện trải nghiệm người dùng. Nếu bạn muốn cung cấp phản hồi, vui lòng điền vào cuộc khảo sát ngắn dưới đây (không yêu cầu đăng nhập) ở: -tradeFeedbackWindow.msg.part2=nếu bạn có câu hỏi hay vấn đề, vui lòng liên hệ với người dùng khác và các nhàn đóng góp qua Bisq forum ở: +tradeFeedbackWindow.msg.part2=nếu bạn có câu hỏi hay vấn đề, vui lòng liên hệ với người dùng khác và các nhàn đóng góp qua Bisq forum ở: tradeFeedbackWindow.msg.part3=Cám ơn bạn đã sử dụng Bisq! portfolio.pending.role=Vai trò của tôi @@ -829,7 +831,7 @@ settings.net.onionAddressLabel=Địa chỉ onion của tôi settings.net.btcNodesLabel=Sử dụng nút Bitcoin Core thông dụng settings.net.bitcoinPeersLabel=Các đối tác được kết nối settings.net.useTorForBtcJLabel=Sử dụng Tor cho mạng Bitcoin -settings.net.bitcoinNodesLabel=nút Bitcoin Core để kết nối +settings.net.bitcoinNodesLabel=nút Bitcoin Core để kết nối settings.net.useProvidedNodesRadio=Sử dụng các nút Bitcoin Core đã cung cấp settings.net.usePublicNodesRadio=Sử dụng mạng Bitcoin công cộng settings.net.useCustomNodesRadio=Sử dụng nút Bitcoin Core thông dụng @@ -926,10 +928,10 @@ account.arbitratorSelection.minOne=Bạn cần có ít nhất một trọng tài account.altcoin.yourAltcoinAccounts=Tài khoản altcoin của bạn account.altcoin.popup.wallet.msg=Please be sure that you follow the requirements for the usage of {0} wallets as described on the {1} web page.\nUsing wallets from centralized exchanges where (a) you don''t control your keys or (b) which don''t use compatible wallet software is risky: it can lead to loss of the traded funds!\nThe arbitrator is not a {2} specialist and cannot help in such cases. account.altcoin.popup.wallet.confirm=Tôi hiểu và xác nhận rằng tôi đã biết loại ví mình cần sử dụng. -account.altcoin.popup.xmr.msg=Nếu bạn muốn giao dịch XMR trên Bisq, hãy chắc chắn bạn hiểu và tuân thủ các yêu cầu sau:\n\nĐể gửi XMR, bạn cần sử dụng hoặc là ví Monero GUI chính thức hoặc ví Monero CLI với nhãn luu-thongtin-tx được kích hoạt (mặc định trong phiên bản mới). Chắc chắn rằng bạn có thể truy cập khóa tx vì điều này là cần thiết trong trường hợp khiếu nại.\nví-monero-cli (dùng lệnh get_tx_key) \nví-monero-gui (đi đến tab lịch sử và nhấp vào nút (P) để lấy bằng chứng thanh toán)\n\nNgoài công cụ kiểm tra giao dịch XMR (https://xmr.llcoins.net/checktx.html) việc xác minh cũng có thể được thực hiện ngay trên ví.\nví-monero-cli: dùng lệnh (check_tx_key).\nví-monero-gui: ở trên Nâng cao>trang Chứng minh/Kiểm tra.\nVới những block explorer thông thường, chuyển khoản không thể xác minh được.\n\nBạn cần cung cấp cho trọng tài các dữ liệu sau trong trường hợp khiếu nại:\n- Khóa tx riêng\n- Hash của giao dịch\n- Địa chỉ công cộng của người nhận\n\nNếu bạn không thể cung cấp các dữ liệu trên hoặc nếu bạn sử dụng ví không thích hợp sẽ dẫn tới thua trong vụ khiếu nại. Người gửi XMR chịu trách nhiệm xác minh chuyển khoản XMR cho trọng tài trong trường hợp khiếu nại.\n\nKhông có ID thanh toán cầu thiết, chỉ là địa chỉ công cộng thông thường.\nNếu bạn không chắc chắn về quá trình, truy cập (https://www.getmonero.org/resources/user-guides/prove-payment.html) hoặc diễn đàn Monero (https://forum.getmonero.org) để tìm thêm thông tin. -account.altcoin.popup.blur.msg=Nếu bạn muốn giao dịch BLUR trên Bisq, hãy chắc chắn bạn hiểu và tuân thủ các yêu cầu sau:\n\nĐể gửi BLUR, bạn cần sử dụng ví CLI hoặc GUI của mạng BLUR. \n\nNếu bạn sử dụng ví CLI, sau khi chuyển tiền, ví sẽ hiển thị một mã giao dịch (tx ID). Bạn phải lưu thông tin này lại. Ngay sau khi chuyển tiền, bạn phải dùng lệnh 'get_tx_key' để lấy khóa riêng của giao dịch. Nếu bạn không thực hiện bước này, rất có thể sau này bạn sẽ không lấy được khóa giao dịch nữa. \n\nNếu bạn sử dụng ví GUI của mạng BLUR, khóa riêng giao dịch và tx ID sẽ được hiển thị ngay trên tab "Lịch sử". Ngay sau khi chuyển tiền, xác định vị trí của giao dịch mà bạn quan tâm. Nhấp chuột vào biểu tượng "?" ở góc phải bên dưới của hộp chứa giao dịch. Bạn cần phải lưu thông tin này lại. \n\nTrường hợp tranh chấp, bạn phải đưa ra cho trọng tài những thông tin sau:1.) mã giao dịch, 2.) khóa riêng của giao dịch, 3.) địa chỉ ví của người nhận. Trọng tài lúc đó sẽ sử dụng Blur Transaction Viewer (https://blur.cash/#tx-viewer) để xác minh giao dịch chuyển BLUR .\n\nNếu bạn không thể cung cấp các thông tin yêu cầu, bạn sẽ thua trong lần tranh chấp này. Trong tất cả mọi trường hợp tranh chấp, người chuyển BLUR chịu 100% trách nhiệm xác minh giao dịch với trọng tài.\n\nNếu bạn vẫn chưa hiểu rõ về những yêu cầu này, vui lòng vào Discord của BLUR (https://discord.gg/dMWaqVW) để được hỗ trợ. -account.altcoin.popup.ccx.msg=Nếu bạn muốn giao dịch CCX trên Bisq, hãy chắc chắn bạn hiểu các yêu cầu sau:\n\nĐể gửi CCX, bạn cần phải sử dụng ví chính thức của Conceal, ví CLI hay GUI đều được. Sau khi chuyển tiền, ví \nsẽ hiển thị khóa bí mật của giao dịch. Bạn phải lưu khóa bí mật này lại cùng với mã giao dịch (tx ID) và địa chỉ ví công khai \ncủa người nhận phòng khi có tranh chấp. Trường hợp có tranh chấp, bạn phải cung cấp cả ba thông tin này cho trọng tài , sau đó trọng tài sẽ dùng Conceal Transaction Viewer \n(https://explorer.conceal.network/txviewer).\nVì Conceal là một đồng coin riêng tư, nên các trang dò khối sẽ không thể xác minh giao dịch chuyển tiền.\n\nNếu bạn không thể cung cấp các thông tin yêu cầu cho trọng tài, bạn sẽ thua trong lần tranh chấp này.\nNếu bạn không lưu lại khóa giao dịch bí mật ngay sau khi thực hiện chuyển CCX, sau này bạn sẽ không lấy lại được nữa.\nNếu bạn vẫn chưa hiểu rõ về những yêu cầu này, vui lòng vào Discord của Conceal (http://discord.conceal.network) để được hỗ trợ. -account.altcoin.popup.drgl.msg=Để giao dịch Dragonglass trên Bisq, bạn cần phải hiểu và tuân thủ các yêu cầu sau:\n\nĐể đảm bảo tính riêng tư, những giao dịch do Dragonglass cung cấp không thể xác minh bằng blockchain công cộng. Nếu được yêu cầu, bạn có thể chứng minh giao dịch thanh toán của bạn bằng cách sử dụng khóa-riêng-TXN.\nKhóa riêng-TXN là khóa dùng một lần được tạo tự động cho mỗi giao dịch và chỉ có thể truy cập thông qua ví DRGL của bạn. \nDù là giao dịch được thực hiện trên ví DRGL GUI (trong hội thoại chi tiết giao dịch) hay bằng ví giản đơn Dragonglass CLI (dùng lệnh "get_tx_key"), thì đều cần phải có phiên bản Dragonglass 'Oathkeeper' hoặc cao hơn.\n\nTrường hợp tranh chấp, bạn cần phải cung cấp cho trọng tài những dữ liệu sau:\n- Khóa riêng-TXN\n- Mã giao dịch\n- Địa chỉ công cộng của người nhận\n\nViệc xác minh có thể được thực hiện bằng cách sử dụng những thông tin ở trên làm dữ liệu nhập tại \(http://drgl.info/#check_txn).\n\nNếu bạn không cung cấp được các thông tin trên, hoặc nếu bạn sử dụng một ví không hợp lệ, điều này có thể khiến bạn thua trong lần tranh chấp này. Người gửi Dragonglass chịu trách nhiệm xác minh giao dịch chuyển DRGL cho trọng tài trong trường hợp có tranh chấp. Việc sử dụng PaymentID không được yêu cầu. \n\nNếu như bạn vẫn chưa chắc chắn về bất cứ phần nào trong quá trình này,liên hệ Dragonglass trên Discord (http://discord.drgl.info) để được hỗ trợ. +account.altcoin.popup.xmr.msg=Trading XMR on Bisq requires that you understand and fulfill the following requirements:\n\nFor sending XMR, you need to use either the official Monero GUI wallet or Monero CLI wallet with the store-tx-info flag enabled (default in new versions). Please be sure you can access the tx key as that would be required in case of a dispute.\nmonero-wallet-cli (use the command get_tx_key)\nmonero-wallet-gui (go to history tab and click on the (P) button for payment proof)\n\nIn addition to XMR checktx tool (https://xmr.llcoins.net/checktx.html) verification can also be accomplished in-wallet.\nmonero-wallet-cli : using command (check_tx_key).\nmonero-wallet-gui : on the Advanced > Prove/Check page.\nAt normal block explorers the transfer is not verifiable.\n\nYou need to provide the arbitrator the following data in case of a dispute:\n- The tx private key\n- The transaction hash\n- The recipient's public address\n\nFailure to provide the above data, or if you used an incompatible wallet, will result in losing the dispute case. The XMR sender is responsible for providing verification of the XMR transfer to the arbitrator in case of a dispute.\n\nThere is no payment ID required, just the normal public address.\nIf you are not sure about that process visit (https://www.getmonero.org/resources/user-guides/prove-payment.html) or the Monero forum (https://forum.getmonero.org) to find more information. +account.altcoin.popup.blur.msg=Trading BLUR on Bisq requires that you understand and fulfill the following requirements:\n\nTo send BLUR you must use the Blur Network CLI or GUI Wallet. \n\nIf you are using the CLI wallet, a transaction hash (tx ID) will be displayed after a transfer is sent. You must save this information. Immediately after sending the transfer, you must use the command 'get_tx_key' to retrieve the transaction private key. If you fail to perform this step, you may not be able to retrieve the key later. \n\nIf you are using the Blur Network GUI Wallet, the transaction private key and transaction ID can be found conveniently in the "History" tab. Immediately after sending, locate the transaction of interest. Click the "?" symbol in the lower-right corner of the box containing the transaction. You must save this information. \n\nIn the event that arbitration is necessary, you must present the following to an arbitrator: 1.) the transaction ID, 2.) the transaction private key, and 3.) the recipient's address. The arbitrator will then verify the BLUR transfer using the Blur Transaction Viewer (https://blur.cash/#tx-viewer).\n\nFailure to provide the required information to the arbitrator will result in losing the dispute case. In all cases of dispute, the BLUR sender bears 100% of the burden of responsibility in verifying transactions to an arbitrator. \n\nIf you do not understand these requirements, do not trade on Bisq. First, seek help at the Blur Network Discord (https://discord.gg/dMWaqVW). +account.altcoin.popup.ccx.msg=Trading CCX on Bisq requires that you understand the following requirements:\n\nTo send CCX you must use an official Conceal wallet, either CLI or GUI. After sending a transfer payment, the wallets\ndisplay the transaction secret key. You must save it along with the transaction hash (ID) and the recipient's public\naddress in case arbitration is necessary. In such a case, you must give all three to the arbitrator, who will then\nverify the CCX transfer using the Conceal Transaction Viewer (https://explorer.conceal.network/txviewer).\nBecause Conceal is a privacy coin, block explorers cannot verify transfers.\n\nFailure to provide the required data to the arbitrator will result in losing the dispute case.\nIf you do not save the transaction secret key immediately after transferring CCX, it cannot be recovered later.\nIf you do not understand these requirements, seek help at the Conceal discord (http://discord.conceal.network). +account.altcoin.popup.drgl.msg=Trading Dragonglass on Bisq requires that you understand and fulfill the following requirements:\n\nBecause of the privacy Dragonglass provides, a transaction is not verifiable on the public blockchain. If required, you can prove your payment through the use of your TXN-Private-Key.\nThe TXN-Private Key is a one-time key automatically generated for every transaction that can only be accessed from within your DRGL wallet.\nEither by DRGL-wallet GUI (inside transaction details dialog) or by the Dragonglass CLI simplewallet (using command "get_tx_key").\n\nDRGL version 'Oathkeeper' and higher are REQUIRED for both.\n\nIn case of a dispute, you must provide the arbitrator the following data:\n- The TXN-Private key\n- The transaction hash\n- The recipient's public address\n\nVerification of payment can be made using the above data as inputs at (http://drgl.info/#check_txn).\n\nFailure to provide the above data, or if you used an incompatible wallet, will result in losing the dispute case. The Dragonglass sender is responsible for providing verification of the DRGL transfer to the arbitrator in case of a dispute. Use of PaymentID is not required.\n\nIf you are unsure about any part of this process, visit Dragonglass on Discord (http://discord.drgl.info) for help. account.altcoin.popup.ZEC.msg=Khi sử dụng {0} bạn chỉ có thể sử dụng địa chỉ rõ ràng (bắt đầu bằng t) không phải địa chỉ z (riêng tư), vì trọng tài sẽ không thể xác minh giao dịch với địa chỉ z. account.altcoin.popup.XZC.msg=Khi sử dụng {0} bạn chỉ có thể sử dụng địa chỉ rõ ràng (có thể theo dõi) chứ không phải địa chỉ không thể theo dõi, vì trọng tài không thể xác minh giao dịch với địa chỉ không thể theo dõi tại một block explorer. account.altcoin.popup.bch=Bitcoin Cash và Bitcoin Clashic được bảo vệ không chào lại. Nếu bạn sử dụng các coin này, phải chắc chắn bạn đã thực hiện đủ biện pháp phòng ngừa và hiểu rõ tất cả nội dung. Bạn có thể bị mất khi gửi một coin và vô tình gửi coin như vậy cho block chain khác. Do các "airdrop coins" này có cùng lịch sử với Bitcoin blockchain do đó có một số nguy cơ mất an toàn và quyền riêng tư.\n\nVui lòng đọc tại diễn đàn Bisq để biết thêm về chủ đề này: https://forum.bisq.io/t/airdrop-coins-information-thread-bch-btg-bchc @@ -1306,7 +1308,7 @@ dao.burnBsq.assets.lookBackPeriod=Giai đoạn xác minh dao.burnBsq.assets.trialFee=Phí cho giai đoạn dùng thử dao.burnBsq.assets.totalFee=Tổng số phí đã trả dao.burnBsq.assets.days={0} ngày -dao.burnBsq.assets.toFewDays=Phí tài sản quá thấp. Số ngày tối thiểu cho giai đoạn dùng thử là {0}. +dao.burnBsq.assets.toFewDays=The asset fee is too low. The min. amount of days for the trial period is {0}. # suppress inspection "UnusedProperty" dao.assetState.UNDEFINED=Không xác định @@ -1322,7 +1324,7 @@ dao.assetState.REMOVED_BY_VOTING=Bị gỡ bỏ thông qua bỏ phiếu dao.proofOfBurn.header=Bằng chứng đốt dao.proofOfBurn.amount=Số tiền dao.proofOfBurn.preImage=Pre-image -dao.proofOfĐốt.burn=Đốt +dao.proofOfBurn.burn=Đốt dao.proofOfBurn.allTxs=Tất cả bằng chứng của các giao dịch đốt dao.proofOfBurn.myItems=Bằng chứng giao dịch đốt của tôi dao.proofOfBurn.date=Ngày @@ -1400,7 +1402,7 @@ dao.proposal.type.short.CONFISCATE_BOND=Tịch thu tài sản đảm bảo dao.proposal.details=Thông tin về đề xuất dao.proposal.selectedProposal=Đề xuất được chọn dao.proposal.active.header=Các đề xuất có hiệu lực -dao.proposal.active.remove.confirm=Bạn có chắc bạn muốn gỡ bỏ đề xuất này?\nPhí đề xuất đã trả sẽ bị mất. +dao.proposal.active.remove.confirm=Bạn có chắc bạn muốn gỡ bỏ đề xuất này?\nPhí đề xuất đã trả sẽ bị mất. dao.proposal.active.remove.doRemove=Vâng, xin hãy gở đề xuất của tôi dao.proposal.active.remove.failed=Không thể gỡ bỏ đề xuất. dao.proposal.myVote.accept=Chấp nhận đề xuất @@ -1562,7 +1564,7 @@ contractWindow.title=Thông tin khiếu nại contractWindow.dates=Ngày chào giá / Ngày giao dịch contractWindow.btcAddresses=Địa chỉ Bitcoin người mua BTC / người bán BTC contractWindow.onions=Địa chỉ mạng người mua BTC / người bán BTC -contractWindow.numDisputes=Số khiếu nại người mua BTC / người bán BTC +contractWindow.numDisputes=Số khiếu nại người mua BTC / người bán BTC contractWindow.contractHash=Hash của hợp đồng displayAlertMessageWindow.headline=Thông tin quan trọng! @@ -1746,7 +1748,7 @@ popup.headline.error=Lỗi popup.doNotShowAgain=Không hiển thị lại popup.reportError.log=Mở log file popup.reportError.gitHub=Báo cáo cho người theo dõi vấn đề GitHub -popup.reportError={0}\n\nTo help us to improve the software please report the bug on our issue tracker on GitHub (https://github.com/bisq-network/bisq-desktop/issues).\nThe error message will be copied to the clipboard when you click a button below.\nIt will make debugging easier if you can attach the bisq.log file as well. +popup.reportError={0}\n\nTo help us to improve the software please report this bug by opening a new issue at https://github.com/bisq-network/bisq/issues.\nThe above error message will be copied to the clipboard when you click either of the buttons below.\nIt will make debugging easier if you include the bisq.log file by pressing "Open log file", saving a copy, and attaching it to your bug report. popup.error.tryRestart=Hãy khởi động lại ứng dụng và kiểm tra kết nối mạng để xem bạn có thể xử lý vấn đề này hay không. popup.error.takeOfferRequestFailed=Có lỗi xảy ra khi ai đó cố gắng để nhận một trong các chào giá của bạn:\n{0} @@ -1787,7 +1789,7 @@ popup.info.securityDepositInfo=To ensure both traders follow the trade protocol, popup.info.cashDepositInfo=Chắc chắn rằng khu vực của bạn có chi nhánh ngân hàng có thể gửi tiền mặt.\nID (BIC/SWIFT) ngân hàng của bên bán là: {0}. popup.info.cashDepositInfo.confirm=Tôi xác nhận tôi đã gửi tiền -popup.info.shutDownWithOpenOffers=Bisq đang đóng, nhưng vẫn có các chào giá đang mở. \n\nNhững chào giá này sẽ không có tại mạng P2P khi Bisq đang đóng, nhưng chúng sẽ được công bố lại trên mạng P2P vào lần tiếp theo bạn khởi động Bisq.\nĐể giữ các chào giá luôn trực tuyến, vui lòng để Bisq chạy và đảm bảo là máy tính của bạn cũng đang trực tuyến(có nghĩa là đảm bảo là máy tính của bạn không chuyển về chế độ chờ...nếu màn hình về chế độ chờ thì không sao). +popup.info.shutDownWithOpenOffers=Bisq đang đóng, nhưng vẫn có các chào giá đang mở. \n\nNhững chào giá này sẽ không có tại mạng P2P khi Bisq đang đóng, nhưng chúng sẽ được công bố lại trên mạng P2P vào lần tiếp theo bạn khởi động Bisq.\nĐể giữ các chào giá luôn trực tuyến, vui lòng để Bisq chạy và đảm bảo là máy tính của bạn cũng đang trực tuyến(có nghĩa là đảm bảo là máy tính của bạn không chuyển về chế độ chờ...nếu màn hình về chế độ chờ thì không sao). popup.privateNotification.headline=Thông báo riêng tư quan trọng! @@ -1805,6 +1807,9 @@ popup.attention.forTradeWithId=Cần chú ý khi giao dịch có ID {0} popup.roundedFiatValues.headline=Tính năng bảo mật mới: Giá trị tiền pháp định đã làm tròn popup.roundedFiatValues.msg=Để tăng tính bảo mật, lượng {0} đã được làm tròn.\n\nTùy vào bạn đang sử dụng phiên bản nào của ứng dụng mà bạn sẽ phải trả hay nhận được hoặc là giá trị thập phân hoặc là giá trị đã làm tròn. \n\nCả hai giá trị này từ đây sẽ tuân theo giao thức giao dịch.\n\nCũng nên lưu ý là giá trị BTC sẽ tự động thay đổi sao cho khớp nhất có thể với lượng tiền pháp định đã được làm tròn. +popup.info.multiplePaymentAccounts.headline=Multiple payment accounts available +popup.info.multiplePaymentAccounts.msg=You have multiple payment accounts available for this offer. Please make sure you've picked the right one. + #################################################################### # Notifications @@ -2065,7 +2070,7 @@ payment.emailOrMobile=Email hoặc số điện thoại payment.useCustomAccountName=Sử dụng tên tài khoản thông dụng payment.maxPeriod=Thời gian giao dịch cho phép tối đa payment.maxPeriodAndLimit=Thời gian giao dịch tối đa: {0} / Giới hạn giao dịch tối đa: {1} / Tuổi tài khoản: {2} -payment.maxPeriodAndLimitCrypto=Thời gian giao dịch tối đa: {0} / Giới hạn giao dịch tối đa: {1} +payment.maxPeriodAndLimitCrypto=Thời gian giao dịch tối đa: {0} / Giới hạn giao dịch tối đa: {1} payment.currencyWithSymbol=Tiền tệ: {0} payment.nameOfAcceptedBank=Tên NH được chấp nhận payment.addAcceptedBank=Thêm NH được chấp nhận @@ -2085,10 +2090,10 @@ payment.clearXchange.info=Chắc chắc bạn đáp ứng các yêu cầu khi s payment.moneyGram.info=Khi dùng MoneyGram người mua BTC phải gửi số xác nhận và ảnh chụp hoá đơn đến emailnguoiwf bán. Hoá đơn phải chỉ rõ tên đầy đủ, quốc gia, tiểu bang và số lượng. Người mua sẽ trình email của người bán ra trong quá trình giao dịch payment.westernUnion.info=Khi sử dụng Western Union, người mua BTC phải gửi MTCN (số theo dõi) và ảnh giấy biên nhận bằng email cho người bán BTC. Giấy biên nhận phải nêu rõ họ tên, thành phố, quốc gia của người bán và số tiền. Người mua sẽ được hiển thị email người bán trong quá trình giao dịch. -payment.halCash.info=Khi sử dụng HalCash người mua BTC cần phải gửi cho người bán BTC mã HalCash bằng tin nhắn điện thoại.\n\nVui lòng đảm bảo là lượng tiền này không vượt quá số lượng tối đa mà ngân hàng của bạn cho phép gửi khi dùng HalCash. Số lượng rút tối thiểu là 10 EUR và tối đa là 600 EUR. Nếu rút nhiều lần thì giới hạn sẽ là 3000 EUR/ người nhận/ ngày và 6000 EUR/người nhận/tháng. Vui lòng kiểm tra chéo những giới hạn này với ngân hàng của bạn để chắc chắn là họ cũng dùng những giới hạn như ghi ở đây.\n\nSố tiền rút phải là bội số của 10 EUR vì bạn không thể rút các mệnh giá khác từ ATM. Giao diện người dùng ở phần 'tạo chào giá' và 'chấp nhận chào giá' sẽ điều chỉnh lượng btc sao cho lượng EUR tương ứng sẽ chính xác. Bạn không thể dùng giá thị trường vì lượng EUR có thể sẽ thay đổi khi giá thay đổi.\n\nTrường hợp tranh chấp, người mua BTC cần phải cung cấp bằng chứng chứng minh mình đã gửi EUR. +payment.halCash.info=When using HalCash the BTC buyer needs to send the BTC seller the HalCash code via a text message from their mobile phone.\n\nPlease make sure to not exceed the maximum amount your bank allows you to send with HalCash. The min. amount per withdrawal is 10 EUR and the max. amount is 600 EUR. For repeated withdrawals it is 3000 EUR per receiver per day and 6000 EUR per receiver per month. Please cross check those limits with your bank to be sure they use the same limits as stated here.\n\nThe withdrawal amount must be a multiple of 10 EUR as you cannot withdraw other amounts from an ATM. The UI in the create-offer and take-offer screen will adjust the BTC amount so that the EUR amount is correct. You cannot use market based price as the EUR amount would be changing with changing prices.\n\nIn case of a dispute the BTC buyer needs to provide the proof that they sent the EUR. payment.limits.info=Hãy hiểu rằng tất cả giao dịch chuyển khoản ngân hàng đều có thể có rủi ro bị đòi tiền lại.\n\nĐể hạn chế rủi ro này, Bisq đã đặt giới hạn trên mỗi giao dịch dựa trên hai yếu tố:\n\n1. Mức rủi ro đòi tiền lại ước tính cho mỗi phương thức thanh toán áp dụng\n2. Tuổi tài khoản của bạn đối với phương thức thanh toán\n\nTài khoản bạn đang tạo là mới và tuổi bằng không. Sau khi tài khoản của bạn được hai tháng tuổi, giới hạn trên mỗi giao dịch của bạn sẽ tăng lên theo:\n\n● Trong tháng đầu tiên, giới hạn trên mỗi giao dịch của bạn là {0}\n● Trong tháng thứ hai, giới hạn trên mỗi giao dịch của bạn là {1}\n● Sau hai tháng, giới hạn trên mỗi giao dịch của bạn là {2}\n\nLưu ý không có giới hạn trên tổng số lần bạn có thể giao dịch. -payment.cashDeposit.info=Vui lòng xác nhận rằng ngân hàng của bạn cho phép nạp tiền mặt vào tài khoản của người khác. Chẳng hạn, Ngân Hàng Mỹ và Wells Fargo không còn cho phép nạp tiền như vậy nữa. +payment.cashDeposit.info=Vui lòng xác nhận rằng ngân hàng của bạn cho phép nạp tiền mặt vào tài khoản của người khác. Chẳng hạn, Ngân Hàng Mỹ và Wells Fargo không còn cho phép nạp tiền như vậy nữa. payment.f2f.contact=thông tin liên hệ payment.f2f.contact.prompt=Bạn muốn liên hệ với đối tác giao dịch qua đâu? (email, địa chỉ, số điện thoại,....) @@ -2098,7 +2103,7 @@ payment.f2f.optionalExtra=Thông tin thêm tuỳ chọn. payment.f2f.extra=thông tin thêm payment.f2f.extra.prompt=Người tạo có thể đặt ‘ các điều khoản’ hoặc thêm thông tin liên hệ mở, để hiểnnthij trong báo giá -payment.f2f.info=Những giao dịch ‘mặt đối mặt’ đi kèm những quy tắc và rủi ro khác với giao dịch trực tuyến.\n\nNhững khác biệt chính đó là:\n● Bên mua và bán cần trao đổi thông tin về thời gian và địa điểm gặp mặt sử dụng những thông tin liên lạc mà họ cung cấp. \n● Bên mua và bán cần phải mang theo laptop và thực hiện việc xác nhận ‘đã gửi tiền’ và ‘đã nhận tiền’ tại nơi gặp.\n● Nếu bên chào giá có những ‘điều khoản và điều kiện’ đặc biệt, họ sẽ phải nêu ra ở phần ‘thông tin thêm’ trong tài khoản.\n● Chấp nhận chào giá tức là bên chấp nhận đã đồng ý với các ‘điều khoản và điều kiện’ của bên chào giá.\n● Trong trường hợp tranh chấp, trọng tài sẽ không giúp được gì nhiều bởi vì để cung cấp các bằng chứng không thể thay đổi về những việc xảy ra tại nơi gặp mặt thường là rất khó. Trong những trường hợp như vậy, số BTC này có thể sẽ bị khóa vô thời hạn hoặc khóa đến khi bên mua và bán đạt được thỏa thuận. \n\nĐể chắc chắn là bạn hiểu rõ sự khác nhau của các giao dịch ‘mặt đối mặt’vui lòng đọc hướng dẫn và khuyến nghị tại: 'https://docs.bisq.network/trading-rules.html#f2f-trading' +payment.f2f.info='Face to Face' trades have different rules and come with different risks than online transactions.\n\nThe main differences are:\n● The trading peers need to exchange information about the meeting location and time by using their provided contact details.\n● The trading peers need to bring their laptops and do the confirmation of 'payment sent' and 'payment received' at the meeting place.\n● If a maker has special 'terms and conditions' they must state those in the 'Additional information' text field in the account.\n● By taking an offer the taker agrees to the maker's stated 'terms and conditions'.\n● In case of a dispute the arbitrator cannot help much as it is usually hard to get tamper proof evidence of what happened at the meeting. In such cases the BTC funds might get locked indefinitely or until the trading peers come to an agreement.\n\nTo be sure you fully understand the differences with 'Face to Face' trades please read the instructions and recommendations at: 'https://docs.bisq.network/trading-rules.html#f2f-trading' payment.f2f.info.openURL=Mở trang web payment.f2f.offerbook.tooltip.countryAndCity=Đất nước và thành phố:{0}/{1} payment.f2f.offerbook.tooltip.extra=Thông tin thêm: {0} diff --git a/core/src/main/resources/i18n/displayStrings_zh.properties b/core/src/main/resources/i18n/displayStrings_zh.properties index 15434ef0dd..ccea4cc7c6 100644 --- a/core/src/main/resources/i18n/displayStrings_zh.properties +++ b/core/src/main/resources/i18n/displayStrings_zh.properties @@ -299,6 +299,8 @@ market.trades.tooltip.candle.date=日期: offerbook.createOffer=创建委托 offerbook.takeOffer=下单 +offerbook.takeOfferToBuy=Take offer to buy {0} +offerbook.takeOfferToSell=Take offer to sell {0} offerbook.trader=商人 offerbook.offerersBankId=卖家的银行 ID: {0} offerbook.offerersBankName=卖家的银行名称: {0} @@ -560,12 +562,12 @@ portfolio.pending.step3_buyer.warn.part1b=在您的支付供应商(例如:银行 portfolio.pending.step3_buyer.warn.part2=BTC卖家仍然没有确认您的付款！\n如果付款发送成功，请检查{0}\n如果BTC卖家在{1}之前不确认收到您的付款，交易将由仲裁员进行调查。 portfolio.pending.step3_buyer.openForDispute=BTC卖家尚未确认您的付款！\n最大 交易期已过\n请联系仲裁员以争取解决纠纷。 # suppress inspection "TrailingSpacesInProperty" -portfolio.pending.step3_seller.part=您的贸易伙伴已确认他已发起{0}付款。\n\n +portfolio.pending.step3_seller.part=Your trading partner has confirmed that they have initiated the {0} payment.\n\n portfolio.pending.step3_seller.altcoin.explorer=on your favorite {0} blockchain explorer portfolio.pending.step3_seller.altcoin.wallet=at your {0} wallet portfolio.pending.step3_seller.altcoin={0}Please check {1} if the transaction to your receiving address\n{2}\nhas already sufficient blockchain confirmations.\nThe payment amount has to be {3}\n\nYou can copy & paste your {4} address from the main screen after closing that popup. portfolio.pending.step3_seller.postal={0}请检查您是否已经从BTC买家收到了{1} \"US Postal Money Order\" \n\n交易ID(“付款原因”文本)是：“{2}” -portfolio.pending.step3_seller.bank=Your trading partner has confirmed that he initiated the {0} payment.\n\nPlease go to your online banking web page and check if you have received {1} from the BTC buyer.\n\nThe trade ID (\"reason for payment\" text) of the transaction is: \"{2}\"\n\n +portfolio.pending.step3_seller.bank=Your trading partner has confirmed that they have initiated the {0} payment.\n\nPlease go to your online banking web page and check if you have received {1} from the BTC buyer.\n\nThe trade ID (\"reason for payment\" text) of the transaction is: \"{2}\"\n\n portfolio.pending.step3_seller.cash=Because the payment is done via Cash Deposit the BTC buyer has to write \"NO REFUND\" on the paper receipt, tear it in 2 parts and send you a photo by email.\n\nTo avoid chargeback risk, only confirm if you received the email and if you are sure the paper receipt is valid.\nIf you are not sure, {0} portfolio.pending.step3_seller.moneyGram=The buyer has to send you the Authorisation number and a photo of the receipt by email.\nThe receipt must clearly show your full name, country, state and the amount. Please check your email if you received the Authorisation number.\n\nAfter closing that popup you will see the BTC buyer's name and address for picking up the money from MoneyGram.\n\nOnly confirm receipt after you have successfully picked up the money! portfolio.pending.step3_seller.westernUnion=买方必须发送MTCN(跟踪号码)和一张收据的照片。\n收据必须清楚地显示您的全名,城市,国家,数量。如果您收到MTCN，请查收邮件。\n\n关闭弹窗后，您将看到BTC买家的姓名和在西联的收钱地址。\n\n只有在您成功收到钱之后，再确认收据！\n @@ -926,10 +928,10 @@ account.arbitratorSelection.minOne=您至少需要选择一名仲裁员 account.altcoin.yourAltcoinAccounts=Your altcoin accounts account.altcoin.popup.wallet.msg=Please be sure that you follow the requirements for the usage of {0} wallets as described on the {1} web page.\nUsing wallets from centralized exchanges where (a) you don''t control your keys or (b) which don''t use compatible wallet software is risky: it can lead to loss of the traded funds!\nThe arbitrator is not a {2} specialist and cannot help in such cases. account.altcoin.popup.wallet.confirm=我了解并确定我知道我需要哪种钱包。 -account.altcoin.popup.xmr.msg=If you want to trade XMR on Bisq please be sure you understand and fulfill the following requirements:\n\nFor sending XMR you need to use either the official Monero GUI wallet or Monero CLI wallet with the store-tx-info flag enabled (default in new versions). Please be sure you can access the tx key as that would be required in case of a dispute.\nmonero-wallet-cli (use the command get_tx_key)\nmonero-wallet-gui (go to history tab and click on the (P) button for payment proof)\n\nIn addition to XMR checktx tool (https://xmr.llcoins.net/checktx.html) verification can also be accomplished in-wallet.\nmonero-wallet-cli : using command (check_tx_key).\nmonero-wallet-gui : on the Advanced > Prove/Check page.\nAt normal block explorers the transfer is not verifiable.\n\nYou need to provide the arbitrator the following data in case of a dispute:\n- The tx private key\n- The transaction hash\n- The recipient's public address\n\nIf you cannot provide the above data or if you used an incompatible wallet it would result in losing the dispute case. The XMR sender is responsible to be able to verify the XMR transfer to the arbitrator in case of a dispute.\n\nThere is no payment ID required, just the normal public address.\nIf you are not sure about that process visit (https://www.getmonero.org/resources/user-guides/prove-payment.html) or the Monero forum (https://forum.getmonero.org) to find more information. -account.altcoin.popup.blur.msg=If you want to trade BLUR on Bisq please be sure you understand and fulfill the following requirements:\n\nTo send BLUR you must use the Blur Network CLI or GUI Wallet. \n\nIf you are using the CLI wallet, a transaction hash (tx ID) will be displayed after a transfer is sent. You must save this information. Immediately after sending the transfer, you must use the command 'get_tx_key' to retrieve the transaction private key. If you fail to perform this step, you may not be able to retrieve the key later. \n\nIf you are using the Blur Network GUI Wallet, the transaction private key and transaction ID can be found conveniently in the "History" tab. Immediately after sending, locate the transaction of interest. Click the "?" symbol in the lower-right corner of the box containing the transaction. You must save this information. \n\nIn the event that arbitration is necessary, you must present the following to an arbitrator: 1.) the transaction ID, 2.) the transaction private key, and 3.) the recipient's address. The arbitrator will then verify the BLUR transfer using the Blur Transaction Viewer (https://blur.cash/#tx-viewer).\n\nIf you cannot provide the required information to the arbitrator, you will lose the dispute. In all cases of dispute, the BLUR sender bears 100% of the burden of responsiblity in verifying transactions to an arbitrator. \n\nIf you do not understand these requirements, do not trade on Bisq. First, seek help at the Blur Network Discord (https://discord.gg/dMWaqVW). -account.altcoin.popup.ccx.msg=If you want to trade CCX on Bisq please be sure you understand the following requirements:\n\nTo send CCX you must use an official Conceal wallet, either CLI or GUI. After sending a transfer payment, the wallets\ndisplay the transaction secret key. You must save it along with the transaction hash (ID) and the recipient's public\naddress in case arbitration is necessary. In such a case, you must give all three to the arbitrator, who will then\nverify the CCX transfer using the Conceal Transaction Viewer (https://explorer.conceal.network/txviewer).\nBecause Conceal is a privacy coin, block explorers cannot verify transfers.\n\nIf you cannot provide the required data to the arbitrator, you will lose the dispute case.\nIf you do not save the transaction secret key immediately after transferring CCX, it cannot be recovered later.\nIf you do not understand these requirements, seek help at the Conceal discord (http://discord.conceal.network). -account.altcoin.popup.drgl.msg=Trading Dragonglass on Bisq requires that you understand and fulfill the following requirements:\n\nBecause of the privacy Dragonglass provides a transaction is not verifyable on the public blockchain. If required you can prove your payment thru use of your TXN-Private-Key.\nThe TXN-Private Key is a one-time key automatically generated for every transaction that can only be accessed from within your DRGL wallet.\nEither by DRGL-wallet GUI (inside transaction details dialog) or by the Dragonglass CLI simplewallet (using command "get_tx_key").\n\nDRGL version 'Oathkeeper' and higher are REQUIRED for both.\n\nIn case of a dispute, you must provide the arbitrator the following data:\n- The TXN-Private key\n- The transaction hash\n- The recipient's public address\n\nVerification of payment can be made using the above data as inputs at \ (http://drgl.info/#check_txn).\n\nIf you cannot provide the above data or if you used an incompatible wallet it would result in losing the dispute case. The Dragonglass sender is responsible to be able to verify the DRGL transfer to the arbitrator in case of a dispute. Use of PaymentID is not required.\n\nIf you are unsure about any part of this process, visit Dragonglass on Discord (http://discord.drgl.info) for help. +account.altcoin.popup.xmr.msg=Trading XMR on Bisq requires that you understand and fulfill the following requirements:\n\nFor sending XMR, you need to use either the official Monero GUI wallet or Monero CLI wallet with the store-tx-info flag enabled (default in new versions). Please be sure you can access the tx key as that would be required in case of a dispute.\nmonero-wallet-cli (use the command get_tx_key)\nmonero-wallet-gui (go to history tab and click on the (P) button for payment proof)\n\nIn addition to XMR checktx tool (https://xmr.llcoins.net/checktx.html) verification can also be accomplished in-wallet.\nmonero-wallet-cli : using command (check_tx_key).\nmonero-wallet-gui : on the Advanced > Prove/Check page.\nAt normal block explorers the transfer is not verifiable.\n\nYou need to provide the arbitrator the following data in case of a dispute:\n- The tx private key\n- The transaction hash\n- The recipient's public address\n\nFailure to provide the above data, or if you used an incompatible wallet, will result in losing the dispute case. The XMR sender is responsible for providing verification of the XMR transfer to the arbitrator in case of a dispute.\n\nThere is no payment ID required, just the normal public address.\nIf you are not sure about that process visit (https://www.getmonero.org/resources/user-guides/prove-payment.html) or the Monero forum (https://forum.getmonero.org) to find more information. +account.altcoin.popup.blur.msg=Trading BLUR on Bisq requires that you understand and fulfill the following requirements:\n\nTo send BLUR you must use the Blur Network CLI or GUI Wallet. \n\nIf you are using the CLI wallet, a transaction hash (tx ID) will be displayed after a transfer is sent. You must save this information. Immediately after sending the transfer, you must use the command 'get_tx_key' to retrieve the transaction private key. If you fail to perform this step, you may not be able to retrieve the key later. \n\nIf you are using the Blur Network GUI Wallet, the transaction private key and transaction ID can be found conveniently in the "History" tab. Immediately after sending, locate the transaction of interest. Click the "?" symbol in the lower-right corner of the box containing the transaction. You must save this information. \n\nIn the event that arbitration is necessary, you must present the following to an arbitrator: 1.) the transaction ID, 2.) the transaction private key, and 3.) the recipient's address. The arbitrator will then verify the BLUR transfer using the Blur Transaction Viewer (https://blur.cash/#tx-viewer).\n\nFailure to provide the required information to the arbitrator will result in losing the dispute case. In all cases of dispute, the BLUR sender bears 100% of the burden of responsibility in verifying transactions to an arbitrator. \n\nIf you do not understand these requirements, do not trade on Bisq. First, seek help at the Blur Network Discord (https://discord.gg/dMWaqVW). +account.altcoin.popup.ccx.msg=Trading CCX on Bisq requires that you understand the following requirements:\n\nTo send CCX you must use an official Conceal wallet, either CLI or GUI. After sending a transfer payment, the wallets\ndisplay the transaction secret key. You must save it along with the transaction hash (ID) and the recipient's public\naddress in case arbitration is necessary. In such a case, you must give all three to the arbitrator, who will then\nverify the CCX transfer using the Conceal Transaction Viewer (https://explorer.conceal.network/txviewer).\nBecause Conceal is a privacy coin, block explorers cannot verify transfers.\n\nFailure to provide the required data to the arbitrator will result in losing the dispute case.\nIf you do not save the transaction secret key immediately after transferring CCX, it cannot be recovered later.\nIf you do not understand these requirements, seek help at the Conceal discord (http://discord.conceal.network). +account.altcoin.popup.drgl.msg=Trading Dragonglass on Bisq requires that you understand and fulfill the following requirements:\n\nBecause of the privacy Dragonglass provides, a transaction is not verifiable on the public blockchain. If required, you can prove your payment through the use of your TXN-Private-Key.\nThe TXN-Private Key is a one-time key automatically generated for every transaction that can only be accessed from within your DRGL wallet.\nEither by DRGL-wallet GUI (inside transaction details dialog) or by the Dragonglass CLI simplewallet (using command "get_tx_key").\n\nDRGL version 'Oathkeeper' and higher are REQUIRED for both.\n\nIn case of a dispute, you must provide the arbitrator the following data:\n- The TXN-Private key\n- The transaction hash\n- The recipient's public address\n\nVerification of payment can be made using the above data as inputs at (http://drgl.info/#check_txn).\n\nFailure to provide the above data, or if you used an incompatible wallet, will result in losing the dispute case. The Dragonglass sender is responsible for providing verification of the DRGL transfer to the arbitrator in case of a dispute. Use of PaymentID is not required.\n\nIf you are unsure about any part of this process, visit Dragonglass on Discord (http://discord.drgl.info) for help. account.altcoin.popup.ZEC.msg=当使用{0}时，您只能使用透明地址(以t开头)而不是z开头地址(私有)，因为仲裁者无法使用z地址验证事务。 account.altcoin.popup.XZC.msg=When using {0} you can only use the transparent (traceable) addresses not the untraceable addresses, because the arbitrator would not be able to verify the transaction with untraceable addresses at a block explorer. account.altcoin.popup.bch=Bitcoin Cash and Bitcoin Clashic suffer from replay protection. If you use those coins be sure you take sufficient precautions and understand all implications.You can suffer losses by sending one coin and unintentionally send the same coins on the other block chain.Because those "airdrop coins" share the same history with the Bitcoin blockchain there are also security risks and a considerable risk for losing privacy.\n\nPlease read at the Bisq Forum more about that topic: https://forum.bisq.io/t/airdrop-coins-information-thread-bch-btg-bchc @@ -1306,7 +1308,7 @@ dao.burnBsq.assets.lookBackPeriod=Verification period dao.burnBsq.assets.trialFee=Fee for trial period dao.burnBsq.assets.totalFee=Total fees paid dao.burnBsq.assets.days={0} days -dao.burnBsq.assets.toFewDays=The asset fee is too low. The min. amount of days for the trial perios is {0}. +dao.burnBsq.assets.toFewDays=The asset fee is too low. The min. amount of days for the trial period is {0}. # suppress inspection "UnusedProperty" dao.assetState.UNDEFINED=Undefined @@ -1584,7 +1586,7 @@ displayUpdateDownloadWindow.verify.failed=验证失败。\n请到 https://bisq.i displayUpdateDownloadWindow.success=新版本成功下载并验证签名(s) 。\n\n请打开下载目录,关闭应用程序并安装最新版本。 displayUpdateDownloadWindow.download.openDir=打开下载目录 -dispute概要Window.title=概要 +disputeSummaryWindow.title=概要 disputeSummaryWindow.openDate=Ticket opening date disputeSummaryWindow.role=Trader's role disputeSummaryWindow.evidence=Evidence @@ -1746,7 +1748,7 @@ popup.headline.error=错误 popup.doNotShowAgain=不要再显示 popup.reportError.log=打开日志文件 popup.reportError.gitHub=报告至Github issue tracker -popup.reportError={0}\n\nTo help us to improve the software please report the bug on our issue tracker on GitHub (https://github.com/bisq-network/bisq-desktop/issues).\nThe error message will be copied to the clipboard when you click a button below.\nIt will make debugging easier if you can attach the bisq.log file as well. +popup.reportError={0}\n\nTo help us to improve the software please report this bug by opening a new issue at https://github.com/bisq-network/bisq/issues.\nThe above error message will be copied to the clipboard when you click either of the buttons below.\nIt will make debugging easier if you include the bisq.log file by pressing "Open log file", saving a copy, and attaching it to your bug report. popup.error.tryRestart=请尝试重启您的应用程序或者检查您的网络连接。 popup.error.takeOfferRequestFailed=An error occurred when someone tried to take one of your offers:\n{0} @@ -1805,6 +1807,9 @@ popup.attention.forTradeWithId=交易ID {0}需要注意 popup.roundedFiatValues.headline=New privacy feature: Rounded fiat values popup.roundedFiatValues.msg=To increase privacy of your trade the {0} amount was rounded.\n\nDepending on the client version you''ll pay or receive either values with decimals or rounded ones.\n\nBoth values do comply from now on with the trade protocol.\n\nAlso be aware that BTC values are changed automatically to match the rounded fiat amount as close as possible. +popup.info.multiplePaymentAccounts.headline=Multiple payment accounts available +popup.info.multiplePaymentAccounts.msg=You have multiple payment accounts available for this offer. Please make sure you've picked the right one. + #################################################################### # Notifications @@ -2085,7 +2090,7 @@ payment.clearXchange.info=Please be sure that you fulfill the requirements for t payment.moneyGram.info=When using MoneyGram the BTC buyer has to send the Authorisation number and a photo of the receipt by email to the BTC seller. The receipt must clearly show the seller's full name, country, state and the amount. The buyer will get displayed the seller's email in the trade process. payment.westernUnion.info=When using Western Union the BTC buyer has to send the MTCN (tracking number) and a photo of the receipt by email to the BTC seller. The receipt must clearly show the seller's full name, city, country and the amount. The buyer will get displayed the seller's email in the trade process. -payment.halCash.info=When using HalCash the BTC buyer need to send the BTC seller the HalCash code via a text message from the mobile phone.\n\nPlease make sure to not exceed the maximum amount your bank allows you to send with HalCash. The min. amount per withdrawal is 10 EUR and the max. amount is 600 EUR. For repeated withdrawals it is 3000 EUR per receiver per day and 6000 EUR per receiver per month. Please cross check those limits with your bank to be sure they use the same limits as stated here.\n\nThe withdrawal amount must be a multiple of 10 EUR as you cannot withdraw other amounts from an ATM. The UI in the create-offer and take-offer screen will adjust the BTC amount so that the EUR amount is correct. You cannot use market based price as the EUR amount would be changing with changing prices.\n\nIn case of a dispute the BTC buyer need to provide the proof that he sent the EUR. +payment.halCash.info=When using HalCash the BTC buyer needs to send the BTC seller the HalCash code via a text message from their mobile phone.\n\nPlease make sure to not exceed the maximum amount your bank allows you to send with HalCash. The min. amount per withdrawal is 10 EUR and the max. amount is 600 EUR. For repeated withdrawals it is 3000 EUR per receiver per day and 6000 EUR per receiver per month. Please cross check those limits with your bank to be sure they use the same limits as stated here.\n\nThe withdrawal amount must be a multiple of 10 EUR as you cannot withdraw other amounts from an ATM. The UI in the create-offer and take-offer screen will adjust the BTC amount so that the EUR amount is correct. You cannot use market based price as the EUR amount would be changing with changing prices.\n\nIn case of a dispute the BTC buyer needs to provide the proof that they sent the EUR. payment.limits.info=Please be aware that all bank transfers carry a certain amount of chargeback risk.\n\nTo mitigate this risk, Bisq sets per-trade limits based on two factors:\n\n1. The estimated level of chargeback risk for the payment method used\n2. The age of your account for that payment method\n\nThe account you are creating now is new and its age is zero. As your account grows in age over a two-month period, your per-trade limits will grow along with it:\n\n● During the 1st month, your per-trade limit will be {0}\n● During the 2nd month, your per-trade limit will be {1}\n● After the 2nd month, your per-trade limit will be {2}\n\nPlease note that there are no limits on the total number of times you can trade. payment.cashDeposit.info=Please confirm your bank allows you to send cash deposits into other peoples' accounts. For example, Bank of America and Wells Fargo no longer allow such deposits. @@ -2098,7 +2103,7 @@ payment.f2f.optionalExtra=Optional additional information payment.f2f.extra=Additional information payment.f2f.extra.prompt=The maker can define 'terms and conditions' or add a public contact information. It will be displayed with the offer. -payment.f2f.info='Face to Face' trades have different rules and come with different risks than online transactions.\n\nThe main differences are:\n● The trading peers need to exchange information about the meeting location and time by using their provided contact details.\n● The trading peers need to bring their laptops and do the confirmation of 'payment sent' and 'payment received' at the meeting place.\n● If a maker has special 'terms and conditions' he needs to state those in the 'Addition information' text field in the account.\n● By taking an offer the taker agrees to the maker's stated 'terms and conditions'.\n● In case of a dispute the arbitrator cannot help much as it is usually hard to get tamper proof evidence of what happened at the meeting. In such cases the BTC funds might get locked indefinitely or until the trading peers come to an agreement.\n\nTo be sure you fully understand the differences with 'Face to Face' trades please read the instructions and recommendations at: 'https://docs.bisq.network/trading-rules.html#f2f-trading' +payment.f2f.info='Face to Face' trades have different rules and come with different risks than online transactions.\n\nThe main differences are:\n● The trading peers need to exchange information about the meeting location and time by using their provided contact details.\n● The trading peers need to bring their laptops and do the confirmation of 'payment sent' and 'payment received' at the meeting place.\n● If a maker has special 'terms and conditions' they must state those in the 'Additional information' text field in the account.\n● By taking an offer the taker agrees to the maker's stated 'terms and conditions'.\n● In case of a dispute the arbitrator cannot help much as it is usually hard to get tamper proof evidence of what happened at the meeting. In such cases the BTC funds might get locked indefinitely or until the trading peers come to an agreement.\n\nTo be sure you fully understand the differences with 'Face to Face' trades please read the instructions and recommendations at: 'https://docs.bisq.network/trading-rules.html#f2f-trading' payment.f2f.info.openURL=Open web page payment.f2f.offerbook.tooltip.countryAndCity=County and city: {0} / {1} payment.f2f.offerbook.tooltip.extra=Additional information: {0}