Acls History E-book Project
view my citations
view search history
XML Tagging
Specifications
ACLS History E-Book Project - XML Tagging Specifications
(last update: 05-13-03)

PLEASE NOTE: this set of specifications is dated, and should be used for reference purposes only. A current set can be found at: http://www.historyebook.org/xml/doc/acls-hebook-doc.html


The following specifications include detailed instructions on preparing files for the ACLS History E-Book Project. Publishers should provide these specifications to their conversion or composition vendors. ACLS can also provide a list of experienced vendors.

Files and Resources
DTD: acls-hebook.dtd
XML Template
Encoding, Special Characters, and Styling
Tagging Text
   Text Structure
      Front, Body, Back
      Divisions
      Text Chunks
      Heads
   Front Matter
      Title Page
      Copyright and Permissions
      Table of Contents
      List of Illustrations
      Dedication, Acknowledgments, etc.
   General Elements
      Paragraphs
      Page Breaks
      Links: Notes, Page Breaks, URLs
      Extracts: Quotations, Epigraphs
      Figures
      Tables
      Lists
   Back Matter
      Notes
      Bibliography
      Index
Proofing and Quality Control
List of Elements and Attribute Chart
Cover Image
ACLS Specifications - Log of Specifications Updates
Technical Contacts at ACLS
Files and Resources

DTD:     acls-hebook.dtd     ver. 1.03; date: 07-09-03   (view | download zipped file)
Character Entities:     xhtml-lat1.ent    (view | download zipped file)
XML Template:     acls-hebook-template.xml    (view | download zipped file)

Specifications (this web page):  http://www.historyebook.org/xml/doc/acls-hebook-doc.html

DTD: acls-hebook.dtd

All books must be tagged in XML using the acls-hebook.dtd (see above). A list of all elements and attributes are defined below.

The dtd and specifications are periodically updated, so always check for the latest versions before beginning a new book.

XML Template

For examples on tagging and usage, refer to the XML template,
acls-hebook-template.xml (see above).

Encoding, Special Characters, and Styling

Encoding

Save files in US-ASCII encoding. Add the encoding type to the XML declaration:

<?xml version="1.0" encoding="us-ascii"?>

Special Characters

In order to ensure that our e-books are properly displayed across a range of standard web browsers, our system can currently only index and display the following characters:

Characters
allowed
Rendered
as
Notes
US-ASCII characters
(#0–#127)
  Only characters in the US-ASCII range are allowed.
ISO 8859-1 Latin-1
entities (#160–#255)
  Characters above US-ASCII must be encoded with entities (e.g., é for é) from xhtml-lat1.ent (see Resources and Files above).
& &
. . .
Make sure spacing and punctuation around … is correct, following book or publisher's in-house style. &hellips; will display as: [ . . . ] i.e. [space.space.space.space]
< > < >
“ ” " Curly double quotes will be converted to straight double quotes.
‘ ’ ' '
Curly single quotes and apostrophes will be converted to straight single quotes.
-
Ndash will be converted to hyphen.

If your book includes special or foreign characters outside this range, please add additional entities at the top of your XML file. Refer to this list of entity names. Example of added entity at top of an XML file:

<!ENTITY oelig "œ"> <!-- LATIN SMALL LIGATURE OE -->
We will need to work with the publisher and our programmers on how to index (for searching) and render the additional characters. Note that this should not affect the way you tag or prepare your text for print or other electronic versions. We just want to make it clear that our system can currently handle the entities listed above, and any additional characters will need to be dealt with as needed.

Styling

To tag italic or bold type, use <hi1> tag with rend attribute value italic or bold.

<hi1 rend="italic">text</hi1>
<hi1 rend="bold">text</hi1>

Small caps cannot be easily rendered in HTML browsers, so you must set small cap text in ALL caps, or convert text to title case. Publisher should advise conversion vendor on how to handle small caps.

When converting titles from the print version, hyphens inserted to break a word at the end of a line as well as forced end of line breaks must be removed. For example, if "demo-" is on one line and "cracy" on the next, the hyphen should be removed so the word reads "democracy" with no hyphen.

[ back to top]

Tagging Text

Text Structure

Front, Body, Back

Break down the text using <front>, <body>, and <back> tags. Add mandatory HEB Number and ISBN (E-Book) attributes to <text> tag.

<text id="heb90`xxx" isbn="x-xxxx-xxxx-x">
  <front>Title Page, Copyright, Dedication, etc.</front>
  <body>Introduction, Chapter 1, Chapter 2, etc., Conclusion</body>
  <back>Appendices, Notes, Bibliography, Index, etc.</back>
</text>

Divisions

Use division tags (<div1>, <div2>, <div3>) to subdivide text within <front>, <body>, and <back>.; For example, text with chapters and sections can be broken down as follows:

<div1 type="chapter" id="c01">
  <div2 type="section" id="c01.1">
OR
<div1 type="part" id="pt1">
  <div2 type="chapter" id="c01">
    <div3 type="section" id="c01.1">

Every division must have a type and id attribute, and include a <head> tag.

Note that division tags can be used for any type of text subdivision, not necessarily just the traditional chapter and section. For many "born-digital" works or new projects that are developed simultaneously with print editions, the publisher may choose to break down text in other ways (e.g., smaller units).

Text Chunks

E-books in our system will be delivered in text chunks by division level. The publisher can select the division level which will be delivered. For example:

1. If a book is broken down by chapter in <div1> and section in <div2>, the publisher can select to deliver the text by section by adding the attribute status="hidden" to the <div1> tag.

<div1 type="chapter" id="c01" status="hidden">
  <div2 type="section" id="c01.1">

2. For books without clear section breaks, you can break the chapter into smaller chunks (e.g., by tagging every 10 paragraphs in a separate division).

<div1 type="chapter" id="c01" status="hidden">
  <div2 type="section" id="c01.1">Text for paragraphs 1-10.</div2>
  <div2 type="section" id="c01.2">Text for paragraphs 11-20.</div2>
</div1>

Milestone breaks

If you want to add a separation between a series of paragraphs with a simple skipped line space or asterisks, you can put a milestone tag between paragraphs.

<p></p>
<milestone type="skipline"/> (for a blank line)
or
<milestone type="asterisk"/> (for asterisks)
<p></p>

Heads

Every division must include a <head> tag. Subparts of heads should be broken down by type in <bibl> tags. Paragraph number ranges for text chunks must also be placed inside a <bibl> tag.

It is only necessary to add paragraph-number ranges for the division level at which text chunks will be delivered, not for higher-level divisions that include the status="hidden" attribute (i.e., if text in e-book will be delivered by section, only add paragraph-number ranges to section heads, not part or chapter heads).

See example:

<div1 type="chapter" id="c01" status="hidden">
<head>
  <bibl type="number">Chapter 1</bibl>
  <bibl type="title">Chapter Title</bibl>
  <bibl type="subtitle">Chapter Subtitle</bibl>
</head>
<div2 type="section" id="c01.1">
<head>
  <bibl type="title">Section Title</bibl>
  <bibl type="para">22-39</bibl>
</head>

Heads and paragraph-number ranges [e.g., para 1-10] will appear in a hyperlinked Table of Contents. For new e-books in development, the publisher must make sure that all divisions have heads. In print version books, some sections do not have heads (e.g., first section at the beginning of a chapter, dedication page, etc.). Publishers should inform their vendors of the text to be inserted, for example, [Dedication], [Intro] or [No head in print version].

[ back to top]

Front Matter

Title Page

Begin tagging the <front> section with <titlepage> information. Do not tag the blank and half-title pages.

<front>
  <titlepage>
  <doctitle>
    <titlepart type="main">Title of work</titlepart>
    <titlepart type="subtitle">Subtitle of work</titlepart>
  </doctitle>
  <docauthor>Author's Name</docauthor>
  <docimprint>
    <publisher>Press/Publisher</publisher>
    <pubplace>Publisher's location</pubplace>
  </docimprint>
  </titlepage>
  <div1>Front matter</div1>
  <div1>Front matter</div1>
  <div1>Front matter</div1>
</front>

Copyright and Permissions

Continue tagging all other front matter material in <div1> sections. Create a section with copyright and permissions information.

Include:
1. Head - Since each division needs a head, you must the add the head "Copyright and Permissions" to this section.
2. Copyright and Permissions - Include all copyright and permissions information.
3. ISBN and HEB Number - Include the ISBN for this electronic version and the HEB Number.
4. Version Information - Publisher may choose to include information about other versions of the text, such as the print version, as well as information about variations among the versions (e.g., print edition includes 40 images and this electronic edition contains 150 images; print edition ISBNs and dates).

Do NOT include:
1. CIP - It is not necessary to include the Cataloging-in-Publication information because each of our electronic books is cataloged in full by a professional librarian.
2. Print version information - Do not include any information that pertains specifically to the print version, such as paper type, reprint number, etc.

Note that you can place information in any order you choose. Sample Copyright and Permissions below:

<div1 type="copyright" id="cpy">
<head><bibl type="title">Copyright and Permissions</bibl></head>
  <p>Press</p>
  <p>Location</p>
  <p>© (date and copyright holder)</p>
  <p>Permissions Information. Any other text from copyright page not pertaining exclusively to print version.</p>
  <p>ISBN: x-xxxx-xxxx-x (E-Book)</p>
  <p>HEB Number: HEB90xxx</p>
  <p>Version information.</p>
</div1>

Table of Contents

The Table of Contents does not need to be tagged because a TOC will be generated and linked dynamically from the heads within each division.

List of Illustrations

A List of Illustrations is NOT generated dynamically, so you must tag this in a <div1> section. The list is not generated dynamically so you can have flexibility in what you include in the list (use shorter description, omit source information, add thumbnails, etc.). To create a basic List of Illustration with links to the page within the text on which the figure appears, tag as follows:

<div1>
<list>
  <head><bibl type="title">List of Illustrations</bibl></head>
  <item>Figure 1. Caption for figure. [Page <ptr type="txt" target="pb10" n="10"/>]</item>
  <item>Figure 2. Caption for figure. [Page <ptr type="txt" target="pb22" n="22"/>]</item>
</list>
</div1>

If the figures are not interspersed in the book text, but rather displayed as a separate section (plates), you do not need to create the List of Illustrations. You can simply create a separate <div1> that contains all the figures (see Figures section below).

Dedication, Acknowledgments, etc.

Tag other front-matter text in separate <div1> sections within the <front> section. For example:

<div1 type="dedication" id="ded">

<div1 type="acknowledgments" id="ack">

<div1 type="epigraph" id="epi">

<div1 type="frontispiece" id="fnt">

[ back to top]

General Elements

Paragraphs

Use <p> to tag paragraphs. Add a rend="no-indent" attribute to paragraphs in the text that are rendered without indents.

Paragraphs in the text should also be assigned unique number and id values. In the e-book, the paragraph number (n value) will appear in the left margin next to the paragraph and will be used for identification and citation. Number each paragraph sequentially, beginning with the first paragraph of Acknowledgments (or the first significant front-matter text chunk) and continue numbering throughout the main text. You can also continue numbering through the back matter if it contains paragraphs in sections such as Appendices or About the Author. Do NOT number <p> tags that used just for styling and are not part of book text, such as the <p> tags used in the copyright page. Also, do NOT number paragraphs within extracts, such as epigraphs or quotations.

<p n="40" id="p40" rend="no-indent"></p>
<p n="41" id="p41"></p>
<p n="42" id="p42">
  <q1>
  <p></p>
  </q1>
</p>

Paragraphs will be rendered with justified margins and a text block width of 530 pixels.

Page Breaks

For titles that are also published in print, tag print-version page breaks with <pb> tags. Tagging page breaks gives readers a way to find citations based on the print-version pages. Note that page breaks must be placed within the main text, not in or above head tags.

<div1 type="chapter" id="c01" status="hidden">
  <head><bibl type="title"<Chapter Title</bibl></head>
  <div2 type="section" id="c01.1">
  <head><bibl type="title">Section Title</bibl></head>
  <p n="25" id="p25"><pb n="16" id="pb16"/>Paragraph text.</p>
  </div2>
Page breaks within text should follow this format:
Begining of sentence[space]<pb n="121" id="pb121">rest of sentence.

Links: Notes, Page Breaks, URLs

Our system currently features three types of links.

1. Link to note pop-up window
To tag a note number that will link to a note pop-up window, use the empty <ptr> tag, and add the note-reference number in an n attribute and the note id in a target attribute. Our system will take the n attribute value and put brackets around the number and hyperlink it to a pop-up window that will contain the text of the targeted note.
<ptr n="1" target="c01.n1"/>
<ptr n="10" target="c01.n10"/>

Note: Do not style note-reference numbers as superscript. See section on Notes below for more information about tagging the text of a note.

2. Link to a page break in text
To tag a link to a specific page number in the text, use the empty <ptr> tag, and add "txt" to a type attribute, the page number in an n attribute, and the page break id in a target attribute. Our system will take the n attribute value and hyperlink it to the targeted page break in the text.
<ptr type="txt" target="pb10" n="10"/>
3. Link to external URL
To link to external URLs, use <ref> tags.
<ref type="url" url="http://www.url.com" id="url10">http://www.url.com</ref>

Other types of links, such as linking to paragraphs, figures, etc., will be available in the future.

Extracts: Quotations, Epigraphs

Use <q1> tags to tag extracts formatted as block quotations within a paragraph. Paragraphs within <q1> tags should NOT be numbered.

<p n="20" id="p20">Paragraph text.
  <q1>
  <p>Text of extract.</p>
  </q1>
Continuation of paragraph text.
</p>

If quote is formatted in lines (e.g., verse), use <l> or <lg> with <l>:
<q1>
<lg>
<l>First line.</l>
<l>Second line.</l>
<l>Third line.</l>
</lg>
</q1>

To tag epigraphs, place <epigraph> around the <q1> tag and add <bibl type="epi"> to tag epigraph author and source.

<epigraph>
  <q1>
  <p>Text of epigraph.</p>
  </q1>
  <bibl type="epi">Quotation author, <hi1 rend="italic">Title of quotation source</hi1></bibl>
</epigraph>

Figures

Images will appear in the text where a figure tag is inserted. Users will be able to click on an image to open a pop-up window showing a larger version of the image, either as a large JPEG or within an image viewer. For each title, publishers can select one of two ways for users to enlarge an image:

1. Simple pop-up: Pop-up window brings up a larger version of the image. Recommended for most images.

2. Image viewer: Pop-up window that shows an image viewer that allows users to zoom in and pan on images. Recommended for titles with high-resolution art images or detailed line drawings or maps.

Image Specs:

1. Small JPEG Files for In-line Images
Small JPEG files appear within the text, either embedded in paragraph text or as a series of images in a separate section.
Format/Resolution: JPEG, 72 dpi; image quality: medium or high
Size: 350–530 pixels on the long side, depending on what is needed for clarity
File name: heb9xxxx.0001.jpg

2. Large JPEG Files for Simple Pop-up
Large JPEG files appear in a pop-up window when users click on the small JPEGs images within a book.
Format/Resolution: JPEG, 72 dpi; image quality: high
Size: 600–750 pixels on the long side, depending on what is needed for clarity
File name: heb9xxxx.0001.jpg

3. High Resolution Tiff files
High resolution tiff files will be used to create files for the image viewer tool. Publishers can submit the high resolution files used for print production. If high resolution tiff files are not readily available or difficult to create, please discuss the situation with a technical contact at ACLS.
Format/Resolution: TIFF, 300–600 dpi (depending on image type); image quality: high
Size: Variable
File name: heb9xxxx.0001.tif

Note: Make sure you rotate all image 90 degrees to correct orientation if necessary.

Tip: A quick way to convert image files in one batch is using Adobe Photoshop's Web Photo Gallery feature. First re-name your image files using the figure entity name (heb9xxxx.0001). From the File menu, select Automate, Web Photo Gallery. Select location of original files and destination of converted files. Select Large Images from Options pull-down, click on Re-size Images, select Custom in pull-down, and enter 650 pixels (or higher); then select Contrain: Both, and Quality: High. Next, from the Options pull-down, select Thumbnails, then Size: Custom, 300 pixels (or higher). A web site with converted images will be created. You can then submit these converted images.

Tagging Figures in XML

Place figure entity declarations at the top of the XML file:

<!ENTITY heb9xxxx.0001 SYSTEM "heb9xxxx.0001.jpg" NDATA jpeg>>

Tag figures within the text as follows. All figure tags must be placed within <p> tags. Break down caption information by figure number, caption, and source/permissions.

<p>[text text text]
<figure entity="heb90xxx.0001">
<head>
<bibl type="figno">Figure 1.</bibl>
<bibl type="figcap">Caption for figure.</bibl>
<bibl type="figsrc">Source info/permission for figure.</bibl>
</head>
</figure>
[text text text]
</p>

If figures appear in a separate section (plates), then just tag a <div1> section and tag each figure in a <p> tag

Tables

Use <table> tags for actual tables, or for text formatted as table. Do not repeat column or row header cells if table spans several pages (as they are in print version in such cases).

<table>
  <head><bibl type="title">Table Head (optional)</bibl></head>
  <row>
  <cell></cell>
  <cell></cell>
  </row>
</table>

Lists

Use <list> tag for lists. You can also nest lists within list items. Items in a list will be formatted with a hanging indent.

<list>
  <head><bibl type="title">List Head (optional)</bibl></head>
  <item></item>
  <item></item>
</list>

[ back to top]

Back Matter

Notes

In <back> section, create a <div1> with type="notes". Place notes for each chapter in separate <div2> . Each note id should follow this format: "[xxx].n[notenumber]" where xxx is [int] or [c01], [c02], etc.

<div1 type="notes" id="nts">
<head>...
 <div2 type="notes" id="nts.int">
  <note1 n="1" id="int.n1">
  <p>Text of note.</p>
  </note1>
    . . .
  <note1 n="10" id="int.n10">
  <p>Text of note.</p>
  </note1>
 </div2>
</div1>

Handling "Ibid." in Notes

Since end notes will appear as pop-up windows, for notes that include the word "Ibid." users will not see the referenced note in the pop-up window. You must replace the word "Ibid." with the referenced text, commenting out "Ibid." and commenting where inserted text begins and ends. Note that often it's not such a clear-cut copy and paste replacement, because the referenced note can include lengthy text or multiple books. The question the publisher will need to work out is which portion of the previous note should replace the "Ibid."

<note1 n="10" id="c01.10"> <p>Jones and Smith, <hi1 rend="italic">History of the United States</hi1>, Chapters 1 and 2.</p></note1>
<note1 n="11" id="c01.11"> <p><!--Ibid.--><!--begin insert-->Jones and Smith, <hi1 rend="italic">History of the United States</hi1>, Chapters 1 and 2. <!--end insert--></p></note1>

Publishers may want to consider ending the usage of terms such as "Ibid." and "Op. cit." in their house style, so that notes can be more efficiently processed in the electronic version.

Bibliography

Within <back> section, create a <div1> section with type="bibliography". If there are multiple sections in the bibliography, create subsections using <div2>, etc. All <bibl> tags should be sequentially id'd. Remove 3-em dashes for repeated author names and repeat name.

<div1 type="bibliography" id="bib">
<head><bibl type="title">Bibliography</bibl></head>
  <bibl id="bib1"> ... </bibl>
  <bibl id="bib2"> ... </bibl>
</div>

Index

To tag an index, create a <div1> section with type="index" and put each letter into a separate <list>. Terms with subnested items can be placed within another list within an item tag.

To link a page number to a specific page in the text, use the empty <ptr> tag, and add "txt" in a type attribute, the page number in an n attribute, and the page break id in a target attribute. Our system will take the n attribute value, put brackets around the number and hyperlink it to the targeted page break in the text. For page ranges (e.g., "30-35"), only the first page should be tagged.

<div1 type="index" id="ind">
<head><bibl type="title">Index</bibl></head>
 <list>
  <item>Apples, <ptr type="txt" target="pb1" n="1"/>, <ptr type="txt" target="pb15" n="15"/>-17</item>
  <item>Apricots, <ptr type="txt" target="pb133" n="133"/></item>
 </list>
 <list>
  <item>Bananas, 34<ptr type="txt" target="pb1" n="1"/></item>
  <item></item>
 </list>
</div1>

[ back to top]

Proofing and Quality Control

XML files must be quality checked and proofread before submission to ACLS History E-Book Project. We will soon provide a proofing XSL to help view XML in a format closer to the final on-line version.



List of Elements

The following list shows all the elements defined for the ACLS History E-Book Project acls-hebook.dtd. This list is an edited subset of the elements in the TEI Lite XML dtd.

<back>
contains any appendices, notes, bibliography, index, etc., following the main part of a text.

<bibl>
contains either a.) a sub-component of a heading or b.) a loosely-structured bibliographic citation of which the sub-components may or may not be explicitly tagged.

<body>
contains the whole body of a single unitary text, excluding any front or back matter.

<byline>
at the beginning of a section, contains the primary statement of responsibility given for the work to follow (e.g., foreword).

<cell>
contains one cell of a table.

<div1> ... <div4>
contains a first, second, third, fourth level subdivision of the front, body, or back of a text.

<docauthor>
contains the name of the author of the document, as given on the title page.

<docimprint>
contains the imprint statement (<publisher> name, place of publication <pubplace>), as given (usually) at the foot of a title page.

<doctitle>
contains the title of a document, including all its constituents, as given on a title page. Must be divided into <titlepart> elements.

<epigraph>
contains a quotation, anonymous or attributed, appearing at the start of a section or chapter, or on a title page.

<figure>
marks the spot at which a graphic is to be inserted in a document. Attributes may be used to indicate an entity containing the image itself (in some non-XML notation); <head> within the <figure> element may be used to transcribe captions.

<front>
used to designate any prefatory matter before the start of the text proper.

<head>
contains any heading, for example the title of a section, or the heading of a list or glossary (sub-components should be tagged individually with <bibl> tags).

<hi1>
used to tag text as either italicized (<hi1 rend="italic">) or bold (<hi1 rend="bold">).

<item>
contains one component of a list.

<l>
contains a single, possibly incomplete, line of verse.

<lg>
contains a group of verse lines functioning as a formal unit, e.g., a stanza, refrain, verse paragraph, etc.

<list>
contains any sequence of items organized as a list, whether of numbered, bulletted, or other type.

<milestone>
marks a boundary between two sections of a text that does NOT constitute the start of a new division-based section. Attributes are skipline and asterisk.

<note1>
contains a note or annotation.

<p>
marks paragraphs in prose. (Attribute no-indent permissible.)

<pb>
marks the boundary between one page of a text and the next in a standard reference system.

<ptr>
a pointer (reference) to another location in the current document in terms of one or more identifiable elements.

<publisher>
provides the name of the organization responsible for the publication or distribution of a bibliographic item.

<pubplace>
contains the name of the place where a bibliographic item was published.

<q1>
contains a quotation or apparent quotation.

<ref>
a reference to another location in the current document, in terms of one or more identifiable elements, possibly modified by additional text or comment.

<row>
contains one row of a table.

<salute>
contains a salutation or greeting prefixed to a foreword, dedicatory epistle, or other division of a text, or the salutation in the closing of a letter, preface, etc.

<signed>
contains the closing salutation, etc., appended to a foreword, dedicatory epistle, or other division of a text.

<table>
contains text displayed in tabular form, in rows and columns.

<text>
the entire body of the book.

<titlepage>
contains the title page of a text, appearing within the front matter.

<titlepart>
contains a subsection or division of the title of a work, as indicated on a title page; also used for free-floating fragments of the title page not part of the document title, authorship attribution, etc.

Attribute Chart

Tag type n id target rend miscellaneous
bibl
(div head)
number
title
subtitle
para
bibl
(figure head)
figno
figcap
figsrc
bibl
(references)
bib1
bib100
div1 part
chapter
(etc.)
pt1
c01
(cpy, pre, int ...)
status="hidden"
div2 chapter
section
(etc.)
c01
c01.1
(int.1, nts.c01 ...)
(status="hidden")
div3 section
(etc.)
c01.1 (bib.1.1)
figure entity="..."
hi1 italic
bold
milestone skipline
asterisk
note1 1
10
pre.n1
c01.n10
p 1
10
p1
p10
no-indent
pb 1
10
pb1
pb10
ptr
(note reference)
1
10
c01.n1
c01.n10
ptr
(to page break:
used in fig list,
index)
txt 1
10
pb1
pb10
ref url url="http://www...."
titlepart main
sub


Cover Image

You must submit two JPEG files for the cover image, which will appear on the Title Record Page of each book.

Small cover image: width: 160 pixels; format: JPEG, 72 dpi; image quality: medium or high.
Large cover image for pop-up window: height: 650 pixels; format: JPEG, 72 dpi; image quality: high.
File name, small image: heb9xxxx.0001.001.jpg
File name, large image: heb9xxxx.0001.001-lg.jpg

Technical Contacts at ACLS

Nancy Lin (nlin@acls.org) or Nina Gielen (ngielen@acls.org)

ACLS Specifications - Log of Specifications Updates

HEB19.02
Last modified 05-13-03.

05-13-03 Updates:
1. Epigraph source - bibl tag in epigraph source should include attribute type="epi"<bibl type="epi">
2. All images must be submitted with high resolution tiffs. Small edits to image specs for clarity.
3. Index tagging - Removed specs to tag links to note id in index.

02-20-03 Updates:
1. Figures - Clarify image size specs. Small images, maximum size 530.
2. Small text copyedits.

[ back to top]


© 2003 The ACLS History E-Book Project
Technical Contacts: nlin@acls.org and ngielen@acls.org