On Thu, 2013-02-14 at 19:22 +0000, Tim Lewis wrote: > David, BTW, technically the UEFI spec doesn't use UTF-16. It uses > UCS-2, an older subset of UTF-16. Tim
Coming back to this somewhat later... I think Windows *does* implement UTF-16, doesn't it? See http://blogs.msdn.com/b/michkap/archive/2005/05/11/416552.aspx If I'm reading this correctly, it's essentially a retrospective declaration that Windows always *did* use UTF-16, but it just never used any of the code points where you'd be able to tell the difference? Should we do the same thing for EFI? After all, the consistency with Windows is fairly much the only justification for the bizarre decision to use UCS-2 in the first place, surely? Otherwise I'd expect it really ought to have been UTF-8 from the beginning. -- dwmw2
smime.p7s
Description: S/MIME cryptographic signature
------------------------------------------------------------------------------ AlienVault Unified Security Management (USM) platform delivers complete security visibility with the essential security capabilities. Easily and efficiently configure, manage, and operate all of your security controls from a single console and one unified framework. Download a free trial. http://p.sf.net/sfu/alienvault_d2d
_______________________________________________ edk2-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/edk2-devel
