On 2/13/21 12:33 AM, Hans Hagen wrote:
> On 2/13/2021 12:13 AM, Pablo Rodriguez wrote:
>> Dear Hans,
>>
>> I’m afraid that style doesn’t work for headings in current latest
>> (2021.02.12 18:49):
>> [...]
> can you check again?
Many thanks for your fast fix, Hans.
It works perfectly fine now.
On 2/13/2021 12:13 AM, Pablo Rodriguez wrote:
Dear Hans,
I’m afraid that style doesn’t work for headings in current latest
(2021.02.12 18:49):
\setuphead[chapter][style=\it]
\setuphead[section][style=\it]
\starttext
\chapter{Chapter}
\section{Section}
\input zapf
\stoptext
On 2/13/21 12:13 AM, Pablo Rodriguez wrote:
> Dear Hans,
>
> I’m afraid that style doesn’t work for headings in current latest
> (2021.02.12 18:49):
Hans,
it might be that the style option doesn’t work in other commands (or at
all):
\setuphead[section][style=\it]
Dear Hans,
I’m afraid that style doesn’t work for headings in current latest
(2021.02.12 18:49):
\setuphead[chapter][style=\it]
\setuphead[section][style=\it]
\starttext
\chapter{Chapter}
\section{Section}
\input zapf
\stoptext
Many thanks for your help,
Pablo
--
I need to reinstall luametatex version 2.08.13. Is there a page somewhere
describing how to do this?
Alan
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist :
There's \processseparatedlist[][]\command with an
arbitrary other than a comma...
You should take a look at syst-aux.mkiv and syst-aux.mkxl to see more
helpers:
https://source.contextgarden.net/tex/context/base/mkiv/syst-aux.mkxl
El vie, 12 de feb. de 2021 a la(s) 14:49, Angel M Alganza
Hi Jairo:
On Fri, Feb 12, 2021 at 01:50:58PM -0500, Jairo A. del Rio wrote:
Hi, Ángel. Like this?
\def\mylist{Fulano,Mengano,Sutano}
\def\mycommand#1{#1\blank{\red Something here}\blank}
\starttext
\processcommacommand[\mylist]\mycommand
\stoptext
Yes, exactly like this, thank you.
Oh, I knew about the environment form, but I didn't know about
\currentcommalistitem. Useful to avoid to define ad hoc commands :)
As always, thank you very much for the lesson.
Best regards,
Jairo
El vie, 12 de feb. de 2021 a la(s) 14:25, Wolfgang Schuster (
wolfgang.schuster.li...@gmail.com)
Jairo A. del Rio schrieb am 12.02.2021 um 19:50:
Hi, Ángel. Like this?
\def\mylist{Fulano,Mengano,Sutano}
\def\mycommand#1{#1\blank{\red Something here}\blank}
\starttext
\processcommacommand[\mylist]\mycommand
\stoptext
There are better ways to deal with data in ConTeXt, but it's
Oops, it's "zutano". Sorry for the typo.
Jairo :)
El vie, 12 de feb. de 2021 a la(s) 13:50, Jairo A. del Rio (
jairoadelr...@gmail.com) escribió:
> Hi, Ángel. Like this?
>
> \def\mylist{Fulano,Mengano,Sutano}
>
> \def\mycommand#1{#1\blank{\red Something here}\blank}
>
> \starttext
>
>
Hi, Ángel. Like this?
\def\mylist{Fulano,Mengano,Sutano}
\def\mycommand#1{#1\blank{\red Something here}\blank}
\starttext
\processcommacommand[\mylist]\mycommand
\stoptext
There are better ways to deal with data in ConTeXt, but it's basically that
way, I think.
Jairo
El vie, 12 de feb.
On 2/12/21 7:39 PM, Angel M Alganza wrote:
Is it possible to do that with just ConTeXt or would I need to resort to
Lua. I guess it should be possible both ways, but I haven't figure out
how to do it. Any pointer, please?
https://wiki.contextgarden.net/Processing_Lists
which wasn't
Hello:
I am trying to print a list of names always followed by the same info
(generated by a new command). At the moment, I have all the names
followed by the command like so:
Person Number One
\mycommand
Person Number Two
\mycommand
Person Number Three
Hi,
I uploaded a new version. I'v enow tagged all public macros (not that
anyone will notice) as a step in the overload protection effort. If you
want to get an idea about what we're talking of you can process
s-system-macros.mkxl
This file is mostly for Wolfgang and me when we update to
On 2/12/2021 4:52 PM, Pablo Rodriguez wrote:
On 2/12/21 4:40 PM, Hans Hagen wrote:
On 2/12/2021 3:43 PM, Pablo Rodriguez wrote:
[...]
"\page\null\page" does the trick in your case.
\page[left,empty,right] etc
Hans,
I never thought this were possible:
\starttext
Thanks,
this does the job for me
Kind Regards/Met vriendelijke groet,
Bert Verbeek
On 2/12/21 3:30 PM, Hans Hagen wrote:
for now put this in cont-new.mkxl:
\unprotect
\let\strc_synonyms_place_list\placelistofsynonyms
\protect
On 2/12/21 4:40 PM, Hans Hagen wrote:
> On 2/12/2021 3:43 PM, Pablo Rodriguez wrote:
>> [...]
>> "\page\null\page" does the trick in your case.
>
> \page[left,empty,right] etc
Hans,
I never thought this were possible:
\starttext
\page[left,empty,right,
left,empty,right,
Dear list,
I have the following sample:
\setuppapersize[A4, landscape]
\setupinteractionscreen[option={landscape, paper}]
\starttext
\dorecurse{2}
{\startmakeup[page][pagestate=start, align=middle]
\dontleavehmode
\scale[width=.8\textwidth]{middle}
\stopmakeup}
\stoptext
On 2/11/21 12:11 PM, Ursula Hermann wrote:
> Dear List!
>
>
> I did this example, which works perfect. If i would like to take a new
> page after the Table of Content, is \page the right way?
Hi Ursula,
"\page\null\page" does the trick in your case.
"\setuppagenumber[alternative=doublesided]"
On 2/12/2021 2:37 PM, Bert Verbeek wrote:
Hello all,
I've used ConTeXt MkIV for years to make technical reports. For a new
computer I looked for updates of the software and discovered LMTX. I ran
it on my latest report and found an error on
\completelistofabbreviations, both on win-64 and
Hello all,
I've used ConTeXt MkIV for years to make technical reports. For a new
computer I looked for updates of the software and discovered LMTX. I ran
it on my latest report and found an error on
\completelistofabbreviations, both on win-64 and linux. Context --luatex
worked fine.
A
On Fri, Feb 12 2021, Wolfgang Schuster wrote:
> 2. Add \strut, e.g. \position(1, 1){\strut i}
Ah, thanks. So the anchor is not the baseline, but the top-left corner of
the content.
Since "\setuppositioning[before=\strut]" does not work, I use this
workaround now:
\def\myPosition(#1,
Peter Münster schrieb am 12.02.2021 um 13:31:
Hi,
When I want to type an "i" in the position-command, there is some
vertical offset:
\starttext
\startpositioning
\position(1, 1){i} \position(2, 1){x}
\position(1, 2){x} \position(2, 2){i}
\position(1, 3){a} \position(2, 3){x}
\position(1, 4){x}
Hi,
When I want to type an "i" in the position-command, there is some
vertical offset:
\starttext
\startpositioning
\position(1, 1){i} \position(2, 1){x}
\position(1, 2){x} \position(2, 2){i}
\position(1, 3){a} \position(2, 3){x}
\position(1, 4){x} \position(2, 4){a}
\stoppositioning
\stoptext
On 2/12/2021 12:42 PM, Floris van Manen wrote:
What is the correct ways to pass parameters into a \startMPpage section?
This does not produce a page (obviously if you know how it works)
But how to get the intende output?
\def\blz[#1][#2][#3]{
\startMPpage
draw thefmttext(#1) shifted(10mm,
Werner Hennrich schrieb am 12.02.2021 um 08:26:
Hello everyone,
please can you give me pointers on how to easiest parse multi-valued
\dummyparameter{...} like in
\something[...,weather={sunshine, rain, hail},...]
so that I can test for e.g. rain, sunshine, wind, hail, mist, fog,
storm etc,
What is the correct ways to pass parameters into a \startMPpage section?
This does not produce a page (obviously if you know how it works)
But how to get the intende output?
\def\blz[#1][#2][#3]{
\startMPpage
draw thefmttext(#1) shifted(10mm, 20mm);
draw thefmttext(#2) shifted(10mm, 205m);
draw
Hi,
Like this:
metapost.registerscript("scrutenized", function()
local p = mp.scan.path()
local r = math.round
local d = 10^mp.scan.numeric()
for i=1,#p do
local pi = p[i]
pi[1] = r(pi[1] * d) / d
pi[2] = r(pi[2] * d) / d
end
local x1 = r(p[1][1])
> On 12 Feb 2021, at 10:31, Mikael Sundqvist wrote:
>
> Hi Taco,
>
> thanks, from your observation and the way I build the paths, I found
> out that I can avoid the problem by shortening the paths I join just
> slightly:
>
> cl := (fullcircle scaled 4u) shifted z0;
> cl := cl cutbefore point
On 2/12/2021 9:35 AM, Taco Hoekwater wrote:
Hi,
On 11 Feb 2021, at 17:41, Mikael Sundqvist wrote:
Thanks for your investigation and extended example!
So, if I understand it correctly, the problem occurs where the
different circles are glued together with the .. construction.
Took me a
Hi Taco,
thanks, from your observation and the way I build the paths, I found
out that I can avoid the problem by shortening the paths I join just
slightly:
cl := (fullcircle scaled 4u) shifted z0;
cl := cl cutbefore point (1/6+epsilon) along cl cutafter point
(2/6-epsilon) along cl;
cs :=
Hi,
> On 11 Feb 2021, at 17:41, Mikael Sundqvist wrote:
>
> Thanks for your investigation and extended example!
>
> So, if I understand it correctly, the problem occurs where the
> different circles are glued together with the .. construction.
Took me a while to get it, but the problem is the
a, so easy - thank you Hans!
cheers, Werner
Am 12.02.21 um 09:01 schrieb Hans Hagen:
On 2/12/2021 8:26 AM, Werner Hennrich wrote:
Hello everyone,
please can you give me pointers on how to easiest parse multi-valued
\dummyparameter{...} like in
\something[...,weather={sunshine, rain,
On 2/12/2021 8:26 AM, Werner Hennrich wrote:
Hello everyone,
please can you give me pointers on how to easiest parse multi-valued
\dummyparameter{...} like in
\something[...,weather={sunshine, rain, hail},...]
so that I can test for e.g. rain, sunshine, wind, hail, mist, fog,
storm etc, each
34 matches
Mail list logo
