ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Procházka Lukáš Ing. - Pontex s. r. o." <LPr@pontex.cz>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: \os
Date: Sat, 02 Aug 2014 10:51:48 +0200	[thread overview]
Message-ID: <op.xjyiwm0ftpjj8f@lpr> (raw)
In-Reply-To: <9891CD4C-1BE2-4F7F-8FFF-BAD0E3D88CD6@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1287 bytes --]

Hello,

my case may be a bit more complicated;
it uses an environment file which uses \os in it.

So let's have:

----
\definefontfeature[default][default][onum=no,lnum=yes]

% In fact, in a separate environment file >>
\setupbodyfont[palatino,11pt]
\os
% In fact, in a separate environment file <<

\definefontfeature[default][default][onum=no,lnum=yes]

\starttext
   A:123

   \os
   B:123

   \definefontfeature[default][default][onum=no,lnum=yes]
   C:123
\stoptext
----

So I'd expect (or I'd like to achieve) lining numbers at least in "C:123" (but also in "A:123"; and in page numbers),
but I'm getting old-style numbers at all three cases ("A:123", "B:123" and "C:123").

IOW, I need to suppress the \os feature of the environment file, no matter whether just before or just after it has been included.

Ho to do it?

Lukas


> Below is a example with one of my own fonts which use old style numbers by default.
>
> \definefontfeature[default][default][lnum=yes]
>
> \setupbodyfont[calluna]
>
> \starttext
> 0123456789
> \stoptext


-- 
Ing. Lukáš Procházka [mailto:LPr@pontex.cz]
Pontex s. r. o.      [mailto:pontex@pontex.cz] [http://www.pontex.cz]
Bezová 1658
147 14 Praha 4

Tel: +420 241 096 751
Fax: +420 244 461 038

[-- Attachment #2: t.mkiv --]
[-- Type: application/octet-stream, Size: 365 bytes --]

\definefontfeature[default][default][onum=no,lnum=yes]

% In fact, in a separate environment file >>
\setupbodyfont[palatino,11pt]
\os
% In fact, in a separate environment file <<

\definefontfeature[default][default][onum=no,lnum=yes]

\starttext
  A:123

  \os
  B:123

  \definefontfeature[default][default][onum=no,lnum=yes]
  C:123
\stoptext

[-- Attachment #3: t.pdf --]
[-- Type: application/pdf, Size: 5361 bytes --]

[-- Attachment #4: Type: text/plain, Size: 485 bytes --]

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

  reply	other threads:[~2014-08-02  8:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-01 16:39 \os Procházka Lukáš Ing. - Pontex s. r. o.
2014-08-01 16:51 ` \os Wolfgang Schuster
2014-08-02  8:51   ` Procházka Lukáš Ing. - Pontex s. r. o. [this message]
2014-08-02 17:07     ` \os Wolfgang Schuster
2014-08-02 20:36       ` \os Procházka Lukáš
2014-08-03 17:26         ` \os Joshua Krämer
2014-08-03 18:48         ` \os Wolfgang Schuster
2014-08-03 21:10           ` \os Procházka Lukáš

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=op.xjyiwm0ftpjj8f@lpr \
    --to=lpr@pontex.cz \
    --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).