numeric values in authoring should support locale decimal separator

Fixed the discount point.

Validation error only happens with discount values. Probably, applying the same solution that the one to points will work.

may help

Hi. As said we have investigate this issue in evaluation in SAK-8643. Solution was very simple.

It was a javascript function that changes comma by point
------------------------------------------------------------------------------------------------------ function toPoint(id)
{
var x=document.getElementById(id).value
document.getElementById(id).value=x.replace(',','.')
}
------------------------------------------------------------------------------------------------------

And in each "numeric" jsp inputText tag we must add this:
------------------------------------------------------------------------------------------------------ onchange="toPoint(this.id)"
------------------------------------------------------------------------------------------------------

Sample:
<h:inputText value="#{description.totalOverrideScore}" size="5" id="adjustTotal3" required="false" rendered="#{totalScores.anonymous eq 'false' || description.assessmentGradingId ne '-1'}" onchange="toPoint(this.id)">

It solves the problem of validation. Then float values are stored correctly in database. If code reads float values from database as float values there is not any trouble. The trouble only can happen if a float value is readed as a string. In that case solution is easy too:

Sample: We have a string variable called totalAutoScore:
------------------------------------------------------------------------------------------------------ if (totalAutoScore!= null){
totalAutoScore.replace(',', '.'), "0");
}
------------------------------------------------------------------------------------------------------ We can do this in setters and getters...

This is all the work to do. If we are in a system that uses points... all this code really does nothing. If have a system "with commas", this code traslates always commas to point.

I would say not "instead" but potentially "in addition" and wouldn't that make it a feature request, not a bug? This seems like one little piece under a broader internationalization effort. Diego has done a big part by adding i18n support (), but what else is there? I have no idea, not in my expertise. Maybe Diego would know?
-mARC