From: Andy Wingo <wingo@pobox.com>
To: Gavin Smith <gavinsmith0123@gmail.com>
Cc: Bryan Ferris <saffronsnail@hushmail.com>,
25293-done@debbugs.gnu.org, Texinfo <bug-texinfo@gnu.org>
Subject: bug#25293: More descriptive page titles in documentation?
Date: Wed, 01 Mar 2017 21:55:25 +0100 [thread overview]
Message-ID: <8760jsd8ea.fsf__31754.3767662302$1488401779$gmane$org@pobox.com> (raw)
In-Reply-To: <CAKPWYQ1GcxJ2OvQuUEVjT9+X-Y+f00HXvvm22b=w4OBnwURwRA@mail.gmail.com> (Gavin Smith's message of "Wed, 1 Mar 2017 18:40:25 +0000")
On Wed 01 Mar 2017 19:40, Gavin Smith <gavinsmith0123@gmail.com> writes:
> On 1 March 2017 at 14:49, Andy Wingo <wingo@pobox.com> wrote:
>> Hello Texinfo peoples,
>>
>> We have a suggestion that Guile's HTML manual, e.g.
>>
>> https://www.gnu.org/software/guile/docs/master/guile.html/Procedures-as-Values.html#Procedures-as-Values
>>
>> should have the <title> be defined like:
>>
>> Procedures as Values: Guile Reference Manual
>>
>> instead of
>>
>> Guile Reference Manual: Procedures as Values
>>
>> Any thoughts on if this is possible and if so, how to get it working?
>
> I don't know if you can do it easily with any released version of
> Texinfo, but I changed the order on the suggestion of Bryan Ferris on
> 2017-01-21 in the development code. I believe it is now "Procedures as
> Values (Guile Reference Manual)" and will be output this way in the
> next release, if nothing changes before then.
That's great to hear :-) We'll pick up this change when the next
release comes out.
Happy hacking,
Andy
prev parent reply other threads:[~2017-03-01 20:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-29 18:43 bug#25293: More descriptive page titles in documentation? saffronsnail
2017-01-09 21:56 ` Andy Wingo
2017-03-01 14:49 ` Andy Wingo
[not found] ` <87mvd5f3wk.fsf@pobox.com>
2017-03-01 18:40 ` Gavin Smith
[not found] ` <CAKPWYQ1GcxJ2OvQuUEVjT9+X-Y+f00HXvvm22b=w4OBnwURwRA@mail.gmail.com>
2017-03-01 20:55 ` Andy Wingo [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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='8760jsd8ea.fsf__31754.3767662302$1488401779$gmane$org@pobox.com' \
--to=wingo@pobox.com \
--cc=25293-done@debbugs.gnu.org \
--cc=bug-texinfo@gnu.org \
--cc=gavinsmith0123@gmail.com \
--cc=saffronsnail@hushmail.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).