Yea but it is in the case of merchant installing french language, i dont see it reworking all french zones to have correct ones. It will take a too long time and french zones list will be ID-different for each merchant.

For the list itself, see [url-http://en.wikipedia.org/wiki/ISO_3166-2:FR]ISO 3166-2:FR[/url].Im just thinking about a system (composite primary key) to have all zones sequentialy grouped per country, and not chunks added at end of table in disorder.Need some testing with composite keys.

When building a language extension, should i do also translate the 250 countries and 4000 zones names ?And when installing a new language, why the new descriptions of categories, products, options, status, .... stay empty, the english desc is not copied inside ?Does the merchant have to edit/add all that manually each time he installs a new language ?

When building a language extension, should i do also translate the 250 countries and 4000 zones names ?

Hello. Basically Yes, you need to translate if all needed. Countries and Zones are more related to content like products, categories etc.. so if you have 100 products in english you need to translate them to your language - same with Countries and Zones

And when installing a new language, why the new descriptions of categories, products, options, status, .... stay empty, the english desc is not copied inside ?

To copy all descriptions from English please use Load missing (not translated) language data AbanteCart feature. Go to Admin-System-Localization-Languages and click to edit your language select Source Language to copy from and click Load button.

please note: instead of copy there is 'google translate' text translation method. to use it install paid extension Google Translate API 2 available on AbanteCart Extension Store. With use of google translate API 2 service (not free) you can automatically translate all your text in the shopping cart to any language that you have installed.

On 1.1.9, install Spanish and Russian, the country and zone description stay always empty when content language is not english, even with translations loaded in DB.Same thing for my french descs, do not appear (cache cleared, language settings tried all positions).

I have also put pull request on github for missing countries and zones.Im expecting this to be in place with new ISO-correct usable french zones for 1.2.0

On 1.1.9, install Spanish and Russian, the country and zone description stay always empty when content language is not english, even with translations loaded in DB.Same thing for my french descs, do not appear (cache cleared, language settings tried all positions).

I have also put pull request on github for missing countries and zones.Im expecting this to be in place with new ISO-correct usable french zones for 1.2.0

Have tested 1.2.0.alpha and was really impressed by the very good level of the product.No errors at install and in usage.

On install step 4, the button continue can be confusing as the progress bar stay a long time at end, the user asking if he must click on it or not.

Also my biggest problem is always with french zones which are old and incorrect.A correction would need to shift all next IDs to keep the sequence ordered by country(This could happen with other countries)A solution would be to keep 1000 positions per country in the zone ID sequence:Eg: for country_id=74, reserving zone_id from 74000 to 74999so that each country could change its zones without shifting the others.

As long as these incorrect zones stay there, the software is unusable except for US.I dont see merchants doing adjustments by hand as each will have different french zone_id depending of the order they inserted them.

Personnaly, I stopped my translation as it was becomming a long nightmare.I suppose the same reason for the other translators.

Also my biggest problem is always with french zones which are old and incorrect.A correction would need to shift all next IDs to keep the sequence ordered by country(This could happen with other countries)A solution would be to keep 1000 positions per country in the zone ID sequence:Eg: for country_id=74, reserving zone_id from 74000 to 74999so that each country could change its zones without shifting the others.

As long as these incorrect zones stay there, the software is unusable except for US.I dont see merchants doing adjustments by hand as each will have different french zone_id depending of the order they inserted them.