Hi, I think there's a misunderstanding with regard to RFC 6532. An email message may be said to require three things. 1. That the sender composes it. 2. Transmission from sender to recipient. 3. That the recipient reads it. IETF standards concern themselves exclusively with point 2. If the recipient lacks the necessary fonts to display the message (or the sender does!), that doesn't affect RFC 6532's concept of validity, because that validity exists only within point 2. As a consequence of that, if the message is 6532-valid, then the receiving software has to understand which characters it should display (or read). Successful display is outside the bounds of 6532, but understandable communication of what is to be displayed is within. Arnt