Lists Home |
Date Index |
- From: Andy Dent <firstname.lastname@example.org>
- To: Paul Prescod <email@example.com>, firstname.lastname@example.org
- Date: Fri, 11 Sep 1998 13:03:28 +0800
At 23:01 +0800 10/9/98, Paul Prescod wrote:
>The browser takes XML, pumps it through an XSL engine, receives an XML
>result (according to a known DTD with formatting semantics) and renders
>*that*. You can do the same with your report writer.
I don't think anyone in any of the many messages I've read or the books
I've bought has explained the point of the XSL translation quite so
clearly. I *knew* there was a (stupidly obvious) step I was missing.
I think the thing that confused me is that the generated XML from the XSL
processor will inherently be marked up for rendering and no longer just
structured content, correct? (ie: glorified HTML).
I kept concentrating on XML as remaining free from rendering-oriented
content, so could not see how the gap was closed other than in the final
renderer, like our product.
Mind you, it still may be vastly easier and more efficient for us to skip
this intermediate step as an XML rendition and keep our intermediate
version purely in-memory as a set of c++ formatting objects, applied to a
Andy Dent, Software Designer, A.D. Software, Western Australia
OOFILE - Database, Reports, Graphs, GUI for c++ on Mac, Unix & Windows
PP2MFC - PowerPlant->MFC portability
xml-dev: A list for W3C XML Developers. To post, mailto:email@example.com
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:firstname.lastname@example.org the following message;
To subscribe to the digests, mailto:email@example.com the following message;
List coordinator, Henry Rzepa (mailto:firstname.lastname@example.org)