From: Giacomo Tesio <giacomo@tesio.it>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Cc: 9front@9front.org
Subject: Re: [9fans] unexpected tabs in man pages after font change
Date: Wed, 4 Mar 2015 18:11:14 +0100 [thread overview]
Message-ID: <CAHL7psE+Lw5355k5QR7VUD240-9Z7SgNgSN6P8=XF7CmUHwW-w@mail.gmail.com> (raw)
In-Reply-To: <CAHL7psGHyp2O8X+FCr2PMyXh0TpU03eXWDFGZD+ij4bQFkz3uQ@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 936 bytes --]
Interestingly enough the problem disappears with a mono font.
I suspect that troff is inserting such tabs instead of spaces when it
thinks they are the same. Indeed libframe (as far I could understand from
the manual and the sources) properly handles such variable width fonts.
Looks like I've to inform troff about the glyphs sizes... but how?
Giacomo
2015-03-04 17:13 GMT+01:00 Giacomo Tesio <giacomo@tesio.it>:
> Hi, I've just installed a compact sans font (from
> http://input.fontbureau.com/ ) and manual pages started to look broken.
>
> As you can see in the screenshot (man 2 control), there are white spaces
> that looks like tabs in the middle of the text with apparently no reason.
> Even in the troff source (why the hell we still use troff for manual
> pages? :-D) I can see no command that explain this behaviour.
>
> Any tip to fix them?
>
>
> Giacomo
>
> [image: Immagine in linea 1]
>
[-- Attachment #1.2: Type: text/html, Size: 1534 bytes --]
[-- Attachment #2: unexpected-man-tabs.png --]
[-- Type: image/png, Size: 42340 bytes --]
next prev parent reply other threads:[~2015-03-04 17:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-04 16:13 Giacomo Tesio
2015-03-04 17:11 ` Giacomo Tesio [this message]
2015-03-05 14:15 ` erik quanstrom
2015-03-05 15:22 ` Giacomo Tesio
2015-03-04 21:31 ` Aram Hăvărneanu
2015-03-04 22:29 ` Giacomo Tesio
2015-03-04 22:39 ` Stanley Lieber
2015-03-04 23:09 ` Giacomo Tesio
2015-03-05 0:02 ` Giacomo Tesio
2015-03-04 23:56 sl
2015-03-05 0:17 ` Giacomo Tesio
2015-03-05 14:10 ` erik quanstrom
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='CAHL7psE+Lw5355k5QR7VUD240-9Z7SgNgSN6P8=XF7CmUHwW-w@mail.gmail.com' \
--to=giacomo@tesio.it \
--cc=9fans@9fans.net \
--cc=9front@9front.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.
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).