From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/38621 Path: news.gmane.org!not-for-mail From: Hans Hagen Newsgroups: gmane.comp.tex.context Subject: Re: active strings in luatex? Date: Mon, 14 Jan 2008 09:59:40 +0100 Message-ID: <478B247C.5040704@wxs.nl> References: <20080113033142.GB12550@phare.normalesup.org> <478A97CF.1020708@wxs.nl> <20080113233024.GG5056@phare.normalesup.org> Reply-To: mailing list for ConTeXt users NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1200301283 11745 80.91.229.12 (14 Jan 2008 09:01:23 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 14 Jan 2008 09:01:23 +0000 (UTC) To: Mailing list for ConTeXt users Original-X-From: ntg-context-bounces@ntg.nl Mon Jan 14 10:01:44 2008 Return-path: Envelope-to: gctc-ntg-context-518@m.gmane.org Original-Received: from ronja.vet.uu.nl ([131.211.172.88] helo=ronja.ntg.nl) by lo.gmane.org with esmtp (Exim 4.50) id 1JELCQ-0006NQ-2a for gctc-ntg-context-518@m.gmane.org; Mon, 14 Jan 2008 10:01:42 +0100 Original-Received: from localhost (localhost [127.0.0.1]) by ronja.ntg.nl (Postfix) with ESMTP id CCE481FC91; Mon, 14 Jan 2008 10:01:17 +0100 (CET) Original-Received: from ronja.ntg.nl ([127.0.0.1]) by localhost (smtp.ntg.nl [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 25030-01-4; Mon, 14 Jan 2008 10:00:45 +0100 (CET) Original-Received: from ronja.vet.uu.nl (localhost [127.0.0.1]) by ronja.ntg.nl (Postfix) with ESMTP id 8F6921FC77; Mon, 14 Jan 2008 10:00:43 +0100 (CET) Original-Received: from localhost (localhost [127.0.0.1]) by ronja.ntg.nl (Postfix) with ESMTP id EDBC71FC77 for ; Mon, 14 Jan 2008 10:00:41 +0100 (CET) Original-Received: from ronja.ntg.nl ([127.0.0.1]) by localhost (smtp.ntg.nl [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 21917-05-4 for ; Mon, 14 Jan 2008 10:00:11 +0100 (CET) Original-Received: from mail.pragma-ade.net (dsl-083-247-100-017.solcon.nl [83.247.100.17]) by ronja.ntg.nl (Postfix) with ESMTP id 7266F1FC74 for ; Mon, 14 Jan 2008 10:00:10 +0100 (CET) Original-Received: from [10.100.1.100] (unverified [10.100.1.100]) by controller-1 (SurgeMail 3.7b8) with ESMTP id 4900 for ; Mon, 14 Jan 2008 10:00:10 +0100 User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) In-Reply-To: <20080113233024.GG5056@phare.normalesup.org> X-Server: High Performance Mail Server - http://surgemail.com r=-274017400 X-Authenticated-User: hagen@controller-1 X-Virus-Scanned: amavisd-new at ntg.nl X-BeenThere: ntg-context@ntg.nl X-Mailman-Version: 2.1.9 Precedence: list List-Id: mailing list for ConTeXt users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: ntg-context-bounces@ntg.nl Errors-To: ntg-context-bounces@ntg.nl X-Virus-Scanned: amavisd-new at ntg.nl Xref: news.gmane.org gmane.comp.tex.context:38621 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: > = > =B7 Equivalent sequences need to be treated the same way (c + combining > caron =3D=3D ccaron). > =B7 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'). > =B7 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 t= he Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-cont= ext webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___________________________________________________________________________= ________