* One _inputs_ scalar values (not surrogate code points). * The encoding form will _output_ a short sequence of encoding form–specific code units. (Various voices on this list have stated that these should never be called code points.) * The _algorithm mapping from input to output_ doesn't make use of surrogate code points. (Even though the Glossary states, under "Surrogate Code Point", that they are "for use by UTF-16".) The only "use" is indirect, through awareness of the positioning and size of the range of non-code-point scalar values.
In what way does UTF-16 "use" surrogate code /points/? An encoding form
is a mapping. Let's look at this mapping:
- Re: Code point vs. scalar value Stephan Stiller
- Re: Code point vs. scalar value Philippe Verdy
- Re: Code point vs. scalar value Asmus Freytag
- Re: Code point vs. scalar value Stephan Stiller
- Re: Code point vs. scalar value Stephan Stiller
- Re: Code point vs. scalar value Philippe Verdy
- Re: Code point vs. scalar value Asmus Freytag
- Re: Code point vs. scalar va... Stephan Stiller
- Re: Code point vs. scalar va... Philippe Verdy
- Re: Code point vs. scalar va... Asmus Freytag
- Re: Code point vs. scalar va... Philippe Verdy