Re: [NTG-context] proposed convention for variation switching [wasRE:inheriting ...

2005-04-22 Thread Adam Lindsay
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. Whatever high-level framework(s) we come up with should largely be *in

Re: [NTG-context] proposed convention for variation switching [wasRE:inheriting ...

2005-04-22 Thread Idris Samawi Hamid
On Fri, 22 Apr 2005 15:55:19 +0100, Adam Lindsay <[EMAIL PROTECTED]> 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

Re: [NTG-context] proposed convention for variation switching [wasRE:inheriting ...

2005-04-22 Thread Idris Samawi Hamid
Hi Hans, On Fri, 22 Apr 2005 10:16:47 +0200, Hans Hagen <[EMAIL PROTECTED]> wrote: i'm not that much in favour of capitalized named (clashes with user commands as well as some internals), so \scbf is more likely Heh, heh, that was my original idea; with 2-char capitals I was trying to find a way

Re: [NTG-context] proposed convention for variation switching [wasRE:inheriting ...

2005-04-22 Thread Hans Hagen
Adam Lindsay wrote: Hi Idris, I've brought the subject up repeatedly on the list, and got not a lot of response. I have to think that 1) people are happy with the standard 7 font styles, 2) people have their own hand-rolled solution (like yourself, myself or Vit--see his Storm fonts support for som

Re: [NTG-context] proposed convention for variation switching [wasRE:inheriting ...

2005-04-22 Thread Taco Hoekwater
Hi, What about: light \lf medium \mf if medium is \tf (as it is now), semibold \sf bold \bf lightitalic \li italic \it then italic could be \ti, and all four would be consistent: (l|t|s|b)(t|i) (but I may have missed some reason why this will not work) Greetings, Taco semibold italic \si bold ita

Re: [NTG-context] proposed convention for variation switching [wasRE:inheriting ...

2005-04-22 Thread Vit Zyka
also, whatever system we cook up ... there are so many bold variants nowadays in some fonts ... in practice one will not mix semi bold and bold in a running text, so again, this can be done by typefaces as well: \definetypeface[normalface] [...] \definetypeface[bolderface] [...] \definetypeface[

Re: [NTG-context] proposed convention for variation switching [wasRE:inheriting ...

2005-04-22 Thread Vit Zyka
Idris Samawi Hamid wrote: > Let's keep \sc. After all, ConTeXt already contains many redundancies (and that's a good thing imho->) Yes. (I think that \Var[up] (for upright figures) is more intuituve that \Var[ns]), at least in English:-))) I agree, both Adams's \Var[lf] and Idris's \Var[up] is be

RE: [NTG-context] proposed convention for variation switching [wasRE:inheriting ...

2005-04-21 Thread Idris Samawi Hamid
>= Original Message From Vit Zyka <[EMAIL PROTECTED]> = >Adam Lindsay wrote: >> >> It's not that I'm trying to rain on your parade, it's just that I've lost >> a bit of enthusiasm for standardisation. ok, but this is my take: although I can find workarounds that work for me, next month ot

Re: [NTG-context] proposed convention for variation switching [wasRE:inheriting ...

2005-04-21 Thread Adam Lindsay
Vit Zyka said this at Fri, 22 Apr 2005 00:43:06 +0200: >A) for extended glyph definitions and old style digits {Var[os]} (if >they are not default in the font - in that case there might be reverse >normal style digit variant \Var[ns?]). I'm used to them being called lf: lining figures. But othe

Re: [NTG-context] proposed convention for variation switching [wasRE:inheriting ...

2005-04-21 Thread Vit Zyka
Adam Lindsay wrote: It's not that I'm trying to rain on your parade, it's just that I've lost a bit of enthusiasm for standardisation. I generally agree with Adam, fonts are very varios. But the next Idris idea is nice. More intuitive then \sc, \bc, \ic, and \bic. I would vote for it, but ... at

Re: [NTG-context] proposed convention for variation switching [wasRE:inheriting ...

2005-04-21 Thread Adam Lindsay
Idris Samawi Hamid said this at Thu, 21 Apr 2005 12:36:55 -0600: >Hmm, I was a little worried at first about >2-char switches at first, till I >noticed that type-siz.tex uses some four-letter switches as well, e.g. > >line-575== > \definebodyfont [12pt] [mm] >[mrbf=xc

Re: [NTG-context] proposed convention for variation switching [wasRE:inheriting ...

2005-04-21 Thread Adam Lindsay
Hi Idris, I've brought the subject up repeatedly on the list, and got not a lot of response. I have to think that 1) people are happy with the standard 7 font styles, 2) people have their own hand-rolled solution (like yourself, myself or Vit--see his Storm fonts support for some nice ideas), or 3

Re:[NTG-context] proposed convention for variation switching [wasRE:inheriting ...

2005-04-21 Thread Idris Samawi Hamid
>On this basis, here is my suggestion for an official ConTeXt convention for >professional fonts: I forgot to mention one of the most important advantages of implementing an official ConTeXt standard (aside from inheritance): There will be no need to define \*a--\*d, \*x, and \*xx in user-define

[NTG-context] proposed convention for variation switching [wasRE:inheriting ...

2005-04-21 Thread Idris Samawi Hamid
>= Original Message From "Adam Lindsay" <[EMAIL PROTECTED]> = >I don't have time to really delve into the implementation details, but it >looks like the difference is that ConTeXt isn't so responsive with user- >defined alternatives with more than two characters. Compare the stripped >down