ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Rik <rik@panix.com>
To: ntg-context@ntg.nl
Subject: Re: Slanted, double-quoted quotations
Date: Wed, 15 Oct 2014 21:14:24 -0400	[thread overview]
Message-ID: <543F1BF0.3030804@panix.com> (raw)
In-Reply-To: <E2E94C2C-279C-4959-9924-B29E54A7675A@gmail.com>

On 2014-10-15 17:06, Wolfgang Schuster wrote:
> Am 15.10.2014 um 21:03 schrieb Rik Kabel <context@rik.users.panix.com>:
>
>> I am not sure I understand the need for symstyle and symcolor. The issue is not that the symbols are not styled/colored, but that they do not appear at all when a non-normal style is specified. What I see with the example I posted is:
>> <hacaddjd.png>
>> and I assume that Sander saw a similar issue.
>>
>> Note that there are no square brackets present as defined for layer 2.
>>
>> I realize that style=normal for level 3 should perhaps be style=\tf, since normal is redefined to slanted within the scope of layer 2. With that change to my example, I get
>> <fageaehi.png>
>> This still has the lack of square brackets, and now in addition lacks curly braces for level 3.
>>
>> If your fix is meant to repair that, all is well. If not, could you explain why “it's deliberate and has always been the case in mkiv”?
> When you use “location=text” context checks the value of the style key, when the value of the key is “normal”
> the left and right arguments are used but when you use a different value (e.g. slanted) context applies only
> the style and color values.
>

Thank you, Wolfgang, for that explanation of what is being done.

Can you explain why this is done? It would seem, given the name of the 
command, that the delimiter is more important than the styling, and so I 
suspect that there is some historical reason that this behavior was 
chosen. Styling can be done within the text, as can delimiters, but the 
benefit of the command is that it should be able to manage multiple 
levels automatically.

-- 
Rik Kabel
___________________________________________________________________________________
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-10-16  1:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-15 13:06 Sander Maijers
2014-10-15 14:58 ` Rik Kabel
2014-10-15 17:38   ` Hans Hagen
2014-10-15 19:03     ` Rik Kabel
2014-10-15 21:06       ` Wolfgang Schuster
2014-10-16  1:14         ` Rik [this message]
2014-10-20 14:08           ` Sander Maijers
2014-10-20 15:42             ` Rik
2014-10-21  7:50               ` Sander Maijers

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=543F1BF0.3030804@panix.com \
    --to=rik@panix.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).