c2c-oerpscenario team mailing list archive

["sraps \(Alistek\)" <709201@xxxxxxxxxxxxxxxxxx>]

@Olivier Dony (OpenERP)

With all my respect, again and again, I have to note, that such changes
should be considered twice, and should be asked a professional tax
consultant. Definitely not decided by a programmer.

To sum it up:
1) Name should be real currency name in English (field translatable), eg. "United States dollar";
2) As we see that "ISO code" is a code, then it should be named "iso_code" or "code". As we had it under the name "code", I prefer latest;
3) Symbol is used inside home country only - for local documents, in any other case you HAVE to use currency code;
4) Anyone being familiar with EU tax authority statements, would add the connection to the countries (you know that one currency can be used by several countries), whom official currency it is;
5) If you would have asked any accountant or manager who is familiar with international trade, you would receive an answer that "$" symbol is being shared among several (not to say numerous) currencies, and it is a great  value difference between them;
>From wikipedia:
http://en.wikipedia.org/wiki/$
/The dollar sign ($), originally called the peso sign, is a symbol primarily used to indicate the various peso and dollar units of currency around the world./

6) Any bank requires an ISO code on any payment order even in homeland
transaction, definitely not something like "$" or "Ls";

So you say that any project needing a common fields, should be adding
them, do you really think so? Any country that would need basic currency
name or correct code, would have to add it? Are you serious, what would
happen to module compatibility?

Why regression, because programmer who deleted this field, just had no
idea about all of this, one even not bothered enough to take the ISO
standard and rename all the currencies according to it.

I am kindly asking, do not disregard this regression!

I am sorry but I will reopen this bug, and will keep doing it until you
get serious.



** Changed in: openobject-addons
       Status: Invalid => Confirmed

-- 
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.
https://bugs.launchpad.net/bugs/709201

Title:
  No "code" field in "res.currency" object

Status in Aeroo Reports for Open ERP:
  Confirmed
Status in OpenERP Modules (addons):
  Confirmed
Status in OpenOffice.org Reporting Engine for OpenObject:
  Confirmed

Bug description:
  There is no code field in the res.currency object, which used to hold
  ISO 4217 (http://en.wikipedia.org/wiki/ISO_4217) code for the
  currency. ISO code is the only referable code for a currency, any
  other name is just user friendly representation and may vary from
  country to country, still they are not official names of the currency.

  Please do not disregard this defect as many modules depend on this
  code do find correct currency in a system.

  This defect is present in whole OpenERP's 6th version branch.