public inbox for docbook-tools-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Jorge Godoy <godoy@conectiva.com>
To: "Edward C. Bailey" <ed@redhat.com>
Cc: docbook-tools-discuss@sourceware.cygnus.com,
	Camille Bégnis <camille@mandrakesoft.com>
Subject: Re: Request for Redhat-Centric info (For Ed Bailey)
Date: Wed, 27 Dec 2000 06:36:00 -0000	[thread overview]
Message-ID: <m3puopyiq9.fsf@dagon.conectiva> (raw)
In-Reply-To: <lfbt09hoq1.fsf@pigdog.meridian.redhat.com>

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

"Edward C. Bailey" <ed@redhat.com> writes:

> docbook-3.1-4
> jade-1.2.1-9
> jadetex-2.7-2
> psgml-1.0.3-2
> sgml-common-0.1-8
> stylesheets-1.54.13rh-1
> 
> (I've included psgml here just to let people know that, if you want to use
> Emacs and psgml-mode, I've had problems using the above RPMs with psgml
> versions > 1.0.3, in that it cannot read the pre-parsed DTD it saved.)
> 
> I'll also state that we use these tools to produce "give-to-customer"
> quality HTML, and "copy-editing" quality Postscript.  For final-quality
> print, we use Arbortext's Adept*Publisher software.  So if you do a db2ps
> and wonder why your output doesn't look like our manuals, now you'll know
> why... :-)

We're using the same packages at Conectiva.
But we are using free tools to generate printed books and guides. 

Our last four books were written in DocBook and formatted with Jade
and a customized version of Norm's stylesheets (1.53 and 1.54). There
was another book but the tool we used wasn't completely free. 

For HTML I'm also using CSS.

I think that these tools are mature to have final-quality
documents. But I agree that there are a few things needed here. 

Camille, from Mandrake, might also have something to say... She was
having some common problems and we were talking in private to find a
way of solving them.


Regards,
-- 
Godoy.	<godoy@conectiva.com> 

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

  reply	other threads:[~2000-12-27  6:36 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-27  6:36 txporter
2000-12-27  6:36 ` Edward C. Bailey
2000-12-27  6:36   ` Jorge Godoy [this message]
2000-12-27  6:36     ` Eric Lee Green
2000-12-27  6:36       ` Jorge Godoy
2000-12-27  6:36     ` Ismael Olea
2000-12-27  6:36       ` Jorge Godoy
2000-07-07 10:36         ` Jorge Godoy
2000-12-27  6:36   ` Chuck Mead
2000-12-27  6:36     ` Request for Redhat-Centric info (For Ed Bailey) [NEVERMIND] Chuck Mead
2000-12-27  6:36       ` Edward C. Bailey
2000-12-27  6:36     ` Request for Redhat-Centric info (For Ed Bailey) Edward C. Bailey
2000-12-27  6:36       ` David C. Mason

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=m3puopyiq9.fsf@dagon.conectiva \
    --to=godoy@conectiva.com \
    --cc=camille@mandrakesoft.com \
    --cc=docbook-tools-discuss@sourceware.cygnus.com \
    --cc=ed@redhat.com \
    /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).