On Fri, Sep 13, 2013 at 12:27 PM, John C Klensin <john+w3c@jck.com> wrote: > It is a somewhat different issue but, coming back to Jonathan's > comment quoted above, I think one can make the case that a > string that contains sufficiently invalid Unicode is an invalid > string and that all of it should be shown as hexboxes or > equivalent because the application cannot really know what was > intended and telling the user that may be better than guessing. You could make that case, but it would never happen. Apart from performance issues (long string with a lone surrogate at the end) it's not compatible with deployed web content. -- http://annevankesteren.nl/Received on Friday, 13 September 2013 11:34:47 UTC
This archive was generated by hypermail 2.4.0 : Monday, 23 January 2023 02:14:32 UTC