ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Philipp Gesang <philipp.gesang@alumni.uni-heidelberg.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: [fontloader] node injector / december 3 sync
Date: Mon, 15 Dec 2014 22:00:34 +0100	[thread overview]
Message-ID: <20141215210033.GA27297@acheron> (raw)
In-Reply-To: <548DAAED.2060206@wxs.nl>


[-- Attachment #1.1: Type: text/plain, Size: 2216 bytes --]

···<date: 2014-12-14, Sunday>···<from: Hans Hagen>···

> 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 ... 

The current goal is to add an option to load the code directly
from Context (TL, minimals). Right now this is non-trivial due to
the extra packaging step involved, so the option will facilitate
testing a lot. Let’s see if anyone is confident enough to test
the fontloader on their own if it becomes easier.

> 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)

Just running my tests ;) I’m fairly content with the prospect
that the issue is already addressed in the beta.

Philipp


[-- Attachment #1.2: Type: application/pgp-signature, Size: 819 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 bytes --]

___________________________________________________________________________________
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
___________________________________________________________________________________

      reply	other threads:[~2014-12-15 21:00 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
2014-12-15 21:00   ` Philipp Gesang [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=20141215210033.GA27297@acheron \
    --to=philipp.gesang@alumni.uni-heidelberg.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).