Easy 500 to someone who understands....
Consider the following and tell me why inputBytes does not always equal outputBytes? I think it has something to do with the size of inputBytes but what can I do to coerce input bytes to always be 'convertable' to and from a unicode string?
byte[] inputBytes;
.
.
// inputBytes is created from 'somewhere'
.
.
byte[] outputBytes = Encoding.Unicode.GetBytes(
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
That's because the Input bytes are probably encoded with a default encoding that is not Unicode.
I would guess ASCII, UTF-8 or Latin1 encoding is the default
In any case, you will want to convert the encoding
Here's a site that may help
http://msdn2.microsoft.com
That's because the Input bytes are probably encoded with a default encoding that is not Unicode.
I would guess ASCII, UTF-8 or Latin1 encoding is the default
In any case, you will want to convert the encoding
Here's a site that may help
http://msdn2.microsoft.com
Sure it is... You show it being encoded right here:
byte[] outputBytes = Encoding.Unicode.GetBytes(
First you take the input bytes and encode them into ASCII (or whatever your default encoding is) {Encoding.GetString(inputB
since you are not using "byte[] outputBytes = inputBytes" It is clear that the input bytes are in a format other than Unicode. You have to do a transformation if the bytes aren't in the right format.
Sorry --- The code example was wrong --- Should have been as follows which clearly converts to and from the same code page --- I have also added a code snippet that demonstrated the same issue when xk gets to [0, 216] ....
byte[] inputBytes;
// inputBytes is created from 'somewhere'
byte[] outputBytes = Encoding.Unicode.GetBytes(
//problem can also be demonstrated with the following snippet....
for (byte xi = 0; xi < 255; xi++)
{
for (byte xj = 0; xj < 255; xj++)
{
byte[] xk = new byte[2] { xi, xj };
string xs = Encoding.Default.GetString
if (xs==string.Empty)
string badCodeThatDoesntEncode = "yes";
}
}
You may have a case of invalid characters occuring during the conversion. In multibyte character sets not all two byte sequences are valid sequences, hence if you are creating the inputBytes in a non unicode compatible fashion (you said authentication, so I assume a hash function), the default behavior of the encoders is to _discard_ invalid sequences, hence the discrepancy between inputBytes and outputBytes.
Btw. the default string encoding in .Net is unicode.
Rats! It would be nice if there was a way of doing this - Simply to squash down a byte array to as small as possible string representation (single byte string conversion not good enough). Now I know - Unicode doesnt mean quite mean two byte encoding in the way I thought it might. Hmm.. back to the drawing board
Thanks
Business Accounts
Answer for Membership
by: _TAD_Posted on 2006-10-27 at 09:33:10ID: 17820479
That's because the Input bytes are probably encoded with a default encoding that is not Unicode.
I would guess ASCII, UTF-8 or Latin1 encoding is the default
In any case, you will want to convert the encoding
Here's a site that may help
http://msdn2.microsoft.com