From: schwarze@mandoc.bsd.lv
To: source@mandoc.bsd.lv
Subject: mandoc: In PostScript and PDF output, one AFM unit is not nearly enough
Date: Tue, 15 Jan 2019 07:16:48 -0500 (EST) [thread overview]
Message-ID: <e3eec314e8c86806@fantadrom.bsd.lv> (raw)
Log Message:
-----------
In PostScript and PDF output, one AFM unit is not nearly enough
inter-word spacing, let's try again with 250 AFM units.
Regression caused during my recent term_flushln() reorg in rev. 1.278,
reported by brynet@ (sorry and many thanks for reporting).
Modified Files:
--------------
mandoc:
term.c
Revision Data
-------------
Index: term.c
===================================================================
RCS file: /home/cvs/mandoc/mandoc/term.c,v
retrieving revision 1.279
retrieving revision 1.280
diff -Lterm.c -Lterm.c -u -p -r1.279 -r1.280
--- term.c
+++ term.c
@@ -374,8 +374,9 @@ term_field(struct termp *p, size_t vbl,
continue;
case ' ':
case ASCII_NBRSP:
- vbl++;
- vis++;
+ dv = (*p->width)(p, ' ');
+ vbl += dv;
+ vis += dv;
continue;
default:
break;
--
To unsubscribe send an email to source+unsubscribe@mandoc.bsd.lv
reply other threads:[~2019-01-15 12:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=e3eec314e8c86806@fantadrom.bsd.lv \
--to=schwarze@mandoc.bsd.lv \
--cc=source@mandoc.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).