23.02.2013 Views

GE - Billy Blue Communication Design

GE - Billy Blue Communication Design

GE - Billy Blue Communication Design

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Rule Weights<br />

• To structure information, use l ⁄2 - point horizontal<br />

and vertical rules<br />

• For emphasis, use heavier 1 1 ⁄2 - point rules.<br />

Horizontal & Vertical Spacing<br />

•Space horizontal rules according to the appropriate<br />

measurement system, described in the<br />

general specifications on the previous page.<br />

• Use vertical rules to divide columns of<br />

information:<br />

- Size the column width to accommodate the<br />

requested information. (Note: Using this<br />

method, if column widths are similar in size,<br />

make them the same.)<br />

- Do not use vertical rules at the far left or right<br />

edges of a check.<br />

-Connect the bottom of each vertical rule to a<br />

horizontal rule. Do not connect the tops<br />

of vertical rules to horizontal rules; instead, align<br />

the top of each vertical rule with the top of the<br />

capital letter in the first line of the typography.<br />

Use l ⁄6 -inch horizontal bars for additional structure<br />

and emphasis. Reverse any typography from<br />

these bars, placing it 3 points from the left edge<br />

of the bar.<br />

Typography & Text Placement<br />

Use only Univers Condensed in checks.<br />

• For general information, use 8/8-point Univers 47.<br />

• For emphasis, use 8/8-point Univers 67.<br />

• To deemphasize information, use 6/6-point<br />

Univers 47.<br />

• For the monetary symbol (for example, $ or £), use<br />

16-point Univers 67, placed flush left 3 points<br />

above the horizontal rule for the check amount.<br />

Place the baseline of check typography 8 points<br />

below or 3 points above a horizontal rule.<br />

Place check typography 3 points to the right of a<br />

vertical rule and end the top of the vertical rule<br />

at the top of the capital letter.<br />

Whenever possible, align typography with other<br />

typography and layout elements.<br />

Guidelines for Checks,<br />

continued<br />

Margins<br />

<strong>GE</strong> Identity Program 270, Forms & Checks <strong>GE</strong> Identity Website: www.ge.com/identity<br />

270.18<br />

When possible, maintain the following minimum<br />

margins:<br />

• above the signature Monogram, 1 ⁄4 the diameter of<br />

the Monogram<br />

• at the sides and bottom of the check, 1 ⁄8 inch<br />

Security Pattern<br />

To ensure confidentiality, use an envelope<br />

security pattern consisting of a field of repeated<br />

dots. Reproduce the pattern in positive<br />

or negative form on the inside or outside<br />

of envelopes used for checks.<br />

Dynamic Monogram<br />

Use the Dynamic Monogram in the background<br />

of checks according to the standards and guidelines<br />

in document 134, Dynamic Monogram.<br />

Colors<br />

• For the primary color on all checks, use black.<br />

• To highlight important information (such as the<br />

imprinted serial number), use Laser Red.<br />

• To differentiate or emphasize areas, use a 10 percent<br />

black screen.<br />

• In the Dynamic Monogram, use any appropriate<br />

color (Note: Normally, the letters/curlicues are<br />

reproduced lighter than the field. When opposing<br />

tone progressions are used, it is permissible<br />

for a small part of the top portion of the curlicues<br />

to be darker than the field, as shown in the<br />

examples on pages 19 and 20.)<br />

• For the paper stock, use white.<br />

Notes:<br />

• The Laser Line is the only element of the<br />

graphic signature that may be reproduced in red.<br />

Do not use red in the signature Monogram or<br />

any signature typography.<br />

•To maintain distinction in the Laser Line, do not<br />

use Laser Red in other fine lines.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!