... | ... | @@ -2,7 +2,7 @@ |
|
|
|
|
|
Not a formal subset or profile of HTML or any other formally specified language, but an *approach* to using HTML and web pages.
|
|
|
|
|
|
HTML Typescript has nothing to do with Word documents or word processing documents - except that it is designed so that producing recognizable HTML Typescript documents is relatively *easy* and *straightforward* to produce reliably from Word OpenXML. So while there is no *formal* dependency, there is something of a practical one. Our first use for HTML Typescript is to make data available, which is now locked up in Word - so it has to work for that.
|
|
|
HTML Typescript has nothing to do with Word documents or word processing documents - except that it is designed so that producing recognizable HTML Typescript documents is relatively *easy* and *straightforward* to produce reliably from Word OpenXML. So while there is no formal dependency, there is something of a practical one. Our first use for HTML Typescript is to make data available, which is now locked up in Word - so it has to work for that.
|
|
|
|
|
|
Among other things, this means that insofar as as information available only from Word documents, is ambiguous and underspecified, an HTML Typescript version must mirror (exactly) that ambiguity and underspecification. It should tell us (albeit in HTML+CSS, a language we can understand) exactly what we could know from the Word (if we understood WordML) - and no more. It should not make logical leaps, inferences, or even do very much in the way of translation.
|
|
|
|
... | ... | |