On Dec 4, 2006, at 6:52 PM, Javier M˙gica de Rivera wrote: > b) The encoding axis, wich has turn to also be essential, although > it took a time to realise, I think. Aren't we all switching to Unicode? I believe in the past I'd advocated for a language / script pair, so the above is certainly a good reminder of this omission. > 1) We make a list of names of user-level commands representing > particular font features to be followed by any font that implements > them. For example, \outline, \condensed, \shaded, > \porportionalfigures, \trafficlike, Surely one could select these from the family / other axes I defined? (outline, shaded, trafficlike (what do you mean by that by-the-way? In a ``dangerous bend'' sign?) would go under family, proportionalfigures was a part of one of the things which I described) > \iranic, \novowels (This last for hebrew and others, if it makes > sense). Should be folded into language / script. > 2) We let those commands to be defined by the family. Therefore, > when the family is changed, Latex has to take the definitions for > the newly selected family. I dunno. I think it's better to have an option to have them be persistent _unless_ over-ridden. Say I'm typesetting a running head and introduce a bit of text in a ``code'' style. I'd liefer have the numbers be proportional oldstyle (say) to match the balance of the running head, while of course a standard code block would of course have monospaced figures (though lining or oldstyle would have to suit the balance of the design). William -- William Adams senior graphic designer Fry Communications This email message and any files transmitted with it contain information which is confidential and intended only for the addressee(s). If you are not the intended recipient(s), any usage, dissemination, disclosure, or action taken in reliance on it is prohibited. The reliability of this method of communication cannot be guaranteed. Email can be intercepted, corrupted, delayed, incompletely transmitted, virus-laden, or otherwise affected during transmission. Reasonable steps have been taken to reduce the risk of viruses, but we cannot accept liability for damage sustained as a result of this message. If you have received this message in error, please immediately delete it and all copies of it and notify the sender.