unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Nikita Karetnikov <nikita@karetnikov.org>
Cc: bug-guix@gnu.org
Subject: Re: [PATCH] doc: Improve wording and fix typos in "Introduction" and "Requirements".
Date: Fri, 24 May 2013 17:42:26 +0200	[thread overview]
Message-ID: <87ip28wfj1.fsf@gnu.org> (raw)
In-Reply-To: <87r4gwh8jm.fsf@karetnikov.org> (Nikita Karetnikov's message of "Fri, 24 May 2013 16:22:21 +0400")

Nikita Karetnikov <nikita@karetnikov.org> skribis:

> Is it possible to use ’ instead of ' for the apostrophe and keep the
> source in ASCII?

There’s a contradiction: ’ is not ASCII.

But anyway, the normal way to use Texinfo is like TeX: you use ASCII
quotes, and it does the right thing (see the PDF output, and the Info
output if you’re using makeinfo 5.x.)

> From 3384e3e2e00d3cbef37b913c9a17df5842522ef8 Mon Sep 17 00:00:00 2001
> From: Nikita Karetnikov <nikita@karetnikov.org>
> Date: Fri, 24 May 2013 12:02:15 +0000
> Subject: [PATCH] doc: Improve wording and fix typos in "Introduction" and
>  "Requirements".
>
> * doc/guix.texi (Introduction, Requirements): Rephrase and fix typos.
> ---
>  doc/guix.texi |   66 +++++++++++++++++++++++++++-----------------------------
>  1 files changed, 32 insertions(+), 34 deletions(-)
>
> diff --git a/doc/guix.texi b/doc/guix.texi
> index c3aab81..9a12ff9 100644
> --- a/doc/guix.texi
> +++ b/doc/guix.texi
> @@ -96,42 +96,39 @@ Documentation License.''
>  GNU Guix@footnote{``Guix'' is pronounced like ``geeks'', or ``ɡiːks''
>  using the international phonetic alphabet (IPA).} is a functional
>  package management tool for the GNU system.  Package management consists
> -in all the activities that relate to building packages from source,
> -honoring the build-time and run-time dependencies on packages,
> -installing packages in user environments, upgrading installed packages
> -to new versions or rolling back to a previous set, removing unused
> -software packages, etc.
> +of all activities that relate to building packages from sources,
> +preserving their build-time and run-time dependencies, installing
> +packages in user environments, upgrading installed packages to new
> +versions or rolling back to a previous set, removing unused software
> +packages, etc.

There seems to be some paragraph filling at least here.

Could you rearrange the patch to avoid paragraph filling, so that only
the parts that were really changed show up?

Thanks for looking into this!

Ludo’.

  reply	other threads:[~2013-05-24 15:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-24 12:22 [PATCH] doc: Improve wording and fix typos in "Introduction" and "Requirements" Nikita Karetnikov
2013-05-24 15:42 ` Ludovic Courtès [this message]
2013-05-25  0:30   ` Nikita Karetnikov
2013-05-25 13:56     ` Ludovic Courtès
2013-05-25 21:59       ` Nikita Karetnikov
2013-05-26 20:07         ` Ludovic Courtès
2013-05-25 23:28       ` Alex Sassmannshausen

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=87ip28wfj1.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=bug-guix@gnu.org \
    --cc=nikita@karetnikov.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).