One of the better overviews I found on the topic is a blog entry by. This is a well known issue with plenty of information available on the net, including several code examples how to avoid or circumvent it. The problem I have is that versions of Outlook 2013 and lower cannot seem to handle the web font but at the same time ignore the font stack and reset to Times New Roman instead of my fallback font. I'm using Outlook 2016 to send my emails with this new signature, and Outlook 2016 as well as most other modern email clients seem to display the signature properly. It makes use of a font stack that tries the web font Open Sans first and falls back to Trebuchet MS if the client cannot display the web font. I created a new html email signature for myself and I'm quite pleased with the result.
0 kommentar(er)
