openerp-expert-localization team mailing list archive

["Nhomar Hernandez \(Vauxoo\)" <question216251@xxxxxxxxxxxxxxxxxxxxx>]

Question #216251 on OpenERP Addons changed:
https://answers.launchpad.net/openobject-addons/+question/216251

    Status: Answered => Open

Nhomar Hernandez (Vauxoo) is still having a problem:
Hello.

After talk with other community members, and after read several
comments, some points come out.

1.- Use l10n_xx to load data for states is a wrong a dirty solution, it make us install a COA that we will not need.
2.- Some l10n_xx modules have already data for states, until now it has been good, but not well documented and even we see this data just until now.
3.- ONE module that ask for the country you want to load states is good enought.
4.- This module can be feeded from some generic origin of data, BTW some options come, we have until now just one, but for ca it is buggy, i think we need more options.
5.- We have already data for something like 20 countries, someones already in core (a bzr "mv" solve the problem) and other ones in some community branches.
6.- The best option here is load data in english and manage translations : i.e. l10n_cn has data in chinese, it is incorrect from some points of view, the state name must be managed from translations, BTW there are just 20 or 50 states per country, It is not to much dadta to translate.
7.- Some members of community offered build the module.
8.- Other members offered audit them own countrys, with just a good policy about data format is enought i think, to avoid csv mixed with xml or yaml.
9.- IMHO it can be a base module with the server (like translations), but a module base_data_states is enought.
10.- It can be a the first step to other thing deeper, like lower level country divisions,but this is other history [not for this topic, i think we must go step by step].
11.- In migrations, (info for openerp and other community migration plataforms) you just need to manage the no-load for this data in old databases because probably every company solved in differents ways this things.

Then, We estimate 4 hours to build the base_data_states module, we can
start with it, i just need the opinion from OpenERP R&D team to be sure
it will be merged, or the official opinion of it will not to manage our
own way to do thing in community, both answers should be cool, BTW
probably introduce a new feature like this just before the release they
can consider dangerous and we can expect the merge for next release too.

This module estrategically will be signed by us as:

Author: "Openerp Community"

We will not sign as Vauxoo, because we will make just the base and VE -
MX - CO states, and copy the actual ones we find in the community.

If Odony or Fpopnerp has some different opinion or think the actual
platform has some better solution we are all eyes to read.

Regards and thanks for the feedback.

-- 
You received this question notification because you are a direct
subscriber of the question.