Armory i18n (internationalisation) | Bitcointalksearch.org

goatpig

legendary

Activity: 3738

Merit: 1360

Armory Developer

Quote from: Muhammed Zakir on August 22, 2015, 11:39:04 AM

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.

Muhammed Zakir

hero member

Activity: 560

Merit: 509

I prefer Zakir over Muhammed when mentioning me!

Quote from: goatpig on August 22, 2015, 08:53:33 AM

I know, sry =(

Is it possible for you to tell an ETA?

Quote from: Carlton Banks on August 22, 2015, 09:11:23 AM

You didn't do anything wrong. Apology not accepted Wink

+1. I agree.

Carlton Banks

legendary

Activity: 3430

Merit: 3079

Quote from: goatpig on August 22, 2015, 08:53:33 AM

I know, sry =(

You didn't do anything wrong. Apology not accepted Wink

goatpig

legendary

Activity: 3738

Merit: 1360

Armory Developer

I know, sry =(

Muhammed Zakir

hero member

Activity: 560

Merit: 509

I prefer Zakir over Muhammed when mentioning me!

Quote from: goatpig on August 22, 2015, 07:46:52 AM

Quote from: Muhammed Zakir on August 22, 2015, 07:43:48 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!

goatpig

legendary

Activity: 3738

Merit: 1360

Armory Developer

Quote from: Muhammed Zakir on August 22, 2015, 07:43:48 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.

Muhammed Zakir

hero member

Activity: 560

Merit: 509

I prefer Zakir over Muhammed when mentioning me!

Quote from: doug_armory on August 19, 2015, 10:53:12 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! Wink

doug_armory

sr. member

Activity: 255

Merit: 250

Senior Developer - Armory

Quote from: unamis76 on August 20, 2015, 05:00:17 PM

All right... I'll probably be around when a transition happens Cheesy

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.

unamis76

legendary

Activity: 1512

Merit: 1012

Quote from: knahrvorn on August 19, 2015, 07:11:18 AM

Quote from: unamis76 on August 19, 2015, 06:55:41 AM

Page isn't there anymore.

Sorry, I must have messed up when copy/pasting the link. Should work now.

Thanks, it works now

Quote from: doug_armory on August 19, 2015, 10:53:12 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.

All right... I'll probably be around when a transition happens Cheesy

I bet that there are many users who would be willing to help on translations for several languages...

doug_armory

sr. member

Activity: 255

Merit: 250

Senior Developer - Armory

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.

knahrvorn

newbie

Activity: 58

Merit: 0

Quote from: unamis76 on August 19, 2015, 06:55:41 AM

Page isn't there anymore.

Sorry, I must have messed up when copy/pasting the link. Should work now.

unamis76

legendary

Activity: 1512

Merit: 1012

Page isn't there anymore. If needed I'd also like to contribute to internationalization.

goatpig

legendary

Activity: 3738

Merit: 1360

Armory Developer

Ask njaard

knahrvorn

newbie

Activity: 58

Merit: 0

By chance I discovered this folder in Github today: 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.

Topic: Armory i18n (internationalisation) (Read 1035 times)