RE: [Koha-devel] [Bug 258] New: Budget treats a comma as a period .
Whoops ... Continental Europe uses comma as its decimal separator. Europe (now including the UK) uses SPACE as its thousands separator. As you said, the English-speaking world (ttbomk) uses period as the decimal separator. So the following are all legal representaions of ten thousand 10,000.00 (America) 10 000.00 (Britain) 10 000,00 (Europe) However, when actually using decimals, we Brits tend to use commas for thousands so you are most likely to find either "10 000" or "10,000.00". And I gather that in some places in Europe you are also likely to find "10.000,00" - aaarrgghhhh.... Cheers, Wol -----Original Message----- From: bugzilla-daemon@wilbur.katipo.co.nz [mailto:bugzilla-daemon@wilbur.katipo.co.nz] Sent: 02 April 2003 23:09 To: koha-devel@lists.sourceforge.net Subject: [Koha-devel] [Bug 258] New: Budget treats a comma as a period. http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=258 Summary: Budget treats a comma as a period. Product: Koha Version: 1.9.0 Platform: PC OS/Version: All Status: NEW Severity: normal Priority: P2 Component: Parameters AssignedTo: tonnesen@cmsd.bc.ca ReportedBy: Ilacis@chillco.com QAContact: koha-devel@lists.sourceforge.net /cgi-bin/koha/admin/aqbudget.pl 10,000.00 becomes 10.00 - now I realize that in some countries ten dollars is written as 10,00 so I don't know if that is a translation issue but I believe that all English speaking countries write 10.00 for ten dollars and 10,000.00 for ten thousand. Some sort of validation or direction is necessary though. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact. ------------------------------------------------------- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ _______________________________________________ Koha-devel mailing list Koha-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/koha-devel This transmission is intended for the named recipient only. It may contain private and confidential information. If this has come to you in error you must not act on anything disclosed in it, nor must you copy it, modify it, disseminate it in any way, or show it to anyone. Please e-mail the sender to inform us of the transmission error or telephone ECA International immediately and delete the e-mail from your information system. Telephone numbers for ECA International offices are: Sydney +61 (0)2 9911 7799, Hong Kong + 852 2121 2388, London +44 (0)20 7351 5000 and New York +1 212 582 2333.
Anthony Youngman <Anthony.Youngman@ECA-International.com> wrote:
However, when actually using decimals, we Brits tend to use commas for thousands so you are most likely to find either "10 000" or "10,000.00". And
Brits don't do that if they want to pass their maths qualifications now. Older Brits may be a problem. Maybe we should have gb and gb.afraid-of-change settings? ;-) MJR
On Thu, 3 Apr 2003, MJ Ray wrote:
Anthony Youngman <Anthony.Youngman@ECA-International.com> wrote:
However, when actually using decimals, we Brits tend to use commas for thousands so you are most likely to find either "10 000" or "10,000.00". And
Brits don't do that if they want to pass their maths qualifications now. Older Brits may be a problem. Maybe we should have gb and gb.afraid-of-change settings? ;-)
Well, we may have some additional issues to deal with here, what about currency with no decimel part, or currencies with different kinds of units (do any of these still exist?). Perhaps we need to store currency in two fields (curr_major and curr_minor) with names controlled by (curr_major_name and curr_minor_name). Then we can ask for data to be entered without separators: Please enter the $curr_major_name amount of the fine: ________ Please enter the $curr_minor_name amount of the fine: ________ (Please enter all figures as whole numbers, and without separators.) (or something like that) This may be too much overhead for a problem we don't really need to worry about, but ... -pate
MJR
------------------------------------------------------- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ _______________________________________________ Koha-devel mailing list Koha-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/koha-devel
Pat Eyler <pate@eylerfamily.org> wrote:
Well, we may have some additional issues to deal with here, what about currency with no decimel part, or currencies with different kinds of units (do any of these still exist?). Perhaps we need to store currency in two fields (curr_major and curr_minor) with names controlled by (curr_major_name and curr_minor_name). Then we can ask for data to be
Only two? Why not have a curr_elements linked list table (four elements, called id, unit, amount, next_id) and then enter the id of the highest valued currency unit used in the cost column. The names would be controlled by curr_name, a reference into a chain in the curr_names table describing a linked list of currencies, least valued first and how many of them before we are worth one of the next most highly valued unit. Then koha purchases can handle all currencies, no matter how many units they have in the system. After that, we can add a table that describes the accounting worth of the various things that libraries may barter for fines and purchases. Or maybe we pick one basic unit for each exchange and use decimals relative to them. Your choice ;-) MJR
On Thu, 3 Apr 2003, MJ Ray wrote:
Pat Eyler <pate@eylerfamily.org> wrote:
Well, we may have some additional issues to deal with here, what about currency with no decimel part, or currencies with different kinds of units (do any of these still exist?). Perhaps we need to store currency in two fields (curr_major and curr_minor) with names controlled by (curr_major_name and curr_minor_name). Then we can ask for data to be
Only two? Why not have a curr_elements linked list table (four elements, called id, unit, amount, next_id) and then enter the id of the highest valued currency unit used in the cost column. The names would be controlled by curr_name, a reference into a chain in the curr_names table describing a linked list of currencies, least valued first and how many of them before we are worth one of the next most highly valued unit. Then koha purchases can handle all currencies, no matter how many units they have in the system. After that, we can add a table that describes the accounting worth of the various things that libraries may barter for fines and purchases.
Isn't this a bit overkill? Is there anyone who still uses three or more units of currency? IMHO the most sensible thing to do is to use an integer, recording the number of smallest-valued units of currency (cents, pence, centimes, halala, rubber ningis, or whatever). Heck, that'd even work with pre-decimalisation L.S.d in the UK. -- Andrew Arensburger Actually, these _do_ represent the arensb@ooblick.com opinions of ooblick.com! Generic Tagline V 6.01
participants (4)
-
Andrew Arensburger -
Anthony Youngman -
MJ Ray -
Pat Eyler