From: "onf" <onf@disroot.org>
To: "Ihor Radchenko" <yantar92@posteo.net>
Cc: "G. Branden Robinson" <g.branden.robinson@gmail.com>,
<emacs-orgmode@gnu.org>, <groff@gnu.org>,
"Ingo Schwarze" <schwarze@usta.de>
Subject: Re: [BUG] "\fC" macro in ox-man.el [9.6.15 (release_9.6.15 @ /usr/share/emacs/29.2/lisp/org/)]
Date: Thu, 02 Jan 2025 15:29:59 +0100 [thread overview]
Message-ID: <D6RNQQBW0ZRT.286500LUD4SCS@disroot.org> (raw)
In-Reply-To: <D6QQKDIPMTUF.1QUU2S9V18AAK@disroot.org>
Hi Ihor,
On Wed Jan 1, 2025 at 1:30 PM CET, onf wrote:
> On Wed Jan 1, 2025 at 10:38 AM CET, Ihor Radchenko wrote:
> > >> Also, what if we leave \fC and add \f[CR]/.EX on top?
> > >> AFAIU, the worst case scenario for \fC is that it does nothing. By
> > >> leaving it there, we thus retain old working exports working while also
> > >> adding appropriate format when \f[CR] is supported.
> > >
> > > The \f escape sets current font. \fP restores previous font.
> > > What this means is that doing \fC\f[CR]Lorem\fP:
> > > (1) sets the text Lorem in Courier if font name C or CR exists
> > > (2) restores previous font if neither font C nor CR exists
> > > (3) sets font to Courier if both font name C and CR exist
> >
> > What about \fC\f[CR]Lorem\fP\fP?
>
> (1) if both C and CR exist, sets Lorem in Courier
> (2) if only C or CR exists, sets font to Courier
> (3) if neither exists, does nothing
>
> [...]
>
> It's important to understand that troff commands don't really use
> nesting or a stack as one might be used to from HTML and similar
> markup languages. That's why it's also not possible to e.g. nest
> bold and italic like this:
> Normal \fBbold \fIbold-italic\fP bold\fP normal
> [...]
> One has to do one of these instead:
> Normal \fBbold \f[BI]bold-italic\fP bold\fR normal
> Normal \fBbold \f[BI]bold-italic\fB bold\fR normal
> Normal \fBbold\fP \f[BI]bold-italic\fP \fBbold\fP normal
I don't know why it took me so long, but I think what you're looking
for is this:
\fC\f(CRLorem\fR
\fR sets regular / "roman" font, i.e. what's usually the default.
Just as shown in the examples with nested italic within bold, you
will likely have to track the style changes desired by Org-mode
and map them into the appropriate fonts, since troff knows only
fonts, not "text styles", and so these changes cannot be nested.
Note that I've used the syntax \f(, not \f[], because older
implementations of troff (such as Plan9 troff iirc) don't support it.
If you used \f[CR] on those platforms, it would be interpretted like:
\f[ -> set font [ (non-existent => ignored)
CR] -> text CR]
meaning you would get CR] in the text.
~ onf
next prev parent reply other threads:[~2025-01-02 14:31 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 [this message]
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
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=D6RNQQBW0ZRT.286500LUD4SCS@disroot.org \
--to=onf@disroot.org \
--cc=emacs-orgmode@gnu.org \
--cc=g.branden.robinson@gmail.com \
--cc=groff@gnu.org \
--cc=schwarze@usta.de \
--cc=yantar92@posteo.net \
/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).