<?xml version="1.0" encoding="ISO-8859-1"?>
<sect1 id="intro-use-sect1">
 <sect1info>
  
  <!-- Please, do NOT edit the following revision history by hand. Use the
  "make <module_name>.revision" target instead.  -->
  
  <revhistory><revision><revnumber>0.8</revnumber><date>YYYY-MM-DD</date><authorinitials>tbn</authorinitials><revremark>write</revremark> </revision><revision><revnumber>0.8</revnumber><date>YYYY-MM-DD</date><authorinitials>tbn</authorinitials><revremark>translate</revremark> </revision><revision><revnumber>0.8</revnumber><date>YYYY-MM-DD</date><authorinitials>tbn</authorinitials><revremark>tproof</revremark> </revision><revision><revnumber>0.8</revnumber><date>YYYY-MM-DD</date><authorinitials>tbn</authorinitials><revremark>pproof</revremark> </revision><revision><revnumber>0.8</revnumber><date>YYYY-MM-DD</date><authorinitials>tbn</authorinitials><revremark>ispell</revremark> </revision><revision><revnumber>0.8</revnumber><date>YYYY-MM-DD</date><authorinitials>tbn</authorinitials><revremark>lproof</revremark> </revision>
      <revision>
        <revnumber>1.en.lproof</revnumber>
        <date>YYYY-MM-DD</date>
        <authorinitials>tbn</authorinitials>
      </revision>
      <revision>
        <revnumber>1.en.ispell</revnumber>
        <date>YYYY-MM-DD</date>
        <authorinitials>tbn</authorinitials>
      </revision>
      <revision>
        <revnumber>1.en.pproof</revnumber>
        <date>2002-07-22</date>
        <authorinitials>jp</authorinitials>
      </revision>
      <revision>
        <revnumber>1.en.tproof</revnumber>
        <date>YYYY-MM-DD</date>
        <authorinitials>tbn</authorinitials>
      </revision>
      <revision>
        <revnumber>1.en.write</revnumber>
        <date>2002-06-27</date>
        <authorinitials>jp</authorinitials>
      </revision>
    </revhistory>
 </sect1info>
 
 <title id="intro-use-sect1-ti1">Choosing Borges</title>
 <sect2>
  <title id="intro-use-sect1-ti2">Do I need it?</title>
  
  <abstract>
   <para id="intro-use-sect1-pa1">This section, instead of presenting features, addresses the
    needs that &prog-borges; answers.</para>
  </abstract>
  
  <formalpara>
   <title id="intro-use-sect1-ti3">Constant revision, Multiple languages</title> <para id="intro-use-sect1-pa2">If you
    manage or publish books that need frequent(constant) revision in
    multi-languages. &prog-borges; is for you. It will enable you to
    track changes at the paragraph or block of text level, maximizing
    translator's and proof reader's time.</para></formalpara>
  
  <formalpara>
   <title id="intro-use-sect1-ti4">Team Leaders</title> <para id="intro-use-sect1-pa3">If you manage a team of authors,
    even scattered around the net, through it's cvs integration, task,
    revision and languages management, &prog-borges; will considerably
    simplify your life.</para></formalpara>
  
  <formalpara>
   <title id="intro-use-sect1-ti5">Reusable Content</title> <para id="intro-use-sect1-pa4">If the content you are
    publishing is reusable, &prog-borges; is for you. For example, you
    write a travel guidebook for the USA and would like, from that
    same content, to publish books on each individual states without
    having to manipulate your document. You can also publish one book
    out of many.</para></formalpara>
  
  <formalpara>
   <title id="intro-use-sect1-ti6">Multiple Format Publishing</title> <para id="intro-use-sect1-pa5">In todays Internet
    world, the format you choose to publish your work is something
    very likely to change. Furthermore, in a <emphasis>Customer
    Relationship Management</emphasis> perspective, it becomes a great
    asset to deliver content in the format most suitable for your
    users. It may be a book, it may be a web site, it may be a
    downloadable &pdf;... &prog-borges;, through it's &xml; and
    DocBook foundation is specifically tailored to address these
    needs... You can define layout for all of those formats and really
    adopt a content provider approach.</para></formalpara>
 </sect2>
 
 <sect2>
  <title id="intro-use-sect1-ti7">Is Borges for me?</title>
  <para id="intro-use-sect1-pa6">Do not think about using &prog-borges; if you:
   <itemizedlist>
    <listitem>
     <para id="intro-use-sect1-pa7">seldom write documents more than 2 pages long;</para>
    </listitem>
    <listitem>
     <para id="intro-use-sect1-pa8">seldom have your documents translated;</para>
    </listitem>
    <listitem>
     <para id="intro-use-sect1-pa9">don't want to work under another operating system
      than Windows&trade;;</para>
    </listitem>
    <listitem>
     <para id="intro-use-sect1-pa10">get scared when seeing a text mode console;</para>
    </listitem>
   </itemizedlist>
   
   Do use &prog-borges; if you:
   <itemizedlist>
    <listitem>
     <para id="intro-use-sect1-pa11">happen to manage many big documents;</para>
    </listitem>
    <listitem>
     <para id="intro-use-sect1-pa12">have those documents translated in many languages;</para>
    </listitem>
    <listitem>
     <para id="intro-use-sect1-pa13">manage a team of many people involved in the production
      of these documents;</para>
    </listitem>
    <listitem>
     <para id="intro-use-sect1-pa14">regularly lose your hair because the documented items
      change everyday;</para>
    </listitem>
    <listitem>
     <para id="intro-use-sect1-pa15">can rely on someone at ease with &os-linux;;</para>
    </listitem>
    <listitem>
     <para id="intro-use-sect1-pa16">wish to bring your documentation project and team into
      new generation of technical documentation with &xml; and
      DocBook.</para>
    </listitem>
   </itemizedlist>
  </para>
  
  <para id="intro-use-sect1-pa17">In short, &prog-borges; will provide you a solution to
   efficiently manage big documentation projects, bringing higher
   quality and reducing delays. The counterpart will be some time to
   spend reading the documentation and getting used to the system. If
   necessary installing a &os-linux; system will also be needed. If
   you don't know DocBook, you'll have to learn it as well.</para>
  
  <para id="intro-use-sect1-pa18">Still interested in the beast?  Congratulations! read on, and
   good luck. You won't regret it!</para>
 </sect2>
</sect1>
<!-- Keep this comment at the end of the file
Local variables:
mode: xml
sgml-parent-document: ("../../manuals/Borges-doc/master.top.xml" "sect1")
End:
-->