From: "wcohen at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug documentation/11077] URLs in the HTML documentation are not meaningful
Date: Tue, 15 Dec 2009 21:45:00 -0000 [thread overview]
Message-ID: <20091215214518.11784.qmail@sourceware.org> (raw)
In-Reply-To: <20091210160213.11077.dmalcolm@redhat.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1100 bytes --]
------- Additional Comments From wcohen at redhat dot com 2009-12-15 21:45 -------
This is being generated by latex2html from a latex file in doc/langref.tex
According to the man page for latex2html has the following option:
-long_titles <num>
Same as setting: $LONG_TITLES = <num>; Instead of the standard
names: node1.html, node2.html,... the filenames for each HTML
page are constructed from the first <num> words of the section
heading for that page, separated by the _ character. Commas
and common short words (a an to by of and for the) are omitted
from both title and word-count. Warning: Use this switch with
great caution. Currently there are no checks for uniqueness of
names or overall length. Very long names can easily result from
using this feature.
--
http://sourceware.org/bugzilla/show_bug.cgi?id=11077
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next prev parent reply other threads:[~2009-12-15 21:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-10 16:02 [Bug documentation/11077] New: " dmalcolm at redhat dot com
2009-12-15 21:45 ` wcohen at redhat dot com [this message]
2009-12-17 20:20 ` [Bug documentation/11077] " wcohen at redhat dot com
2009-12-17 20:30 ` dmalcolm at redhat dot com
[not found] <bug-11077-6586@http.sourceware.org/bugzilla/>
2013-07-12 22:23 ` fche at redhat dot com
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=20091215214518.11784.qmail@sourceware.org \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@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).