[rfc-i] Use of unicode

[Joe Hildebrand]

In this particular case, many browsers will render an empty box for the
codepoint.  It should be easy to detect.

An example: http://cursive.net/unknown-codepoint.html

On 4/24/12 5:29 AM, "Larry Masinter" <masinter at adobe.com> wrote:

> famously, mainstream browsers accept all input and give no indication of
> rendering failures
> 
> 
> -----Original message-----
> From: Joe Hildebrand <jhildebr at cisco.com>
> To: "Martin J. Dürst" <duerst at it.aoyama.ac.jp>
> Cc: Larry Masinter <masinter at adobe.com>, "rfc-interest at rfc-editor.org"
> <rfc-interest at rfc-editor.org>
> Sent: Tue, Apr 24, 2012 07:54:37 GMT+00:00
> Subject: Re: [rfc-i] Use of unicode
> 
> On 4/23/12 9:56 PM, "Martin J. Dürst" <duerst at it.aoyama.ac.jp> wrote:
> 
>> One thing I was thinking about was that the RFC editor could use a tool
>> that extracts all non-ASCII characters from the document and lists them
>> by frequency and "derived age" (that's the character property in Unicode
>> that tells you in which version of Unicode the character was first
>> encoded). Although not failsafe, that would give some clue about the
>> probability that the character renders reasonably.
> 
> I was thinking of something much less tool-intensive.  Everyone reads the
> I-D in their favorite browser.  If someone can't read a character in a
> mainstream browser on a mainstream OS, the WG finds a work-around, or
> decides to live with it and files a bug on the software.
> 
> --
> Joe Hildebrand
> 

-- 
Joe Hildebrand