From: "Ulrich Spörlein" <uqs@spoerlein.net>
To: discuss@mdocml.bsd.lv
Subject: Re: Render \*(Pi as pi, not n
Date: Thu, 2 Jun 2011 13:15:47 +0200 [thread overview]
Message-ID: <20110602111547.GT1002@acme.spoerlein.net> (raw)
In-Reply-To: <4DE75DF0.4010600@bsd.lv>
On Thu, 02.06.2011 at 12:54:56 +0300, Kristaps Dzonsons wrote:
> On 02/06/2011 12:28, Ulrich Spörlein wrote:
> > Hello,
> >
> > please consider doing the same as groff here, fixing ambiguities
> >
> > Before:
> >
> > The atan2(), atan2f(), and atan2l() functions, if successful,
> > return the arc tangent of y/x in the range [-n, +n] radians.
> >
> > After:
> >
> > The atan2(), atan2f(), and atan2l() functions, if successful,
> > return the arc tangent of y/x in the range [-pi, +pi] radians.
> >
> > Although 'n' might look a little like 'π' we shouldn't replace random
> > letters for greek symbols that have different meaning.
> >
> > Cheers,
> > Uli
>
> Ulrich,
>
> This is not something that groff agrees upon. The stock groff on
> GNU/Linux returns `n' instead of `pi'. Version: GNU troff (groff)
> version 1.21. We've discussed this before, I think... the quick
> solution is to patch it downstream (chars.in). I personally don't like
> the attenuation of /any/ Greek characters, as my own formulas end up
> confusing (those with both pi and n, for example).
I disagree on groff disagreeing
FreeBSD base groff version 1.19.2: \*(Pi -> pi
FreeBSD port groff version 1.21: \*(Pi -> pi
Ubuntu groff version 1.20.1: \*(Pi -> pi
Which distribution where you checking?
Uli
--
To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv
next prev parent reply other threads:[~2011-06-02 11:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-02 9:28 Ulrich Spörlein
2011-06-02 9:54 ` Kristaps Dzonsons
2011-06-02 11:15 ` Ulrich Spörlein [this message]
2011-06-02 11:57 ` Ingo Schwarze
2011-06-02 13:13 ` Kristaps Dzonsons
2011-06-02 13:22 ` Kristaps Dzonsons
2011-06-02 16:09 ` Ingo Schwarze
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=20110602111547.GT1002@acme.spoerlein.net \
--to=uqs@spoerlein.net \
--cc=discuss@mdocml.bsd.lv \
/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).