--- /dev/null
+# Sound formats, from Jan Nicolai Langfeldt <janl@ifi.uio.no>
+0 string .snd audio data:
+>12 long 1 8-bit u-law,
+>12 long 2 8-bit linear PCM,
+>12 long 3 16-bit linear PCM,
+>12 long 4 24-bit linear PCM,
+>12 long 5 32-bit linear PCM,
+>12 long 6 32-bit floating point,
+>12 long 7 64-bit floating point,
+>12 long 23 compressed (G.721 ADPCM),
+>20 long 1 mono,
+>20 long 2 stereo,
+>20 long 4 quad,
+>16 long x %d Hz
+8 long 0x41494646 AIFF sound data file
+0 long 0x4e54524b MultiTrack sound data file
+>4 long x - version %ld
+>20 string U with mipsucode members
+>21 string L with mipsel members
+>21 string B with mipseb members
+>19 string L and a EL hash tabl
+>19 string B and a EB hash tabl
+>22 string X -- out of date
--- /dev/null
+
+Path: sq!geac!torsqnt!tmsoft!robohack!druid!darcy
+From: darcy@druid.uucp (D'Arcy J.M. Cain)
+Newsgroups: comp.graphics
+Subject: Re: File Formats
+Message-ID: <1990Jul12.183149.3002@druid.uucp>
+Date: 12 Jul 90 18:31:49 GMT
+References: <8437@arctic.nprdc.arpa>
+Reply-To: darcy@druid.UUCP (D'Arcy J.M. Cain)
+Organization: D'Arcy Cain Consulting, West Hill, Ontario
+Lines: 47
+
+In article <8437@arctic.nprdc.arpa> armfield@nprdc.navy.mil
+(Sylvia Armfield) writes:
+> I still haven't figured out how to identify the following file formats:
+> CGM
+>
+There is more than one type of CGM file. I can help you out with the clear
+text encoding and the binary encoding. The other encoding is character. It
+is described in ISO 8632-2. In any case all CGM files start with the same
+thing, the BEGIN METAFILE statement. The only difference is in how this
+element is encoded.
+
+In clear text encoding the element is simply the ASCII string "BEGMF". In
+binary encoding you have to read in the first two bytes as a word. The
+MSB is followed in the file by the LSB. This word is bitmapped to include
+the following information:
+ 15 - 12: Element class
+ 11 - 5: Element ID
+ 4 - 0: Parameter list length
+
+BEGIN METAFILE is a "Delimiter Element" making it class 0. The element
+ID within that class is 1. The parameter list length is variable so it
+must be ANDed out when comparing. The bit pattern is then:
+
+ 0 0 0 0 0 0 0 0 0 0 1 x x x x x
+
+To check it simply AND the word with 0xffe0 and compare it with 0x0020. In
+reading the standard I get the impression that it is actually legal to add
+padding characters (nulls) to the beginning of the file. I rather doubt that
+anyone would actually do this but it may be appropriate to read in words till
+a non zero word is read and compare this word. You can read in full words
+since all elements are constrained to start on a word boundary.
+
+If you want the full description of the CGM format it is available from
+ANSI as the following ISO standards:
+
+ ISO 8632-1 Functional specification
+ ISO 8632-2 Character encoding
+ ISO 8632-3 Binary encoding
+ ISO 8632-4 Clear text encoding
+
+HTH
+
+--
+D'Arcy J.M. Cain (darcy@druid) | Government:
+D'Arcy Cain Consulting | Organized crime with an attitude
+West Hill, Ontario, Canada |
+(416) 281-6094 |
--- /dev/null
+#
+# "ar", for all kinds of archives.
+0 string !<arch> current ar archive
+>8 string __.SYMDEF random library
+>0 long =65538 - pre SR9.5
+>0 long =65539 - post SR9.5
+>0 short 2 - object archive
+>0 short 3 - shared library module
+>0 short 4 - debug break-pointed module
+>0 short 5 - absolute code program module
+0 string \<ar> System V Release 1 ar archive
+0 string =<ar> archive
+0 long 0xff6d obsolete ar archive
+0 long 0x213c6172 archive file
+0 long 0177555 very old archive
+0 short 0177555 very old PDP-11 archive
+0 long 0177545 old archive
+0 short 0177545 old PDP-11 archive
+0 string =<ar> archive
+0 string -h- Software Tools format archive text
+# "arc" archiver
+0 byte 26 'arc' archive
+>1 byte 0 (empty)
+>1 byte 1 (old format)
+# Rahul Dhesi's zoo archive format, from keith@cerberus.uchicago.edu.
+20 long 0xdca7c4fd Rahul Dhesi's "zoo" archive
projects / file / commitdiff