Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Decimal comma #6

Open
hgeorgsch opened this issue Oct 25, 2019 · 5 comments
Open

Decimal comma #6

hgeorgsch opened this issue Oct 25, 2019 · 5 comments
Assignees
Labels
bug Something isn't working

Comments

@hgeorgsch
Copy link

STACK does not accept decimal comma for floating point numbers, only the decimal point. This is uncontroversial as long as the code written is maxima code.
Introducing the WYSIWYG interface, the student should be writing in the same language and notation as the question is phrased in, and the decimal comma is used in most languages.
Ideally, decimal comma should be used in both input and output depending on the student's language setting. For most purposes, however, it would suffice to let tex2max translate the decimal comma into a decimal point.

@hgeorgsch hgeorgsch added the bug Something isn't working label Oct 25, 2019
@andstor
Copy link
Member

andstor commented Oct 27, 2019

I have created an issue in tex2max: KQMATH/tex2max#50.

@andstor andstor self-assigned this Oct 27, 2019
@andstor
Copy link
Member

andstor commented Oct 27, 2019

The logic in TeX2Max has now been resolved. I will shortly make a new TeX2Max release and then update Stack.

@hgeorgsch
Copy link
Author

Is this completed?
Does it, BTW, depend on language settings?

@andstor
Copy link
Member

andstor commented Jun 4, 2020

No, the release is still pending, and the logic needs to be implemented in STACK 😅

In the new version, TeX2Max allows both point and comma signs (although, it's configurable). The output is transpiled to points, as Maxima only supports point symbols. It should therefore be straight forward to just update the TeX2Max scripts in STACK.

By supporting both types, I don't think it's necessary to depend on language settings... Or?

@hgeorgsch
Copy link
Author

Probably not. As long as nobody comes up with problems where comma is used for something else, we should be safe.

For consistency, it would be an advantage to only accept comma for language which really use comma, as that is what is done in the calculated qtype. This is low priority though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants