<?xml version="1.0" encoding="windows-1252"?>
<node id="987842" title="Re^6: Best technique to code/decode binary data for inter-machine communication?" created="2012-08-16 13:38:32" updated="2012-08-16 13:38:32">
<type id="11">
note</type>
<author id="733061">
flexvault</author>
<data>
<field name="doctext">
&lt;p&gt;&lt;a href="http://www.perlmonks.org/?node_id=171588"&gt;BrowserUk&lt;/a&gt;,&lt;/p&gt;
&lt;p&gt;WOW, I like that shorthand format, N/(N/a*)* and N/(n/a*)* , look very flexible for future encoding/decoding uses.&lt;/p&gt;&lt;p&gt;
&lt;ul&gt;&lt;i&gt;
Until you apply some form of encode/decoding operation to a file or data stream, anything you read is just a bunch of bytes.&lt;/i&gt;&lt;/ul&gt;
This was my take also!
&lt;ul&gt;&lt;i&gt;
Unicode is a f*** up!
&lt;/i&gt;&lt;/ul&gt;
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.

&lt;/p&gt;
&lt;p&gt;Thank you&lt;/p&gt;
&lt;div class="pmsig"&gt;&lt;div class="pmsig-733061"&gt;
&lt;p&gt;&lt;b&gt;"Well done is better than well said." - Benjamin Franklin&lt;/b&gt;&lt;/p&gt;

&lt;/div&gt;&lt;/div&gt;
</field>
<field name="root_node">
987602</field>
<field name="parent_node">
987781</field>
</data>
</node>
