From: <josephcanedo@gmail.com>
To: "ntg-context@ntg.nl" <ntg-context@ntg.nl>
Subject: Re: "Trial typesetting" in ConTeXt / lua ?
Date: Thu, 19 Nov 2015 19:26:23 +0000 [thread overview]
Message-ID: <8baeb89b4a184ad88342add8c9241b16@gmail.com> (raw)
In-Reply-To: <564E1EFD.6090804@wxs.nl>
[-- Attachment #1.1: Type: text/plain, Size: 2133 bytes --]
I’ll try this in a minute. Thanks a million.
Another bit of complexity, if I have some words in different font (only a few of them), should I call tohbox for these separately and “chain” the different hboxes together ? For example the idea is to “emulate” for instance:
The second line has a word typeset in {\tfx smaller } size.
Thanks a lot again for your help,
Best regards,
Joseph
From: Hans Hagen
Sent: Thursday, November 19, 2015 8:11 PM
To: ntg-context@ntg.nl
On 11/19/2015 5:16 PM, josephcanedo@gmail.com wrote:
> Attached simple MWE. The second line has no ligatures/ no glyph
> substitution/ kern
use this ...
\startluacode
userdata = userdata or { }
if not nodes.typesetters.tohbox then
function nodes.typesetters.tohbox(...)
local list = nodes.typesetters.tonodes(...)
local head = nodes.processors.hpack_filter(list)
local hbox = node.hpack(head)
return hbox
end
end
function userdata.typeset(text)
node.write((nodes.typesetters.tohbox(text)))
end
\stopluacode
i'll add tohbox to the core
-----------------------------------------------------------------
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
___________________________________________________________________________________
[-- Attachment #1.2: Type: text/html, Size: 5187 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 bytes --]
___________________________________________________________________________________
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:[~2015-11-19 19:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-14 10:16 josephcanedo
2015-11-17 8:15 ` josephcanedo
2015-11-17 22:09 ` josephcanedo
2015-11-18 1:46 ` Hans Hagen
2015-11-18 20:49 ` josephcanedo
2015-11-18 21:22 ` Hans Hagen
2015-11-18 21:36 ` josephcanedo
2015-11-19 16:16 ` josephcanedo
2015-11-19 19:11 ` Hans Hagen
2015-11-19 19:26 ` josephcanedo [this message]
2015-11-19 20:36 ` Hans Hagen
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=8baeb89b4a184ad88342add8c9241b16@gmail.com \
--to=josephcanedo@gmail.com \
--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).