I disagree with that characterization, of course. The recommendation for libraries and low-level tools to pass them through rather than screw with them makes them usable. The recommendation to check for noncharacters from unknown sources and fix them was good advice then, and is good advice now. Any app where input of noncharacters causes security problems or crashes is and was not a very good app.
Mark <https://google.com/+MarkDavis> *— Il meglio è l’inimico del bene —* On Mon, Jun 2, 2014 at 6:37 PM, Asmus Freytag <asm...@ix.netcom.com> wrote: > On 6/2/2014 9:27 AM, Mark Davis ☕️ wrote: > > > On Mon, Jun 2, 2014 at 6:21 PM, Shawn Steele <shawn.ste...@microsoft.com> > wrote: > >> The “problem” is now that previously these characters were illegal > > > The problem was that we were inconsistent in standard and related > material about just what the status was for these things. > > > And threw the baby out to fix it. > > A./ > > > Mark <https://google.com/+MarkDavis> > > *— Il meglio è l’inimico del bene —* > > > _______________________________________________ > Unicode mailing > listUnicode@unicode.orghttp://unicode.org/mailman/listinfo/unicode > > >
_______________________________________________ Unicode mailing list Unicode@unicode.org http://unicode.org/mailman/listinfo/unicode
