w
> some \OPENTYPE\ fonts. Not using rules makes some of them look better. The
>effect is subtle and probably not \AMS\ compliant, but we think that it
> will
>work out well for simple math like fractions of decimal numbers.
>Consequently, we have added to our shrinking to-d
effect is subtle and probably not \AMS\ compliant, but we think
that it will
work out well for simple math like fractions of decimal numbers.
Consequently, we have added to our shrinking to-do list the burden to
investigate whether we can remove those obsolete code paths from
the
via ntg-context wrote:
>>>> Hi List,
>>>> I’m getting strange spaces around some decimal points after a clean
>>>> LMTX
>>>> install. MWE:
>>>> \starttext
>>>> \startformula
>>>> v = \frac{1.32}{1.41
t;> Hi List,
>>> I’m getting strange spaces around some decimal points after a clean
>>> LMTX
>>> install. MWE:
>>> \starttext
>>> \startformula
>>> v = \frac{1.32}{1.41} = 0.935
>>> \stopformula
>>> \stoptext
>>>
:
Hi List,
I’m getting strange spaces around some decimal points after a
clean LMTX
install. MWE:
\starttext
\startformula
v = \frac{1.32}{1.41} = 0.935
\stopformula
\stoptext
This produces the result attached below. The 1.32 looks fine,
but the next two
numbers have excess space around
fine, but the next two
numbers have excess space around the decimal point. Adding the line
\showmakeup[mathglue] %\mathspacingmode=1
to the preamble reveals that the second and third decimal points are being
treated as binary operators. It’s very strang. Are others getting this?
can you pick up
fine, but the next two
numbers have excess space around the decimal point. Adding the line
\showmakeup[mathglue] %\mathspacingmode=1
to the preamble reveals that the second and third decimal points are being
treated as binary operators. It’s very strang. Are others getting this?
weird indeed
Hi List,
I’m getting strange spaces around some decimal points after a clean LMTX
install. MWE:
\starttext
\startformula
v = \frac{1.32}{1.41} = 0.935
\stopformula
\stoptext
This produces the result attached below. The 1.32 looks fine, but the next two
numbers have excess space around
rols how {dd} is printed).
>> If it helps, the actual body of the macro can easily be a call to Lua so
>> it's fine if the function takes 5 params where 4 and 5 can be nil or empty
>> strings.
>> I've trawled through syst-aux.mkiv but it only covers optional nu
7;ve trawled through syst-aux.mkiv but it only covers optional numbers of [ ]
or { } but not combinations of both (which given the vast numbers of
combinations is perhaps not surprising!). Have I missed something obvious that
would help me?
So, four optional with mandate {} plus a fallback to a
o be optionally added (because it controls how {dd} is printed).
If it helps, the actual body of the macro can easily be a call to Lua so it's
fine if the function takes 5 params where 4 and 5 can be nil or empty strings.
I've trawled through syst-aux.mkiv but it only covers optional n
]
My difficulty is that while there is only ever just a couple of
numbers in the left-hand 'column', the right-hand 'column' may have
several lengthy paragraphs. If I have one relatively short \startTwo
followed by one that is much longer, it will be forced to start on
th
]
\setupparagraphs[Two][1][width=.1\textwidth,style=\bfx,align=tolerant]
\setupparagraphs[Two][2][width=.9\textwidth,style=normal,align=tolerant]
My difficulty is that while there is only ever just a couple of numbers
in the left-hand 'column', the right-hand 'column' may h
difficulty is that while there is only ever just a couple of numbers in the
left-hand 'column', the right-hand 'column' may have several lengthy
paragraphs. If I have one relatively short \startTwo followed by one that is
much longer, it will be forced to start on the next pa
1, 4, 3;
>3,-4, 1,-2;
>4,-3, 2,-1} $
> \stoptext
>
> The columns with negative numbers in are centred and I would rather have them
> right-aligned so that the digits stack up above each other and the negative
> signs stick out to the left, so to spe
;4,-3, 2,-1} $
> \stoptext
>
> The columns with negative numbers in are centred and I would rather have
> them right-aligned so that the digits stack up above each other and the
> negative signs stick out to the left, so to speak. Is there an easy way to
&
I'm using the following MWE to produce a matrix:
\definemathmatrix[bmatrix]
[matrix:brackets]
[simplecommand=bmatrix]
\starttext
$ a \rightarrow
\bmatrix{1, 2, 3, 4;
2, 1, 4, 3;
3,-4, 1,-2;
4,-3, 2,-1} $
\stoptext
The columns with negative numbers i
\input knuth
>
> \learnedis{some more}
>
>
> \startchapter[title=Standards]
> \placelearnedshort
> \stopchapter
>
> \stoptext
>
>
> My question is, can I have references to the Workbook page numbers in
> the textbook? And visa-versa?
}}
> }
>
> \starttext
>
> \learnedis{blah blah}
>
> \input knuth
>
> \learnedis{some more}
>
>
> \startchapter[title=Standards]
> \placelearnedshort
> \stopchapter
>
> \stoptext
>
>
> My question is, can I have refe
{%
> \learnedshort{#1}
> \learnedlong{\getvalue{#1}}
> }
>
> \starttext
>
> \learnedis{blah blah}
>
> \input knuth
>
> \learnedis{some more}
>
>
> \startchapter[title=Standards]
> \placelearnedshort
> \stopchapter
>
\learnedis{blah blah}
\input knuth
\learnedis{some more}
\startchapter[title=Standards]
\placelearnedshort
\stopchapter
\stoptext
My question is, can I have references to the Workbook page numbers in the
textbook? And visa-versa?
For instance, the Textbook index currently
numbers
in the left-hand 'column', the right-hand 'column' may have several
lengthy paragraphs. If I have one relatively short \startTwo followed by
one that is much longer, it will be forced to start on the next page,
leaving too much empty space on the previous page.
It is p
There is a little thing that I can't figure out though... In one of my
document I have makeup pages. But inserting them result in wrong page
numbering of subsequent pages. It appears that makeups do not increment
page numbers.
Is this a feature? How could re-establish the right page number for
rs ago and it seems like the resources on Context have greatly
> expanded. So thank you all!
>
> There is a little thing that I can't figure out though... In one of my
> document I have makeup pages. But inserting them result in wrong page
> numbering of subsequent pages. It appe
at I can't figure out though... In one of my
document I have makeup pages. But inserting them result in wrong page
numbering of subsequent pages. It appears that makeups do not increment
page numbers.
Is this a feature? How could re-establish the right page number for the
rest of the docume
uments:
> >
> > Equations: 1.1, 2.2, A.1, A.2
> > Sections: 2.1, 2.2, A.1, A.2
> > Chapters: 1, 2, A, B
> > Remarks: A.2.1, A.2.2
> >
> > However, the bar.tex produces wrong prefixes to formulas and remarks.
> > The output depends on the document structure
t is not a big
deal to track the problem. The prefixdata is complemented by the
sectiondata after the loading the tuc file. So, the question is: is it
possible to store the full prefixdata with all necessary prefix numbers
in the tuc file? Here is my proposal to change the source code:
--- strc-l
I, too, am struggling with external (and internal) references.
I have created (and sent to Hans) a MWE that seems to identify two bugs:
1) External references: in a single product, some of these work, and
*some* do not render the numbers (using \in{} [ref], for example). They
are, however
data
after the loading the tuc file. So, the question is: is it possible to
store the full prefixdata with all necessary prefix numbers in the tuc
file? Here is my proposal to change the source code:
--- strc-lst-old.lmt2023-01-29 11:30:15.610309948 +0300
+++ strc-lst.lmt2023-0
ts (Blackletter,
> Calligraphy, Handwriting) are not changed at all from the last release
> (not even version numbers or dates). All other fonts were changed.
>
> On behalf of TUG, I thank Hans, Mikael, and Michael Sharpe, who among
> them did essentially all of the technical font e
ree specialized fonts (Blackletter,
Calligraphy, Handwriting) are not changed at all from the last release
(not even version numbers or dates). All other fonts were changed.
On behalf of TUG, I thank Hans, Mikael, and Michael Sharpe, who among
them did essentially all of the technical font editing f
Hi Marcus,
any news on that?
Seems like you didn’t send your work to Hans or it didn’t arrive.
Happy new year,
Hraban
Am 31.10.22 um 10:05 schrieb Wolfgang Schuster via ntg-context:
Hi Marcus,
do you have an update on the support for german verbose numbers?
Wolfgang
Hans Hagen via ntg
> the steps you took that caused it.
>
> Known bugs:
> - Generated code from table designer needs better formatting
> - Duplicated color definitions in table designer
> - Layout designer -- numbers are not rounded
>
> Best regards,
> Zdeněk Svoboda
&g
ounter an error while using the application, please let me know (and
> cc: th...@mendelu.cz) the steps you took that caused it.
>
> Known bugs:
> - Generated code from table designer needs better formatting
> - Duplicated color definitions in table designer
> - Layout
f you find a bug or
encounter an error while using the application, please let me know (and
cc: th...@mendelu.cz) the steps you took that caused it.
Known bugs:
- Generated code from table designer needs better formatting
- Duplicated color definitions in table designer
- Layout designer -
gt;
> > I played a little bit with these, and noticed some issues: in the following
> > example, linking the bottom bounds of the integral signs is fine (as long
> > as numbers are put there), but for the upper bounds, the \infty and \pi/2
> > are not accepted (nor is any
> Why is this? The reasoning is that it makes no sense to give list
> numbers or list labels (e.g. APA : authoryear) if there is no list, for
> these numbers or labels depend on the context (bibliography by chapter,
> by part, by volume, or by book, for example).
Aditya__
phy subsystem is
that citations will not work unless you render the bibliography list.
Why is this? The reasoning is that it makes no sense to give list
numbers or list labels (e.g. APA : authoryear) if there is no list, for
these numbers or labels depend on the context (bibliography by chapter,
by part,
context wrote:
> > Hi Hans,
> >
> > Thanks for the new release and the nice anchoring features.
> >
> > I played a little bit with these, and noticed some issues: in the
> following example, linking the bottom bounds of the integral signs is fine
> (as long as numb
year.
so a bit like the surface i have as spare (which was slower than the
2013 precission that i recently replaced by a 2018 one)
Here are the numbers without compact fonts enabled. Not much difference.
mkiv lua stats > font engine: otf 3.131, afm 1.513, tfm 1.000, 84
instan
was slower than the
2013 precission that i recently replaced by a 2018 one)
Here are the numbers without compact fonts enabled. Not much difference.
mkiv lua stats > font engine: otf 3.131, afm 1.513, tfm 1.000, 84
instances, 67 shared in backend, 3 common vectors, 64 common has
replaced by a 2018 one)
Here are the numbers without compact fonts enabled. Not much difference.
mkiv lua stats > font engine: otf 3.131, afm 1.513, tfm 1.000, 84
instances, 67 shared in backend, 3 common vectors, 64 common hashes,
load time 1.076 seconds
which means that you do
the extra log
Hans
The laptop was hot stuff in 2017 with 16GB RAM, 1TB SSD, and a 4K touch
screen -- today, not so hot. Due to be replaced next year.
Here are the numbers without compact fonts enabled. Not much difference.
mkiv lua stats > used config file:
selfautoparent:/texmf/web
On 12/15/2022 10:54 PM, Otared Kavian via ntg-context wrote:
Hi Hans,
Thanks for the new release and the nice anchoring features.
I played a little bit with these, and noticed some issues: in the following
example, linking the bottom bounds of the integral signs is fine (as long as
numbers
On 12/15/2022 10:54 PM, Otared Kavian via ntg-context wrote:
Hi Hans,
Thanks for the new release and the nice anchoring features.
I played a little bit with these, and noticed some issues: in the following
example, linking the bottom bounds of the integral signs is fine (as long as
numbers
Hi Hans,
Thanks for the new release and the nice anchoring features.
I played a little bit with these, and noticed some issues: in the following
example, linking the bottom bounds of the integral signs is fine (as long as
numbers are put there), but for the upper bounds, the \infty and \pi/2
On 12/9/22 05:42, peter.hopcroft--- via ntg-context wrote:
> The pdf from the tex below looks wrong to me, screenshot attached.
> It’s always like this when the page number in the second
> \definelayout is 1 more than the page number in the first. For other
> pairs of numbers, it be
The pdf from the tex below looks wrong to me, screenshot attached. It’s always
like this when the page number in the second \definelayout is 1 more than the
page number in the first. For other pairs of numbers, it behaves like I expect:
the short layout is only on those 2 pages.
I’m using the
goes unnoticed. Also, be
careful with the source and target id's! There is currently no low level
allocation mechanism so stick to positive numbers.
So, lots to play with, if you're in the mood,
Hans
(There is quite some experimental code around but to what extend it ends
up in t
Hi Jan,
> Why is there an additional space after the thousand separator in math mode?
Because something like
${\mathbb N} = \{1,2,3,4,\dots\}$
would look quite bad without any space between the numbers.
(The technical reason is that commas have the math class \mathpunct,
meaning t
xtwidth)|]
> \NI \NC \NC \NC\NR
> \NC \NC \NC \NC\NR
> \stoptabulate
> \stopitemize
>
> \input knuth
> \stoptext
>
> See this code which when compiled, the first itemize numbers line up with
> the left edge of text, bu
p(.35\textwidth)|cp(.2\textwidth)|cp(.35\textwidth)|]
\NI \NC \NC \NC\NR
\NC \NC \NC \NC\NR
\stoptabulate
\stopitemize
\input knuth\stoptext
See this code which when compiled, the first itemize numbers line up with the
left ed
Hi Marcus,
do you have an update on the support for german verbose numbers?
Wolfgang
Hans Hagen via ntg-context schrieb am 10.10.2022 um 23:44:
On 10/10/2022 9:21 PM, Marcus Christopher Ludl via ntg-context wrote:
Hello all,
this is my first contribution to this mailing list. 😄
Recently
(2021.10.28
10:19 LMTX) results in the filler dots being right-aligned with the page
numbers (as they should).
I had a similar issue back in April 2021 which got resolved by an update. Since
I haven’t updated in a while, I can’t say in which version the behaviour
changed back, unfortunately
ion mode for me is
the need to explicitly use format with "decimal i" to round the text
rendering of numbers.
Alan
___
If your question is of interest to others as well, please add an entry to the
Wiki!
mai
e.
Will 135\unit{℃} ever break between the digits 135 and the "unit"?
I agree that \unit should probably use an \mbox to prevent unwanted
breaks.
The other role of \unit, I understand, is to uniformize the
representation of numbers (digits).
> > Related,
> > \unit{90°} does
between the number and the
>>> following units be UNBREAKABLE. Perhaps a thin space (preference), but
>>> most certainly non-breakable.
>>>
>>> Similarly around the times in scientific notation.
>>>
>>> I further cannot imagine that a line break be a
bably too large,
> but I think that a little more space than you currently have would be
> better.
I haven’t adjusted the space directly. I just changed the \times and \cdot from
class binom to class ord. I’m not going to tweak the space. I don’t even use
this font. With proportional numbers i
acceptable around a \cdot
in composite units.
This can possibly lead to overfill and underfill, something that I find
*infinitely* more acceptable then breaking numbers and units.
Yes, I agree completely here.
I do not know or use the \units command. Maybe it uses unbreakable
spaces, maybe not. I
able.
>>
>> Similarly around the times in scientific notation.
>>
>> I further cannot imagine that a line break be acceptable around a \cdot
>> in composite units.
>>
>> This can possibly lead to overfill and underfill, something that I find
>> *infinite
that a line break be acceptable around a \cdot
> in composite units.
>
> This can possibly lead to overfill and underfill, something that I find
> *infinitely* more acceptable then breaking numbers and units.
Yes, I agree completely here.
> I do not know or use the \units command
ntific notation.
I further cannot imagine that a line break be acceptable around a \cdot
in composite units.
This can possibly lead to overfill and underfill, something that I find
*infinitely* more acceptable then breaking numbers and units.
I do not know or use the \units command. Maybe it use
gt;>> for some built-in PDF interpreter?
>>
>>> we basically use the old pre 1.6 embedding, same as luatex
>> I saw that the new code renumbers the glyphs, so it uses 0001, 0002
>> etc instead of the mix of various slot numbers in luatex. Perhaps
>> the pri
luatex
I saw that the new code renumbers the glyphs, so it uses 0001, 0002
etc instead of the mix of various slot numbers in luatex. Perhaps
the printers don't like that.
indeed, soem control code confusion; a few days ago i suggested a test
for that and got no response yet
the glyphs, so it uses 0001, 0002
etc instead of the mix of various slot numbers in luatex. Perhaps
the printers don't like that.
--
Ulrike Fischer
http://www.troubleshooting-tex.de/
___
If your question is o
PDF to the printer)
on a Ricoh MP3053 or on a Samsung CLP-680DW, I just get an empty page.
I believe that is the exact same problem I have and that I described
a
few days ago in my email with subject "Missing letters and numbers in
printout". I have some grids on my document, which gets prin
e printer)
>>> on a Ricoh MP3053 or on a Samsung CLP-680DW, I just get an empty page.
>> I believe that is the exact same problem I have and that I described
>> a
>> few days ago in my email with subject "Missing letters and numbers in
>> printout". I have so
page.
I believe that is the exact same problem I have and that I described a
few days ago in my email with subject "Missing letters and numbers in
printout". I have some grids on my document, which gets printed out,
but nothing else does.
The PDFs render fine on every PDF reader I cou
escribed a
few days ago in my email with subject "Missing letters and numbers in
printout". I have some grids on my document, which gets printed out,
but nothing else does.
The PDFs render fine on every PDF reader I could find.
Same here.
PDFs generated directly from Context MK
On 9/29/22 15:54, Angel M Alganza via ntg-context wrote:
> On Wed, Sep 28, 2022 at 03:59:07PM +0200, Hans Hagen via ntg-context wrote:
> [...]
>> but lmtx is and will stay as default
>
> Too bad the default won't work as expected (it did before or, at least
> with TeXLive distribution,) sometimes,
On 9/29/2022 3:54 PM, Angel M Alganza via ntg-context wrote:
No, alas I do not. Could you please point me to where I could download
the latest greatest for 32bits OpenBSD from. I remember a discussion a
few months ago to eliminated 32bits OpenBSD if nobody used it, where I
asked to keep publis
On Wed, Sep 28, 2022 at 03:59:07PM +0200, Hans Hagen via ntg-context wrote:
changed to have 'context file.txt' to compile using luatex instead of
LuaMetaTeX?
top line:
% engine=luatex
Thank you, I'll add that to my source files from now on.
but lmtx is and will stay as default
To bad the
On 9/28/2022 5:10 PM, Pablo Rodriguez via ntg-context wrote:
Well, that is probably too much to say (I mean, that "--luatex"
generates more accurate PDF documents).
depends on how one defines accurate
The main issue would be pretending to use with LuaTeX some features
available only in LuaMe
On 9/28/22 15:30, Angel M Alganza via ntg-context wrote:
> On Tue, Sep 27, 2022 at 04:03:06PM +0200, Pablo Rodriguez via
> ntg-context wrote:
>> [...]
>> I think that this PDF document will be fine with your printer.
>
> It was. I printed it this morning without any problem. Thank you!
Glad to r
On 9/28/2022 3:30 PM, Angel M Alganza via ntg-context wrote:
On Tue, Sep 27, 2022 at 04:03:06PM +0200, Pablo Rodriguez via
ntg-context wrote:
In that case, run "context --luatex --generate" first and then "context
--luatex a6lua.tex".
This would give you a pure LuaTeX-compiled PDF document.
On Tue, Sep 27, 2022 at 04:03:06PM +0200, Pablo Rodriguez via ntg-context wrote:
In that case, run "context --luatex --generate" first and then "context
--luatex a6lua.tex".
This would give you a pure LuaTeX-compiled PDF document.
I think that this PDF document will be fine with your printer.
On Tue, Sep 27, 2022 at 04:03:06PM +0200, Pablo Rodriguez via ntg-context wrote:
Producer: LuaMetaTeX-2.09
No, this was compiled with LuaMetaTeX.
It looks so obvious now, but it didn't (to me) before. :-)
In that case, run "context --luatex --generate" first and then
"context --luate
On 9/26/22 23:04, Angel M Alganza via ntg-context wrote:
> On Mon, Sep 26, 2022 at 10:44:55PM +0200, Hans Hagen via ntg-context wrote:
>
>> mtxrun --script pdf --info oeps.pdf
> [...]
> mtx-pdf | creation date > D:20220920071929+02'00'
> mtx-pdf | modification date > D:202209200
On 9/26/22 20:26, Angel M Alganza via ntg-context wrote:
> On Mon, Sep 26, 2022 at 07:10:40PM +0200, Pablo Rodriguez via ntg-context
> wrote:
> [...]
>> There might be a workaround (or a way of testing this), compiling the
>> PDF document with LuaTeX instead of with LuaMetaTeX.
>
> It seems it is
On 9/26/2022 11:04 PM, Angel M Alganza via ntg-context wrote:
On Mon, Sep 26, 2022 at 10:44:55PM +0200, Hans Hagen via ntg-context wrote:
mtxrun --script pdf --info oeps.pdf
$ mtxrun --script pdf --info a6.pdf
mtx-pdf | filename > a6.pdf
mtx-pdf | pdf version >
On 9/26/2022 8:26 PM, Angel M Alganza via ntg-context wrote:
I didn't know any of the poppler-utils, thank you!
Otherwise, the only option about your documents is guessing.
mtxrun --script pdf --info oeps.pdf
mtxrun --script pdf --fonts oeps.pdf
the second one also shows what characters are
On Mon, Sep 26, 2022 at 10:44:55PM +0200, Hans Hagen via ntg-context wrote:
mtxrun --script pdf --info oeps.pdf
$ mtxrun --script pdf --info a6.pdf
mtx-pdf | filename > a6.pdf
mtx-pdf | pdf version > 1.7
mtx-pdf | major version > 1
mtx-pdf | m
On 9/26/2022 8:26 PM, Angel M Alganza via ntg-context wrote:
I didn't know any of the poppler-utils, thank you!
mtxrun --script pdf --info oeps.pdf
mtxrun --script pdf --fonts oeps.pdf
the second one also shows what characters are in there
Hans
-
On Mon, Sep 26, 2022 at 07:10:40PM +0200, Pablo Rodriguez via ntg-context wrote:
BTW, is TeX Gyre Heros the font with missing chars in the printed
version of your PDF document?
It doesn't seem to be that:
$ pdffonts a6.pdf
name type encoding
On 9/26/22 16:06, Angel M Alganza via ntg-context wrote:
> Hello,
Hi Ángel,
> [...]
> I tried printing the same file (from the same USB drive) into a
> different printer, this time connected to a computer, and sending the
> file from it, which worked just fine. My guess is that the first
> print
iginal email. Yes, MuPDF shows the complete file without
any problem, all letters and numbers are there, as well as in the
printout I got from printing from a coworker computer (Devuan) to their
printer.
Ángel
___
If you
On 9/26/2022 4:06 PM, Angel M Alganza via ntg-context wrote:
Hello,
I have a document that includes some grids (drawn with \grid) as well as
alphanumeric information (letters and numbers) which contents (the info,
not the grids) I modify every year and then print it out. I've been
usi
Hello,
I have a document that includes some grids (drawn with \grid) as well as
alphanumeric information (letters and numbers) which contents (the info,
not the grids) I modify every year and then print it out. I've been
using it without any problem for a few (maybe 4 or 5) years but, this
.imgur.com/CRaam.png
I've tweaked some numbers to get a pretty decent result for this particular
font:
\starttext
M{\dontleavehmode{\raisebox{.45ex}\hbox{\scale[sx=1.1,sy=1.1]{c\hskip-1ex
{\dontleavehmode{\raisebox{0ex}\hbox{\hl[.4]}}Anulty
Mc̲A
sing?
Jethro
> On 21 Aug 2022, at 4:41 PM, Pablo Rodriguez via ntg-context
> wrote:
>
> On 8/18/22 02:13, jethro Reuel via ntg-context wrote:
>> Hello,
>>
>> I am trying to put multiple PDF’s that were typeset differently into
>> one document without modi
odriguez via ntg-context
> wrote:
>
> On 8/18/22 02:13, jethro Reuel via ntg-context wrote:
>> Hello,
>>
>> I am trying to put multiple PDF’s that were typeset differently into
>> one document without modifying the individual files themselves.
>> [...]
>>
xt <
ntg-context@ntg.nl> wrote:
On 8/18/22 02:13, jethro Reuel via ntg-context wrote:
Hello,
I am trying to put multiple PDF’s that were typeset differently into
one document without modifying the individual files themselves.
[...]
The problem is the original page numbers show and I’d prefer
On 8/18/22 02:13, jethro Reuel via ntg-context wrote:
> Hello,
>
> I am trying to put multiple PDF’s that were typeset differently into
> one document without modifying the individual files themselves.
> [...]
> The problem is the original page numbers show and I’d prefer that
Hello,
I am trying to put multiple PDF’s that were typeset differently into one
document without modifying the individual files themselves. I came up with this:
\starttext
\copypages[ass1.pdf][][scale=950]
\copypages[ass2.pdf][][scale=950]
…
stoptext
The problem is the original page numbers
ue (1, 2) you'll also see node numbers
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl |
Hi Mikael,
Thank you for your reply. For the time being I am not in a hurry to solve the
issue with placeformula (when the numbers are on the right, there is no
problem…).
Best regards: Otared
> On 12 Jul 2022, at 23:08, Mikael Sundqvist via ntg-context
> wrote:
> […]
>
On Tue, Jul 12, 2022 at 6:34 PM Otared Kavian via ntg-context
wrote:
>
> Dear Hans, dear Mikael,
>
> In my experiments with the new math engine, I noticed that there is an issue
> with \placeformula when one sets the location of the numbers on the left: the
> number is
Dear Hans, dear Mikael,
In my experiments with the new math engine, I noticed that there is an issue
with \placeformula when one sets the location of the numbers on the left: the
number is one line above the formula. Here is a minimal example:
% begin bug-placeformula-left.tex
\setupformulas
letters and my
> > subsections with Arabic numbers. So far, no joy. What am I missing?
> >
> > Alan
> >
> > Mwe: with ConText ver: 2022.01.21 20:13 LMTX fmt: 2022.2.1. (The
> > problem persists when I run ConTeXt online)
> >
> > \setuphead[s
Am 10.07.22 um 00:35 schrieb Alan Bowen via ntg-context:
I’m trying to get my sections numbered with capital letters and my
subsections with Arabic numbers. So far, no joy. What am I missing?
Alan
Mwe: with ConText ver: 2022.01.21 20:13 LMTX fmt: 2022.2.1. (The
problem persists when I run
201 - 300 of 1014 matches
Mail list logo
