ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Otared Kavian <otared@gmail.com>
Subject: Re: mkiv and Reverse list of abbreviations
Date: Tue, 31 Aug 2010 17:25:08 +0200	[thread overview]
Message-ID: <4C7D1ED4.1020005@wxs.nl> (raw)
In-Reply-To: <9755E97C-ADCB-4B88-ADB7-BC3E86CEC88F@gmail.com>

On 31-8-2010 4:41, Otared Kavian wrote:
> Hi everyone,
>
> I have three questions regarding the use of abbreviations in mkiv: it seems that there is a difference between the way in which mkii and mkiv treat the definitions of synonyms.
>
> If one considers the minimal example:
>
> % ----- begin abbrev-test.tex
>
> \definesynonyms[abbreviation][abbreviations][\infull][\inshort]
>
> \starttext
> \abbreviation{LCTVS}{Locally Convex Topological Vector Space}
> \abbreviation{EEG} {Electroencephalogram}
> \abbreviation{ERP} {Event-Related Potentials}
> \abbreviation{TVS}{Topological Vector Space}
>
> Test inshort: \inshort{EEG}, \inshort{ERP}, \inshort{TVS},
>
> Test infull: \infull{EEG}, \infull{ERP}, \infull{TVS}, \infull{LCTVS}
>
> \completelistofabbreviations
>
> \stoptext
> % ----- end abbrev-test.tex
>
> my questions are the following:
>
> 1) How can I tell mkiv that I want \infull{EEG} result in Electroencephalogram not in "ELECTROENCEPHALOGRAM"?
>
> 2) It seems that the order in which \infull and \inshort are defined in
> 	\definesynonyms[abbreviation][abbreviations][\infull][\inshort]
> is different in mkii and in mkiv: is this observation correct?

I need to check it (no time right now) as there is no reason for it not 
to be compatible

> 3) Is it possible to obtain, beside the list of abbreviations, another ordered list in which the full variant is in the first column while the short variant is in the second column? That is something like:
> 	\completeReverseListOfAbbreviations
> resulting in
>
> 	Electroencephalogram		EEG
> 	Event-Related Potentials		ERP
>
> 	Locally Convex Topological Vector Space		LCTVS
>
> 	Topological Vector Space		TVS
>
> Thanks in advance for any help or insight.

remind me to make it configureable (not that hard)

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
     tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
                                              | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


      reply	other threads:[~2010-08-31 15:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-31 14:41 Otared Kavian
2010-08-31 15:25 ` Hans Hagen [this message]

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=4C7D1ED4.1020005@wxs.nl \
    --to=pragma@wxs.nl \
    --cc=ntg-context@ntg.nl \
    --cc=otared@gmail.com \
    /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).