Hans, Wolfgang,
I am so happy to receive your immediate answers. — Thanks a lot, the problem is
solved and I get the colored labeltext!
Thank you
Willi
> On 24 Jun 2022, at 19:19, Hans Hagen via ntg-context
> wrote:
>
> On 6/24/2022 4:34 PM, Willi Egger via ntg-context wrote:
>> Hi all,
>>
On 6/24/2022 5:15 AM, Benjamin Buchmuller via ntg-context wrote:
Dear list,
I've been confronted with the following 'intriguing' formatting requirement for
a document:
"
• Type density: Must be no more than 15 characters per linear inch (including
characters and spaces).
• Line spacing:
On 6/24/2022 8:28 AM, Max Chernoff wrote:
2. The LuaMetaTeX manual says that "pre_linebreak_filter" is called
_after_ the parfillskip glue has been added, but this doesn't seem
to be the case. With LuaLaTeX/Plain LuaTeX/MkIV, this is true, but
the node list passed to the
On 6/24/2022 4:34 PM, Willi Egger via ntg-context wrote:
Hi all,
Sorry for bothering you again.
I would like that lua is returning a colored string, which is a label-text.
The following does not work, the labeltext remains black, there is no error
though:
return
Willi Egger via ntg-context schrieb am 24.06.2022 um 16:34:
Hi all,
Sorry for bothering you again.
I would like that lua is returning a colored string, which is a label-text.
The following does not work, the labeltext remains black, there is no error
though:
return
Hi all,
Sorry for bothering you again.
I would like that lua is returning a colored string, which is a label-text.
The following does not work, the labeltext remains black, there is no error
though:
return context.color({"red"},context.labeltext(s))
What is the correct approach?
Thanks for
Hans, Wolfgang!
Thank you so much for your instructions! — This expansion thing is something I
will probably never master ;-(
Thank you!
Kind regards
Willi
> On 24 Jun 2022, at 05:42, Wolfgang Schuster via ntg-context
> wrote:
>
> Hans Hagen via ntg-context schrieb am 23.06.2022 um 23:00:
Works, thanks!
On Fri, 2022-06-24 at 12:44 +0200, Wolfgang Schuster via ntg-context wrote:
> Johann Birnick via ntg-context schrieb am 24.06.2022 um 11:59:
> > Thanks! However, if I type \cite[righttext={, section 2.1}] is doesn't work
> > anymore. Any ideas?
>
> What happens with
>
>
Am 23.06.22 um 15:08 schrieb Taco Hoekwater:
Hi,
You could just convert these separately to pdf/svg/jpg/png and then load them
as \externalfigure.
I thought about this solution.
You could also use the filter module to be able to take them inline into the
ConTeXt code:
Thanks for the
Johann Birnick via ntg-context schrieb am 24.06.2022 um 11:59:
Thanks! However, if I type \cite[righttext={, section 2.1}] is doesn't work
anymore. Any ideas?
What happens with
\cite[righttext={{, section 2.1}}]
or
\cite[righttext={\textcomma\ section 2.1}]
Wolfgang
Thanks! However, if I type \cite[righttext={, section 2.1}] is doesn't work
anymore. Any ideas?
Johann
On Fri, 2022-06-24 at 09:24 +0200, Henning Hraban Ramm via ntg-context wrote:
> Am 24.06.22 um 02:09 schrieb Johann Birnick via ntg-context:
> > Hi there,
> >
> > using \cite[myreference] I
Am 24.06.22 um 05:15 schrieb Benjamin Buchmuller via ntg-context:
• Type density: Must be no more than 15 characters per linear inch (including
characters and spaces).
This talks about "type density", not characters per line. This depends
mostly on the font (and letterspacing). I.e. you
Am 24.06.22 um 02:09 schrieb Johann Birnick via ntg-context:
Hi there,
using \cite[myreference] I will get a result like "[1]", or I could also change
the "1" into some more detailed information such as a tag.
However, I want to obtain something like "[1, section 2.1]".
How can I achieve
Hi Hans,
So, if there has been serious issues not resolved (the last year) let me
know.
I've been having two issues with parfillskip nodes in LMTX that I
haven't been able to figure out myself. Neither of them are particularly
serious, but the first one is quite annoying.
(The below is
14 matches
Mail list logo
