From: Ulrike Fischer <news3@nililand.de>
To: ntg-context@ntg.nl
Subject: Re: fonts.enc.reencodings works with latex but not with context
Date: Fri, 11 Mar 2011 13:38:38 +0100 [thread overview]
Message-ID: <11c2au52wkike$.dlg@nililand.de> (raw)
In-Reply-To: <4D7916DA.3050903@wxs.nl>
Am Thu, 10 Mar 2011 19:22:18 +0100 schrieb Hans Hagen:
>> I'm now trying to find out how to setup things so that context users
>> could also benefit from the reencoding. But the equivalent code of
>> the code working with latex doesn't work in context
> this feature is indeed not part of context
Dormant code ;-).
Well in case you want to include it, here a comment:
The pros are: reencode is very easy to use. You only need to find
out the numbers of the original chars.
The cons are that is difficult to clean up the font. E.g. it seems
impossible to get a font table which doesn't show also all the
original chars (which are in positions not needed after the
reencoding) with the reencode-method. You can't adjust kerns and not
pull characters from other fonts.
A "virtual lua font" (\font\mine=luatex-fonts-demo-vf-1-invf.lua) is
much more powerful (and more fun) and works fine with context too,
so I think I will use it the most time and document "reencode" for
(LaTeX)-users who wants to install a chess font in a simple way.
--
Ulrike Fischer
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2011-03-11 12:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-09 16:34 Ulrike Fischer
2011-03-10 18:22 ` Hans Hagen
2011-03-11 12:38 ` Ulrike Fischer [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='11c2au52wkike$.dlg@nililand.de' \
--to=news3@nililand.de \
--cc=ntg-context@ntg.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).