Published on: 2012-08-12T07:59:56+00:00
In a conversation between Wladimir and Geir on August 11th, 2012, they discuss the issue of duplicate strings in translations. Wladimir explains that duplicate strings are not problematic because some strings are used multiple times in the program and may be translated differently based on context. He mentions that Qt translator automatically fills duplicates, while Transifex requires copy and paste. They also discuss using UPnP to map the listening port in bitcoin-qt, with Wladimir forgetting about a compiler flag for this feature.Geir reports that the most common support request he receives at his pool is from users who withdraw coins but cannot see them in their wallet because it is not up-to-date with the block chain. To address this, Wladimir adds a red warning in the balances when the block chain is out of date in version 0.7 of bitcoin-qt to prevent confusion. They also mention that there have been subtle changes made to the English base messages, such as capitalization or punctuation, which can be annoying for translators. However, there is no way to update all translations when the English base message changes without triggering re-translation, and Transifex does not have that option. They note that there were new duplicated strings, but explain that duplicate strings are not a problem since they can be translated differently based on context. Qt translator fills duplicates automatically, while it is unclear if Transifex has the same option.Geir suggests adding a feature to the bitcoin-qt GUI to make it more obvious to users why they can't see new transactions in their wallets. They also discuss the default settings for using UPnP to map the listening port, clarifying that the default depends on compiler flags. They mention that Jeff Garzik proposed a checkpoint release for Bitcoin, noting that there were no major landmark features but several small modifications that would make it useful. Gavin Andresen, one of the core developers, responds that he has no objections to a rc1 happening before he returns from vacation.On August 2, 2012, Jeff Garzik calls for a todo list for version 0.7 of the bitcoin software. Several branches are accepted for inclusion in this version, including addnode optimization and access via RPC, transitioning to requiring block height in block coinbases, making IPv6 support optional again, and getblocktemplate. Other features such as adding a 'mempool' P2P command, extending 'getdata' behavior, and adding prioritisetransaction JSON-RPC method are also deemed appropriate. Testing is still needed for certain features, such as "Child-pays-for-parent / Add transaction fee later" and relaying blocks as a preview before checking transactions. The author also expresses concern that the Bitcoin-Qt client should have a distinct name to avoid confusion with the overall Bitcoin software.Overall, the Bitcoin developers are planning to release a new version of the software soon. The changes are not very significant but aim to create a checkpoint release. Suggestions for improvements include updates to translations, address groupings RPC, extending 'getdata' behavior, addnode optimization, parallelization opportunities, optional IPv6 support, and more. Developers are encouraged to contribute directly to the release notes if they feel there is missing information.
Updated on: 2023-08-01T03:51:57.299873+00:00