On 2/16/06, Taco Hoekwater <[EMAIL PROTECTED]> wrote: > luigi scarso wrote: > > 2) \ifcase\numexpr(#1+1)\or %% a trick to avoid #1=000 > > seem to works , > > \ifcase\numexpr(#1+0) %% > > no > > Why? > > I am not sure what you want and what exactly doesn't work, > but it is better to use numexpr like this: > > \ifcase \numexpr #1+0\relax > because the closing ) does not actually cause it to stop > scanning forward (it stops in the first case because the > \or cannot be part of \numexpr). Done
However any unic-xxx.tex have this line, and I try to make the same thing. unic-001.tex has \ifcase\numexpr(#1+1)\or \Amacron \or So if #1 = 000 then we jump to \Amacron and this is ok. In unic-037.tex \ifcase\numexpr #1\relax % \unicodeLightHorizontal\or \unicodeHeavyHorizontal\or with #1=001 I jump to \unicodeLightHorizontal first (and this is wrong) and then to \unicodeHeavyHorizontal (and this is ok) With \ifcase\numexpr #1+1\relax % \unicodeLightHorizontal\or \unicodeHeavyHorizontal\or with #1=001 I jump \unicodeHeavyHorizontal (and this is ok) _______________________________________________ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
