ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Philipp Gesang <gesang@stud.uni-heidelberg.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: disabling onum in url
Date: Sun, 2 Oct 2011 20:20:14 +0200	[thread overview]
Message-ID: <20111002182014.GB26009@aides> (raw)
In-Reply-To: <4E88A509.6010704@web.de>


[-- Attachment #1.1: Type: text/plain, Size: 1890 bytes --]

On 2011-10-02 19:53, Pablo Rodríguez wrote:
> On 10/02/2011 06:40 PM, Philipp Gesang wrote:
> > Well, in my previous example, rather use:
> > 
> >   \definefontfeature[url][onum=no,smcp=yes]
> > 
> > and come back with a complete example if it doesn’t help.
> 
> Philipp, I'm afraid it doesn't work. Sample file:

As I thought: the problem is rather with latin modern not having
small caps as font feature, so „\definefontfeature” will have
zero effect on the example. Your options are afaics: either pick
a font that has the smcp feature (\setupbodyfont[antykwa-poltawskiego]
for example) or rely on the “style” key of the interaction
setups:

·································································

\setupbodyfontenvironment[default][em=italic]
\setupinteraction[state=start,color=,style=\em,contrastcolor=,focus=standard]

\useURL[aurl][http://www.pragma-ade.com/download-1.htm]

\setupurl[style={\tf\sc}]
%%%                 ^^^ for the traditional method

\define[1]\href{%
  \begingroup
    \setupinteraction[style=\sc]% locally override the interaction style
    \goto{\hyphenatedurl{#1}}[url(#1)]%
  \endgroup%
}

\starttext

42 abcd
%%% With the internal command:
\from[aurl]
42 abcd
%%% Your way:
\href{0123456789abcdef}
42 abcd

\stoptext

·································································

> Imagine a whole book in one document. If you have more than 100 urls, it
> would be inconvenient to have to go to the document preamble and back to
> the body text only to add an url.

In this case, wouldn’t you prefer a bibliography?

Philipp

-- 
()  ascii ribbon campaign - against html e-mail
/\  www.asciiribbon.org   - against proprietary attachments

[-- Attachment #1.2: Type: application/pgp-signature, Size: 198 bytes --]

[-- Attachment #2: 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
___________________________________________________________________________________

  parent reply	other threads:[~2011-10-02 18:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-02 10:58 Pablo Rodríguez
2011-10-02 11:34 ` Philipp Gesang
2011-10-02 15:40   ` Pablo Rodríguez
2011-10-02 16:40     ` Philipp Gesang
2011-10-02 17:53       ` Pablo Rodríguez
2011-10-02 18:00         ` Wolfgang Schuster
2011-10-02 18:41           ` Pablo Rodríguez
2011-10-02 18:20         ` Philipp Gesang [this message]
2011-10-02 18:54           ` Pablo Rodríguez

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=20111002182014.GB26009@aides \
    --to=gesang@stud.uni-heidelberg.de \
    --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).