Download your own copy of Doc To HTML Converter today!Prev Page Prev Page
Using DocToHtml
Getting Started
Conversion Options Dialog
Output Filenames
Template Data Editor
Meta Tags
Font Attr
Paragraph Attr
List Attr
Table Attr
Text Boxes
Body & Footer
Footnotes & Endnotes Options
HTML Template
XML & Charset & PG
Search & Replace
Progress Form
Batch Converter
Main Window
Settings Dialog
Command Line Support
Search & Replace Dialog
Installation Issues
Uninstallation Issues
Crash Recovery
Support for 64-Bit MS Word
Common Issues
Deep Troubleshooting
Registration Benefits
How to Buy
Support & Feedback
How to Speed up the Conversion
Unsupported Formatting
License Agreement
Privacy Policy
Change Log
Other Products

HTML Code Tab

HTML Code Tab of DocToHtml Converter Options Dialog

Indent each level of HTML code by N spaces—this option enables the indentation mode, in which HTML code of all block-level tags (for example, HEAD, BODY, STYLE, TABLE, THEAD, TBODY, TR, TD, UL, OL, and so on) is shifted by N spaces to the right for easy editing.

Indent also content within <P>, <LI> tags—this option enables one additional indentation level for HTML code inside those tags. If your document contains a lot of big paragraphs, it is recommended to use this mode. On the other hand, if your document consists of many small paragraphs and bulleted items, additional indentation may be annoying. Choose whatever better fits your needs.

Wrap HTML code at this margin—this option enables HTML wrapping mode for easy editing.

Do not replace double quotes with "&quot;" in HTML text—if this option is turned on, DocToHtml will not replace " with the &quot; code. This will reduce the resulting file size. By default, DocToHtml does this replacement because it is more safe to use the " character only for enclosing attribute values in tags. Otherwise, some poorly written script may be confused by the " character in HTML code.

Do not use LineFeed (LF, ASCII code 10) character—if this option is turned on, DocToHtml will not insert LineFeed characters at the end of each string in HTML code. Using this option reduces the resulting file size at the expense of HTML code readability.

Surround attributes with quotes only if necessary—turning this option on will make DocToHtml insert quotes to enclose tag attributes only when necessary. Stripping optional quotes will reduce the resulting file size, though you might want to turn this option off if you use certain software tools. In XHTML, all attribute values should be enclosed in quotes, so this option will be inactive if you have specified XHTML as the output format.

Do not use spaces in style definition—if this option is turned on, DocToHtml will not insert additional spaces in the style definition after the : or ; characters. If you disable this option, a style definition may looks like this: style="margin-right: 48pt; page-break-before: auto; ". Otherwise it may look like this: style="margin-right:48pt;page-break-before:auto; ". As you can see, enabling this option will reduce the resulting file size at the expense of HTML code readability.

Tag names in uppercase instead of lowercase—by default, the program uses lowercase tag names. Turning this option on will change that behavior. Actually, it is a matter of taste, HTML-wise. But in XHTML, all tags should be in lowercase, so this option will be inactive if you have specified XHTML as the output format.

Escape characters in stylesheet names—if this option is turned on, DocToHtml will replace any character in the stylesheet name whose Unicode code is greater than 161 with a 6-digit hexadecimal code preceded with a backslash. Escaping such characters ensures that any CSS identifier will fully conform to the CSS2 standard. However, it can reduce the readability of the HTML code and increase the resulting file size. Some browsers can handle non-escaped characters in CSS identifiers just fine. So it’s up to you to decide whether to use such escaping or not.

Convert multiple continuous spaces to just one space—by default, the program changes every second continuous space character into a non-breaking space (the &nbsp; entity). This behavior is aimed at retaining the same visual horizontal distance between objects separated by a sequence of spaces in the resulting HTML document as it was in the original MS Word document. So, for example, a sequence of six continuous spaces will be transformed into the code “ &nbsp; &nbsp; &nbsp; ”. If you want to represent such sequences as one space, just enable this option.

Convert tab characters to just one space—by default, DocToHtml converts every Tab character (ASCII code 9) into a sequence of non-breaking spaces (&nbsp; entities). This was done to make the text occupy approximately the same horizontal space in the resulting HTML document as in the original MS Word document with tab characters. But if you do not want such sequences of non-breaking spaces to appear in the resulting HTML code, just check this checkbox.

Preserve Tabs horizontal distance—if this option is turned on, the program will insert a certain number of &nbsp; entities into the output document, depending on the actual width of the respective Tab character in the input document. Due to some untraceable reason, using this mode causes memory leaks, so enable it only when absolutely necessary. This option also cannot be used together with the “Convert tab characters to just one space” option.

Represent characters outside of the ASCII range as numeric entities—if turned on, this option forces DocToHtml to use numeric entities instead of character codes in the output HTML code for all characters whose code is greater than 127. For example, the numeric entity &#39; will be used in place of the ' character (apostrophe), the numeric entity &#8217; in place of the right single quotation mark, and so on. Moreover, all letter codes of non-English characters that do not fit into the ASCII character set will also be represented as numeric entities. Use this mode only if you have problems with direct processing of character codes greater than 127. (Some applications that work with HTML may have such problems.) By default, this option is turned off, since it may significantly increase the resulting file size.

Comment out content of <STYLE>, <SCRIPT> tags—use this mode if your content must be compatible with very old browsers. Checking this option will cause DocToHtml to enclose any included CSS declarations and JavaScript code in the HTML comment marks (<!-- -->).

Additional check for special chars—turning this option off will slightly speed up the conversion process. However, it might cause incorrect transformation of some characters, especially ones in the “Symbol” font. To the right of the checkbox, you can see the Font text input field, where you can enter the name of a font that must be enclosed in the <FONT> tags. Apparently, MS Word and web browsers use different algorithms for substituting font names if a character with the specified code does not exist in the font required. As a result, if you use some special characters selected via the Insert>Symbol>More... dialog but do not specify the “Symbol” font name, they will be rendered fine in MS Word, but web browsers will display blank black rectangles in their place. This option was added to prevent this annoyance. If you do not want to enclose each special character in a font name specification, just leave this field empty.