Apr 26, 2018 - macOS includes features that make it easy to find and type special characters like emoji and currency symbols. From there, use the Emoji option on the left to find just emoji, or select any of the other menus for arrows, stars, currency symbols, math symbols, punctuation, music symbols, Latin, and other symbols and characters that you can insert into the email. If you go this route, you have to double-click the emoji to add it to the email. For some inexplicable reason, somebody at Microsoft thought it wise to autocorrect “:)” as a truer smiley when composing rich text documents and/or HTML email – rendering it in a specific font face (WingDings). This is why people think you’re crazy for injecting a random “J” in emails – they don’t have the same font(s) installed on their machine! And even if you have WingDings installed, you may only still see a J where a smile should clearly be. So, there’s a simple fix that’ll make your emails 100% more intelligible (as far as smiles are concerned). Delete the autocompletes. • Open Microsoft Outlook (if it’s not already open). ![]() • Fire up the Options panel (found under the File ribbon). • Click open the Mail tab. You should see a “Spelling and Autocorrect” button. The “Editor Options” panel will launch. • From there, click the “AutoCorrect Options” button. The “AutoCorrect: English (U.S.)” properties pane is what you should see next. • Under the default “AutoCorrect” tab, look to the “Replace text as you type” section. • Click the “Delete” button. • Repeat these steps for the other smiley autoreplacements. ![]() This isn’t a solution, but I believe it explains why the issue occurs. Looking at the source code (I used Apple Mail) of an email I received from Outlook, both the HTML and the plain text part of the email claims to be Unicode, e.g.: Content-Type: text/html; charset='utf-8' The content is also in base64 but if you decode it you will see the J, e.g. Free video player that plays all formats. Great work J Since the Unicode standard says that each character has its own unique code, and the message was marked as Unicode, that J should therefore be a J, regardless of font. Unicode dispenses with the idea that you can press the same character on your keyboard and a completely different character can come out depending on the font. If you typed a J, you wanted a J, full stop. Hence, most non-Outlook email clients (and web browsers) show a J. What Outlook should be doing is one of: • Send the smiley in the Unicode position assigned to it, which is 263A (☺) – but I guess at the risk that older non-Unicode clients won’t understand or older computers won’t have a font with the smiley in that codepoint • Continue to send it as a J with an HTML tag saying it should be in Wingdings, but specifying the encoding of the message as something non-Unicode, in the hope that clients will render the symbol. I’m not convinced it will work (a quick mockup of a web page didn’t work), and also causes problems with other unusual characters or other languages not rendering properly.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |