From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Hans Hagen <j.hagen@freedom.nl>
Subject: Re: lpdf.registerfontmethod
Date: Fri, 7 Jul 2023 14:05:39 +0200 [thread overview]
Message-ID: <8473007b-13c3-6c58-ab3f-00cd66e9a32c@freedom.nl> (raw)
In-Reply-To: <31d1664581869deb44737ccc701cd6af601bb1f2.camel@telus.net>
On 7/7/2023 4:51 AM, Max Chernoff wrote:
> Hi Hans,
>
> In lpdf-emb.lmt, there's a commented-out definition of
> lpdf.registerfontmethod that I'd like to use. I've uncommented this in
> my installation and it's worked pretty well for me, so can you please
> uncomment/enable this by default in the distribution?
I'll check it but no time today.
btw ... as you like low level hacking ...
pdftex has a mechanism called pgc (pdf glyph containers) and these are
used when no pk font is found (which also means: no map entry)
\pdffont ... =
\pdfscale 1000
\pdfglyph 1 100 0 0 100 100
... pdf code ...
\pdfendglyph
\pdfendfont
of course one needs a matching tfm file. I searched my disk but it looks
like i removed all the test files of those times. It was some
playground for Thanh and me in the good old pdftex dev days but the
outlines from mp at that time were not good enough to use in these
containers. (It was when the mp to pdf conmverter showed up in context
mkii.) One or these now obsolete sub projects; it was kind of fun
anyway. Other experiments, like with saving positions (which originally
was a context feature that involved betweeen run dvi parsing with
dvipos) did make it into a stable feature eventually (read: documented).
The code is still there (in write3.c) but I bet that there is no
documentation.
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2023-07-07 12:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-07 2:51 lpdf.registerfontmethod Max Chernoff
2023-07-07 12:05 ` Hans Hagen via ntg-context [this message]
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=8473007b-13c3-6c58-ab3f-00cd66e9a32c@freedom.nl \
--to=ntg-context@ntg.nl \
--cc=j.hagen@freedom.nl \
/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).