9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: <tlaronde@kergis.com>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] plan9port troff - \(sq character
Date: Mon, 11 Aug 2025 20:36:22 +0200	[thread overview]
Message-ID: <aJo4Jm_J9_C0j1Pp@kergis.com> (raw)
In-Reply-To: <202508111435.57BEZIdw099738@freefriends.org>

On Mon, Aug 11, 2025 at 05:35:13PM +0300, arnold@skeeve.com wrote:
> Hi.  I'm using plan9port troff to try to reconstitute a book
> from the early 1980s.  The \(sq character in groff (and in
> the original book) came out as small square.
> 
> In plan9 troff I'm getting an upside-down exclamation point.
> Any idea why?  How can I get \(sq to give me a square?

In 9legacy, the (sq is defined with PostScript commands in
sys/lib/troff/font/devutf/charlib/sq

So, as long as it is not an index in a font, but a drawing block
of code, it is a bit weird...

You should try to verify the PostScript code produced in order to
verify that the code for the glyph is added and that the entry in the
dictionnary is correctly called.

But after that, there is ghostscript interpreting the code.

You can perhaps take the PS produced and feed it to another
ghostscript just in order to narrow down the culprit: the PostScript
produced or the way it is rendered i.e. the interpreter.
-- 
        Thierry Laronde <tlaronde +AT+ kergis +dot+ com>
                     http://www.kergis.com/
                    http://kertex.kergis.com/
Key fingerprint = 0FF7 E906 FBAF FE95 FD89  250D 52B1 AE95 6006 F40C

------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T87428730dcc006b0-M0357c314ee8599c3a08cb98e
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

  reply	other threads:[~2025-08-11 18:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-11 14:35 arnold
2025-08-11 18:36 ` tlaronde [this message]
2025-08-11 19:30   ` arnold
2025-08-11 18:57 ` arnold
2025-08-11 19:45   ` ldb
2025-08-13  7:28     ` arnold
2025-08-13 15:00       ` arnold
2025-08-11 19:23 ` LdBeth

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=aJo4Jm_J9_C0j1Pp@kergis.com \
    --to=tlaronde@kergis.com \
    --cc=9fans@9fans.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.
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).