old-www/LDP/solrhe/Securing-Optimizing-Linux-R.../preface2.html

203 lines
4.0 KiB
HTML

<HTML
><HEAD
><TITLE
>Why fiddle?</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.60"><LINK
REL="HOME"
TITLE="Securing and Optimizing Linux"
HREF="index.html"><LINK
REL="UP"
TITLE="Preface"
HREF="preface.html"><LINK
REL="PREVIOUS"
TITLE="Why did i write this book?"
HREF="preface1.html"><LINK
REL="NEXT"
TITLE="DocBook ! "
HREF="preface3.html"></HEAD
><BODY
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>Securing and Optimizing Linux: RedHat Edition -A Hands on Guide</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="preface1.html"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Preface</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="preface3.html"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="section"
><H1
CLASS="section"
><A
NAME="AEN71"
>2. Why fiddle?</A
></H1
><FONT
COLOR="RED"
>Madhu "Maddy"</FONT
><BLOCKQUOTE
CLASS="ABSTRACT"
><DIV
CLASS="abstract"
><A
NAME="AEN78"
></A
><P
></P
><P
>Is there a need to fiddle with what apparently is perfectly working and is serving the need. Well for one the i have choosen a format, <SPAN
CLASS="acronym"
>XML</SPAN
>, unlike the original manuscript which was written in word,
in this case has the advantage of source being one and output can be in various format. That is if the source is in <SPAN
CLASS="acronym"
>XML</SPAN
>, it is easier now to convert into <SPAN
CLASS="acronym"
>HTML, PDF, RTF</SPAN
> <SPAN
CLASS="abbrev"
>etc.</SPAN
> Also to
prove to the sceptics that DocBook is very much suitable for large production quality projects, not that this is the first effort, in this case an entire book has been marked up in <SPAN
CLASS="acronym"
>XML</SPAN
>.
</P
><P
></P
></DIV
></BLOCKQUOTE
><P
>Infact why <SPAN
CLASS="acronym"
>XML</SPAN
> indeed? <SPAN
CLASS="acronym"
>XML</SPAN
> -eXtensible Markup Language has been able to do justice to a large extent to the hype. Maybe having a watch body like w3.org to monitor
has been advantageous; unlike HTML which lacked a formal monitoring, ability to extend, a weak structure and no support for validation, <SPAN
CLASS="acronym"
>XML</SPAN
> has all these and more. It is a system-independant, vendor-independant and
has behind it the proven experience of SGML implementation, XML being a subset of SGML. I concur with Tim Bray's reported comment that it is ridiculous to use an application like MS Word, Quark Express <SPAN
CLASS="abbrev"
>etc.</SPAN
>for writing text which will be stored as a binary
and proprietory format therby bloating it considerably. And unlike <SPAN
CLASS="acronym"
>HTML</SPAN
> which has about <SPAN
CLASS="abbrev"
>aprox.</SPAN
> 50-60 pre-cooked tags, with <SPAN
CLASS="acronym"
>XML</SPAN
> one can make up one's own. Infact this facility of having one's own
tag will make it very, very useful in the long run. And the inherent factor that <SPAN
CLASS="acronym"
>XML</SPAN
> is all about content and nothing to do with presentation will be its greatest strength for years to come. The presentation part is taken care of by
Stylesheet or FO or some such thing.
</P
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="preface1.html"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="preface3.html"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Why did i write this book?</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="preface.html"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>DocBook !</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>