From: Aaron Weber <aaron@ximian.com>
To: docbook-tools-discuss@sources.redhat.com
Subject: File Naming Change in 1.4?
Date: Thu, 24 Oct 2002 08:24:00 -0000 [thread overview]
Message-ID: <1035472323.12497.61.camel@localhost.localdomain> (raw)
Message-ID: <20021024082400.e3FLwfmJY8DGfITyS9d06t7Mb2UHXz3k9jBKo7HiPBQ@z> (raw)
[-- Attachment #1: Type: text/plain, Size: 453 bytes --]
After v. 1.4, has jw/docbook2html stopped producing html files named
after section id's?
kmarass and I are both getting things like "t1.html" rather than
"index.html."
Should we change the links to these filenames, or worry about making
them go back to the old names? (that is, are they always going to be the
same odd names? if they are, I can replace links to
"mailer-using-filters.html" with links to "x37290r.html" without too
much trouble...)
a.
[-- Attachment #2: Type: text/html, Size: 744 bytes --]
next reply other threads:[~2002-10-24 15:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-20 19:23 Aaron Weber [this message]
2002-10-24 8:24 ` Aaron Weber
2002-12-20 19:23 ` Wookey
2002-10-24 8:29 ` Wookey
2002-12-20 19:23 ` Tim Waugh
2002-10-24 9:24 ` 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=1035472323.12497.61.camel@localhost.localdomain \
--to=aaron@ximian.com \
--cc=docbook-tools-discuss@sources.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).