From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: [fontloader] node injector / december 3 sync
Date: Sun, 14 Dec 2014 16:21:17 +0100 [thread overview]
Message-ID: <548DAAED.2060206@wxs.nl> (raw)
In-Reply-To: <20141214134555.GA17823@acheron>
On 12/14/2014 2:45 PM, Philipp Gesang wrote:
> Hi Hans,
>
> from the huge changeset two weeks ago:
>
> +texio.write_nl("The font code has been brought in sync with the context version of 2014.12.01 so")
> +texio.write_nl("if things don't work out as expected the interfacing needs to be checked. When")
>
> -- Message received ;) First off, thanks for bringing the
> fontloader into sync again. So far I haven’t noticed any
> obviously broken features.
>
> However, something is off with the node injector. We have a bug
> reported by Hironori Kitagawa that occurs with the ``palt``
> feature in node mode:
>
> http://tug.org/pipermail/luatex/2014-November/004976.html
>
> Importing the shiny new font injector into the merged fontloader
> fixes the issue. FWIW here are test files
>
> https://bitbucket.org/phg/lua-la-tex-tests/src/tip/cnt-features-12-palt.tex
> https://bitbucket.org/phg/lua-la-tex-tests/src/tip/pln-features-12-palt.tex
>
> The Context version runs fine whereas the plain one does so only
> after my “fix”. The same is true for Context itself: replace
> font-inj.lua with node-inj.lua in the format to reproduce the
> issue. Is there a fix to the fontloader, perhaps only temporarily
> until the revised injector becomes ready?
not really as the new injector does more ... also, the new code is kind
of beta so it might not be a good idea to use that in latex already ...
i'm still working on some issues with disc nodes and fonts that have
ligatures that are not ligatures
so, i'd first like to do more tests here; of course you can use the new
injector if you want ... (i'm not touching generic now while messing
with the context variant)
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
| 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 / 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
___________________________________________________________________________________
next prev parent reply other threads:[~2014-12-14 15:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-14 13:45 Philipp Gesang
2014-12-14 15:21 ` Hans Hagen [this message]
2014-12-15 21:00 ` Philipp Gesang
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=548DAAED.2060206@wxs.nl \
--to=pragma@wxs.nl \
--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).