public inbox for docbook-tools-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Peter Toft <pto@sslug.dk>
To: <docbook-tools-discuss@sourceware.cygnus.com>
Subject: Re: db2pdf: cannot generate system identifier for public text...
Date: Fri, 19 Jan 2001 13:50:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.30.0101192239060.22836-100000@pto.sslug> (raw)
In-Reply-To: <Pine.LNX.4.21.0012271420550.16046-100000@nexus.intra.n-h.com>

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

Friends - One of the oldies but goodies :-)

I still struggle with the problem that doing
a PS og PDF output from my SGML DocBook source could
create lines, which a going longer than the right side
margin of the paper, e.g.

<para>
this line could if but then on the other hand you well
should look at <ulink url=" http://cvs.sslug.dk/linuxbog/httpsplit.pl ">this URL</ulink>
</para>

Depending on the about of "bla bla bla" in from of the
<ulink> the ulink-tag produces code, which lead to my
problem.

We have tried to cure the problem by invoking
http://cvs.sslug.dk/linuxbog/httpsplit.pl - the odd
usage of ComMand in there makes it simple to trace
where we have changes. The idea in the small Perl
program is really to replace

http://cvs.sslug.dk/linuxbog/httpsplit.pl
with
http://cvs.sslug.dk /linuxbog /httpsplit.pl

This is a good way - all the line breaks disappear :-)

BUT it could be even better if we - in some way - could
avoid the additional spaces and get a VERY small
space-like character where the line can be broken
without the output of the ordinary space.

Well - as I told you - it is my old irritating problem,
so if you have a better solution that our httpsplit.pl
please come forward.

Best regards to you all

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

"You don't win a battle by asking, `Will we win?'
You win it by doing your best to win" - Richard M Stallman

LinuxKonference i København: http://LinuxForum.dk/

      parent reply	other threads:[~2001-01-19 13:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-27  6:36 Chris Turchin
2000-12-27  5:30 ` Chris Turchin
2000-12-27  6:36 ` Norman Walsh
2001-01-19 13:50 ` Peter Toft [this message]

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.0101192239060.22836-100000@pto.sslug \
    --to=pto@sslug.dk \
    --cc=docbook-tools-discuss@sourceware.cygnus.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).