From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/89018 Path: news.gmane.org!not-for-mail From: Sander Maijers Newsgroups: gmane.comp.tex.context Subject: Re: Slanted, double-quoted quotations Date: Mon, 20 Oct 2014 16:08:01 +0200 Message-ID: References: <543E8B97.4070803@rik.users.panix.com> <543EB117.4010105@wxs.nl> <543EC4E5.8050605@rik.users.panix.com> <543F1BF0.3030804@panix.com> Reply-To: mailing list for ConTeXt users NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1487242144==" X-Trace: ger.gmane.org 1413814157 23225 80.91.229.3 (20 Oct 2014 14:09:17 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 20 Oct 2014 14:09:17 +0000 (UTC) To: mailing list for ConTeXt users Original-X-From: ntg-context-bounces@ntg.nl Mon Oct 20 16:09:13 2014 Return-path: Envelope-to: gctc-ntg-context-518@m.gmane.org Original-Received: from balder.ntg.nl ([5.39.185.229]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1XgDds-0002WS-5X for gctc-ntg-context-518@m.gmane.org; Mon, 20 Oct 2014 16:09:00 +0200 Original-Received: from localhost (localhost [127.0.0.1]) by balder.ntg.nl (Postfix) with ESMTP id 9F4951023D for ; Mon, 20 Oct 2014 16:08:57 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at balder.ntg.nl Original-Received: from balder.ntg.nl ([127.0.0.1]) by localhost (balder.ntg.nl [127.0.0.1]) (amavisd-new, port 10024) with LMTP id k6SIUeM0n8e1 for ; Mon, 20 Oct 2014 16:08:56 +0200 (CEST) Original-Received: from balder.ntg.nl (localhost [IPv6:::1]) by balder.ntg.nl (Postfix) with ESMTP id 65F071020C for ; Mon, 20 Oct 2014 16:08:14 +0200 (CEST) Original-Received: from localhost (localhost [127.0.0.1]) by balder.ntg.nl (Postfix) with ESMTP id E8E681020C for ; Mon, 20 Oct 2014 16:08:09 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at balder.ntg.nl Original-Received: from balder.ntg.nl ([127.0.0.1]) by localhost (balder.ntg.nl [127.0.0.1]) (amavisd-new, port 10024) with LMTP id sIYUcO--2uSJ for ; Mon, 20 Oct 2014 16:08:07 +0200 (CEST) Original-Received: from filter4-ams.mf.surf.net (filter4-ams.mf.surf.net [192.87.102.72]) by balder.ntg.nl (Postfix) with ESMTP id C8014101FE for ; Mon, 20 Oct 2014 16:08:02 +0200 (CEST) Original-Received: from mail-la0-x22f.google.com (mail-la0-x22f.google.com [IPv6:2a00:1450:4010:c03::22f]) by filter4-ams.mf.surf.net (8.14.3/8.14.3/Debian-9.4) with ESMTP id s9KE81uI012593 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for ; Mon, 20 Oct 2014 16:08:02 +0200 Original-Received: by mail-la0-f47.google.com with SMTP id pv20so4058192lab.34 for ; Mon, 20 Oct 2014 07:08:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=ieGHvDBW/jMGJaGbZbNCL/Y1uewod8SQz8VhHpPZGYg=; b=xoY+uBIFM95olcmuoyUBr2BHl5BYMQLqR0NT5aJhrsWrKuWwmupVRO+cwnQ+NX3MyR 6cfXaK11yvPgugoq2idmgjQ3ze0Z7pNKc06UDBcIUXvUuRtjtKgXLexVVPcukCkFaKlV poLfyqsCunj8BoL+qPG6CDDc9+uxecgIC9o+vLxF0hlr2lYus5hOPE1o4mfvO7A/tS0U jwkd/KnrtcK/WP2gc43MBi1PxPZZHksovhdmW92NOR1vwZjluqhybP3w/bZLMcvPH1i9 th7erueMsWRScFUomTr4rO6WPvW8om6+yoIXTl+2KLjf3th4YxEQsE/yODWxuiOzjO1w 32eA== X-Received: by 10.153.8.164 with SMTP id dl4mr27722582lad.29.1413814081527; Mon, 20 Oct 2014 07:08:01 -0700 (PDT) Original-Received: by 10.152.106.82 with HTTP; Mon, 20 Oct 2014 07:08:01 -0700 (PDT) In-Reply-To: <543F1BF0.3030804@panix.com> X-Bayes-Prob: 0.0001 (Score 0, tokens from: ntg-context@ntg.nl, base:default, @@RPTN) X-CanIt-Geo: ip=2a00:1450:4010:c03::22f; country=IE X-CanItPRO-Stream: uu:ntg-context@ntg.nl (inherits from uu:default, base:default) X-Canit-Stats-ID: 01N5q824T - d98ac23b43a8 - 20141020 (trained as not-spam) X-Scanned-By: CanIt (www . roaringpenguin . com) X-BeenThere: ntg-context@ntg.nl X-Mailman-Version: 2.1.16 Precedence: list List-Id: mailing list for ConTeXt users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: ntg-context-bounces@ntg.nl Original-Sender: "ntg-context" Xref: news.gmane.org gmane.comp.tex.context:89018 Archived-At: --===============1487242144== Content-Type: multipart/alternative; boundary=001a11348cbc1ba39b0505db3e1b --001a11348cbc1ba39b0505db3e1b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I am wondering likewise. Sander Maijers On Thu, Oct 16, 2014 at 3:14 AM, Rik wrote: > On 2014-10-15 17:06, Wolfgang Schuster wrote: > >> Am 15.10.2014 um 21:03 schrieb Rik Kabel : >> >> I am not sure I understand the need for symstyle and symcolor. The issu= e >>> is not that the symbols are not styled/colored, but that they do not ap= pear >>> at all when a non-normal style is specified. What I see with the exampl= e I >>> posted is: >>> >>> 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=3Dnormal for level 3 should perhaps be style=3D\tf= , >>> since normal is redefined to slanted within the scope of layer 2. With = that >>> change to my example, I get >>> >>> 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 =E2=80=9Cit's deliberate and has always been the case in mk= iv=E2=80=9D? >>> >> When you use =E2=80=9Clocation=3Dtext=E2=80=9D context checks the value = of the style key, >> when the value of the key is =E2=80=9Cnormal=E2=80=9D >> 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 chose= n. > Styling can be done within the text, as can delimiters, but the benefit o= f > 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 > ____________________________________________________________ > _______________________ --001a11348cbc1ba39b0505db3e1b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I am wondering likewise.

Sander Maijers

On Thu, Oct 16, 2014 at 3:14 AM, Rik <rik@panix= .com> wrote:
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 a= t all when a non-normal style is specified. What I see with the example I p= osted 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=3Dnormal for level 3 should perhaps be style=3D\tf, si= nce normal is redefined to slanted within the scope of layer 2. With that c= hange 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 =E2=80=9Cit's deliberate and has always been the case in mkiv=E2= =80=9D?
When you use =E2=80=9Clocation=3Dtext=E2=80=9D context checks the value of = the style key, when the value of the key is =E2=80=9Cnormal=E2=80=9D
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 comm= and, that the delimiter is more important than the styling, and so I suspec= t that there is some historical reason that this behavior was chosen. Styli= ng can be done within the text, as can delimiters, but the benefit of the c= ommand 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 t= he Wiki!

maillist : ntg-cont= ext@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage=C2=A0 : http= ://www.pragma-ade.nl / http://tex.aanhet.net
archive=C2=A0 : http://foundry.supelec.fr/projects/contextrev/=
wiki=C2=A0 =C2=A0 =C2=A0: http://contextgarden.net
_____________________________________________________________= ______________________

--001a11348cbc1ba39b0505db3e1b-- --===============1487242144== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX18KSWYgeW91ciBxdWVzdGlvbiBpcyBvZiBpbnRlcmVz dCB0byBvdGhlcnMgYXMgd2VsbCwgcGxlYXNlIGFkZCBhbiBlbnRyeSB0byB0aGUgV2lraSEKCm1h aWxsaXN0IDogbnRnLWNvbnRleHRAbnRnLm5sIC8gaHR0cDovL3d3dy5udGcubmwvbWFpbG1hbi9s aXN0aW5mby9udGctY29udGV4dAp3ZWJwYWdlICA6IGh0dHA6Ly93d3cucHJhZ21hLWFkZS5ubCAv IGh0dHA6Ly90ZXguYWFuaGV0Lm5ldAphcmNoaXZlICA6IGh0dHA6Ly9mb3VuZHJ5LnN1cGVsZWMu ZnIvcHJvamVjdHMvY29udGV4dHJldi8Kd2lraSAgICAgOiBodHRwOi8vY29udGV4dGdhcmRlbi5u ZXQKX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX18= --===============1487242144==--