Sorting it all Out Michael Kaplan's random stuff of dubious value Be sure to read the disclaimer here first!
Okay, this blog is going to serve as a warning that a whole bunch of blogs in this Blog are about to happen about a particular topic.
The topic is one I have kind of talked about before.
The difference in software between UCS-2 and UTF-16, and what is involved with migrating code that "covers" the former to code that covers the latter.
Now the reason that this difference is interesting is just about everyone who is asking the questions (and there seem to be a lot of them, especially these last couple of weeks!), is handicapped by several issues, from incorrect assumptions about what works for them today to inaccurate picture of what they need to do to fix the problems to inappropriate plans for the scope of the work to plan.
It's a mess, it really is. I'm actually even going go change some of the content of a training presentation that is coming up to cover this topic a bit more, too.
Maybe I'll even mention this series! :-)
Anyway, consider this the content-free introduction to this exciting series.
If you are one of the people currently looking at this problem and are doing so with the unreserved joy one might feel for the removal of an impacted wisdom tooth, then this series is here especially for you! :-)
All of the characters in Unicode are taking the long weekend off. I'll see if some of the non-characters stuck in town might want to sponsor....
Waiting with bait on my breath, Michael.
You might want to brush your teeth for the benefit of those around you. :-)
Please do mention UCS-4 aka UTF-32 and UTF-8 while you're at it, and please make sure that UCS-2 should be forbidden :)
A.
If you do expand the scope it might be a good time to let people in on variation selectors as well.
Previous blogs in this series of blogs on this Blog: Part 0: The intro, sans content By the end of this
Previous blogs in this series of blogs on this Blog: Part 0: The intro, sans content Part 1: Getting