From: Hans Hagen <pragma@wxs.nl>
To: Mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: active strings in luatex?
Date: Mon, 14 Jan 2008 09:59:40 +0100 [thread overview]
Message-ID: <478B247C.5040704@wxs.nl> (raw)
In-Reply-To: <20080113233024.GG5056@phare.normalesup.org>
Arthur Reutenauer wrote:
>> if i know the precise specs i can build it into the utf collapser
>
> I can work that out for you, but we need to think about how to treat
> all this consistently, in particular with respect to the questions Mojca
> raised:
>
> · Equivalent sequences need to be treated the same way (c + combining
> caron == ccaron).
> · If we need to compose a glyph out of other glyphs, it may be
> accounted for by some OpenType feature (in particular GPOS 'mark'
> and 'mkmk').
> · If nothing else is available, the good ol' TeX way using \accent is
> still valid, but we need to preserve the original Unicode data in
> the PDF (for searching, etc.).
(1) mkiv already has (actually it was one of the first thing
simplemented) an utf composition handler; this one is initialized using
the big char table which has information about the formal composition
sequences
an option is to add more to this (like the lcaron); fo rthose who want
to play with it i added a command (beta upload)
\definecomposedutf 318 108 126 % lcaron
keep in mind that this acts on the input, so it may mess up definitions
that contain l~ sequences; any input processing cq. token processing
(later stage) is kind of dangerous
(2) it is possible (but no handy interface yet, i may make it a
'context' font feature) to complete a font with all it's composed char
susing virtual fotn trickery (see mk.pdf) which resolves the missing
glyph issue
(3) letter this year (after mplib) we will pick up a 'glyph not present
in font' callback that's on our agenda
(4) another option is to deal with it in the node list handlers, but if
possible i want to avoid this (the more passes, the slower)
[there is already quite some framework present in mikv, but not always
interfaced; much of this is also used in performance testing and such
and some is reported in mk.pdf]
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2008-01-14 8:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-28 18:29 Idris Samawi Hamid
2008-01-13 3:31 ` Arthur Reutenauer
2008-01-13 11:18 ` Taco Hoekwater
2008-01-13 14:38 ` Mojca Miklavec
2008-01-14 0:20 ` Arthur Reutenauer
2008-01-13 18:51 ` Arthur Reutenauer
2008-01-13 22:59 ` Hans Hagen
2008-01-13 23:25 ` Idris Samawi Hamid
2008-01-13 23:30 ` Arthur Reutenauer
2008-01-14 8:59 ` Hans Hagen [this message]
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=478B247C.5040704@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).