ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
	"Thomas A. Schmitz" <thomas.schmitz@uni-bonn.de>
Subject: Re: lmtx: new text & math font stuff
Date: Wed, 30 Dec 2020 21:59:29 +0100	[thread overview]
Message-ID: <511beb47-603b-02d3-3b69-9b2057640af1@xs4all.nl> (raw)
In-Reply-To: <a2f781c6-6395-5b1d-e0f3-47b9806fce1b@uni-bonn.de>

On 12/30/2020 7:27 PM, Thomas A. Schmitz wrote:
> 
> On 12/30/20 4:53 PM, Hans Hagen wrote:
>> As usual, it opens up possibilities, but of course at the price of 
>> testing.
> 
> Hans,
> 
> I had seen the alignment bug as well; this has been fixed in today's 
> upload. I'm in a book project (from xml), so I don't have small examples 
> right now, but I want to point out that there are two more areas where 
> current lmtx has serious problems that luatex doesn't have:

Must have been some side effect of some of the font stuff as iI didn't 
really touch the alignment code.

> 1. I have a bibliography that is structured in sections. lmtx does not 
> respect the scope of these sections, but prints the entire 
> bibliographical list at the first occurrence of 
> \placelistofpublications. I wasn't sure if I had the right keywords and 
> experimented an entire afternoon before I realized this was a bug in 
> lmtx...

hm, should not be too hard to solve (with an example) ... keep in mind 
that there is no functionality difference between mkiv and lmtx 
(although lmtx will evolve), so maybe some oversight in upgrading the 
low level interfacing macros (removing indirectness)

> 2. For some reason, lmtx introduces lots of empty pages into my 
> document. When I compile my book with luatex, I get 176 pages at the 
> moment, in lmtx, I have 208. Must be something about chapter breaks and 
> so on.

here we definitely need an example

> I will try in the next days to come up with examples, but right now, I'm 
> working on a chapter and don't want to interrupt the flow...

sure (sometimes) comparing the tuc files gives a clue

> As always, thanks for your work on context, and best wishes for 2021 - 
> may it suck less that 2020!
Thanks,

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
        tel: 038 477 53 69 | www.pragma-ade.nl | 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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

      reply	other threads:[~2020-12-30 20:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-30 15:53 Hans Hagen
2020-12-30 18:27 ` Thomas A. Schmitz
2020-12-30 20:59   ` Hans Hagen [this message]

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=511beb47-603b-02d3-3b69-9b2057640af1@xs4all.nl \
    --to=j.hagen@xs4all.nl \
    --cc=ntg-context@ntg.nl \
    --cc=thomas.schmitz@uni-bonn.de \
    /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).