This is the mail archive of the
docbook-apps@lists.oasis-open.org
mailing list .
RE: [Fwd: [Fwd: First Open Source Documentation Summit at the O'Reilly Open Source Convention]]
- To: 'Camille Bégnis' <camille at mandrakesoft dot com>
- Subject: RE: [Fwd: [Fwd: First Open Source Documentation Summit at the O'Reilly Open Source Convention]]
- From: Ekbert Mertens <ekbert dot mertens at ixos dot de>
- Date: Wed, 19 Jul 2000 13:48:52 +0200
- Cc: docbook-apps at lists dot oasis-open dot org
Regarding all those mails saying jadetex is not satisfying: Where is the
advantage of jadetex against jadertf? We are using jadertf (for print/pdf
versions); well, it is not that satisfying as I'd like, but since I started
with the SGML stuff two months ago, I found out that much more is possible
than it seemed to be (and than my predestor obviously knew).
In the beginning, I wondered whether we should switch to jadetex (I have no
experience with tex, yet), but hearing you (and the others) we should not,
should we?
Regards
Ekbert Mertens
> -----Original Message-----
> From: Camille Bégnis [mailto:camille@mandrakesoft.com]
> Sent: Mittwoch, 19. Juli 2000 10:42
> To: docbook-apps
> Cc: LDP; docbook-tools list
> Subject: [Fwd: [Fwd: First Open Source Documentation Summit at the
> O'Reilly Open Source Convention]]
>
>
> Hi all,
>
> While reading the article at the end of that message, I wish
> I had been
> there.
> Everyone seems to agree to use DocBook, very well. However, in the
> opinion of the author himself, the jadetex processing tool is
> not suited
> for professional books.
>
> I am personally not really happy with jadetex and some others too I
> know.
> Do the other people here use it?
> Are you happy with it?
> Do you use something else?
> Did you think in developing something else?
>
> I have unhopeful not the sufficient skills in TeX to initiate
> it myself,
> but we, at MandrakeSoft, are interested in participating in
> the project
> of developing a new solution. A completely rewritten "print"
> stylesheet,
> generating true LaTeX seems to be the solution.
>
> Camille.
>
>
> -------- Original Message --------
> From: Dan York <dyork@linuxcare.com>
> Subject: [Fwd: First Open Source Documentation Summit at the O'Reilly
> Open Source Convention]
> Resent-From: ldp-discuss@lists.debian.org
> To: ldp-discuss <ldp-discuss@lists.debian.org>
>
> FYI, this came in from O'Reilly... sounds like an interesting
> meeting...
>
> Regards,
> Dan
>
> -------- Original Message --------
> Subject: First Open Source Documentation Summit at the O'Reilly Open
> Source
> Convention
> Date: Mon, 17 Jul 2000 15:46:38 -0700 (PDT)
> From: Carmel Noah <cammie@oreilly.com>
> To: dan@lpi.org
>
> On Sunday, July 16, O'Reilly sponsored an all-day pre-conference
> meeting on improving the documentation that accompanies open source
> software. Participants at the Open Documentation Summit included
> representatives of open source documentation from the Linux
> Documentation Project, GNOME, KDE, FreeBSD, BSDI, SourceForge, Samba,
> OASIS, Los Alamos National Labs, Python, and Open Content.
>
> O'Reilly Editor-in-Chief Frank Willison reports on what came
> out of the
> meeting:
>
> http://www.oreilly.com/frank/oscon_summit.html
>