#Titel Grundlagen / Graphics File Formats Teil 3 #Logo gadget24:pinsel/AG.Grundlagen #Font topaz 8 #C21 This FAQ (Frequently Asked Questions) list contains information on graphics file formats, including, raster, vector, metafile, Page Description Language, 3D object, animation, and multimedia formats. #Y+7 This FAQ is divided into four parts, each covering a different area of graphics file format information: #Y+7 #C10 Graphics File Formats FAQ (Part 1 of 4): General Graphics Format Questions Graphics File Formats FAQ (Part 2 of 4): Image Conversion and Display Programs Graphics File Formats FAQ (Part 3 of 4): Where to Get File Format Specifications Graphics File Formats FAQ (Part 4 of 4): Tips and Tricks of the Trade #C21 #Y+7 Please email contributions, corrections, and suggestions about this FAQ to jdm@netcom.com. Relevant information posted to newsgroups will not automatically make it into this FAQ. #Y+6 #C10 -- James D. Murray ;-{)>>>> #C21 #Y+6 ---------------------------------------------------------------------- #C31 Subject: 0. Contents of Where to Get File Format Specifications #C21 #Y+8 Subjects marked with are new to this FAQ. Subjects marked with have been updated since the last release of this FAQ. #Y+8 #C31 I. General questions about this FAQ #C21 #Y+8 0. Maintainer's Comments 1. What's new in this latest FAQ release? #Y+8 #C31 II. Where to Get File Format Specifications #C21 #Y+8 0. ABF - Adobe Binary Screen Font 1. AFM - Adobe Font Metrics File Format 2. BDF - Adobe Glyph Bitmap Distribution Format 3. BMP - Windows Bitmap Format 4. BRL-CAD - Ballistic Research Laboratory CAD 5. BUFR - Binary Universal Form for the Representation of Meteorological Data 6. CALS - Computer Aided Acquisition and Logistics Support Raster Format 7. CDF - Cyberspace Description Format 8. CGM - Computer Graphics Metafile 9. CMU - Carnegie Mellon University Formats 10. DEM - Digital Elevation Model 11. DLG - Digital Line Graph 12. DPX - Digital Moving Picture Exchange 13. DXF - Autodesk Drawing Exchange Format 14. EPS - Encapsulated PostScript 15. FBM - Fuzzy Bitmap 16. FFIVW - File Format for the Interchange of Virtual Worlds 17. GIF - Graphics Interchange Format 18. GKS - Graphics Kernel System 19. GRIB - Gridded Binary 20. HDF - Hierarchical Data Format 21. HPGL - Hewlett-Packard Graphics Language 22. HPPCL - Hewlett-Packard Printer Control Language 23. IFF - Interchange File Format 24. IGES - Initial Graphics Exchange Specification 25. IMJ - Image JPEG 26. JBIG - Joint Bilevel Image Group 27. JFIF - JPEG File Interchange Format 28. MGF - Materials and Geometry Format 29. MIFF - Magick Image File Format 30. NAPLPS - North American Presentation Layer Protocol Syntax 31. NFF - Neutral File Format 32. NFF - WorldToolKit Neutral File Format 33. NITF - National Imagery Transmission Format 34. OFF - Object File Format 35. PBM - Portable Bitmap 36. PCX - ZSoft Paint 37. PDF - Portable Document Format 38. PDS - Planetary Data Systems Format 39. PGM - Portable Greymap 40. PIC - Pegasus Imaging Corporation Format 41. PNG - Portable Network Graphics 42. PPM - Portable Pixmap 43. POL - InnovMetric Software Polygon Models Format 44. POV - Persistence of Vision Raytracing 45. PS - PostScript 46. PSD - Adobe Photoshop 47. RAD - Radience 48. RAS - Sun Rasterfile 49. RAY - Rayshade 50. RIB - Renderman Interface Bytestream 51. RIFF - Microsoft Resource Interchange File Format 52. RIX - ColoRIX Image File 53. SDML - Spacial Data Modeling Language 54. SGI - Silicon Graphics Image File Format 55. SHG - Segmented Hyper-Graphic 56. SPIFF - Still Picture Interchange File Format 57. STL - Stereolithography Interface Format 58. TGA - Truevision (Targa) File Format 59. TIFF - Tag Image File Format 60. TRIF - Tiled Raster Interchange Format 61. TTF - TypeType Font 62. Type 42 Font Format 63. URT - Utah Raster Toolkit 64. VICAR2 - Planetary File Format 65. VIFF - Visualization Image File Format 66. VPF - Vector Product Format 67. VRML - Virtual Reality Modeling Language 68. WebOOGL - Web Object Oriented Graphics Library 69. WMF - Window Meta File 70. WPG - WordPerfect Graphics Metafile 71. XBM - X BitMap 72. XPM - X PixMap 73. XWD - X Window Dump #Y+8 #C31 III. Kudos and Assertions #C21 #Y+8 0. Acknowledgments 1. About The Author 2. Disclaimer 3. Copyright Notice #Y+8 ------------------------------ #Seitenende #C31 Subject: I. General questions about this FAQ #C21 ------------------------------ #C30 Subject: 0. Maintainer's Comments #C21 One of the reasons you are looking through this FAQ collection is most likely to locate the specification for one or more graphics file formats. That assumption on my part makes this file one of the most important parts of the Graphics File Formats FAQ collection. I therefore wish to make this section as complete as possible. If you have any suggestions for formats to include then please email me at jdm@netcom.com and let me know! ------------------------------ #C30 #Seitenende Subject: 1. What's new in this latest FAQ release? #C21 o A few upates. Nothing new. ------------------------------ #Seitenende #C31 Subject: II. Where to Get File Format Specifications #C21 This section contains an alphabetical listing of file formats, the names of the creators/caretakers, and where to obtain the official specifications, and a brief description of each format. ------------------------------ #C30 Subject: 0. ABF - Adobe Binary Screen Font #C21 ABF is Adobe Systems' binary screen font format. ABF is, in fact, the binary version of the Adobe's ASCII-based Glyph Bitmap Distribution Format (BDF). Each ABF file is a sequence of 8-, 16-, or 32-bit words in either big- or little-endian order. Each file stores information for one font. The specification for the ABF format is: #C10 Adobe Binary Screen Font Files Specification (Version 2.0), Adobe Developer Support, 31 March 1992, P/N LPS5006. #C21 This document available via FTP as a Tech Note in PostScript format, or as hardcopy when obtained directly from Adobe (see the PostScript section for information on how to contact Adobe Systems, Inc.). ------------------------------ #C30 Subject: 1. AFM - Adobe Font Metrics File Format #C21 AFM is Adobe's ASCII-based file format used for storing font metric data as human-readable data. AFM is the standard Adobe font file format. This format is also known as the Adobe Multiple Font Metrics (AMFM) and Adobe Composite Font Metrics (ACFM) file formats. In fact, AFM, AMFM, and ACFM are actually three variations of the same format. AFM files contain base or composite font information. One AFM file is used per master design of a font. AMFM files store control and global font information for a group of AFM files. And ACFM files contain the global metrics of the composite font program. The specification for the AFM format is: #C10 Adobe Font Metrics File Format Specification (Version 4.0), Adobe Developer Support, 14 February 1992, P/N LPS5004. #C21 This document available via FTP as a Tech Note in PostScript format, or as hardcopy when obtained directly from Adobe (see the PostScript section for information on how to contact Adobe Systems, Inc.). ------------------------------ #C30 Subject: 2. BDF - Adobe Glyph Bitmap Distribution Format #C21 BDF is an ASCII-based file format used to store Adobe screen fonts as human-readable data. The BDF sister format, ABF, stores the same font data using a binary format. This format was previously known as the Character Bitmap Distribution Format, but was renamed to the Glyph Bitmap Distribution Format to bring the format's name into agreement with current industry terminology. The specification for the BDF format is: #C10 Glyph Bitmap Distribution Format (BDF) Specification (Version 2.2), Adobe Developer Support, 22 March 1993, P/N LPS5005. #C21 This document available via FTP as a Tech Note in PostScript format, or as hardcopy when obtained directly from Adobe (see the PostScript section for information on how to contact Adobe Systems, Inc.). ------------------------------ #C30 Subject: 3. BMP - Windows Bitmap Format #C21 BMP is the native bitmap file format of the Microsoft Windows environment. It efficiently stores mapped or unmapped RGB graphics data with pixels 1-, 4-, 8-, or 24-bits in size. Data may be stored raw or compressed using a 4-bit or 8-bit RLE data compression algorithm. BMP is an excellent choice for a simple bitmap format which supports a wide range of RGB image data. The BMP format was created and is maintained by Microsoft Corporation: #C10 Microsoft Corporation One Microsoft Way Redmond, WA 98052-6399 Voice: 206.882.8080 Fax: 206.936.7329 BBS: 206.637.9009 #C21 Look in the Win16 SDK, Win32 SDK, and the Microsoft Developers Network Knowledge Base available at ftp://ftp.microsoft.com, http://www.microsotft.com, and CompuServe for Windows BMP information. Look in the OS/2 Developer Connection SDK for OS/2 BMP information. Additional BMP references: #C10 Luse, Marv. "The BMP File Format," Dr. Dobb's Journal, #219 September 1994 (Vol 9, Issue 10), pp. 18-22. The BMP File Format: Part I, Dr. Dobb's Journal, David Charlap, #228 March 1995 (Vol. 20, Issue 3). The BMP File Format: Part II, Dr. Dobb's Journal, David Charlap, #229 April 1995 (Vol. 20, Issue 4). #C21 The code for the above issues are available at: #C10 ftp://ftp.mv.com/pub/ddj/1994/1194.09/bmp.zip ftp://ftp.mv.com/pub/ddj/1995/1195.03/bmp.zip #C21 ------------------------------ #C30 Subject: 4. BRL-CAD - Ballistic Research Laboratory CAD #C21 For general information about BRL-CAD, contact: #C10 Attn: Mike Muuss BRL-CAD Architect U.S. Army Research Laboratory Aberdeen Proving Ground, MD 21005-5068 Email: mike@brl.mil #C21 ------------------------------ #C30 Subject: 5. BUFR - Binary Universal Form for the Representation of Meteorological Data #C21 BUFR is described in the documents: #C10 Guide to the WMO Code Form FM 94-IX EXT. BUFR, W. Thorpe, Fleet Numerical Oceanography Center, Monterey, California. Standard Formats for Weather Data Exchange Among Automated Weather Information Systems, Document Number FCM-S2-1990. #C21 Documents and information on BUFR are available from: #C10 U.S. Department of Commerce/National Oceanic and Atmospheric Administration (NOAA) Attn: Ms. Lena Loman Office of the Federal Coordinator for Meteorological Services and Supporting Research (OFCM) 6010 Executive Blvd, Suite 900 Rockville, MD 20852 Voice: 301.443.8704 U.S. Department of Commerce/National Oceanic and Atmospheric Administration (NOAA) Attn: Dr. John D. Stackpole Chief, Production Management Branch, Automation Division National Meteorological Center WINMC42, Room 307, WWB 5200 Auth Road Camp Springs, MD 20746 Voice: 301.763.8115 Fax: 301.763.8381 Email: jstack@sun1.wwb.noaa.gov #C21 ------------------------------ #C30 Subject: 6. CALS - Computer Aided Acquisition and Logistics Support Raster Format #C21 CALS files are used for document imaging and therefore only store black-and-white, 1-bit image data. CALS Type I files only store a single image per file and the data is always compressed using the CCITT Group 4 encoding algorithm. CALS Type II files may stored multiple images per file, the image data may be tiled, and tiles stored as raw data or as data compressed using CCITT Group 4 encoding. The CALS raster file format is defined primarily in the following military standards documents: #C10 MIL-STD-1840A, Automated Interchange of Technical Information MIL-R-28002A, Requirements for Raster Graphics Representation in Binary Format #C21 These documents may be obtained from the following sources: #C10 Standardization Documents Ordering Desk Building 4D 700 Robbins Avenue Philadelphia, PA 19111-5094 Global Engineering Documents 2805 McGaw Avenue Irvine, CA 92714 USA Voice: 800.854.7179 Voice: 714.261.1455 #C21 The CALS raster file format is supported through the CALS office of the United States Department of Defense: #C10 CALS Management Support Office (DCLSO) Office of the Assistant Director for Telecommunications and Information Systems Headquarters Defense Logistics Agency Cameron Station Alexandria, VA 22314 USA #C21 ------------------------------ #C30 Subject: 7. CDF - Cyberspace Description Format #C21 CDF is an ASCII-based format used for describing cyberspace decks and virtual worlds. This format provides a standard framework that is used to store, retrieve, modify, and exchange descriptions of cyberspace objects; including object initialization, state, and scheduling, and cyberspase simulation. CDF is based on the CDF format described in Autodesk's Cyberspace Development Kit. Autodesk's CDF is a closed format used to support a proprietary developer's tool, while the proposed CDF format is an open format intended to be accepted as an industry standard. The current CDF specification proposal may be obtained from: #C10 http://vrml.wired.com/proposals/cdf/cdf.html #C21 Questions about CDF should be directed to: #C10 Carl Tollander #C21 ------------------------------ #C30 Subject: 8. CGM - Computer Graphics Metafile #C21 The current version of the CGM ANSI/ISO standard (commonly called CGM:1992) is: #C10 Information Processing Systems--Computer Graphics Metafile for the Storage and Transfer of Picture Description Information, ANSI/ISO 8632-1992. #C21 This standard superseded the early CGM:1986 (ANSI X3.122-1986) ANSI standard. The CGM standard is contained in four ISO standards documents: #C10 ISO/IEC 8632-1:1992 Part 1: Functional Specification ISO/IEC 8632-3:1992 Part 2: Character Encoding ISO/IEC 8632-3:1992 Part 3: Binary Encoding ISO/IEC 8632-4:1992 Part 4: Clear Text Encoding #C21 These documents may be obtained from the following organizations: #C10 International Standards Organization (ISO) 1 rue de Varembe Case Postal 56 CH-1211 Geneva 20 Switzerland Voice: +41 22 749 01 11 Fax: +41 22 733 34 30 American National Standards Institute (ANSI) Sales Department 11 West 42nd Street New York, NY 10036 Voice: 212.642.4900 Canadian Standards Association (CSA) Sales Group 178 Rexdale Blvd. Rexdale, Ontario, M9W 1R3 Voice: 416.747.444 #C21 A WWW page devoted to CGM is: #C10 http://speckle.ncsl.nist.gov/~lsr/cgm_std.htm #C21 ------------------------------ #C30 Subject: 9. CMU - Carnegie Mellon University Formats #C21 ------------------------------ #C30 Subject: 10. DEM - Digital Elevation Model #C21 The format of DEM map files is described in the publication: #C10 Data Users Guide 5 - Digital Elevation Models #C21 and is available for $1.00 US from: #C10 Earth Science Information Center (ESIC) U. S. Geological Survey 507 National Center Reston, VA 22092 USA Voice: 1.800.USA.MAPS Voice: 703.860.645 #C21 ------------------------------ #C30 Subject: 11. DLG - Digital Line Graph #C21 The format of DLG graph files is described in the publications: #C10 Data Users Guide 1 - Digital Line Graphs from 1:24,000-Scale Maps Data Users Guide 2 - Digital Line Graphs from 1:100,000-Scale Maps Data Users Guide 3 - Digital Line Graphs from 1:2,000,000-Scale Maps #C21 and each is available for $2.00 US from: #C10 Earth Science Information Center (ESIC) U. S. Geological Survey 507 National Center Reston, VA 22092 USA Voice: 1.800.USA.MAPS Voice: 703.860.645 #C21 ------------------------------ #C30 Subject: 12. DPX - Digital Moving Picture Exchange #C21 DPX is the SMPTE (Society of Motion Picture and Television Engineers) standard file format for Digital Moving Picture Exchange. DPX is, in fact, the Kodak Cineon raster file format with just a few slight modifications to the file's header. The DPX specification is referred to as the ANSI/SMPTE 268M-1994 Standard (dated: 18 February 1994) and is available directly from SMPTE: #C10 The Society of Motion Picture and Television Engineers 595 W. Hartsdale Avenue White Plains, NY 10607 USA Voice: 914.761.1100 Fax: 914.761.3115 Web: http://www.smpte.com #C21 ------------------------------ #C30 Subject: 13. DXF - Autodesk Drawing eXchange Format #C21 The AutoCAD DXF (Drawing eXchange Format) and AutoCAD DXB (Drawing eXhange Binary) formats are the native vector file formats of Autodesk's AutoCAD CAD application. DXF is probably one of the most widely supported vector formats in the world today. DXF is rich in features, including: support for 3D objects, curves, text, associative dimensioning, and is an easy format to parse. The DXB format is a binary representation of a DXF file and they are usually smaller and faster to load than the equivalent DXF file. The latest "official" DXF revision is Release 12. However, there is an even newer version of DXF containing several changes and additions to the format. Apparently the specification of the latest version of the DXF format is not yet (if it will ever be) freely available. Users are required to pay $4000US for a license to AutoCAD in to obtain the specs for this newest release of DXF file format. The official specification for DXF R12 may be found in the AutoCAD Manual Release 12: #C10 AutoCAD Customization Manual, Release 12, Autodesk Inc., 1992, pp. 241-81. #C21 The specification for DXF R12 has also been released in electonic form and is available in several of the Internet file format archives, such as: #C10 ftp://avalon.vislab.navy.mil/pub/format_specs/dxf_r12.txt.Z #C21 The spec for the most current version, DXF R13, is available at: #C10 ftp://ftp.synapse.net/private/c/cadsyst/misc/r13dxf.zip #C21 Many books detail the DXF format, including: #C10 The AutoCAD Database Book, F.H. Jones and L. Martin, Ventana Press, ISBN 0-940087-04-9. Order: 919.490.0062 voice. AutoCAD, The Complete Reference, 2nd Ed., Johnson, N., McGraw-Hill, New York, NY, 1991. #C21 Additonal information may be obtained directly from Autodesk: #C10 Autodesk Inc. Autodesk Developer Marketing 2320 Marinship Way Sausalito, CA 94965 Voice: 415.491.8719 FTP: ftp://ftp.autodesk.com WWW: http://www.autodesk.com #C21 ------------------------------ #C30 Subject: 14. EPS - Encapsulated PostScript #C21 The PostScript Language Software Development Kit is available from the creator of PostScript, Adobe Systems: #C10 Adobe Systems Inc. Attn: Adobe Systems Developer Support 1585 Charleston Road P.O. Box 7900 Mountain View, CA 94039-7900 Voice: 415.961.7900 Voice: 800.344.8335 Fax: 415.961.3769 #C21 ------------------------------ #C30 Subject: 15. FBM - Fuzzy Bitmap #C21 FBM is the native file format of the Fuzzy pixmap image manipulation and conversion toolkit written by Michael L. Mauldin at Carnegie Mellon University. Code to manipulate FBM (and many other) file formats is found in the FBM distribution: #C10 ftp://nl.cs.cmu.edu/usr/mlm/ftp/fbm.tar.Z #C21 ------------------------------ #C30 Subject: 16. FFIVW - File Format for the Interchange of Virtual Worlds #C21 FFIVM is an ASCII-based, object-oriented format used to describe virtual objects and worlds. This format is not intended to be a native file format of any hardware or software platform, but instead to be used as an interchange medium used for converting one VRML format to another. The FFIVM specification proposal may be found at: #C10 http://vrml.wired.com/proposals/ffivw.html #C21 Questions about FFIVW should be directed to: #C10 Bernie Roehl Kerry Bonin <74367.1630@compuserve.com> #C21 ------------------------------ #C30 Subject: 17. GIF - Graphics Interchange Format #C21 GIF is a data stream-oriented file format used to define the transmission protocol of LZW-encoded bitmap data. GIF images may be up to eight bits (256 colors) in depth and are always compressed. Despite the fact that GIF supports only 8-bits worth of colors, and the multimedia extensions introduced in the 89a release have not been widely utilized, GIF still remains a popular choice for storing lower resolution image data. The GIF89a specification is available via many BBSs and on-line information services. You may also obtain the specification directly from CompuServe: #C10 CompuServe Incorporated Attn: Graphics Technology Department 5000 Arlington Center Boulevard Columbus, OH 43220 Voice: 614.457.8600, 800.848.8199 FTP: ftp://ftp.compuserve.com WWW: http://www.compuserve.com #C21 Note: Any software created or modified after 01 January 1995 that supports the capability of reading and/or writing GIF files must obtain a patent license agreement from Unisys Corporation. See Part I of the FAQ for more details on the Unisys GIF-LZW license agreements. ------------------------------ #C30 Subject: 18. GKS - Graphics Kernel System #C21 GKS is a standard specifying the input and output primitives for displaying 2D and 3D graphical data. Although GKS has no native file format, the CGM (Computer Graphics Metafile) format is often closely associated with its use. The following ISO documents describe the GKS standard: #C10 ISO 7942 Functional Specification ISO 8651-1 Fortran Binding ISO 8651-2 Pascal Binding ISO 8651-3 Ada Binding ISO 8651-4 ISO 8805 GKS-3D ISO 8806 GKS-3D Bindings #C21 These documents are available from ISO, ANSI, and CSA (see the CGM section for the addresses of these organizations). ------------------------------ #C30 Subject: 19. GRIB - Gridded Binary #C10 [ To be done ] #C21 ------------------------------ #C30 Subject: 20. HDF - Hierarchical Data Format #C21 HDF is an object-oriented interchange file format used to transport image data from one machin architecture or operating system to another with no conversion problems or loss of data. Both 8- and 24-bit raster images are supported, color palettes, and data compression (RLE, Incomp, and JPEG). The latest version of HDF is 3.3 and comes with a complete library of functions for manipulating HDF files, including the netCDF library by Unidata. Information on HDF is available from The HDF Information Server maintained by the National Center for Supercomputing Applications: #C10 http://hdf.ncsa.uiuc.edu:8001/ #C21 The HDF FAQ is specifically located at: #C10 http://hdf.ncsa.uiuc.edu:8001/HDF-FAQ.html #C21 The HDU 3.3 User's Guide in both PostScript and MIF format: #C10 ftp://ftp.ncsa.uiuc.edu/HDF/Documentation/HDF3.3/Users_Guide/HDF3 #C21 Source code for HDF may be FTPed from: #C10 ftp://ftp.ncsa.uiuc.edu/HDF #C21 And HDF-related discussions may also be found on the Usenet newsgroup sci.data.formats and in the FAQ for that newsgroup. ------------------------------ #C30 Subject: 21. HPGL - Hewlett-Packard Graphics Language #C21 Hewlett-Packard Graphics Language (HP-GL/2) #C10 [ To be done ] #C21 ------------------------------ #C30 Subject: 22. HPPCL - Hewlett-Packard Printer Control Language #C21 PCL is capable of rendering both raster and vector graphics. The official specification and toolkit for PCL is contained in the following Hewlett-Packard manuals: #C10 PCL 5 Printer Language Technical Reference Manual PCL 5 Developer's Guide, 3rd Edition, Part No. 5002-1847 #C21 The technical reference manual contains a complete description of PCL 5. The developer's guide contains many software examples illustracting how to design PCL-compatable software. These maunals may be obtained directly from Hewlett-Packard. ------------------------------ #C30 Subject: 23. IFF - Interchange File Format #C10 [ To be done ] #C21 ------------------------------ #C30 Subject: 24. IGES - Initial Graphics Exchange Specification #C21 IGES is a set of protocols for the transfer and display of graphical information on remote devices via a telephone or computer communications network. IGES does not define any new graphical file formats, but instead uses existing formats (such as CGM) to encapsulate graphical data. IGES is associated with the NCGA (National Computer Graphics Association) and is part of the U.S. Product Data Association (USPRO) and the IGES/PDES Organization (IGO). The NCGA administers the National IGES User Group (NIUG), which provides access to information on IGES. To obtain the IGES specification, you must be a member of both NIUG and a Regional Interest Group (RIG). The IGES specification is available through the NCGA for $100US. For more information about the NIUG, RIGs, and IGES, contact: #C10 National Computer Graphics Association 2722 Merrilee Drive Suite 3200 Fairfax, VA 22031 USA Voice: 703.698.9600 #C21 ------------------------------ #C30 Subject: 25. IMJ - Image JPEG #C21 IMJ was created by Pegasus Image Corporation as a variation of the JFIF file format. IMJ is essentially a JFIF file with a Microsoft Windows BMP header and enhanced palette optimization. The IMJ format is used in several screensaver applications, and by orgainizations such as Delrina and the National Center for Missing Children. See the section describing the PIC - Pegasus Imaging Corporation Format for more information. ------------------------------ #C30 Subject: 26. JBIG - Joint Bilevel Image Group #C21 JBIG is a lossless method for compressing black and white (1-bit) raster image data. Its primary benefit is as a method for transmitting bi-level image data across a communications channel. JBIG's progressive encoding scheme allows lower resolution version of the image to be sent first, followed by higher resolution images which build on the previously transmitted data (e.g. 75, 150, 300, 450, and 600 DPI). This capability makes JBIG ideal for replacing less-efficient document imaging transmissions methods, such as CCITT Group 3 & 4, but thus far JBIG has not been marketed in such a way as to make this possible. There is no official JBIG file format. You just dump a JBIG data stream into a disk for tape file, give it the extension JBG or JBIG, and you have a JBIG file. JBIG is jointly sponsored by the ITU (CCITT) and ISO/IEC JTCI/SC29 committees. The JBIG standard may be found in the following documents: #C10 Information technology -- Coded representation of picture and audio information -- Progressive bi-level image compression, ISO/IEC 11544:1993 ITU/CCITT Recommendation T.82 #C21 ------------------------------ #C30 Subject: 27. JFIF - JPEG File Interchange Format #C21 JFIF is a data stream-oriented file format used to define the transmission of JPEG-encoded bitmap data. The specification for JFIF may be obtained directly from C-Cube Microsystems: #C10 C-Cube Microsystems Attn: Scott Sinclair Corporate Communications 1778 McCarthy Blvd. Milpitas, CA 95035 Voice: 408.944.6300 Fax: 408.944.6314 #C21 The Independent JPEG Group archive on ftp.uu.net also contains an on-line copy of the JFIF specification and additional JPEG information as: #C10 ftp://ftp.uu.net/graphics/jpeg/jfif.ps.gz ftp://ftp.uu.net/graphics/jpeg/jpeg.documents.gz #C21 ------------------------------ #C30 Subject: 28. MGF - Materials and Geometry Format #C21 MGF is an ASCII-based 3D rendering format designed to model surface geometry and materials for the purpose of visible-light simulation and rendering. The overall objective of this format is to provide a very simple yet fairly complete modeling language that does not place unreasonable demands on the applications programmer or the object library creator. The format specification is available bundled with an MGF file reader and is distributed in the file mgflib0.7.tar.Z on the following sites: #C10 http://radsite.lbl.gov/mgf/HOME.html ftp://hobbes.lbl.gov/www/mgf #C21 The MGF software is currently in an alpha release stage, which means the language may change in some incompatible ways between now and the first release. Use this software and data in this package at your own risk. Questions about MGF should be directed to: #C10 Greg Ward Voice: 510.486.4757 Fax: 510.486.4089 Email: GJWard@lbl.gov #C21 ------------------------------ #C30 Subject: 29. MIFF - Magick Image File Format #C21 MIFF is a bitmap format native to the ImageMagick toolkit which runs under the X Window System. ImageMagick is capable of displaying and converting a variety of still and animated graphics file formats. The specification for MIFF is available in the ImageMagick distribution available from: #C10 ftp://ftp.wizards.dupont.com/pub/ImageMagick/ImageMagick-3.7.tar.gz #C21 For more information about ImageMagick and MIFF, contact: #C10 duPont de Nemour & Company Attn: John Cristy Central Research and Development Experimental Station P.O. Box 80328 Room 162-A Wilmington, DE 19880-0328 Voice: 302.695.1159 Email: cristy@dupont.com #C21 ------------------------------ #C30 Subject: 30. NAPLPS - North American Presentation Layer Protocol Syntax #C21 NAPLPS is a protocol for transferring ASCII-based graphical information to remote terminals via a communications channel (telephone systems, computer networks, and so forth). It is specifically designed to provide usable information transfer rates, even at data rates as low as 2400bps. NAPLPS is used by many Videotext services, Prodigy, the commercial on-line information service, and in standalone information kiosk systems. Although there is no NAPLPS file format, NAPLPS data streams are often saved as files, and the files are then referred to as using the "NAPLPS file format". The NAPLPS specification is a standards documents available through ANSI, ISO, or CSA. (See the CGM section for the addresses of these organizations). The CSA document (T500-1983) also contains a supplement (1-1991) which is not included in the ANSI version of this standard. Further information may be found in the February, March, April, and May 1983 issues of Byte Magazine. These articles explain much of the NAPLPS coding system and discuss the potential for NAPLPS. Michael Dillon has authored a paper on NAPLPS and started a NAPLPS section on SIMTEL20, which may be access via the mirror site: #C10 ftp://oak.oakland.edu/pub/simtel/msdos/naplps #C21 Michael Dillon may be contacted at: #C10 CompuServe: 71532,137 Internet: mpdillon@halcyon.halcyon.com BBS: 604.546.2705 #C21 The BBS also contains NAPLPS Shareware and art. ------------------------------ #C30 Subject: 31. NFF - Neutral File Format #C21 NFF is a minimal scene description language used to test rendering algorithms and efficiency schemes. It supports basic geometry of objects, surface characteristics, placement of lights, color of objects, and the viewing angle of the human eye. NFF is ASCII-based and is used with the Standard Procedural Database (SPD) software package used for creating databases for testing rendering schemes. The specification for NFF is available on numerous FTP sites which archive file format documents, such as: #C10 ftp://zamenhof.cs.rice.edu/pub/graphics.formats #C21 and is available along with the SPD test programs, which produce NFF objects: #C10 ftp://ftp.princeton.edu/pub/Graphics/SPD #C21 You may also contact the author of NFF: #C10 Eric Haines 3D/Eye Inc. 1050 Craft Road Ithica, NY 14850 Email: erich@eye.com #C21 ------------------------------ #C30 Subject: 32. NFF - WorldToolKit Neutral File Format #C21 The WorldToolKit Neutral File Format is a creation of Sense8 for their WorldToolKit software product. WorldToolKit is a C language library providing the functionality needed to do virtual reality, including file parsing, sensor drivers, object management, behavior, and rendering. Sense8's NFF format was loosely adapted from the Videoscape (.geo) format, with the addition of 12-bit color, per-polygon texture application, and portals. It was later extended to support vertex normals, 24-bit color, and vertex uv coordinates. The current version of NFF is 2.1. Sense8 also supports a binary format of NFF called BFF (.bff file extension) The BFF format layout and order is identical to the ASCII version, with the exception that only 24-bit, and not 12-bit, colors are not supported. The WorldToolKit Neutral File Format was created and is maintained by: #C10 Sense8 100 Shoreline Hwy. Ste. 282 Mill Valley, CA 94941 Voice: 415.331.6318 Fax: 415.331.9148 Email: info@sense8.com #C21 Sense8's NFF specification is available via FTP at: #C10 ftp://avalon.vislab.navy.mil/pub/format_specs #C21 Questions about Sense8's NFF format should be directed to: #C10 Ben Discoe #C21 ------------------------------ #C30 Subject: 33. NITF - National Imagery Transmission Format #C21 The National Imagery Transmission Format Standard (Version 2.0) is documented as a collection of military standards documents. The actual file format is documented in the following standard: #C10 MIL-STD-2500, National Imagery Transmission Format (Version 2.0) for the National Imagery Transmission Format Standard, 18 June 1993 #C21 The remaining standards are as follows: #C10 MIL-HDBK-1300, National Imagery Transmission Format Standard (NITFS), 18 June 1993 MIL-STD-3201, Computer Graphics Metafile (CGM) Implementation Standard for the National Imagery Transmission Format Standard, 18 June 1993 MIL-STD-188-196, Bi-Level Image Compression for the National Imagery Transmission Format Standard, 18 June 1993 MIL-STD-188-197 Adaptive Recursive Interpolated Differential Pulse Code Modulation (ARIDPCM) Compression Algorithm for the National Imagery Transmission Format Standard, 18 June 1993 MIL-STD-188-198A, Joint Photographic Experts Group (JPEG) Image Compression for the National Imagery Transmission Format Standard, 15 December 1993 MIL-STD-188-199, Vector Quantization Decompression for the National Imagery Transmission Format Standard, 27 June 1994 MIL-STD-245-44500, Tactical Communications Protocol 2 (TACO2) for the National Imagery Transmission Format Standard, 18 June 1993 JIEO Circular 9008, National Imagery Transmission Format Standards (NITFS) Certification Test & Evaluation Program Plan, 30 June 1993 #C21 The NITFS standards may be obtained via FTP from the ITSI (Information Technology Standards Integrated) BBS at: #C10 ftp://jcdbs.2000.disa.mil/pub/library #C21 ITSI BSS may also be reached by modem at 703.834.6501 (14.4kbps, N-8-1). To receive hardcopies any or all of these documents, send a request via mail, fax, or email to: #C10 DISA/JIEO/CFS/TBCE c/o Logicaon Fay Mignone 1831 Wiehle Avenue Reston, VA 22090 USA Fax: 703.318.1098 Attn: Fay Mignone Email: mignone@cdbs.itsi.disa.mil #C21 or: #C10 Defense Information Systems Agency Center for Standards Carol Ciepiela Attn: TBCE, Rm 3304 10701 Parkridge Blvd Reston, VA 22091 USA Voice: 703.487.3536 Email: edi@itsi.disa.mil #C21 Questions may be directed to: #C10 NITFS Certification Test Facility Voice: 602.538.5458 x5494 #C21 ------------------------------ #C30 Subject: 34. OFF - Object File Format #C21 OFF was developed in 1986 at Digital Equipment Corporation's Workstation Systems Engineering for the interchange and archiving of 3D objects. OFF is an ASCII-based format and is independent of languages, devices, and operating systems. The specification for OFF is: #C10 Rost, Randi, OFF--A 3D Object File Format, November 6, 1986 (updated October 12, 1989). #C21 The OFF archive is available from: #C10 ftp://gatekeeper.dec.com/pub/DEC #C21 This archive contains the format specification, tools, and objects. It is not currently supported and is copyrighted. ------------------------------ #C30 Subject: 35. PBM - Portable Bitmap #C21 The Portable greymap file format is part of the Extended Portable Bitmap Utilities (PBMPLUS). PBM is used as an intermediate format for storing monochrome bitmap information generated by the PBMPLUS toolkit. PBM files may be either binary or ASCII and store data one-bit-per-pixel in size. Information and source code for PBM can be found in the distribution for PBMPLUS located at: #C10 ftp://ftp.wustl.edu/graphics/graphics/packages/pbmplus/pbmplus10dec91.tar.Z #C21 The specification for the PBM format can also be found in the manual page for pbm(5) on many Unix systems. ------------------------------ #C30 Subject: 36. PCX - ZSoft Paint #C21 PCX is one of the oldest bitmapped formats popularized by MS-DOS paint programs that first appeared in the early 1980's. PCX files may store mapped and unmapped image data from 1- to 24-bits in pixel depth, always contain RLE-compressed image data, and are recognized by almost all still-image graphics programs ever written. But because of the kludged evolution of the PCX format (caused partly by the efforts of Zsoft to continue to support the ever-changing world of graphics display adapters) it is generally advised that the MS Windows BMP format be used in place of PCX whenever possible. Once upon a time ZSoft was bought by Wordstar, who was then bought by SoftKey. It is not currently known if anyone distributes the original, poorly written, specification for PCX. No matter, as most book on graphics file format completely describe the PCX format. ------------------------------ #C30 Subject: 37. PDF - Portable Document Format #C21 PDF files are viewable using Adobe's Acrobat Reader 2.0 program. PDF was created and is maintained by Adobe Systems Incorporated: #C10 Adobe Systems Incorporated 1585 Charleston Road P.O. Box 7900 Mountain View, CA 94039-7900 Voice: 415.961.4400 Voice: 415.961.4111 (Developer Support) Fax: 415.961.3769 #C21 Sample PDF images files may be found at: #C10 ftp://ftp.adobe.com/pub/adobe/Acrobat/PDFsamples #C21 The Adobe Acrobat Software Developer's Kits for Unix, Macintosh, Microsoft Windows, and MS-DOS may be found at: #C10 ftp://ftp.adobe.com/pub/adobe/Acrobat/SDK #C21 Additional PDF information may also be gathered from Adobe's home Web page: #C10 http://www.adobe.com #C21 ------------------------------ #C30 Subject: 38. PDS - Planetary Data Systems Format #C21 PDS was created by the Planetary Branch of the National Aeronautics and Space Administration (NASA) to store solar, lunar, and planetary data collected both on Earth and by spacecraft. And as with most U.S. Government documents, the specification is quite large and spread over several documents: #C10 Jet Propulsion Laboratory, Standard for the Preparation and Interchange of Data Sets, JPL Document D-4683, NASA, Pasadena, CA, 1988. Jet Propulsion Laboratory, Data Preparation Workbook, JPL Document D-7669, NASA, Pasadena, CA, 1990. Jet Propulsion Laboratory, Planetary Data System Standards Reference, JPL Document D-4683, NASA, Pasadena, CA, 1990. Jet Propulsion Laboratory, Specification for the Object Description Language, NASA, Pasadena, CA, 1990. #C21 These documents are available from: #C10 NASA Planetary Branch Jet Propulsion Laboratory Mail Stop 525-3610 4800 Oak Grove Drive Pasadena, CA 91109 Voice: 818.354.7587 Email: PDS_Operator@jplpds.jpl.nasa.gov #C21 ------------------------------ #C30 Subject: 39. PGM - Portable Greymap #C21 The Portable greymap file format is part of the Extended Portable Bitmap Utilities (PBMPLUS). PGM is used as an intermediate format for storing greyscale bitmap information generated by the PBMPLUS toolkit. PGM files may be either binary or ASCII and store pixel values up to 8 bits in size. Information and source code for PGM can be found in the distribution for PBMPLUS (see the section on the PBM format for information on PBMPLUS). The specification for the PGM format can also be found in the manual page for pgm(5) on many Unix systems. ------------------------------ #C30 Subject: 40. PIC - Pegasus Imaging Corporation Format #C10 Pegasus Image Corporation 4350 W. Cypress Street, Suite 908 Tampa, FL 33607 Voice: 813.875.7575 Fax: 813.875.7705 BBS: 813.874.5515 Name: guest guest, Password: demo CIS: GO PEGASUS #C21 ------------------------------ #C30 Subject: 41. PNG - Portable Network Graphics #C21 PNG (pronounced "ping") is a new bitmap format which is currently in development. Its creation is an attempt to give the graphics community an alternative to the shortcomings and misgivings found in most popular file formats. The current legal situation involving the GIF format may also have something to do with it too :-) The following paragraph, excerpted from the PNG (Portable Network Graphics) specification explains the basic rationale behind the format: #C10 The PNG format is intended to provide a portable, legally unencumbered, simple, lossless, streaming-capable, well-compressed, well-specified standard for bitmapped image files which gives new features to the end user at minimal cost to the developer. #C21 The PNG specification is now in its 10th draft. This draft is considered finalized to the point that software may be safely written without the worry of the specification changing in non-backwardly compatable ways. A public draft of the current PNG specification may be found at: #C10 http://sunsite.unc.edu/boutell/png.html ftp://swrinde.nde.swri.edu/pub/png/documents/png10.txt ftp://ftp.uu.net:/graphics/png/documents/ #C21 Questions about PNG may be asked on the comp.graphics.misc newsgroup, or via email at: #C10 png-info@uunet.uu.net #C21 or directed to the principle author of the PNG specification: #C10 Thomas Boutell #C21 PNG developers may join the PNG mailing list. Send email to #C10 png-info@uunet.uu.net #C21 and ask for more information. A human will be reading your request to join the list, so make it good. Other PNG mailing lists include: #C10 png-list@dworkin.wustl.edu png-announce@dworkin.wustl.edu png-implement@dworkin.wustl.edu #Y-30 #C21 General PNG discussion Announcements related to PNG Implementation discussion These lists contain a general discussion of PNG, announcements related to PNG, and discussions regarding PNG implementation. To find out more about the mailing list server, send mail to png-list-request@dworkin.wustl.edu with the word "help" (and nothing else) in the message body. The official PNG FTP archive is: #C10 ftp://ftp.uu.net/graphics/png/ #C21 A reference implementation in portable C of a PNG reader and writer is available at: #C10 ftp://ftp.uu.net/graphics/png/src/ #C21 And test PNG images for your benchmarking pleasure: #C10 ftp://ftp.uu.net/graphics/png/images/ ftp://ftp.photodex.com/PNG/images/ #C21 PNG materials can also be had in great profusion from: #C10 ftp://swrinde.nde.swri.edu/pub/png/ #C21 All programs on this site are in beta test and should be used carefully. In the case of questionable implementation, the specification is to be considered corrent and the code in error. The PNG group has a home page with pointers to many other PNG resources at: #C10 http://quest.jpl.nasa.gov/PNG/ #C21 Group 42 is the author of the PNGLIB support library for developer's using the PNG file format. Their Web page contains a developer's section which includes the PNGLIB library, PNG format specification, Compression Library, and Image Test Suite. A Freeware version of theis library is currently available. Group 42 may be reached at: #C10 Group 42, Inc. Voice: 800.520.0042 Voice: 513.831.3400 Email: info@group42.com WWW: www.group42.com #C21 And PNG's very first journal article has appeared: #C10 PNG: The Portable Network Graphic Format, Dr. Dobb's Journal, Lee Daniel Crocker, #232 July 1995 (Vol 20, Issue 7), pp. 36-44. #C21 The code for the above issues are available at: #C10 ftp://ftp.mv.com/pub/ddj/1995/1195.07/ptot.zip #C21 And a rather CompuServe-biased official press release: #C10 http://www.compuserve.com/new/news_rel/png2.html #C21 ------------------------------ #C30 Subject: 42. PPM - Portable Pixmap #C21 The Portable pixmap file format is part of the Extended Portable Bitmap Utilities (PBMPLUS). PPM is used as an intermediate format for storing color bitmap information generated by the PBMPLUS toolkit. PPM files may be either binary or ASCII and store pixel values up to 24 bits in size. Information and source code for PPM can be found in the distribution for PBMPLUS (see the section on the PBM format for information on PBMPLUS). The specification for the PPM format can also be found in the manual page for ppm(5) on many Unix systems. ------------------------------ #C30 Subject: 43. POL - InnovMetric Software Polygon Models Format #C21 POL is the native 3D file format for software products created by InnovMetric Software. The POL format was created to fill the need of storing data representing multi-contour, simple, planular, polygons using a binary file format. InnovMetric Software is developing a complete line of software products for building 3-D polygonal models using a 3-D imaging system. Two of these software tools are targeted at real-time 3-D graphics applications. IMCompress and IMFilter are two complementary tools for optimally reducing the number of polygons in a 3-D model. IMCompress uses a surface-based algorithm to downsize highly redundant models such as Digital Terrain Models and polygonal models generated by a CAD or a 3-D imaging system. IMFilter uses a volume-based algorithm to create ultra-compact models (20 to 500 triangles) for level of details management in applications requiring real-time 3-D graphics. The POL file format specification is primarily distributed as Appendix B of the IMCompress User's Guide published by InnovMetric Software. The specification is also available in PostScript format as the file pol.ps in a few of the graphics file format specification archived listed in part 1 of this FAQ. POL was created and is maintained by: #C10 InnovMetric Software Inc. 2065 Charest ouest, Suite 218 Sainte-Foy, Quebec Canada, G1N 2G1 #C21 Questions about POL may be directed to: #C10 Marc Soucy #C21 ------------------------------ #C30 Subject: 44. POV - Persistence of Vision Raytracing #C21 The POV-Ray format is used to store a scene description language used by the POV-Ray ray tracing software package. POV-Ray files are always ASCII to allow easy transportation between different file systems. The specification for the POV file format and scene description language is found in the file povray.doc in the POV-Ray distribution. You may obtain this file (and the entire POV-Ray package) from the official POV-Ray FTP archive site: #C10 ftp://alfred.ccs.carleton.ca/pub/pov-ray/POV-Ray2.2/ #C21 Questions about POV-Ray may also be direct to: #C10 Drew Wells POV-Team Leader 73767.1244@compuserve.com #C21 The following is an excellent book on ray tracing using the POV-Ray tracing software package for the PC: #C10 Ray Tracing Creations: Generate 3D Photo-Realistic Images on the PC, Drew Wells and Chris Young, Waite Group Press 1993. #C21 ------------------------------ #C30 Subject: 45. PS - PostScript #C21 PostScript was created and is maintained by Adobe Systems Incorporated: #C10 Adobe Systems Incorporated 1585 Charleston Road P.O. Box 7900 Mountain View, CA 94039-7900 Voice: 415.961.4400 Voice: 415.961.4111 (Developer Support) Fax: 415.961.3769 BBS: 206.623.6984 (14.4-N-8-1) #C21 The primary source of PostScript formation may be found in the Adobe PostScript Langauge books: #C10 Red Book: Postscript Language Reference Manual, 2nd ed. Adobe Systems Inc., Addison-Wesley. ISBN 0-201-18127-4, $26.95US softcover Blue Book: Postscript Language Tutorial and Cookbook, Adobe Systems Inc., Addison-Wesley. ISBN 0-201-10179-3, $16.95US softcover Green Book: PostScript Language Program Design, Adobe Systems Inc., Addison-Wesley. ISBN 0-201-14396-8, $22.95US softcover Black Book: Adobe Type 1 Font Format Specification, Adobe Systems Inc., Addison-Wesley. ISBN 0-201-57044-0, $14.95US softcover Purple Book: Programming the Display PostScript System with NeXTstep, Adobe Systems Inc., Addison-Wesley. ISBN 0-201-58135-3, $26.95US softcover #C21 You may order these books directly from Adobe Systems in Mountain View, California, by calling 1.800.83.FONTS (U.S. and Canada only) or 415.961.4400 (ask for "Inside Sales"). Or from Hayden Publishing at 1.800.428.5331. Additional information on PostScript may be found on Adobe's FTP server and Web site: #C10 ftp://ftp.adobe.com/pub/adobe/DeveloperSupport/Technotes http://www.adobe.com #C21 The Usenet newsgroup comp.lang.postscript covers issues relating to the Adobe PostScript language. The PostScript FAQ is available at: #C10 http://www.cis.ohio-state.edu/hypertext/faq/usenet/postscript-faq/top.html #C21 The Usenet newsgroup comp.fonts also covers issues relating to fonts. The comp.fonts FAQ is available at: #C10 http://jasper.ora.com/comp.fonts/FAQ #C21 The Usenet newsgroup comp.sources.postscript contains source code of PostScript programs. Other newsgroups that may be of interest are: comp.periphs.printers, comp.laser-printers, comp.text.pdf, comp.text.desktop and comp.publish.prepress. ------------------------------ #C30 Subject: 46. PSD - Adobe Photoshop #C21 PSD is the native bitmap file format of the Adobe Photoshop graphical editing application. PSD files have the extension .PSD under MS Windows and the file type code 8PBS on the Macintosh. Other file formats associated with Photoshop include: Arbitrary Map (.AMP), Brushed (.ABR), Color Table (.ACT), Colors (.ACO), Command Buttens (.ACM), Curves (.ACV), Duotone Options (.ADO), Halftone Screens (.AHS), Hue/Saturation (.HSS), Ink Colors Setup (.API), Custom Kerenel (.ACF), Levels (.ALV), Monitor Setup (.AMS), Replace Color/Color Range (.AXT), Scratch Area (.ASR), Selective Color (.ASV), Separation Setup (.ASP), Separation Tables (.AST), and Transfer Function (.ATF). The format specification for PSD and other file formats associated with Adobe Photoshop may be found in the document PSAPIDOC.* (distributed in the Microsoft Write, Macintosh MacWrite, and Adobe Acrobat format) under the heading "Document File Formats". These documents are part of the Photoshop Plug-In Software Developers Kit, available via FTP and from the Adobe Developers Association's home page: #C10 http://www.adobe.com/Support/ADA.html ftp://ftp.adobe.com/pub/adobe/Applications/Photoshop/*/Plug-In-SDK/ #C21 This SDK is also available directly from Adobe (see the PostScript section for information on how to contact Adobe Systems, Inc.). ------------------------------ #C30 Subject: 47. RAD - Radience #C21 RAD is the native file format for the public domain Unix Radience radiosity renderer. The RAD specification and Radience package are available at: #C10 http://radsite.lbl.gov/radience/HOME.html #C21 ------------------------------ #C30 Subject: 48. RAS - Sun Rasterfile #C21 Sun rasterfile is the native bitmap format of Sun Microsystem Unix systems. The rasterfile format has become more wide-spread with the growing popularity of the SunOS operating system and Sun SPARCStation family of Unix workststaions. Sun rasterfiles store images up to 32 bits in pixel depth and support a basic for of run-length data compression. The primary source of information for Sun Rasterfiles is the SunOS include file /usr/include/rasterfile.h and the rasterfile online manual page: #C10 Sun Microsystems, rasterfile (5), Sun OS 4.0 Programmer's Manual, 1990. #C21 The following jounal article is devoted to the Sun rasterfile: #C10 McGee, Format for Byte-Encoded Rasterfiles, Sun-Spots Digest, Volume 6, Issue 84. #C21 And several books on graphics file formats also feature the rasterfile format. ------------------------------ #C30 Subject: 49. RAY - Rayshade #C21 Rayshade is a ray-tracing application for the MS-DOS environment. The Rayshade format is the native scene description language used by Rayshade. And like most 3D scene-rendering formats it is ASCII-based and supports most features commonly found in these formats. The specification is available in the Rayshade distribution on many BBSs and FTP archive sites. The format is detailed in the document: #C10 Rayshade 4.0 Quick Reference #C21 The author may be contacted at: #C10 Princeton University Attn: Craig Kolb Department of Computer Science 35 Olden Street Princeton, NJ 08544 Email: cek@princeton.edu #C21 ------------------------------ #C30 Subject: 50. RIB - Renderman Interface Bytestream #C21 The RenderMAN file format specification may be found in the following document available from Pixar: #C10 The RenderMAN Interface, Version 3.1, September 1989. San Rafael, CA. Pixar 1001 West Cutting Blvd. Richmond, California 9484 USA Voice: 415.236.4000 #C21 Also of interest is the following publication: #C10 The RenderMan Companion: A Programmer's Guide to Realistic Computer Graphics, Steve Upstill, Addison-Wesley Publishing Company, ISBN 0-201-50868-0, $26.95 #C21 ------------------------------ #C30 Subject: 51. RIFF - Microsoft Resource Interchange File Format #C10 Microsoft Corporation Attn: Multimedia System Group Product Marketing One Microsoft Way Redmond, WA 98052-6399 Voice: 206.882.8080 BBS: 206.637.9009 #C21 Information on RIFF may be found in the following documents: #C10 Microsoft Windows Multimedia Programmer's Guide, Microsoft Corporation, Microsoft Press, Redmond, WA. Microsoft Windows Multimedia Programmer's Reference, Microsoft Corporation, Microsoft Press, Redmond, WA. #C21 The specification is also available in the Microsoft Multimedia Development Kit (MDK), on Disk 8 of the Microsoft Developer's Network CD distribution, and as a MS Windows help file on the FTP archive site: #C10 ftp://ftp.microsoft.com/developer/MSDN/CD8/RIFFNE.ZIP #C21 ------------------------------ #C30 Subject: 52. RIX - ColoRIX Image File #C21 ColorRIX is the native bitmap format of the ColorRIX VGA Paint application for MS-DOS. The ColorRIX format is documented in the ColorRIX VGA Paint manual distributed with the ColorRIX program. The last known address of RIX Softworks was: #C10 RIX SoftWorks Inc. Attn: Richard Brownback or Paul Harker 18023 Sky Park Circle, Suite J Irvine, CA 92714 Voice: 714.476.8266 Voice: 714.476.8486 #C21 ColorRIX is also bundled with several different VGA cards and the specification may also be found on numerous FTP archive sites. ------------------------------ #C30 Subject: 53. SDML - Spacial Data Modeling Language #C21 SDML is a spatial description language used for storing CAD and GIS data, such as found in Landscape Planning, Design, and Architectural databases. SDML currently exists in two versions: the old SDML format and the new (Version 1.0) format. The old format is derived from the ASCII-based format used in the Silicon Graphics CLRview and PolyTRIM software environments. The new format, released in 05Feb95, is a more detailed, capable, and size-optimized revision of the old SDML and supports all the features of the Silicon Graphics CLRMosaic software. The New SDML specification is available from: #C10 http://www.clr.toronto.edu:1080/CLRMOSAIC/SDML.html #C21 Questions about SDML should be directed to: #C10 Rodney Hoinkes, Head of Design Applications Centre for Landscape Research University of Toronto 230 College St. Toronto, ON, M5S 1A1 Voice: 416.978.3551 Fax: 416.971.2094 Email: rodney@clr.toronto.edu WWW: http://www.clr.toronto.edu/PEOPLE/RODNEY/rodney.html #C21 ------------------------------ #C30 Subject: 54. SGI - Silicon Graphics Image File Format #C21 SGI is the native file format of the limage image library found on Silicon Graphics workstations. The limage library provides a set of functions used to read and write SGI images. The SGI file format is a creation of Paul Haeberli (paul@sgi.com) at Silicon Graphics Computer Systems. The SGI format specification may be found at: #C10 ftp://ftp.sgi.com/graphics/SGIIMAGESPEC #C21 The SGI format is also known as the RGB file format. On SGI workstations you can get info on RGB and the limage library by using the following command: #C10 % man 4 rgb #C21 ------------------------------ #C30 Subject: 55. SHG - Segmented Hyper-Graphic #C21 SHG is a file format used by Microsoft in the WinHelp on-line help facility found in Windows 3.1. This format is used to save a Microsoft Bitmap (BMP) or Windows Metafile (WMF) graphic and store the coordinates of specific areas of the bitmap known as "hotspots". When the bitmap is displayed and the user selects a hotspot, WinHelp jumps to another part of the help documentation via a hyper-text link macro stored in the SHG file. Another file format used with SHG files is the Multiple-Resolution Bitmap (MRB) format. MRB files contain one or more SHG images, each rendered at a different resolution. Several SHG files are typically created using the SHED.EXE utility and then fed into the MRB compiler to create a single MRB file. When WinHelp reads the MRB file it chooses which bitmap most closely matches the resolution of the display. SHG is currently officially undocumented by Microsoft, but the specification may be found at: #C10 ftp://ftp.microsoft.com/developr/drg/Multimedia/SHED.ZIP #C21 Information on SHG and MRB may be found in the following journal article: #C10 .mrb and .shg File Formats, Windows/DOS Developer's Journal, Pete Davis, February 1994 (Vol 5, No 4), pp. 37-46. #C21 Questions about these formats may also be directed to Section 16 (WinHelp/Tools) of forum WINSDK on CompuServe. ------------------------------ #C30 Subject: 56. SPIFF - Still Picture Interchange File Format #C21 The "official" JPEG file format. Part 3 of the JPEG standard now includes a fully defined file format to storing JPEG data. When the JPEG format was standardized, disagreements among ISO committees prevented a standard JPEG file format from being created. The defacto format that appeared was JFIF from C-cube Microsystems. The JFIF format, although now quite wide-spread, is very limited in capability as file formats go. SPIFF is intended to replace the JFIF file format, adding features (more colorspaces, a recognized way of including text blocks, and so forth), and provding a backwards-compatability allowing SPIFF files to be read my most JPEG/JFIF decoders. JFIF, however, has a five-year head start on SPIFF, so the likelyhood of it being completely replaced anytime soon is not good. ------------------------------ #C30 Subject: 57. STL - Stereolithography Interface Format #C21 STL files are the native file format of the SLA CAD software created by 3D Systems of Valencia, CA, USA. STL files may be ASCII or binary in form, although binary is far more common due to the very large resulting size of the CAD data when saved to the ASCII format. ------------------------------ #C30 Subject: 58. TGA - Truevision (Targa) File Format #C21 Copies of the TGA specification, including a sample code disk, may be obtained from Truevision: #C10 Truevision Incorporated 7340 Shadeland Station Indianapolis, IN 46256-39925 Voice: 317.841.0332 Fax: 317.576.7700 BBS: 317.577.8783 FTP: ftp.truevision.com #C21 ------------------------------ #C30 Subject: 59. TIFF - Tag Image File Format #C21 The TIFF format was formerly owned and maintained by the Aldus Developer's Association. Aldus has since merged with Adobe Systems and now the Adobe Developers Association (ADA) maintains the TIFF file format. You may obtain a copy of the TIFF 6.0 specification in PDF format at: #C10 http://www.adobe.com/Support/TechNotes.html #C21 Or from the following FTP site: #C10 ftp://sgi.com/graphics/tiff/TIFF6.ps.Z #C21 You may also contact the ADA directly at: #C10 Adobe Developer Association 1585 Charleston Road P.O. Box 7900 Mountain View, CA 94039-7900 USA Voice: 415-961-4111 FAX: 415-967.9231 BBS: 206-623-6984 FTP: ftp://ftp.adobe.com WWW: http://www.adobe.com/Support/ADA.html #C21 And be sure to visit Niles Ritter's The Unofficial TIFF Home Page at: #C10 http://www-mipl.jpl.nasa.gov/~ndr/tiff/ #C21 Note: Any software created or modified after 01 January 1995 that supports the capability of reading and/or writing bitmapped data stored in a TIFF file and compressed using the LZW algorithm must obtain a patent license agreement from Unisys Corporation. See Part I of the FAQ for more details on the Unisys GIF-LZW and TIFF-LZW license agreements. ------------------------------ #C30 Subject: 60. TRIF - Tiled Raster Interchange Format #C21 TRIF was developed by the Tiling Task Group at the National Institute for the interchange of tiled raster data. TRIF is very similar to the CALS Type II raster format and shares many of the same standards documents. The keeper of TRIF seems to be: #C10 Frankie E. Spielman National Institute of Standards and Technology Voice: 301.975.3257 #C21 Military standards for TRIF include: #C10 Standards for the Interchange of Large Format Tiled Raster Documents, NISTIR 88-4017 (December 1988). Section 4, "A Document Application Profile for the Interchange of Large Format Tiled Raster Documents", contains the application profile definition of a TRIF coded document. Requirements for Raster Graphics Representation in Binary Format, MIL-R-28002A Automated Interchange of Technical Information, MIL-STD-1840A (22 December 1987). Information Processing - Text and Office Systems - Office Document Architecture (ODA) and Interchange Format - Part 1: Introduction and General Principles, ISO 8613/1. Information Processing - Text and Office Systems - Office Document Architecture (ODA) and Interchange Format - Part 2: Document Structures, ISO 8613/2. Information Processing - Text and Office Systems - Office Document Architecture (ODA) and Interchange Format - Part 4: Document Profile, ISO 8613/4. Information Processing - Text and Office Systems - Office Document Architecture (ODA) and Interchange Format - Part 7: Raster Graphics Content Architectures - Tiled Raster Graphics Addendum, Addendum to ISO 8613/7. Specification of Abstract Syntax Notation One (ASN.1), ISO 8824. Specification of Basic Encoding Rules for Abstract Notation One (ASN.1), ISO 8825. #C21 ------------------------------ #C30 Subject: 61. TTF - TypeType Font #C21 The TrueType font file format was created by Apple Computer and is used on the Macintosh and Microsoft Windows 3 operating environments. TTF files may be sent to a PostScript interpreter by first converting them to Adobe Type 42 font files. The TrueType font file specification is: #C10 The TrueType Font Format Specification 1.0, Apple Programmers and Developers Association (APDA), P/N M0825LL/A. #C21 This document is available in Windows 3.1 help format and Word for Windows 2.0 format via anonymous FTP from: #C10 ftp://ftp.microsoft.com/developr/drg/TrueType-Info #C21 Information, programs, and code for working with TrueType files may also be found in this directory. ------------------------------ #C30 Subject: 62. Type 42 Font Format #C21 Type 42 is a PostScript font format used to download TrueType fonts to PostScript interpreters which contain a TrueType rasterizer. A TrueType font is first converted to a Type 42 format font and then read by a PostScript interpreter. Type 42 yields better result than if a TrueType font is converted to the Adobe Type 1 or Type 3 font formats. The specification for the Type 42 font format is: #C10 The Type 42 Font Format Specification, Adobe Developer Support, 1 March 1993, P/N LPS5012. #C21 This document available via FTP as a Tech Note in PostScript format, or as hardcopy when obtained directly from Adobe (see the PostScript section for information on how to contact Adobe Systems, Inc.). ------------------------------ #C30 Subject: 63. URT - Utah Raster Toolkit #C21 URT is the native raster file format of the Utah Raster Toolkit. This toolkit, which first appeared in 1983, is a rich source of bitmap manipulation tools and source code. The toolkit is copyrighted, but distributable on a GNU-like license. The specification for the URT file format is found in the following document of the Utah Raster Toolkit: #C10 Design of the Utah RLE Format, Thomas, Spencer W., University of Utah, Department of Computer Science. #C21 The Utah Raster Toolkit distribution (urt-3.0.tar.Z) may be obtained via FTP from the following sites: #C10 ftp://cs.uath.edu ftp://weedeater.math.yale.edu ftp://freebie.engin.umich.edu #C21 Questions about URT may be directed to: #C10 toolkit-request@cs.utah.edu urt-request@caen.engin.umich.edu #C21 ------------------------------ #C30 Subject: 64. VICAR2 - Planetary File Format #C21 VICAR2 is used to store planetary image data gathered from Earth and by spacecraft. VICAR2 is similar in design and use to the FITS and PDS formats. Information on VICAR2 may be obtained directly from JPL: #C10 NASA Attn: Bob Deen Image Processing Laboratory Jet Propulsion Laboratory 4800 Oak Grove Drive Pasadena, CA 91109 Email: rgd059@mipl3.jpl.nasa.gov #C21 ------------------------------ #C30 Subject: 65. VIFF - Visualization Image File Format #C21 VIFF is the native bitmap graphics file format of the Khoros System environment implemented using the X Window System. The VIFF format specification, including other documents related to the VIFF format, may be found in the Khoros distribution. Chapter 1 of Volume II, Programmer's Manual, the files in the directory src/file_formats, and the viff.h file are the most helpful. The following FTP sites archive the Khoros distribution: #C10 ftp://ftp.eece.unm.edu/pub/khoros ftp://ftp.uu.net/pub/window-sys/khoros #C21 The Khoros Consortium may be contacted at: #C10 Khoral Research Inc. 6001 Indian School Road NE Suite 200 Albuquerque, NM 87110 Voice: 505.837.6500 Fax: 505.881.3842 Email: khoros-request@chama.eece.unm.edu Email: khorus@chama.eece.unm.edu (User's Group) Newsgroup: comp.soft-sys.khoros #C21 ------------------------------ #C30 Subject: 66. VPF - Vector Product Format #C21 VPF is a standard format, structure, and organization for large geographic databases that are based on a georelational data model. VPF is primarily used for organizing and encapsulating such digital geographic databases for transmission. More information on VPF may be found in the newsgroup and FAQ of comp.infosystems.gis. The specification for VPF may be found in the following military standard document: #C10 MIL-STD-600006, Vector Product Format, 13 April 1992 #C21 This MIL-STD may be obtained from: #C10 Naval Publications & Forms Center Code 3051 5801 Tabot Ave. Philadelphia, PA 19120 USA #C21 ------------------------------ #C30 Subject: 67. VRML - Virtual Reality Modeling Language #C21 VRML is a proposed design based on the Silicon Graphics Open Inventor ASCII file format. Originally called the Inventor VRML, this format has evolved into what is now the VRML format. VRML is also called a "Markup Language" for reasons that it is used in a fashion similar to HTML (HyperText Markup Language), but for rendering 3D graphics rather than text. VRML, however, is in no way derived from HTML. The current VRML specification may be obtained from: #C10 http://www.eit.com/vrml/vrmlspec.html #C21 Questions about VRML may be directed to: #C10 Mark Pesce, Enterprise Integration Technology, Inc. Anthony Parsi, Labyrinth Group Gavin Bell, Silicon Graphics, Inc. #C21 The original Inventor-VRML specification may be obtained from: #C10 http://www.sgi.com/Technology/Inventor/VRML/VRMLDesign.html #C21 The Labyrinth VRML specification may be obtained from: #C10 http://vrml.wired.com/proposals.labspec.html #C21 VRML Research and Sample images: #C10 http://www.sdsc.edu/vrml http://www.sgi.com/FreeStuff/Cool-Scene.vrml #C21 ------------------------------ #C30 Subject: 68. WebOOGL - Web Object Oriented Graphics Library #C21 WebOOGL is a OOGL-based format used for describing 3D graphics on the World Wide Web. This format supports the embedding of URL links within 3D objects and allows multiple WebOOGL objects found at different locations on the Web to be combined into a single scene. The WebOOGL specification may be found at: #C10 http://www.geom.umn.edu/docs/weboogl/weboogl.html #C21 Additional information om the use of OOGL as a VRML may be obtained from: #C10 http://vrml.wired.com/proposals/oogl.html #C21 ------------------------------ #C30 Subject: 69. WMF - Windows Meta File #C21 WMF is the native vector file format for the Microsoft Windows operating environment. WMF files are actually a collection of GDI (Graphics Device Interface) function calls also native to the Windows environment. When a WMF file is "played back" (typically using the Windows PlayMetaFile() function) the graphics is rendered. WMF files are device-independant and have no limit to their size. Most books on Microsoft Windows programming contain sections on the internals of WMF files. The closest thing Microsoft has for a specification for the WMF format is in Volume 4 of the Microsoft Windows Software Development Kit Programmer's Reference. Chapter 3 details the internals of the Metafile Format. The Microsoft Knowledge Base (available at ftp://microsoft.com and on the Microsoft Developer Network CD) also contains the complete specification of WMF. I also highly recommend the book: #C10 Inside Windows File Formats, Tom Swan, Sams Publishing 1993. ISBN 0-672-30338-8 $24.95 softcover, 337 pages. #C21 ------------------------------ #C30 Subject: 70. WPG - WordPerfect Graphics Metafile #C21 WPG is the native graphics file format of the WordPerfect Corporation line of software products. For this reason it is common to find WPG files in MS-DOS, Microsoft Windows, Apple Macintosh, and Unix environments. WPG files may store bitmapped or vector graphics data, or Encapsulated PostScript data as well. Bitmapped data may be up to 24-bits deep and selectable from a palette of 256 colors. The WPG specification is published in the WordPerfect Corporation Developer's Toolkit for PC Products. This toolkit is available directly from WordPerfect Information Services: #C10 WordPerfect Information Services Voice: 801.225.5000 #C21 Technical questions regarding WPG may be directed to: #C10 WordPerfect Manufacturer/Developer Relations Department Voice: 801.228.7700 Fax: 801.228.7777 CompuServe: 72567,3612 #C21 And if all else fails: #C10 WordPerfect Corporation 1555 North Technology Way Orem, UT 84057 Voice: 800.526.4477 Fax: 801.222.5077 BBS: 801.225.4414 #C21 ------------------------------ #C30 Subject: 71. XBM - X BitMap #C21 XBM is a native file format of The X Window System and is used for storing cursor and icon bitmaps that are used in the X GUI. XBM files are quite different in that they are actually C language source files that are created to be read by a C compiler rather than a graphical display program. XBM data is typically found in headers (.h files) and are a series of static unsigned char arrays containing the monochrome pixel data. There is one array per image stored in the header. XBM was created by the X Consortium as part of the X Window System. Refer to the /bitmaps directory of the X Window distribution for examples of XBM files. The central FTP distribution site for X version 11 is: #C10 ftp://ftp.x.org #C21 Reference works describing XBM include: #C10 Xlib-C language X Interface, Gettys, James, and Robert W. Scheiffler, Consortium Standard, X Version 11, Release 5, First Revision, August 1991. Xlib Programming Manual, Nye, Adrian, third edition, O'Reilly & Associates, Inc. Sebastopol, CA, 1992. #C21 ------------------------------ #C30 Subject: 72. XPM - X PixMap #C21 XPM is a defacto standard for storing monochome, gray-scale, and color pixmap data to disk under the X Window system. XPM files, like XBM files, are C source code files, with each pixmap being defined as a static char array. The XPM format was created through the work of the KOALA Project at Groupe Bull Research. Questions about XPM may be directed to: #C10 BULL Research c/o INRIA 2004 route des Lucoiles 06565 Valbonne Cedex France Email: lehors@sophia.inria.fr #C21 You may subscribe to the XPM mailing list by sending a subscription request to: #C10 xpm-talk-request@sophia.inria.fr #C21 The XPM library (a collection of utilities that read and write XPM files) version 3.2g (April 1993) may be obtained via FTP from: #C10 ftp://avahi.inria.fr/contrib/xpm.tar.Z ftp://export.lcs.mit.edu #C21 And a collection of XPM files (mostly icons) resides at: #C10 ftp://ftp.x.org/contrib/AIcons #C21 ------------------------------ #C30 Subject: 73. XWD - X Window Dump #C21 XWD is used to store screen dumps created by the xwd client process in the X Window System. The image of any window or the background may be saved (dumped) to an XWD file. Using the following command: #C10 xwd -root > bg.xwd #C21 The background is saved to the file bg.xwd. By replacing the "root" flag with the ID of a window, only that window will be saved to the XWD file. XWD was created by the X Consortium as part of the X Window System. Refer to the /usr/include/X11 directory for header files (XWDFile.h) that define the X10 and X11 versions of the XWD format. The central FTP distribution site for X version 11 is: #C10 ftp://ftp.x.org #C21 ------------------------------ #Seitenende #C31 Subject: III. Kudos and Assertions #C21 ------------------------------ #C30 Subject: 0. Acknowledgments #C21 The following people have made this FAQ take just a little bit longer to read since the last time you looked at it (blame them and not me): #C10 Bjorn P. Brox Mike Beanes John Cristy Michael Dillon Ben Discoe James Durham Bruce Garner Eric Haines Glenn Herteg Chris Komnick Tom Lane Stanley F. Quayle Glenn Randers-Pehrson Marc Soucy #C21 ------------------------------ #C30 Subject: 1. About The Author #C21 The author of this FAQ, James D. Murray, lives in the City of Orange, Orange County, California, USA. He is the co-author of the book Encyclopedia of Graphics File Formats published by O'Reilly and Associates, makes a passable living writing Microsoft Windows applications in C++, and may be reached as jdm@netcom.com, or via U.S. Snail at: P.O. Box 70, Orange, CA 92666-0070 USA. #C10 GCS d-- H++ s g- p? au+ a w+ v++ C+++(++++) US+++ p++>++++ L>++ 3 E--- N++ K- W---$ M-@ V-- po Y+ t++ 5- j>x R+>-- G' tv-->! b+++ D++ B e- u* h- f r-->+++ n++ y* #C21 ------------------------------ #C30 Subject: 2. Disclaimer #C21 While every effort has been taken to insure the accuracy of the information contained in this FAQ list compilation, the author and contributors assume no responsibility for errors or omissions, or for damages resulting from the use of the information contained herein. ------------------------------ #C30 Subject: 3. Copyright Notice #C21 This FAQ is Copyright (C) 1994-95 by James D. Murray. All Rights Reserved. This work may be reproduced, in whole or in part, using any medium, including, but not limited to, electronic transmission, CD-ROM, or published in print, under the condition that this copyright notice remains intact.