From: "Piotr Findeisen" <piotr.findeisen@gmail.com>
To: "Jonas Fonseca" <fonseca@diku.dk>
Cc: git@vger.kernel.org
Subject: Re: Documentation/user-manual.txt, asciidoc and "--" escapes
Date: Mon, 10 Nov 2008 11:14:43 +0100 [thread overview]
Message-ID: <ddb82bf60811100214j4246cf25yc1263c2ae8cd10fc@mail.gmail.com> (raw)
In-Reply-To: <20081110100757.GA12868@diku.dk>
>
>> I noticed that all substitutions "--" -> "—", where "—" is a part of
>> sentence punctuation, match \w--\w pattern (e.g. no spaces on both
>> sides) and probably this is how it should be written in English. But
>> basing on this doesn't seem to me to be fool proof.
>
> So another option is to disable all substitution of "--" and just use
> the "—" character when it is explicitly needed. The documentation is
> using UTF-8 after all. This would also fix the usage of "--" in the
> manpages, e.g.
>
> You've now initialized the working directory--you may notice ...
>
> in gittutorial(7). On my setup, with "--" replaced with "—", I get the
> following nroff code:
On my machine, make gittutorial.7 produces manpage that displays "--"
in this place :)
>
> You've now initialized the working directory\(emyou may notice
Anyway, this may be a good idea to use unambiguous "—" (though people
writing docs may be used to using "--" as a punctuation). I can run
through the Documentation replacing "\w--\w" with m-dash, if you want.
Regards,
Piotr
next prev parent reply other threads:[~2008-11-10 10:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ddb82bf60811061904t5defc492m80cd1b759674eb6@mail.gmail.com>
2008-11-07 3:09 ` Fwd: Documentation/user-manual.txt, asciidoc and "--" escapes Piotr Findeisen
2008-11-09 8:44 ` Piotr Findeisen
2008-11-09 18:52 ` Jonas Fonseca
2008-11-10 7:38 ` Piotr Findeisen
2008-11-10 10:07 ` Jonas Fonseca
2008-11-10 10:14 ` Piotr Findeisen [this message]
2008-11-12 0:04 ` Jonas Fonseca
2008-11-14 13:02 ` Piotr Findeisen
2008-11-15 12:07 ` Junio C Hamano
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=ddb82bf60811100214j4246cf25yc1263c2ae8cd10fc@mail.gmail.com \
--to=piotr.findeisen@gmail.com \
--cc=fonseca@diku.dk \
--cc=git@vger.kernel.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 NNTP newsgroup(s).