On 3 October 2018 at 15:41:42, Mark Davis ☕️ via Unicode (unicode@unicode.org)
wrote:
> Let me clear that up; I meant that "the underlying storage never contains
> something that would need to be represented as a surrogate code point." Of
> course, UTF-16 does need surrogate code units. What #1
Mark
On Wed, Oct 3, 2018 at 3:01 PM Daniel Bünzli
wrote:
> On 3 October 2018 at 09:17:10, Mark Davis ☕️ via Unicode (
> unicode@unicode.org) wrote:
>
> > There are two main choices for a scalar-value API:
> >
> > 1. Guarantee that the storage never contains surrogates. This is the
> > simplest
On 3 October 2018 at 09:17:10, Mark Davis ☕️ via Unicode (unicode@unicode.org)
wrote:
> There are two main choices for a scalar-value API:
>
> 1. Guarantee that the storage never contains surrogates. This is the
> simplest model.
> 2. Substitute U+FFFD for surrogates when the API returns code
>
Mark
On Tue, Oct 2, 2018 at 8:31 PM Daniel Bünzli
wrote:
> On 2 October 2018 at 14:03:48, Mark Davis ☕️ via Unicode (
> unicode@unicode.org) wrote:
>
> > Because of performance and storage consideration, you need to consider
> the
> > possible internal data structures when you are looking at so
4 matches
Mail list logo
