From: Taco Hoekwater <taco@elvenkind.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Hans Hagen <pragma@wxs.nl>
Subject: Re: bug in \setfontfeature
Date: Wed, 02 Jan 2008 16:14:17 +0100 [thread overview]
Message-ID: <477BAA49.4010607@elvenkind.com> (raw)
In-Reply-To: <op.t4a496t4nx1yh1@your-b27fb1c401>
Idris Samawi Hamid wrote:
> On Wed, 02 Jan 2008 02:11:22 -0700, Hans Hagen <pragma@wxs.nl> wrote:
>
>> in font=otf.lua, patch ...
>>
>> function fonts.otf.set_dynamics(tfmdata,attribute,features)
>> local shared = tfmdata.shared
>> if shared then
>>
>>
>> end
>> end
>>
>> and remake
>
> Does this handle the other [off-list] utf-8 bug that generates an error
> message from font-tfm.lua:591?
No. You get that error because the font does not have a non-breaking
hyphen, and you can "fix" it by changing that line into
if characters[current.char] and characters[current.char].class ==
"mark" then
and regenerating the format. But it will still not "work", because
the glyph still does not exist.
Best wishes, Taco
___________________________________________________________________________________
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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2008-01-02 15:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-02 3:19 Idris Samawi Hamid
2008-01-02 7:16 ` luigi scarso
2008-01-02 8:43 ` Wolfgang Schuster
2008-01-02 9:11 ` Hans Hagen
2008-01-02 10:01 ` Wolfgang Schuster
2008-01-02 10:03 ` Hans Hagen
2008-01-02 15:00 ` Idris Samawi Hamid
2008-01-02 15:14 ` Taco Hoekwater [this message]
2008-01-02 15:39 ` Idris Samawi Hamid
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=477BAA49.4010607@elvenkind.com \
--to=taco@elvenkind.com \
--cc=ntg-context@ntg.nl \
--cc=pragma@wxs.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).