From: Neil Jerram <neil@ossau.uklinux.net>
To: Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
Cc: bug-guile@gnu.org
Subject: Re: Typos in the manual
Date: Sun, 13 Feb 2011 22:29:58 +0000 [thread overview]
Message-ID: <877hd3wot5.fsf@ossau.uklinux.net> (raw)
In-Reply-To: <20110213070044.GA26711@gmx.de> (Ralf Wildenhues's message of "Sun, 13 Feb 2011 08:00:44 +0100")
Ralf Wildenhues <Ralf.Wildenhues@gmx.de> writes:
> Hi Neil,
Hi Ralf,
I pushed some more changes based on your input. Below has just a few
specific notes.
> * Neil Jerram wrote on Sun, Feb 13, 2011 at 01:49:43AM CET:
>>
>> Will @var always generate appropriate markup for making it clear that
>> GUILE_EFFECTIVE_VERSION isn't meant literally? I think that is what the
>> < and > intend to indicate.
>
> Well, @var is the intended way to denote metasyntactic variables.
> In info output, it capitalizes, in PDF output it uses a different font
> (or small caps IIRC). See 'info texinfo var'. It might sometimes be
> a bit hard to always read them correctly in info output. I'm not sure
> how info could be improved though.
Yes, I'm convinced now and so have applied this.
>> Why is \sqrt2 better than \sqrt{2} ?
>
> No idea, that was pure consistency at work: you already use \sqrt2
> elsewhere. Doesn't matter really.
I went for \sqrt{2} everywhere - I think that avoids anyone (who doesn't
immediately know the fine detail of TeX's lexer) wondering whether \sqrt2
might be a special TeX token.
>> > - In the Autoconf section, several macros are added to the function
>> > index. They come from doc/ref/autoconf{,-macros}.texi (one being
>> > generated from meta/guile.m4. The macros are:
>> > PKG_CHECK_MODULES
>> > GUILE_PROGS
>> > GUILE_FLAGS
>> > GUILE_SITE_DIR
>> > GUILE_CHECK_RETVAL
>> > GUILE_MODULE_CHECK
>> > GUILE_MODULE_AVAILABLE
>> > GUILE_MODULE_REQUIRED
>> > GUILE_MODULE_EXPORTS
>> > GUILE_MODULE_REQUIRED_EXPORT
>> >
>> > The simplest way to fix this
>>
>> Fix what?
>>
>> > would be to adjust indices.texi to
>> > document that Autoconf macros and variables are also listed in this
>> > index. Karl tells me that one should have less indices anyway for the
>> > autotools manuals (ideally just one), so this would seem like a step
>> > in the right direction.
>>
>> Sorry, I'm not following here at all.
>
> Well. If you look at the Procedure Index of the manual, you will find
> entries for the above Autoconf macros in there. The Procedure Index has
> the following intro text:
>
> This is an alphabetical list of all the procedures and macros in Guile.
>
> When looking for a particular procedure, please look under its Scheme
> name as well as under its C name. The C name can be constructed from
> the Scheme names by a simple transformation described in the section
> *Note API Overview::.
>
> In other words, no mention of "Autoconf macros", and I wouldn't expect
> to find them there, among all the Scheme and C symbols. Now, you can
> either fix the text to match the contents, or change the extractor to
> not emit @deffn's for the Autoconf macro in doc/ref/autoconf-macros.texi
> so that they don't end being listed in the Procedure Index.
>
> Is that clearer now?
Yes, thanks; done as you and Karl recommend.
Neil
next prev parent reply other threads:[~2011-02-13 22:29 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-08 20:25 Typos in the manual Ralf Wildenhues
2011-02-13 0:49 ` Neil Jerram
2011-02-13 7:00 ` Ralf Wildenhues
2011-02-13 22:29 ` Neil Jerram [this message]
2011-02-15 15:48 ` Marijn
2011-02-15 20:21 ` Mark Harig
2011-02-15 23:55 ` Neil Jerram
2011-02-16 0:52 ` Mark Harig
2011-02-16 22:37 ` Neil Jerram
2011-02-15 23:49 ` Neil Jerram
2011-02-15 20:48 ` Mark Harig
2011-02-15 21:14 ` Ralf Wildenhues
2011-02-15 22:32 ` Mark Harig
2011-02-16 0:14 ` Neil Jerram
2011-02-16 2:43 ` Mark Harig
2011-02-16 3:30 ` Francis Southern
2011-02-16 23:46 ` Neil Jerram
2011-02-16 3:03 ` Mark Harig
2011-02-16 8:18 ` Thien-Thi Nguyen
2011-02-17 0:10 ` Neil Jerram
2011-02-17 1:21 ` Mark Harig
2011-02-16 21:17 ` Ludovic Courtès
2011-02-17 0:14 ` Neil Jerram
2011-02-17 3:13 ` Mark Harig
2011-02-17 11:33 ` Andy Wingo
2011-02-21 20:23 ` Ludovic Courtès
-- strict thread matches above, loose matches on Subject: below --
2011-02-19 17:40 Bruno Haible
2011-02-19 17:56 ` Ralf Wildenhues
2011-02-24 23:31 ` Ludovic Courtès
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=877hd3wot5.fsf@ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--cc=Ralf.Wildenhues@gmx.de \
--cc=bug-guile@gnu.org \
/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).