On 12/9/2016 7:50 AM, Ray_Net wrote: > Richmond wrote on 09-12-16 11:03: >> "David E. Ross" <[email protected]> writes: >> >>> I assert that it is the sender's reponsibility to ensure that sent >>> messages can be correctly viewed by the intended recipients. This is >> But while we are waiting for the ideal world, we have to be >> pragmatic. Senders with MS Office don't know what they are doing >> typically. > When I was at work, everybody uses Microsoft Outlook and everyboy uses > Wingdings to make a smiley. > We did not know that outside our intranet, that this "picture" is not > shown correctly. > Now, with my windows10 machine, I use SM, but If I use Outlook, I think > that the wingdings smiley will render correctly. > So it looks, that the problem is an SM problem; because Outlook can > render the wingdings smiley which is present on my computer (I have this > font available) >
No, the problem is that Outlook users are inserting a smilie face glyph from a graphics font that has the same code-point (0x004A) as the letter J in other fonts. This is peculiar to Microsoft and its Wingdings font. It is definitely non-standard. The Unicode standard has the smilie face glyph at code-point 0x1F642 It would be definitely wrong -- a major deviation from the commitment to adhere to standards -- for any Mozilla-based application to render 0x004A as anything other than J. You should read <https://www.joelonsoftware.com/2003/10/08/the-absolute-minimum-every-software-developer-absolutely-positively-must-know-about-unicode-and-character-sets-no-excuses/>. -- David E. Ross The Crimea is Putin's Sudetenland. The Ukraine will be Putin's Czechoslovakia. See <http://www.rossde.com/editorials/edtl_PutinUkraine.html>. _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
