public inbox for docbook-tools-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Peter Toft <pto@sslug.dk>
To: Tim Waugh <twaugh@redhat.com>
Cc: Sebastian Rahtz <sebastian.rahtz@computing-services.oxford.ac.uk>,
	Norman Walsh <ndw@nwalsh.com>,
	<docbook-tools-discuss@sourceware.cygnus.com>
Subject: Re: <screen>-- </screen>
Date: Wed, 28 Feb 2001 14:27:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.30.0102282312090.4508-100000@pto.sslug> (raw)
In-Reply-To: <20010224235529.K13721@redhat.com>

On Sat, 24 Feb 2001, Tim Waugh wrote:

> On Sat, Feb 24, 2001 at 10:21:36PM +0100, Peter Toft wrote:
>
> > Then the "-" -> "&dash;" is the way to proceed - only
> > translated within <screen>-tags. Have to make a
> > Perl-hack for this :-)
>
> You'll also have to hack '>>', which suffers from a similar
> affliction.
>
> Surely the fix is to get better TeX output generated in the first
> place?

HELP - This sucks.

I did replace all my "--" entries with "&dash;&dash;"
in my SGML code, and the <screen>-sections look
terrible, since the &dash; is rendered with a font,
which is much wider than the mono-spaced font used in
the <screen>-section.

So

<screen>
drxw------ DIR
-rwxrwxrwx FILE
</screen>

Looks like

drxw------------ DIR  <---cannot show loooong dashes :-)
-rwxrwxrwx FILE

in the PDF - alignment is bad.

AND -rw-r&dash;&dash;r&dash;&dash;
is actually rendeded as
-rw-r----r----
Yes &dash;&dash; gives four dashes....

I have a problem, since I have a book to finish next
week and promised the publisher a PDF-file ready to
print.


 --
Peter Toft, Ph.D. [pto@sslug.dk] http://www.sslug.dk/~pto

Check you back - penguins approaching.....

  parent reply	other threads:[~2001-02-28 14:27 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-19 22:49 Peter Toft
2001-02-22 13:07 ` Peter Toft
2001-12-19 22:49 ` Wookey
2001-02-23  7:53   ` Wookey
2001-12-19 22:49 ` Norman Walsh
2001-02-23 12:59   ` Norman Walsh
2001-02-24  5:46   ` Sebastian Rahtz
2001-02-24 14:02     ` Peter Toft
2001-02-24 15:56       ` Tim Waugh
2001-02-25  8:02         ` Sebastian Rahtz
2001-02-28 14:27         ` Peter Toft [this message]
2001-03-01  1:19           ` Tim Waugh
2001-03-01  7:38           ` Sebastian Rahtz
2001-12-19 22:49   ` Peter Toft
2001-02-23 14:25     ` Peter Toft
2001-12-19 22:49 ` Tim Waugh
2001-02-22 14:07   ` Tim Waugh

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=Pine.LNX.4.30.0102282312090.4508-100000@pto.sslug \
    --to=pto@sslug.dk \
    --cc=docbook-tools-discuss@sourceware.cygnus.com \
    --cc=ndw@nwalsh.com \
    --cc=sebastian.rahtz@computing-services.oxford.ac.uk \
    --cc=twaugh@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).