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:44:41 +0200 [thread overview]
Message-ID: <703D75F8-11DD-4848-AC09-FE296B62E6AB@uni-bonn.de> (raw)
In-Reply-To: <20070916130817.GA2228@phare.normalesup.org>
On Sep 16, 2007, at 3:08 PM, Arthur Reutenauer wrote:
> Yes, it works. So Fontforge is sensitive to the order in which the
> lookups
> are defined in the file? Interesting ...
>
> Thomas, you can try this but I have made a mistake in the Unicode
> code
> for omega with subscribed iota: it should be 1FF3 and not 1FD3.
>
> Arthur
Yep, I had already fixed that (and also replied to Taco's message,
the context list is again a bit out of order today). Arthur, while
we're at it: could you try and insert this line into the fea-file:
sub quotedbl quotesingle i by un1FD3 ;
whenever I try anything like this with the quotedbl character (which
produces some ligatures), I get this error:
</Users/tas/texmf/fonts/opentype/greek/bosporos/BosporosU.otf
!luaTeX error (file /Users/tas/texmf/fonts/opentype/greek/bosporos/
BosporosU.otf): Unexpected error: 255 != 256
==> Fatal error occurred, no output PDF file produced!
(Or similar errors with other fonts). The mechanism for the single
dieresis works:
sub quotedbl i by uni03CA ;
but nothing with quotedbl + something else. Do you have any ideal
what triggers this error?
Best
Thomas
___________________________________________________________________________________
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:44 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
2007-09-16 23:12 ` Hans Hagen
2007-09-16 13:08 ` Arthur Reutenauer
2007-09-16 13:44 ` Thomas A. Schmitz [this message]
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=703D75F8-11DD-4848-AC09-FE296B62E6AB@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).