commons-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From John Zoetebier <john.zoeteb...@transparent.co.nz>
Subject Re: [Codec] RFC2045 Anomaly?
Date Sun, 23 Nov 2003 08:00:50 GMT
On Sun, 23 Nov 2003 17:26:40 +1000, Vikram Goyal <tech@craftbits.com> 
wrote:

>> There is no problem once you understand that the meaning of "0" is
>> contextual.
>> The first "0" is binary zero.
>> The second "0" is digit zero, a character representing the digit "0".
>>
>
> Yes, but as per the rfc, Base64 encoding results in 7bit short line
> transformations. But if the encoded data contains the character '0' it
> violates this principle as 7bit data should not contain this character. A
> '0' character will be the same as a Nul value.

Character "0" is not the same as binary "0".
Just have a look at the ASCII table at http://www.asciitable.com/ref.html
Character "0" is mapped on a bit serie with decimal value 38
This is in 7-bit notation 0100110
The null character is in 7-bit notation 0000000

-- 
John Zoetebier
Web site: http://www.transparent.co.nz

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-user-help@jakarta.apache.org


Mime
View raw message