From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: context works, contextjit fails with Junicode
Date: Wed, 02 Jul 2014 00:08:37 +0200 [thread overview]
Message-ID: <53B33165.6020100@wxs.nl> (raw)
In-Reply-To: <53B32D91.9000906@rik.users.panix.com>
On 7/1/2014 11:52 PM, Rik Kabel wrote:
> The jit engine complains
>
> lua error > error on line 12 in file
> C:/Users/rik/Desktop/junicode_bold.tex:
> C:/ConTeXt/tex/texmf-context/tex/context/base/font-otp.lua:192:
> invalid value (nil) at index 1 in table for 'concat'
only luajittex?
are there more trace lines?
> and produces an incorrect document (no bold or bold italic fonts used)
> for the following document, while the standard engine produces a correct
> document without complaint:
>
> \starttypescript [serif] [junicode]
> \definefontsynonym [Serif] [file:junicode]
> \definefontsynonym [SerifItalic] [file:junicode-italic]
> \definefontsynonym [SerifBold] [file:junicode-bold]
> \definefontsynonym [SerifBoldItalic] [file:junicode-bolditalic]
> \stoptypescript
> \starttypescript [junicode]
> \definetypeface [junicode] [rm] [serif] [junicode] [default]
> \stoptypescript
> \setupbodyfont[junicode]
> \starttext
> \fontalternative{\it\fontalternative}{\bf\fontalternative}{\bi\fontalternative}
> \stoptext
>
> I also note that the standard typescript for junicode is not useful.
> Beside mentioning goudysans (a cosmetic issue only, I think) the font
> file names do not reflect current file names for the font as available
> at http://junicode.sourceforge.net. If anybody has a typescript
> reflecting current ttf file naming, I would appreciate receiving a copy,
> either via the list or directly.
>
> (The typescript in the above is stripped to a minimum, and not what I
> would use other than in such an example.)
what font is that?
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-07-01 22:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-01 21:52 Rik Kabel
2014-07-01 22:08 ` Hans Hagen [this message]
2014-07-01 23:30 ` Rik Kabel
2014-07-02 0:45 ` Hans Hagen
2014-07-02 1:11 ` Rik
2014-07-02 9:30 ` Hans Hagen
2014-07-02 14:23 Andres Conrado
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=53B33165.6020100@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).