ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Jano Kula <jano.kula@tiscali.cz>
Subject: Re: mark ii/iv
Date: Wed, 22 Nov 2006 19:29:11 +0100	[thread overview]
Message-ID: <ek24qh$1dv$1@sea.gmane.org> (raw)
In-Reply-To: <4564732A.2080605@wxs.nl>


>> After reading the document I still miss the good term for this level of 
>> versioning ("kind of version tag") to distiguish it from "usual" ConTeXt 
>> versioning.
>>
>> Hans H., how do you want these versioning systems to be called?
>>
>> ? [date version] = ConTeXt  ver: 2006.10.27 15:16
>> ? [mark version] = MK II
>>   
> the mk versioning is only relevant for engines, i.e. mkiv will provide lua based implementations as well as in the future more functionality. 
> 
> pdftex / xetex : mkii
> luatex         : mkiv 
> 
> in some sense, mkiv is a next generation context but downward compatible 

thanks, made it clearer: not level of versioning, but axis of versioning.

but still, how do we call it? mk version? and how we call the "usual" 
version then? i want to avoid confusion when speaking about version. 
guess which one ;)

there is already a command \markversion, but it doesn't seem to have 
something in common with this versioning.

jano

  reply	other threads:[~2006-11-22 18:29 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-21 19:31 Hans van der Meer
2006-11-21 19:39 ` Jelle Huisman
2006-11-21 19:43 ` Hans Hagen
2006-11-21 21:13   ` andrea valle
2006-11-21 21:27     ` Jelle Huisman
2006-11-21 20:20 ` Wolfgang Schuster
2006-11-22 14:43   ` Jano Kula
2006-11-22 15:56     ` Hans Hagen
2006-11-22 18:29       ` Jano Kula [this message]
2006-11-22 21:43         ` Hans Hagen
2006-11-21 20:20 ` Wolfgang Schuster
2006-11-22 16:42 ` Mojca Miklavec
2006-11-22 21:55   ` Hans Hagen
2006-11-23  2:43     ` Mojca Miklavec
2006-11-23  8:54       ` Taco Hoekwater
2006-11-23  9:43       ` Hans Hagen

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='ek24qh$1dv$1@sea.gmane.org' \
    --to=jano.kula@tiscali.cz \
    --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).