From: "Thomas A. Schmitz" <thomas.schmitz@uni-bonn.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Greek in luatex
Date: Sun, 16 Sep 2007 15:01:12 +0200 [thread overview]
Message-ID: <E5D80FB0-DFC4-4995-B4EC-D720A3C9EC0D@uni-bonn.de> (raw)
In-Reply-To: <46ECE7CE.4040301@elvenkind.com>
Hi Arthur, Taco,
you're my heroes! Changing the order of the lookup tables in the .fea
file actually took care of the problem. Thanks for looking into this,
now I get the results I was expecting; every substitution is applied
to the font! Once the initial lookup has been done, this is
reasonably fast, too, so I like it. I'm eagerly waiting for teh new
release next week to see if this works with copy-and-past from pdfs.
So this appears to be one way to deal with ASCII input a la babel.
Easy to implement, but fails on fonts that don't have the glyphs for
the Latin characters.
One trivial question: when I want to experiment with feature files,
the cached instance of the font seems to be in the way. Only after
deleting the current luatex-cache, regenerating it and recompiling
the format do I get proper results. Is there an easier/faster way to
do this?
Will now go on and experiment some more, especially with type1/afm-
based fonts. Thanks a lot, best wishes
Thomas
On Sep 16, 2007, at 10:22 AM, Taco Hoekwater wrote:
>
> Hi guys,
>
> Try this ordering:
>
>> lookup GreekBabelLookupMultiple {
>> ...
>> } GreekBabelLookupMultiple ;
>>
>> lookup GreekBabelLookupSimple {
>> ...
>> } GreekBabelLookupSimple ;
>>
>
>
>
___________________________________________________________________________________
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:[~2007-09-16 13:01 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
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 [this message]
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=E5D80FB0-DFC4-4995-B4EC-D720A3C9EC0D@uni-bonn.de \
--to=thomas.schmitz@uni-bonn.de \
--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).