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: Greek in luatex
Date: Tue, 11 Sep 2007 12:12:27 +0200	[thread overview]
Message-ID: <46E66A0B.8030100@wxs.nl> (raw)
In-Reply-To: <7EFEDA40-D45B-4A94-A9CC-2599CF5CF462@uni-bonn.de>

Thomas A. Schmitz wrote:
> OK, the message below didn't get too many responses, so maybe I can  
> rephrase my quiestions in a more precise manner:
> 
> 1. For otftotfm, there's the "unicoding" command where you can  
> replace a character in a certain slot with another unicode character,  
> so you could say
> unicoding "A = uni03D1"
> Is anything like this possible in luatex?

sure, but it depends a bit on what level ... font driven or not

if you have open type fonts, you can add features on the fly ...

\starttext

\installfontfeature[otf][verb]

\definefontfeature
   [test]
   [mode=node,language=dflt,script=latn,
    verb=yes,featurefile=verbose-digits.fea]

{\font\test=name:lmroman10regular*test at 20pt \test 1 2 3 4}

\ctxlua{characters.context.show(\number"00AB)}

\stoptext

this replaces 1 by one and 2 by two ...

the file verbose-digits.fea in in the distribution and an example of a 
fontforge specification file

> 2. I see this code in font-otf.lua:
> fonts.otf.features.data.tex = {
>      { "endash", "hyphen hyphen" },
>      { "emdash", "hyphen hyphen hyphen" },
>      { "quotedblleft", "quoteleft quoteleft" },
>      { "quotedblright", "quoteright quoteright" },
>      { "quotedblleft", "grave grave" },
>      { "quotedblright", "quotesingle quotesingle" },
>      { "quotedblbase", "comma comma" }
> }

that's ligatures and there for backward compatibility (hm, makes me 
wonder if it makes more sense to do that using feature files)

> and this list is used in the function function  
> fonts.initializers.base.otf.texligatures(tfm,value)
> 
> How is it possible to write a similar list and function for just a  
> single font or fonts in a specific typescript?

in principle you can add lua code in typescripts and then register that 
as a feature (so, texligatures or tlig is one of them, as is lineheight)

it all depends on how generic things are; we can think of features like 
remap=name-of-remap-vector (keep in mind that this operates on node 
lists then; rencoding the input i.e. regimes is done differently)

so .. just write down detailed specs -)

Han

-----------------------------------------------------------------
                                           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
___________________________________________________________________________________


  reply	other threads:[~2007-09-11 10:12 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-01 10:56 Thomas A. Schmitz
2007-09-11  6:47 ` Thomas A. Schmitz
2007-09-11 10:12   ` Hans Hagen [this message]
2007-09-13  1:15   ` Arthur Reutenauer
2007-09-13  7:03     ` Taco Hoekwater
2007-09-13 10:24       ` Arthur Reutenauer
2007-09-13 11:38         ` Taco Hoekwater
2007-09-13 12:54           ` Thomas A. Schmitz
2007-09-13 18:36           ` Arthur Reutenauer
2007-09-13 18:49             ` Hans Hagen
2007-09-13 19:24             ` Hans Hagen
2007-09-13 19:45               ` Arthur Reutenauer
2007-09-13 20:20                 ` Hans Hagen
2007-09-14  0:24                   ` Arthur Reutenauer
2007-09-13 20:38                 ` Thomas A. Schmitz
2007-09-13 21:05                   ` Hans Hagen
2007-09-13 21:52                     ` Taco Hoekwater
2007-09-15 23:22                   ` Arthur Reutenauer
2007-09-16  6:56                     ` Taco Hoekwater
2007-09-16  8:22                     ` Taco Hoekwater
2007-09-16 13:01                       ` Thomas A. Schmitz
2007-09-16 23:12                         ` Hans Hagen
2007-09-16 13:08                       ` Arthur Reutenauer
2007-09-16 13:44                         ` Thomas A. Schmitz
2007-09-17  8:48                     ` Hans Hagen
2007-09-13 17:42       ` Hans Hagen
2007-09-13  9:45     ` Thomas A. Schmitz
2007-09-13 10:49       ` Arthur Reutenauer
2007-09-13 12:51         ` Thomas A. Schmitz
2007-09-13 14:25         ` Taco Hoekwater
2007-09-13 17:51       ` 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=46E66A0B.8030100@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).