The Gerber Format Specification - FrontDoor
The Gerber Format Specification - FrontDoor
The Gerber Format Specification - FrontDoor
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
<strong>The</strong> <strong>Gerber</strong> <strong>Format</strong> <strong>Specification</strong><br />
Scope of the Document<br />
This specification describes a digital format for representing a bi-level image. <strong>The</strong> specification<br />
is intended for the developers of the software that reads and writes <strong>Gerber</strong> files as well as for<br />
user of such software.<br />
<strong>The</strong> document does not specify the following:<br />
Specific physical methods of storing <strong>Gerber</strong> files<br />
User interface or implementation details of rendering <strong>Gerber</strong> files<br />
Designs of the software being created for handling <strong>Gerber</strong> files<br />
Required computer hardware or operating system<br />
Conformance<br />
A <strong>Gerber</strong> file must follow all requirements of the specification. However, there is no obligation to<br />
use any feature other than those explicitly needed.<br />
If a <strong>Gerber</strong> file violates any requirements of the specification or contains invalid parts then the<br />
file is wholly invalid. An invalid <strong>Gerber</strong> file is meaningless and does not represent an image. A<br />
<strong>Gerber</strong> file reader may produce an image for an invalid file, as a diagnostic help, or to help the<br />
user by guessing what the intended image may be, or because the invalidity was not detected,<br />
but this image is never the representation of the file; and as such it is neither right nor wrong.<br />
If the interpretation of a construct is not specified and there is more than one possible<br />
interpretation then the construct is invalid and must not be used.<br />
Some elements of the format are deprecated. <strong>Gerber</strong> writers (creators of <strong>Gerber</strong> files) must no<br />
longer generate them. However such elements may still be present in legacy files. It is up to a<br />
<strong>Gerber</strong> reader (consumer of <strong>Gerber</strong> files) to implement their handling or not.<br />
References<br />
American National Standard for Information Systems — Coded Character Sets — 7-Bit<br />
American National Standard Code for Information Interchange (7-Bit ASCII), ANSI X3.4-1986<br />
Bible, Mark 7:35<br />
Copyright Ucamco NV<br />
xi