ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Sanjoy Mahajan <sanjoy@mrao.cam.ac.uk>
Subject: Re: unic-xxx.tex glyph lists: minor bugs, questions
Date: Wed, 22 Nov 2006 23:54:01 +0000	[thread overview]
Message-ID: <E1Gn1uj-0002xQ-00@skye.ra.phy.cam.ac.uk> (raw)
In-Reply-To: Your message of "Thu, 16 Nov 2006 17:20:26 +0100." <455C8FCA.30109@wxs.nl>

>> I'll experiment, especially if I can figure out a set of magic
>> kpathsea paths to keep mkii and mkiv in parallel.

> no need for that ; it is made to run in parallel, just an extra zip
> with mkiv and lua files ending up in base, and luatools.lua ending
> up in the script path; also, mkiv does not use kpse -)

Great.  When the mkiv zip is available, I'll try it (tried poking
around the pragma site but didn't find it).  No kpse is indeed good
news!

About backward compatability, maybe the mkiv transition is the time to
sacrifice backward compatability in a few instances where it makes the
code or user interface simpler?  One example off the top of my head is
\setuppapersize[ABC] becoming equivalent to \setuppapersize[ABC][ABC]
(rather than to \setuppapersize[ABC][A4]), and there are no doubt
others.  Or is the (understandable) policy of ConTeXt development that
backward compatability is paramount?

-Sanjoy

`Never underestimate the evil of which men of power are capable.'
         --Bertrand Russell, _War Crimes in Vietnam_, chapter 1.

  reply	other threads:[~2006-11-22 23:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-05  1:24 Philipp Reichmuth
2006-11-05 14:27 ` Hans Hagen
2006-11-06 22:56   ` Philipp Reichmuth
2006-11-09 16:51   ` Mojca Miklavec
2006-11-09 16:56     ` Mojca Miklavec
2006-11-14 11:35       ` Hans Hagen
2006-11-14 11:42     ` Hans Hagen
2006-11-16 10:49       ` Philipp Reichmuth
2006-11-16 13:12       ` Sanjoy Mahajan
2006-11-16 16:20         ` Hans Hagen
2006-11-22 23:54           ` Sanjoy Mahajan [this message]
2006-11-23  9:56             ` 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=E1Gn1uj-0002xQ-00@skye.ra.phy.cam.ac.uk \
    --to=sanjoy@mrao.cam.ac.uk \
    --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).