unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Andreas Enge <andreas@enge.fr>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Agreeing on some "rules" for packaging.
Date: Sat, 31 Aug 2013 12:00:00 +0200	[thread overview]
Message-ID: <20130831100000.GA13269@debian> (raw)
In-Reply-To: <87d2ouxl43.fsf@gnu.org>

On Sat, Aug 31, 2013 at 11:31:08AM +0200, Ludovic Courtès wrote:
> > No, since @xref creates text starting by "See", so is only suitable for the
> > beginning of a sentence.
>     In general, it is best to use '@ref' only when you need some word
>   other than "see" to precede the reference.  When "see" (or "See") is ok,
>   '@xref' and '@pxref' are preferable.

Well, but I would like to start my sentence with "But" and not "See", since
I am pointing the reader to something that contradicts the previous sentence...

> >> s/defined in @ref {Package Naming}/previously defined (@pxref{Package Naming})/
> > This also gives strange output with an additional "see".
>   previously defined (see Section 4.2 “Package Naming”)

and I would like to write "defined in Section..." and not "previously defined
(see Section".

These info rules should not meddle with our writing style. The result is what
I wanted to achieve in the pdf, and I think it looks acceptable in info.

> > Okay. I suppose this also means that the period at the end of a sentence
> > is not allowed to fall at the end of an input line?
> No, that’s not necessary, fortunately.

So texinfo interprets periods at the end of a line as ends of sentences?
And instead of
"a Scheme interpreter, e.g.
Guile"
one has to write
"a Scheme interpreter,
e.g. Guile"?

Andreas

  reply	other threads:[~2013-08-31 10:00 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-27 21:46 Agreeing on some "rules" for packaging Cyril Roelandt
2013-08-27 22:31 ` Nikita Karetnikov
2013-08-28  6:29 ` Andreas Enge
2013-08-28 12:51 ` Ludovic Courtès
2013-08-28 18:32   ` Cyril Roelandt
2013-08-28 20:56     ` Andreas Enge
2013-08-28 22:42       ` Ludovic Courtès
2013-08-28 22:37         ` Cyril Roelandt
2013-08-29  8:59           ` Ludovic Courtès
2013-08-30 21:59         ` Andreas Enge
2013-08-31  9:31           ` Ludovic Courtès
2013-08-31 10:00             ` Andreas Enge [this message]
2013-08-31 10:22               ` Ludovic Courtès
2013-08-28 20:57     ` Ludovic Courtès
2013-08-30 18:15 ` Nikita Karetnikov
2013-08-30 19:35   ` Ludovic Courtès
2013-08-30 21:09     ` Nikita Karetnikov
2013-08-30 21:22       ` Ludovic Courtès
2013-08-30 21:49     ` Ludovic Courtès
2013-09-07  8:20 ` Nikita Karetnikov
2013-09-07  8:36   ` Andreas Enge
2013-09-07 13:11   ` 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://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130831100000.GA13269@debian \
    --to=andreas@enge.fr \
    --cc=guix-devel@gnu.org \
    --cc=ludo@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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).