ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Using forms and saving values
Date: Tue, 5 Apr 2011 14:23:48 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LNX.2.01.1104051418540.1259@ybpnyubfg.ybpnyqbznva> (raw)
In-Reply-To: <EB64E4D0-4455-4F8C-9619-5BAAD4D034C8@googlemail.com>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 857 bytes --]

On Tue, 5 Apr 2011, Wolfgang Schuster wrote:

>
> Am 05.04.2011 um 18:49 schrieb Peter Münster:
>
>> Wolfgang Schuster <schuster.wolfgang@googlemail.com> writes:
>>
>>> No, “mkvi” is a valid file extension for MkIV. The difference between
>>> a mkiv and a mkvi file is that you can use named parameters, e.g.
>>
>> Hello,
>>
>> Why mkvi and not mkv ?
>
> I guess because mkvi has four letters like mkii and mkiv but mkv ha only three.

So the next versions will be mkix, mkxi, mkxv, mkxx, mkxl, mkli, mklv, and 
mkxc. It is gonig to get confusing real soon :)

BTW, does anyone has a minimal example on how to use mkvi syntax. I tried 
a few examples, but the best that I could do was using one of the mtx-* 
scripts to convert mkvi to tex (And that conversion does not work for 
\starttextdefinition ... \stoptexdefinition).

Aditya

[-- Attachment #2: Type: text/plain, Size: 485 bytes --]

___________________________________________________________________________________
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:[~2011-04-05 18:23 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-03 11:00 Cecil Westerhof
2011-04-04 18:29 ` Wolfgang Schuster
2011-04-04 21:01   ` Cecil Westerhof
2011-04-05  1:19   ` Cecil Westerhof
2011-04-05  7:45     ` Peter Rolf
2011-04-05 10:31       ` Cecil Westerhof
2011-04-05 10:50         ` Peter Rolf
2011-04-05 12:06           ` Cecil Westerhof
2011-04-05 12:41             ` Peter Rolf
     [not found]               ` <4D9B14C3.8040707@wxs.nl>
2011-04-05 13:38                 ` Peter Rolf
2011-04-05 13:42                   ` Cecil Westerhof
2011-04-05 13:54                     ` Peter Rolf
2011-04-05 15:26                       ` Wolfgang Schuster
2011-04-05 13:39               ` Cecil Westerhof
2011-04-05 13:45                 ` Wolfgang Schuster
2011-04-05 16:49                   ` Peter Münster
2011-04-05 16:56                     ` Wolfgang Schuster
2011-04-05 18:23                       ` Aditya Mahajan [this message]
2011-04-05 18:32                         ` Wolfgang Schuster
2011-04-05 17:52                     ` Martin Schröder
2011-04-05 13:48     ` Peter Münster
2011-04-05 13:53       ` Cecil Westerhof
2011-04-05 14:03         ` Aditya Mahajan
2011-04-05 14:31           ` Cecil Westerhof

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=alpine.LNX.2.01.1104051418540.1259@ybpnyubfg.ybpnyqbznva \
    --to=adityam@umich.edu \
    --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).