Page 1 of 1

Multi-lingual support & globalization

Posted: Thu Mar 06, 2008 1:49 pm
by roberth.risberg
Hi,

We are looking into buying a eCommerce software to be used in several countries in Europe with its base in Sweden.

I have some questions related to the language management and related questions that I hope that you can help me to answer.

1. How can we manage the different languages of the public interface?
We need to be able to add several languages into the site. Do you have any suggestion about how we can handle that (maybe set up a separate table where we keep all keywords)?

2. Currencies
I think that I saw that you have support for different currencies, is that correct?

3. VAT & Customer groups
Do you have support for showing prices with VAT for one group of users and not showing it for another group? (Consumer vs Companies).

4. Dates & Numbers
Do you have support for the asp.net locale system for showing dates and numbers in the local language format?

5. Character set
Do you support the changing of character sets and code pages?

Maybe we can use a similar approach as described in this article?
http://www.codeproject.com/Kb/aspnet/lo ... Takur.aspx

I have been looking around for a good platform for a while now and the AbleCommerce ecom platform looks great and is built on a modern platform. I really hope that we can solve the localization issues!

Thanks in advance

Roberth Risberg
Stockholm, Sweden.

Re: Multi-lingual support & globalization

Posted: Wed May 14, 2008 1:37 pm
by larserik
I have already bought the AbleCommerce shopping cart. However, it doesn't support multiple languages.
I want to translate it into Norwegian. I have tried translating, but it some of it is hidden in DLL files which I don't have the source code to.
Do I need to buy the CommerceBuilder API source in order to change the source code?
Someone, please clarify. :cry: :?:

Re: Multi-lingual support & globalization

Posted: Wed May 14, 2008 4:14 pm
by jmestep
I'm not sure about part of your question, but you can't buy the source code because it's not out yet. We've been waiting.