TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:Re: HTML & CSS From:Mark Baker <mbaker -at- OMNIMARK -dot- COM> Date:Mon, 7 Dec 1998 13:51:35 -0500
Sven-Ola Tuecke wrote
>mbaker -at- omnimark -dot- com (Mark Baker) wrote:
>>(c) Store your pages in XML or SGML and write a script to detect the
>>browser and output the appropriate CSS/HTML for each browser. This way
>>authors don't have to worry about browser differences and when a new
>>is released you only have to update your script to support the new
>>not edit any of your data. What a dream come true.
>Maybe your dream turns out to be a nightmare:
>If you read the IE5.0 specs, you detect a new
>style sheet language, the development team
>focuses on: XSL. XSL is not CSS or DSSSL. XSL
>is a fine idea, but it may be a new and strange
>concept for layout oriented DTPers...
This is exactly the situation in which the system I describe is most
advantageous. With a server-side program creating the final formatting code
on the fly, you can adapt to any browser innovation. If the browser wants
XSL, fine, your server-side program generates the appropriate XSL code.
Whatever new browser technology cones along, you just update your program to
serve it the encoding it expects.
The important concept here is future proofing. We have all gone through the
pain of version upgrades and software changes that made it difficult to use
older files. Now the acceptable delivery formats are so splintered and
changing so quickly that it is no longer tenable to create in any one final
delivery format. You need to future-proof you data by adopting a neutral
format and converting to presentation formats as needed. This includes
converting to the browser flavor of the month on the fly as people visit
Manager, Technical Communication
OmniMark Technologies Corporation
1400 Blair Place
Canada, K1J 9B8
Email mbaker -at- omnimark -dot- com