-
Notifications
You must be signed in to change notification settings - Fork 99
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
Updated the Conversion spelling #332
Conversation
… and converted all fraction to decimals into a division.
…last column was Yes/No not a number. Other bug fixes in the ismixed sections
# Conflicts: # assessment/libs/simplex.php
…ile to choose the spelling by detecting the browser language.
I hope I did this correctly this time. If not message me in WAMAP so I can fix this. Thanks. Mike |
Why? The gettext I'm also concerned with displaying the British spelling for the units here, when the units handling code for number questions only handles the US spelling. |
…plexcreatelatexinequalities to return the latex version of the objective and constraints.
Updated the function to use the gettext() _ function from a function at the top of the file (conversion). Added simplexcreatelatexinequalities in the simplex and updated the simplex html |
Your original code had already used _ for localization, so I'm still confused what problem this change is trying to solve. |
Also, I just realized that gettext is based on server-declared language, so can't adapt to the client's language preference like you were trying to do here. If your goal is for the same server to deliver both spellings, it might be necessary to go back to your original model, but with gettext used on the fallback case to account for other languages. |
I had a request that deca be spelled deka as that was the way it was done
in Ben's book. I was going to change it and realized that I would need to
update it all over the file.
I responded that it could be spelled either way. I did update the file do
it would be easier to maintain.
…On Fri, May 6, 2022, 6:42 PM David Lippman ***@***.***> wrote:
Your original code had already used _ for localization, so I'm still
confused what problem this change is trying to solve.
—
Reply to this email directly, view it on GitHub
<#332 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA37HZRSQQU24V77GCJXVPLVIXDBRANCNFSM5VGVMXNA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
I want the server to have the same units as the named units.
I was hoping to show the user a localized version.
…On Fri, May 6, 2022, 6:49 PM David Lippman ***@***.***> wrote:
Also, I just realized that gettext is based on server-declared language,
so can't adapt to the client's language preference like you were trying to
do here. If your goal is for the same server to deliver both spellings, it
might be necessary to go back to your original model, but with gettext used
on the fallback case to account for other languages.
—
Reply to this email directly, view it on GitHub
<#332 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA37HZTWTW46P7QZAMGZYFDVIXD3BANCNFSM5VGVMXNA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
I will close this and request and use the gettext() as the fallback. |
Updated the spelling of deca/deka based on the detected browser language.