Public/monero-gui
1
0
Fork 1
mirror of https://github.com/monero-project/monero-gui.git synced 2026-04-19 13:27:27 -04:00
Code Issues Packages Projects Releases Wiki Activity

Rename "blackball" for clarity

Browse Source 
Apparently some people seem to think it's a censorship list...
This commit is contained in:
moneromooo-monero
2018-10-18 19:44:13 +01:00
parent 7615b86ac7
commit 9a09e6189b
37 changed files with 280 additions and 280 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
translations/monero-core_da.ts
View File

@@ -1331,7 +1331,7 @@ The old wallet cache file will be renamed and can be restored later.
<message>
<location filename="../pages/SharedRingDB.qml" line="119"/>
<location filename="../pages/SharedRingDB.qml" line="121"/>
<source>Blackballed outputs</source>
<source>Outputs marked as spent</source>
<translation>Blacklistet outputs</translation>
</message>
<message>
@@ -1342,8 +1342,8 @@ The old wallet cache file will be renamed and can be restored later.
</message>
<message>
<location filename="../pages/SharedRingDB.qml" line="122"/>
<source>In order to obscure which inputs in a Monero transaction are being spent, a third party should not be able to tell which inputs in a ring are already known to be spent. Being able to do so would weaken the protection afforded by ring signatures. If all but one of the inputs are known to be already spent, then the input being actually spent becomes apparent, thereby nullifying the effect of ring signatures, one of the three main layers of privacy protection Monero uses.&lt;br&gt;To help transactions avoid those inputs, a list of known spent ones can be used to avoid using them in new transactions. Such a list is maintained by the Monero project and is available on the getmonero.org website, and you can import this list here.&lt;br&gt;Alternatively, you can scan the blockchain (and the blockchain of key-reusing Monero clones) yourself using the monero-blockchain-blackball tool to create a list of known spent outputs.&lt;br&gt;</source>
<translation>For at skjule hvilke inputs i en Monero transaktion bliver brugt, så skal en tredje part ikke kunne sige hvilke inputs i en ring allerede er kendt for at blive brugt. Hvis en kan det ville det svække beskyttelsen der er fra ring signature. Hvis alle undtagen en af inputne er kendt for alle at være brugt, så bliver den ene input der faktisk bliver brugt synlig, og derved fjerner alt beskyttelse fra ring signature, som er et af de tre beskyttende lag Monero bruger.&lt;br&gt;For at hjælpe transaktioner med at undgå disse inputs, kan en liste af kendte brugte inputs blive brugt for at undgå at bruge dem i nye transaktioner. Sådan en liste bliver vedligeholdt af Monero projektet og er tilgængelig på getmonero.org hjemmesiden, og du kan importere denne liste her.&lt;br&gt;Alternativt kan du scanne blockchainen (og blockchainen fra de Monero kloner der genbruger nøglerne) selv ved brug af monero-blockchain-blackball værktøjet for at oprette en liste over kendte brugte outputs.&lt;br&gt;</translation>
<source>In order to obscure which inputs in a Monero transaction are being spent, a third party should not be able to tell which inputs in a ring are already known to be spent. Being able to do so would weaken the protection afforded by ring signatures. If all but one of the inputs are known to be already spent, then the input being actually spent becomes apparent, thereby nullifying the effect of ring signatures, one of the three main layers of privacy protection Monero uses.&lt;br&gt;To help transactions avoid those inputs, a list of known spent ones can be used to avoid using them in new transactions. Such a list is maintained by the Monero project and is available on the getmonero.org website, and you can import this list here.&lt;br&gt;Alternatively, you can scan the blockchain (and the blockchain of key-reusing Monero clones) yourself using the monero-blockchain-mark-as-spent tool to create a list of known spent outputs.&lt;br&gt;</source>
<translation>For at skjule hvilke inputs i en Monero transaktion bliver brugt, så skal en tredje part ikke kunne sige hvilke inputs i en ring allerede er kendt for at blive brugt. Hvis en kan det ville det svække beskyttelsen der er fra ring signature. Hvis alle undtagen en af inputne er kendt for alle at være brugt, så bliver den ene input der faktisk bliver brugt synlig, og derved fjerner alt beskyttelse fra ring signature, som er et af de tre beskyttende lag Monero bruger.&lt;br&gt;For at hjælpe transaktioner med at undgå disse inputs, kan en liste af kendte brugte inputs blive brugt for at undgå at bruge dem i nye transaktioner. Sådan en liste bliver vedligeholdt af Monero projektet og er tilgængelig på getmonero.org hjemmesiden, og du kan importere denne liste her.&lt;br&gt;Alternativt kan du scanne blockchainen (og blockchainen fra de Monero kloner der genbruger nøglerne) selv ved brug af monero-blockchain-mark-as-spent værktøjet for at oprette en liste over kendte brugte outputs.&lt;br&gt;</translation>
</message>
<message>
<location filename="../pages/SharedRingDB.qml" line="143"/>
@@ -1357,7 +1357,7 @@ The old wallet cache file will be renamed and can be restored later.
</message>
<message>
<location filename="../pages/SharedRingDB.qml" line="156"/>
<source>Please choose a file to load blackballed outputs from</source>
<source>Please choose a file from which to load outputs to mark as spent</source>
<translation>Vælg venligst en fil til at loade blacklistede outputs fra</translation>
</message>
<message>
@@ -1367,7 +1367,7 @@ The old wallet cache file will be renamed and can be restored later.
</message>
<message>
<location filename="../pages/SharedRingDB.qml" line="174"/>
<source>Filename with outputs to blackball</source>
<source>Filename with outputs to mark as spent</source>
<translation>Filnavn med outputs der skal blacklistes</translation>
</message>
<message>
@@ -1382,17 +1382,17 @@ The old wallet cache file will be renamed and can be restored later.
</message>
<message>
<location filename="../pages/SharedRingDB.qml" line="214"/>
<source>Or manually blackball/unblackball a single output:</source>
<source>Or manually mark a single output as spent/unspent:</source>
<translation>Eller manuelt fjern/tilføj et blacklistet enkelt output:</translation>
</message>
<message>
<location filename="../pages/SharedRingDB.qml" line="238"/>
<source>Blackball</source>
<source>Mark as spent</source>
<translation>Blacklist</translation>
</message>
<message>
<location filename="../pages/SharedRingDB.qml" line="247"/>
<source>Unblackball</source>
<source>Mark as unspent</source>
<translation>Whitelist</translation>
</message>
<message>