Suggestions need to be fully formed

by Michael S. Kaplan, published on 2006/03/13 03:09 -05:00, original URI: http://blogs.msdn.com/b/michkap/archive/2006/03/13/550148.aspx


A few days ago, a guy named Ken asked in the Suggestion Box:

Hi Michael,

I been following the codepage articles and i notice that using the method you describe does not produce characters point for certain codepages.  For example, codepage 708, 709, 710, 737, 775 (this just list a few)... doesn't return any code points.   Why is that?  The code page are valid code page identifiers as listed on MSDN.

Thanks in advance.
Ken

One of the biggest problems with leaving anonymous suggestions is that if I have a question about it then the only thing I can do is:

I chose that fourth option. Ken, I hope you are reading this!

These code pages work for me.

However, since the exact post that was being asked about was not left (not even its title!) so I am not sure what specific technique or calling method (or even flags or the error returned or even version of Windows) is involved.

I definitely need more information to suggest what might be going on....


# Nick Lamb on 13 Mar 2006 4:43 AM:

I'd suggest he's talking about your article "Getting the characters in a code page (the code)" from 2006-01-20. The clue being the phrase "doesn't return any code points", since that's the only code you've posted recently that outputs Unicode code points AFAIK.

Does that give you anything to work on Michael?

# Michael S. Kaplan on 13 Mar 2006 8:07 PM:

Hi Nick --

Well, the code in that article (http://blogs.msdn.com/michkap/archive/2006/01/20/515238.aspx) works just fine with these code page values -- as long as the code pages have in fact been installed on the machine....

go to newer or older post, or back to index or month or day