> Date: Sat, 26 Aug 2017 22:07:57 +0100 > From: Richard Wordingham via Unicode <[email protected]> > > > We are miscommunicating. My point was that programming for MS-Windows > > needs a good understanding of what the UTF-16 surrogates are, and in > > what MS-Windows APIs/library functions they can and cannot be used. > > Without this understanding, one cannot figure out why the likes of > > iwspace and iswupper only support the BMP, and what APIs to use to > > lift this limitation. Likewise with display-related APIs, used to > > display Unicode text. > > > If you don't teach UTF-16 including these details, the programmers > > will feel lost when they meet with these complications. > > So what's new compared to UTF-8?
Who said this is new? I said this needs to be _taught_, or else people will be ignorant about these subtleties.
