Hi,
We were considering to drop the virtual math fonts mechanism (which has
served its purpose in the transition in the very early days of luatex
but became obsolete as math fonts evolved) but in the end we were forced
keep this feature and even upgrade it because we liked iwona, kurier and
On Mon, 23 Aug 2021, Aditya Mahajan via ntg-context wrote:
> On Mon, 23 Aug 2021, Benjamin Buchmuller via ntg-context wrote:
>
> > This is the setup I have been using, but I'm unsure if the problem could be
> > related to the other problem I had. (Not scaled to a MWE, but short
> > enough.) I
On 8/23/2021 7:42 PM, Aditya Mahajan wrote:
On Mon, 23 Aug 2021, Benjamin Buchmuller via ntg-context wrote:
This is the setup I have been using, but I'm unsure if the problem could be
related to the other problem I had. (Not scaled to a MWE, but short enough.) I
figured the issue by removing
On Mon, 23 Aug 2021, Benjamin Buchmuller via ntg-context wrote:
> This is the setup I have been using, but I'm unsure if the problem could be
> related to the other problem I had. (Not scaled to a MWE, but short enough.)
> I figured the issue by removing some of the lines.
I get the same
This is the setup I have been using, but I'm unsure if the problem could be
related to the other problem I had. (Not scaled to a MWE, but short enough.) I
figured the issue by removing some of the lines.
\usemodule[vim]
\definetextbackground[codebkg]
[
frame=on,
On 8/23/2021 12:55 AM, Benjamin Buchmuller via ntg-context wrote:
Hi,
Here is another thing which worked previously for me:
ConTeXt ver: 2021.07.30 00:57 LMTX fmt: 2021.8.8 int: english/english
Now:
ConTeXt ver: 2021.08.22 11:54 LMTX fmt: 2021.8.22 int: english/english
Error:
lua
On 8/23/2021 12:10 AM, Benjamin Buchmuller via ntg-context wrote:
Hi,
Thanks for having had a look into the t-vim.
At least the document compiles fine (I get a PDF), although multiple complaints from the lua end
when I use "$" or "#" in my source, for example
#!/usr/bin/bash
etc.
Hi,
Here is another thing which worked previously for me:
ConTeXt ver: 2021.07.30 00:57 LMTX fmt: 2021.8.8 int: english/english
Now:
ConTeXt ver: 2021.08.22 11:54 LMTX fmt: 2021.8.22 int: english/english
Error:
lua error:
registered function call [396]:
Benjamin Buchmuller via ntg-context schrieb am 23.08.2021 um 00:10:
Hi,
Thanks for having had a look into the t-vim.
At least the document compiles fine (I get a PDF), although multiple complaints from the lua end
when I use "$" or "#" in my source, for example
#!/usr/bin/bash
etc.
Hi,
Thanks for having had a look into the t-vim.
At least the document compiles fine (I get a PDF), although multiple complaints
from the lua end when I use "$" or "#" in my source, for example
#!/usr/bin/bash
etc. culminating in
Sorry, but I'm not programmed to handle this case;
I'll
On 8/19/2021 10:07 PM, Aditya Mahajan via ntg-context wrote:
On Thu, 19 Aug 2021, Hans Hagen via ntg-context wrote:
Hi,
Here are the highlights of todays update:
- somewhat more compact tuc files, not for all documents, but it can
accumulate; also less memory used then; i could bring down an
On Thu, 19 Aug 2021, Hans Hagen via ntg-context wrote:
> Hi,
>
> Here are the highlights of todays update:
>
> - somewhat more compact tuc files, not for all documents, but it can
> accumulate; also less memory used then; i could bring down an extreme
> 2000 page 5 column doc tuc file down to
Hi,
Here are the highlights of todays update:
- somewhat more compact tuc files, not for all documents, but it can
accumulate; also less memory used then; i could bring down an extreme
2000 page 5 column doc tuc file down to 5% -- it was 70 MB; for the
luametatex manual it reducec the tuc
Hi,
I uploaded a new version. There are two new features that are
experimental. This time we attempt to deal with the more tricky things
and artifacts of the otherwise nice tex machinery we need to get rid of.
One can rightfully argue that they are not really issues as one can work
around
On 3/2/2021 11:15 AM, mf wrote:
Il 01/03/21 15:44, Hans Hagen ha scritto:
\starttext
\startuseMPgraphic{circle}
lmt_parshape [
path = fullcircle scaled 136mm,
offset = 2mm,
bottomskip = - 1.5LineHeight,
] ;
\stopuseMPgraphic
\start
On 3/2/2021 11:15 AM, mf wrote:
Il 01/03/21 15:44, Hans Hagen ha scritto:
\starttext
\startuseMPgraphic{circle}
lmt_parshape [
path = fullcircle scaled 136mm,
offset = 2mm,
bottomskip = - 1.5LineHeight,
] ;
\stopuseMPgraphic
\start
Il 01/03/21 15:44, Hans Hagen ha scritto:
\starttext
\startuseMPgraphic{circle}
lmt_parshape [
path = fullcircle scaled 136mm,
offset = 2mm,
bottomskip = - 1.5LineHeight,
] ;
\stopuseMPgraphic
\start
On 3/1/2021 6:27 PM, Otared Kavian wrote:
Hi Hans,
Thank you for the new upload.
The teaser examples work fine, many thanks !
I have a question though: how can one center within a page a text, for example
typeset in a circular shape? I tried with \startalignment, and also with
Hi Hans,
Thank you for the new upload.
The teaser examples work fine, many thanks !
I have a question though: how can one center within a page a text, for example
typeset in a circular shape? I tried with \startalignment, and also with
\startplacefigure but none of these gives a centered
Hi,
I uploaded a new lmtx. As I'm currently going through the metafun todo
files I ended up at the fancy shape part (parshapes) running over
multiple paragraphs and decided to provide a (kind of low level)
interface that integrates that. The example code is a few decades old
but still works
Hello,
I noticed yesterday that paragraph indenting appears to have changed
between
LMTX 2020.11.17 & 11.19. Usually the first paragraph after a section
heading
does not indent, as it does with all subsequent paragraphs. With 11.19
the first
paragraph does have an indent. I've had to revert to
On 11/21/20 10:44 PM, Richard Mahoney wrote:
> Hello,
>
> I noticed yesterday that paragraph indenting appears to have changed between
> LMTX 2020.11.17 & 11.19. Usually the first paragraph after a section heading
> does not indent, as it does with all subsequent paragraphs. With 11.19
> the first
El 17/9/20 a las 12:50, Eduardo Bohoyo escribió:
El 17/9/20 a las 12:35, Wolfgang Schuster escribió:
Eduardo Bohoyo schrieb am 17.09.2020 um 10:14:
Thank you for this illustrative example, Wolfgang.
So, what \forgetparagraphfreezing does is to reverse the order that
lmtx currently imposes
El 17/9/20 a las 12:35, Wolfgang Schuster escribió:
Eduardo Bohoyo schrieb am 17.09.2020 um 10:14:
Thank you for this illustrative example, Wolfgang.
So, what \forgetparagraphfreezing does is to reverse the order that
lmtx currently imposes by default, right? In other words,
Eduardo Bohoyo schrieb am 17.09.2020 um 10:14:
Thank you for this illustrative example, Wolfgang.
So, what \forgetparagraphfreezing does is to reverse the order that
lmtx currently imposes by default, right? In other words,
\forgetparagraphfreezing, recovers the default behaviour of MkIV.
El 17/9/20 a las 1:07, ebohoyod escribió:
El 16/9/20 a las 18:23, Wolfgang Schuster escribió:
ebohoyod schrieb am 16.09.2020 um 17:52:
Hi,
It seems that the Lettrine module is one of those affected:
ebohoyod schrieb am 16.09.2020 um 17:52:
Hi,
It seems that the Lettrine module is one of those affected:
https://tex.stackexchange.com/questions/562534/does-context-fail-in-the-lmtx-environment-with-the-lettrine-module?noredirect=1#comment1418902_562534
But, honestly, first, I don't know
Hi,
It seems that the Lettrine module is one of those affected:
https://tex.stackexchange.com/questions/562534/does-context-fail-in-the-lmtx-environment-with-the-lettrine-module?noredirect=1#comment1418902_562534
But, honestly, first, I don't know what means "/Of course it might have
other
On 7/31/20 10:32 AM, Hans Hagen wrote:
> Hi,
>
> Sorry for the long mail ...
>
> One of the changes in lmtx is that we freeze the properties that
> determine the paragraph shape as well as breaking into lines in such a
> way that we have predictable behaviour. As a side effect it can be that
>
On Fri, 31 Jul 2020, Hans Hagen wrote:
Thanks for the update.
Other work in progress is: better columns in itemize, esp proper
footnote support (not that I ever need that but I know users do so ...),
experiments work ok, but I need to check spacing. In general, footnotes
(will) behave a bit
Hi Hraban,
Thank you for reminding me of the solution cooked up by Wolfgang for you a few
years ago. That solution works fine when the notes are short enough, but in
some cases the notes in the margin bump into each other (indeed it is not a
good habit to have long notes, but in some cases one
> Am 01.08.2020 um 15:20 schrieb Otared Kavian :
>
> Regarding footnotes, would it be possible to have a built-in support for
> writing the footnotes in the margin? (For instance, assuming that the layout
> is such that for instance the right margin takes 1/3 of the page width, then
> the
> On 1 Aug 2020, at 16:17, Hans Hagen wrote:
>
> On 8/1/2020 3:20 PM, Otared Kavian wrote:
>>> On 31 Jul 2020, at 10:32, Hans Hagen wrote:
>>>
>>> […]
>>>
>>> Other work in progress is: better columns in itemize, esp proper footnote
>>> support (not that I ever need that but I know users do
On 8/1/2020 3:20 PM, Otared Kavian wrote:
On 31 Jul 2020, at 10:32, Hans Hagen wrote:
[…]
Other work in progress is: better columns in itemize, esp proper footnote
support (not that I ever need that but I know users do so ...), experiments
work ok, but I need to check spacing. In general,
> On 31 Jul 2020, at 10:32, Hans Hagen wrote:
>
> […]
>
> Other work in progress is: better columns in itemize, esp proper footnote
> support (not that I ever need that but I know users do so ...), experiments
> work ok, but I need to check spacing. In general, footnotes (will) behave a
>
On 7/31/2020 10:40 AM, Taco Hoekwater wrote:
Hi Hans,
On 31 Jul 2020, at 10:32, Hans Hagen wrote:
Hi,
Sorry for the long mail ...
One of the changes in lmtx is that we freeze the properties that determine the
paragraph shape as well as breaking into lines in such a way that we have
Hi Hans,
> On 31 Jul 2020, at 10:32, Hans Hagen wrote:
>
> Hi,
>
> Sorry for the long mail ...
>
> One of the changes in lmtx is that we freeze the properties that determine
> the paragraph shape as well as breaking into lines in such a way that we have
> predictable behaviour. As a side
Hi,
Sorry for the long mail ...
One of the changes in lmtx is that we freeze the properties that
determine the paragraph shape as well as breaking into lines in such a
way that we have predictable behaviour. As a side effect it can be that
existing code (lmtx only) will behave differently
38 matches
Mail list logo
