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
It is very easy to create linear expressions in a text editor. It currently seems that a screen reader user gets tripped up in the Microsoft Word math editor. If you make a mistake and backspace or if you add a space accidendetly, it becomes difficult to make changes.
Testing with Notepad, Notepad++, and VS Code, the three editors behaved the same.
Taking the expression, \sqrt ((4^3 +2)/2a) =7 and pasting it into the Word math editor, i.e., alt+= and then ctrl+v and then pressing enter produced the correct results. Moving back into the expression in Word and pressing ctrl+= built up the expression.
Then going from Word to the texteditors also worked identically. Copying the linear expression or the built-up expressionn to the clipboard and pasting it into the editors gave us:
√((4^3+2)/2a)=7
Notice that \sqrt was converted to the unicode character.
Now going back into Word and pasting the expression using √ instead of \sqrt yielded the same results. The only difference is that with \sqrt, you need to have a space character after the shortcut whereas with √, you should not put in a space.
It seems that students and professionals could benefit from using this workflow to create documents with math. If a textbook in HTML or EPUB with MathML were provided to the students, the mathML can be copied into the Word document and converted to the Office Math from Word.
The math that originated as MathML can then be copied and pasted as text and then edited and pasted back into Word.
If we think this is a good option, we should create documentation describing the workflow.
The text was updated successfully, but these errors were encountered:
If you enter UnicodeMath in https://murrayiii.github.io/UnicodeMathML/playground/ , click on the displayed output, and type Ctrl+c, then typing Ctrl+v in Word will paste the built-up result into Word. The web app does this by copying the MathML for the equation to the clipboard and Word recognizes this as MathML and converts it to its internal (OMML) format. Note that the UnicodeMathML web app is a work in progress 😊But you can already enter equations more quickly than in Word since it has math autocomplete.
I meant to ask this in our meeting and forgot... Is this an issue that we want to mention to Microsoft, or more of a discussion item? If we want to submit it as an issue, I believe that we may need more clarity on what we are asking Microsoft to do.
It is very easy to create linear expressions in a text editor. It currently seems that a screen reader user gets tripped up in the Microsoft Word math editor. If you make a mistake and backspace or if you add a space accidendetly, it becomes difficult to make changes.
Testing with Notepad, Notepad++, and VS Code, the three editors behaved the same.
Taking the expression, \sqrt ((4^3 +2)/2a) =7 and pasting it into the Word math editor, i.e., alt+= and then ctrl+v and then pressing enter produced the correct results. Moving back into the expression in Word and pressing ctrl+= built up the expression.
Then going from Word to the texteditors also worked identically. Copying the linear expression or the built-up expressionn to the clipboard and pasting it into the editors gave us:
√((4^3+2)/2a)=7
Notice that \sqrt was converted to the unicode character.
Now going back into Word and pasting the expression using √ instead of \sqrt yielded the same results. The only difference is that with \sqrt, you need to have a space character after the shortcut whereas with √, you should not put in a space.
It seems that students and professionals could benefit from using this workflow to create documents with math. If a textbook in HTML or EPUB with MathML were provided to the students, the mathML can be copied into the Word document and converted to the Office Math from Word.
The math that originated as MathML can then be copied and pasted as text and then edited and pasted back into Word.
If we think this is a good option, we should create documentation describing the workflow.
The text was updated successfully, but these errors were encountered: