Hi Max,
> The example in the original message is reproducible with Plain LuaTeX
(without loading luaotfload), so the behaviour is a part of the engine,
but it could be considered as either a bug or a feature depending on
your viewpoint.
It's dangerous to introduce heuristics because it prevents experiments.
Also, when something is changed 'hard coded' older examplex and even
articles or manuals explaining things (concepts) become invalid (which
is why in luametatex many more aspects can be controlled by flags).
Hard coded heuristics are among the reasons that made me stop using the
ff fiontloader in luatex.
This otfload used in latex/someplainvariant is then the best place to
intercept something. Actually when it comes to numbers, in the case of
pdf one should always be careful with small numbers, for instance there
are cases where tiny boundingbox values can crash / confuse viewers (or
in a worst case a number serializes as [+-]n.mE[+-]p goes unnoticed.
So if your patch to otfload intercepts bordercase user input, that looks
the right approach to me.
FGIW, in MkIV we don't intercept the zero so that one is then valid and
can be used for checking the 'renderer default'. In MkXL we have some
checks that kick in earlier because of other reasons.
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
-----------------------------------------------------------------
_______________________________________________
dev-luatex mailing list -- [email protected]
To unsubscribe send an email to [email protected]
