public inbox for docbook-tools-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Jorge Godoy <godoy@conectiva.com>
To: Peter Toft <pto@sslug.dk>
Cc: Norman Walsh <ndw@nwalsh.com>,
	<docbook-tools-discuss@sourceware.cygnus.com>
Subject: Re: Where, what and how - The future of DocBook
Date: Tue, 05 Dec 2000 16:58:00 -0000	[thread overview]
Message-ID: <kpk89ejrex.fsf@dagon.conectiva> (raw)
Message-ID: <20001205165800.8iYjQ1_7-AReIPKSGLQwbk_KPrfgEk2an6kwUKzZvN0@z> (raw)
In-Reply-To: <Pine.LNX.4.30.0012052258020.1160-100000@pto.sslug>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2971 bytes --]

On Tue, 5 Dec 2000, pto@sslug.dk wrote:

> Agree. Can we get MANY people to use the tools?

What tools? DocBook XML + DSSSL + DSSSL processing tools OR DocBook
XML + XSL Stylesheets + XSL/XML able tools? 

I'm using the first solution mixed with both SGML and XML versions of
DocBook. All of Conectiva's documents (we're beggining with technical
stuff) are migrating to DocBook. Our books and booklets are being
written in DocBook.


As a big documentation project, LDP is also using DocBook. We've
implemented it and already have several documents marked accordingly
to DocBook DTD. 

> How do we get the tools working?
> - Which tools should the ordinary person download?
> - How are they installed?
> - Where is the first "lets try it" - example
> - Where is the tutorials?
> - Where is the full documentation?
> - Can we get standard Linux/*BSD distributions
>   to carry the tools?
> 
> These the the *KEY* questions to answer in the best
> possible way. I am sorry to say that I find it hard to
> find it.

OK. Try taking a look at my mess: http://bazar.conectiva.com.br/~godoy 
If you install the packages available there, you can ignore the
'tetex' ones (but make sure that you have it installed and in a
relatively new version).

I'm trying to gather together information about several things as I
need them (or need to explain them to somebody). I'm sorry but there
are some things in Portuguese and others in English. 


For the "full" documentation, you can try http://docbook.org --- and
buy the O'Reilly book; it's very good!


Standard Linux distributions such as Conectiva, Mandrake, Red Hat,
Debian, SuSE already have packages for DocBook usage.


>> James Clark's SP.
> 
> URL - again, download?, install?, howto? + full docs.

I'd suggest using OpenSP. 

http://openjade.sourceforge.net

> Who is making what at the moment for DocBook?

Development on DocBook or DocBook usage?

> Eg. IMT-2000 standardization (UMTS) - check
> http://www.3gpp.org -> all the work is Word-files.
> 
> I care a lot. I find that Word is eating WAY to much of
> the areas, where DocBook could have been cool. I think
> Word is preferred for many companies today - many do
> not consider DocBook - that is a shame - we can all
> agree on that!

Speak to them about information recuperability and for how long they
can have this same information available. What if they need to recover
some client information or document of a product that was written 5
years ago. Is Word able to do that? 

I confess I don't use Word for several years now (5, IIRC). I was a
Word heavy user, then I switched to LaTeX and now I'm on DocBook SGML
/ XML. 

With LaTeX or DocBook I'm sure that my document will look the same on
every machine I'm working. With Word I wasn't. 


> We have to IMHO!

In some aspects, IMHO, we have already done. 



See you,
-- 
Godoy. <godoy@conectiva.com>

Departamento de Publicações       Conectiva S.A.
Publishing Department             Conectiva Inc.

  parent reply	other threads:[~2000-12-05 16:58 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-27  6:36 Peter Toft
2000-12-03  9:23 ` Peter Toft
2000-12-27  6:36 ` Norman Walsh
2000-12-04  6:08   ` Norman Walsh
2000-12-27  6:36   ` Peter Toft
2000-12-05 14:12     ` Peter Toft
2000-12-27  6:36     ` Alan W. Irwin
2000-12-05 15:53       ` Alan W. Irwin
2000-12-27  6:36       ` Michael Smith
2000-12-05 21:27         ` Michael Smith
2000-12-27  6:36         ` Eric Bischoff
2000-12-06  5:23           ` Eric Bischoff
2000-12-27  6:36         ` Alan W. Irwin
2000-12-05 22:50           ` Alan W. Irwin
2000-12-27  6:36           ` Michael Smith
2000-12-06  0:51             ` Michael Smith
2000-12-27  6:36           ` Gregory Leblanc
2000-12-06  9:39             ` Gregory Leblanc
2000-12-27  6:36     ` Jorge Godoy [this message]
2000-12-05 16:58       ` Jorge Godoy
2000-12-27  6:36       ` Eric Bischoff
2000-12-06  5:10         ` Eric Bischoff
2000-12-27  6:36         ` madhu
2000-12-15  9:22           ` madhu
2000-12-27  6:36           ` Michael Smith
2000-12-15 10:40             ` Michael Smith
2000-12-27  6:36         ` Michael Wiedmann
2000-12-06  5:36           ` Michael Wiedmann
2000-12-27  6:36           ` Eric Bischoff
2000-12-06  5:53             ` Eric Bischoff
2000-12-27  6:36             ` Mark Johnson
2000-12-06  8:05               ` Mark Johnson
2000-12-27  6:36               ` Eric Bischoff
2000-12-06  8:15                 ` Eric Bischoff
  -- strict thread matches above, loose matches on Subject: below --
2000-12-27  6:36 Pfaffner, Peter
2000-12-05  7:18 ` Pfaffner, Peter
2000-12-27  6:36 Peter Ring
2000-12-05  7:45 ` Peter Ring
2000-12-27  6:36 Peter Ring
2000-12-07  3:45 ` Peter Ring
     [not found] <200012061723.KAA06519@gw.estinc.com>
2000-12-27  6:36 ` Craig Boone
2000-12-06 11:06   ` Craig Boone
2000-12-27  6:36   ` Gregory Leblanc
2000-12-06 11:12     ` Gregory Leblanc
     [not found]   ` <200012061858.LAA06946@gw.estinc.com>
2000-12-27  6:36     ` Craig Boone
2000-12-06 11:46       ` Craig Boone
     [not found] <200012061914.UAA08546@mailserv.caiw.nl>
2000-12-27  6:36 ` Hugo.van.der.Kooij
2000-12-06 12:31   ` Hugo.van.der.Kooij

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=kpk89ejrex.fsf@dagon.conectiva \
    --to=godoy@conectiva.com \
    --cc=docbook-tools-discuss@sourceware.cygnus.com \
    --cc=ndw@nwalsh.com \
    --cc=pto@sslug.dk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).