emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: emacs-orgmode@gnu.org, groff@gnu.org
Subject: Re: [BUG] "\fC" macro in ox-man.el [9.6.15 (release_9.6.15 @ /usr/share/emacs/29.2/lisp/org/)]
Date: Sat, 4 Jan 2025 00:37:31 -0600	[thread overview]
Message-ID: <20250104063731.cwp5fylyn5nj75lk@illithid> (raw)
In-Reply-To: <D6SUZCI7NIR4.20OQPOJ5Q7RT@disroot.org>


[-- Attachment #1.1: Type: text/plain, Size: 2358 bytes --]

Hi onf,

At 2025-01-04T01:23:02+0100, onf wrote:
> > > Note that \f[CBI] will break in old troffs due to the "new" \f[]
> > > syntax, so a warning should probably be emitted. And I have no
> > > idea how good support for {bold,italic} Courier is in older troffs
> > > either.
> >
> > Poor, in general.  Where Courier bold-italic existed, it was
> > sometimes called "CX".
> 
> I meant support for CB and CI, not CBI.

Also poor, outside of the horizon I previously articulated.  :(

System V Unix supported these names _only_ on the "aps" device
(Autologic APS-5).  Plan 9 doesn't.  DWB 3.3 doesn't.

The "aps" device on Solaris 10 troff supports CB but not CI.

> Speaking of the left italic correction (\,), could you please give me
> some example(s) where it's actually useful? I have yet to see a single
> instance where it changes anything... (I don't rule out the
> possibility that I may be using it incorrectly or that my fonts might
> be misconfigured, though.)

Sure.  I'm attaching an extract of groff_diff(7) in PDF, which not only
explains the issue but illustrates the problem it solves.

Our Texinfo manual has the same textual content but doesn't deliberately
exhibit the problem.

> > [5] I admit I'm a little fuzzy on Plan 9 from User Space's
> >     objectives for its troff.  I can say that the pace of its
> >     development is not swift.  I don't think Plan 9 advocates pick
> >     up the system to use its typesetter.
> 
> My understanding is that Plan 9 from User Space is merely providing a
> port of the Plan 9 program.

It's a whole OS!  Give it credit... ;-)

> My impression of Plan 9's troff is that it's a poorly maintained
> descendant of DWB troff that's used only to format manpages.

I wouldn't say _poorly_ maintained; its commit rate seems to match or
even exceed its defect rate.  This could illustrate (1) low adoption or
(2) adequacy for the (limited?) purposes to which people apply it.

I'd like to see an attempt at reconstructing DWB 3.4 from the existing
DWB 3.3 code base (made portable) and an old snapshot of Plan 9, maybe
circa 2000.  It'd be good to have a plausible exhibit of the end of the
line for AT&T Unix troff--what the body looked like at the murder scene.

https://lists.gnu.org/archive/html/groff/2022-12/msg00097.html

Regards,
Branden

[-- Attachment #1.2: italic.pdf --]
[-- Type: application/pdf, Size: 431369 bytes --]

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2025-01-04  6:38 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-01  7:51 [BUG] "\fC" macro in ox-man.el [9.6.15 (release_9.6.15 @ /usr/share/emacs/29.2/lisp/org/)] Xiyue Deng
2024-03-03 13:30 ` Ihor Radchenko
2024-03-12  0:06   ` Xiyue Deng
2024-03-13 11:25     ` Ihor Radchenko
2024-03-14 21:46       ` Jeremy Sowden
2024-05-22  9:54         ` Ihor Radchenko
2024-12-18 17:20         ` G. Branden Robinson
2024-12-22 15:41           ` Ihor Radchenko
2024-12-31 17:00             ` G. Branden Robinson
2024-12-31 18:15               ` Ihor Radchenko
2024-12-31 18:42                 ` onf
2024-12-31 18:54                   ` onf
2025-01-01  9:38                   ` Ihor Radchenko
2025-01-01 12:30                     ` onf
2025-01-02 14:29                       ` onf
2025-01-02 17:47                       ` [BUG] ox-man: Nested markup is broken (was: [BUG] "\fC" macro in ox-man.el [9.6.15 (release_9.6.15 @ /usr/share/emacs/29.2/lisp/org/)]) Ihor Radchenko
2025-01-02 21:51                         ` onf
2025-01-03  8:38                           ` [BUG] "\fC" macro in ox-man.el [9.6.15 (release_9.6.15 @ /usr/share/emacs/29.2/lisp/org/)] G. Branden Robinson
2025-01-04  0:23                             ` onf
2025-01-04  6:37                               ` G. Branden Robinson [this message]
2025-01-04 20:10                                 ` onf
2025-01-05 15:24                                   ` Lennart Jablonka
2025-01-04 13:26                             ` Ihor Radchenko
2025-01-04 16:22                               ` Dave Kemper
2025-01-04 17:37                                 ` Ihor Radchenko
2025-01-02 12:14                     ` G. Branden Robinson
2025-01-04 12:21                       ` Ihor Radchenko
2025-01-02 12:38                 ` G. Branden Robinson
2025-01-02 14:21                   ` onf
2025-01-04 12:36                   ` Ihor Radchenko

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://www.orgmode.org/

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

  git send-email \
    --in-reply-to=20250104063731.cwp5fylyn5nj75lk@illithid \
    --to=g.branden.robinson@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=groff@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/emacs/org-mode.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).