Re: [Bitcoin-development] Version 0.7 release planning
Geir, There were a lot of subtle changes to the English base messages such as capitalization or punctuation, I know this is pretty annoying for translators. It is a pity that there is no way to update all translations when the English base message changes but not significantly enough to trigger re-translation. I've looked but Transifex does not have that option. Also there were new duplicated strings: > > "Verify a message to ensure it was signed with a specified Bitcoin address" > "Sign a message to prove you own a Bitcoin address" > "Clear &All" > Duplicate strings are not a problem. Some strings are used multiple times in the program, and thus appear multiple times in the translation. This is because there are cases in which a string that is the same in English is translated differently in another language based on the context. At least Qt translator fills duplicates in automatically, with the option to change them if desired. I'm not sure about Transifex but I've heard it's the same there. > > These two seem odd: > Use UPnP to map the listening port (default: 0) > Use UPnP to map the listening port (default: 1 when listening) > The default depends on compiler flags, hence the two messages. I suppose the message could be split up, so that "Use UPnP to map the listening port" is factored out. Let's do this after 0.7.0 release though, otherwise all the translations for those messages will be broken again. There should be no more message changes before the release unless there is a very good reason. Wladimir -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
Re: [Bitcoin-development] Version 0.7 release planning
By the way, by far the most common support request I have at my pool is > users withdrawing coins and not seeing it in their wallet because it's > not up-to-date with the block chain. Might be worth adding something in > the bitcoin-qt GUI to make it more obvious that users can't see new > transactions and why. > For 0.7 we've added a red "(out of sync)" warning to the balances when the block chain is out of date. However, due to the design of the protocol there is a large variance in block timings, and it is not possible to determine up-to-date status with certainty, so quite a large safety margin is used. To be precise the warning is shown when the last received block was generated more than 90 minutes ago. Wladimir -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
Re: [Bitcoin-development] Version 0.7 release planning
On Saturday, August 11, 2012 4:43:28 PM Geir Harald Hansen wrote: > By the way, by far the most common support request I have at my pool is > users withdrawing coins and not seeing it in their wallet because it's > not up-to-date with the block chain. Might be worth adding something in > the bitcoin-qt GUI to make it more obvious that users can't see new > transactions and why. Bitcoin-Qt even delays showing generation until 2 confirms. > These two seem odd: > Use UPnP to map the listening port (default: 0) > Use UPnP to map the listening port (default: 1 when listening) The default depends on build options, so that should be correct. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
Re: [Bitcoin-development] Version 0.7 release planning
On 02.08.2012 18:43, Jeff Garzik wrote: > There seems to be consensus that we should go ahead and do a release, > before leveldb or ultraprune or anything major lands. There is no > major landmark feature, but just a useful collection of small changes. > It seems like a good time to Release Early, Release Often and make a > checkpoint release. Looks like much goodness in this version. Thanks for all this work. Any chance that options to limit the size of blocks and prioritize paid vs free txes could make it in? By the way, by far the most common support request I have at my pool is users withdrawing coins and not seeing it in their wallet because it's not up-to-date with the block chain. Might be worth adding something in the bitcoin-qt GUI to make it more obvious that users can't see new transactions and why. > 2) Translations update 2012-08-01 (fetched from Transifex) I just now updated the Norwegian translation on Transifex, if you'd like to do another pull before the release. For some reason there were many strings I had already translated that now had no translation and had to be done again (even ones that had the same English text). Many languages are now only about 50% translated. Also there were new duplicated strings: "Verify a message to ensure it was signed with a specified Bitcoin address" "Sign a message to prove you own a Bitcoin address" "Clear &All" These two seem odd: Use UPnP to map the listening port (default: 0) Use UPnP to map the listening port (default: 1 when listening) Regards, Geir H. Hansen, bitminter.com -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
