Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > gnu.groff.bug > #1569

Re: FAMILY-dependent apostrophe behaviour with -mom

Path csiph.com!3.us.feeder.erje.net!feeder.erje.net!news.linkpendium.com!news.linkpendium.com!panix!usenet.stanford.edu!not-for-mail
From Dale Snell <dalesnell54@gmail.com>
Newsgroups gnu.groff.bug
Subject Re: FAMILY-dependent apostrophe behaviour with -mom
Date Mon, 2 Dec 2019 00:05:58 -0800
Lines 52
Approved bug-groff@gnu.org
Message-ID <mailman.99.1575273977.1979.bug-groff@gnu.org> (permalink)
References <CAMbwm8_6uVsLCqCSFM232TmTNCnDtvXnrDb+cyvtqMC_wq2uuA@mail.gmail.com> <CADUdNdJdnJtvP9=-1WfuSPN1yXSQoZy6AsRfLso-vemk0M-54g@mail.gmail.com>
NNTP-Posting-Host lists.gnu.org
Mime-Version 1.0
Content-Type text/plain; charset="UTF-8"
Content-Transfer-Encoding quoted-printable
X-Trace usenet.stanford.edu 1575273978 2326 209.51.188.17 (2 Dec 2019 08:06:18 GMT)
X-Complaints-To action@cs.stanford.edu
Cc bug-groff@gnu.org
To Marc Simpson <marc@0branch.com>
Envelope-to bug-groff@gnu.org
DKIM-Signature v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=ltnjDxEkaVi+h+h1M8PA3JQSa2ZC4puxqif23/yEn8c=; b=gSkYqNJaX1+Syb4S4Wm/eTaWEs+dOpJHiMBYAsCsuXCY5f++L73n9NJpaaFGiC+Iss FMwg1BWIp5u5qPar+h3c1UST16omiQy/czbFwVWIML72qyOuLFvErBBUhs+CcoBizb06 4CVsPxDyr8KhJxfxRzd2TrAF65ykgJI1MKT13sJk+3YmKqI48Ym4MoiOoWF1wwzGj8vU xu7tV6vHT1bg14JTdcZWbwgROKIUHMcT48PePZkIWPQZdiSh79/n2cj59V2rBZuGmuCg txAnhEzAA3kZHZZ3E0oTC0vrVoeon6m18SFV9XnBsd0zs2vObfKwzcN8DzINkCz5xEnx OBBg==
X-Google-DKIM-Signature v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=ltnjDxEkaVi+h+h1M8PA3JQSa2ZC4puxqif23/yEn8c=; b=PekEKTseSpaq/aFJeiYBzBMD7ajSUeGwhE+cw3z3fEAaakvlGaqpAlAm/ZuS5/k+hP XpVYq1WDp5aJvpyH9l0fy/CtEk1tBKVg8rMuihqhqoOKipjd/THe5Sftb5KpdBH8YcHL pf9iW+MV0KeC7u9QXsT245QTIJ3Zlr40+1rokqB9KBVZY19uZTn5MefyaJ7sWDhJz5Y7 m+uQy5OkpWhTKFYx49HODCcvf0p61kwS/XifyjqzsEBt6jrcIl48pzcERAr4z67qSHkB 8z0zz7G/iZe5o+Y5oM1+9cmSF26mlksw6EdV2dNOhwcIXoA+nqJflaKLp6e1d6dAi9fd nQuQ==
X-Gm-Message-State APjAAAWlHkqzhoqzoiZBb7GyJfeHIliob0jHQHFQ77ZSnrXemiOFNn/D c+30GL2jmH+R+zdjujks/7C5lPyG6rAlVjOmmVMINwFAeiKOjQ==
X-Google-Smtp-Source APXvYqwP45Uu/O38pa7+mH/PcqhNqk+/xYQOA4mtEcOudZ4znII1rgkVRy8wQCyMSJxQmUExfM3FzN7D+I8YfnOajZU=
X-Received by 2002:a2e:9592:: with SMTP id w18mr3550491ljh.98.1575273970287; Mon, 02 Dec 2019 00:06:10 -0800 (PST)
In-Reply-To <CAMbwm8_6uVsLCqCSFM232TmTNCnDtvXnrDb+cyvtqMC_wq2uuA@mail.gmail.com>
X-detected-operating-system by eggs.gnu.org: Genre and OS details not recognized.
X-Received-From 2a00:1450:4864:20::235
X-BeenThere bug-groff@gnu.org
X-Mailman-Version 2.1.23
Precedence list
List-Id "Bug reports for the GNU version of nroff, troff et al" <bug-groff.gnu.org>
List-Unsubscribe <https://lists.gnu.org/mailman/options/bug-groff>, <mailto:bug-groff-request@gnu.org?subject=unsubscribe>
List-Archive <https://lists.gnu.org/archive/html/bug-groff>
List-Post <mailto:bug-groff@gnu.org>
List-Help <mailto:bug-groff-request@gnu.org?subject=help>
List-Subscribe <https://lists.gnu.org/mailman/listinfo/bug-groff>, <mailto:bug-groff-request@gnu.org?subject=subscribe>
X-Mailman-Original-Message-ID <CADUdNdJdnJtvP9=-1WfuSPN1yXSQoZy6AsRfLso-vemk0M-54g@mail.gmail.com>
X-Mailman-Original-References <CAMbwm8_6uVsLCqCSFM232TmTNCnDtvXnrDb+cyvtqMC_wq2uuA@mail.gmail.com>
Xref csiph.com gnu.groff.bug:1569

Show key headers only | View raw


On Sun, Dec 1, 2019 at 11:09 AM Marc Simpson <marc@0branch.com> wrote:
>
> Hi all,
>
> I've noticed a difference in the typesetting of apostrophes depending
> on selected font family with groff -mom.
>
> Steps to reproduce (GNU groff version 1.22.4, from MacPorts):

Hi Marc,

I had the same problem some months back.  I posted some messages
here about it, though I don't remember the dates.

Question:  How are you running Groff?  I was using pdfmom to build
my PDFs, and wound up with typewriter apostrophes in my PDF
output.  However, on a whim, I changed to pdfroff, and suddenly it
all worked correctly.  So was it something I did, or a bug in
pdfmom, or groff, or Peter's install-font.sh script, or, or...?
I don't know.  I have a file of personal macros that I include
when I build anything, and I added the line

.tr '\[cq]

which worked, though .char is probably clearer.  Also, the problem
is not system-dependent; you're apparently using MacOS, while I'm
running Fedora 29.

Anyway, the workaround for me was to use pdfroff.  The command
line is quite a bit longer, but since I have Emacs programmed to
run groff from a single function key, I really don't care.  :-)

> It's unclear to me why this behaviour differs on the basis of family;
> is this a bug, a difference caused by installing a custom font, or
> simply user error?  (If the behaviour is intentional, then there's a
> related state bug in CODE toggling.)

I don't think it's intentional.  I've added fonts before and not
had this problem.  I've not tried rolling back to a prior version
of Groff to check to see if it's version dependent.  I probably
should, One of These Days™.

I'm sorry I can't give you an outright cure, but at least you know
you're not alone.  :-)

Anyway, I hope this helps.

--Dale

-- 
A child of five could understand this!  Fetch me a child of five!

Back to gnu.groff.bug | Previous | Next | Find similar


Thread

Re: FAMILY-dependent apostrophe behaviour with -mom Dale Snell <dalesnell54@gmail.com> - 2019-12-02 00:05 -0800

csiph-web