html-typescript.md

@@ -92,9 +92,7 @@ But this is no longer HTML Typescript. (It's something more like "HTML Galley Pr
 * Cross-references are emulated for footnotes and endnotes (as regular structures created as such in the Word document), but by and large, there will be no linking or cross-referencing implemented where they are warranted in the source. Where the source data has a string, we get a string and nothing more. (We expect robust linking mechanisms to come later when data is better structured and more regular.)
 * `class` overloading is okay. `class` is convenient for any semantic labeling. We will be more or less shameless in adding whatever values we think we need, to communicate downstream.
 * Similarly `style` and other *presentational* formatting is not only acceptable - for some applications it is preferred. Word has the feature that any arbitrary span or segment of text may be assigned its own properties for presentation. (And writers using Word do this a lot.)  This has a straightforward analogue in HTML `@style` attribute, which is (for ordinary every day purposes) deprecated or discouraged. It permits us to hang CSS to describe formatting basically wherever we like [example]
-
    In effect, CSS provides us the language to expose a range of features in our source data, in a way familiar to developers and readily processed using tools they already have. So if the Word says, "1inch left margin" we can turn that into "left margin: 72pt" or indeed "left-margin: 1in" in CSS.
-
     Indeed, the very reasons why @style and presentational tagging in general should be avoided in "good" markup -- because *at best*, they represent *work to be done*, while at worst they are misleading cruft -- these are the very same reasons why presentational tagging, `i`, `b` and all that species, are acceptable and indeed preferable as a representation (as 'transparent' as possible) of Word source data. Because that's what the Word data has, and we need to see exactly what is there prior to "casting" it into anything.
 
 The expectation of HTML Typescript is that we wish the thing to be a basis for improvement, not a finished thing in itself.