Saturday 22 December 2012

Internationalisation! ( -zation?)

Like almost all of my software, I wrote Organise to fill my own needs and still use it heavily myself.

Occasionally someone has contacted me about problems with calculations if their system preferences are set to format numbers differently from here in the UK (for example, if they're in a country using a comma as a decimal separator and dot '.' as a thousand separator).



But I've never gone through the app and made sure that Organise works perfectly regardless of user number formats. The same thing applies to the sales tax rate (for example, Canada apparently has three different taxes, which Organise hasn't been able to handle).

I had a wake-up call when Organise was put on offer on a popular download site recently. Why people buy software without taking advantage of a free trial I don't know, but they apparently do, and it's very awkward when they find that it doesn't work for them.

It has been a tough task. The code behind Organise is vast now and there are many places where it makes calculations and needs to take account of the user's choice of number format. But I'm just about there.

And to complete a truly international version (version 6!), I've also tried to add the flexibility that's needed for folks to calculate their sales tax wherever they are. Defaults are in line with the UK rules, but as you can see here it's now as customisable as I think it needs to be.
I hope to have a release candidate ready for download in the new year.

2 comments:

  1. There's a whole branch of translation that deals with this sort of issue: localisation. On one level it's about making sure your copy is suitable for the target market. And on another, more technical, level it's about software, website metadata, and so on.
    There's so much involved in internationalisation!

    ReplyDelete
  2. Thanks for your comment Marian. I'm only dealing with more technical and functional issues here; making sure my software is usable by English speakers in other countries. Translation of the interface and documentation into other languages is a whole other kettle of fish!

    I receive regular offers from people who want to provide translation, and I have released my apps in other languages in the past.

    But I've made a deliberate decision not do do this any more. I know I'm limiting my audience to English speakers but providing even one other language means more work - making changes in two different places and testing twice, and I can't make even a small change without speaking to a translator and getting an answer back. Sadly these are all barriers.

    ReplyDelete