You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For use in Europe, it would greatly appreciate if, instead of the decimal point, a decimal comma could be used as an option.
I can imagine this is a bit more of programming on the input side, but maybe it is easier to substitute it in the output side (which would already be great). Currently, I have to substitute one for the other in a text processor before printing. But that might also substitute full stops in comments, or other uses of the the point char. So this workaround is neither a comfortable nor reliable.
The text was updated successfully, but these errors were encountered:
Hi! It is not possible to do it for the input, but for the output - no problem.
We can add this as an option, but until then, you can easily customize your Calcpad to do that. Download the file bellow and unzip "template.html" in your c:\Program Files\Calpcad\doc folder. Replace the old one. template.zip
Also, you can add the following lines in your "template.html" just after $(document).ready(function () {:
$(".eq").each(function () {
var s = $(this).html().replace(".", ",");
$(this).html(s);
});
This will replace all decimal points in equations with commas, but not in the other text.
The fix does exactly what I needed: sparing me from parsing the output. So that solves the main problem. Also thanks for working on an easy customization option for all users.
I do understand that making the input side of the interpreter configurable is more challenging. And writing a point instead of a comma is something one can easily get used to.
For use in Europe, it would greatly appreciate if, instead of the decimal point, a decimal comma could be used as an option.
I can imagine this is a bit more of programming on the input side, but maybe it is easier to substitute it in the output side (which would already be great). Currently, I have to substitute one for the other in a text processor before printing. But that might also substitute full stops in comments, or other uses of the the point char. So this workaround is neither a comfortable nor reliable.
The text was updated successfully, but these errors were encountered: