Update translations for v1.9.11

This commit is contained in:
Alejandro García 2023-06-22 14:36:52 +03:00
parent 31b427c92e
commit 694ac651a7
No known key found for this signature in database
GPG Key ID: F806F422E222AA02
15 changed files with 409 additions and 19 deletions

View File

@ -27,8 +27,8 @@ shared.readMore=Přečíst více
shared.openHelp=Otevřít nápovědu
shared.warning=Varování
shared.close=Zavřít
shared.closeAnywayDanger=Shut down anyway
shared.okWait=Keep Bisq Open
shared.closeAnywayDanger=Stejně vypnout
shared.okWait=Nechat Bisq otevřený
shared.cancel=Zrušit
shared.ok=OK
shared.yes=Ano
@ -289,7 +289,7 @@ mainView.networkWarning.allConnectionsLost=Ztratili jste připojení ke všem {0
mainView.networkWarning.localhostBitcoinLost=Ztratili jste připojení k Bitcoinovému localhost nodu.\nRestartujte aplikaci Bisq a připojte se k jiným Bitcoinovým nodům nebo restartujte Bitcoinový localhost node.
mainView.networkWarning.clockWatcher=Váš počítač byl uspán {0} sekund. Režim spánku může způsobovat selhání obchodů. Aby Bisq fungoval správně, je potřeba v nastavení počítače deaktivovat automatické přecházení do režimu spánku.
mainView.version.update=(Dostupná aktualizace)
mainView.status.connections=Inbound connections: {0}\nOutbound connections: {1}
mainView.status.connections=Příchozí spojení: {0}\nOdchozí spojení: {1}
####################################################################
# MarketView
@ -362,6 +362,13 @@ offerbook.timeSinceSigning.tooltip.checkmark.wait=počkat alespoň {0} dní
offerbook.timeSinceSigning.tooltip.learnMore=Zjistit více
offerbook.xmrAutoConf=Je automatické potvrzení povoleno
offerbook.cloneOffer=Clone offer (with shared maker fee)
offerbook.clonedOffer.tooltip=This is a cloned offer with shared maker fee transaction ID.\n\Maker fee transaction ID: {0}
offerbook.nonClonedOffer.tooltip=Regular offer without shared maker fee transaction ID.\n\Maker fee transaction ID: {0}
offerbook.cannotActivate.warning=This cloned offer with shared maker fee cannot be activated because it uses the same payment method and currency as another active offer.\n\nYou need to edit the offer and change the payment method or currency or deactivate the offer which has the same payment method and currency.
offerbook.cannotActivateEditedOffer.warning=You can't activate an offer that is currently edited.
offerbook.clonedOffer.info=By cloning an offer one creates a copy of the given offer with a new offer ID but using the same maker fee transaction ID.\n\nThis means there is no extra maker fee needed to get paid and the funds reserved for that offer can be re-used by the cloned offers. This reduces the liquidity requirements for market makers and allows them to post the same offer in different markets or with different payment methods.\n\nAs a consequence if one of the offers sharing the same maker fee transaction is taken all the other offers will get closed as well because the transaction output of that maker fee transaction is spent and would render the other offers invalid. \n\nThis feature requires to use the same trade amount and security deposit and is only permitted for offers with different payment methods or currencies.\n\nFor more information about cloning an offer see: [HYPERLINK:https://bisq.wiki/Cloning_an_offer]
offerbook.timeSinceSigning.help=Když úspěšně dokončíte obchod s uživatelem, který má podepsaný platební účet, je váš platební účet podepsán.\n{0} dní později se počáteční limit {1} zruší a váš účet může podepisovat platební účty ostatních uživatelů.
offerbook.timeSinceSigning.notSigned=Dosud nepodepsáno
offerbook.timeSinceSigning.notSigned.ageDays={0} dní
@ -565,6 +572,7 @@ takeOffer.tac=Přijetím této nabídky souhlasím s obchodními podmínkami def
####################################################################
openOffer.header.triggerPrice=Limitní cena
openOffer.header.makerFeeTxId=Maker fee
openOffer.triggerPrice=Limitní cena {0}
openOffer.triggered=Nabídka byla deaktivována, protože tržní cena dosáhla vámi stanovené limitní ceny.\nProsím nastavte novou limitní cenu ve vaší nabídce
@ -576,7 +584,14 @@ editOffer.publishOffer=Publikování vaší nabídky.
editOffer.failed=Úprava nabídky se nezdařila:\n{0}
editOffer.success=Vaše nabídka byla úspěšně upravena.
editOffer.invalidDeposit=Kauce kupujícího není v rámci omezení definovaných Bisq DAO a nemůže být dále upravována.
editOffer.openTabWarning=You have already the \"Edit Offer\" tab open.
editOffer.cannotActivateOffer=You have edited an offer which uses a shared maker fee with another offer and your edit made the payment method and currency now the same as that of another active cloned offer. Your edited offer will be deactivated because it is not permitted to publish 2 offers sharing the same maker fee with the same payment method and currency.\n\nYou can edit the offer again at \"Portfolio/My open offers\" to fulfill the requirements to activate it.
cloneOffer.clone=Clone offer
cloneOffer.publishOffer=Publishing cloned offer.
cloneOffer.success=Your offer has been successfully cloned.
cloneOffer.cannotActivateOffer=You have not changed the payment method or the currency. You still can clone the offer, but it will be deactivated and not published.\n\nYou can edit the offer later again at \"Portfolio/My open offers\" to fulfill the requirements to activate it.\n\nDo you still want to clone the offer?
cloneOffer.openTabWarning=You have already the \"Clone Offer\" tab open.
####################################################################
# BSQ Swap offer
@ -604,7 +619,7 @@ portfolio.tab.bsqSwap=Nepotvrzené BSQ swapy
portfolio.tab.failed=Selhalo
portfolio.tab.editOpenOffer=Upravit nabídku
portfolio.tab.duplicateOffer=Duplikovat nabídku
portfolio.context.offerLikeThis=Vytvořit novou nabídku jako tato...
portfolio.tab.cloneOpenOffer=Clone offer
portfolio.context.notYourOffer=Můžete duplikovat pouze vámi vytvořené nabídky.
portfolio.closedTrades.deviation.help=Procentuální odchylka od tržní ceny
@ -1069,6 +1084,8 @@ support.warning.disputesWithInvalidDonationAddress=Odložená výplatní transak
support.warning.disputesWithInvalidDonationAddress.mediator=\n\nStále chcete spor uzavřít?
support.warning.disputesWithInvalidDonationAddress.refundAgent=\n\nVýplatu nesmíte provést.
support.warning.traderCloseOwnDisputeWarning=Obchodníci mohou sami zrušit úkol pro podporu pouze pokud došlo k výplatě prostředků.
support.warning.ticketNotAcknowledged=Ticket not acknowledged.
support.resendTicket=This trader has not acknowledged receipt of the dispute ticket.\nWould you like to re-send the ticket?
support.info.disputedTradeUpdate=Disputed trade update: {0}
####################################################################
@ -1131,6 +1148,7 @@ setting.preferences.dao.resyncFromResources.popup=Po restartu aplikace budou dat
setting.preferences.dao.resyncFromGenesis.popup=Resynchronizace z genesis transakce může stát značné množství času a prostředků CPU. Opravdu to chcete udělat? Většinou je resynchronizace z nejnovějších zdrojových souborů dostatečná a mnohem rychlejší.\n\nPokud budete pokračovat, po restartu aplikace budou data správy sítě Bisq znovu načtena z počátečních uzlů a stav konsensu BSQ bude znovu vytvořen z genesis transakce.
setting.preferences.dao.resyncFromGenesis.resync=Resynchronizovat z genesis transakce a vypnout
setting.preferences.dao.isDaoFullNode=Spusťte Bisq jako full node DAO
setting.preferences.dao.processBurningManAccountingData=Process Burningman accounting data
setting.preferences.dao.fullModeDaoMonitor=Monitorování stavu DAO v plném režimu
setting.preferences.dao.fullModeDaoMonitor.popup=Pokud je aktivováno monitorování stavu DAO v plném režimu, vytvářejí se během parsování bloků BSQ hashe stavu DAO. To s sebou nese značné výkonnostní náklady při počáteční synchronizaci DAO.\n\nPro uživatele, kteří Bisq používají pravidelně, by to neměl být problém, protože na parsování nečeká mnoho bloků, avšak pro uživatele, kteří Bisq používají pouze příležitostně, vytváření hashů stavu DAO pro 100 nebo 1000 bloků silně zhoršuje uživatelský zážitek.\n\nV případě, že je deaktivován plný režim (výchozí nastavení), jsou chybějící hashe stavu DAO vyžádány od uzlů sítě a hash stavu DAO založený na nejnovějším bloku vytvoří uživatel. Jelikož jsou všechny hashe propojeny odkazem na předchozí hash, správný hash na špičce řetězce znamená, že všechny předchozí hashe jsou také správné. Hlavní funkce sledování stavu DAO - zjistit, zda není lokální stav DAO nesynchronizován se zbytkem sítě - je tedy stále splněna.
@ -1784,8 +1802,14 @@ dao.burningman.contributorsComboBox.prompt=Select any of my contributors
dao.burningman.daoBalance=Balance for DAO
dao.burningman.daoBalanceTotalBurned=Total amount of burned BSQ
dao.burningman.daoBalanceTotalDistributed=Total amount of distributed BTC / BSQ
dao.burningman.daoBalanceTotalBtcFees=Total amount of BTC fees in BTC / BSQ
dao.burningman.daoBalanceTotalDPT=Total amount of delayed payout transactions BTC / BSQ
dao.burningman.selectedContributor=Selected contributor
dao.burningman.selectedContributor.disabledAccounting=(accounting data not updated)
dao.burningman.selectedContributor.processing=(still processing data...)
dao.burningman.selectedContributorName=Contributor name
dao.burningman.selectedContributorTotalReceived=Total received
dao.burningman.selectedContributorTotalRevenue=Total revenue
dao.burningman.selectedContributorAddress=Receiver address
dao.burningman.shared.table.height=Výška bloku
dao.burningman.shared.table.cycle=Cyklus
@ -1812,6 +1836,8 @@ dao.burningman.table.balanceEntry.revenue=Revenue
dao.burningman.table.balanceEntry.price=kurz BSQ/BTC
dao.burningman.table.balanceEntry.type=Typ
dao.burningman.accounting.popup=To display accounting data of a burningman you need to enable the 'process burningman accounting data' option in settings.\nDo you want to do that now?\nIt will require to restart Bisq to apply that change.\n\nIf you cancel, the displayed accounting data are not up-to-date.
# From BalanceEntry.Type enum names
dao.burningman.balanceEntry.type.UNDEFINED=Nedefinováno
dao.burningman.balanceEntry.type.BTC_TRADE_FEE_TX=Obchodní poplatek

View File

@ -362,6 +362,13 @@ offerbook.timeSinceSigning.tooltip.checkmark.wait=Warte mindestens {0} Tage
offerbook.timeSinceSigning.tooltip.learnMore=Mehr erfahren
offerbook.xmrAutoConf=Automatische Bestätigung aktiviert
offerbook.cloneOffer=Clone offer (with shared maker fee)
offerbook.clonedOffer.tooltip=This is a cloned offer with shared maker fee transaction ID.\n\Maker fee transaction ID: {0}
offerbook.nonClonedOffer.tooltip=Regular offer without shared maker fee transaction ID.\n\Maker fee transaction ID: {0}
offerbook.cannotActivate.warning=This cloned offer with shared maker fee cannot be activated because it uses the same payment method and currency as another active offer.\n\nYou need to edit the offer and change the payment method or currency or deactivate the offer which has the same payment method and currency.
offerbook.cannotActivateEditedOffer.warning=You can't activate an offer that is currently edited.
offerbook.clonedOffer.info=By cloning an offer one creates a copy of the given offer with a new offer ID but using the same maker fee transaction ID.\n\nThis means there is no extra maker fee needed to get paid and the funds reserved for that offer can be re-used by the cloned offers. This reduces the liquidity requirements for market makers and allows them to post the same offer in different markets or with different payment methods.\n\nAs a consequence if one of the offers sharing the same maker fee transaction is taken all the other offers will get closed as well because the transaction output of that maker fee transaction is spent and would render the other offers invalid. \n\nThis feature requires to use the same trade amount and security deposit and is only permitted for offers with different payment methods or currencies.\n\nFor more information about cloning an offer see: [HYPERLINK:https://bisq.wiki/Cloning_an_offer]
offerbook.timeSinceSigning.help=Wenn Sie einen Trade mit einem Partner erfolgreich abschließen, der ein unterzeichnetes Zahlungskonto hat, wird Ihr Zahlungskonto unterzeichnet.\n{0} Tage später wird das anfängliche Limit von {1} aufgehoben und Ihr Konto kann die Zahlungskonten anderer Partner unterzeichnen.
offerbook.timeSinceSigning.notSigned=Noch nicht unterzeichnet
offerbook.timeSinceSigning.notSigned.ageDays={0} Tage
@ -565,6 +572,7 @@ takeOffer.tac=Mit der Annahme dieses Angebots stimme ich den oben festgelegten H
####################################################################
openOffer.header.triggerPrice=Auslösepreis
openOffer.header.makerFeeTxId=Erstellungsgebühr
openOffer.triggerPrice=Auslösepreis {0}
openOffer.triggered=Das Angebot wurde deaktiviert, weil der Marktpreis Ihren Auslösepreis erreicht hat.\nBitte bearbeiten Sie das Angebot, um einen neuen Auslösepreis festzulegen.
@ -576,7 +584,14 @@ editOffer.publishOffer=Ihr Angebot wird veröffentlicht.
editOffer.failed=Bearbeiten des Angebots fehlgeschlagen:\n{0}
editOffer.success=Ihr Angebot wurde erfolgreich bearbeitet.
editOffer.invalidDeposit=Die Kaution des Käufers ist nicht in den, vom Bisq DAO definierten, Beschränkungen und können nicht mehr geändert werden.
editOffer.openTabWarning=You have already the \"Edit Offer\" tab open.
editOffer.cannotActivateOffer=You have edited an offer which uses a shared maker fee with another offer and your edit made the payment method and currency now the same as that of another active cloned offer. Your edited offer will be deactivated because it is not permitted to publish 2 offers sharing the same maker fee with the same payment method and currency.\n\nYou can edit the offer again at \"Portfolio/My open offers\" to fulfill the requirements to activate it.
cloneOffer.clone=Clone offer
cloneOffer.publishOffer=Publishing cloned offer.
cloneOffer.success=Your offer has been successfully cloned.
cloneOffer.cannotActivateOffer=You have not changed the payment method or the currency. You still can clone the offer, but it will be deactivated and not published.\n\nYou can edit the offer later again at \"Portfolio/My open offers\" to fulfill the requirements to activate it.\n\nDo you still want to clone the offer?
cloneOffer.openTabWarning=You have already the \"Clone Offer\" tab open.
####################################################################
# BSQ Swap offer
@ -604,7 +619,7 @@ portfolio.tab.bsqSwap=Unbestätigte BSQ Swaps
portfolio.tab.failed=Fehlgeschlagen
portfolio.tab.editOpenOffer=Angebot bearbeiten
portfolio.tab.duplicateOffer=Angebot kopieren
portfolio.context.offerLikeThis=Erstelle ein gleiches Angebot...
portfolio.tab.cloneOpenOffer=Clone offer
portfolio.context.notYourOffer=Sie können Angebote, die Sie erstellt haben, duplizieren.
portfolio.closedTrades.deviation.help=Prozentuale Preisabweichung vom Markt
@ -1069,6 +1084,8 @@ support.warning.disputesWithInvalidDonationAddress=Die verzögerte Auszahlungstr
support.warning.disputesWithInvalidDonationAddress.mediator=\n\nWollen Sie den Konflikt trotzdem schließen?
support.warning.disputesWithInvalidDonationAddress.refundAgent=\n\nSie müssen nicht auszahlen.
support.warning.traderCloseOwnDisputeWarning=Händler können ihre Support-Tickets nur dann selbst schließen, wenn der Handel ausgezahlt wurde.
support.warning.ticketNotAcknowledged=Ticket not acknowledged.
support.resendTicket=This trader has not acknowledged receipt of the dispute ticket.\nWould you like to re-send the ticket?
support.info.disputedTradeUpdate=Disputed trade update: {0}
####################################################################
@ -1131,6 +1148,7 @@ setting.preferences.dao.resyncFromResources.popup=Nach einem Neustart der Anwend
setting.preferences.dao.resyncFromGenesis.popup=Eine Resync von der Genesis-Transaktion kann erhebliche Zeit und CPU-Ressourcen in Anspruch nehmen. Sind Sie sicher, dass Sie das tun wollen? Meistens ist ein Resync von den neuesten Ressourcendateien ausreichend und viel schneller.\n\nWenn Sie fortfahren, werden nach einem Neustart der Anwendung die Bisq-Netzwerk-Governance-Daten von den Seed-Nodes neu geladen und der BSQ-Konsensstatus wird aus der Genesis-Transaktion neu aufgebaut.
setting.preferences.dao.resyncFromGenesis.resync=Resync von Genesis ausführen und beenden
setting.preferences.dao.isDaoFullNode=Bisq als DAO Full Node betreiben
setting.preferences.dao.processBurningManAccountingData=Process Burningman accounting data
setting.preferences.dao.fullModeDaoMonitor=DAO-Zustandsüberwachung im Vollmodus
setting.preferences.dao.fullModeDaoMonitor.popup=Wenn die Überwachung des Status des DAOs im Vollmodus aktiviert ist, werden die DAO-Hashes beim Parsen der BSQ-Blöcke erstellt. Das geht erheblich auf die Performance bei der ersten DAO-Synchronisierung.\n\nFür Benutzer, die Bisq regelmäßig verwenden, sollte dies kein Problem darstellen, da nicht viele Blöcke zum Parsen anstehen. Für Benutzer, die Bisq nur gelegentlich verwenden, dauert die Erstellung der DAO-Status-Hashes für Hunderte oder Tausende von Blöcken etwas länger.\n\nIst der Vollmodus deaktiviert (Standardeinstellung), werden die fehlenden DAO-Status-Hashes von den Netzwerkknoten angefordert und der DAO-Status-Hash, basierend auf dem aktuellsten Block, vom Benutzer erstellt. Da alle Hashes sich vom vorherigen Hash ableiten, bedeutet ein korrekter Hash an der Spitze der Chain, dass alle vergangenen Hashes ebenfalls korrekt waren. Die Hauptfunktion der DAO-Zustandsüberwachung ist es zu erkennen, ob der lokale DAO-Zustand nicht mehr mit dem Rest des Netzwerks synchron ist.
@ -1784,8 +1802,14 @@ dao.burningman.contributorsComboBox.prompt=Select any of my contributors
dao.burningman.daoBalance=Balance for DAO
dao.burningman.daoBalanceTotalBurned=Total amount of burned BSQ
dao.burningman.daoBalanceTotalDistributed=Total amount of distributed BTC / BSQ
dao.burningman.daoBalanceTotalBtcFees=Total amount of BTC fees in BTC / BSQ
dao.burningman.daoBalanceTotalDPT=Total amount of delayed payout transactions BTC / BSQ
dao.burningman.selectedContributor=Selected contributor
dao.burningman.selectedContributor.disabledAccounting=(accounting data not updated)
dao.burningman.selectedContributor.processing=(still processing data...)
dao.burningman.selectedContributorName=Contributor name
dao.burningman.selectedContributorTotalReceived=Total received
dao.burningman.selectedContributorTotalRevenue=Total revenue
dao.burningman.selectedContributorAddress=Receiver address
dao.burningman.shared.table.height=Blockhöhe
dao.burningman.shared.table.cycle=Zyklus
@ -1812,6 +1836,8 @@ dao.burningman.table.balanceEntry.revenue=Revenue
dao.burningman.table.balanceEntry.price=BSQ/BTC Preis
dao.burningman.table.balanceEntry.type=Typ
dao.burningman.accounting.popup=To display accounting data of a burningman you need to enable the 'process burningman accounting data' option in settings.\nDo you want to do that now?\nIt will require to restart Bisq to apply that change.\n\nIf you cancel, the displayed accounting data are not up-to-date.
# From BalanceEntry.Type enum names
dao.burningman.balanceEntry.type.UNDEFINED=Undefined
dao.burningman.balanceEntry.type.BTC_TRADE_FEE_TX=Trade fee

View File

@ -362,6 +362,13 @@ offerbook.timeSinceSigning.tooltip.checkmark.wait=Espere un mínimo de {0} días
offerbook.timeSinceSigning.tooltip.learnMore=Aprender más
offerbook.xmrAutoConf=¿Está habilitada la confirmación automática?
offerbook.cloneOffer=Clone offer (with shared maker fee)
offerbook.clonedOffer.tooltip=This is a cloned offer with shared maker fee transaction ID.\n\Maker fee transaction ID: {0}
offerbook.nonClonedOffer.tooltip=Regular offer without shared maker fee transaction ID.\n\Maker fee transaction ID: {0}
offerbook.cannotActivate.warning=This cloned offer with shared maker fee cannot be activated because it uses the same payment method and currency as another active offer.\n\nYou need to edit the offer and change the payment method or currency or deactivate the offer which has the same payment method and currency.
offerbook.cannotActivateEditedOffer.warning=You can't activate an offer that is currently edited.
offerbook.clonedOffer.info=By cloning an offer one creates a copy of the given offer with a new offer ID but using the same maker fee transaction ID.\n\nThis means there is no extra maker fee needed to get paid and the funds reserved for that offer can be re-used by the cloned offers. This reduces the liquidity requirements for market makers and allows them to post the same offer in different markets or with different payment methods.\n\nAs a consequence if one of the offers sharing the same maker fee transaction is taken all the other offers will get closed as well because the transaction output of that maker fee transaction is spent and would render the other offers invalid. \n\nThis feature requires to use the same trade amount and security deposit and is only permitted for offers with different payment methods or currencies.\n\nFor more information about cloning an offer see: [HYPERLINK:https://bisq.wiki/Cloning_an_offer]
offerbook.timeSinceSigning.help=Cuando complete con éxito un intercambio con un par que tenga una cuenta de pago firmada, su cuenta de pago es firmada.\n{0} días después, el límite inicial de {1} se eleva y su cuenta puede firmar tras cuentas de pago.
offerbook.timeSinceSigning.notSigned=No firmada aún
offerbook.timeSinceSigning.notSigned.ageDays={0} días
@ -565,6 +572,7 @@ takeOffer.tac=Al tomar esta oferta, afirmo estar de acuerdo con las condiciones
####################################################################
openOffer.header.triggerPrice=Precio de ejecución
openOffer.header.makerFeeTxId=Tasa de creador
openOffer.triggerPrice=Precio de ejecución {0}
openOffer.triggered=La oferta ha sido desactivada porque el precio de mercado alcanzó su precio de disparo.\nPor favor edite la oferta para definir un nuevo precio de disparo.
@ -576,7 +584,14 @@ editOffer.publishOffer=Publicando su oferta.
editOffer.failed=Fallo en la edición de oferta:\n{0}
editOffer.success=Su oferta ha sido editada con éxito.
editOffer.invalidDeposit=El depósito de seguridad del comprador no está dentro de los límites definidos por la DAO Bisq y ya no puede ser ser editado.
editOffer.openTabWarning=You have already the \"Edit Offer\" tab open.
editOffer.cannotActivateOffer=You have edited an offer which uses a shared maker fee with another offer and your edit made the payment method and currency now the same as that of another active cloned offer. Your edited offer will be deactivated because it is not permitted to publish 2 offers sharing the same maker fee with the same payment method and currency.\n\nYou can edit the offer again at \"Portfolio/My open offers\" to fulfill the requirements to activate it.
cloneOffer.clone=Clone offer
cloneOffer.publishOffer=Publishing cloned offer.
cloneOffer.success=Your offer has been successfully cloned.
cloneOffer.cannotActivateOffer=You have not changed the payment method or the currency. You still can clone the offer, but it will be deactivated and not published.\n\nYou can edit the offer later again at \"Portfolio/My open offers\" to fulfill the requirements to activate it.\n\nDo you still want to clone the offer?
cloneOffer.openTabWarning=You have already the \"Clone Offer\" tab open.
####################################################################
# BSQ Swap offer
@ -604,7 +619,7 @@ portfolio.tab.bsqSwap=Swaps BSQ no confirmados
portfolio.tab.failed=Fallidas
portfolio.tab.editOpenOffer=Editar oferta
portfolio.tab.duplicateOffer=Duplicar oferta
portfolio.context.offerLikeThis=Crear nueva oferta como esta...
portfolio.tab.cloneOpenOffer=Clone offer
portfolio.context.notYourOffer=Solo puede duplicar las ofertas en que fue el creador.
portfolio.closedTrades.deviation.help=Desviación porcentual de precio de mercado
@ -1069,6 +1084,8 @@ support.warning.disputesWithInvalidDonationAddress=La transacción de pago demor
support.warning.disputesWithInvalidDonationAddress.mediator=\n\n¿Aún quiere cerrar la disputa?
support.warning.disputesWithInvalidDonationAddress.refundAgent=\n\nUsted no debería realizar el pago.
support.warning.traderCloseOwnDisputeWarning=Los comerciantes puden cerrar por sí mismos sus tickets de soporte cuando el intercambio se haya pagado.
support.warning.ticketNotAcknowledged=Ticket not acknowledged.
support.resendTicket=This trader has not acknowledged receipt of the dispute ticket.\nWould you like to re-send the ticket?
support.info.disputedTradeUpdate=Disputed trade update: {0}
####################################################################
@ -1131,6 +1148,7 @@ setting.preferences.dao.resyncFromResources.popup=Después de un reinicio de la
setting.preferences.dao.resyncFromGenesis.popup=Una resincronización desde la transacción génesis puede llevar mucho tiempo y recursos de CPU. ¿Está seguro de que quiere hacer eso? Generalmente una resincronización de los últimos archivos de recursos es suficiente y mucho más rápida\n\nSi continúa, después de reiniciar la aplicación, los datos de gobernanza de la red Bisq se volverán a cargar desde los nodos semilla y el estado de consenso BSQ se reconstruirá a partir de la transacción génesis.
setting.preferences.dao.resyncFromGenesis.resync=Resincronizar desde la transacción génesis y cerrar la aplicación
setting.preferences.dao.isDaoFullNode=Ejecutar Bisq como nodo completo de la DAO
setting.preferences.dao.processBurningManAccountingData=Process Burningman accounting data
setting.preferences.dao.fullModeDaoMonitor=Estado de monitorización de DAO en modo completo
setting.preferences.dao.fullModeDaoMonitor.popup=Si el estado de monitorización DAO en modo completo se activa los hashes del estado de DAO se crean durante el parsing de los bloques BSQ. Esto tiene considerables costes de rendimiento en al inicio de la sincronización DAO.\n\nPara usuarios que regularmente usen Bisq esto no debería ser un problema porque no hay muchos bloques para hacer parsing, aunque para usuarios que solo usen Bisq de vez en cuando crear los hashes del estado de DAO para cientos o miles de bloques degrada mucho la experiencia de usuario.\n\nEn caso de que se desactive el modo completo (por defecto) los hashes de estado de DAO son requeridos de los nodos de red y los hash del estado de DAO basados en el bloque más reciente serán creados por el usuario. Como todos los hashes están conectados en referencia a el hash previo, un hash correcto al final de la cadena significa que todos los hashes pasados también son correctos. La principal funcionalidad de la monitorización del estado de la DAO (detectar si el estado local de la DAO está desincronizado con el resto de la red) por tanto se aún se cumple.
@ -1784,8 +1802,14 @@ dao.burningman.contributorsComboBox.prompt=Select any of my contributors
dao.burningman.daoBalance=Balance for DAO
dao.burningman.daoBalanceTotalBurned=Total amount of burned BSQ
dao.burningman.daoBalanceTotalDistributed=Total amount of distributed BTC / BSQ
dao.burningman.daoBalanceTotalBtcFees=Total amount of BTC fees in BTC / BSQ
dao.burningman.daoBalanceTotalDPT=Total amount of delayed payout transactions BTC / BSQ
dao.burningman.selectedContributor=Selected contributor
dao.burningman.selectedContributor.disabledAccounting=(accounting data not updated)
dao.burningman.selectedContributor.processing=(still processing data...)
dao.burningman.selectedContributorName=Contributor name
dao.burningman.selectedContributorTotalReceived=Total received
dao.burningman.selectedContributorTotalRevenue=Total revenue
dao.burningman.selectedContributorAddress=Receiver address
dao.burningman.shared.table.height=Altura de bloque
dao.burningman.shared.table.cycle=Ciclo
@ -1812,6 +1836,8 @@ dao.burningman.table.balanceEntry.revenue=Revenue
dao.burningman.table.balanceEntry.price=precio BSQ/BTC
dao.burningman.table.balanceEntry.type=Tipo
dao.burningman.accounting.popup=To display accounting data of a burningman you need to enable the 'process burningman accounting data' option in settings.\nDo you want to do that now?\nIt will require to restart Bisq to apply that change.\n\nIf you cancel, the displayed accounting data are not up-to-date.
# From BalanceEntry.Type enum names
dao.burningman.balanceEntry.type.UNDEFINED=Indefinido
dao.burningman.balanceEntry.type.BTC_TRADE_FEE_TX=Comisión de transacción
@ -2588,7 +2614,7 @@ popup.privateNotification.headline=Notificación privada importante!
popup.securityRecommendation.headline=Recomendación de seguridad importante
popup.securityRecommendation.msg=Nos gustaría recordarle que considere usar protección por contraseña para su cartera, si no la ha activado ya.\n\nTambién es muy recomendable que escriba en un papel las palabras semilla del monedero. Esas palabras semilla son como una contraseña maestra para recuperar su cartera Bitcoin.\nEn la sección \"Semilla de cartera\" encontrará más información.\n\nAdicionalmente, debería hacer una copia de seguridad completa del directorio de aplicación en la sección \"Copia de seguridad\"
popup.bitcoinLocalhostNode.msg=Bisq ha detectado un nodo de Bitcoin Core ejecutándose en esta máquina (en local).\n\nPor favor, asegúrese de:\n- que el nodo está completamente sincronizado al iniciar Bisq\n- que el podado está desabilitado ('prune=0' en bitcoin.conf)\n- que los filtros bloom están deshabilitados ('peerbloomfilters=1' in bitcoin.conf)
popup.bitcoinLocalhostNode.msg=Bisq ha detectado un nodo de Bitcoin Core ejecutándose en esta máquina (en local).\n\nPor favor, asegúrese de:\n- que el nodo está completamente sincronizado al iniciar Bisq\n- que el podado está desabilitado ('prune=0' en bitcoin.conf)\n- que los filtros bloom están habilitados ('peerbloomfilters=1' en bitcoin.conf)
popup.shutDownInProgress.headline=Cerrando aplicación...
popup.shutDownInProgress.msg=Cerrar la aplicación puede llevar unos segundos.\nPor favor no interrumpa el proceso.

View File

@ -362,6 +362,13 @@ offerbook.timeSinceSigning.tooltip.checkmark.wait=wait a minimum of {0} days
offerbook.timeSinceSigning.tooltip.learnMore=بیشتر بدانید
offerbook.xmrAutoConf=Is auto-confirm enabled
offerbook.cloneOffer=Clone offer (with shared maker fee)
offerbook.clonedOffer.tooltip=This is a cloned offer with shared maker fee transaction ID.\n\Maker fee transaction ID: {0}
offerbook.nonClonedOffer.tooltip=Regular offer without shared maker fee transaction ID.\n\Maker fee transaction ID: {0}
offerbook.cannotActivate.warning=This cloned offer with shared maker fee cannot be activated because it uses the same payment method and currency as another active offer.\n\nYou need to edit the offer and change the payment method or currency or deactivate the offer which has the same payment method and currency.
offerbook.cannotActivateEditedOffer.warning=You can't activate an offer that is currently edited.
offerbook.clonedOffer.info=By cloning an offer one creates a copy of the given offer with a new offer ID but using the same maker fee transaction ID.\n\nThis means there is no extra maker fee needed to get paid and the funds reserved for that offer can be re-used by the cloned offers. This reduces the liquidity requirements for market makers and allows them to post the same offer in different markets or with different payment methods.\n\nAs a consequence if one of the offers sharing the same maker fee transaction is taken all the other offers will get closed as well because the transaction output of that maker fee transaction is spent and would render the other offers invalid. \n\nThis feature requires to use the same trade amount and security deposit and is only permitted for offers with different payment methods or currencies.\n\nFor more information about cloning an offer see: [HYPERLINK:https://bisq.wiki/Cloning_an_offer]
offerbook.timeSinceSigning.help=When you successfully complete a trade with a peer who has a signed payment account, your payment account is signed.\n{0} days later, the initial limit of {1} is lifted and your account can sign other peers'' payment accounts.
offerbook.timeSinceSigning.notSigned=Not signed yet
offerbook.timeSinceSigning.notSigned.ageDays={0} روز
@ -565,6 +572,7 @@ takeOffer.tac=با پذیرفتن این پیشنهاد، من قبول می‌
####################################################################
openOffer.header.triggerPrice=قیمت نشان‌شده
openOffer.header.makerFeeTxId=Maker fee
openOffer.triggerPrice=Trigger price {0}
openOffer.triggered=The offer has been deactivated because the market price reached your trigger price.\nPlease edit the offer to define a new trigger price
@ -576,7 +584,14 @@ editOffer.publishOffer=انتشار پیشنهاد شما.
editOffer.failed=ویرایش پیشنهاد، ناموفق بود:\n{0}
editOffer.success=پیشنهاد شما با موفقیت ویرایش شد.
editOffer.invalidDeposit=The buyer's security deposit is not within the constraints defined by the Bisq DAO and can no longer be edited.
editOffer.openTabWarning=You have already the \"Edit Offer\" tab open.
editOffer.cannotActivateOffer=You have edited an offer which uses a shared maker fee with another offer and your edit made the payment method and currency now the same as that of another active cloned offer. Your edited offer will be deactivated because it is not permitted to publish 2 offers sharing the same maker fee with the same payment method and currency.\n\nYou can edit the offer again at \"Portfolio/My open offers\" to fulfill the requirements to activate it.
cloneOffer.clone=Clone offer
cloneOffer.publishOffer=Publishing cloned offer.
cloneOffer.success=Your offer has been successfully cloned.
cloneOffer.cannotActivateOffer=You have not changed the payment method or the currency. You still can clone the offer, but it will be deactivated and not published.\n\nYou can edit the offer later again at \"Portfolio/My open offers\" to fulfill the requirements to activate it.\n\nDo you still want to clone the offer?
cloneOffer.openTabWarning=You have already the \"Clone Offer\" tab open.
####################################################################
# BSQ Swap offer
@ -604,7 +619,7 @@ portfolio.tab.bsqSwap=Unconfirmed BSQ swaps
portfolio.tab.failed=ناموفق
portfolio.tab.editOpenOffer=ویرایش پیشنهاد
portfolio.tab.duplicateOffer=Duplicate offer
portfolio.context.offerLikeThis=Create new offer like this...
portfolio.tab.cloneOpenOffer=Clone offer
portfolio.context.notYourOffer=You can only duplicate offers where you were the maker.
portfolio.closedTrades.deviation.help=Percentage price deviation from market
@ -1069,6 +1084,8 @@ support.warning.disputesWithInvalidDonationAddress=The delayed payout transactio
support.warning.disputesWithInvalidDonationAddress.mediator=\n\nDo you still want to close the dispute?
support.warning.disputesWithInvalidDonationAddress.refundAgent=\n\nYou must not do the payout.
support.warning.traderCloseOwnDisputeWarning=Traders can only self-close their support tickets when the trade has been paid out.
support.warning.ticketNotAcknowledged=Ticket not acknowledged.
support.resendTicket=This trader has not acknowledged receipt of the dispute ticket.\nWould you like to re-send the ticket?
support.info.disputedTradeUpdate=Disputed trade update: {0}
####################################################################
@ -1131,6 +1148,7 @@ setting.preferences.dao.resyncFromResources.popup=After an application restart t
setting.preferences.dao.resyncFromGenesis.popup=A resync from genesis transaction can take considerable time and CPU resources. Are you sure you want to do that? Mostly a resync from latest resource files is sufficient and much faster.\n\nIf you proceed, after an application restart the Bisq network governance data will be reloaded from the seed nodes and the BSQ consensus state will be rebuilt from the genesis transaction.
setting.preferences.dao.resyncFromGenesis.resync=Resync from genesis and shutdown
setting.preferences.dao.isDaoFullNode=Bisq را به عنوان یک گره کامل DAO اجرا کن
setting.preferences.dao.processBurningManAccountingData=Process Burningman accounting data
setting.preferences.dao.fullModeDaoMonitor=Full-mode DAO state monitoring
setting.preferences.dao.fullModeDaoMonitor.popup=If full-mode DAO state monitoring is activated the DAO state hashes are created during parsing the BSQ blocks. This comes with considerable performance costs at the initial DAO sync.\n\nFor users who are regularily using Bisq this should not be an issue as there are not many blocks pending for parsing, though for users who only use Bisq casually creating the DAO state hashes for 100s or 1000s of blocks degrades heavily the user experience.\n\nIn case full-mode is deactivated (default) the missing DAO state hashes are requested from network nodes and the DAO state hash based on the most recent block will be created by the user. As all hashes are connected by reference to the previous hash a correct hash at the chain tip means that all past hashes are correct as well. The main functionality of the DAO state monitoring - to detect if the local DAO state is out of sync with the rest of the network - is therefore still fulfilled.
@ -1784,8 +1802,14 @@ dao.burningman.contributorsComboBox.prompt=Select any of my contributors
dao.burningman.daoBalance=Balance for DAO
dao.burningman.daoBalanceTotalBurned=Total amount of burned BSQ
dao.burningman.daoBalanceTotalDistributed=Total amount of distributed BTC / BSQ
dao.burningman.daoBalanceTotalBtcFees=Total amount of BTC fees in BTC / BSQ
dao.burningman.daoBalanceTotalDPT=Total amount of delayed payout transactions BTC / BSQ
dao.burningman.selectedContributor=Selected contributor
dao.burningman.selectedContributor.disabledAccounting=(accounting data not updated)
dao.burningman.selectedContributor.processing=(still processing data...)
dao.burningman.selectedContributorName=Contributor name
dao.burningman.selectedContributorTotalReceived=Total received
dao.burningman.selectedContributorTotalRevenue=Total revenue
dao.burningman.selectedContributorAddress=Receiver address
dao.burningman.shared.table.height=ارتفاع بلاک
dao.burningman.shared.table.cycle=دوره
@ -1812,6 +1836,8 @@ dao.burningman.table.balanceEntry.revenue=Revenue
dao.burningman.table.balanceEntry.price=BSQ/BTC price
dao.burningman.table.balanceEntry.type=نوع
dao.burningman.accounting.popup=To display accounting data of a burningman you need to enable the 'process burningman accounting data' option in settings.\nDo you want to do that now?\nIt will require to restart Bisq to apply that change.\n\nIf you cancel, the displayed accounting data are not up-to-date.
# From BalanceEntry.Type enum names
dao.burningman.balanceEntry.type.UNDEFINED=تعریف نشده
dao.burningman.balanceEntry.type.BTC_TRADE_FEE_TX=کارمزد معامله

View File

@ -362,6 +362,13 @@ offerbook.timeSinceSigning.tooltip.checkmark.wait=attendez au minimum {0} jours
offerbook.timeSinceSigning.tooltip.learnMore=En savoir plus
offerbook.xmrAutoConf=Est-ce-que la confirmation automatique est activée
offerbook.cloneOffer=Clone offer (with shared maker fee)
offerbook.clonedOffer.tooltip=This is a cloned offer with shared maker fee transaction ID.\n\Maker fee transaction ID: {0}
offerbook.nonClonedOffer.tooltip=Regular offer without shared maker fee transaction ID.\n\Maker fee transaction ID: {0}
offerbook.cannotActivate.warning=This cloned offer with shared maker fee cannot be activated because it uses the same payment method and currency as another active offer.\n\nYou need to edit the offer and change the payment method or currency or deactivate the offer which has the same payment method and currency.
offerbook.cannotActivateEditedOffer.warning=You can't activate an offer that is currently edited.
offerbook.clonedOffer.info=By cloning an offer one creates a copy of the given offer with a new offer ID but using the same maker fee transaction ID.\n\nThis means there is no extra maker fee needed to get paid and the funds reserved for that offer can be re-used by the cloned offers. This reduces the liquidity requirements for market makers and allows them to post the same offer in different markets or with different payment methods.\n\nAs a consequence if one of the offers sharing the same maker fee transaction is taken all the other offers will get closed as well because the transaction output of that maker fee transaction is spent and would render the other offers invalid. \n\nThis feature requires to use the same trade amount and security deposit and is only permitted for offers with different payment methods or currencies.\n\nFor more information about cloning an offer see: [HYPERLINK:https://bisq.wiki/Cloning_an_offer]
offerbook.timeSinceSigning.help=Lorsque vous effectuez avec succès une transaction avec un pair disposant d''un compte de paiement signé, votre compte de paiement est signé.\n{0} Jours plus tard, la limite initiale de {1} est levée et votre compte peut signer les comptes de paiement d''un autre pair.
offerbook.timeSinceSigning.notSigned=Pas encore signé
offerbook.timeSinceSigning.notSigned.ageDays={0} jours
@ -565,6 +572,7 @@ takeOffer.tac=En acceptant cet ordre vous acceptez les conditions de transaction
####################################################################
openOffer.header.triggerPrice=Prix de déclenchement
openOffer.header.makerFeeTxId=Maker fee
openOffer.triggerPrice=Prix de déclenchement {0}
openOffer.triggered=Cette offre a été désactivée car le prix du marché a atteint votre prix de déclenchement\nVeuillez éditer votre offre pour définir un nouveau prix de déclenchement
@ -576,7 +584,14 @@ editOffer.publishOffer=Publication de votre ordre.
editOffer.failed=Échec de la modification de l''ordre:\n{0}
editOffer.success=Votre ordre a été modifié avec succès.
editOffer.invalidDeposit=Le dépôt de garantie de l'acheteur ne respecte pas le cadre des contraintes définies par Bisq DAO et ne peut plus être modifié.
editOffer.openTabWarning=You have already the \"Edit Offer\" tab open.
editOffer.cannotActivateOffer=You have edited an offer which uses a shared maker fee with another offer and your edit made the payment method and currency now the same as that of another active cloned offer. Your edited offer will be deactivated because it is not permitted to publish 2 offers sharing the same maker fee with the same payment method and currency.\n\nYou can edit the offer again at \"Portfolio/My open offers\" to fulfill the requirements to activate it.
cloneOffer.clone=Clone offer
cloneOffer.publishOffer=Publishing cloned offer.
cloneOffer.success=Your offer has been successfully cloned.
cloneOffer.cannotActivateOffer=You have not changed the payment method or the currency. You still can clone the offer, but it will be deactivated and not published.\n\nYou can edit the offer later again at \"Portfolio/My open offers\" to fulfill the requirements to activate it.\n\nDo you still want to clone the offer?
cloneOffer.openTabWarning=You have already the \"Clone Offer\" tab open.
####################################################################
# BSQ Swap offer
@ -604,7 +619,7 @@ portfolio.tab.bsqSwap=Échanges BSQ non-confirmés
portfolio.tab.failed=Échec
portfolio.tab.editOpenOffer=Éditer l'ordre
portfolio.tab.duplicateOffer=Doublon d'offre
portfolio.context.offerLikeThis=Créer une nouvelle offre similaire...
portfolio.tab.cloneOpenOffer=Clone offer
portfolio.context.notYourOffer=Vous pouvez uniquement dupliquer des offres où vous étiez le maker.
portfolio.closedTrades.deviation.help=Pourcentage de déviation du prix par rapport au marché
@ -1069,6 +1084,8 @@ support.warning.disputesWithInvalidDonationAddress=La transaction de paiement re
support.warning.disputesWithInvalidDonationAddress.mediator=\n\nVoulez-vous toujours fermer le litige?
support.warning.disputesWithInvalidDonationAddress.refundAgent=\n\nVous ne devez pas effectuer le paiement.
support.warning.traderCloseOwnDisputeWarning=Les traders peuvent uniquement fermer eux-même les tickets d'assistance quand le trade a été payé.
support.warning.ticketNotAcknowledged=Ticket not acknowledged.
support.resendTicket=This trader has not acknowledged receipt of the dispute ticket.\nWould you like to re-send the ticket?
support.info.disputedTradeUpdate=Disputed trade update: {0}
####################################################################
@ -1131,6 +1148,7 @@ setting.preferences.dao.resyncFromResources.popup=Après un redémarrage de l'ap
setting.preferences.dao.resyncFromGenesis.popup=La synchronisation à partir de la transaction de genèse consomme beaucoup de temps et de ressources CPU. Êtes-vous sûr de vouloir resynchroniser ? En général, la resynchronisation à partir du dernier fichier de ressources est suffisante et plus rapide. \n\nAprès le redémarrage de l'application, les données de gestion du réseau Bisq seront rechargées à partir du nœud d'amorçage et l'état de synchronisation BSQ sera reconstruit à partir de la transaction initiale.
setting.preferences.dao.resyncFromGenesis.resync=Resynchroniser depuis la genèse et fermer
setting.preferences.dao.isDaoFullNode=Exécuter la DAO de Bisq en tant que full node
setting.preferences.dao.processBurningManAccountingData=Process Burningman accounting data
setting.preferences.dao.fullModeDaoMonitor=Full-mode DAO state monitoring
setting.preferences.dao.fullModeDaoMonitor.popup=If full-mode DAO state monitoring is activated the DAO state hashes are created during parsing the BSQ blocks. This comes with considerable performance costs at the initial DAO sync.\n\nFor users who are regularily using Bisq this should not be an issue as there are not many blocks pending for parsing, though for users who only use Bisq casually creating the DAO state hashes for 100s or 1000s of blocks degrades heavily the user experience.\n\nIn case full-mode is deactivated (default) the missing DAO state hashes are requested from network nodes and the DAO state hash based on the most recent block will be created by the user. As all hashes are connected by reference to the previous hash a correct hash at the chain tip means that all past hashes are correct as well. The main functionality of the DAO state monitoring - to detect if the local DAO state is out of sync with the rest of the network - is therefore still fulfilled.
@ -1784,8 +1802,14 @@ dao.burningman.contributorsComboBox.prompt=Select any of my contributors
dao.burningman.daoBalance=Balance for DAO
dao.burningman.daoBalanceTotalBurned=Total amount of burned BSQ
dao.burningman.daoBalanceTotalDistributed=Total amount of distributed BTC / BSQ
dao.burningman.daoBalanceTotalBtcFees=Total amount of BTC fees in BTC / BSQ
dao.burningman.daoBalanceTotalDPT=Total amount of delayed payout transactions BTC / BSQ
dao.burningman.selectedContributor=Selected contributor
dao.burningman.selectedContributor.disabledAccounting=(accounting data not updated)
dao.burningman.selectedContributor.processing=(still processing data...)
dao.burningman.selectedContributorName=Contributor name
dao.burningman.selectedContributorTotalReceived=Total received
dao.burningman.selectedContributorTotalRevenue=Total revenue
dao.burningman.selectedContributorAddress=Receiver address
dao.burningman.shared.table.height=Hauteur de bloc
dao.burningman.shared.table.cycle=Cycle
@ -1812,6 +1836,8 @@ dao.burningman.table.balanceEntry.revenue=Revenue
dao.burningman.table.balanceEntry.price=Prix BSQ/BTC
dao.burningman.table.balanceEntry.type=Type
dao.burningman.accounting.popup=To display accounting data of a burningman you need to enable the 'process burningman accounting data' option in settings.\nDo you want to do that now?\nIt will require to restart Bisq to apply that change.\n\nIf you cancel, the displayed accounting data are not up-to-date.
# From BalanceEntry.Type enum names
dao.burningman.balanceEntry.type.UNDEFINED=Indéterminé
dao.burningman.balanceEntry.type.BTC_TRADE_FEE_TX=Frais de transaction du trade

View File

@ -362,6 +362,13 @@ offerbook.timeSinceSigning.tooltip.checkmark.wait=wait a minimum of {0} days
offerbook.timeSinceSigning.tooltip.learnMore=Leggi di più
offerbook.xmrAutoConf=Is auto-confirm enabled
offerbook.cloneOffer=Clone offer (with shared maker fee)
offerbook.clonedOffer.tooltip=This is a cloned offer with shared maker fee transaction ID.\n\Maker fee transaction ID: {0}
offerbook.nonClonedOffer.tooltip=Regular offer without shared maker fee transaction ID.\n\Maker fee transaction ID: {0}
offerbook.cannotActivate.warning=This cloned offer with shared maker fee cannot be activated because it uses the same payment method and currency as another active offer.\n\nYou need to edit the offer and change the payment method or currency or deactivate the offer which has the same payment method and currency.
offerbook.cannotActivateEditedOffer.warning=You can't activate an offer that is currently edited.
offerbook.clonedOffer.info=By cloning an offer one creates a copy of the given offer with a new offer ID but using the same maker fee transaction ID.\n\nThis means there is no extra maker fee needed to get paid and the funds reserved for that offer can be re-used by the cloned offers. This reduces the liquidity requirements for market makers and allows them to post the same offer in different markets or with different payment methods.\n\nAs a consequence if one of the offers sharing the same maker fee transaction is taken all the other offers will get closed as well because the transaction output of that maker fee transaction is spent and would render the other offers invalid. \n\nThis feature requires to use the same trade amount and security deposit and is only permitted for offers with different payment methods or currencies.\n\nFor more information about cloning an offer see: [HYPERLINK:https://bisq.wiki/Cloning_an_offer]
offerbook.timeSinceSigning.help=Quando completi correttamente un'operazione con un peer che ha un account di pagamento firmato, il tuo account di pagamento viene firmato.\n{0} giorni dopo, il limite iniziale di {1} viene alzato e il tuo account può firmare account di pagamento di altri peer.
offerbook.timeSinceSigning.notSigned=Non ancora firmato
offerbook.timeSinceSigning.notSigned.ageDays={0} giorni
@ -565,6 +572,7 @@ takeOffer.tac=Accettando questa offerta, accetto le condizioni commerciali defin
####################################################################
openOffer.header.triggerPrice=Prezzo di attivazione
openOffer.header.makerFeeTxId=Maker fee
openOffer.triggerPrice=Trigger price {0}
openOffer.triggered=The offer has been deactivated because the market price reached your trigger price.\nPlease edit the offer to define a new trigger price
@ -576,7 +584,14 @@ editOffer.publishOffer=Pubblica la tua offerta.
editOffer.failed=Modifica dell'offerta fallita:\n{0}
editOffer.success=La tua offerta è stata modificata con successo.
editOffer.invalidDeposit=Il deposito di sicurezza dell'acquirente non rientra nei vincoli definiti dalla DAO di Bisq e non può più essere modificato.
editOffer.openTabWarning=You have already the \"Edit Offer\" tab open.
editOffer.cannotActivateOffer=You have edited an offer which uses a shared maker fee with another offer and your edit made the payment method and currency now the same as that of another active cloned offer. Your edited offer will be deactivated because it is not permitted to publish 2 offers sharing the same maker fee with the same payment method and currency.\n\nYou can edit the offer again at \"Portfolio/My open offers\" to fulfill the requirements to activate it.
cloneOffer.clone=Clone offer
cloneOffer.publishOffer=Publishing cloned offer.
cloneOffer.success=Your offer has been successfully cloned.
cloneOffer.cannotActivateOffer=You have not changed the payment method or the currency. You still can clone the offer, but it will be deactivated and not published.\n\nYou can edit the offer later again at \"Portfolio/My open offers\" to fulfill the requirements to activate it.\n\nDo you still want to clone the offer?
cloneOffer.openTabWarning=You have already the \"Clone Offer\" tab open.
####################################################################
# BSQ Swap offer
@ -604,7 +619,7 @@ portfolio.tab.bsqSwap=Unconfirmed BSQ swaps
portfolio.tab.failed=Fallita
portfolio.tab.editOpenOffer=Modifica offerta
portfolio.tab.duplicateOffer=Offerta duplicata
portfolio.context.offerLikeThis=Create new offer like this...
portfolio.tab.cloneOpenOffer=Clone offer
portfolio.context.notYourOffer=You can only duplicate offers where you were the maker.
portfolio.closedTrades.deviation.help=Percentage price deviation from market
@ -1069,6 +1084,8 @@ support.warning.disputesWithInvalidDonationAddress=The delayed payout transactio
support.warning.disputesWithInvalidDonationAddress.mediator=\n\nDo you still want to close the dispute?
support.warning.disputesWithInvalidDonationAddress.refundAgent=\n\nYou must not do the payout.
support.warning.traderCloseOwnDisputeWarning=Traders can only self-close their support tickets when the trade has been paid out.
support.warning.ticketNotAcknowledged=Ticket not acknowledged.
support.resendTicket=This trader has not acknowledged receipt of the dispute ticket.\nWould you like to re-send the ticket?
support.info.disputedTradeUpdate=Disputed trade update: {0}
####################################################################
@ -1131,6 +1148,7 @@ setting.preferences.dao.resyncFromResources.popup=After an application restart t
setting.preferences.dao.resyncFromGenesis.popup=A resync from genesis transaction can take considerable time and CPU resources. Are you sure you want to do that? Mostly a resync from latest resource files is sufficient and much faster.\n\nIf you proceed, after an application restart the Bisq network governance data will be reloaded from the seed nodes and the BSQ consensus state will be rebuilt from the genesis transaction.
setting.preferences.dao.resyncFromGenesis.resync=Resync from genesis and shutdown
setting.preferences.dao.isDaoFullNode=Lancia Bisq come full node DAO
setting.preferences.dao.processBurningManAccountingData=Process Burningman accounting data
setting.preferences.dao.fullModeDaoMonitor=Full-mode DAO state monitoring
setting.preferences.dao.fullModeDaoMonitor.popup=If full-mode DAO state monitoring is activated the DAO state hashes are created during parsing the BSQ blocks. This comes with considerable performance costs at the initial DAO sync.\n\nFor users who are regularily using Bisq this should not be an issue as there are not many blocks pending for parsing, though for users who only use Bisq casually creating the DAO state hashes for 100s or 1000s of blocks degrades heavily the user experience.\n\nIn case full-mode is deactivated (default) the missing DAO state hashes are requested from network nodes and the DAO state hash based on the most recent block will be created by the user. As all hashes are connected by reference to the previous hash a correct hash at the chain tip means that all past hashes are correct as well. The main functionality of the DAO state monitoring - to detect if the local DAO state is out of sync with the rest of the network - is therefore still fulfilled.
@ -1784,8 +1802,14 @@ dao.burningman.contributorsComboBox.prompt=Select any of my contributors
dao.burningman.daoBalance=Balance for DAO
dao.burningman.daoBalanceTotalBurned=Total amount of burned BSQ
dao.burningman.daoBalanceTotalDistributed=Total amount of distributed BTC / BSQ
dao.burningman.daoBalanceTotalBtcFees=Total amount of BTC fees in BTC / BSQ
dao.burningman.daoBalanceTotalDPT=Total amount of delayed payout transactions BTC / BSQ
dao.burningman.selectedContributor=Selected contributor
dao.burningman.selectedContributor.disabledAccounting=(accounting data not updated)
dao.burningman.selectedContributor.processing=(still processing data...)
dao.burningman.selectedContributorName=Contributor name
dao.burningman.selectedContributorTotalReceived=Total received
dao.burningman.selectedContributorTotalRevenue=Total revenue
dao.burningman.selectedContributorAddress=Receiver address
dao.burningman.shared.table.height=Altezza del blocco
dao.burningman.shared.table.cycle=Ciclo
@ -1812,6 +1836,8 @@ dao.burningman.table.balanceEntry.revenue=Revenue
dao.burningman.table.balanceEntry.price=BSQ/BTC price
dao.burningman.table.balanceEntry.type=Tipo
dao.burningman.accounting.popup=To display accounting data of a burningman you need to enable the 'process burningman accounting data' option in settings.\nDo you want to do that now?\nIt will require to restart Bisq to apply that change.\n\nIf you cancel, the displayed accounting data are not up-to-date.
# From BalanceEntry.Type enum names
dao.burningman.balanceEntry.type.UNDEFINED=Non definito
dao.burningman.balanceEntry.type.BTC_TRADE_FEE_TX=Commissione di scambio

View File

@ -362,6 +362,13 @@ offerbook.timeSinceSigning.tooltip.checkmark.wait=wait a minimum of {0} days
offerbook.timeSinceSigning.tooltip.learnMore=もっと詳しく知る
offerbook.xmrAutoConf=自動確認は有効されますか?
offerbook.cloneOffer=Clone offer (with shared maker fee)
offerbook.clonedOffer.tooltip=This is a cloned offer with shared maker fee transaction ID.\n\Maker fee transaction ID: {0}
offerbook.nonClonedOffer.tooltip=Regular offer without shared maker fee transaction ID.\n\Maker fee transaction ID: {0}
offerbook.cannotActivate.warning=This cloned offer with shared maker fee cannot be activated because it uses the same payment method and currency as another active offer.\n\nYou need to edit the offer and change the payment method or currency or deactivate the offer which has the same payment method and currency.
offerbook.cannotActivateEditedOffer.warning=You can't activate an offer that is currently edited.
offerbook.clonedOffer.info=By cloning an offer one creates a copy of the given offer with a new offer ID but using the same maker fee transaction ID.\n\nThis means there is no extra maker fee needed to get paid and the funds reserved for that offer can be re-used by the cloned offers. This reduces the liquidity requirements for market makers and allows them to post the same offer in different markets or with different payment methods.\n\nAs a consequence if one of the offers sharing the same maker fee transaction is taken all the other offers will get closed as well because the transaction output of that maker fee transaction is spent and would render the other offers invalid. \n\nThis feature requires to use the same trade amount and security deposit and is only permitted for offers with different payment methods or currencies.\n\nFor more information about cloning an offer see: [HYPERLINK:https://bisq.wiki/Cloning_an_offer]
offerbook.timeSinceSigning.help=署名された支払いアカウントを持っているピアと成功にトレードすると、自身の支払いアカウントも署名されることになります。\n{0} 日後に、{1} という初期の制限は解除され、他のピアの支払いアカウントを署名できるようになります。
offerbook.timeSinceSigning.notSigned=まだ署名されていません
offerbook.timeSinceSigning.notSigned.ageDays={0}日
@ -565,6 +572,7 @@ takeOffer.tac=このオファーを受けることで、この画面で定義さ
####################################################################
openOffer.header.triggerPrice=価格トリガー
openOffer.header.makerFeeTxId=Maker fee
openOffer.triggerPrice=価格トリガー{0}
openOffer.triggered=市場価格は価格トリガーに達しましたため、オファーが無効にされました。\nオファーには新しい価格トリガーを設定して下さい。
@ -576,7 +584,14 @@ editOffer.publishOffer=あなたのオファーの公開。
editOffer.failed=オファー編集に失敗:\n{0}
editOffer.success=オファー編集に成功しました
editOffer.invalidDeposit=買い手のセキュリティデポジットはBisq DAOによって定義された制約の範囲内ではなく、もう編集することはできません。
editOffer.openTabWarning=You have already the \"Edit Offer\" tab open.
editOffer.cannotActivateOffer=You have edited an offer which uses a shared maker fee with another offer and your edit made the payment method and currency now the same as that of another active cloned offer. Your edited offer will be deactivated because it is not permitted to publish 2 offers sharing the same maker fee with the same payment method and currency.\n\nYou can edit the offer again at \"Portfolio/My open offers\" to fulfill the requirements to activate it.
cloneOffer.clone=Clone offer
cloneOffer.publishOffer=Publishing cloned offer.
cloneOffer.success=Your offer has been successfully cloned.
cloneOffer.cannotActivateOffer=You have not changed the payment method or the currency. You still can clone the offer, but it will be deactivated and not published.\n\nYou can edit the offer later again at \"Portfolio/My open offers\" to fulfill the requirements to activate it.\n\nDo you still want to clone the offer?
cloneOffer.openTabWarning=You have already the \"Clone Offer\" tab open.
####################################################################
# BSQ Swap offer
@ -604,7 +619,7 @@ portfolio.tab.bsqSwap=Unconfirmed BSQ swaps
portfolio.tab.failed=失敗
portfolio.tab.editOpenOffer=オファーを編集
portfolio.tab.duplicateOffer=重複オファー
portfolio.context.offerLikeThis=Create new offer like this...
portfolio.tab.cloneOpenOffer=Clone offer
portfolio.context.notYourOffer=You can only duplicate offers where you were the maker.
portfolio.closedTrades.deviation.help=市場からの割合価格偏差
@ -1069,6 +1084,8 @@ support.warning.disputesWithInvalidDonationAddress=遅延支払いトランザ
support.warning.disputesWithInvalidDonationAddress.mediator=\n\n係争を閉じても本当によろしいですか
support.warning.disputesWithInvalidDonationAddress.refundAgent=\n\n支払いを送信してはいけません。
support.warning.traderCloseOwnDisputeWarning=Traders can only self-close their support tickets when the trade has been paid out.
support.warning.ticketNotAcknowledged=Ticket not acknowledged.
support.resendTicket=This trader has not acknowledged receipt of the dispute ticket.\nWould you like to re-send the ticket?
support.info.disputedTradeUpdate=Disputed trade update: {0}
####################################################################
@ -1131,6 +1148,7 @@ setting.preferences.dao.resyncFromResources.popup=アプリケーションの再
setting.preferences.dao.resyncFromGenesis.popup=ジェネシストランザクションからの再同期はかなりの時間をかけて、かなりのCPUリソースを消費します。本当によろしいですか大抵の場合は最新リソースファイルからの再同期は十分、より早い選択です。\n\n進めたら、アプリケーションの再起動後、Bisqネットワークガバナンスデータはシードードから再ロードされ、BSQのコンセンサス状態はジェネシストランザクションから再構築されるでしょう。
setting.preferences.dao.resyncFromGenesis.resync=ジェネシスから再同期して終了
setting.preferences.dao.isDaoFullNode=BisqをDAOのフルードで実行
setting.preferences.dao.processBurningManAccountingData=Process Burningman accounting data
setting.preferences.dao.fullModeDaoMonitor=Full-mode DAO state monitoring
setting.preferences.dao.fullModeDaoMonitor.popup=If full-mode DAO state monitoring is activated the DAO state hashes are created during parsing the BSQ blocks. This comes with considerable performance costs at the initial DAO sync.\n\nFor users who are regularily using Bisq this should not be an issue as there are not many blocks pending for parsing, though for users who only use Bisq casually creating the DAO state hashes for 100s or 1000s of blocks degrades heavily the user experience.\n\nIn case full-mode is deactivated (default) the missing DAO state hashes are requested from network nodes and the DAO state hash based on the most recent block will be created by the user. As all hashes are connected by reference to the previous hash a correct hash at the chain tip means that all past hashes are correct as well. The main functionality of the DAO state monitoring - to detect if the local DAO state is out of sync with the rest of the network - is therefore still fulfilled.
@ -1784,8 +1802,14 @@ dao.burningman.contributorsComboBox.prompt=Select any of my contributors
dao.burningman.daoBalance=Balance for DAO
dao.burningman.daoBalanceTotalBurned=Total amount of burned BSQ
dao.burningman.daoBalanceTotalDistributed=Total amount of distributed BTC / BSQ
dao.burningman.daoBalanceTotalBtcFees=Total amount of BTC fees in BTC / BSQ
dao.burningman.daoBalanceTotalDPT=Total amount of delayed payout transactions BTC / BSQ
dao.burningman.selectedContributor=Selected contributor
dao.burningman.selectedContributor.disabledAccounting=(accounting data not updated)
dao.burningman.selectedContributor.processing=(still processing data...)
dao.burningman.selectedContributorName=Contributor name
dao.burningman.selectedContributorTotalReceived=Total received
dao.burningman.selectedContributorTotalRevenue=Total revenue
dao.burningman.selectedContributorAddress=Receiver address
dao.burningman.shared.table.height=ブロックの高さ
dao.burningman.shared.table.cycle=サイクル
@ -1812,6 +1836,8 @@ dao.burningman.table.balanceEntry.revenue=Revenue
dao.burningman.table.balanceEntry.price=BSQ/BTC price
dao.burningman.table.balanceEntry.type=タイプ
dao.burningman.accounting.popup=To display accounting data of a burningman you need to enable the 'process burningman accounting data' option in settings.\nDo you want to do that now?\nIt will require to restart Bisq to apply that change.\n\nIf you cancel, the displayed accounting data are not up-to-date.
# From BalanceEntry.Type enum names
dao.burningman.balanceEntry.type.UNDEFINED=未定義
dao.burningman.balanceEntry.type.BTC_TRADE_FEE_TX=取引手数料

View File

@ -362,6 +362,13 @@ offerbook.timeSinceSigning.tooltip.checkmark.wait=wait a minimum of {0} days
offerbook.timeSinceSigning.tooltip.learnMore=Dowiedz się więcej
offerbook.xmrAutoConf=Automatyczne potwierdzenie włączone
offerbook.cloneOffer=Clone offer (with shared maker fee)
offerbook.clonedOffer.tooltip=This is a cloned offer with shared maker fee transaction ID.\n\Maker fee transaction ID: {0}
offerbook.nonClonedOffer.tooltip=Regular offer without shared maker fee transaction ID.\n\Maker fee transaction ID: {0}
offerbook.cannotActivate.warning=This cloned offer with shared maker fee cannot be activated because it uses the same payment method and currency as another active offer.\n\nYou need to edit the offer and change the payment method or currency or deactivate the offer which has the same payment method and currency.
offerbook.cannotActivateEditedOffer.warning=You can't activate an offer that is currently edited.
offerbook.clonedOffer.info=By cloning an offer one creates a copy of the given offer with a new offer ID but using the same maker fee transaction ID.\n\nThis means there is no extra maker fee needed to get paid and the funds reserved for that offer can be re-used by the cloned offers. This reduces the liquidity requirements for market makers and allows them to post the same offer in different markets or with different payment methods.\n\nAs a consequence if one of the offers sharing the same maker fee transaction is taken all the other offers will get closed as well because the transaction output of that maker fee transaction is spent and would render the other offers invalid. \n\nThis feature requires to use the same trade amount and security deposit and is only permitted for offers with different payment methods or currencies.\n\nFor more information about cloning an offer see: [HYPERLINK:https://bisq.wiki/Cloning_an_offer]
offerbook.timeSinceSigning.help=Kiedy z sukcesem zakończysz transakcję z członkiem sieci który ma podpisane konto, Twoje konto zostaje podpisane.\n{0} dni później, początkowy limit {1} jest zniesiony i Twoje konto może podpisywać konta innych.
offerbook.timeSinceSigning.notSigned=Jeszcze nie podpisane
offerbook.timeSinceSigning.notSigned.ageDays={0} dni
@ -565,6 +572,7 @@ takeOffer.tac=Zawierając tą ofertę zgadzam się z warunkami handlu zdefiniowa
####################################################################
openOffer.header.triggerPrice=Cena progowa
openOffer.header.makerFeeTxId=Maker fee
openOffer.triggerPrice=Cena progowa {0}
openOffer.triggered=Oferta została zdezaktywowana ponieważ cena rynkowa osiągnęła Twoją cenę progową. \nZmień ofertę tak aby dopasować ją do nowej ceny progowej
@ -576,7 +584,14 @@ editOffer.publishOffer=Publikacja Twojej oferty.
editOffer.failed=Zmiana oferty nie powiodła się:\n{0}
editOffer.success=Twoja oferta została zmieniona z powodzeniem.
editOffer.invalidDeposit=Depozyt bezpieczeństwa kupującego nie jest ograniczony przez DAO Bisq i nie może być edytowany.
editOffer.openTabWarning=You have already the \"Edit Offer\" tab open.
editOffer.cannotActivateOffer=You have edited an offer which uses a shared maker fee with another offer and your edit made the payment method and currency now the same as that of another active cloned offer. Your edited offer will be deactivated because it is not permitted to publish 2 offers sharing the same maker fee with the same payment method and currency.\n\nYou can edit the offer again at \"Portfolio/My open offers\" to fulfill the requirements to activate it.
cloneOffer.clone=Clone offer
cloneOffer.publishOffer=Publishing cloned offer.
cloneOffer.success=Your offer has been successfully cloned.
cloneOffer.cannotActivateOffer=You have not changed the payment method or the currency. You still can clone the offer, but it will be deactivated and not published.\n\nYou can edit the offer later again at \"Portfolio/My open offers\" to fulfill the requirements to activate it.\n\nDo you still want to clone the offer?
cloneOffer.openTabWarning=You have already the \"Clone Offer\" tab open.
####################################################################
# BSQ Swap offer
@ -604,7 +619,7 @@ portfolio.tab.bsqSwap=Unconfirmed BSQ swaps
portfolio.tab.failed=Nie udało się
portfolio.tab.editOpenOffer=Edytuj ofertę
portfolio.tab.duplicateOffer=Powiel ofertę
portfolio.context.offerLikeThis=Stwórz nową ofertę jak ta...
portfolio.tab.cloneOpenOffer=Clone offer
portfolio.context.notYourOffer=Możesz jedynie powielić oferty jeśli byłeś twórcą.
portfolio.closedTrades.deviation.help=Odchylenie procentowe od ceny rynkowej
@ -1069,6 +1084,8 @@ support.warning.disputesWithInvalidDonationAddress=Opóźniona transakcja wypła
support.warning.disputesWithInvalidDonationAddress.mediator=\n\nCzy wciąż chcesz zamknąć spór ?
support.warning.disputesWithInvalidDonationAddress.refundAgent=\n\nNie możesz dokonać wypłaty
support.warning.traderCloseOwnDisputeWarning=Obie strony transakcji mogą jedynie sami zamknąć zgłoszenia serwisowe w momencie kiedy z obu stron kwoty zostaną przesłane.
support.warning.ticketNotAcknowledged=Ticket not acknowledged.
support.resendTicket=This trader has not acknowledged receipt of the dispute ticket.\nWould you like to re-send the ticket?
support.info.disputedTradeUpdate=Disputed trade update: {0}
####################################################################
@ -1131,6 +1148,7 @@ setting.preferences.dao.resyncFromResources.popup=Po restarcie aplikacji adminis
setting.preferences.dao.resyncFromGenesis.popup=Ponowna sychronizacja od transakcji Genesis może zająć znaczącą ilosć czasu i mocy CPU. Czy jesteś pewien że chcesz to zrobić ? Zwykle synchronizacja od ostatnio zapisanego lokalnie pliku jest wystarczająca i znacznie szybsza.\n\nJeśli będziesz kontynuować, po restarcie aplikacji dane administracji sieci Bisq zostaną ponownie załadowane z seed notes i stan konsensusu Bisq zostanie odtworzony na nowo od transakcji Genesis.
setting.preferences.dao.resyncFromGenesis.resync=Zsynchronizuj ponownie od transakcji Genesis i zamknij
setting.preferences.dao.isDaoFullNode=Uruchom Bisq jako pełny węzeł DAO
setting.preferences.dao.processBurningManAccountingData=Process Burningman accounting data
setting.preferences.dao.fullModeDaoMonitor=Full-mode DAO state monitoring
setting.preferences.dao.fullModeDaoMonitor.popup=If full-mode DAO state monitoring is activated the DAO state hashes are created during parsing the BSQ blocks. This comes with considerable performance costs at the initial DAO sync.\n\nFor users who are regularily using Bisq this should not be an issue as there are not many blocks pending for parsing, though for users who only use Bisq casually creating the DAO state hashes for 100s or 1000s of blocks degrades heavily the user experience.\n\nIn case full-mode is deactivated (default) the missing DAO state hashes are requested from network nodes and the DAO state hash based on the most recent block will be created by the user. As all hashes are connected by reference to the previous hash a correct hash at the chain tip means that all past hashes are correct as well. The main functionality of the DAO state monitoring - to detect if the local DAO state is out of sync with the rest of the network - is therefore still fulfilled.
@ -1784,8 +1802,14 @@ dao.burningman.contributorsComboBox.prompt=Select any of my contributors
dao.burningman.daoBalance=Balance for DAO
dao.burningman.daoBalanceTotalBurned=Total amount of burned BSQ
dao.burningman.daoBalanceTotalDistributed=Total amount of distributed BTC / BSQ
dao.burningman.daoBalanceTotalBtcFees=Total amount of BTC fees in BTC / BSQ
dao.burningman.daoBalanceTotalDPT=Total amount of delayed payout transactions BTC / BSQ
dao.burningman.selectedContributor=Selected contributor
dao.burningman.selectedContributor.disabledAccounting=(accounting data not updated)
dao.burningman.selectedContributor.processing=(still processing data...)
dao.burningman.selectedContributorName=Contributor name
dao.burningman.selectedContributorTotalReceived=Total received
dao.burningman.selectedContributorTotalRevenue=Total revenue
dao.burningman.selectedContributorAddress=Receiver address
dao.burningman.shared.table.height=Wysokość bloku
dao.burningman.shared.table.cycle=Cykl
@ -1812,6 +1836,8 @@ dao.burningman.table.balanceEntry.revenue=Revenue
dao.burningman.table.balanceEntry.price=Cena BSQ/BTC
dao.burningman.table.balanceEntry.type=Typ
dao.burningman.accounting.popup=To display accounting data of a burningman you need to enable the 'process burningman accounting data' option in settings.\nDo you want to do that now?\nIt will require to restart Bisq to apply that change.\n\nIf you cancel, the displayed accounting data are not up-to-date.
# From BalanceEntry.Type enum names
dao.burningman.balanceEntry.type.UNDEFINED=Niezdefiniowane
dao.burningman.balanceEntry.type.BTC_TRADE_FEE_TX=Opłata za dokonanie transakcji

View File

@ -362,6 +362,13 @@ offerbook.timeSinceSigning.tooltip.checkmark.wait=wait a minimum of {0} days
offerbook.timeSinceSigning.tooltip.learnMore=Saiba mais
offerbook.xmrAutoConf=Is auto-confirm enabled
offerbook.cloneOffer=Clone offer (with shared maker fee)
offerbook.clonedOffer.tooltip=This is a cloned offer with shared maker fee transaction ID.\n\Maker fee transaction ID: {0}
offerbook.nonClonedOffer.tooltip=Regular offer without shared maker fee transaction ID.\n\Maker fee transaction ID: {0}
offerbook.cannotActivate.warning=This cloned offer with shared maker fee cannot be activated because it uses the same payment method and currency as another active offer.\n\nYou need to edit the offer and change the payment method or currency or deactivate the offer which has the same payment method and currency.
offerbook.cannotActivateEditedOffer.warning=You can't activate an offer that is currently edited.
offerbook.clonedOffer.info=By cloning an offer one creates a copy of the given offer with a new offer ID but using the same maker fee transaction ID.\n\nThis means there is no extra maker fee needed to get paid and the funds reserved for that offer can be re-used by the cloned offers. This reduces the liquidity requirements for market makers and allows them to post the same offer in different markets or with different payment methods.\n\nAs a consequence if one of the offers sharing the same maker fee transaction is taken all the other offers will get closed as well because the transaction output of that maker fee transaction is spent and would render the other offers invalid. \n\nThis feature requires to use the same trade amount and security deposit and is only permitted for offers with different payment methods or currencies.\n\nFor more information about cloning an offer see: [HYPERLINK:https://bisq.wiki/Cloning_an_offer]
offerbook.timeSinceSigning.help=Quando você completa uma negociação bem sucedida com um par que tem uma conta de pagamento assinada, a sua conta de pagamento é assinada.\n{0} dias depois, o limite inicial de {1} é levantado e sua conta pode assinar as contas de pagamento de outros pares.
offerbook.timeSinceSigning.notSigned=Ainda não assinada
offerbook.timeSinceSigning.notSigned.ageDays={0} dias
@ -565,6 +572,7 @@ takeOffer.tac=Ao aceitar essa oferta, eu concordo com as condições de negocia
####################################################################
openOffer.header.triggerPrice=Preço gatilho
openOffer.header.makerFeeTxId=Maker fee
openOffer.triggerPrice=Trigger price {0}
openOffer.triggered=The offer has been deactivated because the market price reached your trigger price.\nPlease edit the offer to define a new trigger price
@ -576,7 +584,14 @@ editOffer.publishOffer=Publicando a sua oferta.
editOffer.failed=Erro ao editar oferta:\n{0}
editOffer.success=A sua oferta foi editada com sucesso.
editOffer.invalidDeposit=O depósito de segurança do comprador não está dentro dos limites definidos pela DAO Bisq e não pode mais ser editado.
editOffer.openTabWarning=You have already the \"Edit Offer\" tab open.
editOffer.cannotActivateOffer=You have edited an offer which uses a shared maker fee with another offer and your edit made the payment method and currency now the same as that of another active cloned offer. Your edited offer will be deactivated because it is not permitted to publish 2 offers sharing the same maker fee with the same payment method and currency.\n\nYou can edit the offer again at \"Portfolio/My open offers\" to fulfill the requirements to activate it.
cloneOffer.clone=Clone offer
cloneOffer.publishOffer=Publishing cloned offer.
cloneOffer.success=Your offer has been successfully cloned.
cloneOffer.cannotActivateOffer=You have not changed the payment method or the currency. You still can clone the offer, but it will be deactivated and not published.\n\nYou can edit the offer later again at \"Portfolio/My open offers\" to fulfill the requirements to activate it.\n\nDo you still want to clone the offer?
cloneOffer.openTabWarning=You have already the \"Clone Offer\" tab open.
####################################################################
# BSQ Swap offer
@ -604,7 +619,7 @@ portfolio.tab.bsqSwap=Unconfirmed BSQ swaps
portfolio.tab.failed=Falha
portfolio.tab.editOpenOffer=Editar oferta
portfolio.tab.duplicateOffer=Duplicate offer
portfolio.context.offerLikeThis=Create new offer like this...
portfolio.tab.cloneOpenOffer=Clone offer
portfolio.context.notYourOffer=You can only duplicate offers where you were the maker.
portfolio.closedTrades.deviation.help=Percentage price deviation from market
@ -1069,6 +1084,8 @@ support.warning.disputesWithInvalidDonationAddress=The delayed payout transactio
support.warning.disputesWithInvalidDonationAddress.mediator=\n\nDo you still want to close the dispute?
support.warning.disputesWithInvalidDonationAddress.refundAgent=\n\nYou must not do the payout.
support.warning.traderCloseOwnDisputeWarning=Traders can only self-close their support tickets when the trade has been paid out.
support.warning.ticketNotAcknowledged=Ticket not acknowledged.
support.resendTicket=This trader has not acknowledged receipt of the dispute ticket.\nWould you like to re-send the ticket?
support.info.disputedTradeUpdate=Disputed trade update: {0}
####################################################################
@ -1131,6 +1148,7 @@ setting.preferences.dao.resyncFromResources.popup=After an application restart t
setting.preferences.dao.resyncFromGenesis.popup=A resync from genesis transaction can take considerable time and CPU resources. Are you sure you want to do that? Mostly a resync from latest resource files is sufficient and much faster.\n\nIf you proceed, after an application restart the Bisq network governance data will be reloaded from the seed nodes and the BSQ consensus state will be rebuilt from the genesis transaction.
setting.preferences.dao.resyncFromGenesis.resync=Resync from genesis and shutdown
setting.preferences.dao.isDaoFullNode=Executar Bisq como nó completo DAO
setting.preferences.dao.processBurningManAccountingData=Process Burningman accounting data
setting.preferences.dao.fullModeDaoMonitor=Full-mode DAO state monitoring
setting.preferences.dao.fullModeDaoMonitor.popup=If full-mode DAO state monitoring is activated the DAO state hashes are created during parsing the BSQ blocks. This comes with considerable performance costs at the initial DAO sync.\n\nFor users who are regularily using Bisq this should not be an issue as there are not many blocks pending for parsing, though for users who only use Bisq casually creating the DAO state hashes for 100s or 1000s of blocks degrades heavily the user experience.\n\nIn case full-mode is deactivated (default) the missing DAO state hashes are requested from network nodes and the DAO state hash based on the most recent block will be created by the user. As all hashes are connected by reference to the previous hash a correct hash at the chain tip means that all past hashes are correct as well. The main functionality of the DAO state monitoring - to detect if the local DAO state is out of sync with the rest of the network - is therefore still fulfilled.
@ -1784,8 +1802,14 @@ dao.burningman.contributorsComboBox.prompt=Select any of my contributors
dao.burningman.daoBalance=Balance for DAO
dao.burningman.daoBalanceTotalBurned=Total amount of burned BSQ
dao.burningman.daoBalanceTotalDistributed=Total amount of distributed BTC / BSQ
dao.burningman.daoBalanceTotalBtcFees=Total amount of BTC fees in BTC / BSQ
dao.burningman.daoBalanceTotalDPT=Total amount of delayed payout transactions BTC / BSQ
dao.burningman.selectedContributor=Selected contributor
dao.burningman.selectedContributor.disabledAccounting=(accounting data not updated)
dao.burningman.selectedContributor.processing=(still processing data...)
dao.burningman.selectedContributorName=Contributor name
dao.burningman.selectedContributorTotalReceived=Total received
dao.burningman.selectedContributorTotalRevenue=Total revenue
dao.burningman.selectedContributorAddress=Receiver address
dao.burningman.shared.table.height=Altura do bloco
dao.burningman.shared.table.cycle=Ciclo
@ -1812,6 +1836,8 @@ dao.burningman.table.balanceEntry.revenue=Revenue
dao.burningman.table.balanceEntry.price=BSQ/BTC price
dao.burningman.table.balanceEntry.type=Tipo
dao.burningman.accounting.popup=To display accounting data of a burningman you need to enable the 'process burningman accounting data' option in settings.\nDo you want to do that now?\nIt will require to restart Bisq to apply that change.\n\nIf you cancel, the displayed accounting data are not up-to-date.
# From BalanceEntry.Type enum names
dao.burningman.balanceEntry.type.UNDEFINED=Indefinido
dao.burningman.balanceEntry.type.BTC_TRADE_FEE_TX=Trade fee

View File

@ -362,6 +362,13 @@ offerbook.timeSinceSigning.tooltip.checkmark.wait=wait a minimum of {0} days
offerbook.timeSinceSigning.tooltip.learnMore=Saber mais
offerbook.xmrAutoConf=Is auto-confirm enabled
offerbook.cloneOffer=Clone offer (with shared maker fee)
offerbook.clonedOffer.tooltip=This is a cloned offer with shared maker fee transaction ID.\n\Maker fee transaction ID: {0}
offerbook.nonClonedOffer.tooltip=Regular offer without shared maker fee transaction ID.\n\Maker fee transaction ID: {0}
offerbook.cannotActivate.warning=This cloned offer with shared maker fee cannot be activated because it uses the same payment method and currency as another active offer.\n\nYou need to edit the offer and change the payment method or currency or deactivate the offer which has the same payment method and currency.
offerbook.cannotActivateEditedOffer.warning=You can't activate an offer that is currently edited.
offerbook.clonedOffer.info=By cloning an offer one creates a copy of the given offer with a new offer ID but using the same maker fee transaction ID.\n\nThis means there is no extra maker fee needed to get paid and the funds reserved for that offer can be re-used by the cloned offers. This reduces the liquidity requirements for market makers and allows them to post the same offer in different markets or with different payment methods.\n\nAs a consequence if one of the offers sharing the same maker fee transaction is taken all the other offers will get closed as well because the transaction output of that maker fee transaction is spent and would render the other offers invalid. \n\nThis feature requires to use the same trade amount and security deposit and is only permitted for offers with different payment methods or currencies.\n\nFor more information about cloning an offer see: [HYPERLINK:https://bisq.wiki/Cloning_an_offer]
offerbook.timeSinceSigning.help=Quando você completa com sucesso um negócio com um par que tenha uma conta de pagamento assinada, a sua conta de pagamento é assinada .\n{0} dias depois, o limite inicial de {1} é aumentado e a sua conta pode assinar contas de pagamento de outros pares.
offerbook.timeSinceSigning.notSigned=Ainda não assinada
offerbook.timeSinceSigning.notSigned.ageDays={0} dias
@ -565,6 +572,7 @@ takeOffer.tac=Ao aceitar esta oferta, eu concordo com as condições de negócio
####################################################################
openOffer.header.triggerPrice=Preço de desencadeamento
openOffer.header.makerFeeTxId=Maker fee
openOffer.triggerPrice=Trigger price {0}
openOffer.triggered=The offer has been deactivated because the market price reached your trigger price.\nPlease edit the offer to define a new trigger price
@ -576,7 +584,14 @@ editOffer.publishOffer=Publicando sua oferta.
editOffer.failed=A edição da oferta falhou:\n{0}
editOffer.success=Sua oferta foi editada com sucesso.
editOffer.invalidDeposit=O depósito de segurança do comprador não está dentro dos limites definidos pela OAD do Bisq e não pode mais ser editado.
editOffer.openTabWarning=You have already the \"Edit Offer\" tab open.
editOffer.cannotActivateOffer=You have edited an offer which uses a shared maker fee with another offer and your edit made the payment method and currency now the same as that of another active cloned offer. Your edited offer will be deactivated because it is not permitted to publish 2 offers sharing the same maker fee with the same payment method and currency.\n\nYou can edit the offer again at \"Portfolio/My open offers\" to fulfill the requirements to activate it.
cloneOffer.clone=Clone offer
cloneOffer.publishOffer=Publishing cloned offer.
cloneOffer.success=Your offer has been successfully cloned.
cloneOffer.cannotActivateOffer=You have not changed the payment method or the currency. You still can clone the offer, but it will be deactivated and not published.\n\nYou can edit the offer later again at \"Portfolio/My open offers\" to fulfill the requirements to activate it.\n\nDo you still want to clone the offer?
cloneOffer.openTabWarning=You have already the \"Clone Offer\" tab open.
####################################################################
# BSQ Swap offer
@ -604,7 +619,7 @@ portfolio.tab.bsqSwap=Unconfirmed BSQ swaps
portfolio.tab.failed=Falhou
portfolio.tab.editOpenOffer=Editar oferta
portfolio.tab.duplicateOffer=Duplicate offer
portfolio.context.offerLikeThis=Create new offer like this...
portfolio.tab.cloneOpenOffer=Clone offer
portfolio.context.notYourOffer=You can only duplicate offers where you were the maker.
portfolio.closedTrades.deviation.help=Percentage price deviation from market
@ -1069,6 +1084,8 @@ support.warning.disputesWithInvalidDonationAddress=The delayed payout transactio
support.warning.disputesWithInvalidDonationAddress.mediator=\n\nDo you still want to close the dispute?
support.warning.disputesWithInvalidDonationAddress.refundAgent=\n\nYou must not do the payout.
support.warning.traderCloseOwnDisputeWarning=Traders can only self-close their support tickets when the trade has been paid out.
support.warning.ticketNotAcknowledged=Ticket not acknowledged.
support.resendTicket=This trader has not acknowledged receipt of the dispute ticket.\nWould you like to re-send the ticket?
support.info.disputedTradeUpdate=Disputed trade update: {0}
####################################################################
@ -1131,6 +1148,7 @@ setting.preferences.dao.resyncFromResources.popup=After an application restart t
setting.preferences.dao.resyncFromGenesis.popup=A resync from genesis transaction can take considerable time and CPU resources. Are you sure you want to do that? Mostly a resync from latest resource files is sufficient and much faster.\n\nIf you proceed, after an application restart the Bisq network governance data will be reloaded from the seed nodes and the BSQ consensus state will be rebuilt from the genesis transaction.
setting.preferences.dao.resyncFromGenesis.resync=Resync from genesis and shutdown
setting.preferences.dao.isDaoFullNode=Executar Bisq como nó completo OAD
setting.preferences.dao.processBurningManAccountingData=Process Burningman accounting data
setting.preferences.dao.fullModeDaoMonitor=Full-mode DAO state monitoring
setting.preferences.dao.fullModeDaoMonitor.popup=If full-mode DAO state monitoring is activated the DAO state hashes are created during parsing the BSQ blocks. This comes with considerable performance costs at the initial DAO sync.\n\nFor users who are regularily using Bisq this should not be an issue as there are not many blocks pending for parsing, though for users who only use Bisq casually creating the DAO state hashes for 100s or 1000s of blocks degrades heavily the user experience.\n\nIn case full-mode is deactivated (default) the missing DAO state hashes are requested from network nodes and the DAO state hash based on the most recent block will be created by the user. As all hashes are connected by reference to the previous hash a correct hash at the chain tip means that all past hashes are correct as well. The main functionality of the DAO state monitoring - to detect if the local DAO state is out of sync with the rest of the network - is therefore still fulfilled.
@ -1784,8 +1802,14 @@ dao.burningman.contributorsComboBox.prompt=Select any of my contributors
dao.burningman.daoBalance=Balance for DAO
dao.burningman.daoBalanceTotalBurned=Total amount of burned BSQ
dao.burningman.daoBalanceTotalDistributed=Total amount of distributed BTC / BSQ
dao.burningman.daoBalanceTotalBtcFees=Total amount of BTC fees in BTC / BSQ
dao.burningman.daoBalanceTotalDPT=Total amount of delayed payout transactions BTC / BSQ
dao.burningman.selectedContributor=Selected contributor
dao.burningman.selectedContributor.disabledAccounting=(accounting data not updated)
dao.burningman.selectedContributor.processing=(still processing data...)
dao.burningman.selectedContributorName=Contributor name
dao.burningman.selectedContributorTotalReceived=Total received
dao.burningman.selectedContributorTotalRevenue=Total revenue
dao.burningman.selectedContributorAddress=Receiver address
dao.burningman.shared.table.height=Altura do bloco
dao.burningman.shared.table.cycle=Ciclo
@ -1812,6 +1836,8 @@ dao.burningman.table.balanceEntry.revenue=Revenue
dao.burningman.table.balanceEntry.price=BSQ/BTC price
dao.burningman.table.balanceEntry.type=Tipo
dao.burningman.accounting.popup=To display accounting data of a burningman you need to enable the 'process burningman accounting data' option in settings.\nDo you want to do that now?\nIt will require to restart Bisq to apply that change.\n\nIf you cancel, the displayed accounting data are not up-to-date.
# From BalanceEntry.Type enum names
dao.burningman.balanceEntry.type.UNDEFINED=Indefinido
dao.burningman.balanceEntry.type.BTC_TRADE_FEE_TX=Taxa de negócio

View File

@ -362,6 +362,13 @@ offerbook.timeSinceSigning.tooltip.checkmark.wait=wait a minimum of {0} days
offerbook.timeSinceSigning.tooltip.learnMore=Узнать больше
offerbook.xmrAutoConf=Is auto-confirm enabled
offerbook.cloneOffer=Clone offer (with shared maker fee)
offerbook.clonedOffer.tooltip=This is a cloned offer with shared maker fee transaction ID.\n\Maker fee transaction ID: {0}
offerbook.nonClonedOffer.tooltip=Regular offer without shared maker fee transaction ID.\n\Maker fee transaction ID: {0}
offerbook.cannotActivate.warning=This cloned offer with shared maker fee cannot be activated because it uses the same payment method and currency as another active offer.\n\nYou need to edit the offer and change the payment method or currency or deactivate the offer which has the same payment method and currency.
offerbook.cannotActivateEditedOffer.warning=You can't activate an offer that is currently edited.
offerbook.clonedOffer.info=By cloning an offer one creates a copy of the given offer with a new offer ID but using the same maker fee transaction ID.\n\nThis means there is no extra maker fee needed to get paid and the funds reserved for that offer can be re-used by the cloned offers. This reduces the liquidity requirements for market makers and allows them to post the same offer in different markets or with different payment methods.\n\nAs a consequence if one of the offers sharing the same maker fee transaction is taken all the other offers will get closed as well because the transaction output of that maker fee transaction is spent and would render the other offers invalid. \n\nThis feature requires to use the same trade amount and security deposit and is only permitted for offers with different payment methods or currencies.\n\nFor more information about cloning an offer see: [HYPERLINK:https://bisq.wiki/Cloning_an_offer]
offerbook.timeSinceSigning.help=When you successfully complete a trade with a peer who has a signed payment account, your payment account is signed.\n{0} days later, the initial limit of {1} is lifted and your account can sign other peers'' payment accounts.
offerbook.timeSinceSigning.notSigned=Not signed yet
offerbook.timeSinceSigning.notSigned.ageDays={0} дн.
@ -565,6 +572,7 @@ takeOffer.tac=Принимая это предложение, я соглаша
####################################################################
openOffer.header.triggerPrice=Начальная цена
openOffer.header.makerFeeTxId=Maker fee
openOffer.triggerPrice=Trigger price {0}
openOffer.triggered=The offer has been deactivated because the market price reached your trigger price.\nPlease edit the offer to define a new trigger price
@ -576,7 +584,14 @@ editOffer.publishOffer=Публикация вашего предложения.
editOffer.failed=Не удалось изменить предложение:\n{0}
editOffer.success=Ваше предложение успешно отредактировано.
editOffer.invalidDeposit=Сумма залога покупателя не регулируется ДАО Bisq и больше не подлежит изменению.
editOffer.openTabWarning=You have already the \"Edit Offer\" tab open.
editOffer.cannotActivateOffer=You have edited an offer which uses a shared maker fee with another offer and your edit made the payment method and currency now the same as that of another active cloned offer. Your edited offer will be deactivated because it is not permitted to publish 2 offers sharing the same maker fee with the same payment method and currency.\n\nYou can edit the offer again at \"Portfolio/My open offers\" to fulfill the requirements to activate it.
cloneOffer.clone=Clone offer
cloneOffer.publishOffer=Publishing cloned offer.
cloneOffer.success=Your offer has been successfully cloned.
cloneOffer.cannotActivateOffer=You have not changed the payment method or the currency. You still can clone the offer, but it will be deactivated and not published.\n\nYou can edit the offer later again at \"Portfolio/My open offers\" to fulfill the requirements to activate it.\n\nDo you still want to clone the offer?
cloneOffer.openTabWarning=You have already the \"Clone Offer\" tab open.
####################################################################
# BSQ Swap offer
@ -604,7 +619,7 @@ portfolio.tab.bsqSwap=Unconfirmed BSQ swaps
portfolio.tab.failed=Не удалось
portfolio.tab.editOpenOffer=Изменить предложение
portfolio.tab.duplicateOffer=Duplicate offer
portfolio.context.offerLikeThis=Create new offer like this...
portfolio.tab.cloneOpenOffer=Clone offer
portfolio.context.notYourOffer=You can only duplicate offers where you were the maker.
portfolio.closedTrades.deviation.help=Percentage price deviation from market
@ -1069,6 +1084,8 @@ support.warning.disputesWithInvalidDonationAddress=The delayed payout transactio
support.warning.disputesWithInvalidDonationAddress.mediator=\n\nDo you still want to close the dispute?
support.warning.disputesWithInvalidDonationAddress.refundAgent=\n\nYou must not do the payout.
support.warning.traderCloseOwnDisputeWarning=Traders can only self-close their support tickets when the trade has been paid out.
support.warning.ticketNotAcknowledged=Ticket not acknowledged.
support.resendTicket=This trader has not acknowledged receipt of the dispute ticket.\nWould you like to re-send the ticket?
support.info.disputedTradeUpdate=Disputed trade update: {0}
####################################################################
@ -1131,6 +1148,7 @@ setting.preferences.dao.resyncFromResources.popup=After an application restart t
setting.preferences.dao.resyncFromGenesis.popup=A resync from genesis transaction can take considerable time and CPU resources. Are you sure you want to do that? Mostly a resync from latest resource files is sufficient and much faster.\n\nIf you proceed, after an application restart the Bisq network governance data will be reloaded from the seed nodes and the BSQ consensus state will be rebuilt from the genesis transaction.
setting.preferences.dao.resyncFromGenesis.resync=Resync from genesis and shutdown
setting.preferences.dao.isDaoFullNode=Запустить Bisq в режиме полного узла ДАО
setting.preferences.dao.processBurningManAccountingData=Process Burningman accounting data
setting.preferences.dao.fullModeDaoMonitor=Full-mode DAO state monitoring
setting.preferences.dao.fullModeDaoMonitor.popup=If full-mode DAO state monitoring is activated the DAO state hashes are created during parsing the BSQ blocks. This comes with considerable performance costs at the initial DAO sync.\n\nFor users who are regularily using Bisq this should not be an issue as there are not many blocks pending for parsing, though for users who only use Bisq casually creating the DAO state hashes for 100s or 1000s of blocks degrades heavily the user experience.\n\nIn case full-mode is deactivated (default) the missing DAO state hashes are requested from network nodes and the DAO state hash based on the most recent block will be created by the user. As all hashes are connected by reference to the previous hash a correct hash at the chain tip means that all past hashes are correct as well. The main functionality of the DAO state monitoring - to detect if the local DAO state is out of sync with the rest of the network - is therefore still fulfilled.
@ -1784,8 +1802,14 @@ dao.burningman.contributorsComboBox.prompt=Select any of my contributors
dao.burningman.daoBalance=Balance for DAO
dao.burningman.daoBalanceTotalBurned=Total amount of burned BSQ
dao.burningman.daoBalanceTotalDistributed=Total amount of distributed BTC / BSQ
dao.burningman.daoBalanceTotalBtcFees=Total amount of BTC fees in BTC / BSQ
dao.burningman.daoBalanceTotalDPT=Total amount of delayed payout transactions BTC / BSQ
dao.burningman.selectedContributor=Selected contributor
dao.burningman.selectedContributor.disabledAccounting=(accounting data not updated)
dao.burningman.selectedContributor.processing=(still processing data...)
dao.burningman.selectedContributorName=Contributor name
dao.burningman.selectedContributorTotalReceived=Total received
dao.burningman.selectedContributorTotalRevenue=Total revenue
dao.burningman.selectedContributorAddress=Receiver address
dao.burningman.shared.table.height=Номер блока
dao.burningman.shared.table.cycle=Цикл
@ -1812,6 +1836,8 @@ dao.burningman.table.balanceEntry.revenue=Revenue
dao.burningman.table.balanceEntry.price=BSQ/BTC price
dao.burningman.table.balanceEntry.type=Тип
dao.burningman.accounting.popup=To display accounting data of a burningman you need to enable the 'process burningman accounting data' option in settings.\nDo you want to do that now?\nIt will require to restart Bisq to apply that change.\n\nIf you cancel, the displayed accounting data are not up-to-date.
# From BalanceEntry.Type enum names
dao.burningman.balanceEntry.type.UNDEFINED=Не определено
dao.burningman.balanceEntry.type.BTC_TRADE_FEE_TX=Комиссия за сделку

View File

@ -362,6 +362,13 @@ offerbook.timeSinceSigning.tooltip.checkmark.wait=wait a minimum of {0} days
offerbook.timeSinceSigning.tooltip.learnMore=Learn more
offerbook.xmrAutoConf=Is auto-confirm enabled
offerbook.cloneOffer=Clone offer (with shared maker fee)
offerbook.clonedOffer.tooltip=This is a cloned offer with shared maker fee transaction ID.\n\Maker fee transaction ID: {0}
offerbook.nonClonedOffer.tooltip=Regular offer without shared maker fee transaction ID.\n\Maker fee transaction ID: {0}
offerbook.cannotActivate.warning=This cloned offer with shared maker fee cannot be activated because it uses the same payment method and currency as another active offer.\n\nYou need to edit the offer and change the payment method or currency or deactivate the offer which has the same payment method and currency.
offerbook.cannotActivateEditedOffer.warning=You can't activate an offer that is currently edited.
offerbook.clonedOffer.info=By cloning an offer one creates a copy of the given offer with a new offer ID but using the same maker fee transaction ID.\n\nThis means there is no extra maker fee needed to get paid and the funds reserved for that offer can be re-used by the cloned offers. This reduces the liquidity requirements for market makers and allows them to post the same offer in different markets or with different payment methods.\n\nAs a consequence if one of the offers sharing the same maker fee transaction is taken all the other offers will get closed as well because the transaction output of that maker fee transaction is spent and would render the other offers invalid. \n\nThis feature requires to use the same trade amount and security deposit and is only permitted for offers with different payment methods or currencies.\n\nFor more information about cloning an offer see: [HYPERLINK:https://bisq.wiki/Cloning_an_offer]
offerbook.timeSinceSigning.help=When you successfully complete a trade with a peer who has a signed payment account, your payment account is signed.\n{0} days later, the initial limit of {1} is lifted and your account can sign other peers'' payment accounts.
offerbook.timeSinceSigning.notSigned=Not signed yet
offerbook.timeSinceSigning.notSigned.ageDays={0} วัน
@ -565,6 +572,7 @@ takeOffer.tac=ด้วยข้อเสนอนี้ฉันยอมรั
####################################################################
openOffer.header.triggerPrice= ราคาเงื่อนไขที่ตั้งไว้
openOffer.header.makerFeeTxId=Maker fee
openOffer.triggerPrice=Trigger price {0}
openOffer.triggered=The offer has been deactivated because the market price reached your trigger price.\nPlease edit the offer to define a new trigger price
@ -576,7 +584,14 @@ editOffer.publishOffer=กำลังเผยแพร่ข้อเสนอ
editOffer.failed=การแก้ไขข้อเสนอล้มเหลว: \n{0}
editOffer.success=ข้อเสนอของคุณได้รับการแก้ไขเรียบร้อยแล้ว
editOffer.invalidDeposit=The buyer's security deposit is not within the constraints defined by the Bisq DAO and can no longer be edited.
editOffer.openTabWarning=You have already the \"Edit Offer\" tab open.
editOffer.cannotActivateOffer=You have edited an offer which uses a shared maker fee with another offer and your edit made the payment method and currency now the same as that of another active cloned offer. Your edited offer will be deactivated because it is not permitted to publish 2 offers sharing the same maker fee with the same payment method and currency.\n\nYou can edit the offer again at \"Portfolio/My open offers\" to fulfill the requirements to activate it.
cloneOffer.clone=Clone offer
cloneOffer.publishOffer=Publishing cloned offer.
cloneOffer.success=Your offer has been successfully cloned.
cloneOffer.cannotActivateOffer=You have not changed the payment method or the currency. You still can clone the offer, but it will be deactivated and not published.\n\nYou can edit the offer later again at \"Portfolio/My open offers\" to fulfill the requirements to activate it.\n\nDo you still want to clone the offer?
cloneOffer.openTabWarning=You have already the \"Clone Offer\" tab open.
####################################################################
# BSQ Swap offer
@ -604,7 +619,7 @@ portfolio.tab.bsqSwap=Unconfirmed BSQ swaps
portfolio.tab.failed=ผิดพลาด
portfolio.tab.editOpenOffer=แก้ไขข้อเสนอ
portfolio.tab.duplicateOffer=Duplicate offer
portfolio.context.offerLikeThis=Create new offer like this...
portfolio.tab.cloneOpenOffer=Clone offer
portfolio.context.notYourOffer=You can only duplicate offers where you were the maker.
portfolio.closedTrades.deviation.help=Percentage price deviation from market
@ -1069,6 +1084,8 @@ support.warning.disputesWithInvalidDonationAddress=The delayed payout transactio
support.warning.disputesWithInvalidDonationAddress.mediator=\n\nDo you still want to close the dispute?
support.warning.disputesWithInvalidDonationAddress.refundAgent=\n\nYou must not do the payout.
support.warning.traderCloseOwnDisputeWarning=Traders can only self-close their support tickets when the trade has been paid out.
support.warning.ticketNotAcknowledged=Ticket not acknowledged.
support.resendTicket=This trader has not acknowledged receipt of the dispute ticket.\nWould you like to re-send the ticket?
support.info.disputedTradeUpdate=Disputed trade update: {0}
####################################################################
@ -1131,6 +1148,7 @@ setting.preferences.dao.resyncFromResources.popup=After an application restart t
setting.preferences.dao.resyncFromGenesis.popup=A resync from genesis transaction can take considerable time and CPU resources. Are you sure you want to do that? Mostly a resync from latest resource files is sufficient and much faster.\n\nIf you proceed, after an application restart the Bisq network governance data will be reloaded from the seed nodes and the BSQ consensus state will be rebuilt from the genesis transaction.
setting.preferences.dao.resyncFromGenesis.resync=Resync from genesis and shutdown
setting.preferences.dao.isDaoFullNode=ใช้งาน Bisq ในแบบโหนด DAO full node
setting.preferences.dao.processBurningManAccountingData=Process Burningman accounting data
setting.preferences.dao.fullModeDaoMonitor=Full-mode DAO state monitoring
setting.preferences.dao.fullModeDaoMonitor.popup=If full-mode DAO state monitoring is activated the DAO state hashes are created during parsing the BSQ blocks. This comes with considerable performance costs at the initial DAO sync.\n\nFor users who are regularily using Bisq this should not be an issue as there are not many blocks pending for parsing, though for users who only use Bisq casually creating the DAO state hashes for 100s or 1000s of blocks degrades heavily the user experience.\n\nIn case full-mode is deactivated (default) the missing DAO state hashes are requested from network nodes and the DAO state hash based on the most recent block will be created by the user. As all hashes are connected by reference to the previous hash a correct hash at the chain tip means that all past hashes are correct as well. The main functionality of the DAO state monitoring - to detect if the local DAO state is out of sync with the rest of the network - is therefore still fulfilled.
@ -1784,8 +1802,14 @@ dao.burningman.contributorsComboBox.prompt=Select any of my contributors
dao.burningman.daoBalance=Balance for DAO
dao.burningman.daoBalanceTotalBurned=Total amount of burned BSQ
dao.burningman.daoBalanceTotalDistributed=Total amount of distributed BTC / BSQ
dao.burningman.daoBalanceTotalBtcFees=Total amount of BTC fees in BTC / BSQ
dao.burningman.daoBalanceTotalDPT=Total amount of delayed payout transactions BTC / BSQ
dao.burningman.selectedContributor=Selected contributor
dao.burningman.selectedContributor.disabledAccounting=(accounting data not updated)
dao.burningman.selectedContributor.processing=(still processing data...)
dao.burningman.selectedContributorName=Contributor name
dao.burningman.selectedContributorTotalReceived=Total received
dao.burningman.selectedContributorTotalRevenue=Total revenue
dao.burningman.selectedContributorAddress=Receiver address
dao.burningman.shared.table.height=Block height
dao.burningman.shared.table.cycle=วงจร
@ -1812,6 +1836,8 @@ dao.burningman.table.balanceEntry.revenue=Revenue
dao.burningman.table.balanceEntry.price=BSQ/BTC price
dao.burningman.table.balanceEntry.type=หมวด
dao.burningman.accounting.popup=To display accounting data of a burningman you need to enable the 'process burningman accounting data' option in settings.\nDo you want to do that now?\nIt will require to restart Bisq to apply that change.\n\nIf you cancel, the displayed accounting data are not up-to-date.
# From BalanceEntry.Type enum names
dao.burningman.balanceEntry.type.UNDEFINED=ไม่ได้กำหนด
dao.burningman.balanceEntry.type.BTC_TRADE_FEE_TX=ค่าธรรมเนียมการซื้อขาย

View File

@ -362,6 +362,13 @@ offerbook.timeSinceSigning.tooltip.checkmark.wait=wait a minimum of {0} days
offerbook.timeSinceSigning.tooltip.learnMore=Tìm hiểu thêm
offerbook.xmrAutoConf=Is auto-confirm enabled
offerbook.cloneOffer=Clone offer (with shared maker fee)
offerbook.clonedOffer.tooltip=This is a cloned offer with shared maker fee transaction ID.\n\Maker fee transaction ID: {0}
offerbook.nonClonedOffer.tooltip=Regular offer without shared maker fee transaction ID.\n\Maker fee transaction ID: {0}
offerbook.cannotActivate.warning=This cloned offer with shared maker fee cannot be activated because it uses the same payment method and currency as another active offer.\n\nYou need to edit the offer and change the payment method or currency or deactivate the offer which has the same payment method and currency.
offerbook.cannotActivateEditedOffer.warning=You can't activate an offer that is currently edited.
offerbook.clonedOffer.info=By cloning an offer one creates a copy of the given offer with a new offer ID but using the same maker fee transaction ID.\n\nThis means there is no extra maker fee needed to get paid and the funds reserved for that offer can be re-used by the cloned offers. This reduces the liquidity requirements for market makers and allows them to post the same offer in different markets or with different payment methods.\n\nAs a consequence if one of the offers sharing the same maker fee transaction is taken all the other offers will get closed as well because the transaction output of that maker fee transaction is spent and would render the other offers invalid. \n\nThis feature requires to use the same trade amount and security deposit and is only permitted for offers with different payment methods or currencies.\n\nFor more information about cloning an offer see: [HYPERLINK:https://bisq.wiki/Cloning_an_offer]
offerbook.timeSinceSigning.help=When you successfully complete a trade with a peer who has a signed payment account, your payment account is signed.\n{0} days later, the initial limit of {1} is lifted and your account can sign other peers'' payment accounts.
offerbook.timeSinceSigning.notSigned=Not signed yet
offerbook.timeSinceSigning.notSigned.ageDays={0} ngày
@ -565,6 +572,7 @@ takeOffer.tac=Bằng cách nhận báo giá này, tôi đồng ý với các đi
####################################################################
openOffer.header.triggerPrice=Giá khởi phát
openOffer.header.makerFeeTxId=Maker fee
openOffer.triggerPrice=Trigger price {0}
openOffer.triggered=The offer has been deactivated because the market price reached your trigger price.\nPlease edit the offer to define a new trigger price
@ -576,7 +584,14 @@ editOffer.publishOffer=Công bố báo giá.
editOffer.failed=Chỉnh sửa báo giá không thành công:\n{0}
editOffer.success=Báo giá của bạn đã được chỉnh sửa thành công.
editOffer.invalidDeposit=Số tiền đặt cọc cho người mua không nằm trong giới hạn quy định bởi DAO Bisq và không thể chỉnh sửa được nữa
editOffer.openTabWarning=You have already the \"Edit Offer\" tab open.
editOffer.cannotActivateOffer=You have edited an offer which uses a shared maker fee with another offer and your edit made the payment method and currency now the same as that of another active cloned offer. Your edited offer will be deactivated because it is not permitted to publish 2 offers sharing the same maker fee with the same payment method and currency.\n\nYou can edit the offer again at \"Portfolio/My open offers\" to fulfill the requirements to activate it.
cloneOffer.clone=Clone offer
cloneOffer.publishOffer=Publishing cloned offer.
cloneOffer.success=Your offer has been successfully cloned.
cloneOffer.cannotActivateOffer=You have not changed the payment method or the currency. You still can clone the offer, but it will be deactivated and not published.\n\nYou can edit the offer later again at \"Portfolio/My open offers\" to fulfill the requirements to activate it.\n\nDo you still want to clone the offer?
cloneOffer.openTabWarning=You have already the \"Clone Offer\" tab open.
####################################################################
# BSQ Swap offer
@ -604,7 +619,7 @@ portfolio.tab.bsqSwap=Unconfirmed BSQ swaps
portfolio.tab.failed=Không thành công
portfolio.tab.editOpenOffer=Chỉnh sửa báo giá
portfolio.tab.duplicateOffer=Duplicate offer
portfolio.context.offerLikeThis=Create new offer like this...
portfolio.tab.cloneOpenOffer=Clone offer
portfolio.context.notYourOffer=You can only duplicate offers where you were the maker.
portfolio.closedTrades.deviation.help=Percentage price deviation from market
@ -1069,6 +1084,8 @@ support.warning.disputesWithInvalidDonationAddress=The delayed payout transactio
support.warning.disputesWithInvalidDonationAddress.mediator=\n\nDo you still want to close the dispute?
support.warning.disputesWithInvalidDonationAddress.refundAgent=\n\nYou must not do the payout.
support.warning.traderCloseOwnDisputeWarning=Traders can only self-close their support tickets when the trade has been paid out.
support.warning.ticketNotAcknowledged=Ticket not acknowledged.
support.resendTicket=This trader has not acknowledged receipt of the dispute ticket.\nWould you like to re-send the ticket?
support.info.disputedTradeUpdate=Disputed trade update: {0}
####################################################################
@ -1131,6 +1148,7 @@ setting.preferences.dao.resyncFromResources.popup=After an application restart t
setting.preferences.dao.resyncFromGenesis.popup=A resync from genesis transaction can take considerable time and CPU resources. Are you sure you want to do that? Mostly a resync from latest resource files is sufficient and much faster.\n\nIf you proceed, after an application restart the Bisq network governance data will be reloaded from the seed nodes and the BSQ consensus state will be rebuilt from the genesis transaction.
setting.preferences.dao.resyncFromGenesis.resync=Resync from genesis and shutdown
setting.preferences.dao.isDaoFullNode=Chạy ứng dụng Bisq như một full node DAO
setting.preferences.dao.processBurningManAccountingData=Process Burningman accounting data
setting.preferences.dao.fullModeDaoMonitor=Full-mode DAO state monitoring
setting.preferences.dao.fullModeDaoMonitor.popup=If full-mode DAO state monitoring is activated the DAO state hashes are created during parsing the BSQ blocks. This comes with considerable performance costs at the initial DAO sync.\n\nFor users who are regularily using Bisq this should not be an issue as there are not many blocks pending for parsing, though for users who only use Bisq casually creating the DAO state hashes for 100s or 1000s of blocks degrades heavily the user experience.\n\nIn case full-mode is deactivated (default) the missing DAO state hashes are requested from network nodes and the DAO state hash based on the most recent block will be created by the user. As all hashes are connected by reference to the previous hash a correct hash at the chain tip means that all past hashes are correct as well. The main functionality of the DAO state monitoring - to detect if the local DAO state is out of sync with the rest of the network - is therefore still fulfilled.
@ -1784,8 +1802,14 @@ dao.burningman.contributorsComboBox.prompt=Select any of my contributors
dao.burningman.daoBalance=Balance for DAO
dao.burningman.daoBalanceTotalBurned=Total amount of burned BSQ
dao.burningman.daoBalanceTotalDistributed=Total amount of distributed BTC / BSQ
dao.burningman.daoBalanceTotalBtcFees=Total amount of BTC fees in BTC / BSQ
dao.burningman.daoBalanceTotalDPT=Total amount of delayed payout transactions BTC / BSQ
dao.burningman.selectedContributor=Selected contributor
dao.burningman.selectedContributor.disabledAccounting=(accounting data not updated)
dao.burningman.selectedContributor.processing=(still processing data...)
dao.burningman.selectedContributorName=Contributor name
dao.burningman.selectedContributorTotalReceived=Total received
dao.burningman.selectedContributorTotalRevenue=Total revenue
dao.burningman.selectedContributorAddress=Receiver address
dao.burningman.shared.table.height=Chiều cao khối
dao.burningman.shared.table.cycle=Vòng
@ -1812,6 +1836,8 @@ dao.burningman.table.balanceEntry.revenue=Revenue
dao.burningman.table.balanceEntry.price=BSQ/BTC price
dao.burningman.table.balanceEntry.type=Loại
dao.burningman.accounting.popup=To display accounting data of a burningman you need to enable the 'process burningman accounting data' option in settings.\nDo you want to do that now?\nIt will require to restart Bisq to apply that change.\n\nIf you cancel, the displayed accounting data are not up-to-date.
# From BalanceEntry.Type enum names
dao.burningman.balanceEntry.type.UNDEFINED=Không xác định
dao.burningman.balanceEntry.type.BTC_TRADE_FEE_TX=Phí giao dịch

View File

@ -362,6 +362,13 @@ offerbook.timeSinceSigning.tooltip.checkmark.wait=wait a minimum of {0} days
offerbook.timeSinceSigning.tooltip.learnMore=了解更多
offerbook.xmrAutoConf=是否开启自动确认
offerbook.cloneOffer=Clone offer (with shared maker fee)
offerbook.clonedOffer.tooltip=This is a cloned offer with shared maker fee transaction ID.\n\Maker fee transaction ID: {0}
offerbook.nonClonedOffer.tooltip=Regular offer without shared maker fee transaction ID.\n\Maker fee transaction ID: {0}
offerbook.cannotActivate.warning=This cloned offer with shared maker fee cannot be activated because it uses the same payment method and currency as another active offer.\n\nYou need to edit the offer and change the payment method or currency or deactivate the offer which has the same payment method and currency.
offerbook.cannotActivateEditedOffer.warning=You can't activate an offer that is currently edited.
offerbook.clonedOffer.info=By cloning an offer one creates a copy of the given offer with a new offer ID but using the same maker fee transaction ID.\n\nThis means there is no extra maker fee needed to get paid and the funds reserved for that offer can be re-used by the cloned offers. This reduces the liquidity requirements for market makers and allows them to post the same offer in different markets or with different payment methods.\n\nAs a consequence if one of the offers sharing the same maker fee transaction is taken all the other offers will get closed as well because the transaction output of that maker fee transaction is spent and would render the other offers invalid. \n\nThis feature requires to use the same trade amount and security deposit and is only permitted for offers with different payment methods or currencies.\n\nFor more information about cloning an offer see: [HYPERLINK:https://bisq.wiki/Cloning_an_offer]
offerbook.timeSinceSigning.help=当您成功地完成与拥有已验证付款帐户的伙伴交易时,您的付款帐户已验证。\n{0} 天后,最初的 {1} 的限制解除以及你的账户可以验证其他人的付款账户。
offerbook.timeSinceSigning.notSigned=尚未验证
offerbook.timeSinceSigning.notSigned.ageDays={0} 天
@ -565,6 +572,7 @@ takeOffer.tac=接受该报价,意味着我同意这交易界面中的条件。
####################################################################
openOffer.header.triggerPrice=触发价格
openOffer.header.makerFeeTxId=Maker fee
openOffer.triggerPrice=Trigger price {0}
openOffer.triggered=The offer has been deactivated because the market price reached your trigger price.\nPlease edit the offer to define a new trigger price
@ -576,7 +584,14 @@ editOffer.publishOffer=发布您的报价。
editOffer.failed=报价编辑失败:\n{0}
editOffer.success=您的报价已成功编辑。
editOffer.invalidDeposit=买方保证金不符合 Bisq DAO 规定,不能再次编辑。
editOffer.openTabWarning=You have already the \"Edit Offer\" tab open.
editOffer.cannotActivateOffer=You have edited an offer which uses a shared maker fee with another offer and your edit made the payment method and currency now the same as that of another active cloned offer. Your edited offer will be deactivated because it is not permitted to publish 2 offers sharing the same maker fee with the same payment method and currency.\n\nYou can edit the offer again at \"Portfolio/My open offers\" to fulfill the requirements to activate it.
cloneOffer.clone=Clone offer
cloneOffer.publishOffer=Publishing cloned offer.
cloneOffer.success=Your offer has been successfully cloned.
cloneOffer.cannotActivateOffer=You have not changed the payment method or the currency. You still can clone the offer, but it will be deactivated and not published.\n\nYou can edit the offer later again at \"Portfolio/My open offers\" to fulfill the requirements to activate it.\n\nDo you still want to clone the offer?
cloneOffer.openTabWarning=You have already the \"Clone Offer\" tab open.
####################################################################
# BSQ Swap offer
@ -604,7 +619,7 @@ portfolio.tab.bsqSwap=Unconfirmed BSQ swaps
portfolio.tab.failed=失败
portfolio.tab.editOpenOffer=编辑报价
portfolio.tab.duplicateOffer=Duplicate offer
portfolio.context.offerLikeThis=Create new offer like this...
portfolio.tab.cloneOpenOffer=Clone offer
portfolio.context.notYourOffer=You can only duplicate offers where you were the maker.
portfolio.closedTrades.deviation.help=与市场价格偏差百分比
@ -1069,6 +1084,8 @@ support.warning.disputesWithInvalidDonationAddress=延迟支付交易已经被
support.warning.disputesWithInvalidDonationAddress.mediator=\n\n您确定一定要关闭纠纷吗
support.warning.disputesWithInvalidDonationAddress.refundAgent=\n\n您不能进行支付。
support.warning.traderCloseOwnDisputeWarning=Traders can only self-close their support tickets when the trade has been paid out.
support.warning.ticketNotAcknowledged=Ticket not acknowledged.
support.resendTicket=This trader has not acknowledged receipt of the dispute ticket.\nWould you like to re-send the ticket?
support.info.disputedTradeUpdate=Disputed trade update: {0}
####################################################################
@ -1131,6 +1148,7 @@ setting.preferences.dao.resyncFromResources.popup=应用程序重新启动后,
setting.preferences.dao.resyncFromGenesis.popup=从创始交易中出现同步会消耗大量时间以及 CPU 资源。您确定要重新同步吗?通常,从最新资源文件进行重新同步就足够了,而且速度更快。\n\n应用程序重新启动后Bisq 网络治理数据将从种子节点重新加载,而 BSQ 同步状态将从初始交易中重新构建。
setting.preferences.dao.resyncFromGenesis.resync=从创始区块重新同步并关闭
setting.preferences.dao.isDaoFullNode=以 DAO 全节点运行 Bisq
setting.preferences.dao.processBurningManAccountingData=Process Burningman accounting data
setting.preferences.dao.fullModeDaoMonitor=Full-mode DAO state monitoring
setting.preferences.dao.fullModeDaoMonitor.popup=If full-mode DAO state monitoring is activated the DAO state hashes are created during parsing the BSQ blocks. This comes with considerable performance costs at the initial DAO sync.\n\nFor users who are regularily using Bisq this should not be an issue as there are not many blocks pending for parsing, though for users who only use Bisq casually creating the DAO state hashes for 100s or 1000s of blocks degrades heavily the user experience.\n\nIn case full-mode is deactivated (default) the missing DAO state hashes are requested from network nodes and the DAO state hash based on the most recent block will be created by the user. As all hashes are connected by reference to the previous hash a correct hash at the chain tip means that all past hashes are correct as well. The main functionality of the DAO state monitoring - to detect if the local DAO state is out of sync with the rest of the network - is therefore still fulfilled.
@ -1784,8 +1802,14 @@ dao.burningman.contributorsComboBox.prompt=Select any of my contributors
dao.burningman.daoBalance=Balance for DAO
dao.burningman.daoBalanceTotalBurned=Total amount of burned BSQ
dao.burningman.daoBalanceTotalDistributed=Total amount of distributed BTC / BSQ
dao.burningman.daoBalanceTotalBtcFees=Total amount of BTC fees in BTC / BSQ
dao.burningman.daoBalanceTotalDPT=Total amount of delayed payout transactions BTC / BSQ
dao.burningman.selectedContributor=Selected contributor
dao.burningman.selectedContributor.disabledAccounting=(accounting data not updated)
dao.burningman.selectedContributor.processing=(still processing data...)
dao.burningman.selectedContributorName=Contributor name
dao.burningman.selectedContributorTotalReceived=Total received
dao.burningman.selectedContributorTotalRevenue=Total revenue
dao.burningman.selectedContributorAddress=Receiver address
dao.burningman.shared.table.height=区块高度
dao.burningman.shared.table.cycle=周期
@ -1812,6 +1836,8 @@ dao.burningman.table.balanceEntry.revenue=Revenue
dao.burningman.table.balanceEntry.price=BSQ/BTC price
dao.burningman.table.balanceEntry.type=类型
dao.burningman.accounting.popup=To display accounting data of a burningman you need to enable the 'process burningman accounting data' option in settings.\nDo you want to do that now?\nIt will require to restart Bisq to apply that change.\n\nIf you cancel, the displayed accounting data are not up-to-date.
# From BalanceEntry.Type enum names
dao.burningman.balanceEntry.type.UNDEFINED=未定义
dao.burningman.balanceEntry.type.BTC_TRADE_FEE_TX=挂单费

View File

@ -362,6 +362,13 @@ offerbook.timeSinceSigning.tooltip.checkmark.wait=wait a minimum of {0} days
offerbook.timeSinceSigning.tooltip.learnMore=瞭解更多
offerbook.xmrAutoConf=是否開啟自動確認
offerbook.cloneOffer=Clone offer (with shared maker fee)
offerbook.clonedOffer.tooltip=This is a cloned offer with shared maker fee transaction ID.\n\Maker fee transaction ID: {0}
offerbook.nonClonedOffer.tooltip=Regular offer without shared maker fee transaction ID.\n\Maker fee transaction ID: {0}
offerbook.cannotActivate.warning=This cloned offer with shared maker fee cannot be activated because it uses the same payment method and currency as another active offer.\n\nYou need to edit the offer and change the payment method or currency or deactivate the offer which has the same payment method and currency.
offerbook.cannotActivateEditedOffer.warning=You can't activate an offer that is currently edited.
offerbook.clonedOffer.info=By cloning an offer one creates a copy of the given offer with a new offer ID but using the same maker fee transaction ID.\n\nThis means there is no extra maker fee needed to get paid and the funds reserved for that offer can be re-used by the cloned offers. This reduces the liquidity requirements for market makers and allows them to post the same offer in different markets or with different payment methods.\n\nAs a consequence if one of the offers sharing the same maker fee transaction is taken all the other offers will get closed as well because the transaction output of that maker fee transaction is spent and would render the other offers invalid. \n\nThis feature requires to use the same trade amount and security deposit and is only permitted for offers with different payment methods or currencies.\n\nFor more information about cloning an offer see: [HYPERLINK:https://bisq.wiki/Cloning_an_offer]
offerbook.timeSinceSigning.help=當您成功地完成與擁有已驗證付款帳户的夥伴交易時,您的付款帳户已驗證。\n{0} 天后,最初的 {1} 的限制解除以及你的賬户可以驗證其他人的付款賬户。
offerbook.timeSinceSigning.notSigned=尚未驗證
offerbook.timeSinceSigning.notSigned.ageDays={0} 天
@ -565,6 +572,7 @@ takeOffer.tac=接受該報價,意味着我同意這交易界面中的條件。
####################################################################
openOffer.header.triggerPrice=觸發價格
openOffer.header.makerFeeTxId=Maker fee
openOffer.triggerPrice=Trigger price {0}
openOffer.triggered=The offer has been deactivated because the market price reached your trigger price.\nPlease edit the offer to define a new trigger price
@ -576,7 +584,14 @@ editOffer.publishOffer=發佈您的報價。
editOffer.failed=報價編輯失敗:\n{0}
editOffer.success=您的報價已成功編輯。
editOffer.invalidDeposit=買方保證金不符合 Bisq DAO 規定,不能再次編輯。
editOffer.openTabWarning=You have already the \"Edit Offer\" tab open.
editOffer.cannotActivateOffer=You have edited an offer which uses a shared maker fee with another offer and your edit made the payment method and currency now the same as that of another active cloned offer. Your edited offer will be deactivated because it is not permitted to publish 2 offers sharing the same maker fee with the same payment method and currency.\n\nYou can edit the offer again at \"Portfolio/My open offers\" to fulfill the requirements to activate it.
cloneOffer.clone=Clone offer
cloneOffer.publishOffer=Publishing cloned offer.
cloneOffer.success=Your offer has been successfully cloned.
cloneOffer.cannotActivateOffer=You have not changed the payment method or the currency. You still can clone the offer, but it will be deactivated and not published.\n\nYou can edit the offer later again at \"Portfolio/My open offers\" to fulfill the requirements to activate it.\n\nDo you still want to clone the offer?
cloneOffer.openTabWarning=You have already the \"Clone Offer\" tab open.
####################################################################
# BSQ Swap offer
@ -604,7 +619,7 @@ portfolio.tab.bsqSwap=Unconfirmed BSQ swaps
portfolio.tab.failed=失敗
portfolio.tab.editOpenOffer=編輯報價
portfolio.tab.duplicateOffer=Duplicate offer
portfolio.context.offerLikeThis=Create new offer like this...
portfolio.tab.cloneOpenOffer=Clone offer
portfolio.context.notYourOffer=You can only duplicate offers where you were the maker.
portfolio.closedTrades.deviation.help=Percentage price deviation from market
@ -1069,6 +1084,8 @@ support.warning.disputesWithInvalidDonationAddress=延遲支付交易已經被
support.warning.disputesWithInvalidDonationAddress.mediator=\n\n您確定一定要關閉糾紛嗎
support.warning.disputesWithInvalidDonationAddress.refundAgent=\n\n您不能進行支付。
support.warning.traderCloseOwnDisputeWarning=Traders can only self-close their support tickets when the trade has been paid out.
support.warning.ticketNotAcknowledged=Ticket not acknowledged.
support.resendTicket=This trader has not acknowledged receipt of the dispute ticket.\nWould you like to re-send the ticket?
support.info.disputedTradeUpdate=Disputed trade update: {0}
####################################################################
@ -1131,6 +1148,7 @@ setting.preferences.dao.resyncFromResources.popup=應用程序重新啟動後,
setting.preferences.dao.resyncFromGenesis.popup=從創始交易中出現同步會消耗大量時間以及 CPU 資源。您確定要重新同步嗎?通常,從最新資源文件進行重新同步就足夠了,而且速度更快。\n\n應用程序重新啟動後Bisq 網絡治理數據將從種子節點重新加載,而 BSQ 同步狀態將從初始交易中重新構建。
setting.preferences.dao.resyncFromGenesis.resync=從創始區塊重新同步並關閉
setting.preferences.dao.isDaoFullNode=以 DAO 全節點運行 Bisq
setting.preferences.dao.processBurningManAccountingData=Process Burningman accounting data
setting.preferences.dao.fullModeDaoMonitor=Full-mode DAO state monitoring
setting.preferences.dao.fullModeDaoMonitor.popup=If full-mode DAO state monitoring is activated the DAO state hashes are created during parsing the BSQ blocks. This comes with considerable performance costs at the initial DAO sync.\n\nFor users who are regularily using Bisq this should not be an issue as there are not many blocks pending for parsing, though for users who only use Bisq casually creating the DAO state hashes for 100s or 1000s of blocks degrades heavily the user experience.\n\nIn case full-mode is deactivated (default) the missing DAO state hashes are requested from network nodes and the DAO state hash based on the most recent block will be created by the user. As all hashes are connected by reference to the previous hash a correct hash at the chain tip means that all past hashes are correct as well. The main functionality of the DAO state monitoring - to detect if the local DAO state is out of sync with the rest of the network - is therefore still fulfilled.
@ -1784,8 +1802,14 @@ dao.burningman.contributorsComboBox.prompt=Select any of my contributors
dao.burningman.daoBalance=Balance for DAO
dao.burningman.daoBalanceTotalBurned=Total amount of burned BSQ
dao.burningman.daoBalanceTotalDistributed=Total amount of distributed BTC / BSQ
dao.burningman.daoBalanceTotalBtcFees=Total amount of BTC fees in BTC / BSQ
dao.burningman.daoBalanceTotalDPT=Total amount of delayed payout transactions BTC / BSQ
dao.burningman.selectedContributor=Selected contributor
dao.burningman.selectedContributor.disabledAccounting=(accounting data not updated)
dao.burningman.selectedContributor.processing=(still processing data...)
dao.burningman.selectedContributorName=Contributor name
dao.burningman.selectedContributorTotalReceived=Total received
dao.burningman.selectedContributorTotalRevenue=Total revenue
dao.burningman.selectedContributorAddress=Receiver address
dao.burningman.shared.table.height=區塊高度
dao.burningman.shared.table.cycle=週期
@ -1812,6 +1836,8 @@ dao.burningman.table.balanceEntry.revenue=Revenue
dao.burningman.table.balanceEntry.price=BSQ/BTC price
dao.burningman.table.balanceEntry.type=類型
dao.burningman.accounting.popup=To display accounting data of a burningman you need to enable the 'process burningman accounting data' option in settings.\nDo you want to do that now?\nIt will require to restart Bisq to apply that change.\n\nIf you cancel, the displayed accounting data are not up-to-date.
# From BalanceEntry.Type enum names
dao.burningman.balanceEntry.type.UNDEFINED=未定義
dao.burningman.balanceEntry.type.BTC_TRADE_FEE_TX=掛單費