ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Pablo Rodriguez <oinos@gmx.es>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: lua code prevents compilation
Date: Thu, 02 Apr 2015 01:21:40 +0200	[thread overview]
Message-ID: <551C7D84.8050503@gmx.es> (raw)
In-Reply-To: <5519B31A.1050107@wxs.nl>

On 03/30/2015 10:33 PM, Hans Hagen wrote:
> On 3/30/2015 5:19 PM, Pablo Rodriguez wrote:
>> [...]
>> For some reason unknown to me, the only way to compile the sample is to
>> remove the luacode snippet.
>>
>> I need the lua code to have underscore hyphenation in type commands. And
>> I need two extra \definehyphenationfeatures and \sethyphenationfeatures
>> to invoke it.
>>
>> Have I hit a bug or what am I missing?
> 
> I don't know as i see nothing at all with that code .. this is more fun:

Many thanks for your reply, Hans,

The following code shows the problem:

\startluacode

    function document.addfunnyhyphen(tfmdata)
        local underscore = utf.byte("_")
        local char       = tfmdata.characters[underscore]
        tfmdata.characters[0xFE000]   = {
            width    = 0,
            height   = 0,
            depth    = 0,
            commands = {
                { "right", -char.width },
                { "down", char.depth },
                { "slot", 1, underscore },
            }
        }
    end


utilities.sequencers.appendaction("aftercopyingcharacters","after","document.addfunnyhyphen")

\stopluacode
%~ \definefontfamily[ornamenta][rm][TypographyTribute]
\definehyphenationfeatures[underscore][righthyphenchar="FE000]
\setuphyphenation[method=traditional]
\sethyphenationfeatures[strict]
\setupbodyfont[ornamenta]
\starttext
\hsize\zeropoint
{\sethyphenationfeatures[underscore]\tt pandoc}
A
\stoptext

If you uncomment the line with the font definition, font loading crashes
compilation. It only crashes with this font
(http://www.dafont.com/typographytribute.font) or FontAwesome
(http://www.fontawesome.io).

Both lack the underscore glyph. This causes the crash, since it works
fine if I replace the glyph with an existing glyph in the font.

Error message:

code.tex: ! LuaTeX fatal error error in error handling
\font_helpers_low_level_define ...\scaledfontmode
                                                  \relax \ifcase
\scaledfont...
\font_helpers_trigger_define ..._identifier_class
                                                  \csname
\v_font_identifier...
\applyfontclassstrategies ...\fontface \endcsname
                                                  \else \expandafter
\font_h...
\font_helpers_synchronize_font ...classstrategies
                                                  \fi \setfalse
\c_font_auto...
\rm ->\ifmmode \mathrm \else \normalrm
                                       \fi
\font_basics_switch_style ...ntstyle #1\endcsname
                                                  \edef \fontstyle
{#1}\ifmm...
...

Would it be possible that ConTeXt silently ignores that the font doesn’t
contain the glyph?

I think this might be a bug.

Many thanks for your help,


Pablo
-- 
http://www.ousia.tk
___________________________________________________________________________________
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:[~2015-04-01 23:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-30 15:19 Pablo Rodriguez
2015-03-30 20:33 ` Hans Hagen
2015-04-01 23:21   ` Pablo Rodriguez [this message]
2015-04-02  0:23     ` Hans Hagen
2015-04-02  7:35       ` 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=551C7D84.8050503@gmx.es \
    --to=oinos@gmx.es \
    --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).