Skip to content

Changes

Page history
Mostly inline formatting authored by Wendell Piez's avatar Wendell Piez
Show whitespace changes
Inline Side-by-side
home.md
View page @ c37b5d6d
......@@ -2,19 +2,19 @@
See page on the original [Pre-alpha Specs](pre-alpha-specs) (before redesign)
**HTMLevator** supports structural induction and "section type inferencing" in conversion of data from (appropriately coded) `.docx` files into HTML. It is designed to be used with XSweet.
HTMLevator supports structural induction and "section type inferencing" in conversion of data from (appropriately coded) `.docx` files into HTML. It is designed to be used with XSweet.
*Structural induction* means HTMLevator will produce `<section>` elements where needed to "wrap" (structure) unorganized contents. *Section type inferencing* means recognizing, for example, a "Conclusions" section (by means of its title and/or other properties) and submitting it to appropriate handling -- including validation, to detect whether and where such a section is permitted).
**HTMLevator** relies on **XSweet** (a companion project) via its Header Promotion pathway to produce HTML h1-h6 in HTML extracted from Word `docx` files wherever Paragraph Styles are assigned named "Header 1" through "Header 6".
HTMLevator relies on XSweet (a companion project) via its Header Promotion pathway to produce HTML h1-h6 in HTML extracted from Word `docx` files wherever Paragraph Styles are assigned named "Header 1" through "Header 6".
Within Word, by default these styles are bound to the appropriate Outline level - hence, the structure of the HTML file produced by **HTMLevator** can be displayed directly in Word -- *before the conversion is run* -- by using the Outline View. Likewise, preparation of any Word file for **HTMLevator(( requires only assuring that Header 1 - Header 6 styles are assigned correctly to section titles at their respective levels of hierarchy.
Prepare Word file for HTMLevator requires by assigning Header 1 - Header 6 styles to your section titles at their respective levels of hierarchy. Within Word (since by default these styles are bound to the appropriate Outline level), this nominal structure can ordinarily be displayed in the Outline View (even before XSweet/HTMLevator are run).
**XSweet** and **HTMLevator** do the rest - **XSweet** makes HTML with h1-h6, then **HTMLevator** makes nested sections for the detected headers -- and goes from there.
Given these Paragraph Style assignments, XSweet and HTMLevator do the rest - XSweet makes HTML with h1-h6, then HTMLevator makes nested sections for the detected headers. (And goes from there to do things with these sections if/as necessary).
**HTMLevator** can also be used on files with no such preparation but YMMV - its efficacy depends entirely on whether/how **XSweet** header promotion works to detect h1-h6 on your file.
HTMLevator can also be used on files with no such preparation but YMMV - its efficacy depends entirely on whether/how XSweet header promotion works to detect h1-h6 on your file.
**HTMLevator** has two parts:
More details:
## Structural induction
......