|
Title: Armory i18n (internationalisation) Post by: knahrvorn on August 19, 2015, 07:56:50 AM By chance I discovered this folder in Github today: https://github.com/etotheipi/BitcoinArmory/tree/master/po (https://github.com/etotheipi/BitcoinArmory/tree/master/po), containing what looks like code for handling i18n of Armory, along with a single (partly finished) localised/translated file in Icelandic.
Is this finished work? If so, I'd be happy to contribute a Danish localisation of Armory. Title: Re: Armory i18n (internationalisation) Post by: goatpig on August 19, 2015, 10:04:51 AM Ask njaard
Title: Re: Armory i18n (internationalisation) Post by: unamis76 on August 19, 2015, 10:55:41 AM Page isn't there anymore. If needed I'd also like to contribute to internationalization.
Title: Re: Armory i18n (internationalisation) Post by: knahrvorn on August 19, 2015, 11:11:18 AM Page isn't there anymore. Sorry, I must have messed up when copy/pasting the link. Should work now.Title: Re: Armory i18n (internationalisation) Post by: doug_armory on August 19, 2015, 02:53:12 PM The work isn't finished. Long story short, the ideal solution is to upgrade the Armory codebase to Python 3, which has much better internationalization/Unicode support. It's far more difficult under Python 2, and prone to weird bugs too. IIRC, we had one translation (Icelandic?) we tried sticking in. We found that it broke a lot of our code and had to abandon it.
The aforementioned Python 3 upgrade is something that must come sooner or later. The question is when exactly we will make the jump. It definitely won't be in time for 0.94. Honestly, I'd be surprised if anything is released before the year's out, but that's just a personal opinion, not official policy. I've been surprised before. :) Title: Re: Armory i18n (internationalisation) Post by: unamis76 on August 20, 2015, 09:00:17 PM Page isn't there anymore. Sorry, I must have messed up when copy/pasting the link. Should work now.Thanks, it works now :) The work isn't finished. Long story short, the ideal solution is to upgrade the Armory codebase to Python 3, which has much better internationalization/Unicode support. It's far more difficult under Python 2, and prone to weird bugs too. IIRC, we had one translation (Icelandic?) we tried sticking in. We found that it broke a lot of our code and had to abandon it. The aforementioned Python 3 upgrade is something that must come sooner or later. The question is when exactly we will make the jump. It definitely won't be in time for 0.94. Honestly, I'd be surprised if anything is released before the year's out, but that's just a personal opinion, not official policy. I've been surprised before. :) All right... I'll probably be around when a transition happens :D I bet that there are many users who would be willing to help on translations for several languages... Title: Re: Armory i18n (internationalisation) Post by: doug_armory on August 20, 2015, 09:55:56 PM All right... I'll probably be around when a transition happens :D I bet that there are many users who would be willing to help on translations for several languages... Thanks. I'm sure we'll get the word out once we're ready to handle translations. :) Title: Re: Armory i18n (internationalisation) Post by: Muhammed Zakir on August 22, 2015, 11:43:48 AM The work isn't finished. Long story short, the ideal solution is to upgrade the Armory codebase to Python 3, which has much better internationalization/Unicode support. It's far more difficult under Python 2, and prone to weird bugs too. IIRC, we had one translation (Icelandic?) we tried sticking in. We found that it broke a lot of our code and had to abandon it. The aforementioned Python 3 upgrade is something that must come sooner or later. The question is when exactly we will make the jump. It definitely won't be in time for 0.94. Honestly, I'd be surprised if anything is released before the year's out, but that's just a personal opinion, not official policy. I've been surprised before. :) Are you planning to support compressed public keys when upgrading to Python 3? Congrats for becoming Sr. Member, btw! ;) Title: Re: Armory i18n (internationalisation) Post by: goatpig on August 22, 2015, 11:46:52 AM Are you planning to support compressed public keys when upgrading to Python 3? That's part of the new wallets, not the Py3 upgrade. Title: Re: Armory i18n (internationalisation) Post by: Muhammed Zakir on August 22, 2015, 11:52:13 AM Are you planning to support compressed public keys when upgrading to Python 3? That's part of the new wallets, not the Py3 upgrade. Okay! Thanks. Waiting for it for a long time! :) Title: Re: Armory i18n (internationalisation) Post by: goatpig on August 22, 2015, 12:53:33 PM I know, sry =(
Title: Re: Armory i18n (internationalisation) Post by: Carlton Banks on August 22, 2015, 01:11:23 PM I know, sry =( You didn't do anything wrong. Apology not accepted ;) Title: Re: Armory i18n (internationalisation) Post by: Muhammed Zakir on August 22, 2015, 03:39:04 PM I know, sry =( Is it possible for you to tell an ETA? You didn't do anything wrong. Apology not accepted ;) +1. I agree. Title: Re: Armory i18n (internationalisation) Post by: goatpig on August 22, 2015, 03:51:11 PM Is it possible for you to tell an ETA? I have not worked on that branch at all so I can't really tell. I may implement a wallet consistency check for the new format in the coming weeks so I'll know more then. I know the branch passes the current unit tests but I don't know by how much retro compatibility and GUI integration has progressed. |