From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/57186 Path: news.gmane.org!not-for-mail From: Michael Saunders Newsgroups: gmane.comp.tex.context Subject: typescripts Date: Wed, 17 Mar 2010 07:16:26 -0500 Message-ID: <54d7f5601003170516q76f5d740w1c789c31c2903b4@mail.gmail.com> Reply-To: mailing list for ConTeXt users NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Trace: dough.gmane.org 1268828816 27196 80.91.229.12 (17 Mar 2010 12:26:56 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Wed, 17 Mar 2010 12:26:56 +0000 (UTC) To: ntg-context@ntg.nl Original-X-From: ntg-context-bounces@ntg.nl Wed Mar 17 13:26:52 2010 Return-path: Envelope-to: gctc-ntg-context-518@m.gmane.org Original-Received: from balder.ntg.nl ([195.12.62.10]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1NrsKn-0002aH-VU for gctc-ntg-context-518@m.gmane.org; Wed, 17 Mar 2010 13:26:50 +0100 Original-Received: from localhost (localhost [127.0.0.1]) by balder.ntg.nl (Postfix) with ESMTP id 95756C9D52; Wed, 17 Mar 2010 13:26:41 +0100 (CET) X-Virus-Scanned: Debian amavisd-new at balder.ntg.nl Original-Received: from balder.ntg.nl ([127.0.0.1]) by localhost (balder.ntg.nl [127.0.0.1]) (amavisd-new, port 10024) with LMTP id abgenpIzH6gD; Wed, 17 Mar 2010 13:26:36 +0100 (CET) Original-Received: from balder.ntg.nl (localhost [127.0.0.1]) by balder.ntg.nl (Postfix) with ESMTP id 4CE9EC9D54; Wed, 17 Mar 2010 13:25:01 +0100 (CET) Original-Received: from localhost (localhost [127.0.0.1]) by balder.ntg.nl (Postfix) with ESMTP id 99DD8C9D54 for ; Wed, 17 Mar 2010 13:24:53 +0100 (CET) X-Virus-Scanned: Debian amavisd-new at balder.ntg.nl Original-Received: from balder.ntg.nl ([127.0.0.1]) by localhost (balder.ntg.nl [127.0.0.1]) (amavisd-new, port 10024) with LMTP id Ttgl4ejC-4E6 for ; Wed, 17 Mar 2010 13:24:40 +0100 (CET) Original-Received: from mail-yw0-f199.google.com (mail-yw0-f199.google.com [209.85.211.199]) by balder.ntg.nl (Postfix) with ESMTP id A8078C9BE2 for ; Wed, 17 Mar 2010 13:16:27 +0100 (CET) Original-Received: by ywh37 with SMTP id 37so457196ywh.2 for ; Wed, 17 Mar 2010 05:16:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=TdZVv0xBdrRXqVj5LdfHe4bHy1cuSVGa7rBVvL3sw94=; b=KtdsXiIldtMpyDrB2YVRI7pRsYndIXvwbCp9hDloiPAH2+j6iGhalaQVRK92g43rsM iTdYjcRFACGkEjfZpJyYoTtMyXT/7M/b7oFgqe/3KlpoJFsf2vFt0R/qL7CAeSSCC46I 1dEa0QAgJO6Y9CogX8c8KK4nRMTcPRIOuxJbA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=Ks83PQJHeG9Ia0wQApRq1eNwjvypJ5pCuMlYLHDwgTExFAAcB1nCAmC9jzAfLGs0W5 qOnOZmKL/z/NVbchQsK4jKcAPXs5zDWT04o9pnpvCZLQSq6LavfMy8S5mj5NMJ0kgLuS cAgWeB+bdOtLRMxcxsWjdgRpDGoMFqx5HT7fQ= Original-Received: by 10.101.155.19 with SMTP id h19mr974590ano.43.1268828186721; Wed, 17 Mar 2010 05:16:26 -0700 (PDT) X-BeenThere: ntg-context@ntg.nl X-Mailman-Version: 2.1.12 Precedence: list List-Id: mailing list for ConTeXt users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: ntg-context-bounces@ntg.nl Errors-To: ntg-context-bounces@ntg.nl Xref: news.gmane.org gmane.comp.tex.context:57186 Archived-At: Wolfgang Schuster: > You can apply only *one* feature to \definefontfeatures. I've seen examples like this: \definefontfeature [fea] [mode=node,language=dflt,script=arab, init=yes,medi=yes,fina=yes,isol=yes, liga=yes,dlig=yes,rlig=yes,tlig=yes, calt=yes,trep=yes,mark=yes,mkmk=yes, kern=yes,curs=yes] so I think you mean to say that I can apply only one feature to \definefontsynonym or to \definetypeface. I tried this and it checks out. Thanks---it's nice to see hz working. Protrusion is only on the right margin? > > 2. As far as I can tell from trying to decode examples, there is some > > hidden connection between the first arguments of the second typescript > > block and the font switches. So, for example, a secret connection > > between SerifBoldItalic and \bi seems to connect Junicode-BoldItalic > > to \bi. Fine, but, in all the examples I've seen, there are no more > > than two weights and no widths. In some cases, I have five weights > > (light, book, medium, semi-bold, bold). How do I set up the > > typescript for this and the switches in the text? Must I learn more > > pairs like (SerifBoldItalic, \bi)? You need more typefaces. One for light, another one for condensed etc. ------------------------------ Mojca Miklavec: >> Must I learn more pairs like (SerifBoldItalic, \bi)? > Yes, but there are not many (tf, it, sl, bf, bi, bs, sc) and I assume > that they are extensible. See also below. > > You need more typefaces. One for light, another one for condensed etc. > Maybe I'm wrong, but shouldn't it be possible (I didn't test) to > modify font-unk.mkiv and add a few extra definitions to the following? > (Maybe not modify font-unk itself, but just adding a couple of more > definitons to the typescript.) > > \definebodyfont [default] [rm] > [tf=Serif sa 1, > bf=SerifBold sa 1, > it=SerifItalic sa 1, > sl=SerifSlanted sa 1, > bi=SerifBoldItalic sa 1, > bs=SerifBoldSlanted sa 1, > sc=SerifCaps sa 1] > > You could add your > in=SerifYourFontVariantName sa 1, > bd=SerifYourOtherFontVariantName sa 1, > > And then > \definefontsynonym[SerifYourFontVariantName][YourFontName] > It's true that most people don't do that, but I see no reason for not > extending the model for your particular needs. Mojca ------------------------------ Wolfgang Schuster: > The last time i did this you needed for MkIV also > > \definefontalternative[in] > \definefontalternative[bd] > > but be carefull with the shortcuts, \in is already used (references). Thank you both. I want to begin experimenting with this, but there's one thing that still confuses me. If I have a font with say, forty different combinations of weight/width/shape (5x4x2), I will need to come up with forty different pairs like: myNewFontSwitch=SerifMyFontVariantName sa 1, a strain on the poetic imagination, but possible. It would be nicer though, if I could change weight/width/shape independently of each other (then I need have only 5+4+2 switches). For example, when I see something like: \rm\tf roman \it italic \bf bold resulting in: , it's surprising to see that \bf has turned off the italic---you don't expect a switch of the weight to have a hidden switch of the shape in it. Could the typescript be set up with fewer switches, so that: \rm\tf roman \it italic \bf bold would result in: , or, e.g., \rm\tf (regular book roman) \cd (condensed) \it (italic) \bf (bold) would result in: ? (Also, I'm hoping that having a dozen different sets of font features won't require twelve times as many switches and feature names as this. I think there is some easier method for switching---Hans mentioned \addff{}, but I can't find anything in the docs. If that works, that would make two kinds of switches, one for some kinds of features and another for other kinds.) ___________________________________________________________________________________ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___________________________________________________________________________________