... | ... | @@ -34,6 +34,8 @@ HTML Typescript isn't one thing, because it is a transitional format. (So the sa |
|
|
|
|
|
* Structure will be "hidden" in presentational features. For example, margin shifts may indicate things like block quotes or excerpts.
|
|
|
|
|
|
* Similarly, we do not depend on an authors' having used any features of Word including named Styles, in a disciplined way. If they have, such usage is exposed (it is in fact much easier to see as CSS + .class bindings!) and a next-step process can exploit it. But if no Word Styles are ever assigned or Word template is used, or if Styles are used messily and inappropriately (which can often happen), nothing breaks.
|
|
|
|
|
|
* Most of the action happens in `class` and `style` attributes. In particular, `class` may be overloaded (more than one value may be assigned).
|
|
|
|
|
|
* Yet all this is flexible and these assignments (element name, `class` and `style) may be rewritten/refactored along a processing pipeline (aka INK service or recipe) -- so HTML Typescript data that is very 'raw' can (for example) be refined and "fitted" to the needs of a particular HTML client or environment (such as an editor).
|
... | ... | |