> To avoid problems with byte ordering on the used platform you should
> also specify that the data is in big endian byte order.
Yep.
> I use the following (I don't include the version number since it's
> not used in a Plucker document),
>
> 60 string DataPlkr Plucker document
> >0 string >0 "%s",
> >76 beshort >0 %d records
Unfortunately, Solaris doesn't provide the beshort value type. And
doesn't allow strings to be matched in this fashion. Works OK on
Linux, though. I'll put both in the registration doc.
Bill
