Hi Gavin
Thank four your effort. I found out, that the following definition of a new
unit, i called it SI, results also in a correct spaceing in the math
environment:
\defineunit[SI][alternative=text]
It seems, that the option alternative=text solves the problem with no spaces
between value a
When I use the code given, it compiles and displays fine. But when I try
replacing \everypar with \EveryPar, it halts during compiling with this
complaint:
"A number should have been here; I inserted '0'. (If you can't figure out why I
needed to see a number, look up 'weird error' in the index t
These both work great, but do that for the whole document? Is there a way to
restrict it to only apply the lines to some parts of the file, not every single
paragraph?
Thanks!
--Joel
On Monday, October 10, 2022 at 04:57:07 PM MDT, Max Chernoff
wrote:
Hi Joel,
On Mon, 2022-10-10 at 1
Hi Oli,
> Thank four your effort. I found out, that the following definition of a new
> unit, i called it SI, results also in a correct spaceing in the math
> environment:
>
> \defineunit[SI][alternative=text]
>
> It seems, that the option alternative=text solves the problem with no spaces
>
Hi List,
When I use text inside a radical, the text is script-script size.
$\text{Radius} = \sqrt{\text{Area}/\pi}$
It should be normal size. Any ideas for a fix?
I stumbled on this issue when working with \units, but it is not specific to
units.
Thanks!
Gavin
On Wed, 12 Oct 2022 21:14:52 -0600
Gavin wrote:
> As a recovering string theorist, I cannot help but speculate that
> this rule extends to spherical coordinates in any number of
> dimensions. However, if you don’t want the space, you can use
> 135\unit{℃}, which does not add a space.
Will 135\un
On 10/13/22 00:50, Max Chernoff via ntg-context wrote:
> On Wed, 2022-10-12 at 13:14 +0200, Leah Neukirchen wrote:
>> [...]
>> The last version of font-cff.lua should also copy the hinting-related
>> values of the CFF properly (/BlueScale, /StemSnap[HV] etc).
>> We fixed that on the side. ;)
>
> Ya
Am 13.10.22 um 19:41 schrieb Pablo Rodriguez via ntg-context:
On 10/13/22 00:50, Max Chernoff via ntg-context wrote:
On Wed, 2022-10-12 at 13:14 +0200, Leah Neukirchen wrote:
[...]
The last version of font-cff.lua should also copy the hinting-related
values of the CFF properly (/BlueScale, /Ste
Now! I am astonished about this blog! Super that you, Leah and Hans, insisted
to find out what the culprit was! Thank you both so much for your effort!
Kind regards
Willi
> On 11 Oct 2022, at 21:07, Leah Neukirchen via ntg-context
> wrote:
>
> Hans Hagen via ntg-context writes:
>
>> On 10/9
Thank you, Max.
The angle function doesn't appear to provide the same calculation as
my atantwo in all cases.
https://pdfhost.io/v/Oqj7XmibJ_scaled
The shorter line segment should be directed towards the vertex closest
to the longer line segment. I tried using both:
theta := angle( dx, dy )
On 10/13/2022 2:38 PM, Gavin via ntg-context wrote:
Hi List,
When I use text inside a radical, the text is script-script size.
$\text{Radius} = \sqrt{\text{Area}/\pi}$
It should be normal size. Any ideas for a fix?
I stumbled on this issue when working with \units, but it is not specific to
On 10/13/2022 7:41 PM, Pablo Rodriguez via ntg-context wrote:
On 10/13/22 00:50, Max Chernoff via ntg-context wrote:
On Wed, 2022-10-12 at 13:14 +0200, Leah Neukirchen wrote:
[...]
The last version of font-cff.lua should also copy the hinting-related
values of the CFF properly (/BlueScale, /Ste
On 10/13/2022 8:36 PM, Henning Hraban Ramm via ntg-context wrote:
Am 13.10.22 um 19:41 schrieb Pablo Rodriguez via ntg-context:
On 10/13/22 00:50, Max Chernoff via ntg-context wrote:
On Wed, 2022-10-12 at 13:14 +0200, Leah Neukirchen wrote:
[...]
The last version of font-cff.lua should also co
Hi,
> The angle function doesn't appear to provide the same calculation as
> my atantwo in all cases.
They both give the same results, but "angle" gives a result in degrees
while "atantwo" gives a result in radians. This demo:
\startMPpage
vardef atantwo( expr dy, dx ) =
sa
Hi Joel,
> When I use the code given, it compiles and displays fine. But when I
> try replacing \everypar with \EveryPar, it halts during compiling
It looks like \EveryPar is a macro and not a token list.
> These both work great, but do that for the whole document? Is there a
> way to restrict it
15 matches
Mail list logo