Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!aioe.org!news.stack.nl!talisker.lacave.net!lacave.net!not-for-mail From: Alessandro Barracco Newsgroups: comp.lang.ruby Subject: Re: Binary file: SAT Date: Thu, 21 Apr 2011 03:06:11 -0500 Organization: Service de news de lacave.net Lines: 73 Message-ID: <2cddb6943b03d69eca28d3dffeba1374@ruby-forum.com> References: <4fa8adc3b92c44287a399f6cb1aab3ff@ruby-forum.com> NNTP-Posting-Host: bristol.highgroove.com Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: Quoted-printable X-Trace: talisker.lacave.net 1303373612 11200 65.111.164.187 (21 Apr 2011 08:13:32 GMT) X-Complaints-To: abuse@lacave.net NNTP-Posting-Date: Thu, 21 Apr 2011 08:13:32 +0000 (UTC) In-Reply-To: X-Received-From: This message has been automatically forwarded from the ruby-talk mailing list by a gateway at comp.lang.ruby. If it is SPAM, it did not originate at comp.lang.ruby. Please report the original sender, and not us. Thanks! For more details about this gateway, please visit: http://blog.grayproductions.net/categories/the_gateway X-Mail-Count: 381984 X-Ml-Name: ruby-talk X-Rubymirror: Yes X-Ruby-Talk: <2cddb6943b03d69eca28d3dffeba1374@ruby-forum.com> Xref: x330-a1.tempe.blueboxinc.net comp.lang.ruby:3298 Thanx you all. I'm beginning to understand a bit.... These are the first 20 lines of the binary-block in the file: ------------------------------------------------------------------------ 1 mogoo mih m o 1 _ll P/:1 [:,681 ^ 336>1<: ^ \VL ]*63;:- _nk ^ \VL mogqoo QK _mk H:; ^ /- = mo mmeogemi monn 1 n fqfffffffffffffffj:rooh n:rono 1 >,27:>;:- {rn rn _nm mnmqoqoqjgmm | 1 =3D0;& {m rn {rn {l {rn {rn | 1 -:9@)+r:&:r>++-6=3D {rn rn {rn {rn {n {k {j | 1 3*2/ {i rn {rn {rn {h {n | 1 :&:@-:961:2:1+ {rn rn _j 8-6; n _l +-6 n _k ,*-9 o _l >;5 o _k 8->; o = _f /0,+<7:<4 o _k ,+03 oqoohilhjnjnfgklfljfh _k 1+03 lo _k ;,63 o _g = 93>+1:,, o _h /6'>-:> o _k 72>' o _i 8-6;>- o _j 28-6; looo _j *8-6; o = _j )8-6; o _no :1;@96:3;, | 1 ):-+:'@+:2/3>+: {rn rn l o n g | 1 -:9@)+r:&:r>++-6=3D {rn rn {rn {rn {l {k {j | -------------------------------------------------------------------------= It consists of pairs of lines: the first is a code (always 1), the = second is the data. I think that the latter is wrote according to the = SAT format (well to the SAB format, it's binary....). ACIS supports two kinds of save files, SAT and SAB, which stand for = =E2=80=9CStandard ACIS Text=E2=80=9D and =E2=80=9CStandard ACIS Binary=E2=80=9D, respectively. Although one is= ASCII text and = the other is binary data, the model data information stored in the two formats is identical A SAB file has a .sab file extension. A SAB file uses delimiters between elements and binary tags, without additional formatting. The binary formats supported are: int . . . . . . . . . . 4--byte 2s complement (as long) long . . . . . . . . . 4--byte 2s complement double . . . . . . . 8--byte IEEE char . . . . . . . . . 1--byte ASCII where =E2=80=9Cbyte=E2=80=9D is eight bits, and files are considered to b= e byte strings. = For multi--byte data items, byte order normally just matches that of the processor being = used, but a specific order may be imposed by compiling with the preprocessor macro BIG_ENDIAN or LITTLE_ENDIAN defined. -- = Posted via http://www.ruby-forum.com/.=