Transaction

89a271e69ca4638413df5f27c07d2fb88da37b520f9eef63ffa475679dee2ec3
Timestamp (utc)
2024-03-21 23:43:14
Fee Paid
0.00000014 BSV
(
0.00330591 BSV
-
0.00330577 BSV
)
Fee Rate
10.45 sat/KB
Version
1
Confirmations
97,498
Size Stats
1,339 B

2 Outputs

Total Output:
0.00330577 BSV
  • j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckM><div class="post"><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=867.msg10226#msg10226">Quote from: BioMike on August 19, 2010, 08:05:18 AM</a></div><div class="quote">WxWidgets is not really a problem. My problem is the version that is used (2.9), which is considered unstable by many distro packagers (although the WxWidgets devs say it isn't). On the other side, as far as I know WxWidgets uses gtk under Linux for drawing the whole stuff and makes it for the bitcoins devs easy to make things cross platform.<br/></div>wxWidgets 2.9 is their first UTF-8 version.&nbsp; We are UTF-8 on all platforms including Windows.<br/><br/>The distro packages of 2.8 are UTF-16, so they just trip people up.&nbsp; People had endless build problems with 2.8 and its wxString UTF-16/ANSI conditional build options until we standardized on 2.9.&nbsp; Also, to use 2.8, we were using ANSI, which was just a temporary stopgap until wxWidgets supported UTF-8.<br/><br/>This is a problem that will solve itself.&nbsp; With time, 2.9 will become a more mainline release.</div> text/html
    https://whatsonchain.com/tx/89a271e69ca4638413df5f27c07d2fb88da37b520f9eef63ffa475679dee2ec3