ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: typo or bug report in type-buy.tex
Date: Fri, 02 May 2008 09:07:22 +0200	[thread overview]
Message-ID: <481ABDAA.4000702@wxs.nl> (raw)
In-Reply-To: <20080501175226.02f33a88.schuster.wolfgang@googlemail.com>

Wolfgang Schuster wrote:
> On Thu, 01 May 2008 17:37:17 +0200
> Renaud AUBIN <aubin@nibua-r.org> wrote:
> 
>> Hi folks,
>>
>>  From line 199 to 206 :
>> \starttypescript [lucida,lucidabfm] [texnansi,ec,8r,uc]
>>     \definetypeface [lucida] [rm] [serif]       [lucida] [default] 
>> [encoding=\typescripttwo]
>>     \definetypeface [lucida] [ss] [sans]        [lucida] [default] 
>> [encoding=\typescripttwo]
>>     \definetypeface [lucida] [tt] [mono]        [lucida] [default] 
>> [encoding=\typescripttwo]
>>     \definetypeface [lucida] [hw] [handwriting] [lucida] [default] 
>> [encoding=\typescripttwo]
>>     \definetypeface [lucida] [cg] [calligraphy] [lucida] [default] 
>> [encoding=\typescripttwo]
>>     \loadmapfile [\typescriptthree-bh-lucida.map]
>> \stoptypescript
>>
>> I assume it should be :
>> \starttypescript [lucida,lucidabfm] [texnansi,ec,8r,uc]
>>     \definetypeface [lucida] [rm] [serif]       [lucida] [default] 
>> [encoding=\typescripttwo]
>>     \definetypeface [lucida] [ss] [sans]        [lucida] [default] 
>> [encoding=\typescripttwo]
>>     \definetypeface [lucida] [tt] [mono]        [lucida] [default] 
>> [encoding=\typescripttwo]
>>     \definetypeface [lucida] [hw] [handwriting] [lucida] [default] 
>> [encoding=\typescripttwo]
>>     \definetypeface [lucida] [cg] [calligraphy] [lucida] [default] 
>> [encoding=\typescripttwo]
>>     \loadmapfile [\typescripttwo-bh-lucida.map]
>> \stoptypescript
> 
> It makes also sense to replace \definetypeface [lucida] ... with
> \definetypeface [\typescriptone] ..., allows you to write
> 
> \usetypescript[lucidabfm]
> \setupbodyfont[lucidabfm]

ok


-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
      tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
                                              | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


      reply	other threads:[~2008-05-02  7:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-01 15:37 Renaud AUBIN
2008-05-01 15:52 ` Wolfgang Schuster
2008-05-02  7:07   ` Hans Hagen [this message]

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=481ABDAA.4000702@wxs.nl \
    --to=pragma@wxs.nl \
    --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).