ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Idris Samawi Hamid <ishamid@colostate.edu>
Subject: Re: proposed convention for variation switching	[wasRE:inheriting ...
Date: Fri, 22 Apr 2005 11:13:29 -0600	[thread overview]
Message-ID: <opspm8srsju9mfh0@lamar.colostate.edu> (raw)
In-Reply-To: <20050422155519.17938@mail.comp.lancs.ac.uk>

On Fri, 22 Apr 2005 15:55:19 +0100, Adam Lindsay <atl@comp.lancs.ac.uk> 
wrote:

> Idris Samawi Hamid said this at Fri, 22 Apr 2005 08:36:02 -0600:
>
>> In any case whatever high-level framework we come up with should largely
>> be determined by your decision on the low/mid-level framework.
>
> See, I beg to differ.

I  agree with virtually everything u said, but _maybe_ u missed my 
point:-))

If Hans either implements

a) >2-char swutch support; or
b) \sizea(b)(c) etc,

it affects whether the high-level framework will need to use capital
2-char switches or have the option of using unrestricted lower-case 
switches
in whatever framework we agree on. Your point is on the framework being 
_mentioned_,
mine was on the language _used_ to mention the framework (perhaps I should 
have made
that clearer). The logic of the framework used should be largely 
independent,
but the language we use to mention it partly depends on the internal 
implementation.

I look forward to our final consensus!

Best
Idris
-- 
Professor Idris Samawi Hamid
Department of Philosophy
Colorado State University
Fort Collins, CO 80523

  reply	other threads:[~2005-04-22 17:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-21 18:36 Idris Samawi Hamid
2005-04-21 19:56 ` Adam Lindsay
2005-04-21 22:43   ` Vit Zyka
2005-04-21 23:00     ` Adam Lindsay
2005-04-22  8:16   ` Hans Hagen
2005-04-22  9:38     ` Vit Zyka
2005-04-22 14:36     ` Idris Samawi Hamid
2005-04-22 14:55       ` Adam Lindsay
2005-04-22 17:13         ` Idris Samawi Hamid [this message]
2005-04-21 19:59 ` Adam Lindsay
2005-04-21 23:53 Idris Samawi Hamid
2005-04-22  8:45 ` Vit Zyka
2005-04-22  9:03   ` Taco Hoekwater

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=opspm8srsju9mfh0@lamar.colostate.edu \
    --to=ishamid@colostate.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).