Transaction

cc6c387789a9df8bbb4e0c7c3f2cc6d1442d1d631e991015bcffa35edef63dea
Timestamp (utc)
2024-03-22 00:35:07
Fee Paid
0.00000027 BSV
(
0.00268300 BSV
-
0.00268273 BSV
)
Fee Rate
10.29 sat/KB
Version
1
Confirmations
97,309
Size Stats
2,623 B

2 Outputs

Total Output:
0.00268273 BSV
  • j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckMB <div class="post">Ok here is the .po file for French. While I'm at it, I noted a couple of issues:<br/><br/>1. The "About" box didn't take the translation into account, it still displays the english version to me, even though the rest of the software is using the translated strings, and the .po file contains the translation string of the "About" box message. Same problem with the "Apply" button in the Settings window.<br/>2. If an transaction's description in the list of transaction in the main window contains a diacritical character (such as "éàèç"), it's not displayed. I suppose the string is not being properly handled as UTF8 somewhere.<br/>3. Some translated strings don't fit in the dialog box anymore (French is a bit more verbose than English). Some cases can be solved by inserting a " ", but that's not always possible (window titles for example).<br/>4. About the .po file :<br/>&nbsp; &nbsp;- There are a few strings in the .po file that don't needs translation (ie: "Bitcoin"). Maybe those shouldn't be inside _("...") ?<br/>&nbsp; &nbsp;- Others shouldn't be split. I can remember one message about transaction fee where the string is split in two to insert the fee value, where you could simply have put a %s. It makes the message harder to translate as I had to go in the source to find exactly what was going on.<br/>&nbsp; &nbsp;- Some strings have whitespace at the end or start, which necessity is very debatable, and it's easy to miss in PoEdit.<br/>&nbsp; &nbsp;- Many strings have all their words capitalized, which just looks strange in French. I checked, none of my other software do it, so I've used normal capitalization everywhere.<br/>&nbsp; &nbsp;- There are a couple message strings that are almost identical, maybe using the same string for each of those messages would be better ? Example : "This is an oversized transaction that requires a transaction fee of %s" and "Error: This is an oversized transaction that requires a transaction fee of %s&nbsp; ". It's the exact same text except for "Error:" at the beginning and an extra space at the end (which is probably useless ?).<br/><br/>Finally, The provided .po file is not up-to-date, as one of the settings string has changed, and is not getting translated (the one about starting Bitcoin at login).<br/><br/>Otherwise Bitcoin seems like a great concept, good work !</div> text/html
    https://whatsonchain.com/tx/cc6c387789a9df8bbb4e0c7c3f2cc6d1442d1d631e991015bcffa35edef63dea