ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Jonas Stein <news@jonasstein.de>
To: ntg-context@ntg.nl
Subject: Re: list of all (even unused) abbreviations
Date: Sat, 4 Dec 2010 02:43:11 +0100	[thread overview]
Message-ID: <fuios7-l9a.ln1@news.jonasstein.de> (raw)
In-Reply-To: <0A13C2E3-E213-40C1-93B9-3A654D974E97@gmail.com>

>> \definesynonyms[abbreviation][abbreviations][\infull]
>> in Description on [1]
>> 
>> Should i delete the "[\infull]" there? It works fine without it.
>
> Provide a example where it doesn’t work, the \infull is to get
> the full text of the abbreviation in your text, e.g. \infull{VVV}.

in the wiki is an example:
http://wiki.contextgarden.net/Reference/en/definesynonyms

i think "[\infull]" in line 
\definesynonyms[abbreviation][abbreviations][\infull]
is not necessary as it works in the example fine without it.

Kind regards,

-- 
Jonas Stein <news@jonasstein.de>

___________________________________________________________________________________
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-12-04  1:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-29 19:33 Jonas Stein
2010-11-29 19:58 ` Wolfgang Schuster
2010-11-29 20:23   ` Jonas Stein
2010-11-30 20:21     ` Wolfgang Schuster
2010-12-01 19:58       ` Jonas Stein
2010-12-01 20:04         ` Wolfgang Schuster
2010-12-02  1:52           ` Jonas Stein
2010-12-02 13:47             ` Wolfgang Schuster
2010-12-04  1:43               ` Jonas Stein [this message]
2010-12-04 14:38                 ` Wolfgang Schuster

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=fuios7-l9a.ln1@news.jonasstein.de \
    --to=news@jonasstein.de \
    --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).