ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "dr. Hans van der Meer" <havdmeer@ziggo.nl>
To: NTG ConTeXt <ntg-context@ntg.nl>
Subject: Re: smallcaps
Date: Wed, 29 Jun 2016 12:39:46 +0200	[thread overview]
Message-ID: <BFB76720-F492-46A0-B9F2-280AF0A3D01E@ziggo.nl> (raw)
In-Reply-To: <77161DD2-3975-4170-A7AF-1E10E1C265F7@ziggo.nl>


> On 29 Jun 2016, at 10:05, dr. Hans van der Meer <havdmeer@ziggo.nl> wrote:
> 
> I do not understand the behaviour of the \sc macro. I thought smallcaps would turn out to be smaller than capitals. But I see no difference between them except a subtle difference in letterspacing. Am I doing something wrong here?
> 
> Hans van der Meer
> 

The above issue being solved, I guess there is something else in my setup not being as it should be.
Because the code:

\starttext
\setupbodyfont[lucidaot]
{\sc abc}
\stoptext

Does give me abc in smallcaps, but placing the \setupbodyfont before the \starttext surprisingly does not.

\setupbodyfont[lucidaot]
\starttext
{\sc abc}
\stoptext

Changing the lucidaot call for cambria or lmodern gives the expected coorect behaviour.
So I guess there is something amiss with how I did setup the lucida font in my system.
I bought the lucida opentype font and installed my TeX trees as follows. The split between the ConTeXt directory and the one for my local files facilitates downloading new beta versions.

~home\TeX\texmf\
  fonts
    opentype
      bh
        lucidaot
          LucidaBlackletterOT.otf .. LucidaSansTypewriterOT.otf
  tex
    context
      user (my own modules)

~home\Applications\TeX-programs\
    context
      tex
        link to the above texmf
        further as downloaded from the beta

Strange thing furthermore is that changing the name of the lucidaot-directory in the texmf-tree does not seem to make any difference, not in any case when I execute "mtxrun --script font --reload --force" and afterwards "mtxrun --script context --make".

So I guess there are some things I did not right. Can that be spotted from the information given here?

Hans van der Meer


 

___________________________________________________________________________________
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
___________________________________________________________________________________

  parent reply	other threads:[~2016-06-29 10:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-29  8:05 smallcaps dr. Hans van der Meer
2016-06-29  8:29 ` smallcaps Mikael P. Sundqvist
2016-06-29  9:00 ` smallcaps Wolfgang Schuster
2016-06-29  9:26   ` smallcaps Meer, Hans van der
2016-06-29 11:09     ` smallcaps Wolfgang Schuster
2016-06-29 10:39 ` dr. Hans van der Meer [this message]
2016-06-29 10:55   ` smallcaps Wolfgang Schuster
2016-06-29 11:00 ` smallcaps Alan Bowen

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=BFB76720-F492-46A0-B9F2-280AF0A3D01E@ziggo.nl \
    --to=havdmeer@ziggo.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).