From: Ingo Schwarze <schwarze@usta.de>
To: discuss@mdocml.bsd.lv
Subject: Re: .Fn _* issue
Date: Sat, 25 Sep 2010 23:38:12 +0200 [thread overview]
Message-ID: <20100925213812.GE23359@iris.usta.de> (raw)
In-Reply-To: <20100925063547.GB14869@bramka.kerhand.co.uk>
Hi Jason,
Jason McIntyre wrote on Sat, Sep 25, 2010 at 07:35:23AM +0100:
> hi. the source, from cacheflush(3):
>
> .Sh SYNOPSIS
> .In machine/sysarch.h
> .Ft int
> .Fn cacheflush "void *addr" "int nbytes" "int cache"
> .Ft int
> .Fn _flush_cache "char *addr" "int nbytes" "int cache"
>
> formats as:
>
> SYNOPSIS
> #include <machine/sysarch.h>
>
> int
> cacheflush(void *addr, int nbytes, int cache);
>
> int
> _flush_cache(char *addr, int nbytes, int cache);
>
> so the issue is the initial `_' in _flush_cache. it's formatted in a
> different font to the rest of the function name (you can see this best
> on a terminal).
As Kristaps said, the first underscore is rendered underlined.
Apparently, that's the default interpretation of "_\b_".
The second understore, though, is rendered bold, even though
it's physically the exact same sequence of charachters, "_\b_".
Probably, that happens because the preceding 'h' character
is bold and not underlined. If i change that 'h' to underlined,
the second underscore becomes underlined, too.
Thus, i agree with Kristaps that i see nothing we could do about it.
It's not a mandoc bug, maybe not even a bug at all, but a limitation
of backspace encoding for bold and underline.
> this is a long standing bug that we always had in old groff, which
> really annoyed me. new groff fixed it.
Not really. What happens is that groff-1.20.1 uses ANSI encoding,
not backspace encoding for bold and underline, and in ANSI encoding,
that limitation does not exist. In ANSI encoding, the bold underscore
is "\e[1m_" while the underlined underscore would be "\e[4m_",
the "\e" representing the escape character (ASCII 0x1b).
Yours,
Ingo
--
To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv
next prev parent reply other threads:[~2010-09-25 21:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-25 6:35 Jason McIntyre
2010-09-25 15:23 ` Kristaps Dzonsons
2010-09-25 15:35 ` Jason McIntyre
2010-09-25 15:45 ` Kristaps Dzonsons
2010-09-25 17:47 ` Jason McIntyre
2010-09-25 20:18 ` Kristaps Dzonsons
2010-09-25 21:25 ` Jason McIntyre
2010-09-25 21:29 ` Kristaps Dzonsons
2010-09-25 21:38 ` Ingo Schwarze [this message]
2010-09-25 21:43 ` Joerg Sonnenberger
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=20100925213812.GE23359@iris.usta.de \
--to=schwarze@usta.de \
--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).