Changes to Version 2.06

Version 2.07 makes the following changes to version 2.06:

(1) Added Section 508 Requirements section.

(2) ESC sequences –

(a) Added AC_ACUTE processing steps 1(h)(2) and 1(l)(2).

(b) Added AC_MACRON processing step 3.

(3) Bell-g –

(a) Added bell-g007 instruction 2A.

(b) Revised bell-g007 instruction 4.

(c) Added bell-g007 instruction 4A.

(d) Revised bell-g007 instruction 5.

(e) Added bell-g007 instruction 5A.

(4) Bell-G and Bell-T –

(a) Added instruction 9, grid 5, hex 13, typefaces 1 to 4, special processing step 2.

(b) Added instruction 9, grid 5, hex 14, typefaces 1 to 4, special processing step 2.

(c) Added instruction 9, grid 5, hex 15, typefaces 1 to 4, special processing step 2.

(d) Added instruction 9, grid 5, hex 16, typefaces 1 to 4, special processing step 2.

(e) Added instruction 9, grid 5, hex 17, typefaces 1 to 4, special processing step 2.

(f) Added instruction 9, grid 5, hex 21, typefaces 1 to 4, special processing step 2.

(g) Added instruction 9, grid 5, hex 27, typefaces 1 to 4, special processing step 2.

(h) Added instruction 9, grid 5, hex 60, typefaces 1 to 4, special processing step 2.

(i) Added instruction 9, grid 5, hex BA, typefaces 1 to 4, special processing step 2.

(j) Added instruction 9, grid 5, hex C4, typefaces 1 to 4, special processing step 2.

(k) Added instruction 9, grid 6, hex 13, typefaces 1 to 4, special processing step 2.

(l) Added instruction 9, grid 6, hex 15, typefaces 1 to 4, special processing step 2.

(m) Added instruction 9, grid 6, hex 16, typefaces 1 to 4, special processing step 2.

(n) Added instruction 9, grid 6, hex 17, typefaces 1 to 4, special processing step 2.

(o) Added instruction 9, grid 6, hex 21, typefaces 1 to 4, special processing step 2.

(p) Added instruction 9, grid 6, hex 27, typefaces 1 to 4, special processing step 2.

(q) Added instruction 9, grid 6, hex 55, typefaces 1 to 4, special processing step 2.

(r) Added instruction 9, grid 6, hex 60, typefaces 1 to 4, special processing step 2.

(s) Added instruction 9, grid 6, hex BA, typefaces 1 to 4, special processing step 2.

(t) Added instruction 9, grid 6, hex C4, typefaces 1 to 4, special processing step 2.

(u) Added instruction 9, grid 7, hex 12, typeface 3, special processing step 2.

(v) Added instruction 9, grid 7, hex 27, typeface 3, special processing step 2.

(w) Added instruction 9, grid 7, hex 2D, typeface 3, special processing step 2.

(x) Added instruction 9, grid 7, hex 2E, typeface 4, special processing step 2.

(y) Added instruction 9, grid 7, hex 32, typeface 4, special processing step 2.

(z) Added instruction 9, grid 7, hex 3B, typeface 4, special processing step 2.

(aa) Added instruction 9, grid 7, hex 47, typeface 2, special processing step 2.

(bb) Added instruction 9, grid 7, hex 50, typeface 2, special processing step 2.

(cc) Added instruction 9, grid 7, hex 59, typeface 3, special processing step 2.

(dd) Added instruction 9, grid 7, hex 5A, typeface 3, special processing step 2.

(ee) Added instruction 9, grid 7, hex 60, typeface 3, special processing step 2.

(ff) Added instruction 9, grid 7, hex 66, typeface 4, special processing step 2.

(gg) Added instruction 9, grid 7, hex 68, typeface 4, special processing step 2.

(hh) Added instruction 9, grid 7, hex 79, typeface 2, special processing step 2.

(ii) Added instruction 10, grid 8, hex 13, typefaces 1 to 3, special processing step 2.

(jj) Added instruction 10, grid 8, hex 14, typefaces 1 to 3, special processing step 2.

(kk) Added instruction 10, grid 8, hex 15, typefaces 1 to 3, special processing step 2.

(ll) Added instruction 10, grid 8, hex 16, typefaces 1 to 3, special processing step 2.

(mm) Added instruction 10, grid 8, hex 17, typefaces 1 to 3, special processing step 2.

(nn) Added instruction 10, grid 8, hex 5A, typeface 4, special processing step 2.

(5) Bell-I –

(a) Added example citation for formats 5800 to 5803, locator-05.

(b) Added footnote to formats 5800 to 5803, locator 53.

(c) Added special processing instruction #2 to formats 5800 to 5803, locator-54.

(d) Added example citation for formats 5800 to 5803, locator-69.

(e) Added special processing instructions to formats 5800 to 5803, locator-71. Also generally revised example citations.

(f) Added footnote to formats 5800 to 5803, locator-73.

(g) Added footnote to formats 5800 to 5803, locator-74. Also generally revised example citations.

(h) Added footnote to formats 5800 to 5803, locator-75.

(i) Added footnote to formats 5800 to 5803, locator-76. Also revised special processing instruction 0.1.

(j) Added footnote to formats 5800 to 5803, locator-78.

(k) Added footnote to formats 5800 to 5803, locator-82.

(l) Added example citation to formats 5800 to 5803, locator-83.

(m) Added footnote to formats 5800 to 5803, locator-84. Also added example citation to special processing instruction 0.2.

(n) Added footnote to formats 5800 to 5803, locator-85. Also added example citation to special processing instruction 0.2.

(o) Added footnote to formats 5800 to 5803, locator-86. Also added example citation to special processing instruction 0.2.

(p) Added footnote to formats 5800 to 5803, locator-87. Also added example citation to special processing instruction 0.2.

(q) Revised footnote to formats 5800 to 5803, locator-89. Also added example citations to special processing instruction 3.

(r) Added example citation to formats 5800 to 5803, locators-94 to –96

(s) Revised format 5804, locator-01, “follow text with” material.

(t) Revised format 5804, locator-08, “follow text with” material.

(u) Revised format 5810, locator-01, “follow text with” material.

(v) Revised format 5810, locator-19, “follow text with” material.

(w) Revised format 5810, locator-20, “follow text with” material.

(x) Revised format 5811, locator-04, “follow text with” material.

(y) Revised format 5812, locator-04, “follow text with” material.

(z) Revised format 5812, locator-11, “precede text with” material.

(aa) Revised format 5813, locator-04, “follow text with” material.

(bb) Revised formats 58001 to 58009, locator-06, “follow text with” material.

(cc) Revised format 58098, locator-01, “precede text with” material.

(dd) Revised format 58098, locator-08, “precede text with” material.

(6) Assumptions, Questions, and Alternatives: PLS-specific elements in these Specifications – In item 3, added the material between the <style> and </style> tags, the material between the <table> and </table> tags, and the material between {$DOC} and the </body> tag.

(7) Previous versions of these specifications – added version 2.07.

(8) Examples of U.S. Code photocomposition codes --

(a) Added 1 U.S.C. prec. ch. 1.

(b) Revised process for 2 U.S.C. § 60a-2 note (Amendments)

(c) Added 2 U.S.C. § 604.

(d) Added 3 U.S.C. § 205.

(e) Added 4 U.S.C. § 1 note (Ex. Ord. No. 10834)

(f) Replaced 4 U.S.C. § 1 note (Ex. Ord. 10798, § 21) with note (Ex. Ord. 10834, § 21).

(g) Replaced 4 U.S.C. § 1 note (Ex. Ord. 10798, § 33) with note (Ex. Ord. 10834, § 33).

(h) Added 5 U.S.C. app. (Table of Contents).

(i) Added 10 U.S.C. § 2407 note (NATO Cooperative Logistic Support Agreements).

(j) Added 12 U.S.C. § 1785 note (Choice of Highest Applicable Interest Rate).

(k) Added 15 U.S.C. ch. 14 (prec. § 601).

(l) Added 18 U.S.C. § 201 note (Memorandum of Attorney General Regarding Conflict of Interest Provisions of Public Law 87-849, February 1, 1963, 28 F.R. 985).

(m) Added 18 U.S.C. app. (Fed. R. Crim. P.) table of contents.

(n) Added 18 U.S.C. app. (Fed. R. Crim. P.) rule 39.

(o) Added 22 U.S.C. § 2291 note (Determining Major Drug-Transit Countries with Respect to Fiscal Year 1989).

(p) Added 22 U.S.C. § 5952 note (Limitation on Use of Funds for Certain Purposes).

(q) Added 26 U.S.C. § 132 note (Amendment of Subsection (f)).

(r) Added 28 U.S.C. app. (Fed. R. Civ. P.) form 2

(s) Added 28 U.S.C. app. (Fed. Cl. R.) app. A, form A

(t) Added 40 U.S.C. § 71b note (Reorg. Plan No. 5 of 1966).

(u) Added 42 U.S.C. § 2472 note (Amendments).

(v) Added 42 U.S.C. ch. 72, subch. II, pt. B (prec. § 5631).

(w) Added 43 U.S.C. § 502 note (Temporary Activity of Secretary of Interior to Facilitate Emergency Actions with Regard to 1976-1977 Drought).

(x) Added 43 U.S.C. § 751 note (Land Information Study; Report to Congress).

(y) Added 43 U.S.C. § 946 note (Amendments).

(z) Added 43 U.S.C. § 1451 note (Reorg. Plan No. 3 of 1950)

(aa) Added 43 U.S.C. § 1457 note (Emergency Preparedness Functions).

(bb) Added 43 U.S.C. § 1595 note (Effective Date of 1984 Amendment).

(cc) Added 43 U.S.C. § 1733 note (Modification of Regulations Relating to Mining Operations on Public Lands; Posting of Reclamation Bond for All Operations Involving Significant Surface Disturbance).

(dd) Added 43 U.S.C. § 1843 note (Amendments).

(ee) Added 44 U.S.C. § 101 note (Short Title of 1993 Amendment).

(ff) Added 44 U.S.C. § 3506 note (Amendments).

(gg) Added 44 U.S.C. § 3901 note (Short Title).

(hh) Added 48 U.S.C. 864 note (Federal Rules of Criminal Procedure).

(ii) Added 48 U.S.C. §§ 1694 to 1694e.

Schedule of Future Updates to these Specifications

The following is the planned schedule for release of future editions of the specifications, with the issues to be addressed in each new version:

Version 2.08 – Accessibility: (estimated completion date – 5/15/01)

· Verify compliance with 36 C.F.R. § 1194.22

· subsection (g) – row and column headers in data tables

· subsection (h) – markup of data cells where headers have multiple levels.

· Subsection (j) – screen flicker

· Subsection (k) – text-only pages

· Subsection (l) – scripting languages

· Subsection (n) – electronic forms

· Subsection (o) – repetitive navigation links.

· Verify compliance with priority 1 items on the World Wide Web Consortium’s Checklist of Checkpoints for Web Content Accessibility Guidelines 1.0 http://www.w3.org/TR/WCAG10/full-checklist.html#wc-priority-1.

Background

The United States Code is the official compilation of the Federal statutes of a general and permanent nature[1]. By Federal statute[2], the Law Revision Counsel of the U.S. House of Representatives is the publisher and compiler of the Code. The Counsel is an appointee of the Speaker of the House.

In 1977 – at the request of the Law Revision Counsel – the Office of the Law Revision Counsel, the Government Printing Office (GPO), and House Information Systems[3] began work on computerizing the production of the U.S. Code. This evolved into the Integrated Law Revision and Retrieval System[4], jointly developed by LRC, HIS, and GPO. The integrated system was developed to provide the Office of the Law Revision Counsel with direct control of the U.S. Code, to produce the U.S. Code in a more timely fashion, to produce an up-to-date U.S. Code research and retrieval system, and to produce cost savings in typesetting the U.S. Code system. Key elements of the integrated system included:

· A system of tags to format U.S. Code data[5]

· Hardware and software for editing and storing the U.S. Code master database[6]

· Software to typeset the tagged data[7]

· Software to allow full text search of the U.S. Code (meeting or exceeding industry standards for computer assisted legal research)[8]

· Software to (1) format tagged data into a style compatible with the input requirements of the search software, while (2) preserving as much of the typesetting functionality of the tags as possible.

In August of 1977, HIS released a pilot full-text searchable version of title 2 of the U.S. Code. HIS developed mainframe COBOL software to convert the data into a format usable by STAIRS – the mainframe-based search engine from IBM, that was already in use by HIS for the Bill Status System (later “LEGIS”). By September of 1978, the pilot expanded to include all 50 titles of the U.S. Code.

In the early 1980’s, HIS rewrote its software for converting the photocomposition coded data – using a table-driven architecture. The software (which resides on the HIR mainframe) was written primarily in COBOL with tabular data manipulation done through PL/1. In 1986, HIS developed mainframe software to convert the U.S. Code Classification Tables into a format compatible with STAIRS and to incorporate that data into the U.S. Code searchable database.[9] The full-text searchable U.S. Code was made available to House and Senate offices, the Library of Congress, the Congressional Budget Office, the General Accounting Office, the Supreme Court, and several executive branch offices, through communications links to the HIS/HIR mainframe.[10]

In 1991, HIS, at the request of the Law Revision Counsel, began work on producing a CD-ROM version of the U.S. Code for distribution to House offices, the legal community, and the public at large.[11] On January 4, 1995, HIS began making a full-text searchable version of the U.S. Code available to the public through the World Wide Web.[12] Both the CD-ROM and World Wide Web versions of the U.S. Code are accessible through search engines produced by Personal Library Software, Inc. (now part of America Online, Inc.). The conversion of the raw data from GPO photocomposition codes, however, is still processed primarily through software on the HIR mainframe.

Mainframe Migration, SGML, XML, HTML, and XHTML

In 1995, the Committee on House Oversight (now the Committee on House Administration) adopted a resolution directing that HIR prepare a plan for the retirement of the HIR mainframe[13]. As part of the implementation of the plan that was ultimately adopted, access to the STAIRS-based mainframe U.S. Code database was ended effective December 1, 1998[14]. Some of the software necessary to convert the Law Revision Counsel’s master U.S. Code database from GPO photocomposition code format into a format usable to update the U.S. Code web database and to create the annual U.S. Code CD-ROM, however, still resides on the HIR mainframe. The 2001-2005 Strategic Plan adopted by the Chief Administrative Officer of the House in May 2000, nonetheless, has as one of its objectives, completing mainframe migration by September 2001[15]. The Strategic Plan’s companion document, CAO Team Member Feedback: CAO 2001-2005 Draft Strategic Plan, states that “A key component of this objective is a formal certification that the migration solution meets the critical functions of the original application. . . . Mission critical mainframe services will be continued until alternatives are defined, funded and satisfactorily deployed.” It also provides that “Migration objectives include . . . Meet[ing] customer requirements for the application, connectivity, input/output, and user interfaces”.

In 1996, the Law Revision Counsel requested that HIR provide support for the “conversion of the U.S. Code master database from GPO photocomposition coding to SGML coding”.[16] SGML (Standard Generalized Markup Language) exists in many implementations – including

· Extensible Markup Language (XML),

· Document Style Semantics and Specification Language (DSSSL),

· Hypermedia Time-based Structuring Language (HyTime),

· Virtual Reality Markup Language (VRML),

· HyperText Markup Language (HTML), and

· Extensible HyperText Markup Language (XHTML).

Of the SGML implementations, HTML is the implementation that is by far most widely identified with the World Wide Web. Virtually all web browsers are able to display HTML documents. HTML is stable, reasonably robust, and has a well-established infrastructure of authoring and maintenance tools. XML does not have the installed base of browsers or authoring and maintenance tools that HTML has, nor the stability that HTML now has[17], and is far more complex than HTML. XML, nonetheless, has widespread support in the technical community as the wave of the future for SGML coding. The Clerk of the House and the Secretary of the Senate have recommended that “the House and Senate should adopt XML as a data standard to be employed for the exchange of legislative documents, allowing each body to determine appropriate document creation and editing environments”.[18] While the Legislative Branch XML Technical Committee[19], under the leadership of the Clerk of the House and the Secretary of the Senate, has several initiatives in development, it appears highly unlikely that an XML implementation of the U.S. Code—that would be usable by those who are currently using the U.S. Code web database—can be in place by the September 2001 target for mainframe migration.

Fortunately, the U.S. Code is not the only project that has had to face an HTML vs. XML choice. The World Wide Web Consortium (the World Wide Web’s principal standards developing body) is currently developing a specification for XHTML that will allow HTML and XML to coexist and share features that are currently only in one or the other. The current draft of that specification provides guidance as to how to code HTML in such a way that it is compatible with XML[20]. In developing the specifications for converting from GPO photocomposition coding to HTML coding, we have attempted to follow the XHTML standards.

In addition to not precluding use of XML, and to have the new U.S. Code database free of the HIR mainframe by September 2001, it is a goal of the conversion from GPO photocomposition codes to

· format the U.S. Code text so that it is close to the appearance of the Code in its traditional printed bound volumes[21]; and

· maximize accessibility to the U.S. Code.

To help reach these goals, whenever possible, we have only used the commands that are contained in HTML version 3.2. In those instances where additional capabilities have been necessary in order to approximate the appearance of the Code, we have used commands that were added in subsequent versions of HTML. In those few instances where even those features have been inadequate, we have used features from JavaScript and Cascading Style Sheets. Within these constraints, the HTML tagging conforms to the revised Robot Exclusion Standard[22], the W3C PICS Specification[23], and conformance level A of the W3C Content Accessibility Guidelines[24].

Section 508 Requirements

Section 508 of the Rehabilitation Act of 1973 (29 U.S.C. § 794d) provides that Federal government information technology systems are to be available to individuals with disabilities on a basis comparable with access that is available to individuals without disabilities. The Architectural and Transportation Barriers Compliance Board is to issue standards to carry out this mandate, which are to take effect six months after the Board’s standards have been issued. On December 21, 2000, the Board issued its final standards (36 C.F.R. Part 1194). The standards dealing specifically with web sites are contained in 36 C.F.R. § 1194.22. Section 1104.22 provides that:

(a) A text equivalent for every non-text element shall be provided (e.g., via "alt", "longdesc", or in element content).

(b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation.

(c) Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup.

(d) Documents shall be organized so they are readable without requiring an associated style sheet.

(e) Redundant text links shall be provided for each active region of a server-side image map.

(f) Client-side image maps shall be provided instead of server-side image maps except where the regions cannot be defined with an available geometric shape.

(g) Row and column headers shall be identified for data tables.

(h) Markup shall be used to associate data cells and header cells for data tables that have two or more logical levels of row or column headers.

(i) Frames shall be titled with text that facilitates frame identification and navigation.

(j) Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz.

(k) A text-only page, with equivalent information or functionality, shall be provided to make a web site comply with the provisions of this part, when compliance cannot be accomplished in any other way. The content of the text-only page shall be updated whenever the primary page changes.

(l) When pages utilize scripting languages to display content, or to create interface elements, the information provided by the script shall be identified with functional text that can be read by assistive technology.

(m) When a web page requires that an applet, plug-in or other application be present on the client system to interpret page content, the page must provide a link to a plug-in or applet that complies with §1194.21(a) through (l).

(n) When electronic forms are designed to be completed on-line, the form shall allow people using assistive technology to access the information, field elements, and functionality required for completion and submission of the form, including all directions and cues.

(o) A method shall be provided that permits users to skip repetitive navigation links.

(p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required.

Civil actions are permitted against agencies that are not in compliance with the standards by June 21, 2001. The Rehabilitation Act applies to offices of the House of Representatives by virtue of § 102(a)(10) of the Congressional Accountability Act (2 U.S.C. § 1302(a)(10)).

These specifications are in compliance with the standards promulgated by the Board.

Nomenclature

As used in these specifications:

(1) A diamond symbol () indicates a blank space.

(2) {Braced bold text} indicates the name of a variable.

(3) {Braced bold text}_{with a subscript}indicates an array with the subscript as the array’s index.

(4) A bent left arrow (Ã) indicates a carriage return/line feed character.

Special Characters

The U.S. Code data includes some characters that do not follow the standard ASCII definitions. These should be translated at the end of the photocomposition-to-HTML conversion process – in particular, after any G-code and T-code processing, if any.

Name	Decimal Value	Hex Value	Represen- tation	HTML	Example at
EOF	0	00		Special processing: (1) Output: {footnote file}<!--plsfield:END--> - - - (2) print out the {error file}. - - - (3) if a HEX 00 is followed immediately by one or more additional occurrences of HEX 00, the additional occurrence(s) of HEX 00 should be deleted.	1 U.S.C. § 213 (source credit) 34 U.S.C.
Sectwst	06	06	§	Special processing: If two Hex06 appear together, replace the pair with: §§<!-- sections --> If a Hex06 appears not in a pair, replace it with: §<!-- section -->	Single §: 1 U.S.C. § 101 Double §: 2 U.S.C. §§ 1223, 1224
Crlf	10	0A		Special processing: Delete any Hex 0A.	1 U.S.C. § 1
Cents	11	0B	¢	Special Processing: (1) output: ¢<!-- cents --> - - - (2) Add to {error file}: {TITLE NUMBER} USC{appendix} {SECTION NUMBER}{long subsection} ({text field}) – warning – verify implementation of Hex 0B (cents sign)
Pgmark	12	0C	¶	Special processing: If two Hex0C appear together, replace the pair with: ¶¶<!-- paragraphs --> If a Hex0C appears not in a pair, replace it with: ¶<!-- paragraph -->	Single ¶: 11 U.S.C. app. rule 4004 note Double ¶: 11 U.S.C. app. rule 2004 note
Noprnst	14	0E		Special Processing: (1) Delete data through noprnend - - - (2) Add to {error file}: {TITLE NUMBER} USC{appendix} {SECTION NUMBER}{long subsection} ({text field}) – warning – verify implementation of Hex 0E (Noprnst).
Noprnend	15	0F		Special Processing: (1) End of delete started with noprst - - - (2) Add to {error file}: {TITLE NUMBER} USC{appendix} {SECTION NUMBER}{long subsection} ({text field}) – warning – verify implementation of Hex 0E (Noprnend).
Prime	16	10	'	<!-- prime -->'	48 U.S.C. § 1705 note (Proc. No. 4346)
bldlbrak	19	13	[	Special Processing: (1) Output: <strong><!-- [ -->[</strong> - - - (2) Add to {error file}: {TITLE NUMBER} USC{appendix} {SECTION NUMBER}{long subsection} ({text field}) – warning – verify implementation of Hex 13 (bldlbrak)
bldrbrak	20	14	]	Special Processing: (1) Output: <strong><!-- [ -->]</strong> - - - (2) Add to {error file}: {TITLE NUMBER} USC{appendix} {SECTION NUMBER}{long subsection} ({text field}) – warning – verify implementation of Hex 14 (bldrbrak)
emspace[25]	24	18		<!-- -->     <!-- -->	1 U.S.C. § 204(d)
enspace[26]	25	19		<!-- -->   <!-- -->	2 U.S.C. § 1 notes (Constitu-tional Provisions)
plusminus	27	1B	±	Special Processing: (1) Output: <!-- plus or minus -->± - - - (2) Add to {error file}: {TITLE NUMBER} USC{appendix} {SECTION NUMBER}{long subsection} ({text field}) – warning – verify implementation of Hex 1B (plusminus)
dscrhyph	28	1C		Special processing: delete HEX 1C.	1 U.S.C. prec. ch. 1 (Table Showing Disposition of All Sections of Former Title 1)
dagger	30	1E	†	Special Processing: (1) Output: <!-- dagger -->† - - - (2) Add to {error file}: {TITLE NUMBER} USC{appendix} {SECTION NUMBER}{long subsection} ({text field}) – warning – verify implementation of Hex 1E (dagger)
Xyquotes (open)	39	27	“	Special processing: If two HEX 27s occur with no characters between them, then replace the pair with a quotation mark. Otherwise, replace it with an apostrophe.	Single occurrence: 1 U.S.C. § 1 note (Continen-tal United States) Double occurrence: 1 U.S.C. ch. 1
Less than	60	3C	<	Special Processing: (1) Output: <!-- is less than -->< - - - (2) Add to {error file}: {TITLE NUMBER} USC{appendix} {SECTION NUMBER}{long subsection} ({text field}) – warning – verify implementation of Hex 3C (Less than)
Greater than	62	3E	>	Special Processing: (1) Output: <!-- is greater than -->> - - - (2) Add to {error file}: {TITILE NUMBER} USC{appendix} {SECTION NUMBER}{long subsection} ({text field}) – warning – verify implementation of Hex 3E (Greater than)
footnote	92	5C	\	Special processing: (1) Backslashes appear in pairs with a {number} between them. - - - (1A) If {subsection anchor} is “on”, then output: </a> - - - (2) If (a) {footnote switch} = 0; (b) the {number} string does not include a slash (i.e., “/”); (c) {table switch} is “off”; and (d) {format} does not equal 58008; then replace the \{number}\ string with: <a href=“#ftnt{number}text” name=“ftnt{number}” id=“ftnt{number}”><sup>{number}</sup></a> - - - (3) If (a) the {number} does not include a slash; (b) {footnote switch} is greater than zero; and (c) {table switch} is “off”; then replace the \{number}\ string with: <a id=“ftnt{number}text” name=“ftnt{number}text” href=“#ftnt{number}”><sup>{number}</sup></a> - - - (4) If the {number} string is “1/4”, then replace the \{number}\ string with: ¼ - - - (5) If the {number} string is “1/2”, then replace the \{number}\ string with: ½ - - - (6) If the {number} string is “3/4”, then replace the \{number}\ string with: ¾ - - - (7) If the {number} string includes a slash, but is not “1/4”, “1/2”, or “3/4”, then replace the \{first number}/{second number}\ string with: <sup>{first number}</sup>/<sub> {second number}</sub> - - - (8) If (a) {footnote switch} = 0; (b) the {number} string does not include a slash (i.e., “/”); and (c) {table switch} is “on”; then replace the \{number}\ string with: <a href=“#tableftnt{number}text” id=“tableftnt{number}” name=“tableftnt{number}”><sup>{number}</sup></a> - - - (9) If (a) the {number} does not include a slash; (b) {footnote switch} is greater than zero; and (c) {table switch} is “on”; then Replace the \{number}\ string with: <a id=“tableftnt{number}text” name=“tableftnt{number}text” href=“#tableftnt{number}”><sup>{number}</sup></a> - - - (10) If {subsection anchor} is “on”, then output: <a onMouseOver=“window.status=‘{TITLE NUMBER} USC{appendix} {SECTION NUMBER}{long subsection}’; return true”> - - - (11) If (a) {footnote switch} = 0; (b) the {number} string does not include a slash (i.e., “/”); (c) {table switch} is “off”; and (d) {format} equals 58008; then replace the \{number}\ string with: <sup>{number}</sup> - - - (12) If (a) {footnote switch} = 0; (b) the {number} string does not include a slash (i.e., “/”); (c) {table switch} is “off”; (d) {format} equals 58008; and (e) {bell-I} equals 04, then replace the \{number}\ string with: <a href=“#ftnt{number}text” name=“ftnt{number}” id=“ftnt{number}”><sup>{number}</sup></a> - - - (13) If (a) {footnote switch} = 0; (b) the {number} string does not include a slash (i.e., “/”); (c) {table switch} is “off”; (d) {format} equals 58008; then replace the \{number}\ string with: <a href=“#ftnt{number}text” name=“ftnt{number}” id=“ftnt{number}”><sup>{number}</sup></a>	42 U.S.C. § 7412(b)(3) (A) 1 U.S.C. ch. 1 1 U.S.C. ch. 1 28 U.S.C. app. (Sup. Ct. R.) rule 33(1)(c) 5 U.S.C. § 5304(a)(3) (D) 33 U.S.C. § 702a-1¾ 26 U.S.C. § 451 note (Pub. L. 97-248, § 229(c)(2) (B)) 42 U.S.C. § 7412(b)(1) 42 U.S.C. § 7412(b)(1) Con-stitution, art. I, § 2, cl. 1 Con-stitution (catchline) Con-stitution, art. I, § 1, cl. 3
minus[27]	94	5E	-	<!-- minus -->-	22 U.S.C. § 127(a)
emdash[28]	95	5F	—	<!-- --><!-- -->	1 U.S.C. ch. 1
Xyquotes (close)	96	60	”	Special processing: If two HEX 60s occur with no characters between them, then replace the pair with a quotation mark. Otherwise, replace it with an apostrophe.	Single occurrence: 1 U.S.C. § 1 note (Continen-tal United States) Double occurrence: 1 U.S.C. ch. 1
degreemk	171	AB	º	<!-- degrees -->°	45 U.S.C. § 1705 note (Proc. No. 4346)
dbldagger	189	BD	‡	Special Processing: (1) Output: <!-- double dagger -->‡ - - - (2) Add to {error file}: {TITLE NUMBER} USC{appendix} {SECTION NUMBER}{long subsection} ({text field}) – warning – verify implementation of Hex BD (dbldagger)
muchless	190	BE	<<	Special Processing: (1) Output: <nobr><!-- is much greater than -->><a style="position: relative; left: -0.2 em; top: -0.1 em; font-size: 0.8 em; font-weight: normal">></a></nobr> - - - (2) Add to {error file}: {TITILE NUMBER} USC{appendix} {SECTION NUMBER}{long subsection} ({text field}) – warning – verify implementation of Hex BE (Muchless)
balbox	191	BF	~	Special Processing: (1) Output: <!-- box --> > - - - (2) Add to {error file}: {TITLE NUMBER} USC{appendix} {SECTION NUMBER}{long subsection} ({text field}) – warning – verify implementation of Hex BF (Balbox)

ESC sequences

The ESC character (Hex FF) followed by two (or three) characters is used to indicate certain special characters or processes.[29] These need to be converted early in the photocomposition-to-HTML conversion process. The following list indicates the character strings that follow the ESC character and the HTML coding that the ESC and character string should be converted into:

Name	ESC sequence	Process	Ex-ample at
Thin space	ESC 1A	Replace with: <!-- --> <!-- -->	1 U.S.C. prec. ch. 1
N-dash	ESC 09	(1) Replace with: (2) Go back to the previous blank space[30],   <td> tag, <p>, <br>, or bell-code[31] and insert after it: <nobr> (3) Go forward to the next blank space[32],   <td> tag, <p>, <br>, bell-code[33], or EOF (Hex 00), and insert after it: </nobr> (4) Output: <!-- (5) Again output all of the text between <nobr> and </nobr>, but this time replace the occurrence(s) of with a dash[34] (6) Output: -->	1 U.S.C. ch. 1
Multiplication	ESC 0A	Replace with: <!-- times -->×	28 U.S.C. § 1470 note (Rules of Pro-cedure of the Judicial Panel on Multi-district Liti-gation, rule 7.1(c) (iv))
All Mark	ESC 08	Step 1: Replace with: O Step 2: Add to {error file}: {TITLE NUMBER} USC{appendix} {SECTION NUMBER}{long subsection} ({text field}) – warning – verify implementation of ESC 08 (All Mark)
Copyright	ESC AF	Replace with: ©	17 U.S.C. § 401(b)(1)
AC_BREVE [˘]	ESC AE0	Step 1: If preceded by “S”, replace with: If preceded by “s”, replace with: Step 2: Continue normal processing until the next space is reached. Insert a space, “<!--”, another space, the previous word, another space, and “-->”. (For instance, if the original text was “mas▲AE0” (where “▲” is the escape character), then convert it to “maš <!-- mas -->”.) Step 3: Add to {error file}: {TITLE NUMBER} USC{appendix} {SECTION NUMBER}{long subsection} ({text field}) – warning – verify implementation of ESC AE0 (Breve accent)
AC_ACUTE [´]	ESC AE1	Step 1: (a) If preceded by “A”, replace with: Á (b) If preceded by “E”, replace with: É (c) If preceded by “I”, replace with: Í (d) If preceded by “O”, replace with: Ó (e) If preceded by “U”, replace with: Ú (f) If preceded by “Y”, replace with: Ý (g) If preceded by “a”, replace with: á (h) If preceded by “c”, (1) replace with: <nobr>c<a style="position: relative; left: -0.2 em; top: 0.2 em; font-size: 1.8 em; font-weight: normal">´</a></nobr> (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes a c with an acute accent, that may be misinterpreted by your reader as a c followed by the accent." (i) If preceded by “e”, replace with: é (j) If preceded by “i”, replace with: í (k) If preceded by “o”, replace with: ó (l) If preceded by “s”, (1) replace with: <nobr>s<a style="position: relative; left: -0.2 em; top: 0.2 em; font-size: 1.8 em; font-weight: normal">´</a></nobr> (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes an s with an acute accent, that may be misinterpreted by your reader as an s followed by the accent." (m) If preceded by “u”, replace with: ú (n) If preceded by “y”, replace with: ý Step 2: Continue normal processing until the next space is reached. Insert a space, “<!--”, another space, the previous word, another space, and “-->”. (For instance, if the original text was “pa▲AE1per” (where “▲” is the escape character), then convert it to “páper <!-- paper -->”.)	Á: 50 U.S.C. ch. 21 (prec. § 541) É: 7 U.S.C. ch. 43 (prec. § 1761) á: 50 U.S.C. §§ 541 to 546 ć: 22 U.S.C. § 5421(f) (3)(B) (5) é: 7 U.S.C. § 1765a (d) ś: 22 U.S.C. § 5421(f) (3)(B) (5)
AC_GRAVE [`]	ESC AE2	Step 1: If preceded by “A”, replace with: À If preceded by “a”, replace with: à If preceded by “E”, replace with: È If preceded by “I”, replace with: Ì If preceded by “O”, replace with: Ò If preceded by “U”, replace with: Ù If preceded by “a”, replace with: à If preceded by “e”, replace with: è If preceded by “i”, replace with: ì If preceded by “o”, replace with: ò If preceded by “u”, replace with: ù Step 2: Continue normal processing until the next space is reached. Insert a space, “<!--”, another space, the previous word, another space, and “-->”. (For instance, if the original text was “che▲AE2que” (where “▲” is the escape character), then convert it to “chèque <!-- cheque -->”.) Step 3: Add to {error file}: {TITLE NUMBER} USC{appendix} {SECTION NUMBER}{long subsection} ({text field}) – warning – verify implementation of ESC AE2 (Grave accent)
AC_CIRCUMFLEX [^]	ESC AE3	Step 1: If preceded by “A”, replace with: Â If preceded by “E”, replace with: Ê If preceded by “I”, replace with: Î If preceded by “O”, replace with: Ô If preceded by “U”, replace with: Û If preceded by “a”, replace with: â If preceded by “e”, replace with: ê If preceded by “i”, replace with: î If preceded by “o”, replace with: ô If preceded by “u”, replace with: û Step 2: Continue normal processing until the next space is reached. Insert a space, “<!--”, another space, the previous word, another space, and “-->”. (For instance, if the original text was “cha▲AE3ssis” (where “▲” is the escape character), then convert it to “châssis <!-- chassis -->”.) Step 3: Add to {error file}: {TITLE NUMBER} USC{appendix} {SECTION NUMBER}{long subsection} ({text field}) – warning – verify implementation of ESC AE3 (Circumflex)
AC_DIERESIS [¨]	ESC AE4	Step 1: If preceded by “A”, replace with: Ä If preceded by “E”, replace with: Ë If preceded by “I”, replace with: Ï If preceded by “O”, replace with: Ö If preceded by “U”, replace with: Ü If preceded by “Y”, replace with: Ÿ If preceded by “a”, replace with: ä If preceded by “e”, replace with: ë If preceded by “i”, replace with: ï If preceded by “o”, replace with: ö If preceded by “u”, replace with: ü If preceded by “y”, replace with: ÿ Step 2: Continue normal processing until the next space is reached. Insert a space, “<!--”, another space, the previous word, another space, and “-->”. (For instance, if the original text was “u▲AE4berall” (where “▲” is the escape character), then convert it to “überall <!-- uberall -->”.) Step 3: Add to {error file}: {TITLE NUMBER} USC{appendix} {SECTION NUMBER}{long subsection} ({text field}) – warning – verify implementation of ESC AE4 (Dieresis accent )
AC_CARON [ˇ]	ESC AE5	Step 1: If preceded by “S”, replace with: Š If preceded by “s”, replace with: š Step 2: Continue normal processing until the next space is reached. Insert a space, “<!--”, another space, the previous word, another space, and “-->”. (For instance, if the original text was “s▲AE5” (where “▲” is the escape character), then convert it to “š <!-- s -->”.) Step 3: Add to {error file}: {TITLE NUMBER} USC{appendix} {SECTION NUMBER}{long subsection} ({text field}) – warning – verify implementation of ESC AE5 (Caron accent)
AC_TILDE [~]	ESC AE6	Step 1: If preceded by “A”, replace with: Ã If preceded by “N”, replace with: Ñ If preceded by “O”, replace with: Õ If preceded by “a”, replace with: ã If preceded by “n”, replace with: ñ If preceded by “o”, replace with: õ Step 2: Continue normal processing until the next space is reached. Insert a space, “<!--”, another space, the previous word, another space, and “-->”. (For instance, if the original text was “n▲AE6apa” (where “▲” is the escape character), then convert it to “ñapa <!-- napa -->”.) Step 3: Add to {error file}: {TITLE NUMBER} USC{appendix} {SECTION NUMBER}{long subsection} ({text field}) – warning – verify implementation of ESC AE6 (Tilde accent)
AC_ANGSTROM [°]	ESC AE7	Step 1: If preceded by “A”, replace with: Å If preceded by “a”, replace with: å Step 2: Continue normal processing until the next space is reached. Insert a space, “<!--”, another space, the previous word, another space, and “-->”. (For instance, if the original text was “a▲AE7rti” (where “▲” is the escape character), then convert it to “årti <!-- arti -->”.) Step 3: Add to {error file}: {TITLE NUMBER} USC{appendix} {SECTION NUMBER}{long subsection} ({text field}) – warning – verify implementation of ESC AE7 (Angstrom)
AC_MACRON [ˉ]	ESC AE8	Step 1: Replace with: <a style="position: relative; left: -0.3 em; top: -0.3 em; font-size: 1.8 em; font-weight: normal">-</a> Step 2: Continue normal processing until the next space is reached. Insert a space, “<!--”, another space, the previous word, another space, and “-->”. (For instance, if the original text was “‘o▲AE8lelo” (where “▲” is the escape character), then convert it to “‘ōlelo <!-- ‘olelo -->”.) Step 3: Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes a character with a macron on top of it, that may be misinterpreted by your reader as an letter followed by a dash."	^: 20 U.S.C. § 7902(19) f: 20 U.S.C. § 7912(1) (B)(ii)
AC_CEDILLA [¸]	ESC AE9	Step 1: If preceded by “C”, replace with: Ç If preceded by “c”, replace with: ç Step 2: Continue normal processing until the next space is reached. Insert a space, “<!--”, another space, the previous word, another space, and “-->”. (For instance, if the original text was “c▲AE9a” (where “▲” is the escape character), then convert it to “ça <!-- ca -->”.) Step 3: Add to {error file}: {TITLE NUMBER} USC{appendix} {SECTION NUMBER}{long subsection} ({text field}) – warning – verify implementation of ESC AE9 (cedilla)

Bell Codes

A bell (HEX 07) signals that a command is to be given. The character that immediately follows a bell indicates the type of command. As indicated below, some of these commands have arguments – these arguments come immediately after the character following the bell. For instance,

Bell-I80

is a bell-I with an argument of 80. Note that the bell commands are case sensitive.

Bell-a

A bell-a is followed by a three-digit numeric. When a bell-a occurs:

(1) Store the number as {bell-a argument}.

(2) Delete all of the text from the bell-a up to (but not including) the next bell.

(3) Add to {error file}: {TITLE NUMBER} USC{appendix}{SECTION NUMBER}{long subsection} ({text field}) – warning – verify implementation of bell-a{bell-a argument}.

Bell-A

Delete the bell-A.[35]

Bell-c

The bell-c indicates the start of tabular data[36]. The bell-c is normally followed by a long string of qualifiers that define the characteristics of the table. This is then followed by additional codes associated with the actual data in the table. A bell-e marks the end of the table. Note that bell codes within a table (i.e., between a bell-c and a bell-e) may have different characteristics than the same bell codes outside of a table.

A. Arguments for bell-c (excluding column definitions)

(A.1) The bell-c is followed immediately by a number and a comma.

(a) Store the number as the {number of columns in table}.

(b) Set {footnote switch}, {column}, {absolute width indent}, and {table offset} to zero.

(c) Set {HTML frame value} to: void

(d) Set {bearoff}[37] to two.

(e) Set {bearoff default} and {table switch} to: on

(f) Add seven to {Leading}[38]

(g) Set {Body HTML font size}, {Boxhead HTML font size}, {colspan}, {Footnote HTML font size}, {Grid}, {I95 HTML font size}, {I96 HTML font size}, {original grid}, {original typeface}, and {Typeface}, to one.

(h) Set {alignment}, {previous stub locator}, {table leading}, {table row}, and {table width in points}, to zero.

(i) Set {absolute width switch}, {block style}, {I25 switch}, {ns switch}, {row bottom leadering}, {stub indent limit switch}, {table-wide justification}, {top leadering switch}, and {tracing column switch} to: off

(j) Set {HTML border value} to one.

(k) (i) set {table width in pixels} to 480

(ii) if {number of columns in table} is greater than 9, then set {table width in pixels} to 718.

(l) Set {rules value}[39] to: all

(m) If {text field} is “SOURCE”,[40] then set {text field} to: MISC1

(n) Set {boxhead top leading} to 4

(o) Set {bottom of boxhead rule weight}, {end of table rule weight}, {gap between parallel lines}, {horizontal rules weight}, {top of table rule weight}, and {vertical rules weight} to 4

(p) For every value of {N} (from 1 to {number of columns in table}*2[41]), set {bell-D indent}_{N} to:

(q) Set {centering table width} to 720

(r) Set {Body point size} to six

(s) Set {I26 HTML font size} to three

(t) For every value of {N} (from 1 to {number of columns in table}*2[42]), set {vertical rule suppression}_{N} and {vertical rule}_{N}to a blank.

(u) Clear out the contents of {repeated headings file} and {I25 repeated headings file}.

(A.2) If the argument contains an “L” (linerule designation), followed a number and a comma (not an open paren), then store the {HTML frame value} as indicated in the table below:

L argument	HTML frame value
0 [43]	void
1 [44]	hsides
2 [45]	hsides
3 [46]	0
4 [47]	0
5 [48]	0
6 [49]	0
Any other value	0

(a) If {HTML frame value} = 0, then

(i) Add to the {error file}: {TITLE NUMBER} USC{appendix}{SECTION NUMBER}{long subsection} ({text field}) – unidentified argument in c-code – L{L argument}

(ii) Set {HTML frame value} to: void

(b) If {HTML frame value} = “void”, then set {HTML border value} to zero.

(c) If {L argument} = 1, then set {rules value}[50] to: none

(A.3) If the argument contains an “L” followed by a number and an open paren,[51] up to six numbers (delimited by commas), a close paren, and a comma, then

(a) follow the directions in A.2 (ignoring the restriction on open parens contained in the introduction.

(b) [reserved]

(c) If there is a number immediately after the open paren, then set {top of table rule weight} to that number

(d) If there is a number immediately after the first comma, then set {bottom of boxhead rule weight} to that number

(e) If there is a number immediately after the second comma, then set {end of table rule weight} to that number

(f) If there is a number immediately after the third comma, then set {horizontal rules weight} to that number

(g) If there is a number immediately after the fourth comma, then set {vertical rules weight} to that number

(h) If there is a number immediately after the fifth comma, then set {gap between parallel lines} to that number

(h-1) If {top of table rule weight} equals zero, {end of table rule weight} equals zero, and {HTML frame value} equals “hsides”, [52] then

(1) set {HTML frame value} to: void

(2) go to instruction (j-1).

(i) If {top of table rule weight} equals zero and {HTML frame value} equals “hsides”, then set {HTML frame value} to: below

(j) If {end of table rule weight} equals zero and {HTML frame value} equals “hsides”, then set {HTML frame value} to: above

(j-1) If {horizontal rules weight} equals zero and {vertical rules weight} equals zero, then set {rules value}[53] to: none

(k) If {horizontal rules weight} equals zero and {rules value}[54] does not equal “none”, then set {rules value} to: cols

(l) If {vertical rules weight} equals zero and {rules value}[55] does not equal “none”, then set {rules value} to: rows

(m) [reserved]

(n) If {HTML border value} is greater than zero, then

(1) average the non-zero values of {top of table rule weight}, {end of table rule weight}, {horizontal rules weight}, and {vertical rules weight}

(2) divide the average from instruction (n)(1) by four

(3) round off the result of instruction (n)(2) to the nearest whole number

(4) store the result of instruction (n)(3) as {HTML border value}

(A.4) If the argument contains a “b” (bearoff) followed by a number and a comma,[56] then

(a) calculate {bearoff}[57] by multiplying the value of the number that followed the “b” by 0.8 and rounding that product to the nearest whole number.

(b) Set {bearoff default} to: off

(A.5) If the argument contains an “ns,” (minimum space)[58], then:

(a) subtract seven from {Leading}.

(b) Set {ns switch} to: on

(A.6) If the argument contains an “nc,” (no carding)[59], then set {ns switch} to: on

(A.7) If the argument contains an “nj,” (non-justify)[60], then set {table-wide justification} to: off

(A.8) If the argument contains a “j,” (justify)[61], then

(a) set {table-wide justification} to: on

(b) add to {error file}: {TITLE NUMBER} U.S.C.{appendix}{SECTION NUMBER}{long subsection} ({text field}) – attention – verify accuracy of rendering of j in bell-c command line – see Subformat Generation MicroComp (2/1/97), page 4 (item 7).

(A.9) If the argument contains an “nh,” (no hyphenation in stub column)[62], then ignore the code and continue processing.

(A.10) If the argument contains an “lt,” (leader from top)[63], then

(a) set {top leadering switch} to: on

(b) add to {error file}: {TITLE NUMBER} USC{appendix}{SECTION NUMBER}{long subsection} ({text field}) – attention – verify accuracy of rendering of lt in bell-c command line – see Subformat Generation MicroComp (2/1/97), page 4 (item 9).

(A.11) If the argument contains “tp” (title point size) followed by a number followed by a comma[64], then store the {I95 HTML font size} and {I96 HTML font size} according to the following table

tp argument	I95[65] HTML font size	I96[66] HTML font size
0 [67]	0	0
1	1	1
2	1	1
3	1	1
4	1	1
5	1	1
6 [68]	1	1
7 [69]	2	1
8 [70]	3	1
9	4	2
10	5	3
11	5	3
12	6	5
13	6	5
14	7	6
Over 14	7	6

(A.12) If the argument contains a “p” followed by a number, a comma, a second number, a slash, a third number, and a comma (e.g., p6,7/8), then the first number represents the point size of the boxhead, the second number represents the point size of the body of the table, and the third number represents the leading point size of the body of the table[71]. Convert the point sizes according to the following table:

Point size	HTML font size
0 [72]	0
1 [73]	1
2	1
3	1
4 [74]	1
5	1
6 [75]	1
7 [76]	2
8 [77]	3
9	4
10	5
11	5
12	6
13	6
14	7
Over 14	7

(a) Store the point size of the second number as the {Body point size}.

(b) Store the HTML font size of the first number as the {Boxhead HTML font size}.

(c) Store the HTML font size of the second number as the {Body HTML font size}.

(c-1) Store the point size of the third number as {interline leading}.

(d) If {bearoff default} = “on”, then

(i) Multiply the value of {Body point size} by 0.4; round it off to the nearest whole number; and move it to {bearoff}[78].

(ii) Set {bearoff default} to: off

(e) Use the above table to calculate the HTML font size of a point size equal to {Body point size} + 2. Store the HTML font size that results as {I26 HTML font size}.

(f) Subtract the value of {Body point size} from {interline leading}.

(g) Multiply {interline leading} by 0.8 and round off the result to the nearest whole number.

(h) If {interline leading} is greater than {bearoff}, then set {bearoff} to the value of {interline leading}.

(A.13) If the argument contains an “f” (footnote point size)[79] followed by a number and a comma, convert the point size according to the following table and store it as the {Footnote HTML font size}:

Footnote point size	Footnote HTML font size
1	1
2	1
3	1
4	1
5	1
6	1
7	2
8	3
9	4
10	5
11	5
12	6
13	6
14	7
Over 14	7

(A.14) If the argument contains a “g”, a number, and a comma[80], then, store the number as {Grid} and {original grid}.

(A.15) If the argument contains a “t”, a number, and a comma[81], then, store the number as {Typeface} and {original typeface}.

(A.16) If the argument contains an “aw,” (absolute width)[82] and a comma, then set {absolute width switch} to: on

(A.17) If the argument contains an “aw” followed by a number and a comma, then store the number as {absolute width indent}.

(A.18) If the argument contains a “bl,” (block style)[83], then set {block style} to: on

(A.19) If the argument contains a “bl”, followed by a locator and an em-quad[84], then

add to {error file}: {TITLE NUMBER} USC{appendix}{SECTION NUMBER}{long subsection} ({text field}) – undefined argument in c-code – bl em-quad – see Subformat Generation MicroComp (2/1/97), page 4 (item 15).

(A.20) If the argument contains an “o” (offset)[85] followed by a number and a comma, then store the number as {table offset}.

(A.21) If the argument contains an “i1” (indentations)[86] followed by a comma, then set {stub indent limit switch} to: on

B. Column definitions within the arguments for bell-c

The number of columns in the table has already been defined (see item A.1(a), above). The bell-c arguments that follow (items B.1 to B.7A) define the attributes of each column. The columns are defined in the order that the data occurs (i.e., the first (i.e., left-most) column is defined first, the next column is defined second, etc.). When storing the attributes, the column must also be stored (e.g., as the index of an array).

(B.1) If the argument contains an “s” (stub)[87] followed by a number and

· a comma,

· a b and a comma,

· a C and a comma,

· a j and a comma,

· an L and a comma,

· an n and a comma,

· a p and a comma,

· an R and a comma, or

· a V and a comma,

then

(a) increment {column} by 1

(b) set {align}_{column}: left

(c) (i) store the number that followed the “s” as the {column width in points}_{column}.

(ii) if {absolute width switch} is “off”, then double the value stored in {column width in points}_{column}.

(d) add the value of the {column width in points}_{column} to the {table width in points}

(d-1) if {table-wide justification} is “on”, then set {align}_{column} to: justify

(e) if the delimiter was an “R” and a comma, then set {align}_{column} to: right

(f) if the delimiter was a “C” and a comma, then set {align}_{column} to: center

(g) if the delimiter was a “j” and a comma, then set {align}_{column} to: justify

(h) set {valign}_{column}to: top

(i) if {row bottom leadering} is “on”, then set {valign}_{column} to: bottom

(j) if the delimiter was an “n” and a comma, then:

(1) set {rules value} to: cols

(2) if {vertical rule suppression}_{column} does not equal blank, then

(A) set {vertical rule suppression}_{column} to: bordercolor= “#FFFFFF”

(B) go to instruction (j)(4)

(3) set {vertical rule suppression}_{column} to: bordercolorlight=“#FFFFFF”

(4) set {vertical rule suppression}_{column}₊₁ to: bordercolordark=“#FFFFFF”

(k) if the delimiter was a “p” and a comma, then

(1) increment {number of columns in table} by one

(2) increment {column} by one

(3) set {vertical rule}_{column} to: p

(4) set {column width in points}_{column} to zero

(l) if the delimiter was a “b” and a comma, then

(1) increment {number of columns in table} by one

(2) increment {column} by one

(3) set {vertical rule}_{column} to: b

(4) set {column width in points}_{column} to zero

(B.2) If the argument contains an “r” (reading column width)[88] followed by a number and

· a comma,

· a b and a comma,

· a C and a comma,

· a j and a comma,

· an L and a comma,

· an n and a comma,

· a p and a comma,

· an R and a comma, or

· a V and a comma,

then

(a) increment {column} by 1

(b) set {align}_{column} to: left

(c) (i) store the number that followed the “r” as the {column width in points}_{column}

(ii) if {absolute width switch} is “off”, then double the value stored in {column width in points}_{column}.

(d) add the value of the {column width in points}_{column} to the {table width in points}

(d-1) if {table-wide justification} is “on”, then set {align}_{column} to: justify

(e) if the delimiter was an “R” and a comma, then set {align}_{column}to: right

(f) if the delimiter was a “C” and a comma, then set {align}_{column} to: center

(g) if the delimiter was a “j” and a comma, then set {align}_{column} to: justify

(h) set {valign}_{column} to: top

(i) if {row bottom leadering} is “on”, then set {valign}_{column}to: bottom

(j) if {block style} is “on”, then delete the contents of {bell-D indent}_{column}.

(k) if the delimiter was an “n” and a comma, then:

(1) set {rules value} to: cols

(2) if {vertical rule suppression}_{column} does not equal blank, then

(A) set {vertical rule suppression}_{column} to: bordercolor= “#FFFFFF”

(B) go to instruction (k)(4)

(3) set {vertical rule suppression}_{column} to: bordercolorlight=“#FFFFFF”

(4) set {vertical rule suppression}_{column}₊₁ to: bordercolordark=“#FFFFFF”

(l) if the delimiter was a “p” and a comma, then

(1) increment {number of columns in table} by one

(2) increment {column} by one

(3) set {vertical rule}_{column} to: p

(4) set {column width in points}_{column} to zero

(m) if the delimiter was a “b” and a comma, then

(1) increment {number of columns in table} by one

(2) increment {column} by one

(3) set {vertical rule}_{column} to: b

(4) set {column width in points}_{column} to zero

(B.3) If the argument contains a comma, followed by a whole number (figure column)[89], followed by

· a comma,

· a b and a comma,

· a C and a comma,

· a j and a comma,

· an L and a comma,

· an n and a comma,

· a p and a comma,

· an R and a comma, or

· a V and a comma,

then

(a) increment {column} by 1

(b) set {align}_{column} to: right

(c) (i) store the number as the {column width in points}_{column}

(ii) if {absolute width switch} is “on”, then multiply {column width in points}_{column} by five.

(d) add the value of the {column width in points}_{column} to the {table width in points}

(e) if the delimiter was an “L” and a comma, then set {align}_{column} to: left

(f) if the delimiter was a “C” and a comma, then set {align}_{column} to: center

(g) if the delimiter was a “j” and a comma, then set {align}_{column}to: justify

(h) set {valign}_{column} to: top

(i) if {row bottom leadering} is “on”, then set {valign}_{column} to: bottom

(j) if the delimiter was an “n” and a comma, then:

(1) set {rules value} to: cols

(2) if {vertical rule suppression}_{column} does not equal blank, then

(A) set {vertical rule suppression}_{column} to: bordercolor= “#FFFFFF”

(B) go to instruction (j)(4)

(3) set {vertical rule suppression}_{column} to: bordercolorlight=“#FFFFFF”

(4) set {vertical rule suppression}_{column}₊₁ to: bordercolordark=“#FFFFFF”

(k) if the delimiter was a “p” and a comma, then

(1) increment {number of columns in table} by one

(2) increment {column} by one

(3) set {vertical rule}_{column} to: p

(4) set {column width in points}_{column} to zero

(l) if the delimiter was a “b” and a comma, then

(1) increment {number of columns in table} by one

(2) increment {column} by one

(3) set {vertical rule}_{column} to: b

(4) set {column width in points}_{column} to zero

(B.4) If the argument contains a pair of numbers with any character (other than comma or a space) between them (alignment column)[90] , followed by

· a comma,

· a b and a comma,

· an n and a comma, or

· a p and a comma,

then

(a) increment {column} by 1

(b) store the first number as the {left alignment}_{column}

(c) store the separator character as the {separator character}_{column}

(d) store the second number as the {right alignment}_{column}

(e) set {align}_{column} to: char” char=“{separator character}

(f)(i) calculate the value of {column width in points}_{column} according to the formula: {left alignment}_{column} + {right alignment}_{column} + 1 = {column width in points}_{column}

(ii) if {absolute width switch} is “on”, then recalculate the value of {column width in points}_{column}according to the formula (({column width in points}_{column} – 1) * 5) + 1 = {column width in points}_{column}

(g) add the value of the {column width in points}_{column} to the {table width in points}.

(h) set {valign}_{column} to: top

(i) if {row bottom leadering} is “on”, then set {valign}_{column} to: bottom

(j) if the delimiter was an “n” and a comma, then:

(1) set {rules value} to: cols

(2) if {vertical rule suppression}_{column} does not equal blank, then

(A) set {vertical rule suppression}_{column} to: bordercolor= “#FFFFFF”

(B) go to instruction (j)(4)

(3) set {vertical rule suppression}_{column} to: bordercolorlight=“#FFFFFF”

(4) set {vertical rule suppression}_{column}₊₁ to: bordercolordark=“#FFFFFF”

(k) if the delimiter was a “p” and a comma, then

(1) increment {number of columns in table} by one

(2) increment {column} by one

(3) set {vertical rule}_{column} to: p

(4) set {column width in points}_{column} to zero

(l) if the delimiter was a “b” and a comma, then

(1) increment {number of columns in table} by one

(2) increment {column} by one

(3) set {vertical rule}_{column} to: b

(4) set {column width in points}_{column} to zero

(B.5) If the argument contains an “xl” (no leaders – special reading column)[91], followed by a number and

· a comma,

· a b and a comma,

· a C and a comma,

· a j and a comma,

· an L and a comma,

· an n and a comma,

· a p and a comma,

· an R and a comma, or

· a V and a comma,

then

(a) increment {column} by 1

(b) set {align}_{column} to: left

(c) store the number that followed the “xl” as the {column width in points}_{column}

(d) add the value of the {column width in points}_{column} to the {table width in points}

(d-1) if {table-wide justification} is “on”, then set {align}_{column} to: justify

(e) if the delimiter was an “R” and a comma, then set {align}_{column} to: right

(f) if the delimiter was a “C” and a comma, then set {align}_{column} to: center

(g) if the delimiter was a “j” and a comma, then set {align}_{column} to: justify

(h) set {valign}_{column} to: top

(i) if {row bottom leadering} is “on”, then set {valign}_{column} to: bottom

(j) if the delimiter was an “n” and a comma, then:

(1) set {rules value} to: cols

(2) if {vertical rule suppression}_{column} does not equal blank, then

(A) set {vertical rule suppression}_{column} to: bordercolor= “#FFFFFF”

(B) go to instruction (j)(4)

(3) set {vertical rule suppression}_{column} to: bordercolorlight=“#FFFFFF”

(4) set {vertical rule suppression}_{column}₊₁ to: bordercolordark=“#FFFFFF”

(k) if the delimiter was a “p” and a comma, then

(1) increment {number of columns in table} by one

(2) increment {column} by one

(3) set {vertical rule}_{column} to: p

(4) set {column width in points}_{column} to zero

(l) if the delimiter was a “b” and a comma, then

(1) increment {number of columns in table} by one

(2) increment {column} by one

(3) set {vertical rule}_{column} to: b

(4) set {column width in points}_{column} to zero

(B.6) If the argument contains an “xs” (no spread – special reading column)[92], followed by a number and

· a comma,

· a b and a comma,

· a C and a comma,

· a j and a comma,

· an L and a comma,

· an n and a comma,

· a p and a comma,

· an R and a comma, or

· a V and a comma,

then

(a) increment {column} by 1

(b) set {align}_{column}: left

(c) store the number that followed the “xs” as the {column width in points}_{column}

(d) add the value of the {column width in points}_{column} to the {table width in points}

(d-1) if {table-wide justification} is “on”, then set {align}_{column}to: justify

(e) if the delimiter was an “R” and a comma, then set {align}_{column} to: right

(f) if the delimiter was a “C” and a comma, then set {align}_{column} to: center

(g) if the delimiter was a “j” and a comma, then set {align}_{column}to: justify

(h) set {valign}_{column} to: top

(i) if {row bottom leadering} is “on”, then set {valign}_{column} to: bottom

(j) if the delimiter was an “n” and a comma, then:

(1) set {rules value} to: cols

(2) if {vertical rule suppression}_{column} does not equal blank, then

(A) set {vertical rule suppression}_{column} to: bordercolor= “#FFFFFF”

(B) go to instruction (j)(4)

(3) set {vertical rule suppression}_{column} to: bordercolorlight=“#FFFFFF”

(4) set {vertical rule suppression}_{column}₊₁ to: bordercolordark=“#FFFFFF”

(k) if the delimiter was a “p” and a comma, then

(1) increment {number of columns in table} by one

(2) increment {column} by one

(3) set {vertical rule}_{column} to: p

(4) set {column width in points}_{column} to zero

(l) if the delimiter was a “b” and a comma, then

(1) increment {number of columns in table} by one

(2) increment {column} by one

(3) set {vertical rule}_{column} to: b

(4) set {column width in points}_{column} to zero

(B.7) If the argument contains an “xls” (no leaders or spread – special reading column), followed by

· a comma, [93]

· a b and a comma,

· a C and a comma, [94]

· a j and a comma,

· an L and a comma,

· an n and a comma,

· a p and a comma,

· an R and a comma,

· a V and a comma,

then

(a) increment {column} by 1

(b) move the following value to {align}_{column} to: left

(c) store the number that followed the “xls” as the {column width in points}_{column}

(d) add the value of the {column width in points}_{column} to the {table width in points}

(d-1) if {table-wide justification} is “on”, then set {align}_{column} to: justify

(e) if the delimiter was an “R” and a comma, then set {align}_{column} to: right

(f) if the delimiter was a “C” and a comma, then set {align}_{column} to: center

(g) if the delimiter was a “j” and a comma, then set {align}_{column} to: justify

(h) set {valign}_{column} to: top

(i) if {row bottom leadering} is “on”, then set {valign}_{column} to: bottom

(j) if the delimiter was an “n” and a comma, then:

(1) set {rules value} to: cols

(2) if {vertical rule suppression}_{column} does not equal blank, then

(A) set {vertical rule suppression}_{column} to: bordercolor= “#FFFFFF”

(B) go to instruction (j)(4)

(3) set {vertical rule suppression}_{column} to: bordercolorlight=“#FFFFFF”

(4) set {vertical rule suppression}_{column}₊₁ to: bordercolordark=“#FFFFFF”

(k) if the delimiter was a “p” and a comma, then

(1) increment {number of columns in table} by one

(2) increment {column} by one

(3) set {vertical rule}_{column} to: p

(4) set {column width in points}_{column} to zero

(l) if the delimiter was a “b” and a comma, then

(1) increment {number of columns in table} by one

(2) increment {column} by one

(3) set {vertical rule}_{column} to: b

(4) set {column width in points}_{column} to zero

(B.7A) If the argument contains a “tr” (tracer column), followed by a number, followed by a

· a comma,

· a b and a comma,

· a C and a comma,

· a j and a comma,

· an L and a comma,

· an n and a comma,

· a p and a comma,

· an R and a comma,

· a V and a comma,

then

(a) increment (column} by 1

(b) set {align}_{column}to: right

(c) store the number as {column width in points}_{column}

(d) if {absolute width switch} is “on”, then multiply {column width in points}_{column} by five

(e) add {column width in points}_{column} to {table width in points}

(f) if the delimiter was an “L” and a comma, then set {align}_{column} to: left

(g) if the delimiter was an “C” and a comma, then set {align}_{column} to: center

(h) if the delimiter was a “j” and a comma, then set {align}_{column} to: justify

(i) (1) set {valign}_{column}to: bottom

(2) if {top leadering switch} is “on”, then set {valign}_{column} to: top

(j) set {tracing column switch} to: on

(k) add the following to {error file}: {TITLE NUMBER} USC{appendix}{SECTION NUMBER}{long subsection} ({text field}) – attention – verify accuracy of tracing column rendering – see Subformat Generation MicroComp (2/1/97) pages 2 (locator 50) and 4 (item 18), and GPO Style Manual section 13.119.

(l) if the delimiter was an “n” and a comma, then:

(1) set {rules value} to: cols

(2) if {vertical rule suppression}_{column} does not equal blank, then

(A) set {vertical rule suppression}_{column} to: bordercolor= “#FFFFFF”

(B) go to instruction (l)(4)

(3) set {vertical rule suppression}_{column} to: bordercolorlight=“#FFFFFF”

(4) set {vertical rule suppression}_{column}₊₁ to: bordercolordark=“#FFFFFF”

(m) if the delimiter was a “p” and a comma, then

(1) increment {number of columns in table} by one

(2) increment {column} by one

(3) set {vertical rule}_{column} to: p

(4) set {column width in points}_{column} to zero

(n) if the delimiter was a “b” and a comma, then

(1) increment {number of columns in table} by one

(2) increment {column} by one

(3) set {vertical rule}_{column} to: b

(4) set {column width in points}_{column} to zero

(B.8) Once the final column has been processed,

(a) if {absolute width switch} is “on”, then

(i) set {table width in pixels} to the three times the value of {table width in points} and round off to the nearest whole number.

(ii) if {table width in pixels} is greater than 718, then set {centering table width} to the value of {table width in pixels} + 2

(a-1) if {absolute width indent} is greater than zero, then

(i) multiply {absolute width indent} times 2.7 and round off to the nearest whole number

(ii) add {absolute width indent} to {centering table width}

(iii) if {absolute width switch} is “off”, then subtract {absolute width indent} from {table width in pixels}

(a-2) if {absolute width indent} is greater than zero, then

(i) multiply {table offset} times 2.7 and round off to the nearest whole number

(ii) add {table offset} to {centering table width}

(iii) if {absolute width switch} is “off”, then subtract {table offset} from {table width in pixels}

(b) (i) if {number of columns in table} is greater than one, then calculate (for each value of {column}, from one to {number of columns in table} - 1) the {column width in pixels}_{column}[95] by using the following formula:

({column width in points}_{column} / {table width in points}) H {table width in pixels} = {column width in pixels}_{column}

(ii) if {number of columns in table} is greater than one, then calculate {column width in pixels}_{{number of columns in table}}by adding all of the values of {column width in pixels}₁ through {column width in pixels}_{{number of columns in table}}_{– 1} and then subtracting the total from the value of {table width in pixels}

(iii) if {number of columns in table} equals one,[96] then set {column width in pixels}₁ to the value of {table width in pixels}.

(iv) for each value of {column}, where {vertical rule}_{column} is “p”,

(A) set {column width in pixels}_{column}to the value of {gap between parallel lines} divided by four.

(B) Round off {column width in pixels}_{column}to the nearest whole number.

(C) Add the value of {column width in pixels}_{column}to {table width in pixels}.

(D) If {table width in pixels} + 2 > {centering table width}, then set {centering table width} to the value of {table width in pixels} + 2.

(v) for each value of {column}, where {vertical rule}_{column} is “b”,

(A) increment {table width in pixels} by one.

(B) If {table width in pixels} + 2 > {centering table width}, then set {centering table width} to the value of {table width in pixels} + 2

(c) Multiply {leading} by 0.8. Round off {leading} to the nearest whole number. If {leading} is less than zero, then set {leading} to zero. For every occurrence of {leading}, insert in the {Leading file}: <tr></tr>

(d) (i) If {text field} is “STATUTE”, then output: <a onMouseOver=“window.status=‘{TITLE NUMBER} USC{appendix}{SECTION NUMBER}{long subsection}’; return true”>

(ii) Set {frame} to: void

(iii) Set {border} to: 0

(iv) If {bell-y} equals one, then

(1) Set {frame} to: lhs

(2) Set {Border} to: one

(v) output the following: <table width=“{centering table width}” border=“{border}” cellpadding=“0” frame=“{frame}” rules=“none”>{Leading file}<tr><td align=“center”>

(e) clear out the {Leading file}.

(f) set {leading} to seven.

(g) If {ns switch} is “on”, then set {leading} to zero.

C. Codes within a table

As noted in the introduction to Bell-c, bell codes within a table (i.e., between a bell-c and a bell-e) may have different characteristics than the same bell codes outside of a table. In the chart below, find the line associated with the bell code, and

(1) execute the special processing instructions

(2) replace the bell code with the HTML coding shown in the table in the “Precede text with” column;

(3) insert the text that followed the bell-code, up to the next bell[97];

(4) insert the HTML coding shown in the “Follow text with” column;

(5) If the bell-code is a bell-h or bell-I, then store the {FOTP} value

Bell codes within bell-c table
A			(1) Set {table row} to sixty. - - - (2) Add to {error file}: {TITLE NUMBER} USC{appendix} {SECTION NUMBER}{long subsection} ({text field}) – warning – improper use of bell-A in table – Subformat Generation MicroComp (2/1/97) page 2, footnote f, states that bell-A is not to be used inside of a table and a bell-z is to be used instead.
b			See boxhead processing instructions 9(C)(c) and 10(c).	26 U.S.C. § 1252(a)(3)
D	<td width={column width in pixels}_{column} {current column attribute} {vertical rule suppression}_{column}><font size=“{current HTML font size}”>{bell-D indent}_{column}	</font></td>	(1) Set {number of grid changes} and {number of typeface changes} to zero. - - - (2) New column processing . - - - (2A) Execute bell-c instruction F(9)(e) and then return. - - - (3) If {I25 switch} is off, then: (a) Set {current column attribute} to: align=“{align}_{column}” valign=“{valign}_{column}” (b) Set {current HTML font size} to the value of {Body HTML font size} (c) If {row bottom leadering} is “on”, then set {current column attribute} to: align=“{align}_{column}” valign=“bottom” - - - (4) If {I25 switch} is on, then: (a) Set {current column attribute} to: align=“center” valign=“top” (b) Set {current HTML font size} to the value of {Boxhead HTML font size} (c) If {table-wide justification} is “on” and {row bottom leadering} is “off”, then set {current column attribute} to: align=“justify” valign=“top” (d) If {table-wide justification} is “on” and {row bottom leadering} is “on”, then set {current column attribute} to: align=“justify” valign=“bottom” (e) Add to the {I25 repeated headings file} a copy of all of the material output as a result of the bell-D. - - - (5) Set {Grid} to the value of {original grid}. - - - (6) Set {Typeface} to the value of {original typeface}. - - - (7) Process grid and typeface values according to G-codes and T-codes . - - - (8) If {number of columns in table}={column}, then follow the “Follow text with” material with: </tr>	1 U.S.C. (prec. ch. 1) 5 U.S.C. prec. pt. I (Table Showing Disposition of All Sections of Former Title 5)
e	</table></td></tr></table>ÃÃ		(1) Zero out the values for: · {align}_{1 to {number of columns in table}} · {alignment} · {Body HTML font size} · {Boxhead HTML font size} · {colspan} · {column width in pixels}_{1 to {number of columns in table}} · {column width in points}_{1 to {number of columns in table}} · {current column attribute} · {current HTML font size} · {Footnote HTML font size} · {footnote switch} · {HTML border value} · {HTML frame value} · {I95 HTML font size} · {I96 HTML font size} · {left alignment} · {right alignment} · {separator character} · {table width in pixels} · {table width in points} · {valign}_{1 to {number of columns in table}} Note: {leading} is initialized in bell-c instruction B.8, instead of as part of the bell-e processing. - - - (2) If {column} does not equal {number of columns in table}, then precede the “Precede text with” material with: </tr> - - - (3) set {table switch} to: off - - - (4) clear out {repeated headings file} and {I25 repeated headings file}. - - - (5) if {text field} is “STATUTE”, then follow the “Precede text with” material with: </a>	5 U.S.C. § 5332 note (sched. 3)
f	</table><table width=“{table width in pixels}” border=“0” cellspacing=“0” cellpadding=“0” frame=“void” rules=“none”>{footnote top leading}<tr><td width=“{table width in pixels}” align=“justify”> <div align="justify"><font size=“{Footnote HTML font size}”>    <!-- -->	</font></div></td></tr>	(1) Increment {footnote switch} by one. - - - (2) Set {footnote top leading} to a blank space. - - - (3) If {footnote switch} = 1, then set {footnote top leading} to: <tr> </tr><tr></tr><tr> </tr><tr></tr><tr> </tr><tr></tr> - - - (4) Set {number of grid changes} and {number of typeface changes} to zero.	5 U.S.C. § 5332 note (sched. 3)
g			Standard Bell-g processing	36 U.S.C. § 101 (Table Showing Disposition of All Sections From Title 36)
G			Standard Bell-G/Bell-T processing	21 U.S.C. § 350a(i)(2)(B)
h			Boxhead processing	4 U.S.C. § 1 note (Ex. Ord. No. 10798, § 21)
I01	<tr><td {width attribute} align=“{align}_{column}” valign=“{valign}_{column}” {vertical rule suppression}_{column}><div align=“{align}_{column}”><font size=“{Body HTML font size}”> ◊	</font></div></td>	Standard Reading/Stub Column processing	1 U.S.C. (prec. ch. 1)
I02	<tr><td {width attribute} align=“{align}_{column}” valign=“{valign}_{column}” {vertical rule suppression}_{column}><div align=“{align}_{column}”><font size=“{Body HTML font size}”>{stub indent file} ◊	</font></div></td>	Standard Reading/Stub Column processing	21 U.S.C. § 350a(i)(2)(B)
I03	<tr><td {width attribute} align=“{align}_{column}” valign=“{valign}_{column}” {vertical rule suppression}_{column}><div align=“{align}_{column}”><font size=“{Body HTML font size}”>{stub indent file} ◊	</font></div></td>	Standard Reading/Stub Column processing	11 U.S.C. app. (Bankr. R.) rule 7001 note
I04	<tr><td {width attribute} align=“{align}_{column}” valign=“{valign}_{column}” {vertical rule suppression}_{column}><div align=“{align}_{column}”><font size=“{Body HTML font size}”>{stub indent file} ◊	</font></div></td>	Standard Reading/Stub Column processing	20 U.S.C. § 1091(r)(1)
I05	<tr><td {width attribute} align=“{align}_{column}” valign=“{valign}_{column}” {vertical rule suppression}_{column}><div align=“{align}_{column}”><font size=“{Body HTML font size}”>{stub indent file} ◊	</font></div></td>	Standard Reading/Stub Column processing	28 U.S.C. app. (Fed. Cl. R.) app. J (rule 16)
I06	<tr><td {width attribute} align=“{align}_{column}” valign=“{valign}_{column}” {vertical rule suppression}_{column}><div align=“{align}_{column}”><font size= “{Body HTML font size}”>{stub indent file} ◊	</font></div></td>	Standard Reading/Stub Column processing
I07	<tr><td {width attribute} align=“{align}_{column}” valign=“{valign}_{column}” {vertical rule suppression}_{column}><div align=“{align}_{column}”><font size=“{Body HTML font size}”>{stub indent file} ◊	</font></div></td>	Standard Reading/Stub Column processing
I08	<tr><td {width attribute} align=“{align}_{column}” valign=“{valign}_{column}” {vertical rule suppression}_{column}><div align=“{align}_{column}”><font size=“{Body HTML font size}”>{stub indent file} ◊	</font></div></td>	Standard Reading/Stub Column processing
I09	<tr><td {width attribute} align=“{align}_{column}” valign=“{valign}_{column}” {vertical rule suppression}_{column}><div align=“{align}_{column}”><font size=“{Body HTML font size}”>{stub indent file} ◊	</font></div></td>	Standard Reading/Stub Column processing
I10	<tr><td {width attribute} align=“{align}_{column}” valign=“{valign}_{column}” {vertical rule suppression}_{column}><div align=“{align}_{column}”><font size=“{Body HTML font size}”>{stub indent file} ◊	</font></div></td>	Standard Reading/Stub Column processing
I11	<tr><td {width attribute} align=“{align}_{column}” valign=“{valign}_{column}” {vertical rule suppression}_{column}><div align=“{align}_{column}”><font size=“{Body HTML font size}”> ◊	</font></div></td>	Standard Reading/Stub Column processing	1 U.S.C. (prec. ch. 1)
I12	<tr><td {width attribute} align=“{align}_{column}” valign=“{valign}_{column}” {vertical rule suppression}_{column}><div align=“{align}_{column}”><font size=“{Body HTML font size}”>{stub indent file} ◊	</font></div></td>	Standard Reading/Stub Column processing
I13	<tr><td {width attribute} align=“{align}_{column}” valign=“{valign}_{column}” {vertical rule suppression}_{column}><div align=“{align}_{column}”><font size=“{Body HTML font size}”>{stub indent file} ◊	</font></div></td>	Standard Reading/Stub Column processing
I14	<tr><td {width attribute} align=“{align}_{column}” valign=“{valign}_{column}” {vertical rule suppression}_{column}><div align=“{align}_{column}”><font size=“{Body HTML font size}”>{stub indent file} ◊	</font></div></td>	Standard Reading/Stub Column processing
I15	<tr><td {width attribute} align=“{align}_{column}” valign=“{valign}_{column}” {vertical rule suppression}_{column}><div align=“{align}_{column}”><font size=“{Body HTML font size}”>{stub indent file} ◊	</font></div></td>	Standard Reading/Stub Column processing
I16	<tr><td {width attribute} align=“{align}_{column}” valign=“{valign}_{column}” {vertical rule suppression}_{column}><div align=“{align}_{column}”><font size=“{Body HTML font size}”>{stub indent file} ◊	</font></div></td>	Standard Reading/Stub Column processing
I17	<tr><td {width attribute} align=“{align}_{column}” valign=“{valign}_{column}” {vertical rule suppression}_{column}><div align=“{align}_{column}”><font size=“{Body HTML font size}”>{stub indent file} ◊	</font></div></td>	Standard Reading/Stub Column processing
I18	<tr><td {width attribute} align=“{align}_{column}” valign=“{valign}_{column}” {vertical rule suppression}_{column}><div align=“{align}_{column}”><font size=“{Body HTML font size}”>{stub indent file} ◊	</font></div></td>	Standard Reading/Stub Column processing
I19	<tr><td {width attribute} align=“{align}_{column}” valign=“{valign}_{column}” {vertical rule suppression}_{column}><div align=“{align}_{column}”><font size=“{Body HTML font size}”>{stub indent file} ◊	</font></div></td>	Standard Reading/Stub Column processing
I20	<tr><td {width attribute} align=“{align}_{column}” valign=“{valign}_{column}” {vertical rule suppression}_{column}><div align=“{align}_{column}”><font size=“{Body HTML font size}”>{stub indent file} ◊	</font></div></td>	Standard Reading/Stub Column processing
I21	<tr><td {width attribute} align=“{I21 alignment}”><div align=“{I21 alignment}”><font size=”{Body HTML font size}”>	</font></div></td>	(1) set {I21 alignment} to: center - - - (2) if {table-wide justification} is “on”, then set {I21 alignment} to: justify - - - (2A) if {L argument} equals 2, 4, or 6, then set {colspan} to the value of {number of columns in table} - - - (3) Standard Reading/Stub Column processing	20 U.S.C. § 1087pp(b)(4)
I22	<tr><td {width attribute} align=“{align}_{column}” valign=“{valign}_{column}” {vertical rule suppression}_{column}><div align=“{align}_{column}”><font size=“{Body HTML font size}”> ◊	</font></div></td>	Standard Reading/Stub Column processing	1 U.S.C. prec. ch. 1 (Table Showing Disposition of All Sections of Former Title 1)
I23	</table><table width=“{table width in pixels}” border=“0” cellspacing=“0” cellpadding=“0” frame=“void” rules=“none”><tr><td width=“{table width in pixels}” align=“right”><font size=“{Footnote HTML font size}”>	</font></td></tr>	(1) Standard Reading/Stub Column processing - - - (2) Add to the {error file}: {TITLE NUMBER} U.S.C.{appendix} {SECTION NUMBER}{long subsection} ({text field}) – verify accuracy of rendering of I23 in subformat generation table – see Subformat Generation MicroComp (2/1/97), page 2.
I24	<tr><td width=“{width attribute}” align=“{I24 alignment}” valign=“{valign}_{column}” {vertical rule suppression}_{column}><div align=“{I24 alignment}”><font size=“{Body HTML font size}”>   ◊	</font></div></td>	(1) if {line type} is J, then set {I24 alignment} to: justify - - - (2) if {line type} is L, then set {I24 alignment} to: left - - - (3) if {line type} is C, then set {I24 alignment} to: center - - - (4) if {line type} is R, then set {I24 alignment} to: right - - - (5) if {line type} is V, then set {I24 alignment} to: left - - - (6) Standard reading/stub column processing
I25	<tr><td {width attribute} align=“{I25 alignment}” valign=“top”><div align=“{I25 alignment}”><font size=“{Boxhead HTML font size}”>	</font></div></td>	(1) Set {I25 alignment} to: center - - - (2) If {table-wide justification} is “on”, then set {I25 alignment} to: justify - - - (3) Standard Reading/Stub Column processing - - - (4) Set {I25 switch} to: on - - - (5) Clear out the contents of {I25 repeated headings file}. - - - (6) Add to the {I25 repeated headings file} all material output as a result of the bell-I25.	20 U.S.C. § 1087oo(c)(2)
I26	<tr><td {width attribute} align=“{align}_{column}” valign=“{valign}_{column}” {vertical rule suppression}_{column}><div align=“{align}_{column}”><font size=“{I26 HTML font size}”> ◊	</font></div></td>	Standard Reading/Stub Column processing
I27			(1) Process this locator as if it were a bell-I40. - - - (2) Add the following to {error file}: {TITLE NUMBER}{long subsection} ({text field}) USC{appendix} {SECTION NUMBER}(long subsection} ({text field}) – warning – improper use of locator-27 in table – Subformat Generation MicroComp (2/1/97), page 6, in item E(2)(g) states that locator-27 is obsolete and locator-40 should be used instead.
I28	<tr><td {width attribute} align=“{I28 alignment}”><font size=“{Body HTML font size}”>	</font></td>	(1) set {I21 alignment} to: center - - - (2) if {table-wide justification} is “on”, then set {I21 alignment} to: justify - - - (3) if {L argument} equals 2, 4, or 6, then set {colspan} to the value of {number of columns in table} - - - (4) Standard Reading/Stub Column processing
I29			(1) Process this locator as if it were a bell-f. - - - (2) Add the following to {error file}: {TITLE NUMBER} USC{appendix} {SECTION NUMBER}{long subsection} ({text field}) – warning – improper use of locator-29 in table – Subformat Generation MicroComp (2/1/97), page 6, item E(2)(i), states that a bell-f is to used for footnotes, not a locator-29.
I30	<tr><td colspan=“{number of columns in table}” align=“{I30 alignment}”><div align=“{I30 alignment}”><font size=“{Body HTML font size}”>	</font></td>	(1) Set {I30 alignment} to: center - - - (2) If {table-wide justification} is “on”, set {I30 alignment} to: justify - - - (3) Standard Reading/Stub Column processing
I31	<tr><td {width attribute} align=“{align}_{column}” valign=“{valign}_{column}” {vertical rule suppression}_{column}><div align=“{align}_{column}”><font size=“{Body HTML font size}”> ◊	</font></div></td>	Standard Reading/Stub Column processing	1 U.S.C. (prec. ch. 1)
I38	<tr><td {width attribute} align=“{align}_{column}” valign=“{valign}_{column}” {vertical rule suppression}_{column}><div align=“{align}_{column}”><font size=“{Body HTML font size}”> ◊	</font></div></td>	Standard Reading/Stub Column processing
I39	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="none" rules="none"> {Leading file}<tr><td width=“120”>  </td><td width=“480”>{footnote divider file}<div align=“justify”><font size=“1”>   <!-- -->	</div></font></td></tr> </table>	(1) if the {footnote file} is not empty, then set the {leading file} and the {footnote divider file} to a blank. - - - (2) Increment {footnote switch} by one. - - - (3) [reserved] - - - (4) Do not output this material. Add it, instead, to the {footnote file} for use with document breaks (i.e., locator 80 (in formats 5800 to 5803) and bell-R)	33 U.S.C. § 1285(c)(2)
I40	<td colspan= “{colspan}” align=“{alignment}”><font size=“{Body HTML font size}” ◊	</font></td>	(1) Set {number of grid changes} and {number of typeface changes} to zero. - - - (2) The locator-40 is followed by either · ({colspan}); or · {alignment} ({colspan}) where {alignment} is “J”, “L”, or “R”, and {colspan} is a number. - - - (3) Increment {colspan} by one. - - - (4) If {alignment} = J, then set {alignment} to: justify - - - (5) If {alignment} = L, then set {alignment} to: left - - - (6) If {alignment} = R, then set {alignment} to: right - - - (7) If {alignment} = 0, and {table-wide justification} is “off”, then set {alignment} to: center - - - (7A) If {alignment} = 0, and {table-wide justification} is “on”, then set {alignment} to: justify - - - (8) Do not output the close paren or any of the material before it. - - - (9) Long table testing and processing . - - - (10) After completing the “Follow text with” processing, set {alignment} to 0.
I50	<tr><td {width attribute} align=“{align}₁” valign=“{valign}₁” {vertical rule suppression}_{column}><div align=“{align}₁”><font size=“{Body HTML font size}”>	</font></div></td>	Standard Reading/Stub Column processing
I51 to I80			(1) Take the two-digit argument that follows the bell-I, subtract 49 and subtract {column}. For each occurrence of the remaining number, act as if there is a bell-D. - - - (2) Add to {error file}: {TITLE NUMBER} USC{appendix} {SECTION NUMBER}{long subsection} ({text field}) – warning – improper use of bell-{bell code} in table – Subformat Generation MicroComp (2/1/97), page 6, item E(2)(p) states that a bell-D should be used instead.
I95	{plsfield tag}<table width=“{table width in pixels}” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none"><tr><td width=“{table width in pixels}” align="center"><font size=“{I95 HTML font size}”>	</font></td></tr><tr> </tr><tr></tr><tr></tr> <tr></tr></table>	(1) If {I95 HTML font size}=“0”, then delete the bell-I95 and all of the text that follows it through the next bell. Stop processing the bell-I95 and begin processing the next bell-code. - - - (2) If {I95 HTML font size} = 2, then: (a) if {text field} equals “MISC1”, “MISC2”, “MISC3”, “MISC4”, “MISC5”, “MISC6”, “MISC7”, or “MISC8”, then set {plsfield tag} to a blank. (b) If {text field} equals “HEAD”, “STATUTE”, “SOURCE”, or “STATAMEND”, then (1) set {text field} to: MISC1 (2) set {plsfield tag} to: <!--plsfield:MISC1--> (c) If {text field} equals “REFTEXT”, then (1) set {text field} to: MISC2 (2) set {plsfield tag} to: <!--plsfield:MISC2--> (d) If {text field} equals “COD”, then (1) set {text field} to: MISC3 (2) set {plsfield tag} to: <!--plsfield:MISC3--> (e) If {text field} equals “CHANGE”, then (1) set {text field} to: MISC4 (2) set {plsfield tag} to: <!--plsfield:MISC4--> (f) If {text field} equals “TRANS”, then (1) set {text field} to: MISC5 (2) set {plsfield tag} to: <!--plsfield:MISC5--> (g) If {text field} equals “EXEC”, then (1) set {text field} to: MISC6 (2) set {plsfield tag} to: <!--plsfield:MISC6--> (h) If {text field} equals “CROSS”, then (1) set {text field} to: MISC7 (2) set {plsfield tag} to: <!--plsfield:MISC7--> (i) If {text field} equals “SECREF”, then (1) set {text field} to: MISC8 (2) set {plsfield tag} to: <!--plsfield:MISC8--> - - - (3) [reserved] - - - (4) Set the value of {HTML font size} to the value of {I95 HTML font size} - - - (5) Set {number of grid changes} and {number of typeface changes} to zero. - - - (6) Add to the {repeated headings file}: the “Precede text with” material, the text that follows the bell-I95, the literal “<!-- --> <!-- --> Continued”, and the “Follow text with” material.	7-point miscellaneous table title: 1 U.S.C. (prec. ch. 1). 7-point Historical and Revision Notes table title: 5 U.S.C. § 101 notes. 6-point table title: 4 U.S.C. § 1 notes (Ex. Ord. No. 10834, § 33). No table title (0 point size): 4 U.S.C. § 1 notes (Ex. Ord. No. 10834, § 21).
I96	<table width=“{table width in pixels}” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none”> <tr><td width=“{table width in pixels}” align="center"><font size=“{I96 HTML font size}”>	</font></td></tr><tr> </tr><tr></tr><tr></tr> <tr></tr></table>	(1) Set the value of {HTML font size} to the value of {I96 HTML font size} - - - (2) Set {number of grid changes} and {number of typeface changes} to zero. - - - (3) Add to the {repeated headings file}: the “Precede text with” material, the text that follows the bell-I95, the literal “<!-- --> <!-- --> Continued”, and the “Follow text with” material	5 U.S.C. § 5332 note (sched. 3)
I97	<table width=“{table width in pixels}” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none”> <tr><td width=“{table width in pixels}” align="center"><font size=“{I96 HTML font size}”>	</font></td></tr><tr> </tr><tr></tr><tr></tr> <tr></tr></table>	(1) Set the value of {HTML font size} to the value of {I96 HTML font size} - - - (2) Set {number of grid changes} and {number of typeface changes} to zero. - - - (3) Add to the {repeated headings file}: the “Precede text with” material, the text that follows the bell-I95, and the “Follow text with” material	5 U.S.C. § 5332 note (sched. 3)
j	<tr bgcolor=“#000000”><td colspan=“{number of columns in table}” height=“{bottom of boxhead rule height}”><font size=“1”></font></td></tr>		(1) Clear the {boxheads file}. - - - (2) Set {colspan} to one. - - - (3) Divide {bottom of boxhead rule weight}[98] by four, round off the result to the nearest whole number, and store it as {bottom of boxhead rule height}. - - - (4) If {bottom of boxhead rule height} equals zero or {HTML frame value} equals “void”, then do not output the “Precedes text with” material. - - - (5) Examine all of the text between bell-j and bell-e. If it consists entirely of photocomposition codes and blanks[99], then (a) delete all of the text to the bell-e, and (b) begin processing with the bell-e. - - - (6) Any material that is output should also be added to the {repeated headings file}.	1 U.S.C. (prec. ch. 1) 16 U.S.C. § 3631(f) 15 U.S.C. § 205 note (Measures of Length)
J	<div align=“justify”>	</div>	In the previous <td> or <th> tag, delete any “align=” instruction and replace the instruction with: align=“justify”
l			(1) Set {row bottom leadering} to: on - - - (2) In the previous <td>< or <th> tag, delete any “valign=” instruction and replace the instruction with: valign=“bottom”	16 U.S.C. § 3631(f)
L			In the previous <td> or <th> tag, delete any “align=” instruction and replace the instruction with: align=“left”	26 U.S.C. § 1252(a)(3)
m			See boxhead processing instructions 9(C)(d) and 10(d)
N			Delete the bell-N	33 U.S.C. § 1285(c)(2)
oi0			In the previous <td> or <th> tag, replace the “align” attribute with: align=“center”	5 U.S.C. § 5332 note (sched. 3)
oi1	<!-- -->    <!-- -->		In the previous <td> or <th> tag, replace the “align” attribute with: align=“left”
oi2	<!-- -->    <!-- -->		In the previous <td> or <th> tag, replace the “align” attribute with: align=“left”
oi3	<!-- -->        <!-- -->		In the previous <td> or <th> tag, replace the “align” attribute with: align=“left”
oi4	<!-- -->           <!-- -->		In the previous <td> or <th> tag, replace the “align” attribute with: align=“left”
oi5	<!-- -->                <!-- -->		In the previous <td> or <th> tag, replace the “align” attribute with: align=“left”
oi6	<!-- -->                    <!-- -->		In the previous <td> or <th> tag, replace the “align” attribute with: align=“left”
oi7	<!-- -->                        <!-- -->		In the previous <td> or <th> tag, replace the “align” attribute with: align=“left”
oi8	<!-- -->                            <!-- -->		In the previous <td> or <th> tag, replace the “align” attribute with: align=“left”
oi9	<!-- -->                                <!-- -->		In the previous <td> or <th> tag, replace the “align” attribute with: align=“left”
P	<br>	</br>		1 U.S.C. (prec. ch. 1)
q			(1) If {column} does not equal {number of columns in table}, then output: </tr> - - - (2) The bell-q is followed by a two-digit argument. Subtract the argument from {table leading}.
Q			(1) If {column} does not equal {number of columns in table}, then output: </tr> - - - (2) The bell-Q is followed by a two-digit argument. Add the argument to {table leading}.	5 U.S.C. § 5332 note (sched. 3)
r			Horizontal Rule processing	“n” and “s” options: 5 U.S.C. § 5332 note (sched. 8, pt. I)
R			In the previous <td> or <th> tag, delete any “align=” instruction and replace the instruction with: align=“right”	26 U.S.C. § 1252(a)(3)
s			Add to {colspan} the argument that follows the bell-s. If the argument is zero, then set {colspan} to one.	5 U.S.C. § 5332 note (sched. 3)
t			See boxhead processing instructions 9(C)(b) and 10(b).
T			standard Bell-G/Bell-T processing	Examples of %T1, %T3, and %T4 at 1 U.S.C. (prec. ch. 1).
xl			Delete bell-xl.	1 U.S.C. prec. ch. 1 (Table Showing Disposition of All Sections of Former Title 1)
z			(1) Add to {error file}: {TITLE NUMBER} USC{appendix} {SECTION NUMBER}{long subsection} ({text field}) – attention – verify accuracy of bell-z in table - - - (2) set {table row} to sixty.
.			Delete the bell-period
any other			Add to {error file}: {TITLE NUMBER} USC{appendix} {SECTION NUMBER}{long subsection} ({text field}) – unidentified bell code in table – {Bell code}

D. Boxhead processing

(1) Load everything from the first bell-h1 to the bell-j into {boxheads file}.

(2) Each bell-h has a one-digit numerical argument (from 1 to 6). Store the highest bell-h argument contained in the {boxheads file} as the {number of rows of boxheads}.

(3) (a) Set {original bell-h argument}, {current bell-h argument}, {previous bell-h argument}, and {next bell-h argument} to one.

(b) If {HTML frame value} equals “void”, and (for all values of {N} from 1 to {number of columns in table}) {vertical rule suppression}_{N} and {vertical rule}_{N}are blank, then set {HTML border value} to zero.

(c) Set {number of grid changes} and {number of typeface changes} to zero.

(d) Set {column} to zero.

(e) Add {boxhead top leading} to {table leading}, multiply that sum by 0.8, round that product off to the nearest whole number, and add the following to {boxhead top leading file} for each occurrence of {table leading}: <tr></tr>

(f) Set {table leading} to zero.

(4) (a) Output and also add to the {repeated headings file}: <table width=“{table width in pixels}” border=“0” cellspacing=“0” cellpadding=“0” frame=“void” rules=“none”><tr><td></td></tr>{boxhead top leading file}</table><table width=“{table width in pixels}” border=“{HTML border value}” cellspacing=“0” cellpadding=“{bearoff}” frame=“{HTML frame value}” rules=“{rules value}”><tr>

(b) If {Boxhead HTML font size} equals zero[100], then

(i) Output and also add to the {repeated headings file}: </tr>

(ii) Clear out the {boxheads file}

(iii) Set {colspan} to one

(iv) Set {column} to the value of {number of columns in table} [101]

(v) Resume normal processing for bell codes within a bell-c table, starting with the bell code that follows the bell-j.

(5) Go to the beginning of the {boxheads file}.

(6) Set {rowspan} according to the formula {rowspan} = 1 + {number of rows of boxheads} – {original bell-h argument}

(7) Set {colspan} to one.

(8) Within the {boxheads file} go to the next[102] occurrence of a bell-h{original bell-h argument} (or the bell-j, whichever comes first).

(a) If the bell-h{original bell-h argument} is reached, store the location of the bell-h.

(b) If the bell-j is reached, then

(i) output and also add to the {repeated headings file}: </tr>

(ii) increment {original bell-h argument} by 1.

(iii) if {original bell-h argument} is greater than {number of rows of boxheads}, then resume normal processing for bell codes within a bell-c table, starting with the bell-j.

(iv) go to Step 5.

(9) (A) Within the {boxheads file} go to the next occurrence of a bell-h[103] (or bell-j, whichever comes first).

(B) If a bell-h is reached, then

(a) store the argument that followed the bell-h whose position was stored in Step 8(a) as {current bell-h argument}.

(b) Store the argument that follows the second bell-h as {next bell-h argument}.

(c) (1) If {next bell-h argument} is greater than {current bell-h argument}, then subtract one from {rowspan}.

(2) Count the number of times bell-h occurs (a) after the bell-h{current bell-h argument} whose position was stored in Step 8(a) and (b) before the next occurrence of bell-h{current bell-h argument} (or bell-j, whichever comes first) and then set {colspan} to that number

(C) If the bell-j is reached, then:

(a) Set {boxhead valign value} to: middle

(b) If the data between the h-code whose position was stored in Step 8(a) and the bell-j contains a bell-t, then set {boxhead valign value} to: top

(c) If the data between the h-code whose position was stored in Step 8(a) and the bell-j contains a bell-b, then set {boxhead valign value} to: bottom

(d) If the data between the h-code whose position was stored in Step 8(a) and the bell-j contains a bell-m, then delete the bell-m.

(e) (1) Set {heading width} to: colspan=“{colspan}”

(2) If {colspan}=1 and {current bell-h argument}=1, then

(i) execute new column processing

(ii) set {heading width} to: width=“{column width in pixels}_{column}”

(3) Output and also add to the {repeated headings file}: <th align=“center” valign=“{boxhead valign value}” rowspan=“{rowspan}” {heading width} {vertical rule suppression}_{column}><font size=“{Boxhead HTML font size}”>

(f) Output (and also add to the {repeated headings file}) all of the text between the h-code whose position was stored in Step 8(a) and the bell-j[104]; and then delete the text (including the bell-h{current bell-h argument}) from the {boxheads file}.

(g) Output and also add to the {repeated headings file}: </font></th></tr>

(h) increment {original bell-h argument} by 1

(i) if {original bell-h argument} is greater than {number of rows of boxheads}, then resume normal processing for bell codes within a bell-c table, starting with the bell-j.

(j) Go to Step 5.

(10) (a)Set {boxhead valign value} to: middle

(b) If the data between the h-code whose position was stored in Step 8(a) and the bell-h (or bell-j) contains a bell-t, then set {boxhead valign value} to: top

(c) If the data between the h-code whose position was stored in Step 8(a) and the bell-h (or bell-j) contains a bell-b,[105] then set {boxhead valign value} to: bottom

(d) If the data between the h-code whose position was stored in Step 8(a) and the bell-h (or bell-j) contains a bell-m, then delete the bell-m.

(e) (1) Set {heading width} to: colspan=“{colspan}”

(2) If {colspan}=1 and {current bell-h argument}=1, then

(a) execute new column processing

(b) set {heading width} to: width=“{column width in pixels}_{column}”

(4) If {next bell-h argument} is greater than {current bell-h argument}, and {L argument} equals one[106], then output (and also add to the {repeated headings file}: <nobr><u style="text-decoration: underline">

(f) Output (and also add to the {repeated headings file}) all of the text between the h-code whose position was stored in Step 8(a) and the next bell-h (or the bell-j, whichever comes first)[107]; and then delete the text (plus the bell-h{current bell-h argument}) from the {boxheads file}.

(g) (1) If {next bell-h argument} is greater than {current bell-h argument}, and {L argument} equals one[108], then output (and also add to the {repeated headings file}):  </u></nobr>

(2) Output and also add to the {repeated headings file}: </font></th>

(h) Go to Step 6 .

E. Horizontal Rule Processing [109]

(1) (a) If {column} does not equal {number of columns in table}, then output: </tr> (b) Set {column} to zero.

(i) Set {double rule switch}_{N}to “off” for each value of {N} from one to {number of columns in table}.

(2) Output: <tr>

(3) The arguments of a bell-r are delimited by commas. Examine each argument.

(4) If the argument is “n”[110] then

(a) Execute new column processing .

(b) output: <td bgcolor=“#FFFFFF” height=”2”></td>

(c) if {column} = {number of columns in table}, then output: </tr>

(5) If the argument is “s”[111] then

(a) Execute new column processing.

(b) output: <td bgcolor=“#000000” height=“2”></td>

(c) if {column} = {number of columns in table}, then output: </tr>

(6) If the argument is “d” then

(a) Execute new column processing.

(b) output: <td bgcolor=“#000000” height=“2”></td>

(c) if {column} = {number of columns in table}, then output: </tr>

(d) set {double rule switch}_{column} to: on

(7) If the argument is “b” then

(a) Execute new column processing.

(b) output: <td bgcolor=“#000000” height=“3”></td>

(c) if {column} = {number of columns in table}, then output: </tr>

(8) If {double rule switch}_{column} is “on” for any value of {column}, then

(a) set {column} to one

(b) if {double rule switch}_{column}is “on”, then output: <td bgcolor=“#000000” height=“2”></td>

(c) if {double rule switch}_{column}is “off”, then output: <td bgcolor=“#FFFFFF” height=“2”></td>

(d) Execute new column processing.

(e) if {column} is less than or equal to {number of columns in table}, then return to step (b)

(f) if {column} is greater than {number of columns in table}, then output: </tr>

F. Standard Reading/Stub Column Processing

(1) (a) conduct long table testing and processing.

(b) If {table leading} is greater than zero, then multiply {table leading} by 0.8, round the product off to the nearest whole number, and (for each instance of the number) precede the “Precede text with” material with: <tr></tr>

(c) [reserved]

(d) Set {table leading} to zero.

(2) (a) Set {column} to one.

(b) Set {number of grid changes} and {number of typeface changes} to zero.

(c) If {tracing column switch} is “on” and {Bell code} is not bell-I50, then set {column} to two.

(3) [reserved]

(4) Set {width attribute} to: width=“{column width in pixels}_{column}”

(5) If {colspan} is greater than one, then set {column} to the value of {colspan} and set {width attribute} to: colspan=“{colspan}”

(6) Set {I25 switch} and {row bottom leadering} to: off

(7) If {Body HTML font size} equals zero[112], and {Bell code} does not equal either bell-I25 or bell-I26, then

(a) do not output the “Precede text with” material

(b) skip to the next bell-I or bell-e (whichever comes first) and resume processing

(8) If {Boxhead HTML font size} equals zero and {Bell code} is bell-I25, then

(a) do not output the “Precede text with” material

(b) skip to the next bell-I or bell-e (whichever comes first) and resume processing

(9) (a) Clear the {stub indent file}.

(b) set {stub indent} to the two-digit number following the bell-I (e.g., with a bell-I04, the two-digit number following the bell-I would be “04”).

(c) subtract eleven from {stub indent}.

(d) if {stub indent} is less than zero, then add ten to {stub indent}.

(e) if

(1) {stub indent limit switch} is “off” and

(2) for the value of {Body HTML font size}, {column width in pixels}_{column} exceeds the value shown in this table:

{Body HTML font size}	{column width in pixels}_{column}
1	145
2	190
3	225
4	255
5	335
6	450
7	680

Then, (A) double the value of {stub indent}; and

(B) if {align}_{column} is “left”, then set {align}_{column}to: justify

(f) for each occurrence of {stub indent}, add the following to {stub indent file}:

(10) If {tracing column switch} is “on” and {Bell code} is not “I50”, then delete “<tr>” from the “Precede text with” material.

(11) Store the bell-I and its argument as {Bell code}.

(12) If

· {tracing column switch} is “on”;

· {Bell code} is not bell-I50; and

· {previous stub locator} is not bell-I50;

then add to {error file}: {TITLE NUMBER} USC{appendix}{SECTION NUMBER}{long subsection} ({text field}) – error – locator-50 missing from line in table with tracing column

(13) Store the value of {Bell code} as {previous stub locator}.

(14) If {column} = {number of columns in table}, then add the following after the “Follow text with” material: </tr>

G. Long table testing and processing

(1) If {tracing column switch} is “off”, then increment {table row} by one.

(2) If {tracing column switch} is “on” and {Bell code} is bell-I50, then increment {table row} by one.

(3) If {column} does not equal {number of columns in table} and either

· {table row} is greater than one; or

· {current bell-h argument} equals one

then output: </tr>

(4) If {table row} is greater than sixty[113], then

(a) output: </table></td></tr></table><table width=“{centering table width}” border=“0” cellpadding=“0” frame=“void” rules=“none”><tr></tr><tr></tr><tr></tr><tr></tr><tr></tr><tr></tr><tr><td align=“center”>{repeated headings file}{I25 repeated headings file}

(b) set {table row} to zero.

H. New column processing

(1) increment {column} by one

(2) if {vertical rule}_{column} is “b”, then

(a) output: <td width=“1” bgcolor=“#000000”><font size=“{Body HTML font size}”> </font></td>

(b) add to the {error file}: {TITLE NUMBER} USC{appendix}{SECTION NUMBER}{long subsection} ({text field}) – attention – verify accuracy of table with bold vertical rule

(c) increment {column} by one

(3) if {vertical rule}_{column} is “p”, then

(a) output: <td width=“{column width in pixels}_{column}”><font size=“{Body HTML font size}” </font></td>

(b) add to the {error file}: {TITLE NUMBER} USC{appendix}{SECTION NUMBER}{long subsection} ({text field}) – attention – verify accuracy of table with parallel vertical rules

(c) increment {column} by one

Bell-C

The bell-C formerly indicated the start of tabular data. A bell-E marked the end of the table. Neither of these codes are used in the U.S. Code – they have been replaced with the bell-c and bell-e. If a bell-C is encountered in the U.S. Code, add to the {error file}:

{TITLE NUMBER}USC{appendix}{SECTION NUMBER}{long subsection} ({text field}) -- Improper function code, bell-C

then add all of the data, up to (and including) the bell-E, to the {error file}.

Bell-F

At the beginning of each U.S. Code title (and at the beginning of each appendix to a title) is a bell-F followed by a 4- or 5-digit argument. The argument of the bell-F is the {format} number[114] and it should be stored for later use.

The argument for a bell-F is four digits long unless the bell is preceded by

«MDNM»

where “«” is a Hex-AE and “»” is a Hex-AF. An example of the five-character F-code can be found at the running head of the U.S. Constitution.

If {format} is not one of the formats defined in the Bell-I section of these specifications, then add the following to the {error file}: {TITLE NUMBER} USC{appendix}{SECTION NUMBER}{long subsection} ({text field}) – invalid format: F{format}

Whenever a bell-F occurs,

(1) set {table switch} to: off

(2) set {footnote switch} and {FOTP row width in pixels} to zero

(3) set {appendix} to a blank

(4) set {bell-Y} to zero

(5) [reserved]

(6) if {subsection anchor} is “on”, then output: </a>

(7) set {subsection anchor} to: off

(8) set {leading} to zero

(9) set {text field} to: CITE

Bell-g

The bell-g comes in two different styles:

· bell-gs, followed by a comma, followed by a one- (or more) digit numeric; and

· bell-g followed by a three-digit numeric.

If the first style is encountered[115], then multiply the numeric by 1.5 and store it as {graphic depth}.

If the second style is encountered, it is immediately followed by a bell-T. Process the data according to the bell-g/bell-T combinations in the following table:

Bell-g argument	Bell-T argument	Instructions	Example at
007	1	(1) If {SECTION NUMBER} is 402, {long subsection} is (b)(1), and {line type} is J, then reset the align attribute in the previous <td> tag from “justify” to “left” (2) If {subsection anchor} is “on”, then output: </a> (2A) Set {circled characters} to a blank. (3) Take each character between (but not including) the T-code and the next bell (4) Before each non-blank character captured in step 3, insert: <nobr>    <b> (4A) In addition to outputting the characters captured in step 3, also append the characters to the end of {circled characters}. (5) After each non-blank character in step 3, insert: </b> <a style=“position: relative; left: -0.7 em; top: 0.1em; font-size: 1.8 em; font-weight: normal”>O</a></nobr> (5A) Add the following to the previous <table> tag: summary=“warning to users of assistive technology: this paragraph includes a special character or characters, {circled characters}-in-a-circle, that may be misinterpreted by your reader as {circled characters} followed by an O.” (6) If {subsection anchor} is “on”, then output: <a onMouseOver=“window.status=’{TITLE NUMBER} USC{appendix}{SECTION NUMBER}{long subsection}’; return true”>	17 U.S.C. § 402(b)(1) 17 U.S.C. § 909(b)(1)
025	3	(1) After the T-code, insert: <i> (2) Process the text between (but not including) the T-code and the next bell, according to the rules for processing caps and small caps. (3) After step 2, insert: </i>	36 U.S.C. prec § 101 (Table Showing Disposition of All Sections of Former Title 36)
077	1	(1) After the T-code, insert: <tt> (2) Output the text between (but not including) the T-code and the next bell (3) After step 2, output: </tt>	28 U.S.C. app. (Fed. R. App. P.) rule 32 note (Committee Notes on Rules 1998 Amendment, ¶ (a)(5), typeface)
401	3	(1) After the T-code, insert: <b> (2) Process the text between (but not including) the T-code and the next bell, according to the rules for processing caps and small caps. (3) After step 2, insert: </b>	2 U.S.C. § 59h(a)
741	4	(1) After the T-code, insert: <i> (2) Process the text between (but not including) the T-code and the next bell, according to the rules for processing caps and small caps. (3) After step 2, insert: </i>	12 U.S.C. § 1813 note (Amendment of Section)
742	3	(1) After the T-code, insert: <i><b> (2) Process the text between (but not including) the T-code and the next bell, according to the rules for processing caps and small caps. (3) After step 2, insert: </b></i>	2 U.S.C. § 60l (catchline)
940	1	Output the text between (but not including) the T-code and the next bell	2 U.S.C. § 59h(a)
940	2	(1) After the T-code, insert: <b> (2) Process the text between (but not including) the T-code and the next bell, according to the rules for processing caps and small caps. (3) After step 2, insert: </b>	28 U.S.C. app. (Fed. Cl. R) rule 77(l)

Bell-G and Bell-T

The bell-T has a one-digit argument (1 to 4)[116]. The bell-G also has a one-digit argument (1 to 8)[117]. When a bell-T is encountered, move the current value of {Typeface} to {old typeface}, move the bell-T argument to {Typeface}, and increment {number of typeface changes} by one. When a bell-G is encountered, move the current value of {Grid} to {old grid}, move the bell-G argument to {Grid}, and increment {number of grid changes} by one.

If there is at least one non-blank character between the current code and the next bell-c, bell-D[118], bell-F, bell-g, bell-G, bell-h[119], bell-I, bell-j[120], bell-K, bell-q, bell-Q, bell-R, bell-S, or bell-T, then

(1) If {number of grid changes} is greater than {number of typeface changes}, then set {old typeface} to the value of {Typeface} and set {number of typeface changes} to the value of {number of grid changes}.

(2) If {number of typeface changes} is greater than {number of grid changes}, then set {old grid} to the value of {Grid} and set {number of grid changes} to the value of {number of typeface changes}.

(3) If {old grid} = 1 and {old typeface} = 2, then output: </b>

(4) If {old grid} = 1 and {old typeface} = 3, then output: </i>

(4A) If {old grid} = 2 and {old typeface} = 1, then output: </sup>

(4B) If {old grid} = 2 and {old typeface} = 2, then output: </sub>

(4C) If {old grid} = 2 and {old typeface} = 3, then output: </sup></i>

(4D) If {old grid} = 2 and {old typeface} = 4, then output: </sub></i>

(4E) If {old grid} = 4 and {old typeface} = 1, then output: </font>

(4F) If {old grid} = 4 and {old typeface} = 2, then output: </b></font>

(4G) If {old grid} = 4 and {old typeface} = 3, then output: </i></font>

(5) If {Grid} = 1 and {Typeface} = 2, then output: <b>

(6) If {Grid} = 1 and {Typeface} = 3, then output: <i>

(7) If {Grid} = 1 and {Typeface} = 4, then use the Caps and Small Caps processing.

(7A) If {Grid} = 2 and {Typeface} = 1,[121] then output: <sup>

(7B) If {Grid} = 2 and {Typeface} = 2,[122] then output: <sub>

(7C) If {Grid} = 2 and {Typeface} = 3, then output: <i><sup>

(7D) If {Grid} = 2 and {Typeface} = 4, then output: <i><sub>

(8) If {Grid} = 3, then

(a) add to {error file}: {TITLE NUMBER} USC{appendix}{SECTION NUMBER}{long subsection} ({text field}) – unidentified grid call – grid {Grid}

(b) set {Grid} to one

(8A) If {Grid} = 4,[123] then output: <font face=“arial, helvetica, geneva”>

(8B) If {Grid} = 4 and {Typeface} = 2,[124] then output: <b>

(8C) If {Grid} = 4 and {Typeface} = 3, then output: <i>

(8D) If {Grid} = 4 and {Typeface} = 4, then

(a) add to {error file}: {TITLE NUMBER} USC{appendix}{SECTION NUMBER}{long subsection} ({text field}) – unidentified grid call – grid {Grid}

(b) set {Grid} to one

(9) If {Grid} = 5, 6, or 7, then use the tables below, substituting the value indicated for each character in the current grid and typeface:

Grid 5
Hex	Typeface 1	Typeface 2	Typeface 3	Typeface 4
00	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character
01	<sup><!-- * --> ·</sup>	<sub><!-- * --> ·</sub>	<sup><i><!-- * --> ·</i></sup>	<sub><i><!-- * --> ·</i></sub>
02 to 05	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character
06	Special processing: If two Hex06 appear together, replace the pair with: <sup>§§ </sup><!-- sections --> If a Hex06 appears not in a pair, replace it with: <sup>§</sup> <!-- section -->	Special processing: If two Hex06 appear together, replace the pair with: <sub>§§ </sub><!-- sections --> If a Hex06 appears not in a pair, replace it with: <sub>§</sub> <!-- section -->	Special processing: If two Hex06 appear together, replace the pair with: <sup><i>§§</i></sup> <!-- sections --> If a Hex06 appears not in a pair, replace it with: <sup><i>§ </i></sup><!-- section -->	Special processing: If two Hex06 appear together, replace the pair with: <sub><i>§ §</i></sub> <!-- sections --> If a Hex06 appears not in a pair, replace it with: <sub><i>§ </i></sub><!-- section -->
07	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character
08	<sup>O</sup>	<sup>O</sup>	<sup>O</sup>	<sup>O</sup>
09	Special processing: (1) Replace with: <sup></sup> (2) Go back to the previous blank space[125],   <td> tag, <p>, <br>, bell-code[126], or EOF[127], and insert after it: <nobr> (3) Go forward to the next blank space[128],   <td> tag, <p>, <br>, bell-code[129], or EOF[130], and insert after it: </nobr> (4) Output: <!-- (5) Again output all of the text between <nobr> and </nobr>, but this time replace the occurrence(s) of with a dash[131] (6) Output: -->	Special processing: (1) Replace with: <sup></sup> (2) Go back to the previous blank space[132],   <td> tag, <p>, <br>, bell-code[133], or EOF[134], and insert after it: <nobr> (3) Go forward to the next blank space[135],   <td> tag, <p>, <br>, bell-code[136], or EOF[137], and insert after it: </nobr> (4) Output: <!-- (5) Again output all of the text between <nobr> and </nobr>, but this time replace the occurrence(s) of with a dash[138] (6) Output: -->	Special processing: (1) Replace with: <sup></sup> (2) Go back to the previous blank space[139],   <td> tag, <p>, <br>, bell-code[140], or EOF[141], and insert after it: <nobr> (3) Go forward to the next blank space[142],   <td> tag, <p>, <br>, bell-code[143], or EOF[144], and insert after it: </nobr> (4) Output: <!-- (5) Again output all of the text between <nobr> and </nobr>, but this time replace the occurrence(s) of with a dash[145] (6) Output: -->	Special processing: (1) Replace with: <sup></sup> (2) Go back to the previous blank space[146],   <td> tag, <p>, <br>, bell-code[147], or EOF[148], and insert after it: <nobr> (3) Go forward to the next blank space[149],   <td> tag, <p>, <br>, bell-code[150], or EOF[151], and insert after it: </nobr> (4) Output: <!-- (5) Again output all of the text between <nobr> and </nobr>, but this time replace the occurrence(s) of with a dash[152] (6) Output: -->
0A	<sup><!-- x -->×</sup>	<sub><!-- x -->×</sub>	<sup><i>><!-- x -->×</i></sup>	<sub><i>><!-- x -->×</i></sub>
0B	<sup>><!-- tilde -->~</sup>	<sub><!-- tilde -->~</sub>	<sup><i><!-- tilde -->~</i></sup>	<sub><i><!-- tilde -->~</i></sub>
0C	Special processing: If two Hex0C appear together, replace the pair with: <sup>¶¶ </sup><!-- paragraphs --> If a Hex0C appears not in a pair, replace it with: <sup>¶</sup> <!-- paragraph -->	Special processing: If two Hex0C appear together, replace the pair with: <sub>¶ ¶</sub><!-- paragraphs --> If a Hex0C appears not in a pair, replace it with: <sub>¶</sub> <!-- paragraph -->	Special processing: If two Hex0C appear together, replace the pair with: <sup><i>¶¶</i></sup><!-- paragraphs --> If a Hex0C appears not in a pair, replace it with: <sup><i>¶ </i></sup><!-- paragraph -->	Special processing: If two Hex0C appear together, replace the pair with: <sub><i>¶ ¶</i></sup> <!-- paragraphs --> If a Hex0C appears not in a pair, replace it with: <sub><i>¶ </i></sub><!-- paragraph -->
0D to 0F	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character
10	<sup><!-- divided by -->÷</sup>	<sub><!-- divided by -->÷</sub>	<sup><i><!-- divided by -->÷</i> </sup>	<sub><i><!-- divided by -->÷</i> </sub>
11	<sup><nobr><!-- is much less than --><<a style="position: relative; left: -0.2 em; top: -0.1 em; font-size: 0.8 em; font-weight: normal"><</a></nobr></sup>	<sub><nobr><!-- is much less than --><<a style="position: relative; left: -0.2 em; top: -0.1 em; font-size: 0.8 em; font-weight: normal"><</a></nobr></sub>	<sup><i><nobr><!-- is much less than --><<a style="position: relative; left: -0.2 em; top: -0.1 em; font-size: 0.8 em; font-weight: normal"><</a></nobr></i></sup>	<sub><i><nobr><!-- is much less than --><<a style="position: relative; left: -0.2 em; top: -0.1 em; font-size: 0.8 em; font-weight: normal"><</a></nobr></i></sub>
12	<sup><nobr><!-- is much greater than -->><a style="position: relative; left: -0.2 em; top: -0.1 em; font-size: 0.8 em; font-weight: normal">></a></nobr></sup>	<sub><nobr><!-- is much greater than -->><a style="position: relative; left: -0.2 em; top: -0.1 em; font-size: 0.8 em; font-weight: normal">></a></nobr></sub>	<sup><i><nobr><!-- is much greater than -->><a style="position: relative; left: -0.2 em; top: -0.1 em; font-size: 0.8 em; font-weight: normal">></a></nobr></i></sup>	<sub><i><nobr><!-- is much greater than -->><a style="position: relative; left: -0.2 em; top: -0.1 em; font-size: 0.8 em; font-weight: normal">></a></nobr></i></sub>
13	Special processing: (1) Output: <sup><nobr><!-- is nearly equal to -->~<a style="position: relative; left: -0.5 em; top: -0.2 em; font-size: 1.0 em; font-weight: normal">~</a></nobr></sup> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes a is-nearly-equal-to sign that may be misinterpreted by your reader as two tildes.”	Special processing: (1) Output: <sub><nobr><!-- is nearly equal to -->~<a style="position: relative; left: -0.5 em; top: -0.2 em; font-size: 1.0 em; font-weight: normal">~</a></nobr></sub> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes a is-nearly-equal-to sign that may be misinterpreted by your reader as two tildes.”	Special processing: (1) Output: <sup><i><nobr><!-- is nearly equal to -->~<a style="position: relative; left: -0.5 em; top: -0.2 em; font-size: 1.0 em; font-weight: normal">~</a> </nobr></i></sup> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes a is-nearly-equal-to sign that may be misinterpreted by your reader as two tildes.”	Special processing: (1) Output: <sub><i><nobr><!-- is nearly equal to -->~<a style="position: relative; left: -0.5 em; top: -0.2 em; font-size: 1.0 em; font-weight: normal">~</a> </nobr></i></sub> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes a is-nearly-equal-to sign that may be misinterpreted by your reader as two tildes.”
14	Special processing: (1) Output: <sup><nobr><!-- is approximately equal to -->=<a style="position: relative; left: -0.5 em; top: -0.3 em; font-size: 1.0 em; font-weight: normal">~</a></nobr></sup> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes a is-approximately-equal-to sign that may be misinterpreted by your reader as an equal sign followed by a tilde.”	Special processing: (1) Output: <sub><nobr><!-- is approximately equal to -->=<a style="position: relative; left: -0.5 em; top: -0.3 em; font-size: 1.0 em; font-weight: normal">~</a></nobr></sub> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes a is-approximately-equal-to sign that may be misinterpreted by your reader as an equal sign followed by a tilde.”	Special processing: (1) Output: <sup><i><nobr><!-- is approximately equal to -->=<a style="position: relative; left: -0.5 em; top: -0.3 em; font-size: 1.0 em; font-weight: normal">~</a></nobr></i></sup> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes a is-approximately-equal-to sign that may be misinterpreted by your reader as an equal sign followed by a tilde.”	Special processing: (1) Output: <sup><i><nobr><!-- is approximately equal to -->=<a style="position: relative; left: -0.5 em; top: -0.3 em; font-size: 1.0 em; font-weight: normal">~</a></nobr></i></sup> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes a is-approximately-equal-to sign that may be misinterpreted by your reader as an equal sign followed by a tilde.”
15	Special processing: (1) Output: <sup><nobr><!-- is not less than --><<a style="position: relative; left: -0.4 em; top: -0.2 em; font-size: 1.0 em; font-weight: normal">\|</a></nobr></sup> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes a is-not-less-than sign that may be misinterpreted by your reader as a less-than sign followed by a vertical pipe.”	Special processing: (1) Output: <sub><nobr><!-- is not less than --><<a style="position: relative; left: -0.4 em; top: -0.2 em; font-size: 1.0 em; font-weight: normal">\|</a></nobr></sub> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes a is-not-less-than sign that may be misinterpreted by your reader as a less-than sign followed by a vertical pipe.”	Special processing: (1) Output: <sup><i><nobr><!-- is not less than --><<a style="position: relative; left: -0.4 em; top: -0.2 em; font-size: 1.0 em; font-weight: normal">\|</a></nobr></i></sup> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes a is-not-less-than sign that may be misinterpreted by your reader as a less-than sign followed by a vertical pipe.”	Special processing: (1) Output: <sub><i><nobr><!-- is not less than --><<a style="position: relative; left: -0.4 em; top: -0.2 em; font-size: 1.0 em; font-weight: normal">\|</a></nobr></i></sub> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes a is-not-less-than sign that may be misinterpreted by your reader as a less-than sign followed by a vertical pipe.”
16	Special processing: (1) Output: <sup><nobr><!-- is not greater than -->&#62<a style="position: relative; left: -0.4 em; top: -0.2 em; font-size: 1.0 em; font-weight: normal" >\|</a></nobr></sup> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes a is-not-greater-than sign that may be misinterpreted by your reader as a greater-than sign followed by a vertical pipe.”	Special processing: (1) Output: <sub><nobr><!-- is not greater than -->&#62<a style="position: relative; left: -0.4 em; top: -0.2 em; font-size: 1.0 em; font-weight: normal" >\|</a></nobr></sub> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes a is-not-greater-than sign that may be misinterpreted by your reader as a greater-than sign followed by a vertical pipe.”	Special processing: (1) Output: <sup><i><nobr><!-- is not greater than -->&#62<a style="position: relative; left: -0.4 em; top: -0.2 em; font-size: 1.0 em; font-weight: normal" >\|</a></nobr></i></sup> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes a is-not-greater-than sign that may be misinterpreted by your reader as a greater-than sign followed by a vertical pipe.”	Special processing: (1) Output: <sub><i><nobr><!-- is not greater than -->&#62<a style="position: relative; left: -0.4 em; top: -0.2 em; font-size: 1.0 em; font-weight: normal" >\|</a></nobr></i></sub> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes a is-not-greater-than sign that may be misinterpreted by your reader as a greater-than sign followed by a vertical pipe.”
17	Special processing: (1) Output: <sup><nobr><!-- minus or plus -->+<a style="position: relative; left: -0.5 em; top: -0.5 em; font-size: 1.0 em; font-weight: normal"></a></nobr></sup> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes a minus-or-plus sign that may be misinterpreted by your reader as a minus-sign followed by a plus-sign.”	Special processing: (1) Output: <sub><nobr><!-- minus or plus -->+<a style="position: relative; left: -0.5 em; top: -0.5 em; font-size: 1.0 em; font-weight: normal"></a></nobr></sub> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes a minus-or-plus sign that may be misinterpreted by your reader as a minus-sign followed by a plus-sign.”	Special processing: (1) Output: <sup><i><nobr><!-- minus or plus -->+<a style="position: relative; left: -0.5 em; top: -0.5 em; font-size: 1.0 em; font-weight: normal"></a></nobr></i></sup> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes a minus-or-plus sign that may be misinterpreted by your reader as a minus-sign followed by a plus-sign.”	Special processing: (1) Output: <sub><i><nobr><!-- minus or plus -->+<a style="position: relative; left: -0.5 em; top: -0.5 em; font-size: 1.0 em; font-weight: normal"></a></nobr></i></sub> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes a minus-or-plus sign that may be misinterpreted by your reader as a minus-sign followed by a plus-sign.”
18 to 1A	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character
1B	<sup><!-- plus or minus -->±</sup>	<sub><!-- plus or minus -->±</sub>	<sup><i><!-- plus or minus -->±</i> </sup>	<sub><i><!-- plus or minus -->±</i></sub>
1C to 1D	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character
1E	<sup><!-- dagger -->†</sup>	<sub><!-- dagger -->†</sub>	<sup><i><!-- dagger -->†</i></sup>	<sub><i><!-- dagger -->†</i></sub>
1F	<sup><!-- C in a circle -->©</sup>	<sup><!-- C in a circle -->©</sup>	<sup><i><!-- C in a circle -->© </i> </sup>	<sup><i><!-- C in a circle -->©</i> </sup>
20 [153]
21	Special processing: (1) Output: <sup><nobr><!-- is identical with -->=<a style="position: relative; left: -0.5 em; top: -0.3 em; font-size: 1.0 em; font-weight: normal"></a></nobr></sup> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes an is-identical-with sign that may be misinterpreted by your reader as an equal-sign followed by a dash.”	Special processing: (1) Output: <sub><nobr><!-- is identical with --=<a style="position: relative; left: -0.5 em; top: -0.3 em; font-size: 1.0 em; font-weight: normal"></a></nobr></sub> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes an is-identical-with sign that may be misinterpreted by your reader as an equal-sign followed by a dash.”	Special processing: (1) Output: <sup><i><nobr><!-- is identical with -->=<a style="position: relative; left: -0.5 em; top: -0.3 em; font-size: 1.0 em; font-weight: normal"></a></nobr></i></sup> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes an is-identical-with sign that may be misinterpreted by your reader as an equal-sign followed by a dash.”	Special processing: (1) Output: <sub><i><nobr><!-- is identical with --> =<a style="position: relative; left: -0.5 em; top: -0.3 em; font-size: 1.0 em; font-weight: normal"></a></nobr></i></sub> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes an is-identical-with sign that may be misinterpreted by your reader as an equal-sign followed by a dash.”
22	<sup><!-- double prime -->''</sup>	<sub><!-- double prime -->''</sub>	<sup><i><!-- double prime -->'' </i></sup>	<sub><i><!-- double prime -->'' </i></sub>
23	<sup>#</sup>	<sub>#</sub>	<sup><i>#</i></sup>	<sub><i>#</i></sub>
24	<sup>$</sup>	<sub>$</sub>	<sup><i>$</i></sup>	<sub><i>$</i></sub>
25	<sup><!-- is not equal to -->≠</sup>	<sub><!-- is not equal to -->≠</sub>	<sup><i><!-- is not equal to -->≠ </i></sup>	<sub><i><!-- is not equal to -->≠ </i></sub>
26	<sup>&</sup>	<sub>&</sub>	<sup><i>&</i></sup>	<sub><i>&</i></sub>
27	Special processing: (1) Output: <sup><nobr><!-- is not identical with -->=<a style="position: relative; left: -0.4 em; top: -0.2 em; font-size: 1.0 em; font-weight: normal">\|</a></nobr></sup> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes an is-not-identical-with sign that may be misinterpreted by your reader as an equal-sign followed by a vertical pipe.”	Special processing: (1) Output: <sub<nobr><!-- is not identical with -->=<a style="position: relative; left: -0.4 em; top: -0.2 em; font-size: 1.0 em; font-weight: normal">\|</a></nobr></sub> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes an is-not-identical-with sign that may be misinterpreted by your reader as an equal-sign followed by a vertical pipe.”	Special processing: (1) Output: <sup><i><nobr><!-- is not identical with -->=<a style="position: relative; left: -0.4 em; top: -0.2 em; font-size: 1.0 em; font-weight: normal">\|</a></nobr></i></sup> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes an is-not-identical-with sign that may be misinterpreted by your reader as an equal-sign followed by a vertical pipe.”	Special processing: (1) Output: <sub><i><nobr><!-- is not identical with -->=<a style="position: relative; left: -0.4 em; top: -0.2 em; font-size: 1.0 em; font-weight: normal">\|</a></nobr></i></sub> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes an is-not-identical-with sign that may be misinterpreted by your reader as an equal-sign followed by a vertical pipe.”
28	<sup>(</sup>	<sub>(</sub>	<sup><i>(</i></sup>	<sub><i>(</i></sub>
29	<sup>)</sup>	<sub>)</sub>	<sup><i>)</i></sup>	<sub><i>)</i></sub>
2A	<sup>*</sup>	<sub>*</sub>	<sup><i>*</i></sup>	<sub><i>*</i></sub>
2B	<sup>+</sup>	<sub>+</sub>	<sup><i>+</i></sup>	<sub><i>+</i></sub>
2C	<sup>,</sup>	<sub>,</sub>	<sup><i>,</i></sup>	<sub><i>,</i></sub>
2D	<sup>-</sup>	<sub>-</sub>	<sup><i>-</i></sup>	<sub><i>-</i></sub>
2E [154]	<sup>.</sup>	<sub>.</sub>	<sup><i>.</i></sup>	<sub><i>.</i></sub>
2F	<sup>/</sup>	<sub>/</sub>	<sup><i>/</i></sup>	<sub><i>/</i></sub>
30 [155]	<sup>0</sup>	<sub>0</sub>	<sup><i>0</i></sup>	<sub><i>0</i></sub>
31 [156]	<sup>1</sup>	<sub>1</sub>	<sup><i>1</i></sup>	<sub><i>1</i></sub>
32 [157]	<sup>2</sup>	<sub>2</sub>	<sup><i>2</i></sup>	<sub><i>2</i></sub>
33 [158]	<sup>3</sup>	<sub>3</sub>	<sup><i>3</i></sup>	<sub><i>3</i></sub>
34 [159]	<sup>4</sup>	<sub>4</sub>	<sup><i>4</i></sup>	<sub><i>4</i></sub>
35 [160]	<sup>5</sup>	<sub>5</sub>	<sup><i>5</i></sup>	<sub><i>5</i></sub>
36 [161]	<sup>6</sup>	<sub>6</sub>	<sup><i>6</i></sup>	<sub><i>6</i></sub>
37 [162]	<sup>7</sup>	<sub>7</sub>	<sup><i>7</i></sup>	<sub><i>7</i></sub>
38 [163]	<sup>8</sup>	<sub>8</sub>	<sup><i>8</i></sup>	<sub><i>8</i></sub>
39 [164]	<sup>9</sup>	<sub>9</sub>	<sup><i>9</i></sup>	<sub><i>9</i></sub>
3A	<sup><!-- is less than or equal to -->≤</sup>	<sub><!-- is less than or equal to -->≤</sub>	<sup><i><!-- is less than or equal to -->≤</i></sup>	<sub><i><!-- is less than or equal to -->≤</i></sub>
3B	<sup><!-- is greater than or equal to -->≥</sup>	<sub><!-- is greater than or equal to -->≥</sub>	<sup><i><!-- is greater than or equal to -->≥</i></sup>	<sub><i><!-- is greater than or equal to -->≥</i></sub>
3C	<sup><!-- is less than --><</sup>	<sub><!-- is less than --><</sub>	<sup><i><!-- is less than --><</i> </sup>	<sub><i><!-- is less than --><</i></sub>
3D	<sup>=</sup>	<sub>=</sub>	<sup><i>=</i></sup>	<sub><i>=</i></sub>
3E	<sup><!-- is greater than -->></sup>	<sub><!-- is greater than -->></sub>	<sup><i><!-- is greater than -->></i> </sup>	<sub><i><!-- is greater than -->></i></sub>
3F [165]	<sup>¦ ¦</sup>	<sub>¦ ¦</sub>	<sup><i>¦ ¦ </i></sup>	<sub><i>¦ ¦</i></sub>
40	<sup>@</sup>	<sub>@</sub>	<sup><i>@</i> </sup>	<sub><i>@</i></sub>
41	<sup>A</sup>	<sub>A</sub>	<sup><i>A</i></sup>	<sub><i>A</i></sub>
42	<sup>B</sup>	<sub>B</sub>	<sup><i>B</i></sup>	<sub><i>B</i></sub>
43 [166]	<sup>C</sup>	<sub>C</sub>	<sup><i>C</i></sup>	<sub><i>C</i></sub>
44 [167]	<sup>D</sup>	<sub>D</sub>	<sup><i>D</i></sup>	<sub><i>D</i></sub>
45	<sup>E</sup>	<sub>E</sub>	<sup><i>E</i></sup>	<sub><i>E</i></sub>
46	<sup>F</sup>	<sub>F</sub>	<sup><i>F</i></sup>	<sub><i>F</i></sub>
47	<sup>G</sup>	<sub>G</sub>	<sup><i>G</i></sup>	<sub><i>G</i></sub>
48	<sup>H</sup>	<sub>H</sub>	<sup><i>H</i></sup>	<sub><i>H</i></sub>
49	<sup>I</sup>	<sub>I</sub>	<sup><i>I</i></sup>	<sub><i>I</i></sub>
4A	<sup>J</sup>	<sub>J</sub>	<sup><i>J</i></sup>	<sub><i>J</i></sub>
4B	<sup>K</sup>	<sub>K</sub>	<sup><i>K</i></sup>	<sub><i>K</i></sub>
4C [168]	<sup>L</sup>	<sub>L</sub>	<sup><i>L</i></sup>	<sub><i>L</i></sub>
4D [169]	<sup>M</sup>	<sub>M</sub>	<sup><i>M</i> </sup>	<sub><i>M</i></sub>
4E	<sup>N</sup>	<sub>N</sub>	<sup><i>N</i></sup>	<sub><i>N</i></sub>
4F [170]	<sup>O</sup>	<sub>O</sub>	<sup><i>O</i></sup>	<sub><i>O</i></sub>
50	<sup>P</sup>	<sub>P</sub>	<sup><i>P</i></sup>	<sub><i>P</i></sub>
51	<sup>Q</sup>	<sub>Q</sub>	<sup><i>Q</i></sup>	<sub><i>Q</i></sub>
52	<sup>R</sup>	<sub>R</sub>	<sup><i>R</i></sup>	<sub><i>R</i></sub>
53 [171]	<sup>S</sup>	<sub>S</sub>	<sup><i>S</i></sup>	<sub><i>S</i></sub>
54 [172]	<sup>T</sup>	<sub>T</sub>	<sup><i>T</i></sup>	<sub><i>T</i></sub>
55	<sup>U</sup>	<sub>U</sub>	<sup><i>U</i></sup>	<sub><i>U</i></sub>
56	<sup>V</sup>	<sub>V</sub>	<sup><i>V</i></sup>	<sub><i>V</i></sub>
57	<sup>W</sup>	<sub>W</sub>	<sup><i>W</i> </sup>	<sub><i>W</i></sub>
58	<sup>X</sup>	<sub>X</sub>	<sup><i>X</i></sup>	<sub><i>X</i></sub>
59	<sup>Y</sup>	<sub>Y</sub>	<sup><i>Y</i></sup>	<sub><i>Y</i></sub>
5A	<sup>Z</sup>	<sub>Z</sub>	<sup><i>Z</i></sup>	<sub><i>Z</i></sub>
5B	<sup>[</sup>	<sub>[</sub>	<sup><i> [</i></sup>	<sub><i> [</i></sub>
5C	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character
5D	<sup>]</sup>	<sub>]</sub>	<sup><i>]</i></sup>	<sub><i>]</i></sub>
5E [173]	Special processing: (1) Store all of the text between the Hex 5E and the previous blank space[174],   <td> tag, <p>, <br>, bell-code[175], or EOF[176], as {hold-1} - - - (2) Store all of the text between Hex 5E and the next blank space[177],   <td> tag, <p>, <br>, bell-code[178], or EOF[179], as {hold-2} - - - (3) Output: <sup>-</sup>{hold-2} <!-- {hold-1}-{hold-2} -->	Special processing: (1) Store all of the text between the Hex 5E and the previous blank space[180],   <td> tag, <p>, <br>, bell-code[181], or EOF[182], as {hold-1} - - - (2) Store all of the text between Hex 5E and the next blank space[183],   <td> tag, <p>, <br>, bell-code[184], or EOF[185], as {hold-2} - - - (3) Output: <sub>-</sub>{hold-2} <!-- {hold-1}-{hold-2} -->	Special processing: (1) Store all of the text between the Hex 5E and the previous blank space[186],   <td> tag, <p>, <br>, bell-code[187], or EOF[188], as {hold-1} - - - (2) Store all of the text between Hex 5E and the next blank space[189],   <td> tag, <p>, <br>, bell-code[190], or EOF[191], as {hold-2} - - - (3) Output: <sup><i>-</i></sup>{hold-2} <!-- {hold-1}-{hold-2} -->	Special processing: (1) Store all of the text between the Hex 5E and the previous blank space[192],   <td> tag, <p>, <br>, bell-code[193], or EOF[194], as {hold-1} - - - (2) Store all of the text between Hex 5E and the next blank space[195],   <td> tag, <p>, <br>, or bell-code[196], or EOF[197], as {hold-2} - - - (3) Output: <sub><i>-</i></sub>{hold-2} <!-- {hold-1}-{hold-2} -->
5F	Special processing: (1) Store all of the text between the Hex 5F and the previous blank space[198],   <td> tag, <p>, <br>, bell-code[199], or EOF[200], as {hold-1} - - - (2) Store all of the text between Hex 5E and the next blank space[201],   <td> tag, <p>, <br>, bell-code[202], or EOF[203], as {hold-2} - - - (3) Output: <sup></sup>{hold-2} <!-- {hold-1}-{hold-2} -->	Special processing: (1) Store all of the text between the Hex 5F and the previous blank space[204],   <td> tag, <p>, <br>, bell-code[205], or EOF[206], as {hold-1} - - - (2) Store all of the text between Hex 5E and the next blank space[207],   <td> tag, <p>, <br>, bell-code[208], or EOF[209], as {hold-2} - - - (3) Output: <sub></sub>{hold-2} <!-- {hold-1}-{hold-2} -->	Special processing: (1) Store all of the text between the Hex 5F and the previous blank space[210],   <td> tag, <p>, <br>, bell-code[211], or EOF[212], as {hold-1} - - - (2) Store all of the text between Hex 5E and the next blank space[213],   <td> tag, <p>, <br>, bell-code[214], or EOF[215], as {hold-2} - - - (3) Output: <sup><i></i></sup>{hold-2} <!-- {hold-1}-{hold-2} -->	Special processing: (1) Store all of the text between the Hex 5F and the previous blank space[216],   <td> tag, <p>, <br>, bell-code[217], or EOF[218], as {hold-1} - - - (2) Store all of the text between Hex 5E and the next blank space[219],   <td> tag, <p>, <br>, or bell-code[220], or EOF[221], as {hold-2} - - - (3) Output: <sub><i></i></sub>{hold-2} <!-- {hold-1}-{hold-2} -->
60	Special processing: (1) Output: <sup><nobr><!-- is less than or greater than -->><a style="position: relative; left: -0.5 em; top: -0.3 em; font-size: 1.0 em; font-weight: normal"><</a></nobr></sup> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes an is-less-than-or-greater-than sign that may be misinterpreted by your reader as a less-than sign followed by a greater-than sign.”	Special processing: (1) Output: <sub><nobr><!-- is less than or greater than -->><a style="position: relative; left: -0.5 em; top: -0.3 em; font-size: 1.0 em; font-weight: normal"><</a></nobr></sub> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes an is-less-than-or-greater-than sign that may be misinterpreted by your reader as a less-than sign followed by a greater-than sign.”	Special processing: (1) Output: <sup><i><nobr><!-- is less than or greater than -->><a style="position: relative; left: -0.5 em; top: -0.3 em; font-size: 1.0 em; font-weight: normal"><</a></nobr></i></sup> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes an is-less-than-or-greater-than sign that may be misinterpreted by your reader as a less-than sign followed by a greater-than sign.”	Special processing: (1) Output: <sub><i><nobr><!-- is less than or greater than -->><a style="position: relative; left: -0.5 em; top: -0.3 em; font-size: 1.0 em; font-weight: normal"><</a></nobr></i></sub> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes an is-less-than-or-greater-than sign that may be misinterpreted by your reader as a less-than sign followed by a greater-than sign.”
61	<sup>a</sup>	<sub>a</sub>	<sup><i>a</i></sup>	<sub><i>a</i></sub>
62	<sup>b</sup>	<sub>b</sub>	<sup><i>b</i></sup>	<sub><i>b</i></sub>
63	<sup>c</sup>	<sub>c</sub>	<sup><i>c</i></sup>	<sub><i>c</i></sub>
64	<sup>d</sup>	<sub>d</sub>	<sup><i>d</i></sup>	<sub><i>d</i></sub>
65	<sup>e</sup>	<sub>e</sub>	<sup><i>e</i></sup>	<sub><i>e</i></sub>
66	<sup>f</sup>	<sub>f</sub>	<sup><i>f</i></sup>	<sub><i>f</i></sub>
67	<sup>g</sup>	<sub>g</sub>	<sup><i>g</i></sup>	<sub><i>g</i></sub>
68	<sup>h</sup>	<sub>h</sub>	<sup><i>h</i></sup>	<sub><i>h</i></sub>
69	<sup>i</sup>	<sub>i</sub>	<sup><i>i</i></sup>	<sub><i>i</i></sub>
6A	<sup>j</sup>	<sub>j</sub>	<sup><i>j</i></sup>	<sub><i>j</i></sub>
6B	<sup>k</sup>	<sub>k</sub>	<sup><i>k</i></sup>	<sub><i>k</i></sub>
6C	<sup>l</sup>	<sub>l</sub>	<sup><i>l</i></sup>	<sub><i>l</i></sub>
6D	<sup>m</sup>	<sub>m</sub>	<sup><i>m</i></sup>	<sub><i>m</i></sub>
6E [222]	<sup>n</sup>	<sub>n</sub>	<sup><i>n</i></sup>	<sub><i>n</i></sub>
6F	<sup>o</sup>	<sub>o</sub>	<sup><i>o</i></sup>	<sub><i>o</i></sub>
70	<sup>p</sup>	<sub>p</sub>	<sup><i>p</i></sup>	<sub><i>p</i></sub>
71	<sup>q</sup>	<sub>q</sub>	<sup><i>q</i></sup>	<sub><i>q</i></sub>
72	<sup>r</sup>	<sub>r</sub>	<sup><i>r</i></sup>	<sub><i>r</i></sub>
73	<sup>s</sup>	<sub>s</sub>	<sup><i>s</i></sup>	<sub><i>s</i></sub>
74 [223]	<sup>t</sup>	<sub>t</sub>	<sup><i>t</i></sup>	<sub><i>t</i></sub>
75	<sup>u</sup>	<sub>u</sub>	<sup><i>u</i></sup>	<sub><i>u</i></sub>
76	<sup>v</sup>	<sub>v</sub>	<sup><i>v</i></sup>	<sub><i>v</i></sub>
77	<sup>w</sup>	<sub>w</sub>	<sup><i>w</i></sup>	<sub><i>w</i></sub>
78 [224]	<sup>x</sup>	<sub>x</sub>	<sup><i>x</i></sup>	<sub><i>x</i></sub>
79	<sup>y</sup>	<sub>y</sub>	<sup><i>y</i></sup>	<sub><i>y</i></sub>
7A	<sup>z</sup>	<sub>z</sub>	<sup><i>z</i></sup>	<sub><i>z</i></sub>
7B	<sup><!-- { -->{</sup>	<sub><!-- { -->{</sub>	<sup><i><!-- { -->{</i></sup>	<sub><i><!-- { -->{</i></sub>
7C [225]	<sup>¦</sup>	<sub>¦</sub>	<sup><i>¦</i> </sup>	<sub><i>¦</i> </sub>
7D	<sup><!-- } -->}</sup>	<sub><!-- } -->}</sub>	<sup><i><!-- } -->}</i></sup>	<sub><i><!-- } -->}</i></sub>
7E	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character
7F	<sup><!-- R in a circle -->®</sup>	<sup><!-- R in a circle -->®</sup>	<sup><i><!-- R in a circle -->®</i> </sup>	<sup><i><!-- R in a circle -->®</i> </sup>
80 to A9	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character
AA	<sup><!-- is greater than or equal to -->≥</sup>	<sub><!-- is greater than or equal to -->≥</sub>	<sup><i><!-- is greater than or equal to -->≥</i></sup>	<sub><i><!-- is greater than or equal to -->≥</i></sub>
AB [226]	<sup><!-- degrees -->°</sup>	<sub><!-- degrees -->°</sub>	<sup><i><!-- degrees -->°</i></sup>	<sub><i><!-- degrees -->°</i></sub>
AC	<sup><!-- prime -->'</sup>	<sub><!-- prime -->'</sub>	<sup><i><!-- prime -->'</i></sup>	<sub><i><!-- prime -->'</i></sub>
AD	/	/	<i>/</i>	<i>/</i>
AE	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character
AF [227]	<sup><!-- C in a circle -->©</sup>	<sup><!-- C in a circle -->©</sup>	<sup><i><!-- C in a circle -->©</i> </sup>	<sup><i><!-- C in a circle -->©</i> </sup>
B0 to B9	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character
BA	Special processing: (1) Output: <sup><nobr><!-- is greater than or less than --><<a style="position: relative; left: -0.5 em; top: -0.3 em; font-size: 1.0 em; font-weight: normal">></a></nobr></sup> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes an is-greater-than-or-less-than sign that may be misinterpreted by your reader as a greater-than sign followed by a less-than sign.”	Special processing: (1) Output: <sub><nobr><!-- is greater than or less than --><<a style="position: relative; left: -0.5 em; top: -0.3 em; font-size: 1.0 em; font-weight: normal">></a></nobr></sub> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes an is-greater-than-or-less-than sign that may be misinterpreted by your reader as a greater-than sign followed by a less-than sign.”	Special processing: (1) Output: <sup><Ii<nobr><!-- is greater than or less than --><<a style="position: relative; left: -0.5 em; top: -0.3 em; font-size: 1.0 em; font-weight: normal">></a></nobr></i></sup> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes an is-greater-than-or-less-than sign that may be misinterpreted by your reader as a greater-than sign followed by a less-than sign.”	Special processing: (1) Output: <sub><i<nobr><!-- is greater than or less than --><<a style="position: relative; left: -0.5 em; top: -0.3 em; font-size: 1.0 em; font-weight: normal">></a></nobr></i></sub> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes an is-greater-than-or-less-than sign that may be misinterpreted by your reader as a greater-than sign followed by a less-than sign.”
BB	<sup><!-- radical -->√ </sup>	<sub><!-- radical -->√</sub>	<sup><i><!-- radical -->√</i></sup>	<sub><i><!-- radical -->√</i></sub>
BC	[STAR]	[STAR]	<i>[STAR]</i>	<i>[STAR]</i>
BD	<sup><!-- double dagger -->‡</sup>	<sub><!-- radical -->‡</sub>	<sup><i><!-- radical -->‡</i></sup>	<sub><i><!-- radical -->‡</i></sub>
BE	<sup><!-- is less than or equal to -->≤</sup>	<sub><!-- is less than or equal to -->𕫤</sub>	<sup><i><!-- is less than or equal to -->≤</i></sup>	<sub><i><!-- is less than or equal to -->≤</i></sub>
BF	<sup><!-- ( ) --></sup>	<sub><!-- ( ) --></sub>	<sup><i><!-- ( ) --></i></sup>	<sub><i><!-- ( ) --></i></sub>
C0 to C3	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character
C4	Special processing: (1) Output: <sup><nobr><!-- in perspecitve to -->~<a style="position: relative; left: -0.5 em; top: 0.2 em; font-size: 1.0 em; font-weight: normal"></a></nobr></sup> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes an in-perspective-to sign that may be misinterpreted by your reader as a tilde followed by a dash.”	Special processing: (1) Output: <sub><nobr><!-- in perspecitve to -->~<a style="position: relative; left: -0.5 em; top: 0.2 em; font-size: 1.0 em; font-weight: normal"></a></nobr></sub> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes an in-perspective-to sign that may be misinterpreted by your reader as a tilde followed by a dash.”	Special processing: (1) Output: <sup><i><nobr><!-- in perspecitve to -->~<a style="position: relative; left: -0.5 em; top: 0.2 em; font-size: 1.0 em; font-weight: normal"></a></nobr></i></sup> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes an in-perspective-to sign that may be misinterpreted by your reader as a tilde followed by a dash.”	Special processing: (1) Output: <sub><i><nobr><!-- in perspecitve to -->~<a style="position: relative; left: -0.5 em; top: 0.2 em; font-size: 1.0 em; font-weight: normal"></a></nobr></i></sub> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes an in-perspective-to sign that may be misinterpreted by your reader as a tilde followed by a dash.”
C5	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character
C6	<b>/</b>	<b>/</b>	<i><b>/</b></i>	<i><b>/</b></i>
C7 to C8	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character
C9	<sup><!-- infinity -->∞</sup>	<sub><!-- infinity -->∞</sub>	<sup><i><!-- infinity -->∞</i></sup>	<sub><i><!-- infinity -->∞</i></sub>
CA	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character
CB	<sup><!-- is perpendicular to -->⊥</sup>	<sub><!-- is perpendicular to -->⊥</sub>	<sup><i><!-- is perpendicular to -->⊥</i></sup>	<sub><i><!-- is perpendicular to -->⊥</i></sub>
CC to FF	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character

Grid 6
Hex	Typeface 1	Typeface 2	Typeface 3	Typeface 4
00	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character
01	<!-- * -->·	<b><!-- * -->·</b>	<sup><!-- * -->·</sup>	<sub><!-- * -->· </sub>
02 to 05	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character
06	Special processing: If two Hex06 appear together, replace the pair with: <sup>§§ </sup><!-- sections --> If a Hex06 appears not in a pair, replace it with: <sup>§</sup> <!-- section -->	Special processing: If two Hex06 appear together, replace the pair with: <b>§§ </b><!-- sections --> If a Hex06 appears not in a pair, replace it with: <b>§</b> <!-- section -->	Special processing: If two Hex06 appear together, replace the pair with: <sup>§§</sup> <!-- sections --> If a Hex06 appears not in a pair, replace it with: <sup>§ </sup><!-- section -->	Special processing: If two Hex06 appear together, replace the pair with: <sub>§ §</sub> <!-- sections --> If a Hex06 appears not in a pair, replace it with: <sub>§ </sub><!-- section -->
07	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character
08	O	<b>O</b>	<sup>O</sup>	<sup>O</sup>
09	Special processing: (1) Replace with: (2) Go back to the previous blank space[228],   <td> tag, <p>, <br>, bell-code[229], or EOF[230], and insert after it: <nobr> (3) Go forward to the next blank space[231],   <td> tag, <p>, <br>, bell-code[232], or EOF[233], and insert after it: </nobr> (4) Output: <!-- (5) Again output all of the text between <nobr> and </nobr>, but this time replace the occurrence(s) of with a dash[234] (6) Output: -->	Special processing: (1) Replace with: <b></b> (2) Go back to the previous blank space[235],   <td> tag, <p>, <br>, bell-code[236], or EOF[237], and insert after it: <nobr> (3) Go forward to the next blank space[238],   <td> tag, <p>, <br>, bell-code[239], or EOF[240], and insert after it: </nobr> (4) Output: <!-- (5) Again output all of the text between <nobr> and </nobr>, but this time replace the occurrence(s) of with a dash[241] (6) Output: -->	Special processing: (1) Replace with: <sup></sup> (2) Go back to the previous blank space[242],   <td> tag, <p>, <br>, bell-code[243], or EOF[244], and insert after it: <nobr> (3) Go forward to the next blank space[245],   <td> tag, <p>, <br>, bell-code[246], or EOF[247], and insert after it: </nobr> (4) Output: <!-- (5) Again output all of the text between <nobr> and </nobr>, but this time replace the occurrence(s) of with a dash[248] (6) Output: -->	Special processing: (1) Replace with: <sup></sup> (2) Go back to the previous blank space[249],   <td> tag, <p>, <br>, or bell-code[250], or EOF[251], and insert after it: <nobr> (3) Go forward to the next blank space[252],   <td> tag, <p>, <br>, bell-code[253], or EOF[254], and insert after it: </nobr> (4) Output: <!-- (5) Again output all of the text between <nobr> and </nobr>, but this time replace the occurrence(s) of with a dash[255] (6) Output: -->
0A [256]	<!-- x -->×	<b><!-- x -->×</b>	<sup><!-- x -->×</sup>	<sub><!-- x -->×</sub>
0B	<!-- tilde -->~	<b><!-- tilde -->~</b>	<sup><!-- tilde -->~</sup>	<sub><!-- tilde -->~</sub>
0C	Special processing: If two Hex0C appear together, replace the pair with: ¶¶<!-- paragraphs --> If a Hex0C appears not in a pair, replace it with: ¶<!-- paragraph -->	Special processing: If two Hex0C appear together, replace the pair with: <b>¶¶ </b><!-- paragraphs --> If a Hex0C appears not in a pair, replace it with: <b>¶</b><!-- paragraph -->	Special processing: If two Hex0C appear together, replace the pair with: <sup>¶ ¶</sup><!-- paragraphs --> If a Hex0C appears not in a pair, replace it with: <sup>¶</sup><!-- paragraph -->	Special processing: If two Hex0C appear together, replace the pair with: <sub>¶ ¶</sub><!-- paragraphs --> If a Hex0C appears not in a pair, replace it with: <sub>¶ </sub><!-- paragraph -->
0D to 0F	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character
10	<!-- divided by -->÷	<b><!-- divided by -->÷</b>	<sup><!-- divided by -->÷</sup>	<sub><!-- divided by -->÷</sub>
11	<nobr><!-- is much less than --><<a style="position: relative; left: -0.2 em; top: -0.1 em; font-size: 0.8 em; font-weight: normal"><</a></nobr>	<b><nobr><!-- is much less than --><<a style="position: relative; left: -0.2 em; top: -0.1 em; font-size: 0.8 em; font-weight: normal"><</a></nobr></b>	<sup><nobr><!-- is much less than --><<a style="position: relative; left: -0.2 em; top: -0.1 em; font-size: 0.8 em; font-weight: normal"><</a></nobr></sup>	<sub><nobr><!-- is much less than --><<a style="position: relative; left: -0.2 em; top: -0.1 em; font-size: 0.8 em; font-weight: normal"><</a></nobr></sub>
12	<nobr><!-- is much greater than -->><a style="position: relative; left: -0.2 em; top: -0.1 em; font-size: 0.8 em; font-weight: normal">></a></nobr>	<b><nobr><!-- is much greater than -->><a style="position: relative; left: -0.2 em; top: -0.1 em; font-size: 0.8 em; font-weight: normal">></a></nobr></b>	<sup><nobr><!-- is much greater than -->><a style="position: relative; left: -0.2 em; top: -0.1 em; font-size: 0.8 em; font-weight: normal">></a></nobr></sup>	<sub><nobr><!-- is much greater than -->><a style="position: relative; left: -0.2 em; top: -0.1 em; font-size: 0.8 em; font-weight: normal">></a></nobr></sub>
13	Special processing: (1) Output: <nobr><!-- is nearly equal to -->~<a style="position: relative; left: -0.5 em; top: -0.2 em; font-size: 1.0 em; font-weight: normal">~</a></nobr> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes an is-nearly-equal-to sign that may be misinterpreted by your reader as a tilde followed by another tilde.”	Special processing: (1) Output: <b><nobr><!-- is nearly equal to -->~<a style="position: relative; left: -0.5 em; top: -0.2 em; font-size: 1.0 em; font-weight: normal">~</a></nobr></b> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes an is-nearly-equal-to sign that may be misinterpreted by your reader as a tilde followed by another tilde.”	Special processing: (1) Output: <sup><nobr><!-- is nearly equal to -->~<a style="position: relative; left: -0.5 em; top: -0.2 em; font-size: 1.0 em; font-weight: normal">~</a></nobr></sup> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes an is-nearly-equal-to sign that may be misinterpreted by your reader as a tilde followed by another tilde.”	Special processing: (1) Output: <sub><nobr><!-- is nearly equal to -->~<a style="position: relative; left: -0.5 em; top: -0.2 em; font-size: 1.0 em; font-weight: normal">~</a></nobr></sub> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes an is-nearly-equal-to sign that may be misinterpreted by your reader as a tilde followed by another tilde.”
14	<!-- is approximately equal to -->≅	<b><!-- is approximately equal to -->≅</b>	<sup><!-- is approximately equal to -->≅</sup>	<sub><!-- is approximately equal to -->≅</sub>
15	Special processing: (1) Output: <nobr><!-- is not less than --><<a style="position: relative; left: -0.4 em; top: -0.2 em; font-size: 1.0 em; font-weight: normal">\|</a></nobr> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes an is-not-less-than sign that may be misinterpreted by your reader as a less-than sign followed by a vertical pipe.”	Special processing: (1) Output: <b><nobr><!-- is not less than --><<a style="position: relative; left: -0.4 em; top: -0.2 em; font-size: 1.0 em; font-weight: normal">\|</a></nobr></b> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes an is-not-less-than sign that may be misinterpreted by your reader as a less-than sign followed by a vertical pipe.”	Special processing: (1) Output: <sup><nobr><!-- is not less than --><<a style="position: relative; left: -0.4 em; top: -0.2 em; font-size: 1.0 em; font-weight: normal">\|</a></nobr></sup> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes an is-not-less-than sign that may be misinterpreted by your reader as a less-than sign followed by a vertical pipe.”	Special processing: (1) Output: <sub><nobr><!-- is not less than --><<a style="position: relative; left: -0.4 em; top: -0.2 em; font-size: 1.0 em; font-weight: normal">\|</a></nobr></sub> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes an is-not-less-than sign that may be misinterpreted by your reader as a less-than sign followed by a vertical pipe.”
16	Special processing: (1) Output: <nobr><!-- is not greater than -->&#62<a style="position: relative; left: -0.4 em; top: -0.2 em; font-size: 1.0 em; font-weight: normal" >\|</a></nobr> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes an is-not-greater-than sign that may be misinterpreted by your reader as a greater-than sign followed by a vertical pipe.”	Special processing: (1) Output: <b><nobr><!-- is not greater than -->&#62<a style="position: relative; left: -0.4 em; top: -0.2 em; font-size: 1.0 em; font-weight: normal" >\|</a></nobr></b> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes an is-not-greater-than sign that may be misinterpreted by your reader as a greater-than sign followed by a vertical pipe.”	Special processing: (1) Output: <sup><nobr><!-- is not greater than -->&#62<a style="position: relative; left: -0.4 em; top: -0.2 em; font-size: 1.0 em; font-weight: normal" >\|</a></nobr></sup> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes an is-not-greater-than sign that may be misinterpreted by your reader as a greater-than sign followed by a vertical pipe.”	Special processing: (1) Output: <sub><nobr><!-- is not greater than -->&#62<a style="position: relative; left: -0.4 em; top: -0.2 em; font-size: 1.0 em; font-weight: normal" >\|</a></nobr></sub> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes an is-not-greater-than sign that may be misinterpreted by your reader as a greater-than sign followed by a vertical pipe.”
17	Special processing: (1) Output: <nobr><!-- minus or plus -->+<a style="position: relative; left: -0.5 em; top: -0.5 em; font-size: 1.0 em; font-weight: normal"></a></nobr> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes a minus-or-plus sign that may be misinterpreted by your reader as a dash followed by a plus sign.”	Special processing: (1) Output: <b><nobr><!-- minus or plus -->+<a style="position: relative; left: -0.5 em; top: -0.5 em; font-size: 1.0 em; font-weight: normal"></a></nobr></b> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes a minus-or-plus sign that may be misinterpreted by your reader as a dash followed by a plus sign.”	Special processing: (1) Output: <sup><nobr><!-- minus or plus -->+<a style="position: relative; left: -0.5 em; top: -0.5 em; font-size: 1.0 em; font-weight: normal"></a></nobr></sup> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes a minus-or-plus sign that may be misinterpreted by your reader as a dash followed by a plus sign.”	Special processing: (1) Output: <sub><nobr><!-- minus or plus -->+<a style="position: relative; left: -0.5 em; top: -0.5 em; font-size: 1.0 em; font-weight: normal"></a></nobr></sub> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes a minus-or-plus sign that may be misinterpreted by your reader as a dash followed by a plus sign.”
18 [257]	<!-- -->     <!-- -->	<!-- -->     <!-- -->	<!-- -->     <!-- -->	<!-- -->     <!-- -->
19 [258]	<!-- -->  <!-- -->	<!-- -->   <!-- -->	<!-- -->   <!-- -->	<!-- -->   <!-- -->
1A	<!-- --> <!-- -->	<!-- --> <!-- -->	<!-- --> <!-- -->	<!-- --> <!-- -->
1B	<!-- plus or minus -->±	<b><!-- plus or minus -->±</b>	<sup><!-- plus or minus -->±</sup>	<sub><!-- plus or minus -->±</sub>
1C to 1D	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character
1E	<!-- dagger -->†	<b><!-- dagger -->†</b>	<sup><!-- dagger -->†</sup>	<sub><!-- dagger -->†</sub>
1F	<!-- C in a circle -->©	<b><!-- C in a circle -->©</b>	<sup><!-- C in a circle -->©</sup>	<sup><!-- C in a circle -->©</sup>
20
21	Special processing: (1) Output: <nobr><!-- is identical with -->=<a style="position: relative; left: -0.5 em; top: -0.3 em; font-size: 1.0 em; font-weight: normal"></a></nobr> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes an is-identical-with sign that may be misinterpreted by your reader as an equals sign followed by a dash.”	Special processing: (1) Output: <b><nobr><!-- is identical with -->=<a style="position: relative; left: -0.5 em; top: -0.3 em; font-size: 1.0 em; font-weight: normal"></a></nobr></b> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes an is-identical-with sign that may be misinterpreted by your reader as an equals sign followed by a dash.”	Special processing: (1) Output: <sup><nobr><!-- is identical with -->=<a style="position: relative; left: -0.5 em; top: -0.3 em; font-size: 1.0 em; font-weight: normal"></a></nobr></sup> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes an is-identical-with sign that may be misinterpreted by your reader as an equals sign followed by a dash.”	Special processing: (1) Output: <sub><nobr><!-- is identical with -->=<a style="position: relative; left: -0.5 em; top: -0.3 em; font-size: 1.0 em; font-weight: normal"></a></nobr></sub> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes an is-identical-with sign that may be misinterpreted by your reader as an equals sign followed by a dash.”
22	<!-- double prime -->''	<b><!-- double prime -->''</b>	<sup><!-- double prime -->''</sup>	<sub><!-- double prime -->''</sub>
23	#	<b>#</b>	<sup>#</sup>	<sub>#</sub>
24	$	<b>$</b>	<sup>$</sup>	<sub>$</sub>
25	<!-- is not equal to -->≠	<b><!-- is not equal to -->≠</b>	<sup><!-- is not equal to -->≠</sup>	<sub><!-- is not equal to -->≠</sub>
26	&	<b>&</b>	<sup>&</sup>	<sub>&</sub>
27	Special processing: (1) Output: <nobr><!-- is not identical with -->=<a style="position: relative; left: -0.4 em; top: -0.2 em; font-size: 1.0 em; font-weight: normal">\|</a></nobr> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes an is-not-identical-with sign that may be misinterpreted by your reader as an equals sign followed by a vertical pipe.”	Special processing: (1) Output: <b><nobr><!-- is not identical with -->=<a style="position: relative; left: -0.4 em; top: -0.2 em; font-size: 1.0 em; font-weight: normal">\|</a></nobr></b> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes an is-not-identical-with sign that may be misinterpreted by your reader as an equals sign followed by a vertical pipe.”	Special processing: (1) Output: <sup><nobr><!-- is not identical with -->=<a style="position: relative; left: -0.4 em; top: -0.2 em; font-size: 1.0 em; font-weight: normal">\|</a></nobr></sup> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes an is-not-identical-with sign that may be misinterpreted by your reader as an equals sign followed by a vertical pipe.”	Special processing: (1) Output: <sub><nobr><!-- is not identical with -->=<a style="position: relative; left: -0.4 em; top: -0.2 em; font-size: 1.0 em; font-weight: normal">\|</a></nobr></sub> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes an is-not-identical-with sign that may be misinterpreted by your reader as an equals sign followed by a vertical pipe.”
28	(	<b>(</b>	<sup>(</sup>	<sub>(</sub>
29	)	<b>)</b>	<sup>)</sup>	<sub>)</sub>
2A	*	<b>*</b>	<sup>*</sup>	<sub>*</sub>
2B	+	<b>+</b>	<sup>+</sup>	<sub>+</sub>
2C	,	<b>,</b>	<sup>,</sup>	<sub>,</sub>
2D	-	<b>-</b>	<sup>-</sup>	<sub>-</sub>
2E	.	<b>.</b>	<sup>.</sup>	<sub>.</sub>
2F	/	<b>/</b>	<sup>/</sup>	<sub>/</sub>
30	0	<b>0</b>	<sup>0</sup>	<sub>0</sub>
31	1	<b>1</b>	<sup>1</sup>	<sub>1</sub>
32	2	<b>2</b>	<sup>2</sup>	<sub>2</sub>
33	3	<b>3</b>	<sup>3</sup>	<sub>3</sub>
34	4	<b>4</b>	<sup>4</sup>	<sub>4</sub>
35	5	<b>5</b>	<sup>5</sup>	<sub>5</sub>
36	6	<b>6</b>	<sup>6</sup>	<sub>6</sub>
37	7	<b>7</b>	<sup>7</sup>	<sub>7</sub>
38	8	<b>8</b>	<sup>8</sup>	<sub>8</sub>
39	9	<b>9</b>	<sup>9</sup>	<sub>9</sub>
3A	<!-- is less than or equal to -->≤	<b><!-- is less than or equal to -->≤</b>	<sup><!-- is less than or equal to -->≤</sup>	<sub><!-- is less than or equal to -->≤</sub>
3B	<!-- is greater than or equal to -->≥	<b><!-- is greater than or equal to -->≥</b>	<sup><!-- is greater than or equal to -->≥</sup>	<sub><!-- is greater than or equal to -->≥</sub>
3C	<!-- is less than --><	<b><!-- is less than --><</b>	<sup><!-- is less than --><</sup>	<sub><!-- is less than --><</sub>
3D	=	<b>=</b>	<sup>=</sup>	<sub>=</sub>
3E [259]	<!-- is greater than -->>	<b><!-- is greater than -->></b>	<sup><!-- is greater than -->></sup>	<sub><!-- is greater than -->></sub>
3F [260]	¦ ¦	<b>¦ ¦</b>	<sup>¦ ¦ </sup>	<sub>¦ ¦</sub>
40	@	<b>@</b>	<sup>@</sup>	<sub>@</sub>
41	<!-- Alpha -->Α	<b><!-- Alpha -->Α</b>	<sup><!-- Alpha -->Α</sup>	<sub><!-- Alpha -->Α</sub>
42	<!-- Beta -->Β	<b><!-- Beta -->Β</b>	<sup><!-- Beta -->Β</sup>	<sub><!-- Beta -->Β</sub>
43	<!-- Psi -->Ψ	<b><!-- Psi -->Ψ</b>	<sup><!-- Psi -->Ψ</sup>	<sub><!-- Psi -->Ψ</sub>
44	<!-- Delta -->Δ	<b><!-- Delta -->Δ</b>	<sup><!-- Delta -->Δ</sup>	<sub><!-- Delta -->Δ</sub>
45	<!-- Epsilon -->Ε	<b><!-- Epsilon -->Ε</b>	<sup><!-- Epsilon -->Ε</sup>	<sub><!-- Epsilon -->Ε</sub>
46 [261]	<!-- Phi -->Φ	<b><!-- Phi -->Φ</b>	<sup><!-- Phi -->Φ</sup>	<sub><!-- Phi -->Φ</sub>
47	<!-- Gamma -->Γ	<b><!-- Gamma -->Γ</b>	<sup><!-- Gamma -->Γ</sup>	<sub><!-- Gamma -->Γ</sub>
48	<!—Eta -->Η	<b><!-- Eta -->Η</b>	<sup><!-- Eta -->Η</sup>	<sub><!-- Eta -->Η</sub>
49	<!-- Iota -->Ι	<b><!-- Iota -->Ι</b>	<sup><!-- Iota -->Ι</sup>	<sub><!-- Iota -->Ι</sub>
4A	<!-- Xi -->Ξ	<b><!-- Xi -->Ξ</b>	<sup><!-- Xi -->Ξ</sup>	<sub><!-- Xi -->Ξ</sub>
4B	<!-- Kappa -->Κ	<b><!-- Kappa -->Κ</b>	<sup><!-- Kappa -->Κ</sup>	<sub><!-- Kappa -->Κ</sub>
4C	<!-- Lambda -->Λ	<b><!-- Lambda -->Λ</b>	<sup><!-- Lambda -->Λ</sup>	<sub><!-- Lambda -->Λ</sub>
4D	<!-- Mu -->Μ	<b><!-- Mu -->Μ</b>	<sup><!-- Mu -->Μ</sup>	<sub><!-- Mu -->Μ</sub>
4E	<!-- Nu -->Ν	<b><!-- Nu -->Ν</b>	<sup><!-- Nu -->Ν</sup>	<sub><!-- Nu -->Ν</sub>
4F	<!-- Omicron -->Ο	<b><!-- Omicron -->Ο</b>	<sup><!-- Omicron -->Ο</sup>	<sub><!-- Omicron -->Ο</sub>
50	<!--Pi -->Π	<b><!--Pi -->Π</b>	<sup><!--Pi -->Π</sup>	<sub><!--Pi -->Π</sub>
51	<!-- Classic Theta -->Θ	<b><!-- Classic Theta -->Θ</b>	<sup><!-- Classic Theta -->Θ</sup>	<sub><!-- Classic Theta -->Θ</sub>
52	<!-- Rho -->Ρ	<b><!-- Rho -->Ρ</b>	<sup><!-- Rho -->Ρ</sup>	<sub><!-- Rho -->Ρ</sub>
53	<!-- Sigma -->Σ	<b><!-- Sigma -->Σ</b>	<sup><!-- Sigma -->Σ</sup>	<sub><!-- Sigma -->Σ</sub>
54	<!-- Tau -->Τ	<b><!-- Tau -->Τ</b>	<sup><!-- Tau -->Τ</sup>	<sub><!-- Tau -->Τ</sub>
55	Special processing: (1) Output: <nobr><!-- Theta -->O<a style="position: relative; left: -0.6 em; top: -0.0 em; font-size: 1.0 em; font-weight: normal"></a></nobr> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes a Theta that may be misinterpreted by your reader as an O followed by a dash.”	Special processing: (1) Output: <b><nobr><!-- Theta -->O<a style="position: relative; left: -0.6 em; top: -0.0 em; font-size: 1.0 em; font-weight: normal"></a></nobr></b> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes a Theta that may be misinterpreted by your reader as an O followed by a dash.”	Special processing: (1) Output: <sup><nobr><!-- Theta -->O<a style="position: relative; left: -0.6 em; top: -0.0 em; font-size: 1.0 em; font-weight: normal"></a></nobr></sup> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes a Theta that may be misinterpreted by your reader as an O followed by a dash.”	Special processing: (1) Output: <sub><nobr><!-- Theta -->O<a style="position: relative; left: -0.6 em; top: -0.0 em; font-size: 1.0 em; font-weight: normal"></a></nobr></sub> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes a Theta that may be misinterpreted by your reader as an O followed by a dash.”
56	<!-- Omega -->Ω	<b><!-- Omega -->Ω</b>	<sup><!-- Omega -->Ω</sup>	<sub><!-- Omega -->Ω</sub>
57	Modern Theta	<b>Modern Theta</b>	<sup>Modern Theta</sup>	<sub>Modern Theta</sub>
58	<!-- Chi -->Χ	<b><!-- Omega -->Χ</b>	<sup><!-- Omega -->Χ</sup>	<sub><!-- Omega -->Χ</sub>
59	<!-- Upsilon -->Υ	<b><!-- Upsilon -->Υ</b>	<sup><!-- Upsilon -->Υ</sup>	<sub><!-- Upsilon -->Υ</sub>
5A	<!-- Zeta -->Ζ	<b><!-- Zeta -->Ζ</b>	<sup><!-- Zeta -->Ζ</sup>	<sub><!-- Zeta -->Ζ</sub>
5B	[	<b>[</b>	<sup>[</sup>	<sub>[</sub>
5C	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character
5D	]	<b>]</b>	<sup>]</sup>	<sub>]</sub>
5E [262]	Special processing: (1) Store all of the text between the Hex 5E and the previous blank space[263],   <td> tag, <p>, <br>, bell-code[264], or EOF[265], as {hold-1} - - - (2) Store all of the text between Hex 5E and the next blank space[266],   <td> tag, <p>, <br>, bell-code[267], or EOF[268], as {hold-2} - - - (3) Output: -{hold-2} <!-- {hold-1}-{hold-2} -->	Special processing: (1) Store all of the text between the Hex 5E and the previous blank space[269],   <td> tag, <p>, <br>, bell-code[270], or EOF[271], as {hold-1} - - - (2) Store all of the text between Hex 5E and the next blank space[272],   <td> tag, <p>, <br>, bell-code[273], or EOF[274], as {hold-2} - - - (3) Output: <b>-</b>{hold-2} <!-- {hold-1}-{hold-2} -->	Special processing: (1) Store all of the text between the Hex 5E and the previous blank space[275],   <td> tag, <p>, <br>, bell-code[276], or EOF[277], as {hold-1} - - - (2) Store all of the text between Hex 5E and the next blank space[278],   <td> tag, <p>, <br>, bell-code[279], or EOF[280], as {hold-2} - - - (3) Output: <sup>-</sup>{hold-2} <!-- {hold-1}-{hold-2} -->	Special processing: (1) Store all of the text between the Hex 5E and the previous blank space[281],   <td> tag, <p>, <br>, bell-code[282], or EOF[283], as {hold-1} - - - (2) Store all of the text between Hex 5E and the next blank space[284],   <td> tag, <p>, <br>, bell-code[285], or EOF[286], as {hold-2} - - - (3) Output: <sub>-</sub>{hold-2} <!-- {hold-1}-{hold-2} -->
5F [287]	Special processing: (1) Store all of the text between the Hex 5F and the previous blank space[288],   <td> tag, <p>, <br>, bell-code[289], or EOF[290], as {hold-1} - - - (2) Store all of the text between Hex 5E and the next blank space[291],   <td> tag, <p>, <br>, bell-code[292], or EOF[293], as {hold-2} - - - (3) Output: {hold-2} <!-- {hold-1}-{hold-2} -->	Special processing: (1) Store all of the text between the Hex 5F and the previous blank space[294],   <td> tag, <p>, <br>, bell-code[295], or EOF[296], as {hold-1} - - - (2) Store all of the text between Hex 5E and the next blank space[297],   <td> tag, <p>, <br>, bell-code[298], or EOF[299], or EOF[300], as {hold-2} - - - (3) Output: <b></b>{hold-2} <!-- {hold-1}-{hold-2} -->	Special processing: (1) Store all of the text between the Hex 5F and the previous blank space[301],   <td> tag, <p>, <br>, or bell-code[302], or EOF[303], as {hold-1} - - - (2) Store all of the text between Hex 5E and the next blank space[304],   <td> tag, <p>, <br>, bell-code[305], or EOF[306], as {hold-2} - - - (3) Output: <sup></sup>{hold-2} <!-- {hold-1}-{hold-2} -->	Special processing: (1) Store all of the text between the Hex 5F and the previous blank space[307],   <td> tag, <p>, <br>, bell-code[308], or EOF[309], as {hold-1} - - - (2) Store all of the text between Hex 5E and the next blank space[310],   <td> tag, <p>, <br>, bell-code[311] , or EOF[312], as {hold-2} - - - (3) Output: <sub></sub>{hold-2} <!-- {hold-1}-{hold-2} -->
60	Special processing: (1) Output: <nobr><!-- is less than or greater than -->><a style="position: relative; left: -0.5 em; top: -0.3 em; font-size: 1.0 em; font-weight: normal"><</a></nobr> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes a less-than-or-greater-than sign that may be misinterpreted by your reader as a less-than sign followed by a greater-than sign.”	Special processing: (1) Output: <b><nobr><!-- is less than or greater than -->><a style="position: relative; left: -0.5 em; top: -0.3 em; font-size: 1.0 em; font-weight: normal"><</a></nobr></b> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes a less-than-or-greater-than sign that may be misinterpreted by your reader as a less-than sign followed by a greater-than sign.”	Special processing: (1) Output: <sup><nobr><!-- is less than or greater than -->><a style="position: relative; left: -0.5 em; top: -0.3 em; font-size: 1.0 em; font-weight: normal"><</a></nobr></sup> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes a less-than-or-greater-than sign that may be misinterpreted by your reader as a less-than sign followed by a greater-than sign.”	Special processing: (1) Output: <sub><nobr><!-- is less than or greater than -->><a style="position: relative; left: -0.5 em; top: -0.3 em; font-size: 1.0 em; font-weight: normal"><</a></nobr></sub> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes a less-than-or-greater-than sign that may be misinterpreted by your reader as a less-than sign followed by a greater-than sign.”
61	<!-- alpha -->α	<b><!-- alpha -->α</b>	<sup><!-- alpha -->α</sup>	<sub><!-- alpha -->α</sub>
62	<!-- beta -->β	<b><!-- beta -->β</b>	<sup><!-- beta -->β</sup>	<sub><!-- beta -->β</sub>
63	<!-- psi -->ψ	<b><!-- psi -->ψ</b>	<sup><!-- psi -->ψ</sup>	<sub><!-- psi -->ψ</sub>
64	<!-- delta -->δ	<b><!-- delta -->δ</b>	<sup><!-- delta -->δ</sup>	<sub><!-- delta -->δ</sub>
65	<!-- epsilon -->ε	<b><!-- epsilon -->ε</b>	<sup><!-- epsilon -->ε</sup>	<sub><!-- epsilon -->ε</sub>
66 [313]	<!-- phi -->φ	<b><!-- phi -->φ</b>	<sup><!-- phi -->φ</sup>	<sub><!-- phi -->φ</sub>
67	<!-- gamma -->γ	<b><!-- gamma -->γ</b>	<sup><!-- gamma -->γ</sup>	<sub><!-- gamma -->γ</sub>
68	<!-- eta -->η	<b><!-- eta -->η</b>	<sup><!-- eta -->η</sup>	<sub><!-- eta -->η</sub>
69	<!-- iota -->ι	<b><!-- iota -->ι</b>	<sup><!-- iota -->ι</sup>	<sub><!-- iota -->ι</sub>
6A	<!-- xi -->ξ	<b><!-- xi -->ξ</b>	<sup><!-- xi -->ξ</sup>	<sub><!-- xi -->ξ</sub>
6B	<!-- kappa -->κ	<b><!-- kappa -->κ</b>	<sup><!-- kappa -->κ</sup>	<sub><!-- kappa -->κ</sub>
6C	<!-- lambda -->λ	<b><!-- lambda -->λ</b>	<sup><!-- lambda -->λ</sup>	<sub><!-- lambda -->λ</sub>
6D [314]	<!-- mu -->µ	<b><!-- mu -->µ</b>	<sup><!-- mu -->µ</sup>	<sub><!-- mu -->µ</sub>
6E	<!-- nu -->ν	<b><!-- nu -->ν</b>	<sup><!-- nu -->ν</sup>	<sub><!-- nu -->ν</sub>
6F	<!-- omicron -->ο	<b><!-- omicron -->ο</b>	<sup><!-- omicron -->ο</sup>	<sub><!-- omicron -->ο</sub>
70	<!-- pi -->π	<b><!-- pi -->π</b>	<sup><!-- pi -->π</sup>	<sub><!-- pi -->π</sub>
71	classic theta	<b>classic theta<b>	<sup>classic theta</sup>	<sub>classic theta</sub>
72	<!-- rho -->ρ	<b><!-- rho -->ρ</b>	<sup><!-- rho -->ρ</sup>	<sub><!-- rho -->ρ</sub>
73	<!-- sigma -->σ	<b><!-- sigma -->σ</b>	<sup><!-- sigma -->σ</sup>	<sub><!-- sigma -->σ</sub>
74	<!-- tau -->τ	<b><!-- tau -->τ</b>	<sup><!-- tau -->τ</sup>	<sub><!-- tau -->τ</sub>
75	<!-- theta -->θ	<b><!-- theta -->θ</b>	<sup><!-- theta -->θ</sup>	<sub><!-- theta -->θ</sub>
76	<!-- omega -->ω	<b><!-- omega -->ω</b>	<sup><!-- omega -->ω</sup>	<sub><!-- omega -->ω</sub>
77	modern theta	<b>modern theta</b>	<sup>modern theta</sup>	<sub>modern theta</sub>
78	<!-- chi -->χ	<b><!-- chi -->χ</b>	<sup><!-- chi -->χ</sup>	<sub><!-- chi -->χ</sub>
79	<!-- upsilon -->υ	<b><!-- upsilon -->υ</b>	<sup><!-- upsilon -->υ</sup>	<sub><!-- upsilon -->υ</sub>
7A	<!-- zeta -->ζ	<b><!-- zeta -->ζ</b>	<sup><!-- zeta -->ζ</sup>	<sub><!-- zeta -->ζ</sub>
7B	<!-- { -->{	<b><!-- { -->{</b>	<sup><!-- { -->{</sup>	<sub><!-- { -->{</sub>
7C [315]	¦	<b>¦</b>	<sup>¦</sup>	<sub>¦</sub>
7D	<!-- } -->}	<b><!-- } -->}</b>	<sup><!-- } -->}</sup>	<sub><!-- } -->}</sub>
7E	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character
7F [316]	<!-- R in a circle -->®	<!-- R in a circle -->®	<sup><!-- R in a circle -->®</sup>	<sup><!-- R in a circle -->®</sup>
80 to A9	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character
AA	<!-- is greater than or equal to -->≥	<b><!-- is greater than or equal to -->≥</b>	<sup><!-- is greater than or equal to -->≥</sup>	<sub><!-- is greater than or equal to -->≥</sub>
AB [317]	<!-- degrees -->°	<b><!-- degrees -->°</b>	<sup><!-- degrees -->°</sup>	<sub><!-- degrees -->°</sub>
AC	<!-- prime -->'	<b><!-- prime -->'</b>	<sup><!-- prime -->'</sup>	<sub><!-- prime -->'</sub>
AD	/	/	/>	/
AE	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character
AF	<!-- C in a circle -->©	<!-- C in a circle -->©	<sup><!-- C in a circle -->©</sup>	<sub><!-- C in a circle -->©</sub>
B0 to B9	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character
BA	Special processing: (1) Output: <nobr><!-- is greater than or less than --><<a style="position: relative; left: -0.5 em; top: -0.3 em; font-size: 1.0 em; font-weight: normal">></a></nobr> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes a greater-than-or-less-than sign that may be misinterpreted by your reader as a greater-than sign followed by a less-than sign.”	Special processing: (1) Output: <b><nobr><!-- is greater than or less than --><<a style="position: relative; left: -0.5 em; top: -0.3 em; font-size: 1.0 em; font-weight: normal">></a></nobr></b> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes a greater-than-or-less-than sign that may be misinterpreted by your reader as a greater-than sign followed by a less-than sign.”	Special processing: (1) Output: <sup><nobr><!-- is greater than or less than --><<a style="position: relative; left: -0.5 em; top: -0.3 em; font-size: 1.0 em; font-weight: normal">></a></nobr></sup> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes a greater-than-or-less-than sign that may be misinterpreted by your reader as a greater-than sign followed by a less-than sign.”	Special processing: (1) Output: <sub><nobr><!-- is greater than or less than --><<a style="position: relative; left: -0.5 em; top: -0.3 em; font-size: 1.0 em; font-weight: normal">></a></nobr></sub> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes a greater-than-or-less-than sign that may be misinterpreted by your reader as a greater-than sign followed by a less-than sign.”
BB	<!-- radical -->√	<b><!-- radical -->√</b>	<sup><!-- radical -->√</sup>	<sub><!-- radical -->√</i></sub>
BC	[STAR]	[STAR]	[STAR]	[STAR]
BD	<!-- double dagger -->‡	<b><!-- double dagger -->‡</b>	<sup><!-- double dagger -->‡ </sup>	<sub><!-- double dagger -->‡ </sub>
BE	<!-- is less than or equal to -->≤	<b><!-- is less than or equal to -->≤</b>	<sup><!-- is less than or equal to -->≤</sup>	<sub><!-- is less than or equal to -->≤</sub>
BF [318]	<!-- ( ) -->	<b><!-- ( ) --></b>	<sup><!-- ( ) --></sup>	<sub><!-- ( ) --></sub>
BA to C3	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character
C4	Special processing: (1) Output: <nobr><!-- in perspecitve to -->~<a style="position: relative; left: -0.5 em; top: 0.2 em; font-size: 1.0 em; font-weight: normal"></a></nobr> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes an in-perspective-to sign that may be misinterpreted by your reader as a tilde followed by a dash.”	Special processing: (1) Output: <b><nobr><!-- in perspecitve to -->~<a style="position: relative; left: -0.5 em; top: 0.2 em; font-size: 1.0 em; font-weight: normal"></a></nobr></b> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes an in-perspective-to sign that may be misinterpreted by your reader as a tilde followed by a dash.”	Special processing: (1) Output: <sup><nobr><!-- in perspecitve to -->~<a style="position: relative; left: -0.5 em; top: 0.2 em; font-size: 1.0 em; font-weight: normal"></a></nobr></sup> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes an in-perspective-to sign that may be misinterpreted by your reader as a tilde followed by a dash.”	Special processing: (1) Output: <sub><nobr><!-- in perspecitve to -->~<a style="position: relative; left: -0.5 em; top: 0.2 em; font-size: 1.0 em; font-weight: normal"></a></nobr></sub> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes an in-perspective-to sign that may be misinterpreted by your reader as a tilde followed by a dash.”
C5	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character
C6	<b>/</b>	<b>/</b>	<b>/</b>	<b>/</b>
C7 to C8	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character
C9	<!-- infinity -->∞	<b><!-- infinity -->∞</b>	<sup><!-- infinity -->∞</sup>	<sub><!-- infinity -->∞</sub>
CA	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character
CB	<!-- is perpendicular to -->⊥	<b><!-- is perpendicular to -->⊥</b>	<sup><!-- is perpendicular to -->⊥</sup>	<sub><!-- is perpendicular to -->⊥</sub>
CC to FF	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character

Grid 7
Hex	Typeface 1	Typeface 2	Typeface 3	Typeface 4
00	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character
01 [319]	<font size=“1”><!-- * -->•</font>	<!-- * -->•	<!-- * -->•	Special processing: unidentified character
02 to 05	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character
06	<sup><font face=“arial, helvetica, geneva”>4</sup>	Special processing: If two Hex06 appear together, replace the pair with: <sub>§§ </sub><!-- sections --> If a Hex06 appears not in a pair, replace it with: <sub>§</sub> <!-- section -->	Special processing: If two Hex06 appear together, replace the pair with: <sup><i>§§</i></sup> <!-- sections --> If a Hex06 appears not in a pair, replace it with: <sup><i>§ </i></sup><!-- section -->	Special processing: unidentified character
07	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character
08	<sub><font face=“arial, helvetica, geneva”>9</sub>	<font face=“Letter Gothic, Monospaced, FrnkGothITC Bk BT, Franklin Gothic, FrankfurtGothic”> <sup>7</sup>/<sub>8 </sub></font>	O	O
09	Special processing: (1) Replace with: (2) Go back to the previous blank space[320],   <td> tag, <p>, <br>, bell-code[321], or EOF[322], and insert after it: <nobr> (3) Go forward to the next blank space[323],   <td> tag, <p>, <br>, bell-code[324], or EOF[325], and insert after it: </nobr> (4) Output: <!-- (5) Again output all of the text between <nobr> and </nobr>, but this time replace the occurrence(s) of with a dash[326] (6) Output: -->	Special processing: (1) Replace with: (2) Go back to the previous blank space[327],   <td> tag, <p>, <br>, bell-code[328], or EOF[329], and insert after it: <nobr> (3) Go forward to the next blank space[330],   <td> tag, <p>, <br>, bell-code[331], or EOF[332], and insert after it: </nobr> (4) Output: <!-- (5) Again output all of the text between <nobr> and </nobr>, but this time replace the occurrence(s) of with a dash[333] (6) Output: -->	Special processing: (1) Replace with: (2) Go back to the previous blank space[334],   <td> tag, <p>, <br>, bell-code[335], or EOF[336], and insert after it: <nobr> (3) Go forward to the next blank space[337],   <td> tag, <p>, <br>, bell-code[338], or EOF[339], and insert after it: </nobr> (4) Output: <!-- (5) Again output all of the text between <nobr> and </nobr>, but this time replace the occurrence(s) of with a dash[340] (6) Output: -->	Special processing: (1) Replace with: (2) Go back to the previous blank space[341],   <td> tag, <p>, <br>, bell-code[342], or EOF[343], and insert after it: <nobr> (3) Go forward to the next blank space[344],   <td> tag, <p>, <br>, bell-code[345], or EOF[346], and insert after it: </nobr> (4) Output: <!-- (5) Again output all of the text between <nobr> and </nobr>, but this time replace the occurrence(s) of with a dash[347] (6) Output: -->
0A	<sup><s>6</s></sup>	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character
0B	<sup><font face=“arial, helvetica, geneva”>7</sup>	<!-- cents -->¢	<!-- cents -->¢	Special processing: unidentified character
0C	<sup><font face=“arial, helvetica, geneva”>8</sup>	Special processing: If two Hex0C appear together, replace the pair with: ¶¶ <!-- paragraphs --> If a Hex0C appears not in a pair, replace it with: ¶<!-- paragraph -->	Special processing: If two Hex0C appear together, replace the pair with: ¶ ¶<!-- paragraphs --> If a Hex0C appears not in a pair, replace it with: ¶<!-- paragraph -->	Special processing: unidentified character
0D to 0F	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character
10	<sup><s>4</s></sup>	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character
11	Special processing: unidentified character	Special processing: unidentified character	[CUBE]	Special processing: unidentified character
12	Special processing: unidentified character	Special processing: unidentified character	Special processing: (1) Output: <!-- is proportionately equal to --><a style="position: relative; left: 0.0 em; top: -0.1 em; font-size: 0.8 em; font-weight: normal; letter-spacing: -0.1 em; text-decoration: underline">oc</a> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes an is-proportionally-equal-to sign that may be misinterpreted by your reader as: oc.”	Special processing: unidentified character
13	<sub><font face=“arial, helvetica, geneva”>5</sub>	<font face=“Letter Gothic, Monospaced, FrnkGothITC Bk BT, Franklin Gothic, FrankfurtGothic”> <sup>3</sup>/<sub>8 </sub></font>	Special processing: unidentified character	Special processing: unidentified character
14	<sub><font face=“arial, helvetica, geneva”>6</sub>	<font face=“Letter Gothic, Monospaced, FrnkGothITC Bk BT, Franklin Gothic, FrankfurtGothic”><sup>1</sup>/<sub>2</sub> </font>	<!-- slashed zero -->Ø	Special processing: unidentified character
15	<sub><font face=“arial, helvetica, geneva”>7</sub>	<font face=“Letter Gothic, Monospaced, FrnkGothITC Bk BT, Franklin Gothic, FrankfurtGothic”><sup>5 </sup>/<sub>8</sub> </font>	<font face=“Letter Gothic, Monospaced, FrnkGothITC Bk BT, Franklin Gothic, FrankfurtGothic”> <b><!-- slashed zero -->Ø</b> </font>	Special processing: unidentified character
16	<sub><font face=“arial, helvetica, geneva”>8</sub>	<font face=“Letter Gothic, Monospaced, FrnkGothITC Bk BT, Franklin Gothic, FrankfurtGothic”><sup>3 </sup>/<sub>4</sub> </font>	<font face=“Letter Gothic, Monospaced, FrnkGothITC Bk BT, Franklin Gothic, FrankfurtGothic”> <!-- slashed zero -->Ø</font>	Special processing: unidentified character
17	<sub><font face=“arial, helvetica, geneva”>0</sub>	[INVERTED SOLID TRIANGLE]	Special processing: unidentified character	Special processing: unidentified character
18 [348]	<!-- -->     <!-- -->	<!-- -->     <!-- -->	<!-- -->     <!-- -->	<!-- -->     <!-- -->
19	<!-- -->  <!-- -->	<!-- -->   <!-- -->	<!-- -->   <!-- -->	<!-- -->   <!-- -->
1A [349]	<!-- --> <!-- -->	<!-- --> <!-- -->	<!-- --> <!-- -->	<!-- --> <!-- -->
1B	<sup><font face=“arial, helvetica, geneva”>1</sup>	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character
1C to 1D	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character
1E	<sup><s>7</s></sup>	<!-- dagger -->†	<!-- dagger -->†	Special processing: unidentified character
1F	<sup><font face=“arial, helvetica, geneva”>3</sup>	<sup><!-- C in a circle -->©</sup>	<sup><!-- C in a circle -->©</sup>	<sup><!-- C in a circle -->©</sup>
20 [350]
21	<sup><s>9</s></sup>	Special processing: unidentified character	<!-- caret -->^	<sub><!-- } -->} </sub>
22	<sup><s>0</s></sup>	Special processing: unidentified character	[PERENNIAL]	Special processing: unidentified character
23	/	Special processing: unidentified character	#	#
24 [351]	<sub><s>1</s></sub>	Special processing: unidentified character	[PENTAGON]	<sup>\| </sup>
25	<sub><s>2</s></sub>	+	[RECTANGLE]	<sup><!-- { -->{ </sup>
26	<!-- 1/4 -->¼	<!-- minus -->-	<!-- up and down arrows -->↑&#8595	(
27	<sub><s>3</s></sub>	Special processing: unidentified character	Special processing: (1) Output: <nobr><!-- equal and divide -->=<a style="position: relative; left: -0.3 em; top: -0.0 em; font-size: 1.2 em; font-weight: normal">:</a></nobr> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes an equal-and-divide sign that may be misinterpreted by your reader as an equal sign followed by a colon.”	<sub>)</sub>
28	<sub><s>4</s></sub>	<font face=“GoudyOlSt BT, Goudy Old Style, GoldenOldStyle”>(</font>	<!-- inverted caret --><font face="Letter Gothic, Monospaced, FrnkGothITC Bk BT, Franklin Gothic, FrankfurtGothic">v</font>	<sup>(</sup>
29	<sub><s>5</s></sub>	<font face=“GoudyOlSt BT, Goudy Old Style, GoldenOldStyle”>)</font>	[INVERTED HOLLOW TRIANGLE]	<sup>[</sup>
2A	<sub><s>6</s></sub>	Special processing: (1) If {HTML font size} is greater than or equal to 7, then output: <b></b> (2)* If {HTML font size} is less than 7, then output: <font size=“+1”>*</font>	<!-- open triangle -->Δ	<sup>]</sup>
2B	<sub><s>7</s></sub>	<!-- plus in a circle -->⊕	<!-- plus in a circle -->⊕	Special processing: unidentified character
2C	<sub><s>8</s></sub>	<b><!-- up arrow -->↑</b>	<!-- right angle --><font face="Letter Gothic, Monospaced, FrnkGothITC Bk BT, Franklin Gothic, FrankfurtGothic"> <sup>L</sup></font>	belongs with
2D	<sub><s>9</s></sub>	<font face=“Bodoni, Bodoni Campanile, Modern 735, Bodoni Poster, Bodnoff”>. . .</font>	Special processing: (1) Output: <nobr><!-- is geometrically proportional to -->::<a style="position: relative; left: -0.7 em; top: -0.1 em; font-size: 0.5 em; font-weight: normal"></a></nobr> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes an is-geometrically-proportional-to sign that may be misinterpreted by your reader as two colons followed by a dash.”	<sup><!-- radical -->√</sup>
2E	<sub><s>0</s></sub>	<b><!-- left arrow -->←</b>	<!-- left-right arrow -->↔	Special processing: (1) Output: <nobr><!-- belongs to --><a style="position: relative; left: 0.0 em; top: 0.0 em; font-size: 1.0 em; font-weight: normal; font-family: sans-serif">C</a><a style="position: relative; left: -1.2 em; top: -0.4 em; font-size: 0.5 em" ></a></nobr> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes a belongs-to sign that may be misinterpreted by your reader as a C followed by a dash.”
2F	<sup><b>0</b></sup>	<!-- x in a circle -->⊗	<!-- inverted caret --><font face="Letter Gothic, Monospaced, FrnkGothITC Bk BT, Franklin Gothic, FrankfurtGothic"> <sup>v</sup></font>	<font size=“7”>(</font>
30 [352]	<sup>1</sup>/<sub>8 </sub>	[SOLID BOX]	↑\|	<font size=“6”><!-- sigma -->Σ </font>
31 [353]	<sup>3</sup>/<sub>8 </sub>	<b>(</b>	\|↑	<font size=“6”><!-- integral -->∫ </font>
32 [354]	<sup>5</sup>/<sub>8 </sub>	<b>)</b>	↓\|	Special processing: (1) Output: <nobr><!-- contour integral -->< font size="6">∫< /font><a style="position: relative; left: -0.6 em; top: -0.6 em; font-size: 1.0 em; font-weight: normal">O</a></nobr> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes a contour-integral sign that may be misinterpreted by your reader as an integral signed followed by an O.”
33 [355]	<sup>7</sup>/<sub>8 </sub>	<b><s>(</s></b>	\|↓	<font size=“6”>\| </font>
34 [356]	<sup>1</sup>/<sub>16 </sub>	<b><s>)</s></b>	Special processing: unidentified character	<font size=“6”> \|\| </font>
35 [357]	<sup>3</sup>/<sub>16 </sub>	<b>[</b>	Special processing: unidentified character	<font size=“6”>\| </font>
36	<sup>5</sup>/<sub>16 </sub>	<b>]</b>	Special processing: unidentified character	<font size=“6”>/</font>
37	<sup>7</sup>/<sub>16 </sub>	<b><s>[</s></b>	Special processing: unidentified character	<font size=“6”><!-- Pi -->Π </font>
38 [358]	<sup>9</sup>/<sub>16 </sub>	<b><s>]</s></b>	\|\|	<font size=“6”> <!-- Gamma -->Γ </font>
39 [359]	<sup><b>1</b></sup>	Special processing: unidentified character	\|\|\|	<font size=“6”> <!-- radical -->√ </font>
3A	<sup><b>2</b></sup>	:	<sup><!-- caret -->_</sup>	<sub><!-- { -->{ </sub>
3B	<sup><b>3</b></sup>	<b><!-- right arrow -->→</b>	<sup>[angle]</sup>	Special processing: (1) Output: <nobr><!-- is contained in a subclass of --><a style="position: relative; left: 0.0 em; top: 0.0 em; font-size: 1.0 em; font-weight: normal; font-family: sans-serif; text-decoration: underline">C</a></nobr> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes an is-contained-in-a-subclass-of sign that may be misinterpreted by your reader as a C.”
3C [360]	<sup><b>4</b></sup>	<font face=“Bodoni, Bodoni Campanile, Modern 735, Bodoni Poster, Bodnoff”> </font>	[solid left triangle]	Special processing: unidentified character
3D	<sup><b>5</b></sup>	Special processing: unidentified character	=	Special processing: unidentified character
3E	<sup><b>6</b></sup>	Special processing: unidentified character	[solid right triangle]	Special processing: unidentified character
3F	<sup><b>7</b></sup>	<b><!-- down arrow -->↓</b>	[angle]	contains the subclass
40	<sup><b>8</b></sup>	@	@	@
41 [361]	<sup>1</sup>/<sub>32 </sub>	<!-- solid diamond -->♦	Special processing: unidentified character	<font size=“6”>(</font>
42 [362]	<sup>3</sup>/<sub>32 </sub>	<!-- open diamond -->◊	Special processing: unidentified character	<font size=“6”>)</font>
43	<sup>5</sup>/<sub>32 </sub>	<!-- C in a circle -->©	Special processing: unidentified character	<!-- C in a circle -->©
44	<sup>7</sup>/<sub>32 </sub>	[solid triangle]	Special processing: unidentified character	Special processing: unidentified character
45 [363]	<sup>9</sup>/<sub>32 </sub>	[shaded box]	<u style="text-decoration: underline">→< /u>	<font size=“6”><!-- { -->{</font>
46 [364]	<sup><b>9</b></sup>	<font face=“Bodoni, Bodoni Campanile, Modern 735, Bodoni Poster, Bodnoff”>------</font>	Special processing: unidentified character	<font size=“6”><!-- } -->} </font>
47 [365]	<sub><b>0</b></sub>	Special processing: (1) Output: <!-- because -->.<a style="position: relative; left: -0.5 em; top: -0.5 em; font-size: 0.8 em; font-weight: normal; letter-spacing: -0.1 em">.</a><a style="position: relative; left: -0.2 em; top: -0.5 em; font-size: 0.8 em; font-weight: normal; letter-spacing: -0.1 em">.</a> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes a because sign that may be misinterpreted by your reader as three periods.”	Special processing: unidentified character	<font size=“6”>< </font>
48 [366]	<sub><b>1</b></sub>	<font face=“Bodoni, Bodoni Campanile, Modern 735, Bodoni Poster, Bodnoff”>--------</font>	=	<font size=“6”>> </font>
49 [367]	<sub><b>2</b></sub>	[large shaded box]	≡	<sub><!-- radical -->√ </sub>
4A	<sup>1</sup>/<sub>64 </sub>	[box with diagonal strokes]	/	<font size=“7”> <!-- sigma -->Σ</font>
4B	<sup>3</sup>/<sub>64 </sub>	[dotted box]	//	<font size=“7”> <!-- integral -->∫</font>
4C	<sup>5</sup>/<sub>64 </sub>	\	\	Special processing: unidentified character
4D [368]	<sup>7</sup>/<sub>64 </sub>	<b>\</b>	\\	<font size=“7” >\|</font>
4E [369]	<sup>9</sup>/<sub>64 </sub>	[bell]	[zigzag arrow]	<font size=“7”> \|\|</font>
4F [370]	<sub><b>3</b></sub>	<b>[bell]</b>	Special processing: unidentified character	<b><font size=“7” >\|</font></b>
50	<sub><b>4</b></sub>	Special processing: (1) Output: <nobr><!-- is not identical with -->=<a style="position: relative; left: -0.4 em; top: -0.2 em; font-size: 1.0 em; font-weight: normal">\|</a>< /nobr> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes an is-not-identical-with sign that may be misinterpreted by your reader as an equals sign followed by a vertical pipe.”	Special processing: unidentified character	<font size=“7”>/</font>
51	<sub><b>5</b></sub>	<!-- therefore -->∴	<sup><!-- is perpendicular to -->⊥</sup>	<font size=“7”><!-- radical -->√ </font>
52	<sub><b>6</b></sub>	<!-- R in a circle -->®	<!-- is perpendicular to -->⊥	<!-- R in a circle -->®
53	<sub><b>7</b></sub>	Special processing: unidentified character	<sup>[inverted open triangle]</sup>	<font size=“7”>)</font>
54	<sub><b>8</b></sub>	<!-- function -->ƒ	<!-- allmark -->°	<font size=“7”>[</font>
55	<sub><b>9</b></sub>	<!-- per mile -->‰	<sup>[rectangle] </sup>	<font size=“7”>]</font>
56 [371]	<b><!-- 1/2 -->½</b>	Special processing: unidentified character	<sup><!-- open triangle -->Δ</sup>	<font size=“7”> <!-- { -->®{ </font>
57	<b><sup>1</sup>/<sub>3</sub></b>	Special processing: unidentified character	<sup><!-- ( ) -->¤</sup>	<font size=“7”> <!-- } -->} </font>
58 [372]	<b><sup>2</sup>/<sub>3</sub></b>	<font face=“Bodoni, Bodoni Campanile, Modern 735, Bodoni Poster, Bodnoff”></font>	<sup><!—is geometrically proportional to -->∝</sup>	<font size=“7”>< </font>
59 [373]	<b><!-- 1/4 -->¼</b>	Special processing: unidentified character	Special processing: (1) Output: <sup><!-- approaches the limit --><nobr><!-- approaches the limit -->=<a style="position: relative; left: -0.4 em; top: -0.6 em; font-size: 1.0 em; font-weight: normal">.</a></nobr></sup> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes an approaches-the-limit sign that may be misinterpreted by your reader as an equal sign followed by a period.”	<font size=7>> </font>
5A [374]	<b><!-- 3/4 -->¾</b>	Special processing: unidentified character	Special processing: (1) Output: <nobr ><!-- equal and divide -->=<a style="position: relative; left: -0.3 em; top: -0.0 em; font-size: 1.2 em; font-weight: normal">:</a></nobr> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes an equal-and-divide sign that may be misinterpreted by your reader as an equal sign followed by a colon.”	Special processing: unidentified character
5B	<b><sup>1</sup>/<sub>8</sub></b>	Special processing: unidentified character	is greater than	<font size=“6”>[</font>
5C	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character
5D	<b><sup>3</sup>/<sub>8</sub></b>	Special processing: unidentified character	is less than	<font size=“6”>]</font>
5E	<b><sup>5</sup>/<sub>8</sub></b>	<nobr>    <b>-</b> <a style="position: relative; left: -0.6 em; top: 0.2 em; font-size: 1.8 em; font-weight: normal">O</a></nobr>	is equivalent to	Special processing: unidentified character
5F [375]	<b><sup>7</sup>/<sub>8</sub></b>	Special processing: unidentified character	<!-- --><!-- -->	<sup>(</sup>
60	Special processing: unidentified character	Special processing: unidentified character	Special processing: (1) Output: <nobr ><!-- approaches the limit -->=<a style="position: relative; left: -0.4 em; top: -0.6 em; font-size: 1.0 em; font-weight: normal">.</a></nobr> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes an approaches-the-limit sign that may be misinterpreted by your reader as an equal sign followed by a period.”	<sub>(</sub>
61	<sup>1</sup>/<sub>1 </sub>	Special processing: unidentified character	<!-- up arrow -->↑	<!-- Sigma -->Σ
62	<!-- 1/2 -->½	<font size=“+1”>•<!-- * --></font>	Special processing: unidentified character	<!-- integral -->∫
63	<sup>3</sup>/<sub>2 </sub>	Special processing: unidentified character	<!-- right arrow -->→	Special processing: unidentified character
64	<sup>5</sup>/<sub>2 </sub>	Special processing: unidentified character	Special processing: unidentified character	<!-- union --><font face="Letter Gothic, Monospaced, FrnkGothITC Bk BT, Franklin Gothic, FrankfurtGothic">U </font>
65	<sup>7</sup>/<sub>2 </sub>	Special processing: unidentified character	<!—down arrow -->↓	<!-- intersection -->∩
66	<sup>9</sup>/<sub>2 </sub>	Special processing: unidentified character	Special processing: unidentified character	Special processing: (1) Output: <!-- is implied by --><a style="font-family: sans-serif">C</a> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes an is-implied-by sign that may be misinterpreted by your reader as a C.”
67	<sup>1</sup>/<sub>3 </sub>	•<!-- -->	<!-- left arrow -->←	implies
68	<sup>2</sup>/<sub>3 </sub>	Special processing: unidentified character	Special processing: unidentified character	Special processing: (1) Output: <nobr ><!-- is nearly implied by --><a style="font-family: sans-serif">C</a><a style="position: relative; left: -0.4 em; top: -0.1 em; font-size: 1.1 em; font-weight: normal">\|</a></nobr> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes an is-nearly-implied-by sign that may be misinterpreted by your reader as a C followed by a vertical pipe.”
69	<sup>3</sup>/<sub>3 </sub>	<sup>a</sup>/c	Special processing: unidentified character	nearly implies
6A	<!-- 3/4 -->¾	Special processing: unidentified character	<!-- down arrow and up arrow -->↓ ↑	)
6B	<sup>5</sup>/<sub>4 </sub>	Special processing: unidentified character	Special processing: unidentified character	[
6C	<sup>7</sup>/<sub>4 </sub>	Special processing: unidentified character	Special processing: unidentified character	]
6D	<sup>9</sup>/<sub>4 </sub>	<i><sup>c</sup>/o</i>	Special processing: unidentified character	<!-- { -->{
6E	<sup>1</sup>/<sub>5 </sub>	Special processing: unidentified character	Special processing: unidentified character	<!-- } -->}
6F [376]	<sup>2</sup>/<sub>5 </sub>	Special processing: unidentified character	Special processing: unidentified character	<
70 [377]	<sup>3</sup>/<sub>5 </sub>	#	Special processing: unidentified character	>
71 [378]	<sup>4</sup>/<sub>5 </sub>	Special processing: unidentified character	Special processing: unidentified character	\|
72 [379]	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character	\|\|
73	<sup>1</sup>/<sub>6 </sub>	Special processing: unidentified character	Special processing: unidentified character	/
74	<sup>2</sup>/<sub>6 </sub>	Special processing: unidentified character	Special processing: unidentified character	<!-- radical -->√
75	<sup>3</sup>/<sub>6 </sub>	<!-- British pounds -->£	Special processing: unidentified character	Special processing: (1) If {HTML font size} is greater than or equal to seven, then output: <nobr><!-- square root --> <sup>2</sup><a style="position: relative; left: -0.4 em; top: 0.3 em; font-size: 1.0 em; font-weight: normal">√</a></nobr> - - - (2) If {HTML font size} is less than seven, then output: <nobr><!-- square root --> <sup><font size="-1" >2</font> </sup><a style="position: relative; left: -0.4 em; top: 0.3 em; font-size: 1.0 em; font-weight: normal">√</a></nobr>
76	<sup>4</sup>/<sub>6 </sub>	Special processing: unidentified character	Special processing: unidentified character	Special processing: (1) If {HTML font size} is greater than or equal to seven, then output: <nobr><!-- cube root --> <sup>3</sup><a style="position: relative; left: -0.4 em; top: 0.3 em; font-size: 1.0 em; font-weight: normal">√</a></nobr> - - - (2) If {HTML font size} is less than seven, then output: <nobr><!-- cube root --> <sup><font size="-1" >3</font> </sup><a style="position: relative; left: -0.4 em; top: 0.3 em; font-size: 1.0 em; font-weight: normal">√</a></nobr>
77	<sup>5</sup>/<sub>6 </sub>	Special processing: unidentified character	Special processing: unidentified character	Special processing: (1) If {HTML font size} is greater than or equal to seven, then output: <nobr><!-- fourth root --> <sup>4</sup><a style="position: relative; left: -0.4 em; top: 0.3 em; font-size: 1.0 em; font-weight: normal">√</a></nobr> - - - (2) If {HTML font size} is less than seven, then output: <nobr><!-- fourth root --> <sup><font size="-1" >4</font> </sup><a style="position: relative; left: -0.4 em; top: 0.3 em; font-size: 1.0 em; font-weight: normal">√</a></nobr>
78	<sup>6</sup>/<sub>6 </sub>	Special processing: unidentified character	Special processing: unidentified character	<sub>[</sub>
79	Special processing: unidentified character	Special processing: (1) Output: <!-- varies as --><a style="position: relative; left: 0.0 em; top: -0.1 em; font-size: 0.8 em; font-weight: normal; letter-spacing: -0.1 em">oc</a> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes a varies-as sign that may be misinterpreted by your reader as: ac”	<!-- right angle --><font face="Letter Gothic, Monospaced, FrnkGothITC Bk BT, Franklin Gothic, FrankfurtGothic">L </font>	<sub>]</sub>
7A [380]	Special processing: unidentified character	<b><i><!-- check -->√</i> </b>	<!-- differential -->∂	<sub>\| </sub>
7B	<sup><s>2</s></sup>	Special processing: unidentified character	Special processing: unidentified character	<!-- { -->{
7C [381]	Special processing: unidentified character	Special processing: unidentified character	\|	Special processing: unidentified character
7D	<sup><s>3</s></sup>	Special processing: unidentified character	Special processing: unidentified character	<!-- } -->~
7E	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character
7F	<sup><font face=“arial, helvetica, geneva”>2</sup>	<sup><!-- R in a circle -->®</sup>	<sup><!-- R in a circle -->®</sup>	<sup><!-- R in a circle -->®</sup>
80 to A9	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character
AA	<sup><s>5</s></sup>	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character
AB	<sub><font face=“arial, helvetica, geneva”>1</sub>	<!-- degrees -->°	<!-- degrees -->°	Special processing: unidentified character
AC	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character
AD	/	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character
AE	<sup><font face=“arial, helvetica, geneva”>5</sup>	<sup><!-- C in a circle -->© </sup>	<sup><!-- C in a circle -->© </sup>	<sup><!-- C in a circle -->© </sup>
AF to BA	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character
BB	<sup><font face=“arial, helvetica, geneva”>0</sup>	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character
BC	<sub><font face=“arial, helvetica, geneva”>3</sub>	<font face=“Letter Gothic, Monospaced, FrnkGothITC Bk BT, Franklin Gothic, FrankfurtGothic”><sup>1 </sup>/<sub>8</sub> </font>	Special processing: unidentified character	Special processing: unidentified character
BD	<sup><s>8</s></sup>	<!-- double dagger -->‡	<!-- double dagger -->‡	Special processing: unidentified character
BE	<sup><s>1</s></sup>	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character
BF	<sup><font face=“arial, helvetica, geneva”>6</sup>	Special processing: unidentified character	<!-- ( ) -->¤	Special processing: unidentified character
C0 to C3	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character
C4	<sub><font face=“arial, helvetica, geneva”>4</sub>	<font face=“Letter Gothic, Monospaced, FrnkGothITC Bk BT, Franklin Gothic, FrankfurtGothic”><sup>1 </sup>/<sub>4</sub> </font>	Special processing: unidentified character	Special processing: unidentified character
C5	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character
C6	<b>/</b>	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character
C7 to C8	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character
C9	<sub><font face=“arial, helvetica, geneva”>2</sub>	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character
CA	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character
CB	<sup><font face=“arial, helvetica, geneva”>9</sup>	<!-- diamond -->♦	Special processing: unidentified character	Special processing: unidentified character
CC to FF	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character	Special processing: unidentified character

(10) If {Grid} equals 8 and

(a) {Typeface} equals 1, then

(1) output: <font face=“Letter Gothic, Monospaced, FrnkGothITC Bk BT, Franklin Gothic, FrankfurtGothic”>

(2) convert the stored text according to the Typeface 1 column

(3) follow the material with: </font>

(b) {Typeface} equals 2, then

(1) output: <font face=“Letter Gothic, Monospaced, FrnkGothITC Bk BT, Franklin Gothic, FrankfurtGothic”><b>

(2) convert the stored text according to the Typeface 2 column

(3) follow the material with: </b></font>

(1) output: <font face=“Letter Gothic, Monospaced, FrnkGothITC Bk BT, Franklin Gothic, FrankfurtGothic” size={HTML font size}><i>

(2) convert the stored text according to the Typeface 3 column

(3) follow the material with: </i></font>

(d) {Typeface} equals 4, then convert the stored text according to the Typeface 4 column.

Grid 8
Hex	Typefaces 1, 2, & 3	Typeface 4
00	Special processing: unidentified character	Special processing: unidentified character
01	<!-- * -->•	Special processing: unidentified character
02 to 05	Special processing: unidentified character	Special processing: unidentified character
06	Special processing: If two Hex06 appear together, replace the pair with: §§<!-- sections --> If a Hex06 appears not in a pair, replace it with: §<!-- section -->	Special processing: unidentified character
07	Special processing: unidentified character	Special processing: unidentified character
08	O	Special processing: unidentified character
09	Special processing: (1) Replace with: (2) Go back to the previous blank space[382],   <td> tag, <p>, <br>, bell-code[383], or EOF[384], and insert after it: <nobr> (3) Go forward to the next blank space[385],   <td> tag, <p>, <br>, bell-code[386], or EOF[387], and insert after it: </nobr> (4) Output: <!-- (5) Again output all of the text between <nobr> and </nobr>, but this time replace the occurrence(s) of with a dash[388] (6) Output: -->	Special processing: (1) Replace with: (2) Go back to the previous blank space[389],   <td> tag, <p>, <br>, bell-code[390], or EOF[391], and insert after it: <nobr> (3) Go forward to the next blank space[392],   <td> tag, <p>, <br>, bell-code[393], or EOF[394], and insert after it: </nobr> (4) Output: <!-- (5) Again output all of the text between <nobr> and </nobr>, but this time replace the occurrence(s) of with a dash[395] (6) Output: -->
0A	<!-- x -->×	Special processing: unidentified character
0B	<!-- cents -->¢	Special processing: (1) if {HTML font size} is greater than or equal to 7, then output: <b>O</b> (2) if {HTML font size} is less than 7, then output: <font size=“+1”><b>O</b></font>
0C	Special processing: If two Hex0C appear together, replace the pair with: <sup>¶¶ </sup><!-- paragraphs --> If a Hex0C appears not in a pair, replace it with: <sup>¶</sup> <!-- paragraph -->	Special processing: unidentified character
0D to 0F	Special processing: unidentified character	Special processing: unidentified character
10	<!-- divided by -->÷	Special processing: unidentified character
11	<nobr><!-- is much less than --><<a style="position: relative; left: -0.2 em; top: -0.1 em; font-size: 0.8 em; font-weight: normal"><</a></nobr>	Special processing: unidentified character
12	<nobr><!-- is much greater than -->><a style="position: relative; left: -0.2 em; top: -0.1 em; font-size: 0.8 em; font-weight: normal">></a></nobr>	Special processing: unidentified character
13	Special processing: (1) Output: <nobr><!-- is nearly equal to -->~<a style="position: relative; left: -0.5 em; top: -0.2 em; font-size: 1.0 em; font-weight: normal">~</a></nobr> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes a nearly-equals sign that may be misinterpreted by your reader as two equal signs.”	Special processing: unidentified character
14	Special processing: (1) Output: <nobr><!-- is approximately equal to -->=<a style="position: relative; left: -0.5 em; top: -0.3 em; font-size: 1.0 em; font-weight: normal">~</a></nobr> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes an is-approximately-equal-to sign that may be misinterpreted by your reader as an equal sign followed by a tilde.”	Special processing: unidentified character
15	Special processing: (1) Output: <nobr><!-- is not less than --><<a style="position: relative; left: -0.4 em; top: -0.2 em; font-size: 1.0 em; font-weight: normal">\|</a></nobr> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes an is-not-less-than sign that may be misinterpreted by your reader as a less-than sign followed by a vertical pipe.”	Special processing: unidentified character
16	Special processing: (1) Output: <nobr><!-- is not greater than -->&#62<a style="position: relative; left: -0.4 em; top: -0.2 em; font-size: 1.0 em; font-weight: normal" >\|</a></nobr> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes an is-not-greater-than sign that may be misinterpreted by your reader as a greater-than sign followed by a vertical pipe.”	Special processing: unidentified character
17	Special processing: (1) Output: <nobr><!-- minus or plus -->+<a style="position: relative; left: -0.5 em; top: -0.5 em; font-size: 1.0 em; font-weight: normal"></a></nobr> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes a minus-or-plus sign that may be misinterpreted by your reader as a minus sign followed by a plus sign.”	Special processing: unidentified character
18 to 1A	Special processing: unidentified character	Special processing: unidentified character
1B	<!-- plus or minus -->±	Special processing: unidentified character
1C to 1D	Special processing: Unidentified character	Special processing: unidentified character
1E	<!-- dagger -->†	Special processing: unidentified character
1F	<sup><!-- C in a circle -->©</sup>	Special processing: unidentified character
20	Special processing: unidentified character	Special processing: unidentified character
21	!	Special processing: unidentified character
22	“	Special processing: unidentified character
23	#	Special processing: unidentified character
24	$	Special processing: unidentified character
25	%	Special processing: unidentified character
26	&	Special processing: unidentified character
27	‘	Special processing: unidentified character
28	(	Special processing: unidentified character
29	)	Special processing: unidentified character
2A	*	Special processing: unidentified character
2B	+	Special processing: unidentified character
2C	,	Special processing: unidentified character
2D	-	Special processing: unidentified character
2E	.	Special processing: unidentified character
2F	/	Special processing: unidentified character
30	0	Special processing: unidentified character
31	1	Special processing: unidentified character
32	2	Special processing: unidentified character
33	3	Special processing: unidentified character
34	4	Special processing: unidentified character
35	5	Special processing: unidentified character
36	6	Special processing: unidentified character
37	7	Special processing: unidentified character
38	8	Special processing: unidentified character
39	9	Special processing: unidentified character
3A	:	Special processing: unidentified character
3B	;	Special processing: unidentified character
3C [396]	<	Special processing: unidentified character
3D	=	Special processing: unidentified character
3E [397]	>	Special processing: unidentified character
3F	?	Special processing: unidentified character
40	@	Special processing: unidentified character
41	A	Special processing: unidentified character
42	B	Special processing: unidentified character
43	C	[Cancergram]
44	D	Special processing: unidentified character
45	E	Special processing: unidentified character
46	F	Special processing: unidentified character
47	G	Special processing: unidentified character
48	H	Special processing: unidentified character
49	I	Special processing: unidentified character
4A	J	Special processing: unidentified character
4B	K	[open key]
4C	L	Special processing: unidentified character
4D	M	Special processing: unidentified character
4E	N	Special processing: unidentified character
4F	O	Special processing: unidentified character
50	P	Special processing: unidentified character
51	Q	Special processing: unidentified character
52	R	Special processing: unidentified character
53	S	[snowflake]
54	T	[steering wheel]
55	U	Special processing: unidentified character
56	V	[floppy disc]
57	W	[grid]
58	X	[computer terminal]
59	Y	[open book]
5A	Z	Special processing: (1) Output: <nobr><!-- target --><a style="font-family: sans-serif">O</a><a style="position: relative; left: -0.5 em; top: -0.0 em; font-size: 1.0 em; font-weight: normal">·</a></nobr> - - - (2) Add the following to the previous <table> tag: summary="Warning to users of assistive technology: this paragraph includes a target sign that may be misinterpreted by your reader as an O followed by a period.”
5B	[	Special processing: unidentified character
5C	Special processing: unidentified character	Special processing: unidentified character
5D	]	Special processing: unidentified character
5E	-	Special processing: unidentified character
5F	Special processing: (1) Store all of the text between the Hex 5F and the previous blank space[398],   <td> tag, <p>, <br>, bell-code[399], or EOF[400], as {hold-1} - - - (2) Store all of the text between Hex 5E and the next blank space[401],   <td> tag, <p>, <br>, bell-code[402], or EOF[403], as {hold-2} - - - (3) Output: <sup></sup>{hold-2} <!-- {hold-1}-{hold-2} -->	Special processing: unidentified character
60	‘	Special processing: unidentified character
61	a	Special processing: unidentified character
62	b	Special processing: unidentified character
63	c	Special processing: unidentified character
64	d	Special processing: unidentified character
65	e	Special processing: unidentified character
66	f	Special processing: (1) if {HTML font size} is greater than or equal to 7, then output: <b><font face=“arial, helvetica, geneva”>federal</font></b> (2) if {HTML font size} is less than 7, then output: <b><font face=“arial, helvetica, geneva” size=“+1”>federal </font></b>
67	g	Special processing: unidentified character
68	h	Special processing: unidentified character
69	i	Special processing: unidentified character
6A	j	Special processing: unidentified character
6B	k	Special processing: unidentified character
6C	l	Special processing: unidentified character
6D	m	Special processing: unidentified character
6E	n	Special processing: unidentified character
6F	o	Special processing: unidentified character
70	p	Special processing: unidentified character
71	q	Special processing: unidentified character
72	r	Special processing: (1) if {HTML font size} is greater than or equal to 7, then output: <b><font face=“arial, helvetica, geneva”>register</font></b> (2) if {HTML font size} is less than 7, then output: <b><font face=“arial, helvetica, geneva” size=“+1”>register </font></b>
73	s	Special processing: unidentified character
74	t	Special processing: unidentified character
75	u	Special processing: unidentified character
76	v	Special processing: unidentified character
77	w	Special processing: unidentified character
78	x	Special processing: unidentified character
79	y	Special processing: unidentified character
7A	z	Special processing: unidentified character
7B	<!-- { -->{	Special processing: unidentified character
7C	<!-- is less than or equal to -->≤	Special processing: unidentified character
7D	<!-- } -->}	Special processing: unidentified character
7E	Special processing: unidentified character	Special processing: unidentified character
7F	<!-- R in a circle -->®	Special processing: unidentified character
80 to A9	Special processing: unidentified character	Special processing: unidentified character
AA	<!-- is greater than or equal to -->≥	Special processing: unidentified character
AB	°	Special processing: unidentified character
AC	‘	Special processing: unidentified character
AD	<!-- is identical with -->≡	Special processing: unidentified character
AE	Special processing: unidentified character	Special processing: unidentified character
AF	<sup><!-- C in a circle -->©</sup>	Special processing: unidentified character
B0 to B9	Special processing: unidentified character	Special processing: unidentified character
BA	<!-- is greater than or equal to -->≥	Special processing: unidentified character
BB	<!-- radical -->√	Special processing: unidentified character
BC	[solid star]	Special processing: unidentified character
BD	<!-- double dagger -->‡	Special processing: unidentified character
BE	<!-- is less than or equal to -->≤	Special processing: unidentified character
BF	<!-- ( ) -->¤	Special processing: (1) if {HTML font size} is greater than or equal to 7, then output: O (2) if {HTML font size} is less than 7, then output: <font size=“+1”>O</font>
C0 to C3	Special processing: unidentified character	Special processing: unidentified character
C4	<!-- in perspective to --><u style="text-decoration: underline">~</u>	Special processing: unidentified character
C5	Special processing: unidentified character	Special processing: unidentified character
C6	<!-- difference -->~	Special processing: unidentified character
C7 to C8	Special processing: unidentified character	Special processing: unidentified character
C9	<!-- infinity -->∞	Special processing: unidentified character
CA	Special processing: unidentified character	Special processing: unidentified character
CB	<!-- is perpendicular with -->⊥	Special processing: unidentified character
CC to FF	Special processing: unidentified character	Special processing: unidentified character

(11) If {Grid} = 1 and {Typeface} = 1, 2, or 3, then output the data through the next bell-c, bell-D[404], bell-F, bell-g, bell-h[405], bell-I, bell-j[406], bell-K, bell-q, bell-Q, bell-R, bell-S, bell-T, or HEX 00.

(12)If step 11 was positive because of a code other than bell-G, bell-K, or bell-T

and

if {original grid} does not equal {Grid} or {original typeface} does not equal {Typeface}

then:

(a) If {Grid} = 1 and {Typeface} = 2, then precede the “follow text with” material[407] with: </b>

(b) If {Grid} = 1 and {Typeface} = 3, then precede the “follow text with” material[408] with: </i>

(c) If {original grid} = 1 and {original typeface} = 2, then precede the “follow text with” material[409] with: <b>

(d) If {original grid} = 1 and {original typeface} = 3, then precede the “follow text with” material[410] with: <i>

(e) If {Grid} = 2 and {Typeface} = 1, then precede the “follow text with” material with: </sup>

(f) If {Grid} = 2 and {Typeface} = 2, then precede the “follow text with” material with: </sub>

(g) If {Grid} = 2 and {Typeface} = 3, then precede the “follow text with” material with: </sup></i>

(h) If {Grid} = 2 and {Typeface} = 4, then precede the “follow text with” material with: </sub></i>

(i) If {original grid} = 2 and {original typeface} = 1, then precede the “follow text with” material with: <sup>

(j) If {original grid} = 2 and {original typeface} = 2, then precede the “follow text with” material with: <sub>

(k) If {original grid} = 2 and {original typeface} = 3, then precede the “follow text with” material with: <i><sup>

(l) If {original grid} = 2 and {original typeface} = 4, then precede the “follow text with” material with: <i><sub>

(m) If {Grid} = 4 and {Typeface} = 1, then precede the “follow text with” material with: <font face=“ arial, helvetica, geneva”>

(n) If {Grid} = 4 and {Typeface} = 2, then precede the “follow text with” material with: <font face=“ arial, helvetica, geneva”><b>

(o) If {Grid} = 4 and {Typeface} = 3, then precede the “follow text with” material with: <font face=“ arial, helvetica, geneva”><i>

(p) If {original grid} = 4 and {original typeface} = 1, then precede the “follow text with” material with: </font>

(q) If {original grid} = 4 and {original typeface} = 2, then precede the “follow text with” material with: </b></font>

(r) If {original grid} = 4 and {original typeface} = 3, then precede the “follow text with” material with: </i></font>

Processing Unidentified Characters

(1) Add to {error file}: {TITLE NUMBER} USC{appendix}{SECTION NUMBER}{long subsection} ({text field}) – unidentified character – grid {grid} typeface {new typeface} hex {hex value of unidentified character}

(2) Output: UNIDENTIFIED CHARACTER

Bell-I

The bell-I is followed by two numerics. That two numeric argument, plus the value of the current {format}[411] and whether or not this is part of a table[412] determines the function of an I-code. If an I-code appears outside of a bell-c table, use the chart below associated with the most recent format number, then find the line associated with the two-digit bell-I value, store the values for {bell-I}, {Font size in points}, {HTML font size}, {Top leading}, {Bottom leading}, {Typeface}, {Grid}, {FOTP}, {primary indent}, {secondary indent}, and {line type} and

(1) (a) Set {old leading} to the value of {leading}.

(b) If {Top leading} – {font size in points} > 0, then add the result to {leading}[413].

(2) If {leading} < 0, then set {leading} to zero.

(3) Recalculate {leading} by multiplying it by 0.8 and rounding the product off to the nearest whole number.

(4) For every occurrence of {leading}, insert in the {leading file}: <tr></tr>

(4A) Set {original typeface} to the value of {Typeface}.

(4B) Set {original grid} to the value of {Grid}.

(4C) Set {number of grid changes} and {number of typeface changes} to zero.

(4D) Set {footnote switch} to zero.

(4E) [reserved]

(4F) Process any “special processing” instructions dealing with {text field}, {SECTION NUMBER}, {subsection primary indent}, or {USCDoc}. Also, if the “special processing” instructions direct that text not be output (e.g., locator-28 in format 5800), then follow all of the special processing instructions for the locator and execute I-code instructions 5, 6, and 7 to 11 (in each case writing to the file or variable designated in the special processing instructions instead of outputting the data).

(5) Replace the I-code with the HTML coding shown in the table in the “Precede text with” column.

(5A) [Reserved]

(5B) If

· {TITLE NUMBER} is greater than zero,

· {text field} equals “STATUTE”,

· {FOTP} equals either blank or one, and

· the next non-blank character (after processing all G-codes, K-codes, and T-codes) is an open paren,

then:

(a) If {primary indent} is greater than {greatest indent}, then

(a) Blank out {subsection}_{N}and {previous subsection}_{N}for all values of {N} from {greatest indent}+1 to {primary indent}

(ii) move the value of {primary indent} to {greatest indent}

(iii) go to step (c).

(b) If {primary indent} is less than {greatest indent}, then blank out {subsection}_{N} and {previous subsection}_{N}for all values of {N} from {primary indent}+1 to {greatest indent}.

(c) Set {subsection anchor} to: on

(d) Store the value of {subsection}_{{primary indent}} as {previous subsection}_{{primary
indent}}.

(e) Store the data following the “(”, up to (but not including) the next “)”, as {subsection}_{{primary indent}}.

(f) If {previous subsection}_{{primary indent}} and {subsection}_{{primary indent}} are not one of the pairs shown in the following table, then add the following to the {error file}: {TITLE NUMBER} USC{appendix}{SECTION NUMBER}{long subsection} ({text field}) – warning – subsection ({previous subsection}_{{primary indent}}) is followed by subsection ({subsection}_{{primary indent}})

{previous subsection}_{{primary indent}}	{subsection}_{{primary indent}}

{previous subsection}_{{primary indent}}	{previous subsection}_{{primary indent}} + 1
	1
	a
	A
	i
	I
Z	AA
AA	BB
BB	CC
CC	DD
DD	EE
EE	FF
FF	GG
GG	HH
HH	II
II	III
II	JJ
JJ	KK
KK	LL
LL	MM
MM	NN
NN	OO
OO	PP
PP	QQ
QQ	RR
RR	SS
SS	TT
TT	UU
UU	VV
VV	WW
WW	XX
XX	YY
YY	ZZ
ZZ	AAA
AAA	BBB
BBB	CCC
CCC	DDD
DDD	EEE
EEE	FFF
FFF	GGG
GGG	HHH
HHH	III
III	IV
III	JJJ
JJJ	KKK
KKK	LLL
LLL	MMM
MMM	NNN
NNN	OOO
OOO	PPP
PPP	QQQ
QQQ	RRR
RRR	SSS
SSS	TTT
TTT	UUU
UUU	VVV
VVV	WWW
WWW	XXX
XXX	YYY
YYY	ZZZ
ZZZ	AAAA
z	aa
aa	bb
bb	cc
cc	dd
dd	ee
ee	ff
ff	gg
gg	hh
hh	ii
ii	iii
ii	jj
jj	kk
kk	ll
ll	mm
mm	nn
nn	oo
oo	pp
pp	qq
qq	rr
rr	ss
ss	tt
tt	uu
uu	vv
vv	ww
ww	xx
xx	yy
yy	zz
zz	aaa
aaa	bbb
bbb	ccc [414]
ccc	ddd
ddd	eee
eee	fff
fff	ggg
ggg	hhh
hhh	iii
iii	iv
iii	jjj
jjj	kkk
kkk	lll
lll	mmm
mmm	nnn
nnn	ooo
ooo	ppp
ppp	qqq
qqq	rrr
rrr	sss
sss	ttt
ttt	uuu
uuu	vvv
vvv	www
www	xxx
xxx	yyy
yyy	zzz
zzz	aaaa
I	II
IV	V
V	VI
VI	VII
VII	VIII
VIII	IX
IX	X
X	XI
XI	XII
XII	XIII
XIII	XIV
XIV	XV
XV	XVI
XVI	XVII
XVII	XVIII
XVIII	XIX
XIX	XX
XX	XXI
i	ii
iv	v
v	vi
vi	vii
vii	viii
viii	ix
ix	x
x	xi
xi	xii
xii	xiii
xiii	xiv
xiv	xv
xv	xvi
xvi	xvii
xvii	xviii
xviii	xix
xix	xx
xx	xxi

(g) blank out the file {long subsection}.

(h) copy into {long subsection} all of the non-blank values of {subsection}_{N}where {N} equals all values from zero to {greatest indent}. Insert an open paren in front of each addition to {long subsection} and insert a close paren after each addition to {long subsection}.[415]

(i) Output: <a name=“{long subsection}” id=“{long subsection}” onMouseOver=“window.status=‘{TITLE NUMBER} USC{appendix}{SECTION NUMBER}{long subsection}’; return true”>

(j) If {subsection}_{{primary indent}} is larger than six characters, add to {error file}: {TITLE NUMBER} USC{appendix}{SECTION NUMBER}{long subsection} ({text field}) – warning – subsection designation exceeds six characters – {subsection}_{{primary
indent}}.

(k) If the next non-blank character (after the close paren) is an open paren[416], then

(1) increment {primary indent} by {Font size in points}

(2) output: </a>

(3) go back to step (a).

(l) Set {subsection primary indent} to the value of {primary indent}[417]

(m) set {subsection secondary indent}_{{primary indent}} to the value of {secondary indent}.

(5C) If

· {TITLE NUMBER} is greater than zero,

· {text field} is “STATUTE”,

· {FOTP} is either blank or one,

· {primary indent} is greater than or equal to {subsection primary indent}[418] or {line type} is “C”, and

· the first non-blank character after the bell-I (after processing all G-codes, K-codes, and T-codes) is not an open paren, then[419]

(a) output: <a onMouseOver=“window.status=’{TITLE NUMBER} USC{appendix}{SECTION NUMBER}{long subsection}’; return true”>

(b) set {subsection anchor} to: on

(5D) If

· {TITLE NUMBER} is greater than zero,

· {text field} is “STATUTE”,

· {FOTP} is either blank or one,

· {primary indent} is less than {subsection primary indent}[420], and

· the first non-blank character after the bell-I (after processing all G-codes, K-codes, and T-codes) is not an open paren, then[421]

(a) starting with {N} = {primary indent}, and decrementing by one for each unsuccessful test, find the first instance where {primary indent} = {subsection secondary indent}_{N}. If {primary indent} ≠ = {subsection secondary indent}_{N} for any value of {N} greater than –1, then

(i) add to the {error file}: {TITLE NUMBER} USC{appendix}{SECTION NUMBER} – unable to positively identify subsection designation following subsection {long subsection}

(ii) go to instruction 6 .

(b) blank out {subsection}_{X} and {previous subsection}_{X}for all values of {X} from {N} + 1 to {greatest indent}.

(c) blank out the file {long subsection}.

(d) copy into {long subsection} all of the non-blank values of {subsection}_{N}where {N} equals all values from zero to {greatest indent}. Insert an open paren in front of each addition to {long subsection} and insert a close paren after each addition to {long subsection}.[422]

(e) output: <a onMouseOver=“window.status=’{TITLE NUMBER} USC{appendix}{SECTION NUMBER}{long subsection}’; return true”>

(f) set {subsection anchor} to: on

(g) Set {subsection primary indent} to the value of {primary indent}[423]

(6) Insert the text that followed the I-code, (up to the next bell[424]), while carrying out any remaining special processing instructions not related to FOTP processing or the “Follow text with” material.

(6A) If {subsection anchor}[425] is set to “on”, then

(a) output: </a>

(b) set {subsection anchor} to: off

(7) Insert the HTML coding shown in the “Follow text with” column and carry out any special processing instructions related to FOTP processing or the “Follow text with” material.

(7A) If {bell-Y} = 1, then (in the <table> tag output in instruction #7) change the “border=” value to “1” and change the “frame=” value to “lhs”.

(8) Set {leading} to zero.

(9) If ({bottom leading} – {font size in points}) > 0, then add the result to {leading}.

(10)Clear out the contents of the {Leading file}.

(11)If {footnote switch} is greater than zero, then set {leading} to the value of {old leading}.

(12) If {FOTP} is blank, then set {FOTP row width in pixels} to zero.

Formats 5800 to 5803
%I	Precede text with	Follow text with	Font size in points	HTML font size	Top lead- ing	Bottom leading	Type-face	G r i d	F O T P	PI[426]	SI [427]	LT [428]	Special processing	Example at
01	<!—odd pages running ear:	-->	7	2	0	0	1	1		0	0	C		26 U.S.C. app. (T.C.R.) app. I
02	<!—even pages running ear:	-->	8	3	9	0	1	1		56	48	J
03			3	1	10	16	1	1		189	189	L	Delete all text through the next bell	page prec. 1 U.S.C.
04	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none"> {Leading file}<tr><td width=“120”> </td><td width=“480” align="center"><font size=“5”><b>	</b></font></td></tr> </table>	10	5	11	0	2	1		0	0	C		1 U.S.C. prec. § 1
05	<table width="100%" border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none">{Leading file}<tr><td align="center"><font size=“3”><i>	</i></font></td></tr> </table>	8	3	9	0	3	1		0	0	C	If {text field} is “HEAD”, then (a) set {text field} to: MISC1 (b) insert the following before the “Precede text with” material: <!--plsfield: MISC1-->	1 U.S.C. prec. § 1
06			8	3	0	0	1	1		0	0	C	Do not output this material. Instead, discard all of the text up tp and including the em-dash (HEX FF) and store the remainder as {RUNNING HEAD}.	5 U.S.C. prec. pt. I
07	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="rows">{Leading file}<tr><td width=“120”> </td><td width=“48” align=“left” valign="top"><font size=“3”><b> <!-- -->	</b></font></td>	8	3	9	0	2	1	1	0	8	L	FOTP processing	5 U.S.C. prec. pt. I
08	<td width=“14”> </td><td width=“308” align=“justify” valign="top"><div align="justify"><font size=“3”><b>         <!-- -->	</b></font></div></td>	8	3	9	0	2	1	2	28	36	J	FOTP processing	5 U.S.C. prec. pt. I
09	<td width=“14”> </td><td width=“96” align="right" valign="bottom"><font size=“3”><b>	</b></font></td>	8	3	9	0	2	1	3	177	177	R	FOTP processing	5 U.S.C. prec. pt. I
10	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none"> {Leading file}<tr><td width=“120”>  </td><td align=“justify” width=“480”> <div align="justify"><font size=“3”>	</font></div></td></tr> </table>ÃÃ	8	3	9	0	1	1		0	0	J		23 U.S.C. § 127(a)
11	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none"> {Leading file}<tr><td width=“120”>  </td><td align=“justify” width=“480”> <div align="justify"><font size=“3” >    <!-- -->	</font></div></td></tr> </table>ÃÃ	8	3	9	0	1	1		8	0	J		One of the largest paragraphs associated with locator-11 can be found at 12 U.S.C. § 24 (Seventh).
12	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none"> {Leading file}<tr><td width=“134”>  </td><td align=“justify” width=“466”> <div align="justify"><font size=“3” >    <!-- -->	</font></div></td></tr> </table>ÃÃ	8	3	9	0	1	1		16	8	J		2 U.S.C. § 60a-2(a)(1)
13	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none"> {Leading file}<tr><td width=“148”>  </td><td align=“justify” width=“452”> <div align="justify"><font size=“3” >    <!-- -->	</font></div></td></tr> </table>ÃÃ	8	3	9	0	1	1		24	16	J		2 U.S.C. § 60a-2(a)(1)(A)
14	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none"> {Leading file}<tr><td width=“162”>  </td><td align=“justify” width=“438”> <div align="justify"><font size=“3” >    <!-- -->	</font></div></td></tr> </table>ÃÃ	8	3	9	0	1	1		32	24	J		42 U.S.C. § 300x-7(a) (4)(A)(i)
15	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none"> {Leading file}<tr><td width=“120”>  </td><td align=“justify” width=“480”> <div align="justify"><font size=“3”> <!-- -->	</font></div></td></tr> </table>ÃÃ	8	3	9	0	1	1		0	8	J		28 U.S.C. app. (Fed. R. Civ. P.) form 34 [429]
16	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none"> {Leading file}<tr><td width=“176”>  </td><td align=“justify” width=“424”> <div align="justify"><font size=“3” >    <!-- -->	</font></div></td></tr> </table>ÃÃ	8	3	9	0	1	1		40	32	J		45 U.S.C. § 358(a)(1) (B)(ii)
17	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none"> {Leading file}<tr><td width=“134”>  </td><td align=“justify” width=“466”> <div align="justify"><font size=“3”>	</font></div></td></tr> </table>ÃÃ	8	3	9	0	1	1		8	8	J		2 U.S.C. § 60a-2(a)(1)(B)
18	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none"> {Leading file}<tr><td width=“148”>  </td><td align=“justify” width=“452”> <div align="justify"><font size=“3”><b> <!-- -->	</b></font></div></td></tr></table>ÃÃ	8	3	12	12	2	1		16	32	J		2 U.S.C. § 60l(a)(2)(A)
19	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none"> {Leading file}<tr><td width=“120”>  </td><td align=“justify” width=“480”> <div align="justify"><font size=“3”><b> <!-- -->	</b></div></font></td></tr></table>ÃÃ	8	3	12	12	2	1		0	15	J		42 U.S.C. § 300x-7(a)
20[430]	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none">{Leading file}<tr><td width=“120”> </td><td width=“72” align=“justify” valign="top"><div align="justify"><font size=“2”>	</font></div></td>	7	2	8	0	1	1	1	0	0	J	FOTP processing	28 U.S.C. § 1470 note (Rules of Procedure of the Judicial Panel on Multidistrict Litigation)
21	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none"> {Leading file}<tr><td width=“120”>  </td><td align=“justify” width=“480”> <div align="justify"><font size=“2” >    <!-- -->	</font></div></td></tr> </table>	7	2	8	0	1	1		7	0	J		4 U.S.C. § 1 note (Ex. Ord. No. 10798, § 21)
22	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none"> {Leading file}<tr><td width=“132”>  </td><td align=“justify” width=“468”> <div align="justify"><font size=“2” >    <!-- -->	</font></div></td></tr> </table>	7	2	8	0	1	1		14	7	J		2 U.S.C. § 60a-2 note (Amend-ments)
23	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none"> {Leading file}<tr><td width=“144”>  </td><td align=“justify” width=“456”> <div align="justify"><font size=“2” >    <!-- -->	</font></div></td></tr> </table>	7	2	8	0	1	1		21	14	J		5 U.S.C. § 301 note (Improve-ments in Identi-fication-Related Documents)
24	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none">{Leading file}<tr><td width=“156”> </td><td align=“justify” width=“444”> <div align="justify"><font size=“2” >    <!-- -->	</font></div></td></tr> </table>	7	2	8	0	1	1		28	21	J		2 U.S.C. § 621 note (Financial Safety and Soundness of Government-sponsored Enterprises)
25	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none">{Leading file}<tr><td width=“120”> </td><td align=“justify” width=“480”> <div align="justify"><font size=“2”> <!-- -->	</font><div></td></tr> </table>	7	2	8	0	1	1		0	7	J		3 U.S.C. ch. 2 note (Reorg. Plan No. 1 of 1997)
26	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none"> {Leading file}<tr><td width=“120”>  </td><td align=“justify” width=“480”> <div align="justify"><font size=“2”> <!-- -->	</font></dir></td></tr> </table>	7	2	8	0	1	1		0	14	J		2 U.S.C. § 57 note (Committee Ord. No. 30)
27	<table width=“588” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none"> {Leading file}<tr><td width=“120”>  </td><td width=“468” align="right"><font size=“2”>	</font></td></tr> </table>	7	2	10	0	4	1		0	0	R	Caps and small caps	20 U.S.C. § 60a-1 note (Order of the President Pro Tempore of the United States Senate, December 12, 1999, § 11)
28	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="none" rules="none"> {Leading file}<tr><td width=“120”>  </td><td width=“480”>{footnote divider file}<div align=“justify”><font size=“1”>   <!-- -->	</font></div></td></tr> </table>	6	1	8	0	1	1		6	0	J	(1) if the {footnote file} is not empty, then set the {leading file} and the {footnote divider file} to a blank. - - - (2) Increment {footnote switch} by one. - - - (3) Do not output this material. Add it, instead, to the {footnote file} for use with document breaks (i.e., locator 80 (in formats 5800 to 5803) and bell-R)	42 U.S.C. § 7412(a)(11), (b)(3)(A)
29	<td width=“9”> </td><td align="right" valign="bottom" width=“231”><font size=“1”>	</font></td>	6	1	7	0	1	1	2	0	0	R	FOTP processing	5 U.S.C. prec. pt. I
30	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none"> {Leading file}<tr><td width=“144”>  </td><td align=“justify” width=“456”> <div align="justify"><font size=“2”> <!-- -->	</font></div></td></tr> </table>	7	2	8	0	1	1		14	21	J		5 U.S.C. § 101 note (Cross References)
31	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none"> {Leading file}<tr><td width=“132”>  </td><td align=“justify” width=“468”> <div align="justify"><font size=“2”>	</font></div></td></tr> </table>	7	2	8	0	1	1		7	7	J		5 U.S.C. § 6101 note (Federal Employees Flexible and Compressed Work Schedules, § 103(c)(1) (A))
32	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none"> {Leading file}<tr><td width=“148”>  </td><td align=“justify” width=“452”> <div align="justify"><font size=“3”>	</font></div></td></tr> </table>ÃÃ	8	3	9	0	1	1		16	16	J		5 U.S.C. § 7103(a)(16) (B)
33	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none"> {Leading file}<tr><td width=“120”>  </td><td align=“justify” width=“480”> <div align="justify"><font size=“2”>	</font></div></td></tr> </table>	7	2	8	0	1	1		0	0	J		2 U.S.C. § 60a-2 note (Amend-ments)
34	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none"> {Leading file}<tr><td width=“132”>  </td><td align=“justify” width=“468”> <div align="justify"><font size=“2”> <!-- -->	</font></div></td></tr> </table>	7	2	8	0	1	1		7	14	J		5 U.S.C. app. (Reorg. Plan No. 3 of 1967 (Message of the President))
35	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none"> {Leading file}<tr><td width=“156”>  </td><td align=“justify” width=“444”> <div align="justify"><font size=“2”> <!-- -->	</font></div></td></tr> </table>	7	2	8	0	1	1		21	28	J		2 U.S.C. § 60a note (Cod-ification)
36	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none"> {Leading file}<tr><td width=“120”>  </td><td align=“justify” width=“480”> <div align="justify"><font size=“2”> <!-- -->	</font></div></td></tr> </table>	7	2	8	0	1	1		0	28	J		2 U.S.C. § 60a note (Cod-ification)
37	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="rows"> {Leading file}<tr><td width=“120”>  </td><td valign="top" align=“left” width=“240”><font size=“2”>	</font></td>	7	2	8	0	1	1	1	0	0	L	FOTP processing	10 U.S.C. § 522
38	<td width=“12”> </td><td valign="bottom" align="right" width=“228”><font size=“2”>	</font></td>	7	2	8	0	1	1	2	0	0	R	(7) FOTP processing - - - (2) Add to {error file}: {TITLE NUMBER} USC{appendix} {SECTION NUMBER}{long subsection} ({text field}) – warning – improper use of locator-38 (format {format}) – LRC documentation states that this locator is not to be used in data.
39			14	7	16	0	2	1		0	0	C	Delete all text up to the next bell.	Page prec. 1 U.S.C.
40	<td width=“12”> </td><td width=“396” align="justify" valign="bottom"><div align="justify"><font size=“2” > <!-- -->	</font></div></td>	7	2	8	0	1	1	2	54	61	J	FOTP processing	16 U.S.C. ch. 1 (prec. § 1)
41	<td width=“12”> </td><td width=“300” align="justify" valign="bottom"><div align="justify"><font size=“2” > <!-- -->	</font></div></td>	7	2	9	0	1	1	2	14	21	J	(1) Add to {error file}: {TITLE NUMBER} USC{appendix} {SECTION NUMBER}{long subsection} ({text field}) – warning – verify implementation of format {format}, bell-I41 - - - (2) FOTP processing
42	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none">{Leading file}<tr><td width=“120”> </td><td width=“480” align=“justify”><div align="justify"><font size=“3”><i>     <!-- -->	</i></font></div></td></tr></table>ÃÃ	8	3	9	0	3	1		8	0	J		16 U.S.C. § 3631 note (Amend-ment of Section)
43	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none">{Leading file}<tr><td width=“120”> </td><td align=“justify” width=“480”><div align="justify"><font size=“3”><I>	</i></font></div></td></tr></table>ÃÃ	8	3	9	0	3	1		0	0	J	Add to {error file}: {TITLE NUMBER} USC{appendix} {SECTION NUMBER}{long subsection} ({text field}) –warning – verify implementation of format {format}, bell-I43
44	<table width="600" border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none">{Leading file}<tr><td width=“120”> </td><td align=“justify” width=“480”><div align="justify"><font size=“3”><i>	</i></font></div></td></tr></table>ÃÃ	8	3	9	0	3	1		0	0	J		34 U.S.C.
45	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="rows">{Leading file}<tr><td width=“120”> </td><td width=“142” valign="top" align=“right”><font size=“2”>	<font></td>	7	2	8	0	1	1	1	0	0	R	FOTP processing	7 U.S.C. ch. 31A (prec. § 950aaa)
46	<td width=“12”> </td><td width=“396” align= justify” valign="top"><div align="justify"><font size=“2”> <!-- -->	</font></div></td>	7	2	8	0	1	1	2	36	43	J	FOTP processing	5 U.S.C. ch. 1 (prec. § 101)
47	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none"> {Leading file}<tr><td width=“120”>  </td><td align=“right” width=“480”><font size=“2” >    <!-- -->	</font></td>	7	2	12	0	1	1		0	0	R	Add to {error file}: {TITLE NUMBER} USC{appendix} {SECTION NUMBER}{long subsection} ({text field}) – warning – verify implementation of format {format}, bell-I47
48	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none">{Leading file}<tr><td width=“120”> </td><td width=“105” valign="top" align=“right”><font size=“2”>	</font></td>	7	2	8	0	1	1	1	0	0	R	FOTP processing	1 U.S.C. ch. 3 (prec. § 201)
49	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none"> {Leading file}<tr><td width=“148”>  </td><td width=“452” align=“justify”> <div align="justify"><font size=“3”><i> <!-- -->	</i></font></div></td> </tr></table>ÃÃ	8	3	12	12	1	1		16	32	J		Constitution (signatures)[431]
50	<td width=“12”> </td><td width=“326” align=“justify” valign="bottom"><div align="justify"> <!-- -->	</div></td></tr></table>	7	2	8	0	1	1	2	87	94	J		7 U.S.C. ch. 31A (prec. § 950aaa)
51	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none"> {Leading file}<tr><td width=“120”>  </td><td width=“480” align=“center”><font size=“5”>	</font></td></tr> </table>	10	5	20	18	1	1		0	0	C	Add to {error file}: {TITLE NUMBER} USC{appendix} {SECTION NUMBER}{long subsection} ({text field}) – warning – verify implementation of format {format}, bell-I51
52	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none"> {Leading file}<tr><td width=“120”>  </td><td width=“480” align="center" valign="top"><font size=“5”><b>	</b></font></td>	10	5	20	15	2	1	1	0	0	C	FOTP processing	5 U.S.C. pt. I (prec. § 101)
53 [432]	<!--plsfield:SOURCE--><table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none">{Leading file}<tr><td width=“120”> </td><td width=“480” align=“justify”><div align="justify"><font size=“3”>	</font></div></td></tr> </table>	8	3	13	0	1	1		0	0	J	(1)(a) If {text field} equals “STATAMEND”, “MISC1”, “REFTEXT”, “MISC2”, “COD”, “MISC3”, “CHANGE”, “MISC4”, “TRANS”, “MISC5”, “EXEC”, “MISC6”, “CROSS”, “MISC7”, “SECREF”, or “MISC8”, then add to {error file}: {TITLE NUMBER} USC{appendix}{SECTION NUMBER} – SOURCE occurs after {text field} (b) Set value of {text field} to: SOURCE - - - (2) Set {long subsection} to blanks	One of the largest source credits associated with locator-53 can be found at 5 U.S.C. § 5315.
54	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none"> {Leading file}<tr><td width=“120”>  </td><td width=“480” align=“center”><font size=“5”>	</font></td></tr> </table>	10	5	18	14	4	1		0	0	C	(1) Caps and small caps - - - (2) Add to {error file}: {TITLE NUMBER} USC{appendix} {SECTION NUMBER}{long subsection} ({text field}) – warning – verify implementation of format {format}, bell-I54
55	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none"> {Leading file}<tr><td align=“justify” width=“120”>  </td><td width=“480”><div align="justify"><font size=“1”>     <!-- -->	</font></div></td></tr> </table>	6	1	7	0	1	1		6	0	J		Declaration of Independ-ence (note following signatures)
56	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none"> {Leading file}<tr><td width=“148”>  </td><td align=“justify” width=“452”> <div align="justify"><font size=“3”> <!-- -->	</font></div></td></tr> </table>ÃÃ	8	3	9	0	1	1		16	32	J		7 U.S.C. § 1635j(a)(1) (C)(ii)(V)
57	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none"> {Leading file}<tr><td width=“134”>  </td><td align=“justify” width=“466”> <div align="justify"><font size=“3”>  #160;  <i>	</i></font></div></td></tr></table>ÃÃ	8	3	9	0	3	1		16	8	J		2 U.S.C. § 434 note (Amendment of Subsection (a)(11))
58	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none"> {Leading file}<tr><td width=“120”>  </td><td align=“justify” width=“480”> <div align="justify"><font size=“3”><i>	</i></font></div></td></tr></table>ÃÃ	8	3	9	0	3	1		8	8	J		26 U.S.C. § 402 note (Amendment of Section)
59	<td width=“12”> </td><td valign="bottom" width=“363” align=“justify”><div align="justify"><font size=“2”> <!-- -->	</font></div></td>	7	2	8	0	1	1	2	65	72	J	FOTP processing	1 U.S.C. ch. 3 (prec. § 201)
60	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none"> {Leading file}<tr><td width=“120”>  </td><td width=“161” valign="top" align=“right”><font size=“2”>	</font></td>	7	2	8	0	1	1	1	0	0	R	FOTP processing	28 U.S.C. app. (Fed. R. Civ. P) (prec. rule 1)[433]
61	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none"> {Leading file}<tr><td width=“120”>  </td><td width=“480” align=“center”><font size=“1”>	</font></td></tr> </table>	6	1	9	9	1	1		0	0	C		5 U.S.C. § 5332 note (Sched. 8, pt. II)
62	<table width=“558” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none"> {Leading file}<tr><td width=“120”>  </td><td width=“438” align=“right”><font size=“3”>	</font></td></tr> </table>ÃÃ	8	3	8	8	4	1		0	0	R	Caps and small caps	28 U.S.C. app. (Fed. R. Civ. P.) form 1 [434]
63	<table width=“586” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none"> {Leading file}<tr><td width=“120”>  </td><td width=“466” align=“right”><font size=“3”>	</font></td></tr> </table>ÃÃ	8	3	12	12	4	1		0	0	R	Caps and small caps	28 U.S.C. § 1746(1)
64	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none"> {Leading file}<tr><td width=“148”>  </td><td align=“justify” width=“452”> <div align="justify"><font size=“3”>     <i>	</i></font></div></td></tr></table>ÃÃ	8	3	9	0	3	1		24	16	J		12 U.S.C. § 1813 note (Amendment of Section)
65	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none"> {Leading file}<tr><td width=“148”>  </td><td align=“justify” width=“452”> <div align="justify"><font size=“3”><i>	</i></font></div></td></tr></table>ÃÃ	8	3	9	0	3	1		16	16	J	Add to {error file}: {TITLE NUMBER} USC{appendix} {SECTION NUMBER}{long subsection} ({text field}) – warning – verify implementation of format {format}, bell-I65
66	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none"> {Leading file}<tr><td width=“148”>  </td><td align=“justify” width=“452”> <div align="justify"><font size=“3”> <!-- -->	</font></div></td></tr> </table>ÃÃ	8	3	9	0	1	1		16	24	J		5 U.S.C. § 101
67	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none"> {Leading file}<tr><td width=“134”>  </td><td align=“justify” width=“466”> <div align="justify"><font size=“3”><i> <!-- -->	</i></font></div></td></tr></table>ÃÃ	8	3	12	12	3	1		8	24	J		12 U.S.C. § 1828 note (Enactment of Subsection (t))
68	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none"> {Leading file}<tr><td width=“120”>  </td><td align=“justify” width=“480”> <div align="justify"><font size=“3”><i> <!-- -->	</i></font></div></td></tr></table>ÃÃ	8	3	12	12	3	1		0	16	J		7 U.S.C. § 2020 note (Enactment of Subsection (r))
69	<td width=“12”> </td><td align=“justify” valign="bottom" width=“308”> <div align="justify"><font size=“2”> <!-- -->	</font></div></td>	7	2	8	0	1	1	2	98	105	J	FOTP processing	18 U.S.C. app. (Fed. R. Crim. P.) Table of Contents
70	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="rows"> {Leading file}<tr><td width=“120”>  </td><td width=“240” align=“left” valign="top"><font size=“1”>	</font></td>	6	1	7	0	1	1	1	0	0	L	FOTP processing	5 U.S.C. prec. pt. I
71	{plsfield tag}<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none"> {Leading file}<tr><td width=“120”>  </td><td width=“480” align=“center”><font size=“2”><b>	</b></font></td></tr> </table>	7	2	14	12	1	1		0	0	C	(1) If {text field} equals “MISC1”, “MISC2”, “MISC3”, “MISC4”, “MISC5”, “MISC6”, “MISC7”, or “MISC8”, then set {plsfield tag} to a blank. - - - (2) If {text field} equals “HEAD”, “STATUTE”, “SOURCE”, or “STATAMEND”, then: (a) set {text field} to: MISC1 (b) set {plsfield tag} to: <!--plsfield:MISC1--> - - - (3) If {text field} equals “REFTEXT”, then (a) set {text field} to: MISC2 (b) set {plsfield tag} to: <!--plsfield:MISC2--> - - - (4) If {text field} equals “COD”, then (a) set {text field} to: MISC3 (b) set {plsfield tag} to: <!--plsfield:MISC3--> - - - (5) If {text field} equals “CHANGE”, then (a) set {text field} to: MISC4 (b) set {plsfield tag} to: <!--plsfield:MISC4--> - - - (6) If {text field} equals “TRANS”, then (a) set {text field} to: MISC5 (b) set {plsfield tag} to: <!--plsfield:MISC5--> - - - (7) If {text field} equals “EXEC”, then (a) set {text field} to: MISC6 (b) set {plsfield tag} to: <!--plsfield:MISC6--> - - - (8) If {text field} equals “CROSS”, then (a) set {text field} to: MISC7 (b) set {plsfield tag} to: <!--plsfield:MISC7--> - - - (9) If {text field} equals “SECREF”, then (a) set {text field} to: MISC8 (b) set {plsfield tag} to: <!--plsfield:MISC8--> - - - (10) Caps and small caps. - - - (11) Set {long subsection} to a blank.	40 U.S.C. § 71b note (Reorg. Plan No. 5 of 1966) 15 U.S.C. ch. 14 (prec. § 601) note (Reorg. Plan No. 1 of 1957) 43 U.S.C. § 1451 (Reorg. Plan No. 3 of 1950)
72	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none"> {Leading file}<tr><td width=“168”>  </td><td align=“justify” width=“432”> <div align="justify"><font size=“3”><b> <!-- -->	</b></font></div></td></tr></table>ÃÃ	8	3	12	12	2	1		32	48	J		7 U.S.C. § 935(c)(2)(C)(ii)(I)
73 [435]	{plsfield tag}<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none">{Leading file}<tr><td width=“120”> </td><td width=“480”><center><font size=“2”>	</font></center></td> </tr></table>	7	2	14	12	4	1		0	0	C	(0.1) Set {plsfield tag} to: <!--plsfield:SECREF--> - - - (0.2) If the value of {text field} is “SECREF”, then set {plsfield tag} to a blank. - - - (1) (a) If {text field} equals “MISC8”, then add to {error file}: {TITLE NUMBER} USC{appendix} {SECTION NUMBER} – SECREF occurs after MISC8 (b) Set value of {text field} to: SECREF - - - (2) Caps and small caps - - - (3) Set {long subsection} to blanks.	1 U.S.C. § 1 note (Section Referred to in Other Sections) 2 U.S.C. § 900 note (Section Referred to in Other Sections)
74 [436]	ÃÃ{plsfield tag}<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none">{Leading file}<tr><td width=“120”> </td><td width=“480”><center><font size=“2”>	</font></center></td> </tr></table>	7	2	14	12	4	1		0	0	C	(1) If {text field} equals “MISC1”, ”MISC2”, “MISC3”, “MISC4”, “MISC5”, “MISC6”, “MISC7”, or “MISC8”, then set {plsfield tag} to a blank. - - - (1A) If {text field} equals “HEAD”, “STATUTE”, “SOURCE”, or “STATAMEND”, then: (a) set {text field} to: MISC1 (b) set {plsfield tag} to: <!--plsfield:MISC1--> - - - (1B) If {text field} equals “REFTEXT”, then (a) set {text field} to: MISC2 (b) set {plsfield tag} to: <!--plsfield:MISC2--> - - - (1C) If {text field} equals “COD”, then (a) set {text field} to: MISC3 (b) set {plsfield tag} to: <!--plsfield:MISC3--> - - - (1D) If {text field} equals “CHANGE”, then (a) set {text field} to: MISC4 (b) set {plsfield tag} to: <!--plsfield:MISC4--> - - - (1E) If {text field} equals “TRANS”, then (a) set {text field} to: MISC5 (b) set {plsfield tag} to: <!--plsfield:MISC5--> - - - (1F) If {text field} equals “EXEC”, then (a) set {text field} to: MISC6 (b) set {plsfield tag} to: <!--plsfield:MISC6--> - - - (1G) If {text field} equals “CROSS”, then (a) set {text field} to: MISC7 (b) set {plsfield tag} to: <!--plsfield:MISC7--> - - - (1H) If {text field} equals “SECREF”, then (a) set {text field} to: MISC8 (b) set {plsfield tag} to: <!—plsfield:MISC8--> - - - (2) Caps and small caps. - - - (3) Set {long subsection} to a blank.	44 U.S.C. § 3901 note (Amend-ments) 44 U.S.C. § 3506 note (Amend-ments) 43 U.S.C. § 1595 note (Effective Date of 1984 Amendment) 44 U.S.C. § 101 note (Short Title of 1993 Amendment) 43 U.S.C. § 502 note (Temporary Authority of Secretary of the Interior to Facilitate Emergency Actions with Regard to 1976-1977 Drought) 22 U.S.C. § 5952 note (Limitation on Use of Funds for Certain Purposes) 22 U.S.C. § 2291 note (Determin-ing Major Drug-Transit Countries with Respect to Fiscal Year 1989) 10 U.S.C. § 2407 note (NATO Cooperative Logistic Support Agreements) 28 U.S.C. app. (Fed. R. Civ. P.) form 2 note (Explanatory Notes) 42 U.S.C. § 2472 note (Amend-ment) 43 U.S.C. § 946 (Amend-ments) 43 U.S.C. § 1843 note (Amend-ments) 2 U.S.C. § 60a-2 note (Amend-ments) 43 U.S.C. § 1753 note (Modifica-tion of Regulations Relating to Mining Operations on Public Lands; Posting of Reclamation Bond for All Operations Involving Significant Surface Disturbance) 43 U.S.C. § 751 note (Land Information Study; Report to Congress) 18 U.S.C. § 201 note (Memoran-dum of Attorney-General Regarding Conflict of Interest Provisions of Public Law 87-849, February 1, 1963, 28 F.R. 985) 12 U.S.C. § 1785 note (Choice of Highest Applicable Interest Rate) 42 U.S.C. ch. 72, subch. II, pt. B (prec. § 5631)
75 [437]	ÃÃ{plsfield tag}<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none">{Leading file}<tr><td width=“120”> </td><td width=“480”><center><font size=“2”>	</font></center></td> </tr></table>	7	2	14	12	4	1		0	0	C	(0.1) Set {plsfield tag} to: <!--plsfield:REFTEXT--> - - - (0.2) If the value of {text field} is “REFTEXT”, then set {plsfield tag} to a blank. - - - (1) (a) If {text field} equals “MISC2”, “COD”, “MISC3”, “CHANGE”, “MISC4”, “TRANS”, “MISC5”, “EXEC”, “MISC6”, “CROSS”, “MISC7”, “SECREF”, or “MISC8”, then add to {error file}: {TITLE NUMBER} USC{appendix} {SECTION NUMBER} – REFTEXT occurs after {text field} (b) Set value of {text field} to: REFTEXT - - - (2) Caps and small caps - - - (3) Set {long subsection} to blanks.	7 U.S.C. § 6807 note (References in Text)
76 [438]	ÃÃ{plsfield tag}<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none">{Leading file} <tr><td width=“120”> </td><td width=“480”><font size=“2”><center>	</font></center></td> </tr></table>	7	2	14	12	4	1		0	0	C	(0.1) Set {plsfield tag} TO: <!--plsfield:COD--> - - - (0.2) If the value of {text field} is “COD”, then set {plsfield tag} to a blank. - - - (1) (a) If {text field} equals “MISC3”, “CHANGE”, “MISC4”, “TRANS”, “MISC5”, “EXEC”, “MISC6”, “CROSS”, “MISC7”, “SECREF”, or “MISC8”, then add to {error file}: {TITLE NUMBER} USC{appendix} {SECTION NUMBER} – COD occurs after {text field} (b) Set value of {text field} to: COD - - - (2) Caps and small caps - - - (3) Set {long subsection} to blanks.	2 U.S.C. § 60a-2 notes (Cod-ification)
77	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none">{Leading file}<tr><td width=“162”> </td><td align=“justify” width=“438”><font size=“3”> <div align="justify"><b> <!-- -->	</b></font></div></td></tr></table>ÃÃ	8	3	12	12	2	1		24	40	J		8 U.S.C. § 1152(a)(4) (A)(i)
78 [439]	ÃÃ{plsfield tag}<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none">{Leading file}<tr><td width=“120”> </td><td width=“480”><center><font size=“2”>	</font></center></td> </tr></table>	7	2	14	12	4	1		0	0	C	(0.1) Set {plsfield tag} to: <!--plsfield:CHANGE--> - - - (0.2) If the value of {text field} is “CHANGE”, then set {plsfield tag} to a blank. - - - (1) (a) If {text field} equals “CHANGE”, “MISC4”, “TRANS”, “MISC5”, “EXEC”, “MISC6”, “CROSS”, “MISC7”, “SECREF”, or “MISC8”, then add to {error file}: {TITLE NUMBER} USC{appendix} {SECTION NUMBER} – CHANGE occurs after {text field} (b) Set value of {text field} to: CHANGE - - - (2) Caps and small caps - - - (3) Set {long subsection} to blanks.	44 U.S.C. § 3303a (Change of Name)
79	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none"> {Leading file}<tr><td width=“134”>  </td><td align=“justify” width=“466”> <div align="justify"><font size=“3”><b> <!-- -->	</b></font></div></td></tr></table>ÃÃ	8	3	12	12	2	1		8	24	J		26 U.S.C. § 1252(a)(3)
80 [440]	{footnote file}<!--plsfield:END--> <!--plsfield:USCDOC-->{USCDoc}<!--plsfield:CITE--><table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none"><tr width=“600”><td width=“120”> </td><td align=“left”><font size=“3”>{TITLE NUMBER}USC{APPENDIX}	</font></td></td></table> <!--plsfield:EXPCITE--> {HIERARCHICAL INFORMATION} <table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none"><tr><<td><font size=“1”> </font></td></tr></table><table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none"><tr width=“600”><td width=“120”>  </td><td width=“{section number width}” valign="top"><font size=“3”> <!--plsfield:HEAD--> <b><nobr> {SECTION NUMBER}. </nobr></b></td>	8	3	16	0	2	1		0	0	L	(1) The data between this locator and the next locator is the {SECTION NUMBER}. Replace “§<!-- section -->” with “§”. Replace “” with “-”. Replace <!-- --> <!-- --> with a blank. Delete any occurrences of “<nobr>” and “</nobr>”. Conduct special character processing. - - - (2) The value for the {TITLE NUMBER} variable is associated with the bell-R01 photo-composition code. - - - (3) Once the Precede-text-with processing has been completed, clear out the {footnote file}. - - - (4) Set value of {text field} to: HEAD - - - (5) Set {greatest indent} to zero. - - - (6) Set {long subsection} to blanks. - - - (7) Set {subsection anchor} to: off - - - (8) Store in {number of characters in section number} to the number of characters (including blanks and symbols) that are in {SECTION NUMBER}. - - - (9) Multiply {number of characters in section number} by eight and store as {section number width}. - - - (10) Subtract {section number width} from 480 and store the result as {catchline width} - - - (11) For every value of {N} (from 0 to 999), set {subsection}_{N} to a blank. - - - (12) Set {subsection primary indent} to zero. - - - (13) increment {USCDoc} by one.	1 U.S.C. § 1
81	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none"> {Leading file}<tr><td width=“120”>  </td><td width=“480” valign="top" align="center"><font size=“3”>	</font></td>	8	3	16	14	1	1	1	0	0	C	FOTP processing	28 U.S.C. app. (Fed. Cl. R.) app. J (rule 16)[441]
82 [442]	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none"> {Leading file}<tr><td width=“120”>  </td><td align=“justify”width=“480”> <div align="justify"><font size=“2”>     <!-- -->	</font></div></td></tr> </table>	7	2	8	0	1	1		7	0	J	If {text field} does not equal “SECREF”, then add to {error file}: {TITLE NUMBER} USC {SECTION NUMBER}{long subsection} ({text field}) – Locator-82 (format {format}) used outside Section Referred to in Other Sections note.	4 U.S.C. § 1 note (Section Referred to in Other Sections)
83	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none"> {Leading file}<tr><td width=“120”>  </td><td width=“480” align=“center”><font size=“3”><i>	</i></font></td></tr> </table>ÃÃ	8	3	16	14	3	1		0	0	C		28 U.S.C. app. (Fed. Cl. R.) app. A, form A
84 [443]	{plsfield tag}<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none"> {Leading file}<tr><td width=“120”>  </td><td width=“480”><center><font size=“3”>	</font></center></td> </tr></table>	8	3	14	12	4	1		0	0	C	(0.1) Set {plsfield tag} to: <!--plsfield:STATAMEND--> - - - (0.2) If the value of {text field} is “STATAMEND”, then set {plsfield tag} to a blank. - - - (1) (a) If {text field} equals “MISC1”, “REFTEXT”, “MISC2”, “COD”, “MISC3”, “CHANGE”, “MISC4”, “TRANS”, “MISC5”, “EXEC”, “MISC6”, “CROSS”, “MISC7”, “SECREF”, or “MISC8”, then add to {error file}: {TITLE NUMBER} USC {SECTION NUMBER} – STATAMEND occurs after {text field} (b) Set value of {text field} to: S0TATAMEND - - - (2) Caps and small caps - - - (3) Set {long subsection} to blanks.	16 U.S.C. § 3631 note (Amend-ment of Section) 26 U.S.C. 132 note (Amendment of Subsection (f))
85 [444]	ÃÃ{plsfield tag}<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none">{Leading file}<tr><td width=“120”> </td><td width=“480”> <center><font size=“2”>	</font></center></td> </tr></table>	7	2	14	12	4	1		0	0	C	(0.1) Set {plsfield tag} to: <!--plsfield:TRANS--> - - - (0.2) If the value of {text field} is “TRANS”, then set {plsfield tag} to a blank. - - - (1) (a) If {text field} equals “MISC5”, “EXEC”, “MISC6”, “CROSS”, “MISC7”, “SECREF”, or “MISC8”, then add to {error file}: {TITLE NUMBER} USC {SECTION NUMBER} – TRANS occurs after {text field} (b) Set value of {text field} to: TRANS - - - (2) Caps and small caps - - - (3) Set {long subsection} to blanks.	43 U.S.C. § 1457 note (Transfer of Functions) 43 U.S.C. § 1457 note (Emergency Preparedness Functions)
86 [445]	ÃÃ{plsfield tag}<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none">{Leading file}<tr><td width=“120”> </td><td width=“480”> <center><font size=“2”>	</font></center></td> </tr></table>	7	2	14	12	4	1		0	0	C	(0.1) Set {plsfield tag} to: <!--plsfield:EXEC--> - - - (0.2) If the value of {text field} is “EXEC”, then set {plsfield tag} to a blank. - - - (1) (a) If {text field} equals “MISC6”, “CROSS”, “MISC7”, “SECREF”, or “MISC8”, then add to {error file}: {TITLE NUMBER} USC {SECTION NUMBER} – EXEC occurs after {text field} (b) Set value of {text field} to: EXEC - - - (2) Caps and small caps - - - (3) Set {long subsection} to blanks.	36 U.S.C. § 2111 note (Ex. Ord. No. 9873) 4 U.S.C. § 1 note (Ex. Ord. No. 10834)
87 [446]	ÃÃ{plsfield tag}<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none">{Leading file}<tr><td width=“120”> </td><td width=“480”> <center><font size=“2”>	</font></center></td> </tr></table>	7	2	14	12	4	1		0	0	C	(0.1) Set {plsfield tag} to: <!--plsfield:CROSS--> - - - (0.2) If the value of {text field} is “CROSS”, then set {plsfield tag} to a blank. - - - (1) (a) If {text field} equals “MISC7”, “SECREF”, or “MISC8”, then add to {error file}: {TITLE NUMBER} USC {SECTION NUMBER} – CROSS occurs after {text field} (b) Set value of {text field} to: CROSS - - - (2) Caps and small caps - - - (3) Set {long subsection} to blanks.	3 U.S.C. § 1 note (Cross References) 48 U.S.C. § 864 note (Federal Rules of Criminal Procedure)
88	<table width=“586” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none"> {Leading file}<tr><td width=“134”>  </td><td align=“justify” width=“452”> <div align="justify"><font size=“3”><i>     <!-- -->	</i></font></div></td> </tr></table>ÃÃ	8	3	9	0	3	1		16	8	J		16 U.S.C. § 3631 note (Amend-ment of Section)
89 [447]	<td width=“{catchline width}” align=“justify”><div align="justify"><b> <!-- -->	</b></div></td></font> </tr></table> <!--plsfield:{text field}-->	8	3	0	14	2	1		0	16	J	(1) Delete all characters until the first character that is neither a period nor a blank - - - (2) Set value of {text field} to: STATUTE - - - (3) If (after processing any G-codes, K-codes, and T-codes), the first non-blank, non-punctuation character are any of: Repealed Omitted Transferred Abrogated Rescinded Then set {text field} to: MISC1 - - - (4) Set {footnote divider file} to: <font size=“2”> ____________ </font></td></tr><tr><td>  </td><td>	1 U.S.C. § 1 3 U.S.C. § 205 2 U.S.C. § 604 48 U.S.C. §§ 1694 to 1694e 18 U.S.C. app. (Fed. R. Crim. P.) rule 39 18 U.S.C. app. (Fed. R. Crim. P.) rule 19
90	<br /><strong><font color=“#FFFFFF”>Improper locator code</font></strong><!-- I90 even page ears:	--><br />	8	3	0	0	2	1		0	0	L	Add to {error file}: {TITLE NUMBER} USC {SECTION NUMBER}{long subsection} ({text field}) – improper use of locator-90 (format {format}) – LRC documentation states that this locator (which sets even page ears) is not to be used in data.
91	<br /><strong><font color=“#FFFFFF”>Improper locator code</font></strong><!-- I91 odd page ears:	--><br />	8	3	0	0	2	1		0	0	R	Add to {error file}: {TITLE NUMBER} USC {SECTION NUMBER}{long subsection} ({text field}) – improper use of locator-91 (format {format}) – LRC documentation states that this locator (which sets odd page ears) is not to be used in data.
92	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none"> {Leading file}<tr><td width=“120”>  </td><td width=“480” align=“center”><font size=“2”>	</font></td></tr> </table>	7	2	14	16	1	1		0	0	C		8 U.S.C. § 1182 note (Resettle-ment of Refugee-Escapee)
93	<table width="100%" border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none">{Leading file}<tr><td align=“justify” valign="top" width="240"><font size=“1”>	</font></td>	6	1	7	0	1	1	1	0	0	L	FOTP processing	5 U.S.C. prec. pt. I
94	<td width=“9”> </td><td width=“231” valign="bottom" align="right"><font size=“1”>	</font></td>	6	1	7	0	1	1	2	0	0	R	FOTP processing	5 U.S.C. app. (Table of Contents)
95	<table width="100%" border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="rows">{Leading file}<tr><td align=“justify” valign="top" width="90%"><div align="justify"><font size=“3”><b> <!-- -->	</b></font></div></td>	8	3	10	0	2	1	1	0	16	J	FOTP processing	5 U.S.C. app. (Table of Contents)
96	<td width=“1%”> </td><td width="9%" valign="bottom" align="right"><font size=“3”><b>	</b></font></td>	8	3	10	0	2	1	2	0	0	R	FOTP processing	5 U.S.C. app. (Table of Contents)
97	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none"> {Leading file}<tr><td width=“120”>  </td><td align=“left” width=“480”>                        <strong><font color=“#FFFFFF” size=“3”>Improper locator code</font></strong><!--I97--><font size=“3”>	</font></td></tr> </table>	8	3	666	0	1	1		24	0	L	Add to {error file}: {TITLE NUMBER} USC {SECTION NUMBER}{long subsection} ({text field}) – improper locator, format {format}, bell-I97
98	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none"> {Leading file}<tr><td width=“120”> </td><td width=“480” align=“right”><strong><font color=“#FFFFFF” size=“3”>Improper locator code</font></strong><!--I98--><font size=“3”>	</font></td></tr> </table>	8	3	8	0	1	1		0	0	R	Add to {error file}: {TITLE NUMBER} USC {SECTION NUMBER}{long subsection} ({text field}) – improper locator, format {format}, bell-I98
99	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none"> {Leading file}<tr><td width=“120”>  </td><td align=“left” width=“480”><strong><font color=“#FFFFFF” size=“3”>Improper locator code</font></strong><!--I99--><font size=“3”>	</font></td></tr> </table>	8	3	8	0	1	1		0	0	L	Add to {error file}: {TITLE NUMBER} USC {SECTION NUMBER}{long subsection} ({text field}] – improper locator, format {format}, bell-I99
Any other	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none"> {Leading file}<tr><td width=“120”>  </td><td align=“left” width=“480”><font size=“3”>	</font></td></tr> </table>	8	3	0	0	1	1		0	0	L	Add to {error file}: {TITLE NUMBER} USC {SECTION NUMBER}{long subsection} ({text field}] – unidentified process, format {format}, bell-I{bell-I}

Format 5804
%I	Precede text with	Follow text with	Font size in points	HTML font size	Top lead- ing	Bottom leading	Type-face	G r i d	F O T P	PI[448]	SI [449]	LT[450]	Special processing	Example at
01	{footnote file}<!--plsfield:END--> <!--plsfield:USCDOC-->{USCDoc} <!--plsfield:CITE--><table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules=“rows”><tr width=“600”><td width=“120”>  </td><td width=“480” align="left"><font size=“3”>U.S.C.	<p id=“blankline”><!--plsfield:EXPCITE--> {HIERARCHICAL INFORMATION}₁</p id=“blankline”></td></tr></table> <table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules=“rows”><!--plsfield:HEAD--><tr width=“600”><td width=“120”>  </td><td width=“480” align="center"><font size=“5”><b> {HIERARCHICAL INFORMATION}₁ </b></font></td></tr> </table><!--plsfield:MISC1-->	10	5	0	0	1	1		0	0	C	(1) Set {leading} and {greatest indent} to zero. - - - (2) Set {text field} to: MISC1 - - - (3) Set {footnote divider file} to: <font size=“2”> ____________ </font> </td></tr><tr> <td> </td> <td> - - - (4) After outputting the “precede text with” material, clear out {footnote file} - - - (5) In addition to outputting the text between the bell-I01 and the next locator, also store[451] the text as {HIERARCHICAL INFORMATION}₁ - - - (6) Increment {USCDoc} by one.	Table IX (prec. title 1)
02	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules=“rows”>{Leading file}<tr width=“600”><td width=“120”>  </td><td width=“480” align="center"><font size=“1”></font> </td></tr></table>		3	1	10	10	1	1		189	0	L		Table IX (prec. title 1)
03	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules=“rows”>{Leading file}<tr width=“600”><td width=“120”>  </td><td width=“480” align="center"><font size=“3”>	</font></td></tr> </table>	8	3	16	10	1	1		0	0	C		Table IX (prec. title 1)
04	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none"> {Leading file}<tr><td width=“120”> </td><td width=“480” align=“justify”><div align="justify"><font size=“3”> <!-- -->	</font></div></td></tr></table>ÃÃ	8	3	9	9	1	1		0	16	J		28 U.S.C. app. (Fed. Cl. R.) rule 16
05	<table width=“100%” border=“0” cellspacing=“0” cellpadding=“0” frame=“void”>{Leading file}<tr><td width=“120”> </td><td align=“center” ><font size=“7”><i>	</i></font></td></tr> </table>	72	7	84	0	3	3		0	0	C	Add to {error file}: {HIERARCHICAL INFORMATION}₁USC {SECTION NUMBER}{long subsection} ({text field}) – warning – verify implementation of format {format}, bell-I05
06			8	3	8	0	1	1		0	0	C	(1) Do not output this material. Store it, instead, as {HIERARCHICAL INFORMATION}₁	Table IX (prec. title 1)
07	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none"> {Leading file}<tr><td width=“120”>  </td><td width=“480” align=“justify”><div align="justify"><font size=“2”> <!-- -->	</font></div></td></tr></table>	7	2	8	0	1	1		0	14	J		Table I (prec. title 1)
08	{footnote file}<!--plsfield:END--> <!--plsfield:USCDOC-->{USCDoc} <!--plsfield:CITE--><table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules=“rows”><tr width=“600”><td width=“120”>  </td><td width=“480” align="left"><font size=“3”>U.S.C. {HIERARCHICAL INFORMATION}₁:	<p id=“blankline”><!--plsfield:EXPCITE--> {HIERARCHICAL INFORMATION}₁</p id=“blankline”></td></tr></table> <table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules=“rows”><!--plsfield:HEAD--><tr width=“600”><td width=“120”>  </td><td width=“480” align="justify”><div align="justify"><font size=“3”><b> {Act}</b></font></div></td></tr></table> <!--plsfield:REFTEXT-->	8	3	28	12	2	1		0	0	L	(1) Set {leading} and {greatest indent} to zero. - - - (2) Set {text field} to: REFTEXT - - - (3) Set {footnote divider file} to: <font size=“2”> ____________ </font> </td></tr><tr> <td> </td> <td> - - - (4) After outputting the “precede text with” material, clear out {footnote file} - - - (5) In addition to outputting the text between the bell-I01 and the next locator, also store[452] the text as {Act} _{- - -} (6) increment {USCDoc} by one.	Table IX, title 1
09	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules=“rows”><tr width=“600”><td width=“120”>  </td><td width=“139” align="left"><font size=“2”><i>	</i></font></td>	7	2	8	0	3	1		0	0	L		Table IX, title 1
10	<td width=“341” align=“left”><font size=“2”><i>	</i></font></td></tr> </table>	7	2	0	10	3	1		60	60	L		Table IX, title 1
11	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame=“void”>{Leading file}<tr><td width=“120”> </td><td width=“480” align=“left”><font size=“3”><b>	</b></font></td></tr> </table>ÃÃ	8	3	16	12	2	1		0	0	L	Add to {error file}: {HIERARCHICAL INFORMATION}₁ USC {SECTION NUMBER}{long subsection} ({text field}) – error – format {format}, bell-I11 should not be in raw data
12	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame=“void”>{Leading file}<tr><td width=“120”> </td><td width=“139” align=“left”><font size=“2”><i>	</i></font></td></tr> </table>	7	2	8	0	3	1		0	0	L	Add to {error file}: {HIERARCHICAL INFORMATION}₁ USC {SECTION NUMBER}{long subsection} ({text field}) – error – format {format}, bell-I12 should not be in raw data
13	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame=“void”>{Leading file}<tr><td width=“120”> </td><td width=“480” align=“left”><font size=“2”><i>	</i></font></td></tr> </table>	7	2	0	10	3	1		60	0	L	Add to {error file}: {HIERARCHICAL INFORMATION}₁ USC {SECTION NUMBER}{long subsection} ({text field}) – error – format {format}, bell-I13 should not be in raw data
14	<table width=“100%” border=“0” cellspacing=“0” cellpadding=“0” frame=“void”>{Leading file}<tr><td width=“120”> </td><td align=“center”><font size=“1”>	</font></td></tr> </table>	6	1	7	0	1	4		0	0	C	(1) Add to {error file}: {HIERARCHICAL INFORMATION}₁ USC {SECTION NUMBER}{long subsection} ({text field}) – warning – verify implementation of format {format}, bell-I14 – normally used for GPO imprint line - - - (2) Caps and small caps
15	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame=“void”>{Leading file}<tr><td width=“120”> </td><td width=“480” align=“center”><font size=“1”>	</font></td></tr> </table>	6	1	7	0	1	4		0	0	C	(1) Add to {error file}: {HIERARCHICAL INFORMATION}₁ USC {SECTION NUMBER}{long subsection} ({text field}) – warning – verify implementation of format {format}, bell-I15 – normally used for signature lines - - - (2) Caps and small caps
16	<table width="100%" border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none">{Leading file}<tr><td align=“justify”><div align="justify"><font size=“3”>               <!-- -->	</font></div></td></tr></table>	8	3	9	0	1	1		16	0	J		18 U.S.C. app. (Fed. R. Evid.)
17 [453]	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none">{Leading file}<tr><td width=“120”> </td><td width=72 align=“justify” valign="top"><div align="justify"><font size=“2”>	</font></div></td>	7	2	8	0	1	1	1	0	0	J	(1) FOTP processing - - - (2) ) Add to {error file}: {HIERARCHICAL INFORMATION}₁ USC {SECTION NUMBER}{long subsection} ({text field}) – warning – verify implementation of format {format}, bell-I17 – normally used for signature lines
18	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="none" rules="none"> {Leading file}<tr><td width=“120”>  </td><td width=“480”>{footnote divider file}<div align=“justify”><font size=“1”>      <!-- -->	</div></font></td> </tr></table>ÃÃ	6	1	8	8	1	1		12	0	J	(1) if the {footnote file} is not empty, then set the {leading file} and the {footnote divider file} to a blank. - - - (2) Increment {footnote switch} by one. - - - (3) Do not output this material. Add it, instead, to the {footnote file} for use with document breaks (i.e., locator 80 (in formats 5800 to 5803) and bell-R) - - - (4) Add to {error file}: {HIERARCHICAL INFORMATION}₁ USC {SECTION NUMBER}{long subsection} ({text field}) – unidentified process, format {format}, bell-I18
19	<td width=“12”> </td><td valign=“bottom” align=“justify” width=“396”><div align="justify"><font size=“2”> <!-- -->	</font></div></td>	7	2	8	0	1	1	2	54	66	J	(1) Add to {error file}: {HIERARCHICAL INFORMATION}₁ USC {SECTION NUMBER}{long subsection} ({text field}) – warning – verify implementation of format {format}, bell-I19 - - - (2) FOTP processing
20	<td width=“12”> </td><td valign=“bottom” align=“justify” width=“396”> <div align="justify"><font size=“2”> <!-- -->	</font></div></td>	7	2	8	0	1	1	2	36	40	J	(1) Add to {error file}: {HIERARCHICAL INFORMATION}₁ USC {SECTION NUMBER}{long subsection} ({text field}) – warning – verify implementation of format {format}, bell-I20 - - - (2) FOTP processing
21	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none"> {Leading file}<tr><td width=“120”>  </td><td width=“480” align=“justify”><div align="justify"><font size=“2”>    <!-- -->	</font></div></td></tr></table>	7	2	8	8	1	1		7	0	J		7 U.S.C. § 612c note (Com-modity Distribu-tion Reform, § 3(f))
22	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none"> {Leading file}<tr><td width=“132”>  </td><td width=“468” align=“justify”> <div align="justify"><font size=“2”>    <!-- -->	</font></div></td></tr></table>	7	2	0	0	1	1		14	7	J		7 U.S.C. § 612c note (Commodity Distribution Reform, § 3(f)(1))
23	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none"> {Leading file}<tr><td width=“144”>  </td><td width=“456” align=“justify”><div align="justify"><font size=“2”>    <!-- -->	</font></div></td></tr></table>	7	2	0	0	1	1		21	14	J		7 U.S.C. § 612c note (Com-modity Distribution Reform, § 3(f)(2)(A))
24	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none"> {Leading file}<tr><td width=“180”>  </td><td width=“420” align=“justify” ><div align="justify"><font size=“2”>    <!-- -->	</font></div></td></tr></table>	7	2	8	0	1	1		42	35	J		8 U.S.C. § 1101 note (Effective Date of 1996 Amendments, § 309(c)(5) (C)(i)(I) (aa))
25	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none"> {Leading file}<tr><td width=“132”>  </td><td width=“273” valign="top" align=“justify”> <div align="justify"><font size=“2”> <!-- -->	</font></div></td>	7	2	8	0	1	1	1	21	28	J	FOTP processing	2 U.S.C. § 358 note
26	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="rows"> {Leading file}<tr><td width=“192”>  </td><td width=“110” valign="top" align=“justify”> <div align="justify"><font size=“2”> <!-- -->	</font></div></td>	7	2	8	0	1	1	1	42	49	J	FOTP processing	2 U.S.C. § 358 note
27	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none"> {Leading file}<tr><td width=“120”>  </td><td width=“480” align=“justify”><div align="justify"><font size=“2”>	</font></div></td></tr></table>	7	2	0	0	1	1		0	0	J		10 U.S.C. ch. 1201
28	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="none" rules="none"> {Leading file}<tr><td width=“120”>  </td><td width=“480”>{footnote divider file}<div align=“justify”><font size=“1”>   <!-- -->	</div></font></td> </tr></table>	6	1	8	8	1	1		6	0	J	(1) if the {footnote file} is not empty, then set the {leading file} and the {footnote divider file} to a blank. - - - (2) Increment {footnote switch} by one. - - - (3) Do not output this material. Add it, instead, to the {footnote file} for use with document breaks (i.e., locator 80 (in formats 5800 to 5803) and bell-R)	10 U.S.C. ch. 1201
29	<td width=“9”> </td><td width=“231” valign="top" align="right"><font size=“1”>	</font></td>	6	1	7	7	1	1	2	0	0	R	FOTP processing	10 U.S.C. subtitle A
30	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none"> {Leading file}<tr><td width=“120”>  </td><td width=“195” valign="top" align="center"><font size=“2”>	</font></td>	7	2	8	0	1	1	1	0	0	C	FOTP processing	28 U.S.C. § 2254 note (forms)
31	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none"> {Leading file}<tr><td width=“120”>  </td><td valign="top" align=“left” width=“195”><font size=“2”>	</font></td><td width=90> </td>	7	2	8	0	1	1	1	0	0	L	FOTP processing	26 U.S.C. § 419A(f)(7) (B)
32	<td width=“12”> </td><td width=“273” valign="top" align=“left” valign="bottom"><font size=“2”> <!-- -->	</font></td>	7	2	8	0	1	1	2	120	127	L	FOTP processing	28 U.S.C. app. (Fed. R. App. P.) form 1
33	<td width=“12”> </td><td width=“273” valign="top" valign="bottom" align=“center”><font size=“2”>	</font></td>	7	2	8	0	1	1	2	120	120	C	FOTP processing	28 U.S.C. § 2254 note (forms)
34	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none"> {Leading file}<tr><td width=“190”>  </td><td width=“410” align=“justify”><div align="justify"><font size=“3”>     <!-- -->	</font></div></td></tr></table>ÃÃ	8	3	9	0	1	1		48	40	J		7 U.S.C. § 136a(h)(3) (B)(iii)(III) (aa)
35	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none"> {Leading file}<tr><td width=“120”>  </td><td width=“285” align=“justify” valign="top"><div align="justify"><font size=“2”> <!-- -->	</font></div></td>	7	2	8	0	1	1	1	0	7	J	FOTP processing	10 U.S.C. § 1557(a)
36	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="rows"> {Leading file}<tr><td width=“120”>  </td><td width=“285” align=“justify” valign="top"><div align="justify"><font size=“2”> <!-- -->	</font></div></td>	7	2	8	0	1	1	1	0	7	J	FOTP processing	10 U.S.C. § 1557(a)
37	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="rows"> {Leading file}<tr><td width=“120”>  </td><td width=“480” align=“left” valign="top"><font size=“2”> <!-- -->	</font></td>	7	2	8	0	1	1	1	0	7	L	FOTP processing	10 U.S.C. subtitle A
38	<td width=“12”> </td><td width=“310” align=“justify” valign="top"><div align="justify"><font size=“2”> <!-- -->	</font></div></td>	7	2	8	0	1	1	2	28	36	J	FOTP processing	10 U.S.C. subtitle A
39	<td width=“12”> </td><td width=“98” align="right" valign="bottom"><font size=“2”>	</font></td>	7	2	8	0	1	1	3	177	177	R	FOTP processing	10 U.S.C. subtitle A.
40	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="rows"> {Leading file}<tr><td width=“132”>  </td><td width=“273” align=“justify” valign="top"><div align="justify"><font size=“1”> <!-- -->	</font></div></td>	6	1	7	0	1	1	1	0	6	J	FOTP processing	5 U.S.C. § 5332 note (sched. 4)
41	<td width=“9”> </td><td width=“186” valign="top" align=“right”><font size=“1”>	</font></td>	6	1	7	0	1	1	2	0	0	R	FOTP processing	5 U.S.C. § 5332 note (sched. 4)
42	<td width=“10”> </td><td width=“185” align=“justify” valign="top"><div align="justify"><font size=“1”>	</font></div></td>	6	1	7	0	1	1	1	0	0	J	FOTP processing
43	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="rows"> {Leading file}<tr><td width=“132”>  </td><td valign="top" align=“justify” width=“273”> <div align="justify"><font size=“2”> <!-- -->	</font></div></td>	7	2	8	0	1	1	1	21	28	J	FOTP processing	10 U.S.C. § 12003(a)
44	<td width=“12”> </td><td width=“183” valign="top" align="right"><font size=“2”>	</font></td>	7	2	8	0	1	1	2	0	0	R	FOTP processing	10 U.S.C. § 1557(a)
45	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="rows"> {Leading file}<tr><td width=“120”>  </td><td valign="top" align=“justify” width=“320”> <div align="justify"><font size=“1”> <!-- -->	</font></div></td>	6	1	7	0	1	1	1	0	6	J	(1) Add to {error file}: {HIERARCHICAL INFORMATION}₁ USC {SECTION NUMBER}{long subsection} ({text field}) – warning – verify implementation of format {format}, bell-I45 - - - (2) FOTP processing
46	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="rows"> {Leading file}<tr><td width=“120”>  </td><td valign="top" align=“justify” width=“320”> <div align="justify"><font size=“1”>               <!-- -->	</font></div></td>	6	1	7	0	1	1	1	12	18	J	(1) Add to {error file}: {HIERARCHICAL INFORMATION}₁ USC {SECTION NUMBER}{long subsection} ({text field}) –warning – verify implementation of format {format}, bell-I46 - - - (2) FOTP processing
47	<td width=“9”> </td><td width=“151” valign="bottom" align="justify"><div align="justify"><font size=“1”> <!-- -->	</font></div></td>	6	1	7	0	1	1	2	141	147	J	(1) Add to {error file}: {HIERARCHICAL INFORMATION}₁ USC {SECTION NUMBER}{long subsection} ({text field}) – warning – verify implementation of format {format}, bell-I47 - - - (2) FOTP processing
48	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none"> {Leading file}<tr><td width=“274”>  </td><td align=“justify” width=“326”><div align="justify"><font size=“2”>	</font></div></td></tr></table>	7	2	8	0	1	1		90	97	J		5 U.S.C. § 1101 note (Ex. Ord. No. 12107, § 2-1(a))
49	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="rows"> {Leading file}<tr><td width=“120”>  </td><td valign="top" align=“justify” width=“153”> <div align="justify"><font size=“1”>	</font></div></td>	6	1	7	0	1	1	1	0	6	J	(1) Add to {error file}: {HIERARCHICAL INFORMATION}₁ USC {SECTION NUMBER}{long subsection} ({text field}) – warning – verify implementation of format {format}, bell-I49 - - - (2) FOTP processing
50	<td width=“9”> </td><td width=“75” valign="bottom" align="right"><font size=“1”>	</font></td>	6	1	7	0	1	1	2	66	66	R	(1) Add to {error file}: {HIERARCHICAL INFORMATION}₁ USC {SECTION NUMBER}{long subsection} ({text field}) – unidentified process, format {format}, bell-I50 - - - (2) FOTP processing
51	<td width=“9”> </td><td width=“150” valign="bottom" align="justify"><div align="justify"><font size=“1”> <!-- -->	</font></div></td>	6	1	7	0	1	1	3	106	112	J	(1) Add to {error file}: {HIERARCHICAL INFORMATION}₁ USC {SECTION NUMBER}{long subsection} ({text field}) – warning – verify implementation of format {format}, bell-I51 - - - (2) FOTP processing
52	<td width=“9”> </td><td width=“75” valign="bottom" align="right"><font size=“1”>	</font></td>	6	1	7	0	1	1	4	172	172	R	(1) Add to {error file}: {HIERARCHICAL INFORMATION}₁ USC {SECTION NUMBER}{long subsection} ({text field}) – warning – verify implementation of format {format}, bell-I52 - - - (2) FOTP processing
53	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void"> {Leading file}<tr><td width=“120”>  </td><td valign="top" align=“justify” width=“125”><div align="justify"><font size=“2”> <!-- -->	</font></div></td>	7	2	8	0	1	1	1	0	7	J	(1) Add to {error file}: {HIERARCHICAL INFORMATION}₁ USC {SECTION NUMBER}{long subsection} ({text field}) – unidentified process, format {format}, bell-I53 - - - (2) FOTP processing
54	<td width=“12”> </td><td width=“100” valign="bottom" align="right"><font size=“2”>	</font></td>	7	2	8	0	1	1	2	54	54	R	(1) Add to {error file}: {HIERARCHICAL INFORMATION}₁ USC {SECTION NUMBER}{long subsection} ({text field}) – warning – verify implementation of format {format}, bell-I54 - - - (2) FOTP processing
55	<td width=“12”> </td><td width=“119” valign="bottom" align="justify"><div align="justify"><font size=“2”> <!-- -->	</font></div></td>	7	2	8	0	1	1	3	106	113	J	(1) Add to {error file}: {HIERARCHICAL INFORMATION}₁ USC {SECTION NUMBER}{long subsection} ({text field}) – warning – verify implementation of format {format}, bell-I55 - - - (2) FOTP processing
56	<td width=“12”> </td><td width=“100” valign="bottom" align="right"><font size=“2”>	</font></td>	7	2	8	0	1	1	4	160	160	R	(1) Add to {error file}: {HIERARCHICAL INFORMATION}₁ USC {SECTION NUMBER}{long subsection} ({text field}) – warning – verify implementation of format {format}, bell-I56 - - - (2) FOTP processing
57	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="rows"> {Leading file}<tr><td width=“120”>  </td><td valign="top" align=“center” width=“278”><font size=“1”>	</font></td>	6	1	6	6	3	1	1	0	0	C	(1) Add to {error file}: {HIERARCHICAL INFORMATION}₁ USC {SECTION NUMBER}{long subsection} ({text field}) – warning – verify implementation of format {format}, bell-I57 - - - (2) FOTP processing
58	<td width=“9”> </td><td width=“193” valign="bottom" align="justify"><div align="justify"><font size=“1”> <!-- -->	</font></div></td>	6	1	6	6	3	1	2	126	132	J	(1) Add to {error file}: {HIERARCHICAL INFORMATION}₁ USC {SECTION NUMBER}{long subsection} ({text field}) –warning – verify implementation of format {format}, bell-I58 - - - (2) FOTP processing
59	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="rows"> {Leading file}<tr><td width=“120”>  </td><td valign="top" align=“left” width=“390”><font size=“1”> <!-- -->	</font></td>	6	1	6	6	1	1	1	0	6	L	(1) Add to {error file}: {HIERARCHICAL INFORMATION}₁ USC {SECTION NUMBER}{long subsection} ({text field}) – warning – verify implementation of format {format}, bell-I59 - - - (2) FOTP processing
60	<td width=“9”> </td><td width=“480” valign="bottom" align="right"><font size=“1”>	</font></td>	6	1	6	6	1	1	2	0	0	R	(1) Add to {error file}: {HIERARCHICAL INFORMATION}₁ USC {SECTION NUMBER}{long subsection} ({text field}) – warning – verify implementation of format {format}, bell-I60 - - - (2) FOTP processing
61	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none"> {Leading file}<tr><td width=“120”>  </td><td width=“192” valign="top" align="right"><font size=“2”>	</font></td>	7	2	8	0	1	1	1	0	0	R	FOTP processing	18 U.S.C. app. (Fed. R. Crim. P.) prec. rule 1
62	<td width=7> </td><td align=“justify” valign="bottom" width=“281”> <div align="justify"><font size=“2”> <!-- -->	</font></div></td>	7	2	8	0	1	1	2	116	123	J	FOTP processing	18 U.S.C. app. (Fed. R. Crim. P.) prec. rule 1
63	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="box" rules="none"> {Leading file}<tr><td width=“120”>  </td><td width=“480” valign="top" align="center"><font size=“1”><i>	</i></font></td>	6	1	14	12	3	1	1	0	0	C	FOTP processing	5 U.S.C. § 5332 note (sched. 4)
64	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="box" rules="none"> {Leading file} <tr><td width=“120”>  </td><td width=“480” align="center"><font size=“1”>	</font></td></tr> </table>	6	1	14	12	4	1		0	0	C	Caps and small caps	5 U.S.C. § 5332 note (sched. 4)
65	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="rows"> {Leading file}<tr><td width=“120”>  </td><td valign="top" align=“left” width=“480”><font size=“1”>	</font></td>	4	1	4	9	1	1	1	0	0	L	(1) Add to {error file}: {HIERARCHICAL INFORMATION}₁ USC {SECTION NUMBER}{long subsection} ({text field}) – warning – verify implementation of format {format}, bell-I65 - - - (2) FOTP processing
66	<td width=“11”> </td><td width=“274” align=“left” valign="top"><font size=“2”>	</font></td>	7	2	8	0	1	1	2	84	84	L	FOTP processing	28 U.S.C. app. (Fed. R. Civ. P.) form 10
67	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none"> {Leading file}<tr><td width=“120”>  </td><td align=“justify” width=“480”><div align="justify"><font size=“2”><b> <!-- -->	</b></font></div></td></tr></table>	7	2	12	9	2	1		0	14	J		10 U.S.C. § 111 note
68	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="none" rules="none"> {Leading file}<tr><td width=“174”>  </td><td width=“426”>{footnote divider file}<div align=“justify”><font size=“1”>   <!-- -->	</div></font></td> </tr></table>	6	1	8	8	1	1		12	6	J	(1) if the {footnote file} is not empty, then set the {leading file} and the {footnote divider file} to a blank. - - - (2) Increment {footnote switch} by one. - - - (3) Do not output this material. Add it, instead, to the {footnote file} for use with document breaks (i.e., locator 80 (in formats 5800 to 5803) and bell-R) - - - (4) Add to {error file}: {HIERARCHICAL INFORMATION}₁ USC {SECTION NUMBER}{long subsection} ({text field}) – warning – verify implementation of format {format}, bell-I68
69	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none"> {Leading file}<tr><td width=“190”>  </td><td align=“justify” width=“410”><div align="justify"><font size=“3”><b> <!-- -->	</b></font></div></td></tr></table>ÃÃ	8	3	12	12	2	1		40	56	J		7 U.S.C. § 6802(4) (A)(iii)(III) (aa)
70	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="box" rules="none"> {Leading file}<tr><td width=“120”>  </td><td width=“240” valign="top" align="left"><font size=“1”>	</font></td>	6	1	7	7	1	1	1	0	0	L	FOTP processing	10 U.S.C. subtitle A
71	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="box" rules="none"> {Leading file}<tr><td width=“120”>  </td><td width=“480” align="center"><font size=“2”>	</font></td></tr> </table>	7	2	14	12	1	1		0	0	C		5 U.S.C. § 1101 note (Ex. Ord. No. 12107, § 2-1(a))
72	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="rows"> {Leading file}<tr><td width=“120”>  </td><td width=“285” align=“justify” valign="top"><div align="justify"><font size=“2”> <!-- -->	</font></div></td>	7	2	8	0	1	1	1	0	25	J	FOTP processing	5 U.S.C. § 5305 note (Fed. Law Enforce-ment Pay Reform, § 403(b)(1))
73	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="rows"> {Leading file}<tr><td width=“144”>  </td><td width=“261” align=“justify” valign="top"><div align="justify"><font size=“2”> <!-- -->	</font></div></td>	7	2	8	0	1	1	1	14	39	J	FOTP processing	26 U.S.C. § 4682(b)
74	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="rows"> {Leading file}<tr><td valign="top" width=“168”>  </td><td align=“justify” width=“237”><div align="justify"><font size=“2”> <!-- -->	</font></div></td>	7	2	8	0	1	1	1	28	53	J	FOTP processing	47 U.S.C. § 158(g) (Private Radio Services) (1)(g)(i)
75	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="rows"> {Leading file}<tr><td width=“192”>  </td><td valign="top" align=“justify” width=“213”> <div align="justify"><font size=“2”> <!-- -->	</font></div></td>	7	2	8	0	1	1	1	42	67	J	FOTP processing	47 U.S.C. § 158(g) (Private Radio Services) (6)(j)(vii) (1)
76	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none"> {Leading file}<tr><td width=“120”>  </td><td valign="top" align=“justify” width=“285”> <div align="justify"><font size=“2”> <!-- -->	</font></div></td>	7	2	8	0	1	1	1	0	25	J	FOTP processing	47 U.S.C. § 158(g) (Private Radio Services) (1)
77	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none"> {Leading file}<tr><td width=“120”>  </td><td valign="top" align=“center” width=“480”><font size=“2”>	</font></td>	7	2	14	12	1	1	1	0	0	C	Add to {error file}: {HIERARCHICAL INFORMATION}₁ USC {SECTION NUMBER}{long subsection} ({text field}) – warning – verify implementation of format {format}, bell-I77 – normally used for “[see main edition]” centered text
78	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void"> {Leading file}<tr><td width=“120”>  </td><td align=“justify” width=“480”><div align="justify"><font size=“2”>	</font></div></td></tr></table>	7	2	0	0	1	1	1	0	0	J	Add to {error file}: {HIERARCHICAL INFORMATION}₁ USC {SECTION NUMBER}{long subsection} ({text field}) – warning – verify implementation of format {format}, bell-I78
79	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void"> {Leading file}<tr><td width=“120”>  </td><td align=“justify” width=“480”><div align="justify"><font size=“3”>	</font></div></td></tr></table>ÃÃ	8	3	0	0	1	1		0	0	J	Add to {error file}: {HIERARCHICAL INFORMATION}₁ USC {SECTION NUMBER}{long subsection} ({text field}) – warning – verify implementation of format {format}, bell-I79
80	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void"> {Leading file}<tr><td width=“120”>  </td><td align=“left” width=“139”><font size=“3”>	</font></td>	8	3	9	0	1	1		0	0	L		Table IX, title 1
81	<td width=“341” align=“justify”><div align="justify"><font size=“3”>	</font></div></td></tr></table>	8	3	0	0	1	1		60	68	J		Table IX, title 1
82	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void"> {Leading file}<tr><td width=“120”>  </td><td align=“left” width=“130”><font size=“3”>	</font></td></tr> </table>ÃÃ	8	3	9	0	1	1		0	0	L	Add to {error file}: {HIERARCHICAL INFORMATION}₁ USC {SECTION NUMBER}{long subsection} ({text field}) – warning – verify implementation of format {format}, bell-I82
83	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="box" rules="none"> {Leading file}<tr><td width=“120”>  </td><td width=“480” align=“center”><font size=“3”>	</font></td></tr> </table>ÃÃ	8	3	0	0	1	1		0	0	C		15 U.S.C. § 1679c
84	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void"> {Leading file}<tr><td width=“120”>  </td><td align=“left” width=“480”><font size=“1”>	</font></td></tr> </table>	1	1	1	0	1	1		0	0	L	Add to {error file}: {HIERARCHICAL INFORMATION}₁ USC {SECTION NUMBER}{long subsection} ({text field}) – warning – verify implementation of format {format}, bell-I84
85	<!-- UNDEFINED LOCATOR, format 5804, bell-I85 -->		0	1	0	0	2	1		0	0	C	Add to {error file}: {HIERARCHICAL INFORMATION}₁ USC {SECTION NUMBER}{long subsection} ({text field}) – unidentified process, format {format}, bell-I85
86	<!-- UNDEFINED LOCATOR, format 5804, bell-I86 -->		0	1	0	0	1	1		0	0	C	Add to {error file}: {HIERARCHICAL INFORMATION}₁ USC {SECTION NUMBER}{long subsection} ({text field}) – unidentified process, format {format}, bell-I86
87	<!-- UNDEFINED LOCATOR, format 5804, bell-I87 -->		0	1	0	0	2	1		0	0	C	Add to {error file}: {HIERARCHICAL INFORMATION}₁ USC {SECTION NUMBER}{long subsection} ({text field}) – unidentified process, format {format}, bell-I87
88	<!-- UNDEFINED LOCATOR, format 5804, bell-I88 -->		0	1	0	0	2	1		0	0	C	Add to {error file}: {HIERARCHICAL INFORMATION}₁ USC {SECTION NUMBER}{long subsection} ({text field}) – unidentified process, format {format}, bell-I88
89	<!-- UNDEFINED LOCATOR, format 5804, bell-I89 -->		0	1	0	0	2	1		0	0	C	Add to {error file}: {HIERARCHICAL INFORMATION}₁ USC {SECTION NUMBER}{long subsection} ({text field}) – unidentified process, format {format}, bell-I89
90	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="rows"> {Leading file}<tr><td width=“120”>  </td><td valign="top" align=“left” width=“480”><font size=“3”>	</font></td>	8	3	14	12	4	1	1	0	0	C	(1) Add to {error file}: {HIERARCHICAL INFORMATION}₁ USC {SECTION NUMBER}{long subsection} ({text field}) – warning – verify implementation of format {format}, bell-I90 - - - (2) FOTP processing
91 [454]	<table width=“100%” border=“0” cellspacing=“0” cellpadding=“0” frame=“void” rules=“none”>{Leading file}<tr><center><img src=“./images/	.gif” width=“{width value from graphics table}” height=“{height value from graphics table}” alt=“{alt value from graphics table}” /></center>	8	3	9	0	4	1	1	0	0	L	(1) Delete the string “.eps”. - - - (2) FOTP processing	10 U.S.C. app. (R.C.A.A. F.) rule 20
92	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="rows"> {Leading file}<tr><td width=“120”>  </td><td valign="top" align=“left” width=“480”><font size=“3”>	</font></td>	8	3	14	12	4	1	1	0	0	C	(1) Add to {error file}: {HIERARCHICAL INFORMATION}₁ USC {SECTION NUMBER}{long subsection} ({text field}) – warning – verify implementation of format {format}, bell-I92 - - - (2) FOTP processing
93	<table width=“100%” border=“0” cellspacing=“0” cellpadding=“0” frame="void"> {Leading file}<tr><td valign="top" align=“center” width=“100%”><font size=“3”>	</font></td>	8	3	14	12	4	1	1	0	0	C	(1) Add to {error file}: {HIERARCHICAL INFORMATION}₁ USC {SECTION NUMBER}{long subsection} ({text field}) – warning – verify implementation of format {format}, bell-I93 - - - (2) FOTP processing
94 [455]	<table width=“100%” border=“0” cellspacing=“0” cellpadding=“0” frame=“void” rules=“none”>{Leading file}<tr><center><img src=“./images/	.gif” width=“{width value from graphics table}” height=“{height value from graphics table}” alt=“{alt value from graphics table}” /></center>	8	3	9	0	4	1	1	0	0	L	Delete the string “.eps”. - - - (2) FOTP processing	11 U.S.C. app. form 1
95	<table width=“100%” border=“0” cellspacing=“0” cellpadding=“0” frame="void"> {Leading file}<tr><td valign="top" align=“center” width=“100%”><font size=“3”>	</font></td>	8	3	14	12	4	1	1	0	0	C	(1) Add to {error file}: {HIERARCHICAL INFORMATION}₁ USC {SECTION NUMBER}{long subsection} ({text field}) – warning – verify implementation of format {format}, bell-I95 - - - (2) FOTP processing
96	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="box" rules="none"> {Leading file}<tr><td width=“120”>  </td><td width=“480” align="center"><font size=“1”>	</font></td></tr> </table>	6	1	14	12	4	1		0	0	C	(1) Add to {error file}: {HIERARCHICAL INFORMATION}₁ USC {SECTION NUMBER}{long subsection} ({text field}) – warning – verify implementation of format {format}, bell-I96 - - - (2) FOTP processing
97	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void"> {Leading file}<tr><td width=“120”>  </td><td width=“480” align="left"><font size=“3”>                       <!-- -->	</font></td></tr> </table>ÃÃ	8	3	666	0	1	1		24	0	L	Add to {error file}: {HIERARCHICAL INFORMATION}₁ USC {SECTION NUMBER}{long subsection} ({text field}) – warning – verify implementation of format {format}, bell-I97
98	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void"> {Leading file}<tr><td width=“120”>  </td><td width=“480” align="right"><font size=“3”>	</font></td></tr> </table>ÃÃ	8	3	8	0	1	1		0	0	R	Add to {error file}: {HIERARCHICAL INFORMATION}₁ USC {SECTION NUMBER}{long subsection} ({text field}) – warning – verify implementation of format {format}, bell-I98
99	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void"> {Leading file}<tr><td width=“120”>  </td><td width=“480” align="left"><font size=“3”>	</font></td></tr> </table>ÃÃ	8	3	8	0	1	1		0	0	L	Add to {error file}: {HIERARCHICAL INFORMATION}₁ USC {SECTION NUMBER}{long subsection} ({text field}) – warning – verify implementation of format {format}, bell-I99
Any other	<!-- UNDEFINED LOCATOR, format 5804, bell-I{bell-I} -->		8	3	0	0	1	1		0	0	L	Add to {error file}: {HIERARCHICAL INFORMATION}₁ USC {SECTION NUMBER}{long subsection} ({text field}) – unidentified process, format 5804, bell-I{bell-I}

Format 5807
%I	Precede text with	Follow text with	Font size in points	HTML font size	Top lead- ing	Bottom leading	Type-face	G r i d	F O T P	PI[456]	SI [457]	LT[458]	Special processing	Example at
01 to 56	<!-- UNDEFINED LOCATOR, format 5807, bell-I{bell-I} -->		8	3	0	0	1	1		0	0	L	Add to {error file}: {TITLE NUMBER} USC {SECTION NUMBER}{long subsection} ({text field}) – unidentified process, format 5807, bell-I{bell-I}
57	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules=“rows”>{Leading file}<tr><td width=“120”>  </td><td width=“233” align="left" valign=“top”><font size=“3”> <!-- -->	</font></td>	8	3	9	9	1	1	1	0	8	L	(1) FOTP processing - - - (2) Set {SECTION NUMBER} to a blank..	Declaration of Independence (signatures)
58	<td width=“14”>  </td><td width=“233” align="left" valign=“top”><font size=“3”> <!-- -->	</font></td>	8	3	9	9	1	1	2	109	117	L	FOTP processing	Declaration of Independence (signatures)
59 to 82	<!-- UNDEFINED LOCATOR, format 5807, bell-I{bell-I} -->		8	3	0	0	1	1		0	0	L	Add to {error file}: {TITLE NUMBER} USC {SECTION NUMBER}{long subsection} ({text field}) – unidentified process, format 5807, bell-I{bell-I}
83	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none"> {Leading file}<tr><td width=“120”>  </td><td width=“480” align=“center”><font size=“3”><i>	</i></font></td></tr> </table>	8	3	16	14	3	1		0	0	C		Declaration of Independence (signatures)
84 to 99	<!-- UNDEFINED LOCATOR, format 5807, bell-I{bell-I} -->		8	3	0	0	1	1		0	0	L	Add to {error file}: {TITLE NUMBER} USC {SECTION NUMBER}{long subsection} ({text field}) – unidentified process, format 5807, bell-I{bell-I}
Any other	<!-- UNDEFINED LOCATOR, format 5807, bell-I{bell-I} -->		8	3	0	0	1	1		0	0	L	Add to {error file}: {TITLE NUMBER} USC {SECTION NUMBER}{long subsection} ({text field}) – unidentified process, format 5807, bell-I{bell-I}

Format 5810
%I	Precede text with	Follow text with	Font size in points	HTML font size	Top lead- ing	Bottom leading	Type-face	G r i d	F O T P	PI[459]	SI [460]	LT[461]	Special processing	Example at
01	{footnote file}<!--plsfield:END--> <!--plsfield:USCDOC-->{USCDoc} <!--plsfield:CITE--><table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules=“rows”><tr width=“600”><td width=“120”>  </td><td width=“480” align="left"><font size=“3”>U.S.C.	<p id=“blankline”><!--plsfield:EXPCITE--> {HIERARCHICAL INFORMATION}₁</p id=“blankline”></td></tr></table> <table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules=“rows”><!--plsfield:HEAD--><tr width=“600”><td width=“120”>  </td><td width=“480” align="center"><font size=“5”><b> {HIERARCHICAL INFORMATION}₁ </b></font></td></tr> </table ><!--plsfield:MISC1-->	10	5	12	12	2	1		0	0	C	(1) Set {leading} and {greatest indent} to zero. - - - (2) Set {text field} to: MISC1 - - - (3) Set {footnote divider file} to: <font size=“2”> ____________ </font> </td></tr><tr> <td> </td> <td> - - - (4) After outputting the “precede text with” material, clear out {footnote file} - - - (5) In addition to outputting the text between the bell-I01 and the next locator, also store[462] the text as {HIERARCHICAL INFORMATION}₁ - - - (6) Increment {USCDoc} by one.	Table of Popular Names (catchline)
02	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules=“rows”>{Leading file}<tr width=“600”><td width=“120”>  </td><td width=“480” align="center"><font size=“1”></font> </td></tr></table>		3	1	10	10	1	1		189	0	L		Table of Popular Names (intro-duction)
03	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules=“rows”>{Leading file}<tr width=“600”><td width=“120”>  </td><td width=“480” align="justify"><div align="justify"><font size=“3”>	</font></div></td></tr></table>	8	3	17	10	1	1		0	0	J		Table of Popular Names (Intro-duction)
04	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules=“rows”>{Leading file}<tr width=“600”><td width=“120”>  </td><td width=“480” align="center"><font size=“1”></font> </td></tr></table>		3	1	10	10	1	1		189	0	L		Table of Popular Names (intro-duction)
05	<!-- UNDEFINED LOCATOR, format {format}, bell-I{bell-I} -->		8	3	0	0	1	1		0	0	L	Add to {error file}: {HIERARCHICAL INFORMATION} – unidentified process, format {format}, bell-I{bell-I}
06			8	3	8	0	1	1		0	0	C	Do not output this material. Store it, instead, as {HIERARCHICAL INFORMATION}₁	Table of Popular Names (running head)
07 to 11	<!-- UNDEFINED LOCATOR, format {format}, bell-I{bell-I} -->		8	3	0	0	1	1		0	0	L	Add to {error file}: {HIERARCHICAL INFORMATION} – unidentified process, format {format}, bell-I{bell-I}
12	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules=“rows”>{Leading file}<tr width=“600”><td width=“148”>  </td><td width=“452” align="justify"><div align="justify"><font size=“3”> <!-- -->	</font></div></td></tr></table>	8	3	9	9	1	1		16	24	J		Table of Popular Names (A.A.A. Farm Relief and Inflation Act)
13	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none">{Leading file}<tr width=“600”><td width=“120”> </td><td width=“480” align=“center”><font size=“3”>	</font></td></tr> </table>	8	3	17	10	1	1		0	0	C	Add to {error file}: {HIERARCHICAL INFORMATION}₁, – warning – verify implementation of format {format}, bell {bell-I}
14 to 18	<!-- UNDEFINED LOCATOR, format {format}, bell-I{bell-I} -->		8	3	0	0	1	1		0	0	L	Add to {error file}: {HIERARCHICAL INFORMATION} – unidentified process, format {format}, bell-I{bell-I}
19	{footnote file}<!--plsfield:END--> <!--plsfield:USCDOC-->{USCDoc} <!--plsfield:CITE--><table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules=“rows”><tr width=“600”><td width=“120”>  </td><td width=“480” align="left"><font size=“3”>U.S.C. {HIERARCHICAL INFORMATION}₁:	<p id=“blankline”><!--plsfield:EXPCITE--> {HIERARCHICAL INFORMATION}₁</p id=“blankline”></td></tr></table> <table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules=“rows”><!--plsfield:HEAD--><tr width=“600”><td width=“120”>  </td><td width=“480” align="justify”><div align="justify"><font size=“3”><b> {Act}</b></font></div></td></tr></table ><!--plsfield:COD-->	8	3	14	10	2	1		0	0	J	(1) Set {leading} and {greatest indent} to zero. - - - (2) Set {text field} to: COD - - - (3) Set {footnote divider file} to: <font size=“2”> ____________ </font> </td></tr><tr> <td> </td> <td> - - - (4) After outputting the “precede text with” material, clear out {footnote file} - - - (5) In addition to outputting the text between the bell-I01 and the next locator, also store[463] the text as {Act} - - - (6) increment {USCDoc} by one.	Table of Popular Names (A.A.A. Farm Relief and Inflation Act)
20	{footnote file}<!--plsfield:END--> <!--plsfield:USCDOC-->{USCDoc} <!--plsfield:CITE--><table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules=“rows”><tr width=“600”><td width=“120”>  </td><td width=“480” align="left"><font size=“3”>U.S.C. {HIERARCHICAL INFORMATION}₁:	<p id=“blankline”><!—plsfield:EXPCITE--> {HIERARCHICAL INFORMATION}₁</p id=“blankline”></td></tr></table> <table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules=“rows”><!—plsfield:HEAD--><tr width=“600”><td width=“120”>  </td><td width=“480” align="justify”> <div align="justify"><font size=“3”><b> {Act}</b></font></div></td></tr></table ><!--plsfield:COD-->	8	3	14	10	2	1		0	0	J	(1) Set {leading} and {greatest indent} to zero. - - - (2) Set {text field} to: COD - - - (3) Set {footnote divider file} to: <font size=“2”> ____________ </font> </td></tr><tr> <td> </td> <td> - - - (4) After outputting the “precede text with” material, clear out {footnote file} - - - (5) In addition to outputting the text between the bell-I01 and the next locator, also store[464] the text as {Act} _{- - -} (6) Add to {error file}: {HIERARCHICAL INFORMATION}₁, – warning – verify implementation of format {format}, bell {bell-I} - - - (7) increment {USCDoc} by one.
21 to 92	<!-- UNDEFINED LOCATOR, format {format}, bell-I{bell-I} -->		8	3	0	0	1	1		0	0	L	Add to {error file}: {HIERARCHICAL INFORMATION} – unidentified process, format {format}, bell-I{bell-I}
93	<table width="600" border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none">{Leading file}<tr><td align=“left” valign="top" width="240"><font size=“1”>	</font></td>	6	1	7	0	1	1	1	0	0	L	(1) FOTP processing _{- - -} (2) Add to {error file}: {HIERARCHICAL INFORMATION}₁, – warning – verify implementation of format {format}, bell {bell-I}
94 to 96	<!-- UNDEFINED LOCATOR, format {format}, bell-I{bell-I} -->		8	3	0	0	1	1		0	0	L	Add to {error file}: {HIERARCHICAL INFORMATION} – unidentified process, format {format}, bell-I{bell-I}
97	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none"> {Leading file}<tr><td width=“120”>  </td><td align=“left” width=“480”>                        <strong><font color=“#FFFFFF” size=“3”>Improper locator code</font></strong><!--I97--><font size=“3”>	</font></td></tr> </table>	8	3	666	0	1	1		24	0	L	Add to {error file}: [HIERARCHICAL INFORMATION}₁ – improper locator, format {format}, bell-I97
98	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none"> {Leading file}<tr><td width=“120”> </td><td width=“480” align=“right”><strong><font color=“#FFFFFF” size=“3”>Improper locator code</font></strong> <!--I98--> <font size=“3”>	</font></td></tr> </table>	8	3	8	0	1	1		0	0	R	Add to {error file}: [HIERARCHICAL INFORMATION}₁ – improper locator, format {format}, bell-I98
99	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none"> {Leading file}<tr><td width=“120”>  </td><td align=“left” width=“480”><strong><font color=“#FFFFFF” size=“3”>Improper locator code</font></strong> <!--I99--> <font size=“3”>	</font></td></tr> </table>	8	3	8	0	1	1		0	0	L	Add to {error file}: [HIERARCHICAL INFORMATION}₁ – improper locator, format {format}, bell-I99
Any other	<!-- UNDEFINED LOCATOR, format {format}, bell-I{bell-I} -->		8	3	0	0	1	1		0	0	L	Add to {error file}: {HIERARCHICAL INFORMATION} – unidentified process, format {format}, bell-I{bell-I}

Format 5811
%I	Precede text with	Follow text with	Font size in points	HTML font size	Top lead- ing	Bottom leading	Type-face	G r i d	F O T P	PI[465]	SI [466]	LT[467]	Special processing	Example at
01	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules=“rows”>{Leading file}<tr width=“600”><td width=“120”> </td><td width=“480” align="center"><font size=“2”>	</font></td></tr> </table>	7	2	8	0	1	1		0	0	C	Add to {error file}: {HIERARCHICAL INFORMATION}₁, – warning – verify implementation of format {format}, bell-I01.
02	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules=“rows”>{Leading file}<tr width=“600”><td width=“120”> </td><td width=“480” align="justify"><div align="justify">        <!-- -->	</div></td></tr></table>	8	3	9	0	1	1		16	0	J		Table I (prec. Abbrevia-tions)
03	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules=“rows”>{Leading file}<tr width=“600”><td width=“120”>  </td><td width=“480” align="center"><font size=“1”></font> </td></tr></table>		3	1	10	16	1	1		189	189	L		Table I (prec. Abbrevia-tions)
04	{footnote file}<!--plsfield:END--> <!--plsfield:USCDOC-->{USCDoc} <!--plsfield:CITE--><table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules=“rows”><tr width=“600”><td width=“120”>  </td><td width=“480” align="left"><font size=“3”>U.S.C.	<p id=“blankline”><!--plsfield:EXPCITE--> {HIERARCHICAL INFORMATION}₁</p id=“blankline”></td></tr></table> <table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules=“rows”><tr width=“600”><td width=“120”>  </td><td width=“480” align="center"><font size=“5”><b> {HIERARCHICAL INFORMATION}₁ </b></font></td></tr> </table ><!--plsfield:HEAD-->	10	5	11	0	2	1		0	0	C	(1) Set {leading} and {greatest indent} to zero. - - - (2) Set {text field} to: HEAD - - - (3) Set {footnote divider file} to: <font size=“2”> ____________ </font> </td></tr><tr> <td> </td> <td> - - - (4) After outputting the “precede text with” material, clear out {footnote file} - - - (5) In addition to outputting the text between the bell-I04 and the next locator, also store[468] the text as {HIERARCHICAL INFORMATION}₁ - - - (6) Increment {USCDoc} by one.	Table I (catchline)
05	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none">{Leading file}<tr><td width=“120”>  </td><td width=“480” align=“center”><font size=“3”><i>	</i></font></td></tr> </table>	8	3	9	0	3	1		0	0	C	(1) If the locator-05 is followed immediately by a bell-T1, then : (a) in addition to outputting the text between the bell-I05 and the next locator, also store[469] it as {TITLE} (b) add the following before the “precede text with” material: {footnote file}<!--plsfield:END--><!--plsfield:USCDOC-->{USCDoc}<!--plsfield:CITE--> <table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none"><tr width=“600”><td width=“120”>  </td><td width=“480” align=“left”><font size=“3”>{Title} </table><table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none"><tr width=“600”><td width=“120”>  </td><td width=“480”><!--plsfield:EXPCITE--> {HIERARCHICAL INFORMATION}₁ </font></td></tr> </table> - - - (2) increment {USCDoc} by one.	Table I (Abbrevia-tions)
06			8	3	8	0	1	1		0	0	C	Do not output this material. Store it, instead, as {HIERARCHICAL INFORMATION}₁	Table I (running head)
07	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none">{Leading file}<tr width=“600”><td width=“120”> </td><td width=“218” align=“center” valign=“top”><font size=“1”><b>	</b></font></td>	6	1	14	0	2	1	1	0	0	C	FOTP processing	Table VI
08	<td width=“5”> </td><td width=“257” align=“center” valign=“top”><font size=“1”><b>	</b></font></td>	6	1	14	0	2	1	5	96	0	C	FOTP processing	Table VI
09	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none">{Leading file}<tr width=“600”><td width=“120”> </td><td width=“218” align=“left” valign=“top”><font size=“1”><hr width=“218”></hr>	</font></td>	3	1	4	7	1	1	1	0	0	L	FOTP processing	Table VI
10	<td width=“5”> </td><td width=“257” align=“left” valign=“top”><font size=“1”><hr width=“257”></hr>	</font></td>	3	1	4	7	1	1	5	96	0	L	FOTP processing	Table VI
11	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none">{Leading file}<tr width=“600”><td width=“120”> </td><td width=“162” align=“center” valign=“top”><font size=“1”><b>	</b></font></td>	6	1	7	0	2	1	1	0	0	C	FOTP processing	Table VI
12	<td width=“5”> </td><td width=“51” align=“center” valign=“top”><font size=“1”><b>	</b></font></td>	6	1	7	0	2	1	4	72	72	C	FOTP processing	Table VI
13	<td width=“5”> </td><td width=“65” align=“center” valign=“top”><font size=“1”><b>	</b></font></td>	6	1	7	0	2	1	5	96	96	C	FOTP processing	Table VI
14	<td width=“5”> </td><td width=“100” align=“center” valign=“top”><font size=“1”><b>	</b></font></td>	6	1	7	0	2	1	6	130	130	C	FOTP processing	Table VI
15	<td width=“5”> </td><td width=“72” align=“center” valign=“top”><font size=“1”><b>	</b></font></td>	6	1	7	0	2	1	7	175	175	C	FOTP processing	Table VI
16	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none">{Leading file}<tr width=“600”><td width=“120”> </td><td width=“162” align=“center” valign=“top”><font size=“1”><b>	</b></font></td>	6	1	16	12	2	1	1	0	0	C	FOTP processing	Table VI
17 to 20	<!-- UNDEFINED LOCATOR, format {format}, bell-I{bell-I} -->		8	3	0	0	1	1		0	0	L	Add to {error file}: {HIERARCHICAL INFORMATION} – unidentified process, format {format}, bell-I{bell-I}
21	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none">{Leading file}<tr width=“600”><td width=“120”> </td><td width=“42” align=“left” valign=“top”><font size=“1”>	</font></td>	6	1	0	0	1	1	1	0	0	L	FOTP processing	Table VI
22	<td width=“5”> </td><td width=“23” align=“right” valign=“top”><font size=“1”>	</font></td>	6	1	0	0	1	1	2	20	20	R	FOTP processing	Table VI
23	<td width=“5”> </td><td width=“87” align=“left” valign=“top”><font size=“1”>	</font></td>	6	1	0	0	1	1	3	32	32	L	FOTP processing	Table VI
24	<td width=“5”> </td><td width=“51” align=“right” valign=“top”><font size=“1”>	</font></td>	6	1	0	0	1	1	4	72	72	R	FOTP processing	Table VI
25	<td width=“5”> </td><td width=“65” align=“right” valign=“top”><font size=“1”>	</font></td>	6	1	0	0	1	1	5	96	96	R	FOTP processing	Table VI
26	<td width=“22”> </td><td width=“100” align=“left” valign=“top”><font size=“1”> <!-- -->	</font></td>	6	1	0	0	1	1	6	136	142	L	FOTP processing	Table VI
27	<td width=“22”> </td><td width=“60” align=“left” valign=“bottom”><font size=“1”>	</font></td>	6	1	0	0	1	1	7	181	181	L	FOTP processing	Table VI
28 to 30	<!-- UNDEFINED LOCATOR, format {format}, bell-I{bell-I} -->		8	3	0	0	1	1		0	0	L	Add to {error file}: {HIERARCHICAL INFORMATION} – unidentified process, format {format}, bell-I{bell-I}
31	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none">{Leading file}<tr width=“600”><td width=“120”> </td><td width=“480” align=“center” valign=“top”><font size=“1”><b>	</b></font></td>	6	1	16	12	2	1	1	0	0	C	FOTP processing	Table VIII
32	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none">{Leading file}<tr width=“600”><td width=“120”> </td><td width=“110” align=“left” valign=“top”><font size=“1”>	</font></td>	6	1	8	0	1	1	1	0	0	L	FOTP processing	Table VIII
33	<td width=“5”> </td><td width=“47” align=“left” valign=“top”><font size=“1”>	</font></td>	6	1	0	0	1	1	2	51	51	L	FOTP processing	Table VIII
34 to 39	<!-- UNDEFINED LOCATOR, format {format}, bell-I{bell-I} -->		8	3	0	0	1	1		0	0	L	Add to {error file}: {HIERARCHICAL INFORMATION} – unidentified process, format {format}, bell-I{bell-I}
40	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none">{Leading file}<tr width=“600”><td width=“120”> </td><td width=“11” align=“center” valign=“top”><font size=“1”><b>	</b></font></td>	6	1	7	0	2	1	1	0	0	C	FOTP processing	Table VIII
41	<td width=“5”> </td><td width=“47” align=“left” valign=“top”><font size=“1”><b>	</b></font></td>	6	1	7	0	2	1	2	51	51	L	FOTP processing	Table VIII
42 to 80	<!-- UNDEFINED LOCATOR, format {format}, bell-I{bell-I} -->		8	3	0	0	1	1		0	0	L	Add to {error file}: {HIERARCHICAL INFORMATION} – unidentified process, format {format}, bell-I{bell-I}
81	<td width=“5”> </td><td width=“341” align=“justify”><div align="justify"><font size=“3”> <!-- -->	</font></div></td>	8	3	9	9	1	1	2	60	68	J	(1) FOTP processing - - - (2) Add to {error file}: {HIERARCHICAL INFORMATION}₁, – warning – verify implementation of format {format}, bell-I81.
82 to 92	<!-- UNDEFINED LOCATOR, format {format}, bell-I{bell-I} -->		8	3	0	0	1	1		0	0	L	Add to {error file}: {HIERARCHICAL INFORMATION} – unidentified process, format {format}, bell-I{bell-I}
93	<table width="600" border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none">{Leading file}<tr><td align=“left” valign="top" width="240"><font size=“1”>	</font></td>	6	1	7	0	1	1	1	0	0	L	FOTP processing	Table VI
94 to 96	<!-- UNDEFINED LOCATOR, format {format}, bell-I{bell-I} -->		8	3	0	0	1	1		0	0	L	Add to {error file}: {HIERARCHICAL INFORMATION} – unidentified process, format {format}, bell-I{bell-I}
97	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none"> {Leading file}<tr><td width=“120”>  </td><td align=“left” width=“480”>                        <strong><font color=“#FFFFFF” size=“3”>Improper locator code</font></strong><!--I97--><font size=“3”>	</font></td></tr> </table>	8	3	666	0	1	1		24	0	L	Add to {error file}: [HIERARCHICAL INFORMATION}₁ – improper locator, format {format}, bell-I97
98	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none"> {Leading file}<tr><td width=“120”> </td><td width=“480” align=“right”><strong><font color=“#FFFFFF” size=“3”>Improper locator code</font></strong> <!--I98--> <font size=“3”>	</font></td></tr> </table>	8	3	8	0	1	1		0	0	R	Add to {error file}: [HIERARCHICAL INFORMATION}₁ – improper locator, format {format}, bell-I98
99	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none"> {Leading file}<tr><td width=“120”>  </td><td align=“left” width=“480”><strong><font color=“#FFFFFF” size=“3”>Improper locator code</font></strong> <!--I99--> <font size=“3”>	</font></td></tr> </table>	8	3	8	0	1	1		0	0	L	Add to {error file}: [HIERARCHICAL INFORMATION}₁ – improper locator, format {format}, bell-I99
Any other	<!-- UNDEFINED LOCATOR, format {format}, bell-I{bell-I} -->		8	3	0	0	1	1		0	0	L	Add to {error file}: {HIERARCHICAL INFORMATION} – unidentified process, format {format}, bell-I{bell-I}

Format 5812
%I	Precede text with	Follow text with	Font size in points	HTML font size	Top lead- ing	Bottom leading	Type-face	G r i d	F O T P	PI[470]	SI [471]	LT[472]	Special processing	Example at
01	<!-- UNDEFINED LOCATOR, format {format}, bell-I{bell-I} -->		8	3	0	0	1	1		0	0	L	Add to {error file}: {HIERARCHICAL INFORMATION}₁, {Stat vol}, Act of {month} {day}, {year}, § {Stat section} – unidentified process, format {format}, bell-I{bell-I}
02	<!-- UNDEFINED LOCATOR, format {format}, bell-I{bell-I} -->		8	3	0	0	1	1		0	0	L	Add to {error file}: {HIERARCHICAL INFORMATION}₁, {Stat vol}, Act of {month} {day}, {year}, § {Stat section} – unidentified process, format {format}, bell-I{bell-I}
03	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules=“rows”>{Leading file}<tr width=“600”><td width=“120”>  </td><td width=“480” align="center"><font size=“1”></font> </td></tr></table>		4	1	10	0	1	1		189	0	L		Table III (prec. Abbrevia-tions)
04	{footnote file}<!--plsfield:END--> <!--plsfield:USCDOC-->{USCDoc} <!--plsfield:CITE--><table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules=“rows”><tr width=“600”><td width=“120”>  </td><td width=“480” align="left"><font size=“3”>U.S.C.	<p id=“blankline”><!--plsfield:EXPCITE--> {HIERARCHICAL INFORMATION}₁</p id=“blankline”></td></tr></table> <table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules=“rows”><tr width=“600”><td width=“120”>  </td><td width=“480” align="center"><font size=“5”><b> {HIERARCHICAL INFORMATION}₁ </b></font></td></tr> </table ><!--plsfield:MISC1-->	10	5	10	0	2	1		0	0	C	(1) Set {leading} and {greatest indent} to zero. - - - (2) Set {text field} to: MISC1 - - - (3) Set {footnote divider file} to: <font size=“2”> ____________ </font> </td></tr><tr> <td> </td> <td> - - - (4) After outputting the “precede text with” material, clear out {footnote file} - - - (5) Set {State vol} to: introduction - - - (6) Set {year}, {month}, and {day} to blanks. - - - (7) In addition to outputting the text between the bell-I01 and the next locator, also store[473] the text as {HIERARCHICAL INFORMATION}₁ - - - (8) Increment {USCDoc} by one.	Table III (catchline)
05	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none">{Leading file}<tr><td width=“120”>  </td><td width=“480” align=“center”><font size=“3”> <!-- -->	</font></td></tr> </table>	8	3	18	17	1	1		0	8	C		Table III (Abbrevia-tions)
06	<!-- UNDEFINED LOCATOR, format {format}, bell-I{bell-I} -->		8	3	0	0	1	1		0	0	L	Add to {error file}: {HIERARCHICAL INFORMATION}₁, {Stat vol}, Act of {month} {day}, {year}, § {Stat section} – unidentified process, format {format}, bell-I{bell-I}
07	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none">{Leading file}<tr width=“600”><td width=“120”> </td><td width=“480” align=“justify” valign=“top”><div align="justify"><font size=“2”> <!-- -->	</b></div></font></td></tr></table>	7	2	8	0	1	1		0	7	J		Table III (Abbrevia-tions)
08	<!-- UNDEFINED LOCATOR, format {format}, bell-I{bell-I} -->		8	3	0	0	1	1		0	0	L	Add to {error file}: {HIERARCHICAL INFORMATION}₁, {Stat vol}, Act of {month} {day}, {year}, § {Stat section} – unidentified process, format {format}, bell-I{bell-I}
09			6	1	14	0	2	1		0	0	C	Do not output this material. Store it, instead, as {Congress}	Table III (2^nd Cong.)
10			6	1	13	10	2	1		0	0	C	Do not output this material. Store it, instead, as {Stat vol}	Table III (2^nd Cong.)
11	{footnote file}<!--plsfield:END--> <!--plsfield:USCDOC-->{USCDoc} <!--plsfield:CITE--><table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules=“rows”><tr width=“600”><td width=“120”>  </td><td width=“480” align="left"><font size=“3”>U.S.C. {HIERARCHICAL INFORMATION}₁ ({year})<p id=“blankline”><!--plsfield:EXPCITE--> {HIERARCHICAL INFORMATION}₁</p id=“blankline”></td></tr></table> <!--plsfield:MISC1--> <table width=“100%” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules=“rows”><tr width=“100%”><td width=“18%” align="center"><font size=“1”><b> {Congress} </b></font></td><td width=“45%”>  </td><td width=“27%” align=“center”><font size=“1”><b>{USC header}</b></font></td></tr><tr><td width=“63%”> </td><td width=“27%” align=“left”><font size=“1”><hr></hr></font></td></tr><tr> <td width=“17%” align=“left”><font size=“1”><b>{Stat vol}</b></font></td> <td width=“16%”><font size=“1”><b>{Pub L header}</b></font></td><td width=“7%” align=“center”><font size=“1”><b>{Stat ch header}<b></font></td><td width=“16%” align=“center”><font size=“1”><b>{Stat section header}</b></font><td><td width=“8%” align=“center”><font size=“1”><b>{Stat page header}</b></font></td><td width=“8%” align=“center”><font size=“1”><b>{USC title header}</b></font></td><td width=“18%” align=“center”><font size=“1”><b>{USC section header}</b></font></td><td width=“10%” align=“center”><font size=“1”><b>{status header}</b></font></td></tr><tr><td width=“4%” align=“left” valign=“top”><font size=“1”>	</font></td>	6	1	7	0	1	1		0	0	L	(1) Set {leading} and {greatest indent} to zero. - - - (2) Set {text field} to: MISC1 - - - (3) Set {footnote divider file} to: <font size=“2”> ____________ </font> </td></tr><tr> <td> </td> <td> - - - (4) After outputting the “precede text with” material, clear out {footnote file} - - - (5) In addition to outputting the text between the bell-I11 and the next locator, also store[474] the text as {year}. - - - (6) Set {percent counter} to: 4 - - - (7) increment {USCDoc} by one.	Table III (June 1, 1789, § 2)
12	<td width=“6%” align=“left” valign=“top”><font size=“1”>	</font></td>	6	1	0	0	1	1		18	18	L	(1) In addition to outputting the text between the bell-I12 and the next locator, also store[475] the text as {month}. - - - (2) Add 6 to {percentage counter} - - - (3) If the previous locator was not a locator-11, then set {percentage counter} to 10 and insert the following before the “precede text with” material: <tr><td width=“4%”>  </td>	Table III (June 1, 1789, § 2; and July 27, 1789, § 1)
13	<td width=“3%” align=“right” valign=“top”><font size=“1”>	</font></td>	6	1	0	0	1	1		44	44	R	(1) In addition to outputting the text between the bell-I13 and the next locator, also store[476] the text as {day}. - - - (2) Add 3 to {percentage counter}	Table III (June 1, 1789, § 2)
14	<td width=“4%” align=“left” valign=“top”><font size=“1”>	</font></td>	6	1	0	0	1	1		58	58	L	Add 4 to {percentage counter}	Table III (June 1, 1789, § 2)
15	<td width=“10%” align=“left” valign=“top”><font size=“1”> <!-- -->	</font></td>	6	1	0	0	1	1		78	84	L	add 10 to {percentage counter}	Table III (January 22, 1902)
16	<td width=“6%” align=“left” valign=“top”><font size=“1”>	</font></td>	6	1	0	0	1	1		122	122	L	add 6 to {percentage counter}	Table III (January 22, 1902)
17	<td width=“23%” align=“left” valign=“top”><font size=“1”> <!-- -->	</font></td>	6	1	0	7	1	1	1	155	161	L	(1) In addition to outputting the text between the bell-I13 and the next locator, also store[477] the text as {Stat section}. - - - (2) If the previous locator was not a locator-25, then insert the following before the “precede text with” material: <tr><td width=“33%”>  </td> - - - (3) FOTP processing - - - (4) Add 17 to {percentage counter}	Table III (June 1, 1789, §§ 2 & 3)
18	<td width=“8%” align=“right” valign=“top”><font size=“1”> <!-- -->	</font></td>	6	1	0	7	1	1	2	230	236	R	(1) FOTP processing - - - (2) Add 8 to {percentage counter}	Table III (June 1, 1789, § 2)
19	<td width=“8%” align=“right” valign=“top”><font size=“1”> <!-- -->	</font></td>	6	1	0	7	1	1	3	266	272	R	(1) FOTP processing - - - (2) Add 8 to {percentage counter}	Table III (June 1, 1789, § 2)
20	<td width=“18%” align=“left” valign=“top”><font size=“1”> <!-- -->	</font></td>	6	1	0	7	1	1	4	303	309	L	(1) FOTP processing - - - (2) Add 18 to {percentage counter} - - - (3) If {percentage counter} does not equal 90, then add to {error file}: {HIERARCHICAL INFORMATION}₁, {Stat vol}, Act of {month} {day}, {year}, § {Stat section} – error –improperly positioned line of text	Table III (June 1, 1789, § 2)
21	<td width=“10%” align=“left” valign=“top”><font size=“1”> <!-- -->	</font></td>	6	1	0	7	1	1	5	384	391	L	(1) FOTP processing - - - (3) If {percentage counter} does not equal 100, then add to {error file}: {HIERARCHICAL INFORMATION}₁, {Stat vol}, Act of {month} {day}, {year}, § {Stat section} – error –improperly positioned line of text	Table III (June 1, 1789, § 2)
22	<!-- UNDEFINED LOCATOR, format {format}, bell-I{bell-I} -->		8	3	0	0	1	1		0	0	L	Add to {error file}: {HIERARCHICAL INFORMATION}₁, {Stat vol}, Act of {month} {day}, {year}, § {Stat section} – unidentified process, format {format}, bell-I{bell-I}
23	<!-- UNDEFINED LOCATOR, format {format}, bell-I{bell-I} -->		8	3	0	0	1	1		0	0	L	Add to {error file}: {HIERARCHICAL INFORMATION}₁, {Stat vol}, Act of {month} {day}, {year}, § {Stat section} – unidentified process, format {format}, bell-I{bell-I}
24	<!-- UNDEFINED LOCATOR, format {format}, bell-I{bell-I} -->		8	3	0	0	1	1		0	0	L	Add to {error file}: {HIERARCHICAL INFORMATION}₁, {Stat vol}, Act of {month} {day}, {year}, § {Stat section} – unidentified process, format {format}, bell-I{bell-I}
25	<td width=“16%” align=“left” valign=“top”><font size=“1”> <!-- -->	</font></td>	6	1	0	0	1	1		78	84	L	add 16 to {percentage counter}	Table III (June 1, 1789, § 2)
26	<td width=“6%” align=“left” valign=“top”><font size=“1”>	</font></td>	6	1	0	0	1	1		122	122	L	add 6 to {percentage counter}	Table III (February 7, 1902)
27	<!-- UNDEFINED LOCATOR, format {format}, bell-I{bell-I} -->		8	3	0	0	1	1		0	0	L	Add to {error file}: {HIERARCHICAL INFORMATION}₁, {Stat vol}, Act of {month} {day}, {year}, § {Stat section} – unidentified process, format {format}, bell-I{bell-I}
28	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="none" rules="none"> {Leading file}<tr><td width=“120”>  </td><td width=“480”>{footnote divider file}<div align=“justify”><font size=“1”>      <!-- -->	</div></font></td> </tr></table>	6	1	8	0	1	1		12	0	J	(1) if the {footnote file} is not empty, then set the {leading file} and the {footnote divider file} to a blank. - - - (2) Increment {footnote switch} by one. - - - (3) Do not output this material. Add it, instead, to the {footnote file} for use with document breaks (e.g., locator 80 (in formats 5800 to 5803) and bell-R)	Table III (July 1, 1870)
29 to 40	<!-- UNDEFINED LOCATOR, format {format}, bell-I{bell-I} -->		8	3	0	0	1	1		0	0	L	Add to {error file}: {HIERARCHICAL INFORMATION}₁, {Stat vol}, Act of {month} {day}, {year}, § {Stat section} – unidentified process, format {format}, bell-I{bell-I}
41	<tr><td width=“4%”>  </td><td width=“6%” align=“left” valign=“top”><font size=“1”>	</font></td>	6	1	0	0	1	1		18	18	L	(1) add 10 to {percentage counter} - - - (2) Add to {error file}: {HIERARCHICAL INFORMATION}₁, {Stat vol}, Act of {month} {day}, {year}, § {Stat section} – warning – verify implementation of format {format}, bell-I{bell-I}
42 to 54	<!-- UNDEFINED LOCATOR, format {format}, bell-I{bell-I} -->		8	3	0	0	1	1		0	0	L	Add to {error file}: {HIERARCHICAL INFORMATION}₁, {Stat vol}, Act of {month} {day}, {year}, § {Stat section} – unidentified process, format {format}, bell-I{bell-I}
55			6	1	0	0	2	1		78	78	C	Do not output this material. Store it, instead, as {Pub L header}	Table III (1^st Cong.)
56			6	1	0	0	2	1		78	78	C	(1) Do not output this material. Store it, instead, as {Pub L header} - - - (2) Add to {error file}: {HIERARCHICAL INFORMATION}₁, {Stat vol}, Act of {month} {day}, {year}, § {Stat section} – warning – verify implementation of format {format}, bell-I{bell-I}
57 to 58	<!-- UNDEFINED LOCATOR, format {format}, bell-I{bell-I} -->		8	3	0	0	1	1		0	0	L	Add to {error file}: {HIERARCHICAL INFORMATION}₁, {Stat vol}, Act of {month} {day}, {year}, § {Stat section} – unidentified process, format {format}, bell-I{bell-I}
59			6	1	24	0	2	1		0	0	C	Do not output this material. Store it, instead, as {Congress}	Table III (1^st Cong.)
60			6	1	0	0	2	1		266	266	C	Do not output this material. Store it, instead, as {USC header}	Table III (1^st Cong.)
61			3	3	3	0	1	1		0	0	L	Do not output this material.	Table III (1^st Cong.)
62			6	1	10	0	2	1		0	0	C	Do not output this material. Store it, instead, as {Stat vol}	Table III (1^st Cong.)
63			6	1	0	0	2	1		78	78	C	Do not output this material. Store it, instead, as {Pub L header}	Table III (57^th Cong.)
64			6	1	0	0	2	1		122	122	C	Do not output this material. Store it, instead, as {Stat ch header}	Table III (1^st Cong.)
65			6	1	0	0	2	1		155	155	C	Do not output this material. Store it, instead, as {Stat section header}	Table III (1^st Cong.)
66			6	1	0	0	2	1		230	236	C	Do not output this material. Store it, instead, as {Stat page header}	Table III (1^st Cong.)
67			6	1	0	0	2	1		266	272	C	Do not output this material. Store it, instead, as {USC title header}	Table III (1^st Cong.)
68			6	1	0	0	2	1		300	306	C	Do not output this material. Store it, instead, as {USC section header}	Table III (1^st Cong.)
69			6	1	0	10	2	1		384	384	C	Do not output this material. Store it, instead, as {status header}	Table III (1^st Cong.)
70 to 71	<!-- UNDEFINED LOCATOR, format {format}, bell-I{bell-I} -->		8	3	0	0	1	1		0	0	L	Add to {error file}: {HIERARCHICAL INFORMATION}₁, {Stat vol}, Act of {month} {day}, {year}, § {Stat section} – unidentified process, format {format}, bell-I{bell-I}
72			6	1	10	0	2	1		0	0	C	(1) Do not output this material. Store it, instead, as {Stat vol} - - - (2) Add to {error file}: {HIERARCHICAL INFORMATION}₁, {Stat vol}, Act of {month} {day}, {year}, § {Stat section} – warning – verify implementation of format {format}, bell-I{bell-I}
73			6	1	0	0	2	1		78	78	C	(1) Do not output this material. Store it, instead, as {Pub L header} - - - (2) Add to {error file}: {HIERARCHICAL INFORMATION}₁, {Stat vol}, Act of {month} {day}, {year}, § {Stat section} – warning – verify implementation of format {format}, bell-I{bell-I}
74			6	1	0	0	2	1		122	122	C	(1) Do not output this material. Store it, instead, as {Stat ch header} - - - (2) Add to {error file}: {HIERARCHICAL INFORMATION}₁, {Stat vol}, Act of {month} {day}, {year}, § {Stat section} – warning – verify implementation of format {format}, bell-I{bell-I}
75	<table width=“100%” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules=“rows”><tr width=“100%”><td width=“100%” align=“left”><font size=“1”>	</font></td></tr> </table>	1	1	0	0	1	1		0	0	L	Add to {error file}: {HIERARCHICAL INFORMATION}₁, {Stat vol}, Act of {month} {day}, {year}, § {Stat section} – warning – verify implementation of format {format}, bell-I{bell-I}
76 to 77	<!-- UNDEFINED LOCATOR, format {format}, bell-I{bell-I} -->		8	3	0	0	1	1		0	0	L	Add to {error file}: {HIERARCHICAL INFORMATION}₁, {Stat vol}, Act of {month} {day}, {year}, § {Stat section} – unidentified process, format {format}, bell-I{bell-I}
78	<td width=“16%” align=“left” valign=“top”><font size=“1”>	</font></td>	6	1	0	0	1	1		78	78	L	(1) add 16 to {percentage counter} - - - (2) Add to {error file}: {HIERARCHICAL INFORMATION}₁, {Stat vol}, Act of {month} {day}, {year}, § {Stat section} – warning – verify implementation of format {format}, bell-I{bell-I}
79	<!-- UNDEFINED LOCATOR, format {format}, bell-I{bell-I} -->		8	3	0	0	1	1		0	0	L	Add to {error file}: {HIERARCHICAL INFORMATION}₁, {Stat vol}, Act of {month} {day}, {year}, § {Stat section} – unidentified process, format {format}, bell-I{bell-I}
80	<tr width=“100%”><td width=“100%” align=“left”><font size=“1”>	</font></td>	6	1	0	0	1	1		0	0	L	Add to {error file}: {HIERARCHICAL INFORMATION}₁, {Stat vol}, Act of {month} {day}, {year}, § {Stat section} – warning – verify implementation of format {format}, bell-I{bell-I}
81	<td width=“3%” align=“right”><font size=“1”>	</font></td>	6	1	0	0	1	1		44	44	R	Add to {error file}: {HIERARCHICAL INFORMATION}₁, {Stat vol}, Act of {month} {day}, {year}, § {Stat section} – warning – verify implementation of format {format}, bell-I{bell-I}
82	<!-- UNDEFINED LOCATOR, format {format}, bell-I{bell-I} -->		8	3	0	0	1	1		0	0	L	Add to {error file}: {HIERARCHICAL INFORMATION}₁, {Stat vol}, Act of {month} {day}, {year}, § {Stat section} – unidentified process, format {format}, bell-I{bell-I}l
83			6	1	0	0	2	1		78	78	L	(1) Do not output this material. Store it, instead, as {Pub L header} - - - (2) Add to {error file}: {HIERARCHICAL INFORMATION}₁, {Stat vol}, Act of {month} {day}, {year}, § {Stat section} – warning – verify implementation of format {format}, bell-I{bell-I}
84			6	1	0	0	2	1		122	122	C	(1) Do not output this material. Store it, instead, as {Stat ch header} - - - (2) Add to {error file}: {HIERARCHICAL INFORMATION}₁, {Stat vol}, Act of {month} {day}, {year}, § {Stat section} – warning – verify implementation of format {format}, bell-I{bell-I}
85 to 88	<!-- UNDEFINED LOCATOR, format {format}, bell-I{bell-I} -->		8	3	0	0	1	1		0	0	L	Add to {error file}: {HIERARCHICAL INFORMATION}₁, {Stat vol}, Act of {month} {day}, {year}, § {Stat section} – unidentified process, format {format}, bell-I{bell-I}
89			6	1	0	0	2	1		0	0	C	(1) Do not output this material. Store it, instead, as {Congress} - - - (2) (2) Add to {error file}: {HIERARCHICAL INFORMATION}₁, {Stat vol}, Act of {month} {day}, {year}, § {Stat section} – warning – verify implementation of format {format}, bell-I{bell-I}
90 or 96	<!-- UNDEFINED LOCATOR, format {format}, bell-I{bell-I} -->		8	3	0	0	1	1		0	0	L	Add to {error file}: {HIERARCHICAL INFORMATION}₁, {Stat vol}, Act of {month} {day}, {year}, § {Stat section} – unidentified process, format {format}, bell-I{bell-I}
97	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none"> {Leading file}<tr><td width=“120”>  </td><td align=“left” width=“480”>                        <strong><font color=“#FFFFFF” size=“3”>Improper locator code</font></strong><!--I97--><font size=“3”>	</font></td></tr> </table>	8	3	666	0	1	1		24	0	L	Add to {error file}: {HIERARCHICAL INFORMATION}₁, {Stat vol}, Act of {month} {day}, {year}, § {Stat section} – improper locator, format {format}, bell-I97
98	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none"> {Leading file}<tr><td width=“120”> </td><td width=“480” align=“right”><strong><font color=“#FFFFFF” size=“3”>Improper locator code</font></strong><!--I98--><font size=“3”>	</font></td></tr> </table>	8	3	8	0	1	1		0	0	R	Add to {error file}: {HIERARCHICAL INFORMATION}₁, {Stat vol}, Act of {month} {day}, {year}, § {Stat section} – improper locator, format {format}, bell-I98
99	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none"> {Leading file}<tr><td width=“120”>  </td><td align=“left” width=“480”><strong><font color=“#FFFFFF” size=“3”>Improper locator code</font></strong><!--I99--><font size=“3”>	</font></td></tr> </table>	8	3	8	0	1	1		0	0	L	Add to {error file}: {HIERARCHICAL INFORMATION}₁, {Stat vol}, Act of {month} {day}, {year}, § {Stat section} – improper locator, format {format}, bell-I99
Any other	<!-- UNDEFINED LOCATOR, format {format}, bell-I{bell-I} -->		8	3	0	0	1	1		0	0	L	Add to {error file}: {HIERARCHICAL INFORMATION}₁, {Stat vol}, Act of {month} {day}, {year}, § {Stat section} – unidentified process, format {format}, bell-I{bell-I}

Format 5813
%I	Precede text with	Follow text with	Font size in points	HTML font size	Top lead- ing	Bottom leading	Type-face	G r i d	F O T P	PI[478]	SI [479]	LT[480]	Special processing	Example at
01	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules=“rows”>{Leading file}<tr width=“600”><td width=“120”> </td><td width=“480” align="center"><font size=“2”>	</font></td></tr> </table>	7	2	8	0	1	1		0	0	C	Add to {error file}: {HIERARCHICAL INFORMATION}₁, – warning – verify implementation of format {format}, bell-I01.
02	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules=“rows”>{Leading file}<tr width=“600”><td width=“120”> </td><td width=“480” align="justify"><div align="justify">	</div></td></tr></table>	8	3	9	0	1	1		0	0	J	Add to {error file}: {HIERARCHICAL INFORMATION}₁, – warning – verify implementation of format {format}, bell-I02.
03	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules=“rows”>{Leading file}<tr width=“600”><td width=“120”>  </td><td width=“480” align="center"><font size=“1”></font> </td></tr></table>		3	1	10	16	1	1		189	189	L		Table IV (prec. table)
04	{footnote file}<!--plsfield:END--> <!--plsfield:USCDOC-->{USCDoc} <!--plsfield:CITE--><table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules=“rows”><tr width=“600”><td width=“120”>  </td><td width=“480” align="left"><font size=“3”>U.S.C.	<p id=“blankline”><!--plsfield:EXPCITE--> {HIERARCHICAL INFORMATION}₁</p id=“blankline”></td></tr></table> <table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules=“rows”><tr width=“600”><td width=“120”>  </td><td width=“480” align="center"><font size=“5”><b> {HIERARCHICAL INFORMATION}₁ </b></font></td></tr> </table ><!--plsfield:HEAD-->	10	5	11	0	2	1		0	0	C	(1) Set {leading} and {greatest indent} to zero. - - - (2) Set {text field} to: HEAD - - - (3) Set {footnote divider file} to: <font size=“2”> ____________ </font> </td></tr><tr> <td> </td> <td> - - - (4) After outputting the “precede text with” material, clear out {footnote file} - - - (5) In addition to outputting the text between the bell-I01 and the next locator, also store[481] the text as {HIERARCHICAL INFORMATION}₁ - - - (6) Increment {USCDoc} by one.	Table IV (catchline)
05	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none">{Leading file}<tr><td width=“120”> </td><td width=“480” align=“center”><font size=“3”><i>	</i></font></td></tr> </table>	8	3	9	0	3	1		0	0	C		Table IV (prec. table)
06			8	3	8	0	1	1		0	0	C	Delete all of the material between the locator-06 and the next locator	Table IV (running head)
07 to 09	<!-- UNDEFINED LOCATOR, format {format}, bell-I{bell-I} -->		8	3	0	0	1	1		0	0	L	Add to {error file}: {HIERARCHICAL INFORMATION}₁ – unidentified process, format {format}, bell-I{bell-I}
10	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none">{Leading file}<tr><td width=“120”> </td><td width=“480” align=“justify”><div align="justify"><font size=“3”>	</font></div></td></tr></table>	8	3	0	0	1	1		0	0	J	Add to {error file}: {HIERARCHICAL INFORMATION}₁ – warning – verify implementation of format {format}, bell-I{bell-I}
11 to 92	<!-- UNDEFINED LOCATOR, format {format}, bell-I{bell-I} -->		8	3	0	0	1	1		0	0	L	Add to {error file}: {HIERARCHICAL INFORMATION}₁ – unidentified process, format {format}, bell-I{bell-I}
93	<table width="600" border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none">{Leading file}<tr><td width=“120”> </td><td align=“left” valign="top" width="240"><font size=“1”>	</font></td>	6	1	7	0	1	1	1	0	0	L	(1) FOTP processing - - - (2) Add to {error file}: {HIERARCHICAL INFORMATION}₁ – warning – verify implementation of format {format}, bell-I{bell-I}
94	<td width=“9”> </td><td width=“231” align=“right” valign=“bottom”>	</font></td>	6	1	7	0	1	1	2	0	0	R	(1) FOTP processing - - - (2) Add to {error file}: {HIERARCHICAL INFORMATION}₁ – warning – verify implementation of format {format}, bell-I{bell-I}
95	<table width="600" border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none">{Leading file}<tr><td width=“120”> </td><td align=“justify” valign="top" width="240"><div align="justify"><font size=“3”><b> <!-- -->	</b></font></div></td>	8	3	10	0	2	1	1	0	16	J	(1) FOTP processing - - - (2) Add to {error file}: {HIERARCHICAL INFORMATION}₁ – warning – verify implementation of format {format}, bell-I{bell-I}
96	<td width=“14”> </td><td width=“226” align=“right” valign=“bottom”><b>	</b></font></td>	8	3	10	0	2	1	2	0	0	R	(1) FOTP processing - - - (2) Add to {error file}: {HIERARCHICAL INFORMATION}₁ – warning – verify implementation of format {format}, bell-I{bell-I}
97	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none"> {Leading file}<tr><td width=“120”>  </td><td align=“left” width=“480”>                        <strong><font color=“#FFFFFF” size=“3”>Improper locator code</font></strong><!--I97--><font size=“3”>	</font></td></tr> </table>	8	3	666	0	1	1		24	0	L	Add to {error file}: [HIERARCHICAL INFORMATION}₁ – improper locator, format {format}, bell-I97
98	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none"> {Leading file}<tr><td width=“120”> </td><td width=“480” align=“right”><strong><font color=“#FFFFFF” size=“3”>Improper locator code</font></strong> <!--I98--> <font size=“3”>	</font></td></tr> </table>	8	3	8	0	1	1		0	0	R	Add to {error file}: [HIERARCHICAL INFORMATION}₁ – improper locator, format {format}, bell-I98
99	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none"> {Leading file}<tr><td width=“120”>  </td><td align=“left” width=“480”><strong><font color=“#FFFFFF” size=“3”>Improper locator code</font></strong> <!--I99--> <font size=“3”>	</font></td></tr> </table>	8	3	8	0	1	1		0	0	L	Add to {error file}: [HIERARCHICAL INFORMATION}₁ – improper locator, format {format}, bell-I99
Any other	<!-- UNDEFINED LOCATOR, format {format}, bell-I{bell-I} -->		8	3	0	0	1	1		0	0	L	Add to {error file}: {HIERARCHICAL INFORMATION} – unidentified process, format {format}, bell-I{bell-I}

Formats 58001 to 58009
%I	Precede text with	Follow text with	Font size in points	HTML font size	Top lead- ing	Bottom leading	Type-face	G r i d	F O T P	PI[482]	SI [483]	LT[484]	Special processing	Example at
01 to 03	[same as format 5800]
04	<!--plsfield:HEAD--><table width=“100%” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none"> {Leading file}<tr><td width=“120”> </td><td width=“480” align="center"><font size=“5”><b>	</b></font></td></tr> </table><!--plsfield:STATUE-->	10	5	11	0	2	1		0	0	C	Set {text field} to: STATUTE	Declaration of Independence (catchline)
05	[same as format 5800]
06	{footnote file}<!--plsfield:END--> <!--plsfield:USCDOC-->{USCDoc} <!--plsfield:CITE--><table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame=“void” rules=“none”><tr width=“600”><td width=“120”> </td><td width=“480”><font size=“3”>USC	<p id=“blankline”><!--plsfield:EXPCITE--> {HIERARCHICAL INFORMATION}₁ <br></br></p id=“blankline”></td> </tr></table>	8	3	0	0	1	1		0	0	C	(1) Set {greatest indent} and {TITLE NUMBER} to zero. - - - (2) In addition to outputting the text between the bell-I06 and the next bell[485], also store the text as {HIERARCHICAL INFORMATION}₁ - - - (3) Set {footnote divider file} to: <font size=“2”>____________</font></td></tr><tr> <td> </td> <td> - - - (4) Set {text field} to: EXPCITE - - - (5) Set {SECTION NUMBER} as a blank. - - - (6) After completing output of “Precede text with” material, clear out the {footnote file} - - - (7) increment {USCDoc} by one.	Declaration of Independence (running head)
07 to 79	[same as format 5800]
80	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame=“void” rules=“none”>{Leading file}<tr width=“600”><td width=“120”> </td><td width=“480” align=“left” valign=“top”><font size=“3”><b><nobr>	<!-- -->  < /nobr></b></font></td>	8	3	16	0	2	1		0	0	L	Add to {error file}: {HIERARCHICAL INFORMATION}₁, {SECTION NUMBER} – warning – verify implementation of format {format}, bell-I80.
81	[same as format 5800]													Constitution, art. I
82 to 88	[same as format 5800]
89	<td align=“justify” valign=“top”><div align="justify"><font size=“3”><b> <!-- -->	</b></font></div></td></tr></table>	8	3	0	14	2	1		0	16	J	Add to {error file}: {HIERARCHICAL INFORMATION}₁, {SECTION NUMBER} – warning – verify implementation of format {format}, bell-I89.
90 to 99	[same as format 5800]
Any other	<!-- UNDEFINED LOCATOR, format {format} bell-I{bell-I} -->		8	3	0	0	1	1		0	0	L	Add to {error file}: {TITLE NUMBER} USC {SECTION NUMBER}{long subsection} ({text field}) – unidentified process, format 5807, bell-I{bell-I}

Formats 58071 to 58079
%I	Precede text with	Follow text with	Font size in points	HTML font size	Top lead- ing	Bottom leading	Type-face	G r i d	F O T P	PI[486]	SI [487]	LT[488]	Special processing	Example at
01 to 21	<!-- UNDEFINED LOCATOR, format {format}, bell-I{bell-I} -->		8	3	0	0	1	1		0	0	L	Add to {error file}: {TITLE NUMBER} USC {SECTION NUMBER}{long subsection} ({text field}) – unidentified process, format {format}, bell-I{bell-I}
22	<!--	-->	8	3	16	0	1	1		0	0	C		Organic Laws prelim. page
23 to 51	<!-- UNDEFINED LOCATOR, format {format}, bell-I{bell-I} -->		8	3	0	0	1	1		0	0	L	Add to {error file}: {TITLE NUMBER} USC {SECTION NUMBER}{long subsection} ({text field}) – unidentified process, format {format}, bell-I{bell-I}
52	<!--	-->	24	7	36	36	1	3		0	0	C		Organic Laws prelim. Page
53	<!-----	-->	24	7	54	0	1	1		0	0	L		Organic Laws prelim. Page
54 to 99	<!-- UNDEFINED LOCATOR, format {format}, bell-I{bell-I} -->		8	3	0	0	1	1		0	0	L	Add to {error file}: {TITLE NUMBER} USC {SECTION NUMBER}{long subsection} ({text field}) – unidentified process, format {format}, bell-I{bell-I}
Any other	<!-- UNDEFINED LOCATOR, format {format} bell-I{bell-I} -->		8	3	0	0	1	1		0	0	L	Add to {error file}: {TITLE NUMBER} USC {SECTION NUMBER}{long subsection} ({text field}) – unidentified process, format 5807, bell-I{bell-I}

Format 58098
%I	Precede text with	Follow text with	Font size in points	HTML font size	Top lead- ing	Bottom leading	Type-face	G r i d	F O T P	PI[489]	SI [490]	LT[491]	Special processing	Example at
01	{footnote file}<!--plsfield:END--> <!--plsfield:USCDOC-->{USCDoc} <!--plsfield:CITE--><table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame=“void” rules=“none”><tr width=“600”><td width=“120”> </td><td width=“480” align=“left”><font size=“3”>U.S.C. {HIERARCHICAL INFORMATION}₁<p id=“blankline”> <!--plsfield:EXPCITE--> {HIERARCHICAL INFORMATION}₁</p id=“blankline”></td></tr></table><table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame=“void” rules=“none”><tr width=“600”><td width=“120”> </td><td width=“480” align=“center”><font size=“5”><b>	</b></font></td></tr> </table ><!--plsfield:HEAD-->	10	5	0	0	2	1		0	0	C	(1) Set {leading} and {greatest indent} to zero. - - - (2) Set {text field} to: HEAD - - - (3) Set {footnote divider file} to: <font size=“2”> ____________ </font> </td></tr><tr> <td> </td> <td> - - - (4) After outputting the “precede text with” material, clear out {footnote file} - - - (5) increment {USCDoc} by one.	Analytical Index to the Constitution (catchline)
02	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame=“void” rules=“none”>{Leading file}<tr width=“600”><td width=“120”> </td><td width=“480” align=“center”><font size=“5”><b>	</b></font></td></tr> </table>	10	5	0	0	2	1		0	0	C		Analytical Index to the Constitution (catchline)
03	<!-- UNDEFINED LOCATOR, format {format}, bell-I{bell-I} -->		8	3	0	0	1	1		0	0	L	Add to {error file}: {TITLE NUMBER} USC {SECTION NUMBER}{long subsection} ({text field}) – unidentified process, format {format}, bell-I{bell-I}
04			6	1	0	0	1	1		0	0	R	(1) Store the text up to (but not including) the first blank as {article header} - - - (2) Store the text from after the first blank up to (but not including) the second blank as {section header} - - - (3) Store the text from after the second blank up to (but not including) the next bell-I, as {clause header}	Analytical Index to the Constitution (after running head)
05			6	1	0	0	1	1		0	0	R	(1) Store the text up to (but not including) the first blank as {article header} - - - (2) Store the text from after the first blank up to (but not including) the second blank as {section header} - - - (3) Store the text from after the second blank up to (but not including) the next bell-I, as {clause header}	Analytical Index to the Constitution (after running head)
06			6	1	0	0	1	1		0	0	R	(1) Store the text up to (but not including) the first blank as {article header} - - - (2) Store the text from after the first blank up to (but not including) the second blank as {section header} - - - (3) Store the text from after the second blank up to (but not including) the next bell-I, as {clause header}	Analytical Index to the Constitution (after running head)
07			6	1	0	0	1	1		0	0	R	(1) Store the text up to (but not including) the first blank as {article header} - - - (2) Store the text from after the first blank up to (but not including) the second blank as {section header} - - - (3) Store the text from after the second blank up to (but not including) the next bell-I, as {clause header}	Analytical Index to the Constitution (after running head)
08	{footnote file}<!--plsfield:END--> <!--plsfield:USCDOC-->{USCDoc} <!--plsfield:CITE--><table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame=“void” rules=“none”><tr width=“600”><td width=“120”> </td><td width=“480” align=“left”><font size=“3”>U.S.C. {HIERARCHICAL INFORMATION}₁<p id=“blankline”> <!--plsfield:EXPCITE--> {HIERARCHICAL INFORMATION}₁</p id=“blankline”></td></tr></table><table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame=“void” rules=“none”><tr width=“600”><td width=“120”> </td><td width=“480” align=“center”><font size=“1”>	</font></td></tr> </table><table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame=“void” rules=“none”><tr width=“600”><td width=“120”>  </td><td width=“397”>  </td><td width=“28” align=“right”>{article header}</td><td width=“28” align=“right”>{section header}</td><td width=“27” align=“right”>{clause header}</td></tr> </table> <!--plsfield:MISC1-->	6	1	14	12	1	1		0	0	C	(1) Set {leading} and {greatest indent} to zero. - - - (2) Set {text field} to: MISC1 - - - (3) Set {footnote divider file} to: <font size=“2”>____________</font></td></tr><tr><td>  </td><td> - - - (4) After outputting the “precede text with” material, clear out {footnote file} - - - (5) increment {USCDoc} by one.	Analytical Index to the Constitution (A)
09	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame=“void” rules=“none”> {Leading file}<tr width=“600”><td width=“120”> </td><td width=“397” align=“justify” valign=“top”><div align="justify"><font size=“1”> <!-- -->	</font></div></td>	6	1	6	6	1	1	1	0	6	J	FOTP processing	Analytical Index to the Constitution (Abridged)
10	<td wifth=“28” align=“right” valign=“bottom”><font size=“1”>	</font></td>	6	1	0	0	1	1	2	171	0	R	FOTP processing	Analytical Index to the Constitution (Abridged)
11	<td wifth=“28” align=“right” valign=“bottom”><font size=“1”>	</font></td>	6	1	0	0	1	1	3	183	0	R	FOTP processing	Analytical Index to the Constitution (Abridged)
12	<td wifth=“27” align=“right” valign=“bottom”><font size=“1”>	</font></td>	6	1	0	0	1	1	4	195	0	R	FOTP processing	Analytical Index to the Constitution (Abridged)
13	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame=“void” rules=“none”> {Leading file}<tr width=“600”><td width=“148”> </td><td width=“369” align=“justify” valign=“top”><div align="justify"><font size=“1”> <!-- -->	</font></div></td>	6	1	6	6	1	1	1	12	18	J	FOTP processing	Analytical Index to the Constitution (Accused) (He shall be tried . . .)
14	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame=“void” rules=“none”>{Leading file}<tr width=“600”><td width=“120”> </td><td width=“480” align=“left”><font size=“1”>	</font></td></tr> </table>	3	1	108	16	1	1		189	0	L		Analytical Index to the Constitution (catchline)
15	<!-- UNDEFINED LOCATOR, format {format}, bell-I{bell-I} -->		8	3	0	0	1	1		0	0	L	Add to {error file}: {TITLE NUMBER} USC {SECTION NUMBER}{long subsection} ({text field}) – unidentified process, format {format}, bell-I{bell-I}
16	<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame=“void” rules=“none”> {Leading file}<tr width=“600”><td width=“134”> </td><td width=“383” align=“justify” valign=“top”><div align="justify"><font size=“1”>	</font></div></td>	6	1	6	6	1	1	1	6	6	J	FOTP processing	Analytical Index to the Constitution (Death) (Amend-ments)
17 to 89	<!-- UNDEFINED LOCATOR, format {format}, bell-I{bell-I} -->		8	3	0	0	1	1		0	0	L	Add to {error file}: {TITLE NUMBER} USC {SECTION NUMBER}{long subsection} ({text field}) – unidentified process, format {format}, bell-I{bell-I}
90			8	3	0	0	1	1		0	0	L	Do not output this material. Store it, instead, as {HIERARCHICAL INFORMATION}₁	Analytical Index to the Constitution (running head)
91			8	3	0	0	1	1		0	0	R	Do not output this material. Store it, instead, as {HIERARCHICAL INFORMATION}₁	Analytical Index to the Constitution (running head)
92 to 99	<!-- UNDEFINED LOCATOR, format {format}, bell-I{bell-I} -->		8	3	0	0	1	1		0	0	L	Add to {error file}: {TITLE NUMBER} USC {SECTION NUMBER}{long subsection} ({text field}) – unidentified process, format {format}, bell-I{bell-I}
any other	<!-- UNDEFINED LOCATOR, format {format}, bell-I{bell-I} -->		8	3	0	0	1	1		0	0	L	Add to {error file}: {TITLE NUMBER} USC {SECTION NUMBER}{long subsection} ({text field}) – unidentified process, format {format}, bell-I{bell-I}

Other formats
any	<!-- UNDEFINED LOCATOR: format {format}, bell-I{bell-I}	-->	8	3	0	0	1	1		999	999	L	Add to {error file}: {TITLE NUMBER} USC {SECTION NUMBER}{long subsection} ({text field}) – unidentified process, format {format}, bell-I{bell-I}

Other formats

Precede text with

Follow text with

Font

size in points

HTML

font

size

Top

lead-

ing

Bottom

leading

Type-face

PI[492]

SI [493]

LT[494]

Special processing

Example at

any

<!-- UNDEFINED LOCATOR: format {format}, bell-I{bell-I}

-->

999

Add to {error file}:

{TITLE NUMBER} USC {SECTION NUMBER}{long subsection} ({text field}) – unidentified process, format {format}, bell-I{bell-I}

Bell-K

(1) Replace the bell-K with: bell-T{original typeface}bell-G{original typeface}

(2) Process the codes according to the rules for processing bell-T and bell-G .

Bell-L

Precede the text with

<td width=“12”> </td><td align="right" width=“228”><font size=

followed by the current value of {HTML font size}, followed by

Then follow the text with

</font></td></tr></table>

Bell-N

Delete the bell-N.

Bell-P

Repeat the previous I-code (excluding any I-codes that were inside of a bell-c table).

Bell-q

The bell-q is followed by a two-digit argument[495]. Subtract the argument from {leading}.[496]

Bell-Q

The bell-Q is followed by a two-digit argument[497]. Add the argument to {leading}.[498]

Bell-R

Within titles 1 through 50, the U.S. Code is divided into sections. The sections, in turn, may be grouped together into subtitles, chapters, subchapters, parts, subparts, divisions, and/or other groupings. The hierarchy of these groupings varies from title to title (for instance, in title 3, chapters are divided into parts, while in title 26, parts are divided into chapters).

A bell-R, followed by two digits, indicates the start of a new grouping above the section level. The two-digit argument indicates where the grouping sits within the hierarchy. The lower the bell-R argument, the higher in the hierarchy the grouping is. For example a bell-R01 indicates the start of a new title – the highest hierarchical level within the U.S. Code.

Whenever a bell-R is encountered, execute these instructions:

(1) Output the contents of {footnote file} and then clear out {footnote file}.

(2) Output:

(3) If the R-code is a bell-R01, then

(a) go find the next text string that is delimited by “TITLE ” (at the start) and an em-dash (at the end). Store that string as the {TITLE NUMBER}, deleting any leading or trailing blanks.

(b) Set the value of {USCDoc} according to the formula: {USCDoc} = {TITLE NUMBER} H 10,000,000

(c) Set {appendix} to a blank.

(4) Set {leading}[499] and {greatest indent} to zero.

(5) If the R-code is a bell-R05, then

(a) set {appendix} to: app. {RUNNING HEAD}

(b) increment {USCDoc} by one.

(6) Increment {USCDoc} by one

(7) (a) Store as the {SUBDIVISION DESIGNATION}: all of the text that is between (1) the locator-code that follows the R-code and (2) the next bell-code[500].

(b) Within {SUBDIVISION DESIGNATION}, convert any special characters or ESC sequences and execute any bell-g, bell-G, bell-K, or bell-T.

(8) (a) copy the value of {SUBDIVISION DESIGNATION} to {short subdivision designation}.

(b) delete any open brackets from {short subdivision designation}[501]

(c) delete all characters within {short subdivision designation} starting with[502]: <!--

(9) Output: {USCDoc}<table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="none"><tr width=“600”><td width=“120”> </td><td width=“480” align=“left”><font size=“3”>

(10) Output the value of {TITLE NUMBER}.

(11) Output a space and the literal: USC

(12) Output: {appendix}

(13) Output a space and: {short subdivision designation}</font></td></tr></table><table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame=“void” rules=“none”><tr width=“600”><td><font size=“1”> </font></td></tr></table>

(14) (a) Within the data stored in the array {HIERARCHICAL INFORMATION}, remove any entries with an index greater than or equal to the argument of the current bell-R.

(a-1) Set {HIERARCHICAL INFORMATION}_{{bell-R argument}} to: <table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame=“void” rules=“none”><tr width=“600”><td width=“120”> </td><td width=“480” align=“left”><font size=“3”>

(b) At the end of {HIERARCHICAL INFORMATION}_{{bell-R argument}}, add the text of {SUBDIVISION DESIGNATION}

(c) At the end of {HIERARCHICAL INFORMATION}_{{bell-R argument}} add: </font></td></tr><tr></tr><tr></tr><tr></tr></table>

(15) Output:

(16) Output all of the non-blank values from the array {HIERARCHICAL INFORMATION}_{1 to 99}

(17) Output: <table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame=“void” rules=“none”><tr width=“600”><td><font size=“1”> </font></td></tr></table>

(18) Set value of {text field} to: HEAD

(18A) Set {footnote divider file} to: <font size=“2”>____________</font></td></tr><tr><td> </td><td>

(19) Resume processing with the locator-code that follows the R-code.

Bell-S

The bell-S is followed by a 4- or 5-digit argument. The argument of the bell-S is the {format} number[503] and it should be stored for later use.

The argument for a bell-S is four digits long unless the bell is preceded by

«MDNM»

where “«” is a Hex-AE and “»” is a Hex-AF. An example of the five-character F-code can be found in the analysis of the Organic Laws.

If {format} is not one of the formats defined in the Bell-I section of these specifications, then add the following to the {error file}: {TITLE NUMBER} USC {SECTION NUMBER}{long subsection} ({text field}) – invalid format: S{format}

Bell-U

Store the one-digit numeric that follows the bell-U as {bell-U argument}. Then add the following to {error file}: {TITLE NUMBER} USC{appendix}{SECTION NUMBER}{long subsection} ({text field}) – warning – verify implementation of bell-U{bell-U argument} – see Publishing from a Full Text Data Base, 2^nd edition, pages 76-78, and GPO Standardization Manual, 1/1/88, page 4.

Bell-xl

If the previous <table> tag has a rules="rows" attribute, replace the attribute with rules="none". [504]

Bell-X

(1) Add the following to {error file}: {TITLE NUMBER} USC{appendix}{SECTION NUMBER}{long subsection} ({text field}) – warning – verify the implementation of bell-X

(2) Then add to {error file} all of the text that follows the bell-X, up to (and including) the next bell-E.

(3) Finally, add to {error file}: – see Publishing from a Full Text Data Base, 2^nd edition, page 36, and Program Design Documentation, Legal Retrieval System, United States Code Database, DN-1073-1, page 22.

Bell-Y

(1) Set {bell-Y} to the one digit numeric following the bell-Y.

(2) If {bell-Y} = 1, then, in the previous <table> tag, change the “border=” value to “1” and change the “frame=” value to “lhs”.

(3) Add the following to {error file}: {TITLE NUMBER} USC{appendix}{SECTION NUMBER}{long subsection} ({text field}) – warning – verify the implementation of bell-Y{bell-Y} – see Publishing from a Full Text Data Base, 2^nd edition, pages 35 and 82-83.

Bell-Z

Delete all of the data from the bell-Z up to and including the character preceding the next bell.

Bell-01 to Bell-99

When a bell is followed immediately by a two digit-number,

(1) Store the two-digit number as {bell number}.

(2) Divide {bell number} by two and then round the number off to the nearest whole number.

(3) For each occurrence of {bell number}, insert:

For instance, if a bell-05 occurs, replace it with :

(4) Add the following to {error file}: {TITLE NUMBER} USC{appendix}{SECTION NUMBER}{long subsection} ({text field}) – warning – verify the implementation of bell-{bell number}.

Special Processing

Caps and small caps

(1) (a) Set {Small caps HTML font size} one less than the current value of {HTML font size}.

(b) If {Small caps HTML font size} = 0, then set {Small caps HTML font size} to one, and set {HTML font size} to two.[505]

(2) Examine all of the characters[506] between the current bell code and the next cell-c, bell-D[507], bell-F, bell-g, bell-G, bell-h[508], bell-I, bell-K, bell-R, bell-S, or bell-T .

(3) If the first character is a lower case letter, then precede the letter with: </font><font size={Small caps HTML font size}>

(4) In front of each upper case letter, numeral, paren, or bracket, insert:

</font><font size={HTML font size}>

(5) After each upper case letter, numeral, paren, or bracket, insert:

</font><font size={Small caps HTML font size}>

(6) Translate each lower case character into upper case.

(6A) In front of any <nobr> tag, insert: </font><font size={HTML font size}

(7) After the last character, insert:

</font><font size={HTML font size}>

Leadering

Use <table rules=“rows”>, instead of <table rules=“none”>.

FOTP Processing [509]

(1) Based on the current value of {format} and {bell-I}, determine the value of {cell width in pixels}:

{format}	{bell-I}	{cell width in pixels}
5800 to 5803 and 58001 to 58009	07	48
5800 to 5803 and 58001 to 58009	08	322
5800 to 5803 and 58001 to 58009	09	110
5800 to 5803 and 58001 to 58009	20	72
5800 to 5803 and 58001 to 58009	29	240
5800 to 5803 and 58001 to 58009	37	240
5800 to 5803 and 58001 to 58009	38	240
5800 to 5803 and 58001 to 58009	40	408
5800 to 5803 and 58001 to 58009	41	312
5800 to 5803 and 58001 to 58009	45	142
5800 to 5803 and 58001 to 58009	46	408
5800 to 5803 and 58001 to 58009	48	105
5800 to 5803 and 58001 to 58009	50	338
5800 to 5803 and 58001 to 58009	52	480
5800 to 5803 and 58001 to 58009	59	375
5800 to 5803 and 58001 to 58009	60	161
5800 to 5803 and 58001 to 58009	69	320
5800 to 5803 and 58001 to 58009	70	240
5800 to 5803 and 58001 to 58009	81	480
5800 to 5803 and 58001 to 58009	93	240
5800 to 5803 and 58001 to 58009	94	240
5800 to 5803 and 58001 to 58009	95	432
5800 to 5803 and 58001 to 58009	96	48
5804	19	408
5804	20	408
5804	25	273
5804	26	110
5804	29	240
5804	30	195
5804	31	195
5804	32	285
5804	33	285
5804	35	285
5804	36	285
5804	37	480
5804	38	322
5804	39	110
5804	40	273
5804	41	195
5804	42	185
5804	43	273
5804	44	195
5804	45	320
5804	46	320
5804	47	160
5804	49	153
5804	50	84
5804	51	159
5804	52	84
5804	53	125
5804	54	112
5804	55	131
5804	56	112
5804	57	278
5804	58	202
5804	59	390
5804	60	480
5804	62	192
5804	62	281
5804	63	480
5804	65	480
5804	70	240
5804	72	285
5804	73	261
5804	74	237
5804	75	213
5804	92	480
5804	93	480
5804	95	480
5807	57	233
5807	58	247
5810	93	240
5811	07	218
5811	08	257
5811	09	218
5811	10	257
5811	11	162
5811	12	56
5811	13	79
5811	14	105
5811	15	77
5811	16	162
5811	21	42
5811	22	28
5811	23	92
5811	24	56
5811	25	70
5811	26	122
5811	27	82
5811	31	480
5811	32	110
5811	33	52
5811	40	11
5811	41	352
5811	81	346
5811	93	240
5812	17	110.4
5812	18	38.4
5812	10	38.4
5812	20	86.4
5812	21	48
5813	93	240
5813	94	240
5813	95	140
5813	96	240
58098	09	397
58098	10	28
58098	11	28
58098	12	27
58098	13	369
58098	16	383

(2) Add the value of {cell width in pixels} to {FOTP row length in pixels}.

(3) If {FOTP row width in pixels} is greater than 480, then add the following to {error file}: {TITLE NUMBER} USC{appendix}{SECTION NUMBER}{long subsection} ({text field}) – warning – width of FOTP table cells exceeds 480 in a single row

(4) If the FOTP value of the locator that follows the text that follows the current locator

(a) is a blank, or

(b) is a numeric less than or equal to the FOTP value of the current locator,

then set {FOTP row width in pixels} to zero and insert:

</tr></table>ÃÃ

after the material contained in the “Follow Text With” column.

Graphics Processing

Graphics are included in the Code through use of the <img> tag. The general format is

The following table sets out the width, height, and alt values for each of the graphics currently in the U.S. Code:

File	Width	Height	Alt
t4flag	576	334	U.S. Flag
10AR20	576	236	caption
10AR22	576	271	caption
10AR23	576	229	caption
10AR24	576	278	caption
10AR28	576	473	caption
10AR32	576	298	caption
10AAppA	576	194	caption
10AAppB	576	235	caption
11f1p1	576	778	Bank. R. form 1, page 1
11f1p2	576	780	Bank. R. form 1, page 2
11f1p3	576	706	Bank. R. form 1, page 3
11f2p1	576	463	Bank. R. form 2
11f3p1	576	737	Bank. R. form 3, page 1
11f3p2	576	564	Bank. R. form 3, page 2
11f4p1	576	549	Bank. R. form 4
11f5p1	576	746	Bank. R. form 5, page 1
11f5p2	576	740	Bank. R. form 5, page 2
11f6p1	576	737	Bank. R. form 6, page 1
11f6p2	576	764	Bank. R. form 6, page 2
11f6p3	576	801	Bank. R. form 6, page 3
11f6p4	576	827	Bank. R. form 6, page 4
11f6p5	576	801	Bank. R. form 6, page 5
11f6p6	576	776	Bank. R. form 6, page 6
11f6p7	576	810	Bank. R. form 6, page 7
11f6p8	576	758	Bank. R. form 6, page 8
11f6p9	576	808	Bank. R. form 6, page 9
11f6p10	576	755	Bank. R. form 6, page 10
11f6p11	576	675	Bank. R. form 6, page 11
11f6p12	576	829	Bank. R. form 6, page 12
11f6p13	576	766	Bank. R. form 6, page 13
11f6p14	576	789	Bank. R. form 6, page 14
11f6p15	576	790	Bank. R. form 6, page 15
11f6p16	576	805	Bank. R. form 6, page 16
11f6p17	576	765	Bank. R. form 6, page 17
11f6p18	576	762	Bank. R. form 6, page 18
11f6p19	576	752	Bank. R. form 6, page 19
11f7p1	576	762	Bank. R. form 7, page 1
11f7p2	576	774	Bank. R. form 7, page 2
11f7p3	576	741	Bank. R. form 7, page 3
11f7p4	576	774	Bank. R. form 7, page 4
11f7p5	576	726	Bank. R. form 7, page 5
11f7p6	576	683	Bank. R. form 7, page 6
11f7p7	576	719	Bank. R. form 7, page 7
11f7p8	576	709	Bank. R. form 7, page 8
11f7p9	576	777	Bank. R. form 7, page 9
11f7p10	576	807	Bank. R. form 7, page 10
11f8p1	576	750	Bank. R. form 8
11f9p1	576	586	Bank. R. form 9, page 1
11f9p2	576	792	Bank. R. form 9, page 2
11f9p3	576	785	Bank. R. form 9, page 3
11f9p4	576	798	Bank. R. form 9, page 4
11f9p5	576	785	Bank. R. form 9, page 5
11f9p6	576	768	Bank. R. form 9, page 6
11f9p7	576	789	Bank. R. form 9, page 7
11f9p8	576	737	Bank. R. form 9, page 8
11f9p9	576	781	Bank. R. form 9, page 9
11f9p10	576	769	Bank. R. form 9, page 10
11f9p11	576	761	Bank. R. form 9, page 11
11f9p12	576	780	Bank. R. form 9, page 12
11f9p13	576	790	Bank. R. form 9, page 13
11f9p14	576	798	Bank. R. form 9, page 14
11f9p15	576	753	Bank. R. form 9, page 15
11f9p16	576	769	Bank. R. form 9, page 16
11f9p17	576	788	Bank. R. form 9, page 17
11f9p18	576	756	Bank. R. form 9, page 18
11f9p19	576	756	Bank. R. form 9, page 19
11f9p20	576	774	Bank. R. form 9, page 20
11f9p21	576	738	Bank. R. form 9, page 21
11f9p22	576	779	Bank. R. form 9, page 22
11f9p23	576	756	Bank. R. form 9, page 23
11f10p1	576	765	Bank. R. form 10, page 1
11f10p2	576	766	Bank. R. form 10, page 2
11f11a	576	647	Bank. R. form 11A
11f11b	576	665	Bank. R. form 11B
11f12	576	500	Bank. R. form 12
11f13	576	748	Bank. R. form 13
11f14p1	576	768	Bank. R. form 14, page 1
11f14p2	576	439	Bank. R. form 14, page 2
11f15	576	526	Bank. R. form 15
11f16a	576	520	Bank. R. form 16A
11f16b	576	431	Bank. R. form 16B
11f16c	576	639	Bank. R. form 16C
11f16d	576	559	Bank. R. form 16D
11f17	576	683	Bank. R. form 17
11f18p1	576	579	Bank. R. form 18, page 1
11f18p2	576	704	Bank. R. form 18, page 2
11f19	576	713	Bank. R. form 19
11f20a	576	645	Bank. R. form 20A
11f20b	576	662	Bank. R. form 20B
t151278a	576	136	warning
t151278b	576	187	warning
t151278c	576	147	warning
t151278d	576	148	warning
t151278e	576	136	warning
t151278f	576	153	warning
t151278g	576	107	warning
t151278h	576	87	warning
t154402	576	410	Warning Message
t211702	576	366	Seal of the Office of National Drug Control Policy
t26ai	576	485	T.C. R. app. I
t26f1p1	576	654	T.C. R. form 1, page 1
t26f1p2	576	304	T.C. R. form 1, page 2
t26f2	576	723	T.C. R. form 2
t26f3	576	550	T.C. R. form 3
t26f4	576	591	T.C. R. form 4
t26f5	576	371	T.C. R. form 5
t26f6p1	576	833	T.C. R. form 6, page 1
t26f6p2	576	496	T.C. R. form 6, page 2
t26f7	576	812	T.C. R. form 7
t26f8	576	821	T.C. R. form 8
t26f9	576	829	T.C. R. form 9
t26f10p1	576	852	T.C. R. form 10, page 1
t26f10p2	576	297	T.C. R. form 10, page 2
t26f11	576	849	T.C. R. form 11
t26f12	576	759	T.C. R. form 12
t26f1314	576	725	T.C. R. forms 13 and 14
t26f15	576	586	T.C. R. form 15
t26f16	576	810	T.C. R. form 16
t26aiip1	576	758	T.C. R. app. II, page 1
t26aiip2	576	238	T.C. R. app. II, page 2
t26aiii	576	479	T.C. R. app. III
t26aiv	576	803	T.C. R. app. IV
t28ae	576	751	Fed. Cl. R. app. E
t28akp1	576	814	Fed. Cl. R. app. K, page 1
t28akp2	576	609	Fed. Cl. R. app. K, page 2
t28akp3	576	745	Fed. Cl. R. app. K, page 3
t28alp1	576	669	Fed. Cl. R. app. L, page 1
t28alp2	576	677	Fed. Cl. R. app. L, page 2
t28alp3	576	648	Fed. Cl. R. app. L, page 3
t28alp4	576	671	Fed. Cl. R. app. L, page 4
t28f1p1	576	713	Ct. Int’l Trade R. form 1, page 1
t28f1p2	576	729	Ct. Int’l Trade R. form 1, page 2
t28f1p3	576	739	Ct. Int’l Trade R. form 1, page 3
t28f1a	576	700	Ct. Int’l Trade R. form 1A
t28f1b	576	693	Ct. Int’l Trade R. form 1B
t28f2p1	576	715	Ct. Int’l Trade R. form 2, page 1
t28f2p2	576	727	Ct. Int’l Trade R. form 2, page 2
t28f3p1	576	758	Ct. Int’l Trade R. form 3, page 1
t28f3p2	576	403	Ct. Int’l Trade R. form 3, page 2
t28f4	576	819	Ct. Int’l Trade R. form 4
t28f5	576	753	Ct. Int’l Trade R. form 5
t28f6	576	794	Ct. Int’l Trade R. form 6
t28f7p1	576	661	Ct. Int’l Trade R. form 7, page 1
t28f7p2	576	660	Ct. Int’l Trade R. form 7, page 2
t28f8p1	576	821	Ct. Int’l Trade R. form 8, page 1
t28f8p2	576	717	Ct. Int’l Trade R. form 8, page 2
t28f9p1	576	703	Ct. Int’l Trade R. form 9, page 1
t28f9p2	576	681	Ct. Int’l Trade R. form 9, page 2
t28f9p3	576	665	Ct. Int’l Trade R. form 9, page 3
t28f9p4	576	298	Ct. Int’l Trade R. form 9, page 4
t28f9p5	576	763	Ct. Int’l Trade R. form 9, page 5
t28f9p6	576	550	Ct. Int’l Trade R. form 9, page 6
28f10p1	576	838	Ct. Int’l Trade R. form 10, page 1
28f10p2	576	804	Ct. Int’l Trade R. form 10, page 2
t28f11	576	658	Ct. Int’l Trade R. form 11
t28f12	576	814	Ct. Int’l Trade R. form 12
t28f13p1	576	816	Ct. Int’l Trade R. form 13, page 1
t28f13p2	576	782	Ct. Int’l Trade R. form 13, page 2
t28f15p1	576	821	Ct. Int’l Trade R. form 15, page 1
t28f15p2	576	816	Ct. Int’l Trade R. form 15, page 2
t28f16	576	775	Ct. Int’l Trade R. form 16
nasa	378	342	NASA Seal
Any other file	576	{graphic depth}	unidentified graphic

If {Alt} = “unidentified graphic”, then add the following to {error file}: {TITLE NUMBER} USC {SECTION NUMBER}{long subsection} ({text field}) – unidentified graphic – {File}.

Assumptions, Questions, and Alternatives

PLS-specific elements in these Specifications

These specifications assume that PLWeb Turbo will be the search engine used with the U.S. Code database. While most of what is contained in these specifications are not search engine specific, there are several items that are specific to PLWeb. If a different search engine is used then changes may be needed in these items.

The following items in these specifications are PLWeb Turbo specific:

(1) The start of each field is indicated by a

<!--plsfield:

followed by the name of the field, and then followed by

-->

Field delimiters are generated by the following photocomposition codes:

Photocomposition code	Field
%I53 (formats 5800 to 5803)	SOURCE
%I73 (formats 5800 to 5803)	SECREF
%I74 (formats 5800 to 5803)	MISC1 to MISC8
%I75 (formats 5800 to 5803)	REFTEXT
%I76 (formats 5800 to 5803)	COD
%I78 (formats 5800 to 5803)	CHANGE
%I80 (formats 5800 to 5803)	CITE, EXPCITE, and HEAD
%I84 (formats 5800 to 5803)	STATAMEND
%I85 (formats 5800 to 5803)	TRANS
%I86 (formats 5800 to 5803)	EXEC
%I87 (formats 5800 to 5803)	CROSS
%I89 (formats 5800 to 5803)	STATUTE
%R	CITE, EXPCITE, and HEAD

(2) The end of each document is indicated by the string

(3) The doc.tmpl file contains the template used to display the text of sections of the U.S. Code. It is assumed that the doc.tmpl file should contain the following, in addition to any link bars and JavaScript[510] :

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "DTD/xhtml1-transitional.dtd">

<!--

p {position: relative; top:-2.4em}

p.blankline {position: relative; top:0em}

-->

</style>

<!--

function getdoc(a)

{

var PLUS ="+"

var STRPRX =''

var STRSUX =''

var StartPos, PlusChar, PlusCharNum, StrChar, PlusStartDb, DNum, DocNum, PlusStart

var LocationStr, StrPlus, StrMinus, StrDb, Str1, Str2, Str, StrView

LocationStr=document.location + ""

PlusStart = LocationStr.indexOf("+")

PlusStart += 1

Str1 = LocationStr.substring(0, PlusStart)

PlusChar = PlusStart

PlusCharNum=0

for ( PlusChar; StrChar = LocationStr.substring(PlusChar, PlusChar+1); PlusChar++)

{

if (StrChar == PLUS)

{

if (PlusCharNum == 0)

{

StrView = LocationStr.substring(PlusStart, PlusChar)

PlusCharNum++

StartPos = PlusChar + 1

continue

}

if (PlusCharNum == 1)

{

StrDb = LocationStr.substring(StartPos, PlusChar)

PlusCharNum++

StartPos = PlusChar + 1

continue

}

break

}

Str2 = LocationStr.substring(PlusChar, 90)

DocNum = LocationStr.substring(StartPos, PlusChar)

DNum = eval(DocNum)

if ( a < 0 )

{

DNum -= 1

if (DNum <= 0)

{ alert("There are no more documents before this one in this subdatabase!")

DNum = 1

}

else

{

DNum += 1

}

Str = STRPRX + Str1 + StrView + '+' + StrDb + '+' +DNum + Str2 + STRSUX

window.location = Str

window.location.open

}

// -->

</script>

</head><body bgcolor="#FFFFFF" onLoad=“window.defaultStatus=’ ‘“ />

<a href="http://uscode.house.gov/usc.htm">Search USC</a>,

<a href="http://uscode.house.gov/about.htm">About Database</a>,

<a href="http://uscode.house.gov/download.htm">Download USC</a>,

<a href="http://uscode.house.gov/uscct.htm">Classification Tables</a>,

<a href="http://uscode.house.gov/cod.htm">Codification</a>

</center></font>

<a href="javascript:getdoc(-1)"><img src="prevbutt.gif" rel="previous"

rev="next" border=0 with=31 height=31 alt="Previous section "></a>

<a href="javascript:getdoc(1) "> <img src="nextbutt.gif" rel="next"

rev="previous" border=0 with=31 height=31 alt="Next section"></a>

</td>

<form>

<input type="button" value="Go to 1st query term(s)" name="hit0_button"

onClick="window.location.hash='hit0000'">

</form>

</td></tr></table>

{$DOC}

<a href="javascript:getdoc(-1)"><img src="prevbutt.gif" rel="previous"

rev="next" border=0 with=31 height=31 alt="Previous section "></a>

<a href="javascript:getdoc(1) "> <img src="nextbutt.gif" rel="next"

rev="previous" border=0 with=31 height=31 alt="Next section"></a>

<a href="http://uscode.house.gov/usc.htm">Search USC</a>,

<a href="http://uscode.house.gov/about.htm">About Database</a>,

<a href="http://uscode.house.gov/download.htm">Download USC</a>,

<a href="http://uscode.house.gov/uscct.htm">Classification Tables</a>,

<a href="http://uscode.house.gov/cod.htm">Codification</a>

</center></font>

</body></html>

(4) The field USCDOC is storable and non-displayable.

Questions on Formats 5800 to 5803

(1) 4 In %I03, is the 4 pica measurement the width or height of the horizontal rule? Length

(2) 4 In %I28, what are the primary and secondary indents? 1 and 0 ems

(3) 4 In %I36, what is the significance of “can split”? text can be split between columns or pages

(4) 4 Will %I38, %I90, %I91, %I97, %I98, or %I99 ever appear in the raw data? It is possible (though unlikely) that %I38 will (if it does treated it like a %L). The others should never appear.

(5) 4Are any particular locators associated with %I40? All locators with lower FTOP values. What is the secondary indent? 61 pts

(6) 4Are any particular locators associated with %I41? All locators with lower FTOP values.

(7) 4 What is the secondary indent for %I89? 2 ems

(8) 4 Do any of the locators have a default grid with a value other than 1? No

Questions on Format 5804

(1) Is %I77 only used for the “See Main Edition” headings? It is currently only used for “See Main Edition” headings, however, in the future it could be used for other purposes.

Questions on Function Codes

(1) 4 What is the unit of measure for the %Q arguments? points

(2) 4 Is there a difference between %Q and %q (both are used in 23 USC § 127(a))? %Q is positive. %q is negative.

(3) 4What is the effect of adding vertical space? Brings the text that follows it further down on the page. Horizontal space brings text away from the side margin.

(4) 4 If a locator with a grid value of 1 and a typeface value of 1, is followed by

· %T3%G3

· text

· %T2

· text

· %K

What are the typeface and grid values after the %K? Typeface 1 and grid 1. The %K reinstates the typeface and grid values from the original locator.

(5) 4 If the p argument is not included in a %c, what is the default point size for boxheads, footnotes, etc. in a table? 6 points is the default size for all elements in a table.

(6) 4 If the L argument is not included in a %c, what is the default value for the linerule designation? 0

(7) 4 What is the default width for rules? 0.4 points

(8) 4 If a %c does not have a “b” argument, what is the default bearoff? Default bearoff in points = font point size * 0.5

(9) 4 If a %c has a “b” argument, is the value added to the default bearoff or is it instead of the default? Instead of

(10) 4 Within a %c table, what is the function of a locator-97 and how is it different from a locator-95 or a locator-96? Same as locator-96, except it does not add “—continued” when repeated

(11) 4 Other than the locator-97 (e.g., in 5 U.S.C. § 5332 note (sched. 1), are there any other photocomposition codes not listed in the February 1, 1997 edition of Subformat Generation MicroComp? No. Locator-97 is the only one as of 5/8/00.

(12) In a subformat generation table, can the override function (%oi) be used in a stub column (e.g., would %I01%oi0 be valid)?

(13) The illustration of locator-21 on page 9 of Subformat Generation: MicroComp (2/1/97) shows text spanning an entire table. The chart on page 2, however, defines the locator-21 as “start only”. Are these two explanations consistent?

(14) 4 What is a “tracing column”? (Referred to on page 2 (footnote 18) of Subformat Generation: MicroComp (2/1/97).) Normally this is the first column and is mirrored in last column. In MicroComp, the mirroring is not automatic—it does, however, allow a bell-I to be used in the second column of a bell-c table.

(15) Does the U.S. Code use any grid calls higher than 8?

(16) In 21 U.S.C. § 350a(i)(2)(B), why is %G2%T1 used instead of %G5%T1 to make a superscript.

Assumptions used to convert from GPO photocomposition codes to HTML

point size	HTML <font> size	pixels per em
6	1	9
7	2	12
8	3	14
10	5	21
14	7	43

General Rule: Text should be in two column borderless tables.

If the primary indent is greater than (or equal to) the secondary indent, the first column should consist of one blank (i.e.,  ) and have a width determined by the following formula:

120 + ((ems in secondary indent) * (pixels per em for the current point size)).[511]

The text associated with the photocomposition code should be in the second column and should be preceded in that column with one blank (i.e.,  ) for every em in the formula:

(primary indent) - (secondary indent).[512]

The width of the second column should be:

(width of table) - (width of first column)

The total width of the table should normally be 600 pixels.

(number of points) * 0.8 = (number of pixels)

Exceptions:

(1) Spanners

(2) Lines that include locators that do not start a new line

Normal Processing

What values are needed for “normal processing”?

1. FOTP is blank.

2. Line length (LGH) is 207.

3. ~~Primary indent (INDENT PRI) is greater than or equal to secondary indent (INDENT SEC).~~

4. The next photocomposition code is a locator code (i.e., a bell-I).

5. The code is not intended to start a new document.

6. The code is not intended to start the STATUTE or MISC fields.

Questions:

1. What is the function of Line Type (LNTY) values J and V?

Process:

1. If the current format is 5800 and the locator is listed in the following table, then insert the indicated field identifier:

locator	field identifier
53	<!--plsfield:SOURCE-->
73	<!--plsfield:SECREF-->
74	<!--plsfield:MISC-->
75	<!--plsfield:REFTEXT-->
76	<!--plsfield:COD-->
78	<!--plsfield:CHANGE-->
80	<!--plsfield:HEAD-->
84	<!--plsfield:STATAMEND-->
85	<!--plsfield:TRANS-->
86	<!--plsfield:EXEC-->
87	<!--plsfield:CROSS-->
89	<!--plsfield:HEAD-->

2. Literal: <table width=“600” border=“0” cellspacing=“0” cellpadding=“0” frame="void" rules="rows"><td width=

2A. Calculate {leading} = (({bottom leading} of previous locator – {font size in points} of previous locator)[513] + ({top leading} of current locator – {font size in points} of current locator)[514] + arguments from all bell-Q s after the previous locator – arguments from all bell-q s after the previous locator) * 0.8. Round off {leading} to the nearest whole number. For each occurrence of {leading}, insert the literal: <tr></tr>

2B. Insert literal: <tr>

3. Multiply the secondary indent (INDENT SEC) or the primary indent (INDENT PRI) — whichever is smaller — by the pixels-per-em-multiplier shown in the following table for the current point size (PTSZ):

point size	Pixels per em Multiplier
6	9
7	12
8	14
10	21
14	43

Finally, add 120 to the number and insert the number in the text.

4. Literal: > </td><td width=

5. Subtract the value calculated in step 3 from 600 and insert the new number in the text, followed by a blank space.

6. Literal: valign="top"

7. Insert a blank space followed by the HTML Line Justification value shown in this table for the current Line Type (LNTP) value:

Line Type	HTML Align Value
C	align=“center”
J	align=“justify” [515]
L	align=“left”
R	align=“right”

8. Literal: ><font size=

9. Insert the HTML <font> size value shown in this table for the current Point Size (PTSZ) value:

Point size	HTML <font> size
6	1
7	2
8	3
10	5
14	7

10. Literal: >

11. Insert the HTML typeface begin tag shown in this table (or execute the special process) for the current GPO Typeface value:

GPO Typeface	HTML Typeface Begin Tag
1
2	<b>
3	<i>
4	[special processing: Caps & small caps]

12. If the primary indent (INDENT PRI) is greater than the secondary indent (INDENT SEC), then subtract the secondary indent from the primary indent. Then multiply that value by 2 and round it off to the nearest whole number. Insert “ ” once for the number of times equal to the value just calculated (e.g., if the primary indent is 5, the secondary indent is 1, then insert “  ”).

13. If the GPO Typeface (TF) equals 4,

(a) insert “<font size=“-1”>”

(b) Examine each character between the current locator code and the next locator code.

(1) In front of each upper case character, insert “<font size=”+1”>”.

(2) After each upper case character, insert “</font>”.

(3) Translate each lower case character to upper case .

14. If the GPO Typeface (TF) does not equal 4, then insert the text that followed the locator code up to the start of the next photocomposition code.

15. Insert the HTML typeface end tag shown in this table for the current GPO Typeface value:

GPO Typeface	HTML Typeface End Tag
1
2	</b>
3	</i>
4

16. Literal: </font></td></tr></table>

Alternative processing scheme for bell-Q

The current specifications incorporate the bell-Q into the process for calculating {leading}. Prior versions of the specifications, however, had the bell-Q acting independently from the top and bottom leading of individual locators. In those earlier specifications, the Q-code was replaced with the following HTML[516]:

Bell-Q	HTML
01	<font size=“1”><br> </font>
02	<font size=“1”><br> </font>
03	<font size=“1”><br> </font>
04	<font size=“1”><br> </font>
05	<font size=“1”><br> </font>
06	<font size=“1”><br> </font>
07	<font size=“2”><br> </font>
08	<font size=“3”><br> </font>
09	<font size=“4”><br> </font>
10	<font size=“5”><br> </font>
11	<font size=“6”><br> </font>
12	<font size=“6”><br> </font>
13	<font size=“7”><br> </font>
14	<font size=“7”><br> </font>
15	<font size=“1”><br> </font><font size=“4”><br> </font>
16	<font size=“1”><br> </font><font size=“5”><br> </font>
17	<font size=“2”><br> </font><font size=“5”><br> </font>
18	<font size=“1”><br> </font><font size=“6”><br> </font>
19	<font size=“2”><br> </font><font size=“6”><br> </font>
20	<font size=“1”><br> </font><font size=“7”><br> </font>
21	<font size=“2”><br> </font><font size=“7”><br> </font>
22	<font size=“3”><br> </font><font size=“7”><br> </font>
23	<font size=“4”><br> </font><font size=“7”><br> </font>
24	<font size=“5”><br> </font><font size=“7”><br> </font>
25	<font size=“1”><br> </font><font size=“2”><br> </font><font size=“6”><br> </font>
26	<font size=“6”><br> </font><font size=“7”><br> </font>
27	<font size=“1”><br> </font><font size=“2”><br> </font><font size=“7”><br> </font>
28	<font size=“7”><br> <br> </font>
29	<font size=“3”><br> </font><font size=“2”><br> </font><font size=“7”><br> </font>
30	<font size=“1”><br> </font><font size=“5”><br> </font><font size=“7”><br> </font>
31	<font size=“2”><br> </font><font size=“5”><br> </font><font size=“7”><br> </font>
32	<font size=“1”><br> </font><font size=“6”><br> </font><font size=“7”><br> </font>
33	<font size=“2”><br> </font><font size=“6”><br> </font><font size=“7”><br> </font>
34	<font size=“1”><br> </font><font size=“7”><br> <br> </font>
35	<font size=“2”><br> </font><font size=“7”><br> <br> </font>
36	<font size=“3”><br> </font><font size=“7”><br> <br> </font>
37	<font size=“4”><br> </font><font size=“7”><br> <br> </font>
38	<font size=“5”><br> </font><font size=“7”><br> <br> </font>
39	<font size=“1”><br> </font><font size=“2”><br> </font><font size=“6”><br> </font><font size=“7”><br> </font>
40	<font size=“6”><br> </font><font size=“7”><br> <br> </font>
41	<font size=“1”><br> </font><font size=“2”><br> </font><font size=“7”><br> <br> </font>
42	<font size=“7”><br> <br> <br> </font>
43	<font size=“3”><br> </font><font size=“2”><br> </font><font size=“7”><br> <br> </font>
44	<font size=“1”><br> </font><font size=“5”><br> </font><font size=“7”><br> <br> </font>
45	<font size=“2”><br> </font><font size=“5”><br> </font><font size=“7”><br> <br> </font>
46	<font size=“1”><br> </font><font size=“6”><br> </font><font size=“7”><br> <br> </font>
47	<font size=“2”><br> </font><font size=“6”><br> </font><font size=“7”><br>  <br> </font>
48	<font size=“1”><br> </font><font size=“7”><br> <br>  <br> </font>
49	<font size=“2”><br> </font><font size=“7”><br> <br>  <br> </font>
50	<font size=“3”><br> </font><font size=“7”><br> <br>  <br> </font>
51	<font size=“4”><br> </font><font size=“7”><br> <br>  <br> </font>
52	<font size=“5”><br> </font><font size=“7”><br> <br>  <br> </font>
53	<font size=“1”><br> </font><font size=“2”><br> </font><font size=“6”><br> </font><font size=“7”><br>  <br> </font>
54	<font size=“6”><br> </font><font size=“7”><br> <br>  <br> </font>
55	<font size=“1”><br> </font><font size=“2”><br> </font><font size=“7”><br> <br>  <br> </font>
56	<font size=“7”><br> <br> <br>  <br> </font>
57	<font size=“3”><br> </font><font size=“2”><br> </font><font size=“7”><br> <br>  <br> </font>
58	<font size=“1”><br> </font><font size=“5”><br> </font><font size=“7”><br> <br>  <br> </font>
59	<font size=“2”><br> </font><font size=“5”><br> </font><font size=“7”><br> <br>  <br> </font>
60	<font size=“1”><br> </font><font size=“6”><br> </font><font size=“7”><br> <br>  <br> </font>
61	<font size=“2”><br> </font><font size=“6”><br> </font><font size=“7”><br>  <br>  <br> </font>
62	<font size=“1”><br> </font><font size=“7”><br> <br>  <br>  <br> </font>
63	<font size=“2”><br> </font><font size=“7”><br> <br>  <br>  <br> </font>
64	<font size=“3”><br> </font><font size=“7”><br> <br>  <br>  <br> </font>
65	<font size=“4”><br> </font><font size=“7”><br> <br>  <br>  <br> </font>
66	<font size=“5”><br> </font><font size=“7”><br> <br>  <br>  <br> </font>
67	<font size=“1”><br> </font><font size=“2”><br> </font><font size=“6”><br> </font><font size=“7”><br>  <br>  <br> </font>
68	<font size=“6”><br> </font><font size=“7”><br> <br>  <br>  <br> </font>
69	<font size=“1”><br> </font><font size=“2”><br> </font><font size=“7”><br> <br>  <br>  <br> </font>
70	<font size=“7”><br> <br> <br>  <br>  <br> </font>
71	<font size=“3”><br> </font><font size=“2”><br> </font><font size=“7”><br> <br>  <br>  <br> </font>
72	<font size=“1”><br> </font><font size=“5”><br> </font><font size=“7”><br> <br>  <br>  <br> </font>
73	<font size=“2”><br> </font><font size=“5”><br> </font><font size=“7”><br> <br>  <br>  <br> </font>
74	<font size=“1”><br> </font><font size=“6”><br> </font><font size=“7”><br> <br>  <br>  <br> </font>
75	<font size=“2”><br> </font><font size=“6”><br> </font><font size=“7”><br>  <br>  <br>  <br> </font>
76	<font size=“1”><br> </font><font size=“7”><br> <br>  <br>  <br>  <br> </font>
77	<font size=“2”><br> </font><font size=“7”><br> <br>  <br>  <br>  <br> </font>
78	<font size=“3”><br> </font><font size=“7”><br> <br>  <br>  <br>  <br> </font>
79	<font size=“4”><br> </font><font size=“7”><br> <br>  <br>  <br>  <br> </font>
80	<font size=“5”><br> </font><font size=“7”><br> <br>  <br>  <br>  <br> </font>
81	<font size=“1”><br> </font><font size=“2”><br> </font><font size=“6”><br> </font><font size=“7”><br>  <br>  <br>  <br> </font>
82	<font size=“6”><br> </font><font size=“7”><br> <br>  <br>  <br>  <br> </font>
83	<font size=“1”><br> </font><font size=“2”><br> </font><font size=“7”><br> <br>  <br>  <br>  <br> </font>
84	<font size=“7”><br> <br> <br>  <br>  <br>  <br>  </font>
85	<font size=“3”><br> </font><font size=“2”><br> </font><font size=“7”><br> <br>  <br>  <br>  <br>  </font>
86	<font size=“1”><br> </font><font size=“5”><br> </font><font size=“7”><br> <br>  <br>  <br>  <br>  </font>
87	<font size=“2”><br> </font><font size=“5”><br> </font><font size=“7”><br> <br>  <br>  <br>  <br>  </font>
88	<font size=“1”><br> </font><font size=“6”><br> </font><font size=“7”><br> <br>  <br>  <br>  <br>  </font>
89	<font size=“2”><br> </font><font size=“6”><br> </font><font size=“7”><br>  <br>  <br>  <br>  <br>  </font>
90	<font size=“1”><br> </font><font size=“7”><br> <br>  <br>  <br>  <br>  <br>  </font>
91	<font size=“2”><br> </font><font size=“7”><br> <br>  <br>  <br>  <br>  <br>  </font>
92	<font size=“3”><br> </font><font size=“7”><br> <br>  <br>  <br>  <br>  <br>  </font>
93	<font size=“4”><br> </font><font size=“7”><br> <br>  <br>  <br>  <br>  <br>  </font>
94	<font size=“5”><br> </font><font size=“7”><br> <br>  <br>  <br>  <br>  <br>  </font>
95	<font size=“1”><br> </font><font size=“2”><br> </font><font size=“6”><br> </font><font size=“7”><br>  <br>  <br>  <br>  <br>  </font>
96	<font size=“6”><br> </font><font size=“7”><br> <br>  <br>  <br>  <br>  <br>  </font>
97	<font size=“1”><br> </font><font size=“2”><br> </font><font size=“7”><br> <br>  <br>  <br>  <br>  <br>  </font>
98	<font size=“7”><br> <br> <br>  <br>  <br>  <br>  <br>  </font>
99	<font size=“3”><br> </font><font size=“2”><br> </font><font size=“7”><br> <br>  <br>  <br>  <br>  <br>  </font>

Logic for implementation of the Quad-right and Quad-left features in c-table horizontal rule processing

The Government Printing Office’s Subformat Generation MicroComp (February 1, 1997), p. 6 (item G) describes the use of quad-right and quad-left characters in conjunction with horizontal rule processing in bell-c tables. The quad-right and quad-left features, however, have not been implemented in GPO’s MicroComp software and those features are therefore not currently used in the U.S. Code.

At some future point, GPO may implement these features in MicroComp and the U.S. Code may incorporate them. In that event, the following logic should be added to the horizontal rule processing instructions for bell-c tables:

(") If the argument is “n” followed by a quad-right, then

(a) execute new column processing

(b) calculate {colspan} according to the formula: {colspan} = {number of columns in table} – {column} + 1

(c) output: <td bgcolor=“#FFFFFF” height=“1” colspan=“{colspan}”><font size=“1”></font></td></tr>

($) If the argument is “n” followed by a quad-left, then

(a) execute new column processing

(b) output: <td bgcolor=“#FFFFFF” height=“1”><font size=“1”></font></td></tr>

(() If the argument is “s” followed by a quad-right, then

(a) execute new column processing

(b) calculate {colspan} according to the formula: {colspan} = {number of columns in table} – {column} + 1

(c) output: <td bgcolor=“#000000” height=“1” colspan=“{colspan}”><font size=“1”></font></td></tr>

(*) If the argument is “s” followed by a quad-left, then

(a) execute new column processing

(b) output: <td bgcolor=“#000000” height=“1”><font size=“1”></font></td></tr>

(,) If the argument is “d” followed by a quad-right, then

(a) execute new column processing

(b) calculate {colspan} according to the formula: {colspan} = {number of columns in table} – {column} + 2

(c) output: <td bgcolor=“#FFFFFF” height=“1” colspan=“{colspan}”><font size=“1”></font></td></tr>

(.) If the argument is “d” followed by a quad-left, then

(a) execute new column processing

(b) output: <td bgcolor=“#FFFFFF” height=“2”><font size=“1”></font></td></tr>

(0) If the argument is “b” followed by a quad-right, then

(a) execute new column processing

(b) calculate {colspan} according to the formula: {colspan} = {number of columns in table} – {column} + 1

(c) output: <td bgcolor=“#000033” height=“1” colspan=“{colspan}”><font size=“1”></font></td></tr>

(2) If the argument is “b” followed by a quad-left, then

(a) execute new column processing

(b) output: <td bgcolor=“#000033” height=“1”><font size=“1”></font></td></tr>

Mathematical Formulas

No special coding is provided for mathematical formulas. Because of this, mathematical formulas may stretch the capability of the software to properly display the data. Mathematical formulas can be found at the following locations:

23 U.S.C. § 127(a)

25 U.S.C. § 1616a(l)(2)

38 U.S.C. § 7617(c)(1)

38 U.S.C. § 7675(c)(1)

42 U.S.C. § 254o(b)(1)(A)

42 U.S.C. § 288(c)(4)(A)

42 U.S.C. § 300x-7(a)(1), (4)

42 U.S.C. § 1395ww(d)(5)(F)(viii)

45 U.S.C. § 352(a)(3)(A)

45 U.S.C. § 358(a)(1)(B)(ii)(II), (iii)(II), (D)(ii)(II), (iii)(II)

Glossary

Bearoff – in a table, the space between (1) the rule that sets out the boundaries of a cell and (2) the contents of the cell.

Bell code – part of the GPO photocomposition code scheme; text mark-up code that starts with a bell character (i.e., a HEX 07).

Carding – extra space inserted to assist in top-to-bottom page justification. Normally, this is sufficiently small amounts of space designed so that it is not apparent that space has been added.

Catchline – Bold heading that precedes each section, title, subtitle, chapter, subchapter, part, subpart, division, and appendix of the U.S. Code.

FOTP – part of the GPO photocomposition code scheme used to format simple tables. FOTP originally was a shortened version of “format type”.[517]

GPO photocomposition code – tag developed by the U.S. Government Printing Office to implement their scheme for formatting data to facilitate hard copy and electronic printing.

Horizontal space – space between vertical columns.

Interline leading – the space between the bottom of the characters in one line and the top of the characters in the next line.

Leadering – use of characters (often periods) to fill in the space between (1) the end of the text of one cell in a table and (2) the end of the cell.

Leading – the space (horizontal or vertical) between one character and an adjacent character.

Locator code (or “locator”) – specialized bell code that is composed of a bell character (HEX 07), a capital letter “I”, and a two-digit number.

Rule – a line.

Subformat generation – part of the GPO photocomposition code scheme used to format complex tables. Such tables start with a bell character (HEX 07) and a lower case letter “c”. A detailed description of subformat generation can be found in Publishing from a Full Text Data Base, U.S. Government Printing Office, Graphic Systems Development Division, September 1982, pages 54-59, 71-75, and 82-107; Subformat Generation MicroComp, U.S. Government Printing Office, February 1, 1997; and the bell-c section of this document .

Vertical space – space between horizontal rows.

Previous versions of these specifications

Date	Version
March 7, 1999	1.00
February 3, 2000	1.01
March 10, 2000	1.02
March 16, 2000	1.03
March 24, 2000	1.04
March 31, 2000	1.05
April 7, 2000	1.06
April 14, 2000	1.07
April 21, 2000	1.08
April 28, 2000	1.09
May 5, 2000	1.10
May 12, 2000	1.11
May 19, 2000	1.12
June 16, 2000	1.13
June 30, 2000	1.14
July 7, 2000	1.15
July 27, 2000	1.16
August 4, 2000	1.17
August 11, 2000	1.18
August 24, 2000	1.19
August 29, 2000	2.00
October 31, 2000	2.01
November 30, 2000	2.02
December 22, 2000	2.03
January 12, 2001	2.04
February 15, 2001	2.05
March 15, 2001	2.06
April 16, 2001	2.07

Examples of U.S. Code photocomposition codes

U.S.C. title	U.S.C. section	Process
	Organic Laws, prelim. page	Format 58078 (%I22, %I52, and %I53)
	Declaration of Independence	Format 58008 (%I06)
	Declaration of Independence (catchline)	Format 58008 (%I04)
	Declaration of Independence (signatures)	Format 5807 (%I57, %I58, and %I83)
	Declaration of Independence (note following signatures)	Format 5800 (%I55)
	Constitution (running head)	5-digit %F
	Constitution (catchline)	Footnote
	Constitution, art. I	Format 58008 (%I81)
	Constitution, art. I, § 2, cl. 1	Numeric superscript that is not a footnote reference
	Constitution, art. I, § 2, cl. 3	footnote
	Constitution (signatures)	Format 58008 (%I49); %G5%T1 Hex 43, 44, 4C, 4D, 4F, 53, and 54; %G5%T3 Hex 74
	Analytical Index to the Constitution (running head)	Format 58098 (%I90 and %I91)
	Analytical Index to the Constitution (after running head)	Format 58098 (%I04, %I05, %I06 and %I07)
	Analytical Index to the Constitution (catchline)	Format 58098 (%I01, %I02, and %I14)
	Analytical Index to the Constitution (A)	Format 58098 (%I08)
	Analytical Index to the Constitution (Abridged)	Format 58098 (%I09, %I10, %I11, and %I12)
	Analytical Index to the Constitution (Accused) (He shall be tried . . .)	Format 58098 (%I13)
	Analytical Index to the Constitution (Death) (Amendments)	Format 58098 (%I16)
	Page prec. 1 U.S.C.	Format 5800 (%I03 and %I39)
1	Prec. ch. 1 (catchline)	Format 5800 (%I04)
1	Prec. ch. 1 (prec. § 1)	Format 5800 (%I05)
1	prec. ch. 1 (Table Showing Disposition of All Sections of Former Title 1)	Discretionary hyphen; thin space; %c command line with L2, p6, r, tp, and xs arguments and numeric argument without prefix or suffix; and within subformat generation: %D, %I01, %I11, %I22, %I31, %I95 (7-point title), %j, %P, %T1, %T3, %T4, and %xl
1	Ch. 1	Open double quotation mark, close double quotation mark, M-dash, N-dash, and %T2
1	1	Format 5800 (%I80 and %I89); and Crlf [Hex 0A]
1	1 note (Continental United States)	Open single quotation mark and close single quotation mark
1	1 note (Section Referred to in Other Sections)	Format 5800 (%I73)
1	101	§
1	106 note (Pub. L. 100-360, § 411(a)(2))	%T3 and %T4
1	106 note (Pub. L. 104-207, § 1)	%T1
1	Ch. 3 (prec § 201)	Format 5800 (%I48 and %I59)
1	204(d)	M-space
1	213 (source credit)	EOF
2	1 note (Constitutional Provisions)	N-space
2	57 note (Committee Ord. No. 30)	Format 5800 (%I26)
2	59(f)(3)(B)	%T2
2	59h(a)	%g401%T3 and %g940%T1
2	60a note (Codification)	Format 5800 (%I35 and %I36)
2	60a-1 note (Order of the President Pro Tempore of the United States Senate, December 12, 1999, § 11)	Format 5800 (%I27)
2	60a-2(a)(1)	Format 5800 (%I12)
2	60a-2(a)(1)(A)	Format 5800 (%I13)
2	60a-2(a)(1)(B)	Format 5800 (%I17)
2	60a-2 note (Amendments)	Format 5800 (%I22 and %I33); and format 5800 (%I74 following Codification note)
2	60a-2 note (Codification)	Format 5800 (%I76)
2	60l (catchline)	%g742%T3
2	60l(a)(2)(A)	Format 5800 (%I18)
2	350a(i)(2)(B)	%G2
2	358 note	Format 5804 (%I25 and %I26)
2	434 note (Amendment of Subsection (a)(11))	Format 5800 (%I57)
2	604	“Omitted” catchline
2	621 note (Financial Safety and Soundness of Government Sponsored Enterprises, § 508(e)(3)(B)(i))	Format 5800 (%I24)
2	631	p7 in %c command line
2	900 note (Section Referred to in Other Sections)	%I73 occurs second time within notes
2	1223, 1224	§§
3	1 note (Cross References)	Format 5800 (%I87)
3	Ch. 2 note (Reorganization Plan No. 1 of 1997)	Format 5800 (%I25)
3	205	“Repealed” catchline
4	1 note (Ex. Ord. No. 10834)	%I86 following Executive Order note
4	1 note (Ex. Ord. No. 10834, § 21)	Format 5800 (I%I21); %c command line with s and tp0 arguments; and within subformat generation: %h and %I95 (0-point title);
4	1 note (Ex. Ord. No. 10834, § 33)	%g,d; %q; %c command line with numeric with C suffix; and %95 (6-point title) within subformat generation
4	1 note (Section Referred to in Other Sections)	Format 5800 (%I82)
5	Prec. pt. I (running head)	Format 5800 (%I06)
5	Prec. pt. I (title analysis)	Format 5800 (%I07, %I08, %I09, %I29, %I52, %I70, and %I93)
5	prec. pt. I (Table Showing Disposition of Al Sections of Former Title 5)	%c command line with xls argument; %D within subformat generation; table with over 60 lines
5	Ch. 1 (prec. § 101)	Format 5800 (%I46)
5	101	Format 5800 (%I66)
5	101 note (Historic and Revision Notes)	Format 5800 (%I30); %c command line with tp7 argument; and %I95 (7-point title) within subformat generation
5	301 note (Improvements in Identification-Related Documents)	Format 5800 (%I23)
5	601 note (Plain Language in Government Writing)	%G7%T2 Hex 01
5	1101 note (Ex. Ord. No. 12107, § 2-1(a))	Format 5804 (%I48 and %I71)
5	5304(a)(3)(D)	½
5	5305 note (Federal Law Enforcement Pay Reform, § 403(b)(1))	Format 5804 (%I71)
5	5315 (source credit)	Format 5800 (%I53)
5	5332 note (sched. 1)	Caps and small caps with small typeface; and %c command line with b and tp6 arguments
5	5332 note (sched. 3)	within subformat generation: %e, %f, %I96, %I97, %oi1, %Q, and %s; also L0 and p0 in %c command line
5	5332 note (sched. 4)	Format 5804 (%I40, %I41, %I63, and %I64)
5	5332 note (sched. 8, pt. I)	%r within subformat generation
5	5332 note (sched. 8, pt. II)	Format 5800 (%I61)
5	6101 note (Federal Employees Flexible and Compressed Word Schedules, § 103(c)(1)(A)	Format 5800 (%I31)
5	7103(1)(16)(B)	Format 5800 (%I32)
5 app.	Table of contents	Format 5800 (%I94, %I95, and %I96)
5 app. (Fed. Advisory Comm. Act)	1	Format 5802 (%I80)
5 app.	Reorg. Plan No. 3 of 1967 (Message of the President)	Format 5800 (%I34)
7	136a(h)(3)(B)(iii)(III) (aa)	Format 5804 (%I34)
7	612c note (Commodity Distribution Reform, § 3(f))	Format 5804 (%I21)
7	612c note (Commodity Distribution Reform, § 3(f)(1))	Format 5804 (%I22)
7	612c note (Commodity Distribution Reform, § 3(f)(2)(A))	Format 5804 (%I23)
7	935(c)(2)(C)(ii)(I)	Format 5800 (%I72)
7	Ch. 31A (prec. § 950aaa)	Format 5800 (%I45 and %I50)
7	1314(g)(1)	%G2%T2
7	1448	%c command line with p4 argument
7	1635j(a)(1)(C)(ii)(V)	Format 5800 (%I56)
7	Ch. 43 (prec. § 1761)	É
7	1765a(d)	é
7	2020 note (Enactment of Subsection (r))	Format 5800 (%I68)
7	6802(4)(A)(iii)(III)(aa)	Format 5804 (%I69)
7	6807 note (References in Text)	Format 5800 (%I75)
7	Ch. 98 (prec § 6901)	Format 5800 (%I71)
8	1101 note (Effective Date of 1996 Amendments, § 309(c)(5)(C)(i)(I)(aa)	Format 5804 (%I24)
8	1152(a)(4)(A)(i)	Format 5800 (%I77)
8	1182 note (Resettlement of Refugee-Escapee)	Format 5800 (%I92)
10	Subtitle A (prec § 101)	Format 5804 (%I29, %I37, %I38, %I39, and %I70)
10	111 note	Format 5804 (%I67)
10	522	Format 5800 (%I37)
10	1557(a)	Format 5804 (%I35, %I36, and %I44)
10	2407 note (NATO Cooperative Logistic Support Agreements)	Format 5800 (%I74 immediately following section catchline)
10	Ch. 1201 (prec. § 12001)	Format 5804 (%I27 and %I28)
10	6333(a)	%c command line with xls argument with C suffix
10	12003(a)	Format 5804 (%I43)
10 app. (R.C.A.A. F.)	Rule 20	Format 5804 (%I91)
11 app. (Bankr. R.)	Rule 2004 note	¶¶
11 app. (Bankr. R.)	Rule 4004 note	¶
11 app. (Bankr. R.)	Rule 7001 note	%I03 within subformat generation; and %c command line with ns and xl arguments
11 app. (Bankr. R.)	Form 1	Format 5804 (%I94)
12	24(Seventh)	Format 5800 (%I11)
12	1785 note (Choice of Highest Applicable Interest Rate)	Format 5800 (%I74 immediately after cross reference (“Definition of ‘State’”) note)
12	1813 note (Amendment of Section)	Format 5800 (%I64); and %g741%T4
12	1828 note (Enactment of Subsection (t))	Format 5800 (%I67)
15	205 note (Measures of Length)	7-point table heading following source credit; %c command line with L and p ,0 arguments and argument followed by parens; %c command line with nc argument; and %j within subformat generation
15	Ch. 14 (prec. § 601)	Format 5800 (%I71 immediately after Transfer of Functions note
15	1111	%G6%T1 Hex 74
16	ch. 1 (prec. § 1)	Format 5800 (%I40)
16	431 note (National Monuments Established Under Presidential Proclamation)	%c1
16	460u-3	%c command line with nj argument
16	460bb-1 note (Phelgen Estate Auction)	%G6%T1 HEX 34 and 36; and %G6%T2 HEX 34 and 36
16	461 note (Proc. No. 3339)	%G6%T1 Hex AB [degree mark]
16	3631(f)	Within subformat generation: %j and %l; also %c command line with nh argument
16	3631 note (Amendment of Section)	Format 5800 (%I42, %I84, and %I88)
16	3703(e)(3)(A)	Two subsection levels on one line
17	104 note (Particular Proclamations, Treaties and Conventions Establishing Copyright Relations Between the United States of America and Other Countries).	%c command line with f argument; and %G2%T1 within subformat generation
17	401(b)(1)	©
17	401 note (Universal Copyright Convention, Paris, 1971, art. III, § 1)	%G6%T1 ESC AF
17	402(b)(1)	%g007%T1P [P in a circle]
17	402 note (H. Rep. No. 94-1476)	ESC 09 within caps and small caps processing; and %G6%T1 ESC AF
17	909(b)(1)	%g007%T1M [M in a circle]
18	201 note (Memorandum of Attorney General Regarding Conflict of Interest Provisions of Public Law 87-849, February 1, 1963, 28 F.R. 985)	Format 5800 (%I74 immediately after Executive Order note)
18	841(p)(1)	%G5%T2 Hex 33
18	841(p)(3)	%G5%T2 Hex 37
18	1679c	Format 5804 (%I83)
18 app. (Fed. R. Evid.)		Format 5804 (%I16)
18 app. (Fed. R. Crim. P.)	Table of Contents	Format 5802 (%I69)
18 app. (Fed. R. Crim. P.)	Prec. rule 1	Format 5804 (%I61 and %I62)
18 app. (Fed. R. Crim. P.)	Rule 19	“Rescinded” catchline
18 app. (Fed. R. Crim P.)	Rule 39	“Abrogated” catchline
19	3332(b)(2)(A)	%c command line with p8 argument; and %G6%T1 ESC 0A [multiplication sign]
19	3332(b)(3)(A)	%c command line with p8 argument
20	1087oo(c)(2)	%I25 within subformat generation
20	1087pp(b)(4)	%I21 within subformat generation
20	1091(r)(1)	%I04 within subformat generation
20	7902(19)	ô
20	7912(1)(B)(ii)	û
21	350a(i)(2)(B)	Lower case mu (%G6 hex 6D); L1, tp8, and alignment column in %c command line; and within subformat generation: %G and %I02
21	1703(c)(3)(D)(ii)(II)(bb)(ccc)	7-level subsection
22	2291 note (Determining Major Drug-Transit Countries with respect to Fiscal Year 1989)	Format 5800 (%I74 immediately follows MISC7 note)
22	5421(f)(3)(B)(5)	ć and ś
22	5952 note (Limitation on Use of Funds for Certain Purposes)	Format 5800 (%I74 immediately follows MISC6 note)
22	6701(10)A)	%T2%G5 Hex 31 and 30 [subscript 10]
23	127(a)	New paragraph without subsection designation in line; format 5800 (%I10); %Q; minus sign; 3-line open paren (%T4%G7 hex 41); 3-line close paren (%T4%G7 hex 42); Bodoni M-dash (%T2%G7 hex 58); and mathematical formula
25	1616a(l)(2)	Mathematical formula
26	132 note (Amendment of Subsection (f))	Second italicized amendment note in a row
26	402 note (Amendment of Section)	Format 5800 (%I58)
26	419A(f)(7)(B)	Format 5804 (%I31)
26	451 note (Pub. L. 97-248, § 229(c)(2)(B))	Fraction and %xl
26	1252(a)(3)	New paragraph without subsection designation in line; format 5800 (%I79); %c command line with i1 argument; and within subformat generation: %b, %L ,and %R
26	4682(b)	Format 5804 (%I73)
26 app. (T.C.R.)	App. I	%R with catchline that does not contain an em-dash; and format 5800 (%I01)
28	453	%G7%T2 Hex 20 [blank space]
28	1470 note (Rules of Procedure of the Judicial Panel on Multi-district Litigation)	Format 5800 (%I20)
28	1470 note (Rules of Procedure of the Judicial Panel on Multi-district Litigation, rule 7.1(c)(iv))	Multiplication sign
28	1746(1)	Format 5800 (%I63)
28	2254 note (Rules Governing Section 2254 Cases in the United States District Courts, Appendix of Forms, Petition, § 11(e))	%G7%T2 ESC 1A
28	2254 note (Rules Governing Section 2254 Cases in the United States District Courts, Appendix of Forms, In Forma Pauperis Declaration)	Format 5804 (%I30 and %I33)
28	2254 note (Rules Governing Section 2254 Cases in the United States District Courts, Appendix of Forms, In Forma Pauperis Declaration, § 1)	%T1%G6 Hex BF [ballot box]
28 app. (Sup. Ct. R.)	Rule 31(1)(c)	¼
28 app. (Sup. Ct. R.)	Rule 31(1)(g)	%c with numeric argument with n suffix
28 app. (Fed. Cl. R.)	App. A, form A	Format 5802 (%I83)
28 app. (Fed. Cl. R.)	app. E	%A
28 app. (Fed. Cl. R.)	app. J (rule 16)	Format 5802 (%I81); format 5804 (%I04); % command line with aw, bl, and p1 arguments; and %I05 within subformat generation
28 app. (Fed. R. App. P.)	Rule 32 note (Committee Notes on Rules 1998 Amendment, ¶ (a)(5))	%G4VT2; and %g077%T1
28 app. (Fed. R. App. P.)	Form 1	Format 5804 (%I32); and %G7%T4 Hex 46 [close brace]
28 app. (Fed. R. App. P.)	Form 2	%G7%T4 Hex 57 [open brace]
28 app. (Fed. R. Civ. P.)	Prec. rule 1	Format 5802 (%I60)
28 app. (Fed. R. Civ. P.)	Rule 77(l)	%g940%T2
28 app. (Fed. R. Civ. P.)	Form 1	Format 5802 (%I62)
28 app. (Fed. R. Civ. P.)	Form 1B	%G7%T2 Hex 18
28 app. (Fed. R. Civ. P.)	Form 2	Format 5802 (%I74 immediately following within text)
28 app. (Fed. R. Civ. P.)	Form 10	Format 5804 (%I66)
28 app. (Fed. R. Civ. P.)	Form 34	Format 5802 (%I15)
33	702a-1¾	¾
33	1285(c)(2)	Within subformat generation: %I39, %N, %r (with n and s arguments)
34		Format 5800 (%I44); and three consecutive occurrences of HEX 00 [EOF]
36	prec. § 101 (Table Showing Disposition of All Sections of Former Title 36)	%g025%T3
36	2111 note (Ex. Ord. No. 9873)	Format 5800 (%I86)
38	7617(c)(1)	Mathematical formula and upper case phi (%G6%T1 Hex 46)
38	7675(c)(1)	Mathematical formula
40	71b note (Reorg. Plan No. 5 of 1966)	Format 5800 (%I71 immediately after Codification note)
42	254o(b)(1)(A)	Mathematical formula and lower case phi (%G6%T1 Hex 18, 19, and 66)
42	288(c)(4)(A)	Mathematical formula
42	300x-7(a)	Format 5800 (%I19)
42	300x-7(a)(1)	Mathematical formula; %c command line with g, L (0, ,0), and t arguments; and %h2 within subformat generation
42	300x-7(a)(4)	Mathematical formula
42	300x-7(a)(4)(A)(i)	Format 5800 (%I14)
42	1395ww(d)(5)(F)(vii)	Mathematical formula
42	1395ww(d)(5)(F)(vii)(I) (a)	%G6%T1 Hex 5E
42	1395ww note (Amendments, subsection (d)(5)(B)(ii)(I))	%G5%T1 Hex 2E, 30, 34, and 35
42	1395ww note (Amendments, subsection (d)(5)(B)(ii)(II))	%G5%T1 Hex 37 and 39
42	2297h-10(b)(2)(D)	%G5%T2 Hex 38
42	2472 note (Amendments)	Format 5800 (%I74 immediately after source credit)
42	Ch. 72, subch. II, pt. B (prec. § 5631)	Format 5800 (%I74 immediately follows Part Referred to in Other Parts note)
42	6295(i)(1)(A)	%G6%T1 Hex 3E [greater than] and Hex BE [less than]
42	6924(n)(5)(B)	%G5%T1 Hex 5E
42	Ch. 85 (prec. § 7401)	%G5%T2 Hex 78
42	7407 note (Ozone and Particulate Matter Standards, § 6101(a)(1))	%G5%T2 Hex 2E and 35
42	7412(a)(11)	Format 5800 (%I28)
42	7412(b)(1)	Footnote
42	7412(b)(1)(footnote 1)	Subscript 2 (%T2%G5 hex 32)
42	7412(b)(1)(footnote 2)	Subscript n (%T2%G5 hex 6E)
42	7412(b)(3)(A)	Footnote and format 5800 (%I28)
42	7521(g)(1)	%G5%T2 Hex 20
43	502 note (Temporary Authority of Secretary of Interior to Facilitate Emergency Actions with Regard to 1976-1977 Drought)	Format 5800 (%I74 immediately follows MISC5 note)
43	751 note (Land Information Study; Report to Congress)	Format 5800 (%I74 immediately after Transfer of Functions note)
43	946 note (Amendments)	Format 5800 (%I74 immediately after italicized amendment note)
43	1451 note (Reorg. Plan. No. 3 of 1950)	Format 5800 (%I71 immediately follows Executive Order note)
43	1457 note (Emergency Preparedness Functions)	Format 5800 (%I85 follows Transfer of Functions note)
43	1457 note (Transfer of Functions)	Format 5800 (%I85)
43	1595 note (Effective Date of 1984 Amendment)	Format 5800 (%I74 immediately follows MISC3 note)
43	1733 note (Modification of Regulations Relating to Mining Operations on Public Lands; Posting of Reclamation Bond for All Operations Involving Significant Surface Disturbance)	Format 5800 (%I74 immediately after Change of Name note)
43	1843 note (Amendments)	Format 5800 (%I74 immediately after References in Text note)
44	101 note (Short Title of 1993 Amendment)	Format 5800 (%I74 immediately follows MISC4 note)
44	3303a note (Change of Name)	Format 5800 (%I78)
44	3506 note (Amendments)	Format 5800 (%I74 follows immediately after MISC2 note)
44	3901 note (Short Title)	Format 5800 (%I74 follows immediately after MISC1 note)
45	351(I)(2)(B)(i)(II)	%G7%T3 Hex 5F
45	352(a)(3)(A)	Mathematical formula
45	358(a)(1)(B)(ii)	Format 5800 (%I16)
45	358(a)(1)(B)(ii)(II)	Mathematical formula
45	358(a)(1)(B)(iii)(II)	Mathematical formula
45	358(a)(1)(D)(ii)(II)	Mathematical formula
45	358(a)(1)(D)(iii)(II)	Mathematical formula
45	1705 note (Proc. No. 4346)	Degree mark
46	Subtitle I (prec. § 2101)	%R with catchline that contains brackets
47	158(g)((Private Radio Services)(1)	Format 5804 (%I76)
47	158(g)(Private Radio Services)(1)(g)(i)	Format 5804 (%I74)
47	158(g)(Private Radio Services)(6)(j)(vii)(1)	Format 5804 (%I75)
48	864 note (Federal Rules of Criminal Procedure)	Second %I87 within a single section
48	1694 to 1694e	“Transferred” catchline
48	1705 note (Proc. No. 4346)	Prime and degree marks
50	Ch. 21 (prec. § 541)	Á
50	541 to 546	á
Table of Popular Names	Running head	Format 5810 (%I06)
Table of Popular Names	Catchline	Format 5810 (%I01)
Table of Popular Names	Introduction	Format 5810 (%I02, %I03, and %I04)
Table of Popular Names	A.A.A. Farm Relief and Information Act)	Format 5810 (%12 and %I19)
Table I	Running head	Format 5811 (%I06)
Table I	Catchline	Format 5811 (%I04)
Table I	Prec. Abbreviations	Format 5811 (%I02 and %I03)
Table I	Abbreviations	Format 5804 (%I07) and format 5811 (%I05)
Table III	Catchline	Format 5812 (%I04)
Table III	Prec. Abbreviations	Format 5812 (%I03)
Table III	Abbreviations	Format 5812 (%I05 and %I07)
Table III	1^st Cong.	Format 5812 (%55 and %I59 to %I69)
Table III	June 1, 1789, § 2	Format 5812 (%I11 to %I14, %I17 to %I21, and %I25)
Table III	June 1, 1789, § 3	Format 5812 (%I17)
Table III	July 27, 1789, § 1	Format 5812 (%I12)
Table III	2^nd Cong.	Format 5812 (%I09 and %I10)
Table III	July 1, 1879	Format 5812 (%I28)
Table III	January 22, 1902	Format 5812 (%I15 and %I16)
Table III	February 7, 1902	Format 5812 (%I26)
Table IV	Catchline	Format 5813 (%I04)
Table IV	Running head	Format 5813 (%I06)
Table IV	Prec. table	Format 5813 (%I03 and %I05)
Table V		o argument in %c command line
Table VI		Format 5811 (%I07 to %I16, %I21 to %I27, and %I93)
Table VIII		Format 5811 (%I31 to %I33, %I40, and %I41)
Table IX	Prec. title 1	Format 5804 (%I01, %I02, %I03, and %I06)
Table IX	Title 1	Format 5804 (%I08, %I09, %I10, %I80, and %I81)

Examples of U.S. Code Text Generated According to These Specifications

Constitution, preamble to art. I, § 2, cl. 3

[page 1 of 3]

Constitution, preamble to art. I, § 2, cl. 3 [page 2 of 3]

Constitution, preamble to art. I, § 2, cl. 3 [page 3 of 3]

1 U.S.C. prec. ch. 1

2 U.S.C. § 60a-2

[page 1 of 5]

2 U.S.C. § 60a-2 [page 2 of 5]

2 U.S.C. § 60a-2 [page 3 of 5]

2 U.S.C. § 60a-2 [page 4 of 5]

2 U.S.C. § 60a-2 [page 5 of 5]

4 U.S.C. § 1 note (Ex. Ord. No. 10834, § 21)

4 U.S.C. § 1 note (Ex. Ord. No. 10834, § 33)

[page 1 of 2]

4 U.S.C. § 1 note (Ex. Ord. No. 10834, § 33) [page 2 of 2]

5 U.S.C. prec. pt. I

[page 1 of 4]

5 U.S.C. prec. pt. I [page 2 of 4]

5 U.S.C. prec. pt. I [page 3 of 4]

5 U.S.C. prec. pt. I [page 4 of 4]

5 U.S.C. § 101 note

5 U.S.C. § 5332 note (sched. 1 to 4)

[page 1 of 2]

5 U.S.C. § 5332 note (sched. 1 to 4) [page 2 of 2]

5 U.S.C. § 5332 note (sched. 8)

15 U.S.C. § 205

16 U.S.C. § 431 note

16 U.S.C. § 3631

[page 1 of 4]

16 U.S.C. § 3631 [page 2 of 4]

16 U.S.C. § 3631 [page 3 of 4]

16 U.S.C. § 3631 [page 4 of 4]

17 U.S.C. § 402

[page 1 of 3]

17 U.S.C. § 402 [page 2 of 3]

17 U.S.C. § 402 [page 3 of 3]

17 U.S.C. § 909(b)(1)

20 U.S.C. § 1087pp(b)(2)-(4)

[page 1 of 4]

20 U.S.C. § 1087pp(b)(2)-(4) [page 2 of 4]

20 U.S.C. § 1087pp(b)(2)-(4) [page 3 of 4]

20 U.S.C. § 1087pp(b)(2)-(4) [page 4 of 4]

20 U.S.C. § 1091(r)(1)

21 U.S.C. 350a(i)(2)(B)

[page 1 of 2]

21 U.S.C. § 350a(i)(2)(B) [page 2 of 2]

23 U.S.C. § 127(a)-(b)

[page 1 of 4]

23 U.S.C. § 127(a)-(b) [page 2 of 4]

23 U.S.C. § 127(a)-(b) [page 3 of 4]

23 U.S.C. § 127(a)-(b) [page 4 of 4]

26 U.S.C. § 1252(a)(3)

28 U.S.C. app. (Sup. Ct. R.) rule 33

[page 1 of 4]

28 U.S.C. app. (Sup. Ct. R.) rule 33 [page 2 of 4]

28 U.S.C. app. (Sup. Ct. R.) rule 33 [page 3 of 4]

28 U.S.C. app. (Sup. Ct. R.) rule 33 [page 4 of 4]

28 U.S.C. app. (Fed. Cl. R.) app. J, rule 16

[page 1 of 2]

28 U.S.C. app. (Fed. Cl. R.) app. J, rule 16 [page 2 of 2]

34 U.S.C.

42 U.S.C. § 300x-7(a)

42 U.S.C. § 7412(a)(11)-(b)(3)(D)

[page 1 of 5]

42 U.S.C. § 7412(a)(11)-(b)(3)(D) [page 2 of 5]

42 U.S.C. § 7412(a)(11)-(b)(3)(D) [page 3 of 5]

42 U.S.C. § 7412(a)(11)-(b)(3)(D) [page 4 of 5]

42 U.S.C. § 7412(a)(11)-(b)(3)(D) [page 5 of 5]

45 U.S.C. § 358(a)(1)(B)(i)-(ii)

46 U.S.C. subtitle I

Bibliography

Action Item 87-233 (Exchange of Data and Access with DoD). By Elliot Chabot. [House Information Systems]. AS-678. September 18, 1987; Follow-up to Action Item 87-233 (Exchange of Data and Access with DoD). By Elliot Chabot. [House Information Systems]. AS-690. October 20, 1987.

Analysis Report: Legal Text Retrieval for the Joint Committee on Internal Revenue Taxation. By S. Croyden, Jr. Committee on House Administration, House Information Systems. TN-0329. May 27, 1974.

Availability of the U.S. Code on CD-ROM from the U.S. Government Printing Office. U.S. Government Printing Office, Customer Services. Circular Letter Nos. 385 (July 18, 1994), 396 (April 6, 1995), 408 (July 19, 1996), 416 (December 16, 1996), 440 (February 3, 1999), 450 (July 23, 1999), and 471 (September 22, 2000). http://www.access.gpo.gov/customer-service/cirlist.html .

CAO Strategic Plan for 2001-2005: Final Draft. Chief Administrative Officer of the U.S. House of Representatives. May 22, 2000.

CAO Team Member Feedback: CAO 2001-2005 Draft Strategic Plan. Chief Administrative Officer of the U.S. House of Representatives. [2000].

Creating Killer Web Sites: The Art of Third-Generation Site Design. By David Siegel. Hayden Books. 1996.

Drafting Federal Law. By Donald Hirsch. Office of the Legislative Counsel, U.S. House of Representatives. 2^nd edition. December 1989.

“Federal Statutes — Their History and Use” by Ralph H. Dwan and Ernest R. Feidler. Minnesota Law Review. 1938. Pages 1008-1029.

Federal Statutory Research. By Thomas B. Ripy and updated by Rita Ann Reimer. Congressional Research Service, Library of Congress. Report No. 85-219 A. May 15, 1985.

Format No. 5807 – Prelims. [Office of the Law Revision Counsel.] February 8, 1990.

Format No. 5808 – Table of Titles and Chapters. [Office of the Law Revision Counsel.] February 8, 1990.

Format No. 5809 – Analytical Index. [Office of the Law Revision Counsel.] February 8, 1990.

Format No. 5810 – Pop. Names. [Office of the Law Revision Counsel.] February 8, 1990.

Format No. 5811 – Misc. Tables. [Office of the Law Revision Counsel.] February 8, 1990.

Format No. 5812 – Statutes-at-Large (Table III). [Office of the Law Revision Counsel.] February 8, 1990.

Format No. 5813 – Tables 4 & 5. [Office of the Law Revision Counsel.] February 8, 1990.

GPO Coding for Selected Publications: Standardized locator lists and marked up samples showing how to key selected publications. U.S. Government Printing Office. February 1988.

House Legislative Counsel’s Manual of Drafting Style. Edited by Ira Forester. Office of the Legislative Counsel, U.S. House of Representatives. HLC 104-1. November 1995.

How Our Laws Are Made. By Charles W. Johnson. H. Doc. 106-197. January 31, 2000. http://frwebgate.access.gpo.gov/cgi-bin/getdoc.cgi?dbname=106_cong_documents&docid=f:hd197.pdf.

HTML Sourcebook. By Ian S. Graham. John Wiley & Sons, Inc. 3^rd edition (1997) and 4^th edition (1998).

HTML 4.01 Specification: W3C Recommendation. World Wide Web Consortium. December 24, 1999. http://www.w3.org/TR/REC-html40/

Impact of the Legal Retrieval System on H.I.S. Resources. By E. Chabot. [House Information Systems]. LS-67. October 29, 1981.

Information Process Study Report: Production of the United States Code. By Elliot C. Chabot. Committee on House Administration, House Information Systems. DN-1052. February 6, 1981.

Integrated Law Revision and Retrieval System: System Concept. By Joel DiBona, Joseph O’Brien, and Don Rollert. Committee on House Administration, House Information Systems. DN-1004. May 25, 1979.

Legal Retrieval System: Study and Recommendation. Committee on House Administration, House Information Systems. DN-1053. March 31, 1981.

Legal Retrieval System User Requirements. By A. J. J. Delehanty. Committee on House Administration, House Information Systems. DN-1008. September 28, 1979.

Legislative Branch Appropriations Bill, 1998. Report of the Committee on Appropriations. H.R. Rep. 105-196, July 22, 1997. Page 12.

Legislative Branch Appropriations for 1976. Hearings before the Subcommittee on Legislative Branch Appropriations, Committee on Appropriations, U.S. House of Representatives. U.S. Government Printing Office. 1975. Part 1, pages 901-905 (testimony of the Law Revision Counsel).

Legislative Branch Appropriations for 1977. Hearings before the Subcommittee on Legislative Branch Appropriations, Committee on Appropriations, U.S. House of Representatives. U.S. Government Printing Office. 1976. Pages 654-655 (testimony of the Law Revision Counsel).

Legislative Branch Appropriations for 1978. Hearings before the Subcommittee on Legislative Branch Appropriations, Committee on Appropriations, U.S. House of Representatives. U.S. Government Printing Office. 1977. Pages 584-585 (testimony of the Law Revision Counsel).

Legislative Branch Appropriations for 1979. Hearings before the Subcommittee on Legislative Branch Appropriations, Committee on Appropriations, U.S. House of Representatives. U.S. Government Printing Office. 1978. Pages 128-131 (testimony of the Law Revision Counsel).

Legislative Branch Appropriations for 1980. Hearings before the Subcommittee on Legislative Branch Appropriations, Committee on Appropriations, U.S. House of Representatives. U.S. Government Printing Office. 1979. Part 2, pages 1535-1546 (testimony of the Law Revision Counsel).

Legislative Branch Appropriations for 1981. Hearings before the Subcommittee on Legislative Branch Appropriations, Committee on Appropriations, U.S. House of Representatives. U.S. Government Printing Office. 1980. Part 2, pages 138-152 (testimony of the Law Revision Counsel).

Legislative Branch Appropriations for 1982. Hearings before the Subcommittee on Legislative Branch Appropriations, Committee on Appropriations, U.S. House of Representatives. U.S. Government Printing Office. 1981. Part 2, pages 321-324 (testimony of the Law Revision Counsel).

Legislative Branch Appropriations for 1983. Hearings before the Subcommittee on Legislative Branch Appropriations, Committee on Appropriations, U.S. House of Representatives. U.S. Government Printing Office. 1982. Part 2, pages 90-97 (testimony of the Law Revision Counsel).

Legislative Branch Appropriations for 1984. Hearings before the Subcommittee on Legislative Branch Appropriations, Committee on Appropriations, U.S. House of Representatives. U.S. Government Printing Office. [1983]. Part 2, pages 66-69 (testimony of the Law Revision Counsel).

Legislative Branch Appropriations for 1985. Hearings before the Subcommittee on Legislative Branch Appropriations, Committee on Appropriations, U.S. House of Representatives. U.S. Government Printing Office. [1984]. Part 2, pages 271-274 (testimony of the Law Revision Counsel).

Legislative Branch Appropriations for 1986. Hearings before the Subcommittee on Legislative Branch Appropriations, Committee on Appropriations, U.S. House of Representatives. U.S. Government Printing Office. 1985. Part 2, pages 125-129 (testimony of the Law Revision Counsel).

Legislative Branch Appropriations for 1987. Hearings before the Subcommittee on Legislative Branch Appropriations, Committee on Appropriations, U.S. House of Representatives. U.S. Government Printing Office. 1986. Part 2, pages 133-142 (testimony of the Law Revision Counsel).

Legislative Branch Appropriations for 1988. Hearings before the Subcommittee on Legislative Branch Appropriations, Committee on Appropriations, U.S. House of Representatives. U.S. Government Printing Office. 1987. Part 2, pages 84-90 (testimony of the Law Revision Counsel).

Legislative Branch Appropriations for 1989. Hearings before the Subcommittee on Legislative Branch Appropriations, Committee on Appropriations, U.S. House of Representatives. U.S. Government Printing Office. 1988. Part 2, pages 138-143 (testimony of the Law Revision Counsel).

Legislative Branch Appropriations for 1990. Hearings before the Subcommittee on Legislative Branch Appropriations, Committee on Appropriations, U.S. House of Representatives. U.S. Government Printing Office. 1989. Part 2, pages 110-119 (testimony of the Law Revision Counsel).

Legislative Branch Appropriations for 1991. Hearings before the Subcommittee on Legislative Branch Appropriations, Committee on Appropriations, U.S. House of Representatives. U.S. Government Printing Office. 1990. Part 2, pages 119-125 (testimony of the Law Revision Counsel).

Legislative Branch Appropriations for 1992. Hearings before the Subcommittee on Legislative Branch Appropriations, Committee on Appropriations, U.S. House of Representatives. U.S. Government Printing Office. 1991. Part 2, pages 189-195 (testimony of the Law Revision Counsel).

Legislative Branch Appropriations for 1993. Hearings before the Subcommittee on Legislative Branch Appropriations, Committee on Appropriations, U.S. House of Representatives. U.S. Government Printing Office. 1992. Part 2, pages 191-193 (testimony of the Law Revision Counsel).

Legislative Branch Appropriations for 1994. Hearings before the Subcommittee on Legislative Branch Appropriations, Committee on Appropriations, U.S. House of Representatives. U.S. Government Printing Office. 1993. Part 2, pages 133-139 (testimony of the Law Revision Counsel).

Legislative Branch Appropriations for 1995. Hearings before the Subcommittee on Legislative Branch Appropriations, Committee on Appropriations, U.S. House of Representatives. U.S. Government Printing Office. 1994. Part 2, pages 214-220 (testimony of the Law Revision Counsel).

Legislative Branch Appropriations for 1996. Hearings before the Subcommittee on Legislative Branch Appropriations, Committee on Appropriations, U.S. House of Representatives. U.S. Government Printing Office. 1995. Part 2, pages 110-117 (testimony of the Law Revision Counsel).

Legislative Branch Appropriations for 1997. Hearings before the Subcommittee on Legislative Branch Appropriations, Committee on Appropriations, U.S. House of Representatives. U.S. Government Printing Office. 1996. Part 2, pages 305-309 (testimony of the Law Revision Counsel).

Legislative Branch Appropriations for 1998. Hearings before the Subcommittee on Legislative Branch Appropriations, Committee on Appropriations, U.S. House of Representatives. U.S. Government Printing Office. 1997. Part 2, pages 141-148 (testimony of the Law Revision Counsel).

Legislative Branch Appropriations for 1999. Hearings before the Subcommittee on Legislative Branch Appropriations, Committee on Appropriations, U.S. House of Representatives. U.S. Government Printing Office. 1998. Part 2, page 110 (testimony of the Law Revision Counsel).

Legislative Branch Appropriations for 2000. Hearings before the Subcommittee on Legislative Branch Appropriations, Committee on Appropriations, U.S. House of Representatives. U.S. Government Printing Office. 1990. Part 2, pages 67-70 (testimony of the Law Revision Counsel).

Legislative Branch Appropriations for 2001. Hearings before the Subcommittee on Legislative Branch Appropriations, Committee on Appropriations, U.S. House of Representatives. U.S. Government Printing Office. 2000. Part 2, pages 64-66 (testimony of the Law Revision Counsel).

Legislative Information Concept Summary Report – The Legislative Process of the Future (Current and Proposed Plans). By Susan B. Miller. Committee on House Administration, House Information Systems. DN-1141. June 10, 1982.

MicroComp Grid List. U.S. Government Printing Office. May 1996.

PLWeb Turbo 2.6 Administration Guide. Personal Library Software. 1996.

Program Design Documentation, Legal Retrieval System, United States Code Database. By Douglas K. Wright. Committee on House Administration, House Information Systems. DN-1073 (April 23, 1981) & DN-1073-1 (June 23, 1982).

Publishing From a Full Text Data Base. Government Printing Office, Graphic Systems Development Division. GPO Publication 200.4. [1^st edition] September 1982; (2^nd edition) February 1983.

R-codes. By Elliot C. Chabot. [House Information Systems]. LS-82. July 7, 1982.

Report of the Legislative Branch Information and Systems Sharing Committee: Final Report. House Information Resources, Product Line Task Force. June 15, 1996.

Requirements for an XML Search Engine for Legislative Information. [Congressional Research Service, Library of Congress.] June 13, 2000. http://www.loc.gov/crsinfo/xml/xml-requirements.html.

Resolution: House Information Systems Program Plan. Committee on House Oversight. November 15, 1995. http://clerkcap.house.gov/sgmltech/Preserved/CHO1995.pdf.

Specifications for Hypertext Links in the Legal Retrieval System and LEGIS. [House Information Systems]. December 27, 1991.

Specifications for 22-column Table Software. By Elliot Chabot. [House Information Systems]. AS90-209. December 19, 1990.

Subformat Generation: MicroComp. U.S. Government Printing Office. February 1, 1997.

Summary of the MIN/ISIS/LRS Retirement Task Force (1998-1999) [House Information Resources]. [August 9, 1999].

Thoughts on Web Design. By Elliot C. Chabot. Chicago-Kent College of Law, Illinois Institute of Technology. April 19v , 1999. http://www.infoctr.edu/ill/design/design.htm

Understanding Between House Information Systems and the Department of Housing and Urban Development Concerning Data Access and Exchange, September 24, 1992.

U.S. Code CD-ROM Software. By Elliot C. Chabot. [House Information Systems]. AS91-155. August 14, 1991.

United States Code Document Analysis Report. By Betty Harvey. Electronic Commerce Connection, Inc. June 17, 1999. http://clerkcap.house.gov/sgmltech/USCode/docanalysis.pdf

U.S. Code DTD. Legislative Branch SGML Technical Committee. [December 27, 1999]. http://clerkcap.house.gov/sgmltech/uscode.html

U.S. Code Format 5804 – Miscellaneous. [Office of the Law Revision Counsel]. October 9, 1990.

U.S. Code Locator List. [Office of the Law Revision Counsel]. September 19, 1984 [with handwritten additions through January 1997].

U.S. Code Process Analysis: Preliminary Project Definition and Alternatives Analysis: Discussion Draft. House Information Resources. January 24, 2000.

United States Code Revision System: System Design. By Douglas K. Wright. [House Information Systems]. DN-1109. September 14, 1981.

United States Code Revision System: User Requirements. By Elliot C. Chabot. Committee on House Administration, House Information Systems. DN-1072. May 14, 1981.

U.S. Government Printing Office Style Manual. Government Printing Office. March 1984.

United States Law: Finding Statutory Material. By Thomas B. Ripley and Mark Gurevitz. Congressional Research Service, Library of Congress. Report No. 90-110 A. February 22, 1990. http://www.congress.gov/crsp/crspquery.html.

Web Designer’s Guide to Style Sheets. By Steven Mulder. Hyden Books. 1997.

Web Wonk: Tips for Writers and Designers. By David Siegel. 1997. http://www.dsiegal.com/tips/.

W3C Standards Support in IE and the Netscape Gecko Browser Engine. Netscape. http://home.netscape.com/browsers/future/standards.html.

XHTML™ 1.0: The Extensible HyperText Markup Language – A Reformulation of HTML 4 in XML 1.0 (Recommendation). World Wide Web Consortium. January 26, 2000. http://www.w3.org/TR/xhtml1/.

XML: It's the Future of HTML. By Todd Freter. April 2000. http://www.sun.com/980602/xml/.

XML: Principles, Tools, and Techniques. Edited by Dan Connolly. World Wide Web Journal, vol. 2, no. 4 (Winter 1997).

XML Reduced. By Leigh Dodds. October 11, 2000. http://www.xml.com/pub/2000/10/11/deviant/index.html.

Year 2000 Plan. House Information Resources. May 16, 1997.

1985 U.S. Code Data Base Usage. By Elliot C. Chabot. House Information Systems. XAS-105. February 14, 1986.

1986 Legal Retrieval System Usage. By Elliot C. Chabot. House Information Systems. XAS-138. 1987.

1987 Legal Retrieval System Usage. By Elliot C. Chabot. House Information Systems. XAS-172. March 9, 1988.

1988 Legal Retrieval System Usage. By Elliot C. Chabot. House Information Systems. IRS89-8. January 19, 1989.

1989 U.S. Code database usage. By Elliot C. Chabot. House Information Systems. AS90-102. January 9, 1990.

1990 U.S. Code database usage. By Elliot C. Chabot. House Information Systems. AS91-104. January 16, 199[1].

1991 U.S. Code database usage. By Elliot C. Chabot. House Information Systems. AS92-102. January 10, 1992.

1992 U.S. Code database usage. By Elliot C. Chabot. House Information Systems. AS93-103. January 7, 1993.

1993 U.S. Code database usage. By Elliot C. Chabot. House Information Systems. AS94-009. January 12, 1994.

1994 U.S. Code database usage. By Elliot C. Chabot. House Information Systems. AS95-20. February 10, 1995.

1995 U.S. Code database usage. By Elliot C. Chabot. House Information Resources. February 13, 1996.

1996 Annual U.S. Code Database Usage Report. By Elliot C. Chabot. House Information Resources. January 22, 1997.

[1] The Statutes at Large, the other official compilation of Federal statutes, differs from the U.S. Code in that the Statutes at Large is organized in chronological order and includes all of the laws enacted by Congress, while the U.S. Code is organized in subject order and includes only those laws that are of a “general and permanent nature”. Amendments to laws are incorporated directly into the laws being amended in the U.S. Code. In the Statutes at Large, however, amendments are not incorporated into the original laws – they are treated as separate laws and are presented chronologically based on the their date of enactment. The Statutes at Large are compiled under the authority of the Archivist of the United States. 1 U.S.C. § 112.

The United States Code Annotated (published by West Group), the U.S. Code Service (published by Lexis Law Publishing), and the compilations of acts published by the committees of the House and Senate are not official compilations recognized by law.

[2] 1 U.S.C. § 204(a); 2 U.S.C. §§ 285a, 285b(3), (4), 285c.

[3] From its creation until July of 1995, the computer and high technology support staff of the House of Representatives was known as House Information Systems (HIS). On July 1, 1995, HIS merged with the Office of Telecommunications Services and became House Information Resources (HIR).

[4] The Integrated Law Revision and Retrieval System Concept, (Joel DiBona, Joseph O’Brien, and Don Rollert), Committee on House Administration, House Information Systems, DN-1004, May 25, 1979, was approved by the Law Revision Counsel, the Government Printing Office, and the Committee on House Administration in 1979. Legislative Branch Appropriations for 1981, hearing before the Subcommittee on Legislative Branch Appropriations, Committee on Appropriations, U.S. House of Representatives, 1980, part 2, pages 145-146.

[5] The system of tags is the GPO photocomposition code scheme and is described in detail in Publishing From a Full Text Data Base, U.S. Government Printing Office, Graphic Systems Development Division, GPO Pub. No. 200.4 (2^nd ed.), February 1983; R-codes, (Elliot Chabot) [House Information Systems], LS-82, July 7, 1982; U.S. Code Locator List, [Office of the Law Revision Counsel], September 19, 1984; GPO Coding for Selected Publications: Standardized locator lists and marked up samples showing how to key selected publications, U.S. Government Printing Office, February 1988; Format No. 5807 – Prelims, [Office of the Law Revision Counsel], February 8, 1990; Format No. 5808 – Table of Titles and Chapters, [Office of the Law Revision Counsel], February 8, 1990; Format No. 5809 – Analytical Index, [Office of the Law Revision Counsel], February 8, 1990; Format No. 5810 – Pop. Names, [Office of the Law Revision Counsel], February 8, 1990; Format No. 5811 – Misc. Tables, [Office of the Law Revision Counsel], February 8, 1990; Format No. 5812 – Statutes-at-Large (Table III), [Office of the Law Revision Counsel], February 8, 1990; Format No. 5813 – Tables 4 & 5, [Office of the Law Revision Counsel], February 8, 1990; U.S. Code Format 5804 – Miscellaneous, [Office of the Law Revision Counsel], October 9, 1990; Microcomp Grid List, U.S. Government Printing Office, May 1996; and Subformat Generation: MicroComp, U.S. Government Printing Office, February 1, 1997.

[6] The editing software for the U.S. Code was based on ATEX (from Digital Equipment Corp.), which ran on DEC PDP/1100 series hardware. The Counsel’s ATEX became fully operational in January of 1982 (prior to that, the Counsel’s office had been using space on the Clerk’s Bill Processing System housed in 2403 Rayburn House Office Building). In 1996, the ATEX software was replaced by XYWrite (a PC-based clone of ATEX). Requirements and design documentation for the ATEX system can be found at United States Code Revision System: User Requirements, (Elliot C. Chabot), Committee on House Administration, House Information Systems, DN-1072, May 14, 1981; and United States Code Revision System: System Design, (Douglas K. Wright), [House Information Systems], DN-1109, September 14, 1981.

[7] The software to handle typesetting was MTP (the “Multi-Typography Program”) which was developed in-house by GPO. By the mid-1990’s, MTP was replaced by MicroComp (also developed in-house by GPO).

[8] Legal Retrieval System User Requirements, (A. J. J. Delehanty), Committee on House Administration, House Information Systems, DN-1008, September 28, 1979; Legal Retrieval System: Study and Recommendation, Committee on House Administration, House Information Systems, DN-1053, March 31, 1981; and U.S. Code Process Analysis: Preliminary Definition and Alternatives Analysis, Discussion Draft, House Information Resources, January 24, 2000, chapter 6.

[9] The U.S. Code Classification Table was first produced in 1980 as a printed document, with data entry done on the Law Revision Counsel’s ATEX system while sorting and printing were done through the HIS mainframe.

[10] Access to the STAIRS-based mainframe system (other than for data integrity testing) was ended effective December 1, 1998, as part of phase IV of the retirement of the HIR mainframe information services (MIN, ISIS, and LRS), except for internal use by HIR staff for data integrity testing. Access to on-line STAIRS was eliminated for even internal use on January 1, 2000. HIR staff continue to have batch access to STAIRS for U.S. Code data integrity testing.

[11] The first edition of the U.S. Code CD-ROM (containing the laws enacted through January 2, 1991) was released in January 1993. Since that time, the U.S. Code CD-ROM has been produced annually by HIR. Distribution and merchandising of the CD-ROM is done through the Government Printing Office.

[13] The Committee on House Oversight Resolution (House Information Systems Program Plan) of November 15, 1995, provides in part that: “The Director of House Information Resources is directed to submit to the Committee for review and approval by the Chairman . . . a plan for the incremental implementation of the following specific programs as described in the Information Systems Program Plan: . . . 3. A report on the specific issues that must be addressed in preparation for retirement of the IBM mainframe system following retirement of the legacy MIN, ISIS, LIMS, and FMS systems”. http://clerkcap.house.gov/sgmltech/Preserved/CHO1995.pdf.

[14] The retirement of the STAIRS-based mainframe U.S. Code database was part of phase IV of the retirement of the HIR mainframe information services (MIN, ISIS, and LRS). Internal access to the on-line STAIRS system, by HIR staff for data integrity testing continued until January 1, 2000. HIR staff continue to have batch access to STAIRS for U.S. Code data integrity testing.

[15] CAO Strategic Plan for 2001-2005: Final Draft. Chief Administrative Officer of the U.S. House of Representatives. May 22, 2000, page 5 (objective 4, measure 3).

[16] HIR Action Item 96-515, letter of June 10, 1996, from the Law Revision Counsel to the Associate Administrator, House Information Resources.

[17] There are substantial differences between how those versions of Netscape Communicator and Microsoft Internet Explorer that are XML-compatible have implemented XML. See, for instance, Netscape Communications Corp., W3C Standards Support in IE and the Netscape Gecko Browser Engine, (2000), http://home.netscape.com/browsers/future/standards.html.

[18] Letter of August 31, 2000, from the Clerk of the House to the Chairman of the Committee on House Administration, transmitting the SGML/XML Feasibility Study Final Report.

[19] Material on the Technical Committee is available at http://clerkcap.house.gov/sgmltech/.

[20] World Wide Web Consortium, XHTML 1.0: The Extensible HyperText Markup Language – A Reformulation of HTML 4 in XML 1.0 (Recommendation), January 26, 2000, http://www.w3.org/TR/2000/REC-xhtml1-20000126/. The guidance includes having an end tag for all non-empty begin tags (including <p> tags), making all HTML tags lower case, putting all tag attribute values in quotation marks (e.g., <table border=“3”> instead of <table border=3>), and using the “id” attribute with the <a> tag, instead of (or in addition to) the “name” attribute.

[21] The STAIRS version of the U.S. Code allowed for the use of only one font (which was fixed-pitch and could only be in one point size), did not allow for anchors or hypertext links, and was limited to standard ASCII characters.

[22] Kollar, Charles P., John R. R. Leavitt, and Michael Mauldin, “Robot Exclusion Standard Revisited,” (June 2, 1996), http://www.kollar.com/robots.html .

[24] http://www.w3.org/TR/WAI-WEBCONTENT/. Conformance level A is the standard for the “Bobby” web site accessibility analysis software, http://www.cast.org/Bobby/.

[25] In the HTML 4.01 Standard, this is represented as “ ”. The character definitions for HTML 4.01 can be found at http://www.w3.org/TR/html4/sgml/entities.html .

[26] In the HTML 4.01 Standard, this is represented as “ ”.

[27] In the HTML 4.0 Standard, this is represented as “−”.

[28] In the HTML 4.0 Standard, this is represented as “—”. The standard ASCII representation of a hex 5F is an underscore, rather than an emdash.

[29] If the ESC character (followed by two characters) occurs while the value of {Grid} is greater than 4, then instead of following the instructions contained in the list, convert the three characters into a single character of the Hex value indicated by the last two characters. An example can be found at 17 U.S.C. § 401 note (Universal Copyright Convention, Paris, 1971, art. III, § 1) where an ESC AF occurs when {Grid} equals 6 and {Typeface} equals 1. In that case, ESC AF should be translated into a Hex AF character and then processed according to the bell-G and bell-T rules for Grid 6, Typeface 1, Hex AF.

[30] Do not count as a blank space any blank that is within a pair of angle brackets (e.g., ).

[31] For purposes of this rule, do not count a bell-g, bell-G, bell-K, or bell-T as a bell-code. Include a bell-code’s argument as part of the bell-code (e.g., bell-I04 would be a bell code).

[32] Do not count as a blank space any blank that is within a pair of angle brackets (e.g., ).

[33] For purposes of this rule, do not count a bell-g, bell-G, bell-K, or bell-T as a bell-code. Include a bell-code’s argument as part of the bell-code (e.g., bell-I04 would be a bell code).

[34] If there was more than one  between the <nobr> and the </nobr>, then (after the first occurrence) only execute the portion of step 5 that translates  into a dash.

[35] An example can be found at 28 U.S.C. app. (Fed. Cl. R.) app. E.

[36] For a description of the technical terms used to describe the elements of tabular data, see chapter 13 (especially pages 192-193) of the United States Government Printing Office Style Manual (March 1984). For a complete description of tabular data processing using GPO’s photocomposition software, see U.S. Government Printing Office, Subformat Generation: MicroComp, (February 1, 1997).

[37] The value of {bearoff} is also set in bell-c instructions A.4(a) and A.12(d)(i).

[38] The value of {leading} is also adjusted by bell-I, bell-q, bell-Q, and bell-R.

[39] The value of {rules value} is also set in bell-c instructions A.2(c) and A.3(k) to (m).

[40] An example can be found at 15 U.S.C. § 205. Other values of {text field} are processed in bell-c instruction C(bell-I95).

[41] {number of columns in table} is multiplied by two to allow for pseudo-columns created by “p” (parallel lines) and “b” (bold) vertical line instructions

[42] {number of columns in table} is multiplied by two to allow for pseudo-columns created by “p” (parallel lines) and “b” (bold) vertical line instructions

[43] An example can be found at 5 U.S.C. § 5332 note (sched. 3).

[44] An example can be found at 21 U.S.C. § 350a(i)(2)(B).

[45] An example can be found at 1 U.S.C. prec. ch. 1.

[46] L3 is not currently used in the U.S. Code. An explanation of its use, however, is contained in the Government Printing Office’s Subformat Generation MicroComp (February 1, 1997), on page 3 (item 2).

[47] L4 is not currently used in the U.S. Code. An explanation of its use, however, is contained in the Government Printing Office’s Subformat Generation MicroComp (February 1, 1997), on page 3 (item 2).

[48] L5 is not currently used in the U.S. Code. An explanation of its use, however, is contained in the Government Printing Office’s Subformat Generation MicroComp (February 1, 1997), on page 3 (item 2).

[49] L6 is not currently used in the U.S. Code. An explanation of its use, however, is contained in the Government Printing Office’s Subformat Generation MicroComp (February 1, 1997), on page 3 (item 2).

[50] The value for {rules value} is also set in c-code instructions A.1(l) and A.3(k) to (m).

[51] An example can be found at 15 U.S.C. § 205 note.

[52] An example can be found at 42 U.S.C. § 300x-7(a)(1).

[53] The value of {rules value} is also set by c-code instructions A.1(l), A.2(c), and A.3(k), (l).

[54] The value of {rules value} is also set by c-code instructions A.1(l), A.2(c), and A.3(j-1), (l).

[55] The value of {rules value} is also set by c-code instructions A.1(l), A.2(c), and A.3(j-1), (k).

[56] An example can be found at 5 U.S.C. § 5332 note (sched. 1).

[57] The value for {bearoff} is also calculated at c-code instructions A.1(d) and A.12(d)(i).

[58] An example can be found at 11 U.S.C. app. (Bankr. R.) rule 7001 note.

[59] An example can be found at 15 U.S.C. § 205.

[60] An example can be found at 16 U.S.C. § 460u-3.

[61] The “j” option is not currently used in the U.S. Code. An explanation of its use, however, is contained in the Government Printing Office’s Subformat Generation MicroComp (February 1, 1997), on page 4 (item 7).

[62] An example can be found at 16 U.S.C. § 3631(f).

[63] The “lt” option is not currently used in the U.S. Code. An explanation of its use, however, is contained in the Government Printing Office’s Subformat Generation MicroComp (February 1, 1997), on page 4 (item 9).

[64] An example can be found at 1 U.S.C. prec. ch. 1.

[66] I96 designates a headnote. I97 designates a headnote which does not include “—continued” when it is reprinted. I96 and I97 have the same font size.

[67] An example can be found at 4 U.S.C. § 1 note (Ex. Ord. No. 10798, § 21).

[68] An example can be found at 5 U.S.C. § 5332 note (sched. 1).

[69] An example can be found at 5 U.S.C. § 101 note (Historical and Revision Notes).

[70] An example can be found at 21 U.S.C. § 350a(i)(2)(B).

[71] An example can be found at 1 U.S.C. prec. ch. 1.

[72] An example can be found at 5 U.S.C. § 5332 note (sched. 3).

[73] An example can be found at 28 U.S.C. app. (Fed. Cl. R.) app. J (rule 16).

[74] An example can be found at 7 U.S.C. § 1448.

[75] An example can be found at 1 U.S.C. prec. ch. 1.

[76] An example can be found at 2 U.S.C. § 631.

[77] Examples can be found at 19 U.S.C. § 3332(b)(2)(A), (3)(A).

[78] The value for {bearoff} is also calculated at c-code instructions A.1(d) and A.4(a).

[79] An example can be found at 17 U.S.C. § 104 note (Particular Proclamations, Treaties and Conventions Establishing Copyright Relations Between the United States of America and Other Countries).

[80] An example can be found at 42 U.S.C. § 300x-7(a)(1).

[81] An example can be found at 42 U.S.C. § 300x-7(a)(1).

[82] An example can be found at 28 U.S.C. app. (Fed. Cl. R.) app. J (rule 16).

[83] An example can be found at 28 U.S.C. app. (Fed. Cl. R.) app. J (rule 16).

[84] This function is not currently used in the U.S. Code. An explanation of its use, however, is contained in the Government Printing Office’s Subformat Generation MicroComp (February 1, 1997), on page 4 (item 15).

[85] An example can be found at Table V. The “o” followed by a number has the same effect as the “aw” followed by a number.

[86]An example can be found at 26 U.S.C. § 1252(a)(3).

[87] An example can be found at 4 U.S.C. § 1 note (Ex. Ord. No. 10798, § 21).

[88] An example can be found at 1 U.S.C. prec. ch. 1.

[89] An example (without a suffix letter) can be found at 1 U.S.C. prec. ch. 1. An example (with a suffix C) can be found at 4 U.S.C. § 1 note (Ex. Ord. No. 10834, § 33). An example (with a suffix n) can be found at 28 U.S.C. app. (Sup. Ct. R.) rule 33(1)(g).

[90] An example can be found at 21 U.S.C. § 350a(i)(2)(B). HTML 4.0 Sourcebook (pp. 299 & 293) by Ian S. Graham indicates that Internet Explorer 4.0 and Netscape do not yet support the align=“char” attribute to the <td> tag. An alternative approach to processing the alignment column would be to break the material into two columns with the left column flush right and the right column flush left, have alignment character at the end of the first column, and make sure that the vertical rule between the two columns is invisible.

[91] An example can be found at 11 U.S.C. app. (Bankr. R.) rule 7001 note.

[92] An example can be found at 1 U.S.C. prec. ch. 1.

[93] An example (without a suffix letter) can be found at 5 U.S.C. § 101 note.

[94] An example (with a suffix “C”) can be found at 10 U.S.C. § 6333(a).

[95] {column width in pixels}_{column} must be stored as a whole number – after calculating the value of {column width in pixels}_{column}, according to the formula in step B.8(b)(I), then round off the result to the nearest whole number.

[96] An example can be found at 16 U.S.C. § 431 note (National Monuments Established Under Presidential Proclamation).

[97] The exception to this rule is if the bell is part of a bell-b, bell-g, bell-G, bell-K, bell-l, bell-oi, bell-P, bell-t, bell-T, or bell-xl. In any of those cases continue to the next bell. Once that processing has been completed, go back to bell-b, bell-g, bell-G, bell-K, bell-l, bell-oi, bell-P, bell-t, or bell-T that was bypassed, and process them.

[98] The value of {bottom of boxhead rule weight} is set by c-code instructions A.3(b) and (d).

[100] An example can be found at 5 U.S.C. § 5332 note (sched. 3).

[101] This calculation is to satisfy the test in c-code instruction F(1).

[102] With two exceptions, the starting point should be the point previously stored in Step 8(a): (1) If this is the first time that Step 8 has been reached in this table, then start at the beginning of the {boxheads file}; and (2) if Steps 5, 6, and 7 have just been executed, then start at the beginning of the {boxheads file}.

[103] Any bell-h will satisfy this test – it is not necessary for the bell-h to be a bell-h{original bell-h argument}.

[104] If there is a bell-G or a bell-T within the text between the h-code whose position was stored in Step 8(a) and the bell-j, then process the data using the standard bell-G and bell-T processing instructions. If there are bell codes within the text between the h-code whose position was stored in Step 8(a) and the bell-j, then process the data using the standard instructions from the table of bell codes within bell-c tables. If there is a special character within the text between the h-code whose position was stored in Step 8(a) and the bell-j, then process the data using the standard special characters processing instructions.

[105] An example can be found at 26 U.S.C. § 1252(a)(3).

[106] An example can be found at 42 U.S.C. § 300x-7(a)(1).

[107] If there is a bell-G or a bell-T within the text between the h-code whose position was stored in Step 8(a) and the bell-h (or bell-j), then process the data using the standard bell-G and bell-T processing instructions, except that where the instructions call for outputting text, both output it and add it to the {repeated headings file}. If there are other bell codes within the text between the h-code whose position was stored in Step 8(a) and the bell-h (or bell-j), then process the data using the standard instructions from the table of bell codes within bell-c tables, except that where the instructions call for outputting text, both output it and add it to the {repeated headings file}. If there is a special character within the text between the h-code whose position was stored in Step 8(a) and the bell-h (or bell-j), then process the data using the standard special characters processing instructions, except that where the instructions call for outputting text, both output it and add it to the {repeated headings file}.

[108] An example can be found at 42 U.S.C. § 300x-7(a)(1).

[109] The Government Printing Office’s Subformat Generation MicroComp (February 1, 1997), p. 6 (item G) describes the use of quad-right and quad-left characters in conjunction with horizontal rule processing. The quad-right and quad-left features, however, have not been implemented in GPO’s MicroComp software and those features are therefore not currently used in the U.S. Code. Logic for converting the quad-right and quad-left features into HTML are set out at in the notes at the end of these specifications.

[110] An example can be found at 33 U.S.C. § 1285(c)(2).

[111] An example can be found at 33 U.S.C. § 1285(c)(2).

[112] An example can be found at 15 U.S.C. § 205.

[113] An example can be found at 5 U.S.C. prec. pt. I (Table Showing Disposition of All Sections of Former Title 5).

[114] {Format} numbers can also be set by the bell-S.

[115] An example of the “d” argument can be found at 4 U.S.C. § 1 note (Ex. Ord. No. 10834, § 33), where the bell-g is followed by “s,d222”. In that example, {graphic depth} would be 333. The {graphic depth} variable is used in graphic processing.

[116] An example of bell-T1 can be found at 1 U.S.C. § 106 note (Pub. L. 104-207, § 1). An example of bell-T2 can be found at 1 U.S.C. ch. 1 (see also, 2 U.S.C. § 59(f)(3)(B)). Examples of bell-T3 and bell-T4 can be found at 1 U.S.C. § 106 note (Pub. L. 100-360, § 411(a)(2)). If the argument is not 1, 2, 3, or 4, then

(a) add the following to {error file}: {HIERARCHICAL INFORMATION}₁ USC {SECTION NUMBER}{long subsection} ({text field}) – unidentified process, bell-T{typeface}

(b) set {typeface} to 1

[117] If the argument is not a number between 1 and 8, then add to the {error file}: {TITLE NUMBER} USC{appendix}{SECTION NUMBER}{long subsection} ({text field}) – warning – possible character mistranslation – grid 2, typeface {typeface}, hex {hex value of unidentified character}

[121] An example can be found at 17 U.S.C. § 104 note (Particular Proclamations, Treaties and Conventions Establishing Copyright Relations Between the United States and Other Countries, Czechoslovakia).

[122] An example can be found at 7 U.S.C. § 1314c(g)(1).

[123] An example can be found at 28 U.S.C. app. (Fed. R. App. P.) rule 32 note (Committee Notes on Rules 1998 Amendment, ¶ (a)(5)).

[124] An example can be found at 28 U.S.C. app. (Fed. R. App. P.) rule 32 note (Committee Notes on Rules 1998 Amendment, ¶ (a)(5)).

[125] Do not count as a blank space any blank that is within a pair of angle brackets (e.g., ).

[126] For purposes of this rule, do not count a bell-g, bell-G, bell-K, or bell-T as a bell-code.

[128] Do not count as a blank space any blank that is within a pair of angle brackets (e.g., ).

[129] For purposes of this rule, do not count a bell-g, bell-G, bell-K, or bell-T as a bell-code.

[131] If there was more than one  between the <nobr> and the </nobr>, then (after the first occurrence) only execute the portion of step 5 that translates  into a dash.

[132] Do not count as a blank space any blank that is within a pair of angle brackets (e.g., ).

[133] For purposes of this rule, do not count a bell-g, bell-G, bell-K, or bell-T as a bell-code.

[135] Do not count as a blank space any blank that is within a pair of angle brackets (e.g., ).

[136] For purposes of this rule, do not count a bell-g, bell-G, bell-K, or bell-T as a bell-code.

[138] If there was more than one  between the <nobr> and the </nobr>, then (after the first occurrence) only execute the portion of step 5 that translates  into a dash.

[139] Do not count as a blank space any blank that is within a pair of angle brackets (e.g., ).

[140] For purposes of this rule, do not count a , bell-g, bell-G, bell-K, or bell-T as a bell-code.

[142] Do not count as a blank space any blank that is within a pair of angle brackets (e.g., ).

[143] For purposes of this rule, do not count a bell-g, bell-G, bell-K, or bell-T as a bell-code.

[145] If there was more than one  between the <nobr> and the </nobr>, then (after the first occurrence) only execute the portion of step 5 that translates  into a dash.

[146] Do not count as a blank space any blank that is within a pair of angle brackets (e.g., ).

[147] For purposes of this rule, do not count a bell-g, bell-G, bell-K, or bell-T as a bell-code.

[149] Do not count as a blank space any blank that is within a pair of angle brackets (e.g., ).

[150] For purposes of this rule, do not count a bell-g, bell-G, bell-K, or bell-T as a bell-code.

[152] If there was more than one  between the <nobr> and the </nobr>, then (after the first occurrence) only execute the portion of step 5 that translates  into a dash.

[153] An example of typeface 2 can be found at 42 U.S.C. § 7521(g)(1).

[154] An example of typeface 1 can be found at 42 U.S.C. § 1395ww note (Amendments, subsection (d)(5)(B)(ii)(I)). An example of typeface 2 can be found at 42 U.S.C. 7407 note (Ozone and Particulate Matter Standards, § 6101(a)(1)).

[155] An example of typeface 1 can be found at 42 U.S.C. § 1395ww (Amendments, subsection (d)(5)(B)(ii)(I)). An example of typeface 2 can be found at 22 U.S.C. § 7601(10)(A).

[156] An example of typeface 2 can be found at 22 U.S.C. § 7601(10)(A).

[157] An example of typeface 2 can be found at 42 U.S.C. § 7412(b)(1)(footnote 1).

[158] An example of typeface 2 can be found at 18 U.S.C. § 841(p)(1).

[159] Examples of typefaces 1 and 2 can be found at 16 U.S.C. § 460bb-1 note (Phelgen Estate Auction).

[160] An example of typeface 1 can be found at 42 U.S.C. § 1395ww note (Amendments, subsection (d)(5)(B)(ii)(I)). En example of typeface 2 can be found at 42 U.S.C. § 7407 note (Ozone and Particulate Matter Standards, § 6101(a)(1)).

[161] Examples of typefaces 1 and 2 can be found at 16 U.S.C. § 460bb-1 note (Phelgen Estate Auction).

[162] An example of typeface 1 can be found at 42 U.S.C. § 1395ww note (Amendments, subsection (d)(5)(B)(ii)(II)).

[163] An example of typeface 2 can be found at 42 U.S.C. § 2297h-10(b)(2)(D).

[164] An example of typeface 1 can be found at 42 U.S.C. § 1395ww note (Amendments, subsection (d)(5)(B)(ii)(II)).

[166] An example of typeface 1 can be found at Constitution (signatures).

[167] An example of typeface 1 can be found at Constitution (signatures).

[168] An example of typeface 1 can be found at Constitution (signatures).

[169] An example of typeface 1 can be found at Constitution (signatures).

[170] An example of typeface 1 can be found at Constitution (signatures).

[171] An example of typeface 1 can be found at Constitution (signatures).

[172] An example of typeface 1 can be found at Constitution (signatures).

[173] An example of typeface 1 can be found at 42 U.S.C. § 6924(n)(5)(B).

[174] Do not count as a blank space any blank that is within a pair of angle brackets (e.g., ).

[175] For purposes of this rule, do not count a bell-g, bell-G, bell-K, or bell-T as a bell-code.

[177] Do not count as a blank space any blank that is within a pair of angle brackets (e.g., ).

[178] For purposes of this rule, do not count a bell-g, bell-G, bell-K, or bell-T as a bell-code.

[180] Do not count as a blank space any blank that is within a pair of angle brackets (e.g., ).

[181] For purposes of this rule, do not count a bell-g, bell-G, bell-K, or bell-T as a bell-code.

[183] Do not count as a blank space any blank that is within a pair of angle brackets (e.g., ).

[184] For purposes of this rule, do not count a bell-g, bell-G, bell-K, or bell-T as a bell-code.

[186] Do not count as a blank space any blank that is within a pair of angle brackets (e.g., ).

[187] For purposes of this rule, do not count a bell-g, bell-G, bell-K, or bell-T as a bell-code.

[189] Do not count as a blank space any blank that is within a pair of angle brackets (e.g., ).

[190] For purposes of this rule, do not count a bell-g, bell-G, bell-K, or bell-T as a bell-code.

[192] Do not count as a blank space any blank that is within a pair of angle brackets (e.g., ).

[193] For purposes of this rule, do not count a bell-g, bell-G, bell-K, or bell-T as a bell-code.

[195] Do not count as a blank space any blank that is within a pair of angle brackets (e.g., ).

[196] For purposes of this rule, do not count a bell-g, bell-G, bell-K, or bell-T as a bell-code.

[198] Do not count as a blank space any blank that is within a pair of angle brackets (e.g., ).

[199] For purposes of this rule, do not count a bell-g, bell-G, bell-K, or bell-T as a bell-code.

[201] Do not count as a blank space any blank that is within a pair of angle brackets (e.g., ).

[202] For purposes of this rule, do not count a bell-g, bell-G, bell-K, or bell-T as a bell-code.

[204] Do not count as a blank space any blank that is within a pair of angle brackets (e.g., ).

[205] For purposes of this rule, do not count a bell-g, bell-G, bell-K, or bell-T as a bell-code.

[207] Do not count as a blank space any blank that is within a pair of angle brackets (e.g., ).

[208] For purposes of this rule, do not count a bell-g, bell-G, bell-K, or bell-T as a bell-code.

[210] Do not count as a blank space any blank that is within a pair of angle brackets (e.g., ).

[211] For purposes of this rule, do not count a bell-g, bell-G, bell-K, or bell-T as a bell-code.

[213] Do not count as a blank space any blank that is within a pair of angle brackets (e.g., ).

[214] For purposes of this rule, do not count a bell-g, bell-G, bell-K, or bell-T as a bell-code.

[216] Do not count as a blank space any blank that is within a pair of angle brackets (e.g., ).

[217] For purposes of this rule, do not count a bell-g, bell-G, bell-K, or bell-T as a bell-code.

[219] Do not count as a blank space any blank that is within a pair of angle brackets (e.g., ).

[220] For purposes of this rule, do not count a bell-g, bell-G, bell-K, or bell-T as a bell-code.

[222] An example of typeface 2 can be found at 42 U.S.C. § 7412(b)(1)(footnote 2).

[223] An example of typeface 3 can be found at Constitution (signatures).

[224] An example of typeface 2 can be found at 42 U.S.C. ch. 85 (prec. § 7401).

[226] An example of typeface 1 can be found at 16 U.S.C. § 461 note (Proc. No. 3339).

[227] An example of typeface 1 can be found at 17 U.S.C. § 401 note (Universal Copyright Convention, Paris, 1971, art. III, § 1).

[228] Do not count as a blank space any blank that is within a pair of angle brackets (e.g., ).

[229] For purposes of this rule, do not count a bell-g, bell-G, bell-K, or bell-T as a bell-code.

[231] Do not count as a blank space any blank that is within a pair of angle brackets (e.g., ).

[232] For purposes of this rule, do not count a bell-g, bell-G, bell-K, or bell-T as a bell-code.

[234] If there was more than one  between the <nobr> and the </nobr>, then (after the first occurrence) only execute the portion of step 5 that translates  into a dash.

[235] Do not count as a blank space any blank that is within a pair of angle brackets (e.g., ).

[236] For purposes of this rule, do not count a bell-g, bell-G, bell-K, or bell-T as a bell-code.

[238] Do not count as a blank space any blank that is within a pair of angle brackets (e.g., ).

[239] For purposes of this rule, do not count a bell-g, bell-G, bell-K, or bell-T as a bell-code.

[241] If there was more than one  between the <nobr> and the </nobr>, then (after the first occurrence) only execute the portion of step 5 that translates  into a dash.

[242] Do not count as a blank space any blank that is within a pair of angle brackets (e.g., ).

[243] For purposes of this rule, do not count a , bell-g, bell-G, bell-K, or bell-T as a bell-code.

[245] Do not count as a blank space any blank that is within a pair of angle brackets (e.g., ).

[246] For purposes of this rule, do not count a bell-g, bell-G, bell-K, or bell-T as a bell-code.

[248] If there was more than one  between the <nobr> and the </nobr>, then (after the first occurrence) only execute the portion of step 5 that translates  into a dash.

[249] Do not count as a blank space any blank that is within a pair of angle brackets (e.g., ).

[250] For purposes of this rule, do not count a bell-g, bell-G, bell-K, or bell-T as a bell-code.

[252] Do not count as a blank space any blank that is within a pair of angle brackets (e.g., ).

[253] For purposes of this rule, do not count a bell-g, bell-G, bell-K, or bell-T as a bell-code.

[255] If there was more than one  between the <nobr> and the </nobr>, then (after the first occurrence) only execute the portion of step 5 that translates  into a dash.

[256] An example of typeface 1 can be found at 19 U.S.C. § 3332(b)(2)(A).

[257] An example of typeface 1 can be found at 42 U.S.C. § 254o(b)(1)(A).

[258] An example of typeface 1 can be found at 42 U.S.C. § 254o(b)(1)(A).

[259] An example of typeface 1 can be found at 42 U.S.C. § 6295(i)(1)(A).

[261] An example can be typeface 1 can be found at 38 U.S.C. § 7617(c)(1)).

[262] An example of typeface 1 can be found at 42 U.S.C. § 1395ww(d)(5)(F)(vii)(I)(a).

[263] Do not count as a blank space any blank that is within a pair of angle brackets (e.g., ).

[264] For purposes of this rule, do not count a bell-g, bell-G, bell-K, or bell-T as a bell-code.

[266] Do not count as a blank space any blank that is within a pair of angle brackets (e.g., ).

[267] For purposes of this rule, do not count a bell-g, bell-G, bell-K, or bell-T as a bell-code.

[269] Do not count as a blank space any blank that is within a pair of angle brackets (e.g., ).

[270] For purposes of this rule, do not count a bell-g, bell-G, bell-K, or bell-T as a bell-code.

[272] Do not count as a blank space any blank that is within a pair of angle brackets (e.g., ).

[273] For purposes of this rule, do not count a bell-g, bell-G, bell-K, or bell-T as a bell-code.

[275] Do not count as a blank space any blank that is within a pair of angle brackets (e.g., ).

[276] For purposes of this rule, do not count a bell-g, bell-G, bell-K, or bell-T as a bell-code.

[278] Do not count as a blank space any blank that is within a pair of angle brackets (e.g., ).

[279] For purposes of this rule, do not count a bell-g, bell-G, bell-K, or bell-T as a bell-code.

[281] Do not count as a blank space any blank that is within a pair of angle brackets (e.g., ).

[282] For purposes of this rule, do not count a bell-g, bell-G, bell-K, or bell-T as a bell-code.

[284] Do not count as a blank space any blank that is within a pair of angle brackets (e.g., ).

[285] For purposes of this rule, do not count a bell-g, bell-G, bell-K, or bell-T as a bell-code.

[288] Do not count as a blank space any blank that is within a pair of angle brackets (e.g., ).

[289] For purposes of this rule, do not count a bell-g, bell-G, bell-K, or bell-T as a bell-code.

[291] Do not count as a blank space any blank that is within a pair of angle brackets (e.g., ).

[292] For purposes of this rule, do not count a bell-g, bell-G, bell-K, or bell-T as a bell-code.

[294] Do not count as a blank space any blank that is within a pair of angle brackets (e.g., ).

[295] For purposes of this rule, do not count a bell-g, bell-G, bell-K, or bell-T as a bell-code.

[297] Do not count as a blank space any blank that is within a pair of angle brackets (e.g., ).

[298] For purposes of this rule, do not count a bell-g, bell-G, bell-K, or bell-T as a bell-code.

[301] Do not count as a blank space any blank that is within a pair of angle brackets (e.g., ).

[302] For purposes of this rule, do not count a bell-g, bell-G, bell-K, or bell-T as a bell-code.

[304] Do not count as a blank space any blank that is within a pair of angle brackets (e.g., ).

[305] For purposes of this rule, do not count a bell-g, bell-G, bell-K, or bell-T as a bell-code.

[307] Do not count as a blank space any blank that is within a pair of angle brackets (e.g., ).

[308] For purposes of this rule, do not count a bell-g, bell-G, bell-K, or bell-T as a bell-code.

[310] Do not count as a blank space any blank that is within a pair of angle brackets (e.g., ).

[311] For purposes of this rule, do not count a bell-g, bell-G, bell-K, or bell-T as a bell-code.

[313] An example of typeface 1 can be found at 42 U.S.C. § 254o(b)(1)(A).

[314] An example of typeface 1 can be found at 21 U.S.C. § 350a(i)(2)(B).

[316] An example of typeface 1 can be found at 15 U.S.C. § 1111.

[317] An example of typeface 1 can be found at 48 U.S.C. § 1705 note (Proc. No. 4346).

[318] An example of typeface 1 can be found at 28 U.S.C. § 2254 note (Rules Governing Section 2254 Cases in United States District Courts, Appendix of Forms, In Forma Pauperis Declaration, § 1)

[319] An example of typeface 2 can be found at 5 U.S.C. § 601 note (Plain Language in Government Writing).

[320] Do not count as a blank space any blank that is within a pair of angle brackets (e.g., ).

[321] For purposes of this rule, do not count a bell-g, bell-G, bell-K, or bell-T as a bell-code.

[323] Do not count as a blank space any blank that is within a pair of angle brackets (e.g., ).

[324] For purposes of this rule, do not count a bell-g, bell-G, bell-K, or bell-T as a bell-code.

[326] If there was more than one  between the <nobr> and the </nobr>, then (after the first occurrence) only execute the portion of step 5 that translates  into a dash.

[327] Do not count as a blank space any blank that is within a pair of angle brackets (e.g., ).

[328] For purposes of this rule, do not count a bell-g, bell-G, bell-K, or bell-T as a bell-code.

[330] Do not count as a blank space any blank that is within a pair of angle brackets (e.g., ).

[331] For purposes of this rule, do not count a bell-g, bell-G, bell-K, or bell-T as a bell-code.

[333] If there was more than one  between the <nobr> and the </nobr>, then (after the first occurrence) only execute the portion of step 5 that translates  into a dash.

[334] Do not count as a blank space any blank that is within a pair of angle brackets (e.g., ).

[335] For purposes of this rule, do not count a bell-g, bell-G, bell-K, or bell-T as a bell-code.

[337] Do not count as a blank space any blank that is within a pair of angle brackets (e.g., ).

[338] For purposes of this rule, do not count a bell-g, bell-G, bell-K, or bell-T as a bell-code.

[340] If there was more than one  between the <nobr> and the </nobr>, then (after the first occurrence) only execute the portion of step 5 that translates  into a dash.

[341] Do not count as a blank space any blank that is within a pair of angle brackets (e.g., ).

[342] For purposes of this rule, do not count a bell-g, bell-G, bell-K, or bell-T as a bell-code.

[344] Do not count as a blank space any blank that is within a pair of angle brackets (e.g., ).

[345] For purposes of this rule, do not count a bell-g, bell-G, bell-K, or bell-T as a bell-code.

[347] If there was more than one  between the <nobr> and the </nobr>, then (after the first occurrence) only execute the portion of step 5 that translates  into a dash.

[348] An example of typeface 2 can be found at 28 U.S.C. app. (Fed. R. Civ. P.) form 1B.

[349] An example of typeface 2 can be found at 28 U.S.C. § 2254 note (Rules Governing Section 2254 Cases in the United States District Courts, Appendix of Forms, Petition, § 11(e)).

[350] An example of typeface 2 can be found at 28 U.S.C. § 453.

[352] One-eighth, solid box, up arrow/single bond, and sigma.

[353] Three-eighths, open paren, single bond/up arrow, and integral sign.

[354] Five-eighths, close paren, single bond/down arrow, and contour integral.

[355] Seven-eighths, cancelled open paren, down arrow/single bond, and single bond.

[356] One-sixteenth, close paren, and double bond.

[357] Three-sixteenths, open bracket, and single bond.

[358] Nine-sixteenths, close bracket, vertical double bond, and gamma.

[361] An example of typeface 4 can be found at 23 U.S.C. § 127(a).

[362] An example of typeface 4 can be found at 23 U.S.C. § 127(a).

[363] Nine-thirty-seconds, shaded box, right arrow over bond, and open brace.

[364] An example of typeface 4 can be found at 28 U.S.C. app. (Fed. R. App. P.) form 1.

[365] Zero, because, and open square paren (less than).

[366] One, Bodoni H dash, horizontal double bond, and close square paren (greater than).

[367] Two, large shaded box, horizontal triple bond, and radical.

[368] Seven-sixty-fourths, bold backward shill, left diagonal double bond, and single bond.

[369] Nine-sixty-fourths, bell, and double bond.

[371] An example of typeface 4 can be found at 28 U.S.C. app. (Fed. R. App. P.) form 2.

[372] An example of typeface 2 can be found at 22 U.S.C. § 127(a).

[373] One-quarter, approaches a limit, and close square paren.

[375] Seven-eighths, horizontal bond, and open paren. An example of typeface 3 can be found at 45 U.S.C. § 351(i)(2)(B)(i)(II).

[376] Two-fifths and open square paren (less than).

[377] Three-fifths, pound, and close square paren (greater than).

[380] Check mark, differential, and vertical bond.

[382] Do not count as a blank space any blank that is within a pair of angle brackets (e.g., ).

[383] For purposes of this rule, do not count a bell-g, bell-G, bell-K, or bell-T as a bell-code.

[385] Do not count as a blank space any blank that is within a pair of angle brackets (e.g., ).

[386] For purposes of this rule, do not count a bell-g, bell-G, bell-K, or bell-T as a bell-code.

[388] If there was more than one  between the <nobr> and the </nobr>, then (after the first occurrence) only execute the portion of step 5 that translates  into a dash.

[389] Do not count as a blank space any blank that is within a pair of angle brackets (e.g., ).

[390] For purposes of this rule, do not count a bell-g, bell-G, bell-K, or bell-T as a bell-code.

[392] Do not count as a blank space any blank that is within a pair of angle brackets (e.g., ).

[393] For purposes of this rule, do not count a bell-g, bell-G, bell-K, or bell-T as a bell-code.

[395] If there was more than one  between the <nobr> and the </nobr>, then (after the first occurrence) only execute the portion of step 5 that translates  into a dash.

[398] Do not count as a blank space any blank that is within a pair of angle brackets (e.g., ).

[399] For purposes of this rule, do not count a bell-g, bell-G, bell-K, or bell-T as a bell-code.

[401] Do not count as a blank space any blank that is within a pair of angle brackets (e.g., ).

[402] For purposes of this rule, do not count a bell-g, bell-G, bell-K, or bell-T as a bell-code.

[407] If the current data is within a c-code table, then the material in c-code instructions D(9)(C)(g) and D(10)(g)(2) is the “Follow text with” material.

[408] If the current data is within a c-code table, then the material in c-code instructions D(9)(C)(g) and D(10)(g)(2) is the “Follow text with” material.

[409] If the current data is within a c-code table, then the material in c-code instructions D(9)(C)(g) and D(10)(g)(2) is the “Follow text with” material.

[410] If the current data is within a c-code table, then the material in c-code instructions D(9)(C)(g) and D(10)(g)(2) is the “Follow text with” material.

[411] Determined by the most recent F-code or S-code.

[412] Determined by the most recent c-code or e-code.

[413] The value of {leading} is also adjusted by bell-c, bell-q, bell-Q, and bell-R.

[414] An example can be found at 21 U.S.C. § 1703(c)(3)(D)(ii)(II)(bb)(ccc).

[415] For instance, if {subsection}₀= b, {subsection}₄= 7, and all other values of {subsection} are blank, then {long subsection} would be: (b)(7)

[416] An example can be found at 16 U.S.C. § 3703(e)(3)(A).

[417] The variable {subsection primary indent} is used in step 5C.

[418] This value is set by step 5B(l) and locator-80 (formats 5800 to 5803) (special processing instruction 12).

[419] An example can be found at 26 U.S.C. § 1252(a)(3).

[420] This value is set by step 5B(l) and locator-80 (formats 5800 to 5803) (special processing instruction 12).

[421] An example can be found at 23 U.S.C. § 127(a).

[422] For instance, if {subsection}₀= b, {subsection}₄= 7, and all other values of {subsection} are blank, then {long subsection} would be: (b)(7)

[423] The variable {subsection primary indent} is used in step 5C.

[424] The exception to this rule is if the bell is part of a bell-g, bell-G, bell-K, or bell-T. In any of those cases continue to the next bell, until you reach one that is neither a bell-g, bell-G, bell-K, nor bell-T. Once that processing has been completed, go back to bell-g, bell-G, bell-K, or bell-T that was bypassed, and process them.

[425] The value of {subsection anchor} is set by bell-F, bell-I80 (formats 5800 to 5803), and bell-I instructions 5B(c), 5C(b), and 5D(f).

[430] Locator-17 in format 5804 should be identical with this locator.21

[435] Section Referred to in Other Sections note heading.

[440] A locator-89 always follows a locator-80.

[442] Text of Section Referred to in Other Sections note.

[445] Executive Order and Presidential Proclamation note heading.

[447] A locator-89 always follows a locator-80.

[451] Do not, however, include any HTML coding from g-codes, G-codes, K-codes, and T-codes in {HIERARCHICAL INFORMATION}₁.

[452] Do not, however, include any HTML coding from g-codes, G-codes, K-codes, or T-codes, in {Act}.

[453] This should be the same as locator-20 in format 5800.

[454] The locator-90 is used to call one-column graphics files.

[455] Locator-94 is used to call two-column graphics files.

[462] Do not, however, include any HTML coding from g-codes, G-codes, K-codes, or T-codes in {HIERARCHICAL INFORMATION}₁.

[463] Do not, however, include any HTML coding from g-codes, G-codes, K-codes, or T-codes in {Act}.

[464] Do not, however, include any HTML coding from g-codes, G-codes, K-codes, or T-codes in {Act}.

[468] Do not, however, include any HTML coding from g-codes, G-codes, K-codes, or T-codes in {HIERARCHICAL INFORMATION}₁.

[469] Do not, however, include any HTML coding from g-codes, G-codes, K-codes, or T-codes in {TITLE}.

[473] Do not, however, include any HTML coding from g-codes, G-codes, K-codes, or T-codes in {HIERARCHICAL INFORMATION}₁.

[474] Do not, however, include any HTML coding from g-codes, G-codes, K-codes, or T-codes in {year}.

[475] Do not, however, include any HTML coding from g-codes, G-codes, K-codes, or T-codes in {month}.

[476] Do not, however, include any HTML coding from g-codes, G-codes, K-codes, or T-codes in {day}.

[477] Do not, however, include any HTML coding from g-codes, G-codes, K-codes, or T-codes in {Stat section}.

[481] Do not, however, include any HTML coding from g-codes, G-codes, K-codes, or T-codes in {HIERARCHICAL INFORMATION}₁.

[485] The exception to this rule is if the bell is part of a bell-G, bell-K, or bell-T. In any of those cases continue to the next bell, until you reach one that is neither a bell-G, bell-K, nor bell-T. Once that processing has been completed, go back to bell-G, bell-K, or bell-T that was bypassed, and process them.

[495] An example can be found at 4 U.S.C. § 1 note (Ex. Ord. No. 10834, § 33).

[496] The value of {leading} is also adjusted by bell-c, bell-I, bell-Q, and bell-R.

[497] An example can be found at 23 U.S.C. § 127(a).

[498] The value of {leading} is also adjusted by bell-c, bell-I, bell-q, and bell-R.

[499] The value of {leading} is also adjusted by bell-c, bell-I, bell-q, and bell-Q.

[500] For purposes of this rule, do not count a bell-g, bell-G, bell-K, or bell-T as a bell-code. Include a bell-code’s argument as part of the bell-code (e.g., bell-R10 would be a bell code).

[501] An example can be found at 46 U.S.C. subtitle I (prec. § 2101).

[502] Some occurrences of {short subdivision designation} may not have a “<!--”, e.g., 26 U.S.C. app. (T.C.R.) app. I.

[503] {Format} numbers can also be set by the bell-F.

[504] An example of this code can be found at 26 USC § 451 note (Pub. L. 97-248, § 229(c)(2)(B)).

[505] An example of this situation can be found at 5 U.S.C. § 5332 note (sched. 1).

[506] Do not examine characters that are part of the argument of a bell code.

[509] Though it is not currently used in the U.S. Code, the Government Printing Office’s Publishing From a Full Text Data Base, GPO publication 200.4, 2^nd edition, February 1983, pages 47-48, describes the processing needed when the FOTP value is “SC”.

[510] “{$DOC}” represents where the PLS software will insert the text of the retrieved section.

[511] If the primary indent is less the secondary indent, the first column should consist of one blank (i.e.,  ) and have a width determined by the following formula:

120 + ((ems in primary indent) * (pixels per em for the current point size)).

[512] If the formula yields a negative number, use zero.

[515] In Internet Explorer 4.0 and Netscape Communicator 4.5, the align=“justify” argument has not been implemented for the <td> tag, but has been implemented for the <div> tag.

[516] To be consistent with § 4.1 of the XHTML 1.0 (recommended) specification, http://www.w3.org/TR/xhtml1/#diffs, all of the occurrences of “</font>” in this table should be replaced with “</br></font>”.

[517] Publishing from a Full Text Data Base. U.S. Government Printing Office, Graphic Systems Development Division. September 1982. Page 140.

Special Characters

ESC sequences

D. Boxhead processing

E. Horizontal Rule Processing [109]

F. Standard Reading/Stub Column Processing

G. Long table testing and processing

H. New column processing

Bell-G and Bell-T

Processing Unidentified Characters

Formats 5800 to 5803

FOTP Processing [509]

SOURCE

%I74 (formats 5800 to 5803)

5 U.S.C. § 5332 note (sched. 1 to 4) [page 2 of 2]