From: Jorge Godoy <godoy@conectiva.com>
To: Ismael Olea <olea@hispalinux.es>
Cc: "Edward C. Bailey" <ed@redhat.com>,
docbook-tools-discuss@sourceware.cygnus.com,
Camille Bégnis <camille@mandrakesoft.com>
Subject: Re: Request for Redhat-Centric info (For Ed Bailey)
Date: Fri, 07 Jul 2000 10:36:00 -0000 [thread overview]
Message-ID: <m3zontx2id.fsf@dagon.conectiva> (raw)
Message-ID: <20000707103600.dl83dQS_UzBDhYOuhs4iHuLFoVuq1uzTc54Ao6TbvAo@z> (raw)
In-Reply-To: <39661206.64E4B78B@hispalinux.es>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1360 bytes --]
Ismael Olea <olea@hispalinux.es> writes:
> At HispaFuentes we use too. But jadetex limitations avoid us to print
> using it.
>
> > But we are using free tools to generate printed books and guides.
>
> Other than jadetex?
Nope. We're using Jadetex.
I've been annoying Sebastian* a lot with that :-))
I've found few undesirable behaviours of it and these were the ones
that I was talking to Camille. I can remember of:
- Titles being orphans at the end of page
- Some problems with figure numbering at the LoF (List of Figures)
- Some problems with hyphenization (although we defined them correctly
at the Jadetex's config file, some words aren't hyphenated correctly
even thought they work in LaTeX...)
- Keeping the figure title with the image (we managed that by placing
the title below the image. Statistically I've found that our
problems occurred when the title was above the image. This solved the
problem, since if a wrap occurs, both -- image and title -- go to
next page)
There are a few minor problems, but I can't remember of them now... I
must look at my checklist. :-)
What limitations did you find that forbid you from using Jadetex to
print?
* Sebastian Rahtz, the Jadetex maintainer.
Regards,
--
Godoy. <godoy@conectiva.com>
Departamento de Publicações
Publishing Department Conectiva S.A.
next prev parent reply other threads:[~2000-07-07 10: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
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 [this message]
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=m3zontx2id.fsf@dagon.conectiva \
--to=godoy@conectiva.com \
--cc=camille@mandrakesoft.com \
--cc=docbook-tools-discuss@sourceware.cygnus.com \
--cc=ed@redhat.com \
--cc=olea@hispalinux.es \
/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).