On Fri, 20 Jan 2017 22:33:40 -0500
Rik Kabel wrote:
> Can anyone suggest a better way to compose such symbols than using
> the raw TeX commands used here? Is there a more ConTeXt-ish way to do
> this? Is it possible to get options to center the glyphs from which
>
ConTeXters,
I have been using \definesymbol for a while, and for most purposes it
suffices. However, there is one thing that it does not do that perhaps
it should.
What it does not do is offer the option to center one glyph over another
(horizontally and/or vertically) when it should be
Am 20.01.2017 um 23:12 schrieb Henning Hraban Ramm:
> Am 2017-01-20 um 22:26 schrieb Peter Rolf :
>
>> Am 20.01.2017 um 21:54 schrieb Alan Braslau:
>>> On Fri, 20 Jan 2017 21:42:16 +0100
>>> Peter Rolf wrote:
>>>
Maybe intended behaviour, maybe a bug.
Am 2017-01-20 um 22:26 schrieb Peter Rolf :
> Am 20.01.2017 um 21:54 schrieb Alan Braslau:
>> On Fri, 20 Jan 2017 21:42:16 +0100
>> Peter Rolf wrote:
>>
>>> Maybe intended behaviour, maybe a bug. Donno.
>>
>> Not a bug: color and transparency are not the same
Am 20.01.2017 um 21:54 schrieb Alan Braslau:
> On Fri, 20 Jan 2017 21:42:16 +0100
> Peter Rolf wrote:
>
>> Maybe intended behaviour, maybe a bug. Donno.
>
> Not a bug: color and transparency are not the same thing.
>
True, but you define and use them at once. How to separate
On Fri, 20 Jan 2017 21:42:16 +0100
Peter Rolf wrote:
> Maybe intended behaviour, maybe a bug. Donno.
Not a bug: color and transparency are not the same thing.
Alan
___
If your question is of
Hi,
the nested color inherits the transparency from it's surrounding color.
\definecolor[colA] [r=0,g=0,b=0.01,t=0.2,a=1] % transparent
\definecolor[colB] [r=.278431,g=.235294,b=.545098] % opaque
\starttext
\startcolor[colA]
\definedfont[SansBold at 96bp]Titanfall\,
> On 20 Jan 2017, at 18:00, Rik Kabel wrote:
> […]
>
> Otared,
>
> I am not sure what you are doing, but if you are using only the code snippet
> that Hans posted, you will get a blank page. You have to define the layer and
> page background in addition to Hans'
On 2017-01-20 11:42, Otared Kavian wrote:
Hi Hans,
Unfortunately your workaround with \getbuffer does not produce the correct
page: it gives only a blank page.
Thanks for your attention: OK
On 20 Jan 2017, at 10:08, Hans Hagen wrote:
On 1/20/2017 8:59 AM, Aditya Mahajan
Hi Hans,
Unfortunately your workaround with \getbuffer does not produce the correct
page: it gives only a blank page.
Thanks for your attention: OK
> On 20 Jan 2017, at 10:08, Hans Hagen wrote:
>
> On 1/20/2017 8:59 AM, Aditya Mahajan wrote:
>> On Thu, 19 Jan 2017, Rik Kabel
Dear List,
First of all: Thank you Hans and folks for supporting focus=standard
for many things. There are, however, some major places where
focus=standard does not work correctly yet. I pick out the simplest
and in my opinion most severe one: Floats.
Dear devs,
In mathematics the norm of something is usually denoted by the double vertical
bars, e.g. ||v||. This is not available in asciimath.
\usemodule[asciimath]
\starttext
$\asciimath{ x^* = min { x | sum_{kk} ||f(x_{kk}^{20})|| } }$
\stoptext
Could you please add this to the parser?
On 1/20/2017 8:59 AM, Aditya Mahajan wrote:
On Thu, 19 Jan 2017, Rik Kabel wrote:
ConTeXters,
When \dorecurse is active in the following MWE, the lines of text are
overprinted. At least, this is the case for me, please confirm it for
yourself. When \dorecurse is disabled, the lines print as
On Thu, 19 Jan 2017, Rik Kabel wrote:
ConTeXters,
When \dorecurse is active in the following MWE, the lines of text are
overprinted. At least, this is the case for me, please confirm it for
yourself. When \dorecurse is disabled, the lines print as they should,
separately. Please tell me
14 matches
Mail list logo