ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: \definehighlight + \words | \WORDS
Date: Tue, 8 May 2012 13:28:21 +0200	[thread overview]
Message-ID: <0B04301B-300B-45AF-BC64-77522A908BA1@googlemail.com> (raw)
In-Reply-To: <4FA900CF.1090406@wxs.nl>


Am 08.05.2012 um 13:17 schrieb Hans Hagen:

> On 8-5-2012 11:18, Philipp Gesang wrote:
>> On 2012-05-08 11:07, Wolfgang Schuster wrote:
>>> 
>>> Am 08.05.2012 um 10:35 schrieb Philipp Gesang:
>>> 
>>>> Dear listmates,
>>>> 
>>>> I rely on automated uppercasing and lowercasing a lot and I’m
>>>> very happy with the \words and \WORD macros. But I can’t find a
>>>> way to properly combine them with the “style” parameter of
>>>> highlights: it breaks frames and enumerations. Example:
>>>> 
>>>> ········································································
>>>> 
>>>> \definehighlight [tolower] [style=\words,]  %%% This is problematic.
>>>> \def\mylower#1{\bgroup\words#1\egroup}      %%% The command itself
>>>>                                            %%% works, though.
>>>> 
>>>> \starttext
>>>> 
>>>> FOO \tolower{FOO} FOO\par         %%% Works.
>>>> \framed{BAR \mylower{BAR} BAR}    %%% Works.
>>>> \framed{BAR \tolower{BAR} BAR}    %%% Fails.
>>>> \startitemize                     %%% Enumerations don’t work either.
>>>>  \item FOO \mylower{FOO} FOO     %%% Works.
>>>>  \item FOO \tolower{FOO} FOO     %%% Fails.
>>>> \stopitemize
>>>> 
>>>> \stoptext
>>>> 
>>>> ········································································
>>>> 
>>>> In short: while I can always wrap it in a \def, the more elegant
>>>> doesn’t work in all cases. Is there anything wrong with my
>>>> approach?
>>> 
>>> You can use
>>> 
>>>   \definehighlight [tolower] [style={\setcharactercasing[2]}]
>>> 
>>> to create the \tolower command.
>> 
>> Perfect, thanks a lot. So it was caused by the \groupedcommand in
>> the definition of \word.
> 
> The next version will support named casing:
> 
> WORD
> word
> Word
> Words
> capitals cap
> Capitals Cap
> none
> random

It would be also useful to change the following line in font-pre.mkiv to use \setcharacterchasing instead of \WORD (won’t work anymore when you remove \groupedcommand from the \WORD as written in the comments in typo-cap.mkiv)

\definealternativestyle [\v!WORD]           [\WORD]        [\WORD]

Additional entries for \word, Words etc. in font-pre.mkvi are useful as well because “style=word” looks better than “style={\setcharacterchasing[word]}”.

Wolfgang
___________________________________________________________________________________
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:[~2012-05-08 11:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-08  8:35 Philipp Gesang
2012-05-08  9:07 ` Wolfgang Schuster
2012-05-08  9:18   ` Philipp Gesang
2012-05-08 11:17     ` Hans Hagen
2012-05-08 11:28       ` Wolfgang Schuster [this message]
2012-05-08 11:44         ` Philipp Gesang
2012-05-08 11:47         ` Hans Hagen

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=0B04301B-300B-45AF-BC64-77522A908BA1@googlemail.com \
    --to=schuster.wolfgang@googlemail.com \
    --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).