ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Ulrike Fischer <news3@nililand.de>
To: ntg-context@ntg.nl
Subject: Re: decomposed and precomposde glyphs
Date: Thu, 23 Feb 2017 18:26:43 +0100	[thread overview]
Message-ID: <11gpuiqu4t7fv$.dlg@nililand.de> (raw)
In-Reply-To: <dabb397b-ff01-1b15-84d4-d517c9b3cf60@wxs.nl>

Am Thu, 23 Feb 2017 16:55:08 +0100 schrieb Hans Hagen:

> it's not a ligature but a multiple
> 
> fonts.handlers.otf.addfeature
>    {
>      name    = "decompose",
>      type    = "multiple",
>      nocheck = true, -- new trick


I updated my context version and changed my luaotfload.conf so that
it uses the context fontloader. Then the following plain tex
document (and a similar latex document) works and gives the wanted
output. 

BUT: If I uncomment the AU+0323 then I get a fatal error:

texmf-var/luatex-cache/generic/fonts/otl/lmroman10-regular.luc)table={
 [7684]={ 66, 803 },
}

! error:  (linebreak): invalid list tail, probably missing glue
!  ==> Fatal error occurred, no output PDF file produced!Drücken Sie
eine beliebige Taste . . .

(that's from the terminal output, the log doesn't show the
"table=..." part).


This "invalid list tail" is popping up now an then. Philip even
found a version were context crashed:
https://github.com/lualatex/luaotfload/issues/388


\input luaotfload.sty

\directlua
{
  fonts.handlers.otf.addfeature
  {
    name = "compose",
    type = "ligature",
    data =
        {
          ["Ạ"]={ "A", "̣" },
        },
  }
}
\directlua{
fonts.handlers.otf.addfeature
   {
     name    = "decompose",
     type    = "multiple",
     nocheck = true, 
     data    =
         {
           ["Ḅ"] = { "B", "̣" },
         },
   }
}
%\begin{document}
\font\test={file:lmroman10-regular.otf:mode=node;+decompose;+compose;}

\test

Ḅ Ạ % Ạ  %uncomment this to get a fatal error. 
Ḅ

\bye


With the standard fontloader of luaotfload there is no error but the
output is not correct. 

-- 
Ulrike Fischer 
http://www.troubleshooting-tex.de/

___________________________________________________________________________________
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2017-02-23 17:26 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-23 10:58 Ulrike Fischer
2017-02-23 12:19 ` Hans Hagen
2017-02-23 12:35   ` Ulrike Fischer
2017-02-23 13:08     ` Hans Hagen
2017-02-23 14:05       ` Ulrike Fischer
2017-02-23 15:10         ` Hans Hagen
2017-02-23 15:12       ` Ulrike Fischer
2017-02-23 15:55         ` Hans Hagen
2017-02-23 17:26           ` Ulrike Fischer [this message]
2017-02-23 17:41             ` Hans Hagen
2017-02-23 17:47               ` Ulrike Fischer
2017-02-23 17:45             ` luigi scarso
2017-02-23 17:50               ` Ulrike Fischer
2017-02-23 18:28                 ` luigi scarso
2017-02-23 17:47             ` Hans Hagen
2017-02-23 16:20         ` Arthur Reutenauer
2017-02-24  9:35           ` Ulrike Fischer
2017-02-24 11:52             ` 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='11gpuiqu4t7fv$.dlg@nililand.de' \
    --to=news3@nililand.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).