HTML Generator

The eaDocX HTML Generator lets you create a single HTML file from an eaDocX Word document.

Note: there is a feature in MS Word to ‘save as HTML’, but this creates a LARGE file, will a lot of content which is not relevant to most documents.

Creating an HTML document

1. To create an HTML document, you must first create a normal eaDocX Word document. This lets you choose exactly what will appear in your document, and format it the way you want.
2. Once you have done this, you can then generate that document into an HTML file
   1. Note that this re-generates a document from the latest EA content – this is not a ‘save as’ from the current state of the eaDocX document.
3. From the main eaDocX menu, choose Generate / HTML
4. If you have not used this before, you be asked for a location where you want to save the output. Choose any drive and folder
5. eaDocX will then generate a new folder, with the same name as your eaDocX document, which contains:
   1. One HTML file, containing all of the contents of your eaDocX document
   2. Some image files, which are referenced by the HTML
   3. A single CSS (Cascading Style Sheet) file which contains all the formatting details (fonts, colors etc) from your Word document
6. If the folder already exists, it will be overwritten, without warning.
7. You should see a success message, and the document will open in your default web browser.

Known Restrictions

Because we are taking a Word document, which can have a lot of formatting complexity, and saving into HTML, which is more limited in what it can show, your HTML document may look different from your Word document.

Differences we know about :

1. In a relationship matrix report, Word shows the top row as vertical text – HTML can’t show this, so matrix reports don’t look as neat
2. The colors and fonts of Word paragraph styles may not map into the HTML file.
3. If you generate a number of HTML files from the same model, there will not be hyperlinks which connect those documents.
4. If your eaDocX document contains a glossary section, it will not appear in the the HTML document