public inbox for docbook-tools-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Gregory Leblanc <GLeblanc@cu-portland.edu>
To: docbook-tools-discuss@sourceware.cygnus.com
Subject: Linking collections (was: RE: I'm trying to set up docbook-tools...)
Date: Wed, 27 Dec 2000 06:36:00 -0000	[thread overview]
Message-ID: <A5F46F4ED18FD211ABEE00105AC6CF07010938DB@email.cu-portland.edu> (raw)

> -----Original Message-----
> From: Norman Walsh [ mailto:ndw@nwalsh.com ]
> Sent: Friday, July 07, 2000 6:59 AM
> To: docbook-tools-discuss@sourceware.cygnus.com
> Subject: Re: I'm trying to set up docbook-tools...
> 
> |   More details on linking documents, I've got 6 docs that 
> I'm writing in
> | parallel and would really like to link between them. I gave up.
> 
> These are six separate documents, or six parts of the same document?
> SGML doesn't really have a good cross-document linking 
> solution (though
> you can cobble one together, see my tutorials about olink on 
> nwalsh.com).
> XPointer and XLink should do better, but there are still some problems
> given that you don't typically publish the source.

From looking under Documents, DocBook, and XML, I don't see this on your
site.  I'll keep poking around, a bit more and holler with a URL if I find
it, but I'd appreciate a pointer if you read this before I find it.  There
really needs to be a good way to link between separate documents for a lot
of things.  That's one of the biggest problems that the LDP has right now.
It's very hard to reference other documents because all you can do is say
"read document named X", and not do a very good job linking to that
document, or even better, to a specific section of that document.  Thanks,
	Grego

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

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-27  6:36 Gregory Leblanc [this message]
2000-12-27  6:36 ` Linking collections (was: RE: I'm trying to set up docbook-tools. ..) Norman Walsh
2000-07-10  7:03   ` Norman Walsh

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=A5F46F4ED18FD211ABEE00105AC6CF07010938DB@email.cu-portland.edu \
    --to=gleblanc@cu-portland.edu \
    --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).