Nov. 14, 2017
11:08 p.m.
On Tue, Nov 14, 2017 at 02:55:41PM -0800, Asmus Freytag wrote:
Except that library functions written for Windows may well allow A-labels to be generated from UTF-16 in a single step, possibly applying normalization as well.
Sure. There are lots of ways to implement this, which is why IETF standards normally specify wire formats. What you do in the privacy of your own implementation has no interoperability implications. But if you want to hand a U-label to anyone else, it had better be UTF-8 in NFC, or else it can't be a U-label. A -- Andrew Sullivan ajs@anvilwalrusden.com