fontloader fails with "bad argument #1 to 'for iterator"

fontloader fails with "bad argument #1 to 'for iterator"

[Ulrike Fischer]

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:

\starttext

\font\x={file:iosevka-type-slab-regular.ttf}
\x

ablub
\stoptext 


gives 
...ext/tex/texmf-context/tex/context/base/mkiv/font-oup.lua:2137:
bad argument #1 to 'for iterator' (table expected, got nil)


The font can be get from 

https://github.com/be5invis/Iosevka/releases

it is in the 07-iosevka-type-slab-2.0.0.zip.



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

Re: fontloader fails with "bad argument #1 to 'for iterator"

[Hans Hagen]

On 8/18/2018 1:17 PM, Ulrike Fischer wrote:
> 
> 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.

> \starttext
> 
> \font\x={file:iosevka-type-slab-regular.ttf}
> \x
> 
> ablub
> \stoptext
> 
> 
> gives
> ...ext/tex/texmf-context/tex/context/base/mkiv/font-oup.lua:2137:
> bad argument #1 to 'for iterator' (table expected, got nil)
> 
> 
> The font can be get from
> 
> https://github.com/be5invis/Iosevka/releases
> 
> 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.

Hans


-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
        tel: 038 477 53 69 | www.pragma-ade.nl | 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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

Re: fontloader fails with "bad argument #1 to 'for iterator"

[Ulrike Fischer]

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
___________________________________________________________________________________