ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Wolfgang Schuster" <schuster.wolfgang@googlemail.com>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: synonyms with MKIV
Date: Thu, 6 Dec 2007 09:26:27 +0100	[thread overview]
Message-ID: <115224fb0712060026x7fa0049ahef2f413edcf9a304@mail.gmail.com> (raw)
In-Reply-To: <475720FF.4000205@wxs.nl>

2007/12/5, Hans Hagen <pragma@wxs.nl>:
> 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	other threads:[~2007-12-06  8:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-03 16:44 Peter Münster
2007-12-03 17:58 ` Wolfgang Schuster
2007-12-03 19:18   ` Hans Hagen
2007-12-03 19:32   ` Hans Hagen
2007-12-04 15:57     ` Wolfgang Schuster
2007-12-04 18:22       ` Peter Münster
2007-12-05  8:29         ` Wolfgang Schuster
2007-12-05 20:45           ` Peter Münster
2007-12-05 22:06             ` Hans Hagen
2007-12-06  8:26               ` Wolfgang Schuster [this message]
2007-12-06  9:53                 ` Hans Hagen
2007-12-06 14:45                   ` Aditya Mahajan

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=115224fb0712060026x7fa0049ahef2f413edcf9a304@mail.gmail.com \
    --to=schuster.wolfgang@googlemail.com \
    --cc=ntg-context@ntg.nl \
    /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).