2007/12/5, Hans Hagen <[EMAIL PROTECTED]>:
> Peter Münster wrote:
> > On Wed, Dec 05, 2007 at 09:29:08AM +0100, Wolfgang Schuster wrote:
> >>>> this line should be
> >>>>
> >>>> \def\mksavesortedlistentry#1#2#3#4% class key entry meaning
> >>>>   
> >>>> {\immediatewriteutilitytua{table.insert(js['#1'],{'e','#1',\!!bs#2\!!es,\!!bs#3\!!es})}}
> >>> Both versions give wrong output with optional arguments. But the following
> >>> version works for me:
> >> I forgot to mention you have to regenrate the format with my solution, your
> >> seems to work but I found a way to stop processing because you the optinal
> >> argument can also be used to write a mcro in the first pair of braces and 
> >> this
> >> can produce problems.
> >
> > I've also regenrated the format. But now I understand better: it works well
> > with your patch for core-syn.lua and Hans' patch for core-syn.mkiv:
> >   
> > {\immediatewriteutilitytua{table.insert(js['#1'],{'e','#2',\!!bs#3\!!es,\!!bs#4\!!es})}}
>
> can you summarize what i need to change?

Hi Hans,

the first part was your change in core-syn.mkiv to wrote all elements to the
tua file.

The scond correction is on line 108 in core-syn.lua

The order of key and entry is, the same as in the mkii macro

{ { v[2], v[3] } }, -- key, entry

but you wrote

{ { v[3], v[2] } }, -- entry, key

and can give the wrong entry in the synonymlist, e.g.

\definsynonyms[test][tests]
\test[A]{\TeX}{Description Text}

give

A  Description Text

and not

TeX  Description Text


I tested already in my own installation and this did work.

Wolfgang
___________________________________________________________________________________
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://tex.aanhet.net
archive  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

Reply via email to