Re^6: Best technique to code/decode binary data for inter-machine communication?

[flexvault]

in reply to Re^5: Best technique to code/decode binary data for inter-machine communication?
in thread Best technique to code/decode binary data for inter-machine communication?

BrowserUk,

WOW, I like that shorthand format, N/(N/a*)* and N/(n/a*)* , look very flexible for future encoding/decoding uses.

Until you apply some form of encode/decoding operation to a file or data stream, anything you read is just a bunch of bytes.

This was my take also!

Unicode is a f*** up!

Agreed! I haven't looked at this much, but the spec says '22 bits', but Perl code seems to use '24 bits' for each character with the high-order bits being '00'. Whether other implementations do the same I don't know, but seems like too much room for mis-interpretation.

Thank you

[BrowserUk]

I like that shorthand format, N/(N/a*)* and N/(n/a*)* , look very flexible for future encoding/decoding uses.

See also Mystery! Logical explanation or just Satan's work?.

the spec says '22 bits', but Perl code seems to use '24 bits' for each character with the high-order bits being '00'.

utf-8 is a variable width encoding. Each character can require from 1 to 4(*) bytes.

(*Or 6 bytes depending upon the wind direction and the phases of the moon(**).)

<smaller>(**which moon is left unspecified :)</smaller>