ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Luatex question
Date: Tue, 25 Oct 2011 14:27:16 +0200	[thread overview]
Message-ID: <4EA6AB24.5090105@wxs.nl> (raw)
In-Reply-To: <CAPoA6K3U+P5pphMY3YeWjdCeftQsraPfDX=0vU-ZO6wUkMmrbw@mail.gmail.com>

On 25-10-2011 14:09, Lutz Haseloff wrote:
> Hi all,
>
> some months ago I printed the name of the current font with following code:
>
> \starttext
> The current font is: \ctxlua{tex.print(font.getfont(font.current()).fullname)}.
> \stoptext
>
> Now I get an error message:
>
> ! LuaTeX error<main ctx instance>:1: no string to print
> stack traceback:
> 	[C]: in function 'print'
> 	<main ctx instance>:1: in main chunk.
> l.2 ...int(font.getfont(font.current()).fullname)}
>                                                    .
> ?
>
> What is the right way now?
> (didn't find any news in functionref.pdf or luatexref-t.pdf)

In order of efficiency (most efficient on top):

\starttext

\ctxlua{tex.print(fonts.hashes.properties[font.current()].fullname)}
 
\ctxlua{tex.print(fonts.hashes.identifiers[font.current()].properties.fullname)}

\ctxlua{tex.print(font.getfont(font.current()).properties.fullname)}

\stoptext

the font.getfont returns the table that tex gets passed and in context 
that table gets normalized, in the sense that variables are collected in 
'properties' and 'parameters'

in general, don't use font.getfont() in context as in the worst case it 
will rebuild a lua table at the tex

in the current beta you can run s-fnt-35.mkiv to see how this works

(this file will be renamed in a next beta)

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
___________________________________________________________________________________


  parent reply	other threads:[~2011-10-25 12:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-25 12:09 Lutz Haseloff
2011-10-25 12:15 ` luigi scarso
2011-10-25 12:27 ` Hans Hagen [this message]
2011-10-25 13:04   ` Lutz Haseloff

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=4EA6AB24.5090105@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).