I agree that this is a challenge of the scoring system effort. If a user experience if broken due to i18n/l10n issues unrelated to 6530-6532, what should we say about it? Our consensus has been that if the brokenness is a result of choices by the provider, then it gets a score demerit. If it's entirely a result of things outside the control of the provider, then it shouldn't be included in the guide at all. So it's important to determine whether something is inherited from the platform (for example), since that is outside of the provider's control. -----Original Message----- From: UA-EAI <ua-eai-bounces@icann.org> On Behalf Of Arnt Gulbrandsen via UA-EAI Sent: Wednesday, August 17, 2022 4:20 AM To: ua-eai@icann.org Subject: [EXTERNAL] Re: [UA-EAI] header fields inherit from the Operating System for Sinhala [was: Re: UA EAI Meeting Notes 02 August 2022] 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 _______________________________________________ UA-EAI mailing list UA-EAI@icann.org https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmm.icann.org%2Fmailman%2Flistinfo%2Fua-eai&data=05%7C01%7Cmarksv%40microsoft.com%7C6a85395b1d1b4e34764c08da804e3d24%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637963370776306273%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=%2FuBPISWvWwiEOZ5hT6q1h2AHfqCRm00YSUWJQiYQrqc%3D&reserved=0 _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.icann.org%2Fprivacy%2Fpolicy&data=05%7C01%7Cmarksv%40microsoft.com%7C6a85395b1d1b4e34764c08da804e3d24%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637963370776306273%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=6ZOKMWXWlLuFEGdF%2BFKaLcZS%2B9VIqdgTsxyEI27NW5g%3D&reserved=0) and the website Terms of Service (https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.icann.org%2Fprivacy%2Ftos&data=05%7C01%7Cmarksv%40microsoft.com%7C6a85395b1d1b4e34764c08da804e3d24%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637963370776462496%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=sTWk2I73gxVGyr2iZiiE2l68HMOZ2qC6A3U4MnpvX4o%3D&reserved=0). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.