From: Philipp Gesang <phg@phi-gamma.net>
To: news3@nililand.de, mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: issue with Junicode font and \input
Date: Sat, 13 Feb 2016 22:59:29 +0100 [thread overview]
Message-ID: <20160213215929.GB7256@phlegethon> (raw)
In-Reply-To: <19ufmr77naot8.dlg@nililand.de>
[-- Attachment #1.1: Type: text/plain, Size: 783 bytes --]
···<Datum: Saturday, 13. February 2016>···<Von: Ulrike Fischer>···
> Am Sat, 13 Feb 2016 20:26:52 +0100 schrieb Pablo Rodriguez:
>
> > I have the following sample:
> >
> > \definefontfamily[mainface][rm][Junicode]
> > \setupbodyfont[mainface]
> > \starttext
> > \input zapf
> > \stoptext
> >
> > I experience an endless loop (or an unended compilation that I have to
> > kill) if "\input zapf" is selected.
>
> Perhaps it is the same problem that has been found for latex and
> caused documents to hang:
> https://github.com/lualatex/luaotfload/issues/322
I patched font-otn.lua to disable the “contextpos” features to
get rid of the hang. That’s the old loader, though; no idea where
it hangs with the current one.
[-- 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
___________________________________________________________________________________
next prev parent reply other threads:[~2016-02-13 21:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-13 19:26 Pablo Rodriguez
2016-02-13 21:11 ` Ulrike Fischer
2016-02-13 21:59 ` Philipp Gesang [this message]
2016-02-13 23:32 ` Hans Hagen
2016-02-14 1:15 ` Pablo Rodriguez
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=20160213215929.GB7256@phlegethon \
--to=phg@phi-gamma.net \
--cc=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).