# [luatex] some bits of opentype math testing

Hans Hagen pragma at wxs.nl
Wed Jul 28 12:33:40 CEST 2010

```On 28-7-2010 11:49, ulrik.vieth at arcor.de wrote:
>
>   ----- Original Nachricht ----
> Von:     Taco Hoekwater<taco at elvenkind.com>
> An:      Ulrik Vieth<ulrik.vieth at arcor.de>
> Datum:   28.07.2010 08:06
> Betreff: Re: [luatex] some bits of opentype math testing
>
>> On 07/28/2010 02:00 AM, Ulrik Vieth wrote:
>>
>>> Is there anything, we could use as well to diagnose problems?
>>
>> For actual debugging, it depends on how brave you are, debugging
>> something as large as luatex is definitely not for the faint of
>> heart. When trying to diagnose problems, a minimal test file is
>> always needed, so it helps a lot if there was such a file included
>> in the bug report.
>
> So there is no magic  \tracingwhatever we could turn on?

Something \tracingbugs you mean -)

In context there is a lot of tracing code that we can use to look into
node lists and so, but still one needs to know what to look for. There
is also quite some font tracing code, but in the case it would probably
not have helped much simply because when some output looks ok there is
no reason to assume a bug. As we started with cambria it also means that
this font becomes a benchmark which easily leads to the assumption that
it has no problems.

Hans

-----------------------------------------------------------------