{"id":485,"date":"2022-07-26T18:54:43","date_gmt":"2022-07-27T01:54:43","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/math-in-office\/?p=485"},"modified":"2022-07-26T18:54:43","modified_gmt":"2022-07-27T01:54:43","slug":"microsoft-365-modern-comments","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/math-in-office\/microsoft-365-modern-comments\/","title":{"rendered":"Microsoft 365 Modern Comments"},"content":{"rendered":"<p><span style=\"color: #000000;\">The new<\/span> <a href=\"https:\/\/support.microsoft.com\/en-us\/office\/using-modern-comments-in-word-edc6ae71-0a2d-49fe-8faa-986f1e48136a#:~:text=Using%20modern%20comments%20in%20Word%201%20Two%20ways,...%204%20Assigning%20tasks.%20...%205%20FAQs.%20\">Modern Comments facility<\/a> <span style=\"color: #000000;\">aims to give a similar commenting experience on the web and in native apps. On the desktop in Windows and the Mac, the editor component is RichEdit. The facility is a work in progress, and it is getting very nice. This post gives some background on incorporating RichEdit into the Microsoft 365 commenting experience.<\/span><\/p>\n<p><span style=\"color: #000000;\">The most powerful commenting experience to date was in desktop Word, which used Word text boxes for comments. This allowed users to use most Word features in Word comments. Meanwhile, RichEdit lacks many advanced Word features. So, some Word power users have found their workflows hampered or even broken. Initially, RichEdit lacked quite a few popular features, such as HTML interoperability, web image access, built-in autocorrect and autoformatting, considerable Word user interface (UI) functionality in multilevel lists, and so on. We have been working diligently on remedying the most grievous limitations.<\/span><\/p>\n<p><span style=\"color: #000000;\">On the other hand, RichEdit instances are much smaller and faster than Word text boxes which improves performance for documents that have many comments. Other apps don\u2019t have all of Word\u2019s editing power and it\u2019s desirable to have a uniform experience across the apps. Another difference is that only the author sees comments until posted, as in chats. This behavior is hopefully less distracting in collaborative scenarios.<\/span><\/p>\n<p><span style=\"color: #000000;\">We have been enhancing RichEdit in the most requested areas, e.g.,<\/span> <a href=\"https:\/\/devblogs.microsoft.com\/math-in-office\/richedit-html-support\/\">HTML conversion fidelity<\/a>, <a href=\"https:\/\/devblogs.microsoft.com\/math-in-office\/displaying-enlarged-images-in-popup-window\/\">image support<\/a>, <span style=\"color: #000000;\">proofing (built-in autocorrect and most<\/span> <a href=\"https:\/\/devblogs.microsoft.com\/math-in-office\/richedit-autoformatting\/\">autoformatting<\/a> <span style=\"color: #000000;\">options), multilevel-list UI, and more compatible hyperlink handling. PowerPoint has used RichEdit\u2019s multilevel lists for many years, but PowerPoint has its own UI, and RichEdit\u2019s multilevel list UI and accessibility have needed improvements. Together with the improvements needed for<\/span> <a href=\"https:\/\/devblogs.microsoft.com\/math-in-office\/windows-11-notepad\/\">Notepad<\/a>,<span style=\"color: #000000;\"> RichEdit has been getting better and better \ud83d\ude0a.<\/span><\/p>\n<p><span style=\"color: #000000;\">More work remains, such as grammar checking, text prediction, tables, and math typography. RichEdit has as good or better math support as the Office apps, but math isn\u2019t currently enabled in Modern-Comments. Math might be easy to support. RichEdit plain text represents math zones in<\/span> <a href=\"https:\/\/www.unicode.org\/notes\/tn28\/UTN28-PlainTextMath-v3.1.pdf\">UnicodeMath<\/a> <span style=\"color: #000000;\">starting with a \u2018\u2045\u2019 (U+2045) and ending with a \u2018\u2046\u2019 (U+2046). Inserting the plain text into a RichEdit control and calling<\/span> <a href=\"https:\/\/docs.microsoft.com\/en-us\/windows\/win32\/api\/tom\/nf-tom-itextrange2-buildupmath\">ITextRange2::BuildUpMath<\/a> <span style=\"color: #000000;\">builds up the UnicodeMath to<\/span> <a href=\"https:\/\/devblogs.microsoft.com\/math-in-office\/officemath\/\">OfficeMath<\/a>. <span style=\"color: #000000;\">RichEdit has been able to roundtrip OfficeMath in plain text this way ever since Office 2007. For example, copy a document with math zones into Notepad, copy it back to RichEdit, and call ITextRange2::BuildUpMath(). The math zones are restored. The \u201d\u2045&lt;UnicodeMath&gt;\u2046\u201d plain-text syntax is similar to the way LaTeX starts math zones with \u201c\\[\u201c and ends them with \u201c\\]\u201d. In addition, the math ribbon would need to be integrated, although math keyboard entry is faster if you know UnicodeMath or<\/span> <a href=\"https:\/\/en.m.wikibooks.org\/wiki\/LaTeX\/Mathematics\">LaTeX<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>The new Modern Comments facility aims to give a similar commenting experience on the web and in native apps. On the desktop in Windows and the Mac, the editor component is RichEdit. The facility is a work in progress, and it is getting very nice. This post gives some background on incorporating RichEdit into the [&hellip;]<\/p>\n","protected":false},"author":40611,"featured_media":55,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[],"class_list":["post-485","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-math-in-office"],"acf":[],"blog_post_summary":"<p>The new Modern Comments facility aims to give a similar commenting experience on the web and in native apps. On the desktop in Windows and the Mac, the editor component is RichEdit. The facility is a work in progress, and it is getting very nice. This post gives some background on incorporating RichEdit into the [&hellip;]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/math-in-office\/wp-json\/wp\/v2\/posts\/485","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/math-in-office\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/math-in-office\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/math-in-office\/wp-json\/wp\/v2\/users\/40611"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/math-in-office\/wp-json\/wp\/v2\/comments?post=485"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/math-in-office\/wp-json\/wp\/v2\/posts\/485\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/math-in-office\/wp-json\/wp\/v2\/media\/55"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/math-in-office\/wp-json\/wp\/v2\/media?parent=485"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/math-in-office\/wp-json\/wp\/v2\/categories?post=485"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/math-in-office\/wp-json\/wp\/v2\/tags?post=485"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}