From: Rudolf Sykora <rudolf.sykora@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] troff fonts with special characters
Date: Sat, 11 Sep 2010 21:18:04 +0200 [thread overview]
Message-ID: <AANLkTikcgfMetzyyHrE1g2MBzf524N2H3TmRO_fHqKwR@mail.gmail.com> (raw)
In-Reply-To: <AANLkTikgRxdvSX8vj6ZS7Czm4RUEdOPSSW-KqEXt98dy@mail.gmail.com>
Hello,
this starts to be daunting...
When I use troff with the R font, troff uses metrics from /sys/lib/troff/font/R.
Then something, when dpost -f is running, must take the real glyphs
and put them into the final ps.
I guess that something must read /sys/lib/postscript/troff/R to find
out that characters 0-0xFF are now from Times-Roman while above (at
least to 0x25FF) are from LucidaSansUnicodeXX (XX=01--25). Finally ps
is somehow generated (btw. there is no man page for neither
aux/tr2post, nor addpsfonts).
Now, if I want to add some characters which I miss in troff
(mathematics, like U27E8) while using Times-Roman for basic text, it
seems I have to
- find some font that covers my characters
- get the metrics (widths) of my characters (afm2troff.c for T1, some
other tool for TrueType, OpenType)
- add the metrics for troff (e.g. add characters to /sys/lib/troff/font/R)
- add an entry to the table in /sys/lib/postscript/troff/R saying the
name of the new font
- put the font somewhere where gs will find it
- find some bitmap font so that I can also see the characters on
screen, or produce such with ttf2subf
- prey :)
This, if it's really so, sounds really above my powers...
Am I wrong?
Thanks
Ruda
next prev parent reply other threads:[~2010-09-11 19:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-10 12:14 Rudolf Sykora
2010-09-11 19:18 ` Rudolf Sykora [this message]
2010-09-11 22:18 ` Russ Cox
2010-09-12 9:25 ` Rudolf Sykora
2010-09-12 18:25 ` Akshat
2010-09-12 19:38 ` Rudolf Sykora
2010-09-12 20:49 ` Akshat
2010-09-13 14:05 ` Jeff Sickel
2010-09-13 14:28 ` ron minnich
2010-09-13 14:30 ` 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=AANLkTikcgfMetzyyHrE1g2MBzf524N2H3TmRO_fHqKwR@mail.gmail.com \
--to=rudolf.sykora@gmail.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).