ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Ulrike Fischer <news3@nililand.de>
To: ntg-context@ntg.nl
Subject: Re: fontloader fails with "bad argument #1 to 'for iterator"
Date: Sat, 18 Aug 2018 14:13:16 +0200	[thread overview]
Message-ID: <19fdrzi3zo8an.dlg@nililand.de> (raw)
In-Reply-To: <a8a7fadd-ffa8-34ac-7af5-7c811f0cc577@xs4all.nl>

Am Sat, 18 Aug 2018 13:47:32 +0200 schrieb Hans Hagen:

>> On the luaotfload tracker was a bug report that the loading of a
>> font failed if too many character variant were requested
>> 
>> https://github.com/lualatex/luaotfload/issues/424
>> 
>> I wanted to check if the problem still exist with a current
>> fontloader. Here (both context and latex) the loading of this fonts
>> fails even if no character variants at all are requested:
 
> What are character variants? Anyway, if it's "features" there is no 
> relation between choosing features and loading a font.

As far as I got it they are open type features to select variants of
characters and are used as any other open type feature:

;+cv01=0;+cv02=0;+cv03=0;+cv04=0;+cv05=0;+cv06=0;...

In the bug report the problem seemed to be that the user used so
many of this features that some string got too long. 

But due to the other error I couldn't look at it yet.


>> it is in the 07-iosevka-type-slab-2.0.0.zip.
> Hm, another of these N x M instance fonts generated from a common 
> source? I can catch the bad coverage table but it will never render okay.

Thanks. And I will forwared the warning ;-).

-- 
Ulrike Fischer 
https://www.troubleshooting-tex.de/

___________________________________________________________________________________
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

      reply	other threads:[~2018-08-18 12:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-18 11:17 Ulrike Fischer
2018-08-18 11:47 ` Hans Hagen
2018-08-18 12:13   ` 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=19fdrzi3zo8an.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).