--- In [email protected], "Sheri" <sheri...@...> wrote: > Stop! I just found a way to do it without unicode strings. Can embed unicode > code points in angle brackets within the normal ansi style strings. So no > revision is needed here. Hope you see this before spending much time on it.
Good. I just pastd the code into com that would know how to find unicode plugin if required. But then thought, oops, I'll either have to flag somehow that unicode strings are expected, or scan every argument to see if it's a handle to a unicode string. But the latter wouldn't work, because (often?) user would want to provide an ANSI string, assuming and requiring that it would be translated to unicode...no, wait a minute, that's okay, all strings are always translated to BSTR aka unicode anyway, so ansi string would be okay..... <and so on, stream of conciousness, no waste, gotta think the problem out sooner or later nyway, but I'll stop now good night...>
