[Koha-bugs] [Bug 12310] Decimal separators issues in patrons payments/fines

bugzilla-daemon at bugs.koha-community.org bugzilla-daemon at bugs.koha-community.org
Fri Jun 1 12:19:14 CEST 2018


https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12310

Marcel de Rooy <m.de.rooy at rijksmuseum.nl> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|Signed Off                  |Failed QA

--- Comment #95 from Marcel de Rooy <m.de.rooy at rijksmuseum.nl> ---
Preliminary QA:

Very brave to take this upon you !

Tiny suggestion:
.decimal-unformating
Fix spelling please. At least t => tt but what is decimal unformat btw? Better
name? Something with normalize or so??

I have the feeling that DecimalSeparators and CurrencyFormat don't really
harmonize. And yes, I can understand how problematic making changes in this
area must be..

So thousands separators come at the expense of handling both dots and commas.
Still opt for something that is more understandable.

The number of changes to be expected here would be much larger. You actually
use the new js formatting in three acq templates.
What about things like:
C4/Biblio.pm:                $subfield_value =~ s/\./,/ if
C4::Context->preference("CurrencyFormat") eq "FR";
acqui/addorderiso2709.pl:                        $price =~ s/\./,/ if
C4::Context->preference("CurrencyFormat") eq "FR";
acqui/addorderiso2709.pl:                $price =~ s/\./,/ if
C4::Context->preference("CurrencyFormat") eq "FR";
Koha/Number/Price.pm
    $format_params = {
        %$format_params,
        int_curr_symbol   => '',
        mon_thousands_sep => '',
        mon_decimal_point => '.',
    };
koha-tmpl/intranet-tmpl/prog/en/includes/format_price.inc
    [% IF Koha.Preference("CurrencyFormat") == 'FR' %]
        var default_value = {
            thousands_sep: ' ',
            decimal_point: ',',
            decimal_digits: 2
        };
And this is just to name a few; the list could probably be larger when
searching harder.
It might be impossible to make global changes but the risk of this is adding
just another approach in a few places and leaving Koha even more fragmented on
the subject?

Changing state for need of feedback or adjustments.

-- 
You are receiving this mail because:
You are watching all bug changes.


More information about the Koha-bugs mailing list