(t) module if needed. In
any case, also check if things work with mkiv.
I tested the example on mkiv, I got error that dipchip and fliflop JK are not defined.
The file compiles if I comment those out. But in LMTX, I also get a "missing
semicolon" error. There is also this warning,
eeded. In
> any case, also check if things work with mkiv.
I tested the example on mkiv, I got error that dipchip and fliflop JK are not
defined. The file compiles if I comment those out. But in LMTX, I also get a
"missing semicolon" error. There is also this warning, which may have s
On 12/1/21 2:03 PM, Denis Maier via ntg-context wrote:
> Sorry for spamming the list, but I was able to narrow it further down:
> [...]
> \setupinteraction
> [state=start,
>openaction=FitWidth] % comment this out to make it work
> [...]
> Can anyone confirm this?
Hi
On 12/1/2021 2:03 PM, denis.ma...@unibe.ch wrote:
Sorry for spamming the list, but I was able to narrow it further down:
%
\setupinteraction
[
state=start,
openaction=FitWidth, % comment this out to make it work
]
\starttext
asdf
Sorry for spamming the list, but I was able to narrow it further down:
%
\setupinteraction
[
state=start,
openaction=FitWidth, % comment this out to make it work
]
\starttext
asdf
\stoptext
%
Can anyone confirm
; > \setlayer[mwe] { \switchtobodyfont[chancery,8pt] \hskip 5mm Chancery
> > Font Here }
> > \setupbackgrounds[page][background=mwe]
> >
> > \starttext
> > Normal font text goes here. \blank[4*big]
> > { \switchtobodyfo
that if I comment out the \type{setlayer[mwe]} in the source
file, then the above will print in Chancery.
\stoptext
I'd like to have the layers in Chancery font and then one last text string in
the body in Chancery font. But I can't get them both to be Chancery
Font
Here }
\setupbackgrounds[page][background=mwe]
\starttext
Normal font text goes here. \blank[4*big]
{ \switchtobodyfont[chancery] This should be Chancery here to. But isn't. }
\blank[2*big]Note that if I comment out the \type{setlayer[mwe
% comment out
%\stopbackmatter % comment out
\stoptext/
/
/
Uncommenting lines 8 and 9 causes the section numbers to disappear.
Is this normal behavior? Why does the presence of backmatter affect my
sections like this?
technically there can be many so called sectionblocks in any order and
as one
Dear All,
I've noticed that the mere presence of backmatter prevents my sections from
being numbered. Consider the following:
*\starttext\startsection[ title={Create Serverless
Applications},]blablabla\stopsection%\startbackmatter % comment
out%\stopbackmatter % comment out\stoptext
ARABICFONT
خَ % a
خَل
% \stopTEXpage
\stoptext
==
Three bugs:
I. If we use start|stoptex and comment start|stopTeXpage, then both
lines 19 and 21 give an error:
===
tex error > tex error on line 20 in file ./test.tex:
lua error:
callback error: [string
&qu
]
% \setupinterlinespace[line=4.2ex]
\starttext
% \startTEXpage[offset=1ex]
\setupdirections[bidi=global,method=one]
\righttoleft
\ARABICFONT
خَ % a
خَل
% \stopTEXpage
\stoptext
==
Three bugs:
I. If we use start|stoptex and comment start|stopTeXpage, then both
lines 19 and 21 give
]
\righttoleft
\ARABICFONT
خَ % a
خَل
% \stopTEXpage
\stoptext
==
Three bugs:
I. If we use start|stoptex and comment start|stopTeXpage, then both lines
19 and 21 give an error:
===
tex error > tex error on line 20 in file ./test.tex:
lua error:
callback error: [str
in c:\wscite and copied there the scite\context
folder; I added the folder to the PATH.
If I comment the line (import context/scite-context-user) at the end of
SciteGlobalproperties I can load .lua, .tex, .py files and I get the
colours highlighting.
But if I uncomment: first I have Scite
and copied there the
scite\context folder; I added the folder to the PATH.
If I comment the line (import
context/scite-context-user) at the end of SciteGlobalproperties
I can load .lua, .tex, .py files and I get the colours
highlighting.
But if I
{bb}.}
\stopTEXpage
should produce:
Paragraph *¶ 1
*Paragraph *¶ 2*
Paragraph *¶ 3*
1: 1
2: 2
I: Vide paragraphum I.
II: Vide paragraphum II.
but this fails without an existing good tuc file. If I comment out the
two latin lines, compile (to failure), and then uncomment the lines and
s, but if I include the link in my real document, I’am getting
> > > this error message (copied from -error.log):
> > > [...]
> > > Two things seemed to make it work:
> > > 1. Remove the link.
> > > 2. Comment out \expandUx in this setup:
> >
> > Hi De
cument, I’am getting
> > this error message (copied from -error.log):
> > [...]
> > Two things seemed to make it work:
> > 1. Remove the link.
> > 2. Comment out \expandUx in this setup:
>
> Hi Denis,
>
> in my environments to typeset XML sources, I n
; error message (copied from -error.log):
> [...]
> Two things seemed to make it work:
> 1. Remove the link.
> 2. Comment out \expandUx in this setup:
Hi Denis,
in my environments to typeset XML sources, I never need \expandUx, why
do you needit?
Another approach (I don’t know whether
ot;lasttexerror"]="Missing number, treated as zero",
["lasttexhelp"]="A number should have been here; I inserted '0'. (If you can't
figure out why I\nneeded to see a number, look up 'weird error' in the index to
The TeXbook.)",
["linenumber"]=9,
[&quo
lue how viewers and
>>> printers react (so if something would be added/changed it would be option
>>> driven)
>> I wouldn’t expect printers (office printing devices) to react at all; I hope
>> that printers (printshop workers) will react positively to correct
he following comment was posted:
https://github.com/utmapp/UTM/issues/2280#issuecomment-945006193
and I discovered that an upgrade (still in beta) of the VM software
I'm using addressed two burning issues at the same time:
- they claim to have fixed some IPv6-related bug (and the network
magically
On 10/13/2021 10:37 PM, jbf via ntg-context wrote:
In fact, Hans, that was going to be my comment after updating yesterday
to the 10-10-21 version: some of the breaks were a bit overdone. Are
these changes you indicate as tests actually included in the latest
upload, or should I wait a bit
In fact, Hans, that was going to be my comment after updating yesterday
to the 10-10-21 version: some of the breaks were a bit overdone. Are
these changes you indicate as tests actually included in the latest
upload, or should I wait a bit?
Julian
On 14/10/21 2:34 am, Hans Hagen via ntg
ed/changed it would be option driven)
I wouldn’t expect printers (office printing devices) to react at all; I hope
that printers (printshop workers) will react positively to correct boxes in our
PDFs ;)
oh, i'm often surprised about printing houses .. (the best were some
comment on a file havi
t;
> \expanded{\abbreviation[\currentbtxtag]{\textcite[alternative=shorthand,lefttext=,righttext=][\currentbtxtag]}{\textcite[alternative=listsubcite,lefttext=,righttext=][\currentbtxtag]}}
> > ```
> >
> > Again, this works, although I'm still not sure
istsubcite,lefttext=,righttext=][\currentbtxtag]}}
```
Again, this works, although I'm still not sure why
invoking \texdefinition{btx:sbl:inline:shorthand} directly doesn't.
I leave it to Alan to comment on this as he's the bib
'/home/me/bin/context/tex/texmf-linux-64/bin/mtxrun --autogenerate
--script context --autopdf=okular "%f"'
So, following your logic, I should then only need to add, further
on, pdfview.method = "okular", which I have done, but still no joy.
In such a case, yo
dd, further on,
> pdfview.method = "okular", which I have done, but still no joy.
>
> In such a case, you only need to comment on the second option, i. e.
Sumatra:
--The last one wins
pdfview.method = "okular"
--pdfview.method = "sumatra"
opformula]])
>
> fails in LMTX with an error message:
>
> tex error > tex error on line 3 in file ./test.tex: Undefined
> control sequence \undefined
>
> MWE:
>
> \startluacode
> thirddata = thirddata or {}
>
> local comment = [[
>
opformula]])
> >
> > fails in LMTX with an error message:
> >
> > tex error > tex error on line 3 in file ./test.tex: Undefined control
> > sequence \undefined
> >
> > MWE:
> >
> > \startluacode
> >thirddata = thirddata or
ror on line 3 in file ./test.tex: Undefined control
sequence \undefined
MWE:
\startluacode
thirddata = thirddata or {}
local comment = [[
This is a famous formula
\startformula
a^2 + b^2 = c^2
\stopformula
]]
function thirddata.explanation()
context(comm
nce \undefined
MWE:
\startluacode
thirddata = thirddata or {}
local comment = [[
This is a famous formula
\startformula
a^2 + b^2 = c^2
\stopformula
]]
function thirddata.explanation()
context(comment)
end
\stopluacode
\starttext
\ctxlua{thirddata.explanat
TEXMFCACHE to contain
/var/opt/texlive first and then also an individual directory under $HOME.
When I run context under my personal account, it only uses the second.
I assume that's because I may not write under the first. There's a comment
in texmfcnf.lua about that.
Does it perhaps make no sense at
oduced to the code.
Should it be a concern? If so, where should I look to remedy it?
mwe ...
Here it is:
\setuptagging [state=start]
\starttext
The problem involves tagging.
\stoptext
i'll comment the message ... some synchronization is tricky so when
there is a real issue we'l
. \ifinstance) can be used to set
the start/stop command for the buffer.
\protected\def\startnamedtyping[#1]%
{\instancefalse\buff_verbatim_typing_start{#1}}
i noticed that we had a comment about startnamedtyping ...
makes me wonder, are there more instance commands that we need to extend
gma-pod.nl
-
if not modules then modules = { } end modules ['lang-rep'] = {
version = 1.001,
comment = "companion to lang-rep.mkiv",
author= "Hans Hagen, PRAGMA-ADE, Hasselt NL",
copyright = "PRAGMA ADE / Con
Here is an example to clarify my previous comment.
#+BEGIN_SRC xml
reviewed
translated
Bonjour
On 7/15/21 11:10 PM, Jairo A. del Rio wrote:
Hi, list! Is this already fixed in a new upload? I'm compiling old
documents and having the same problem as Thomas, although Wolfgang's
comment fixes it nicely.
Cordially,
There hasn't been a new upload since I asked my question, so for the
time
Hi, list! Is this already fixed in a new upload? I'm compiling old
documents and having the same problem as Thomas, although Wolfgang's
comment fixes it nicely.
Cordially,
Jairo
El lun, 12 de jul. de 2021 a la(s) 11:18, Wolfgang Schuster (
wolfgang.schuster.li...@gmail.com) escribió:
> Tho
1
The 8 following pages provide a quick visual overview of the 28 topics
that will be detailed in "part 2" and "part 4".
Links help the reader to go on the associated pages (markup or
typesetting)
Any comment or idea is welcome.
__
e=11
The 8 following pages provide a quick visual overview of the 28 topics
that will be detailed in "part 2" and "part 4".
Links help the reader to go on the associated pages (markup or typesetting)
Any comment or idea is welcome.
___
, Beethoven wählt
einen Dreiertakt, Mozarts Romanze ist ein 3/8-Takt, Beethoven wählt
einen 2/4,
Mozarts Rondo ist eine Gavotte im 2/2-Takt, Beethoven schreibt ein
Jagdrondo im 6/8-Takt.
\stoptext
If I comment out the part [features=f:onum], I get the fractions that
I'm looking for, but it seems
ist ein 3/8-Takt, Beethoven wählt
einen 2/4,
Mozarts Rondo ist eine Gavotte im 2/2-Takt, Beethoven schreibt ein
Jagdrondo im 6/8-Takt.
\stoptext
If I comment out the part [features=f:onum], I get the fractions that
I'm looking for, but it seems that I can't get the same effect
}\btxperiod
> > \stopsetups
> >
> > ```
> > In the setup and definition, the fields I defined do get into the
> > citation correctly, but the authorconversion remains 'normal'. If I
> > comment out the lines which set up 'normal' authorconversion for the
&
, the fields I defined do get into the
citation correctly, but the authorconversion remains 'normal'. If I
comment out the lines which set up 'normal' authorconversion for the
list, everything, including the bibliography and 'entry' type
citations get 'normalshort'. Is that a bug or am I missing
setup and definition, the fields I defined do get into the
citation correctly, but the authorconversion remains 'normal'. If I
comment out the lines which set up 'normal' authorconversion for the
list, everything, including the bibliography and 'entry' type
citations get 'normalshort'. Is that a bug o
I have probably 30 instances of it occurring
in a tightly-set bibliography. I would assume that it may occur in any
text, but have not noticed it in the body of my book.
I have created an example document that shows it. The problem disappears
if bidi is turned off (comment out the first non-c
urring
in a tightly-set bibliography. I would assume that it may occur in any
text, but have not noticed it in the body of my book.
I have created an example document that shows it. The problem disappears
if bidi is turned off (comment out the first non-comment line) but of
course then the RT
@resources{\pdfbackendcurrentresources}
As mentioned in a comment in back-pdf.mkxl, the command is implemented in
lua in lpdf-ini.lmt.
The command is also used in mlib-pps.mkxl and is documented in ConTeXts
interface. Can somebody tell why it is not expanded?
Any help is appreciated. Cheers,
(2) we have some
> (already) old hyphen patching code for messy fonts (which is kind of bad
> anyway).
>
> We actually want all these hyphens to have the right tounicode even if
> they share shapes (i already had some comment about looking into that
> but never ran into a font th
I’ll look into this, and post to the list once I’ve made the changes so others
can comment.
Denis
Von: ntg-context Im Auftrag von jethro Reuel
Gesendet: Mittwoch, 9. Juni 2021 14:49
An: mailing list for ConTeXt users
Betreff: Re: [NTG-context] Project structure: Specifying environment
button selects a region and copies the marked text
> > to the clipboard."
> >
> > Maybe this is broken (as Luigi suggests) or requires some special
> > setup/configuration?
> I was refereing to a textual copy, not an image one. So one selects
> 'abc'
(hyphens removed), comment
exceptions and see which one does the harm
all the rest is guesswork
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
\bTD
\field[lineField]
\eTD \eTR \eTABLE
\stoptext
This produces
Syntax Error: Form field child is not a dictionary
when you run pdfinfo on it, and Firefox can't properly render the forms
either. However, if you comment the lines defining the begin and end
of the TABLE, the form is
name = "consola",
version = "1.00",
comment = "",
author = "",
copyright = "",
remapping = {
tounicode = true,
unicodes = {
hyphen = 0x002D,
},
},
}
--- 8< --
yphen-minus
<https://unicode-table.com/en/002D/>:
beginbfchar
<015E> <002D>
endbfchar
I have tried with a goodies file, and an updated MWE:
--- 8< --
return {
name = "consola",
version = "1.00",
co
it occasionally, so
here is the
%D reminder).
I tried the mentioned local overload methods but didn't get them to work.
Did I mess up somehow or is the comment above outdated?
Are there any better ways - update-safe though?
Thanks a lot, Werner
Am 23.04.21 um 21:28 schrieb Hans Hagen:
You can
the mentioned local overload methods but didn't get them to work.
Did I mess up somehow or is the comment above outdated?
Are there any better ways - update-safe though?
Thanks a lot, Werner
Am 23.04.21 um 21:28 schrieb Hans Hagen:
You can put this on cont-new.mkxl as test:
\unprotect
\defcsname
else
on the list with time (in lockdown like I am) to put me right.
you need help from a linux expert indeed
Just a comment. I also experienced problems in Linux with --luatex some
days ago.
I got everything right with current latest (2021.05.27 14:15).
I would erase the cache and try it again
like I am) to put me right.
> you need help from a linux expert indeed
Just a comment. I also experienced problems in Linux with --luatex some
days ago.
I got everything right with current latest (2021.05.27 14:15).
I would erase the cache and try it again:
mtxrun --script cache --e
lease.
Thanks. I have updated to version 2021.05.23 and run `mtxrun
--generate`. Syntax highlighting is fine, but with LMTX I'm still
getting an en-dash. Below, a MWE.
Nicola
%
\usemodule[vim]
\startvimrc[name=pseudocode]
syntax keyword Statement while
syntax keyword Constant true
syntax
3-88, Vim is
> called with --clean. That option appears *after* -u, effectively
> overriding it. Moving --clean as the first option (or, better, removing
> it) solves my issue.
>
> Some remarks. The module has this comment:
>
>--clean % dont load scada [sic] file (nvim)
>
er* -u, effectively
overriding it. Moving --clean as the first option (or, better, removing
it) solves my issue.
Some remarks. The module has this comment:
--clean % dont load scada [sic] file (nvim)
If the purpose of the option is to avoid loading a shada file, `-i NONE`
(which is already there)
than one individual, e.g. across organization or even at a wider level
(think CSUR). I think that it is really important to assure that those
work. The breakage of cut and paste seems particularly bad.
You can try to patch luaotfload. Locate the 'report' line and comment
those two as below.
which he added a Special Comment
menu item for « % !TEX useOldSyncParser ».
The ConTeXt code for synctex used to work fine, but beginning last year (if I
remember well) the behaviour became somewhat unstable (again on my machine). It
seems that the content which goes on the first page of the PDF
again).
The renaming of bad glyphs can technically be fixed but a runtime hack
but i try to avoid that .. the more heuristics, the harder to fight.
You can try to patch luaotfload. Locate the 'report' line and comment
those two as below.
local length = read
ocal = resolvers.prefixes.selfautoparent();
texmflocal = string.gsub(texmflocal, "20%d%d$", "texmf-local");
return {
type= "configuration",
version = "1.1.0",
date= "2012-05-24",
time= "12:12:12",
= "english",
version= "1.00",
comment= "English ligature suppression",
author = "Mico Loretan, Dave Jarvis, & Hans Hagen",
copyright = "Public domain",
options= {
{
actions = {
stoptext
% EOF
Expected: Black circle, no border, comment lines ignored.
Actual: Empty square.
2. Transparent stroke
% SOF
\startbuffer[svg]
http://www.w3.org/2000/svg <http://www.w3.org/2000/svg>"
version="1.1">
\stopbuffer
\starttext
\placefigure{}{\includesvgbuffe
Issues encountered with version 2021.03.31 18:04.
1. Comments in SVG
% SOF
\startbuffer[svg]
http://www.w3.org/2000/svg;>
\stopbuffer
\starttext
\placefigure{}{\includesvgbuffer[svg][conversion=mp]}
\stoptext
% EOF
Expected: Black circle, no border, comment lines ignored.
Actual: Em
sur… » (I don't know exactly how to translate
it in English. Something like "an overview of…") so quoting it makes
only sense if the issue is named, at best after the title or the number.
I thought issue may do it. Am I right? Or would be comment a better
place?
Best rega
e the main article
is always named « Le point sur… » (I don't know exactly how to translate
it in English. Something like "an overview of…") so quoting it makes
only sense if the issue is named, at best after the title or the number.
I thought issue may do it. Am I right? Or would be co
t; wrote:
>> >
>> > On 12/25/2020 9:47 PM, Christoph Reller wrote:
>> > > Hi,
>> > >
>> > > Consider the following MWE:
>> > >
>> > > \definefloat[combination][figure]
>> >
with
\startplacefigure but none of these gives a centered circular shape.
Also I noticed that if one removes the comment at the end of
\startshapedparagraph, or add a blank line after that, then the circular shape
is destroyed: is this on purpose ?
\starttext
\startuseMPgraphic{circleBis}
lmt_parshape
circular shape.
Also I noticed that if one removes the comment at the end of
\startshapedparagraph, or add a blank line after that, then the circular shape
is destroyed: is this on purpose ?
Best regards: Otared
% begin example-circular-shape.tex
\starttext
%\startuseMPgraphic{circle
[author: Andrej Arrow] [journal: MAPS]
> [keywords: context] [pages: 2-8] [title: The Font Name Mess] [volume: 40]
> [year: 2010]
>
> If I remove or comment that entry out, then the bibliography renders OK
> (copy from pdf): 1 A. Arrow, “The Font Name Mess”, *MAPS *40, 2-8, 2010.
>
> m
: MAPS]
[keywords: context] [pages: 2-8] [title: The Font Name Mess] [volume: 40]
[year: 2010]
If I remove or comment that entry out, then the bibliography renders OK
(copy from pdf): 1 A. Arrow, “The Font Name Mess”, *MAPS *40, 2-8, 2010.
my .tex source is:
% \setupbackend[export=example.xml,css
Hi
On Wed, 2021-02-24 at 15:16 +0100, Christoph Hintermüller wrote:
>
>
> I hoped so too. But the only i figured that it stops between two
> sections. If i comment the whole set of sections which seem to
> contain
> offending content. Than it simply stops at some later s
want to make it public anyway, but if required i can provide a
> > share
> > link.
>
> You can try to comment some code to see where it fails/succeeds: make
> a
> copy and start wiping stuff. Normally that quickly reveals where it
> goes
> wrong.
>
I hoped so too.
On 2/24/2021 10:42 AM, Christoph Hintermüller wrote:
I'm sorry to be so clue less to not be able to provide more
information. The document it self is too big to be posted and i do not
want to make it public anyway, but if required i can provide a share
link.
You can try to comment some code
on.action
>>> 18 local conversion = specification.conversion or
>>> "Characters"
>>> 19
>>> 20 local n = #pattern
>>&g
ters"
>> 19
>> 20 local n = #pattern
>> 21
>> 22 -- context.startxtable { align = "middle,lohi", width =
>> "0.8cm",
>> 23 >> offset = "0.8ex", bodyfont = "9pt", framecolor = "cyan"
.action
> 18 local conversion = specification.conversion or "Characters"
> 19
> 20 local n = #pattern
> 21
> 22 -- context.startxtable { align = "middle,lohi", width =
> "0.8cm",
> 23 >> offset = "0.8ex",
On 2/17/2021 12:18 AM, Jairo A. del Rio wrote:
I've copied the following example from the ConTeXt archive:
there is a comment in the code
-- todo: anchor, page
so i'll look into it (not hard to fix)
in lmtx i want to add some more natural helpers to the interface; part
of also updating
given me! I have
difficulty understanding your comment 'This is not interfaced via
setuphead *or* setuplangauge *or* because the converter is not
configured that way'. The 'or' throws me out, I'm afraid. Were you
going to suggest somewhere else?
I assumed that I would need to add \def
On 2/11/2021 9:20 AM, jbf wrote:
I appreciate the response.
However, you are light years ahead of me in understanding ConTeXt, so I
don't quite know what to do with the info you have given me! I have
difficulty understanding your comment 'This is not interfaced via
setuphead
I appreciate the response.
However, you are light years ahead of me in understanding ConTeXt, so I
don't quite know what to do with the info you have given me! I have
difficulty understanding your comment 'This is not interfaced via
setuphead *or* setuplangauge *or* because the converter
On 1/14/2021 10:44 AM, Henning Hraban Ramm wrote:
Hi again,
the following example used to work with LMTX (but not MkIV) from September.
Now I get the "narrower" indentation only if I comment the first line (in both
versions) – apparently there’s a setup conflict, and I don’t know an
> Am 14.01.2021 um 10:44 schrieb Henning Hraban Ramm :
>
> Hi again,
> the following example used to work with LMTX (but not MkIV) from September.
>
> Now I get the "narrower" indentation only if I comment the first line (in
> both versions) – apparently there’
Hi again,
the following example used to work with LMTX (but not MkIV) from September.
Now I get the "narrower" indentation only if I comment the first line (in both
versions) – apparently there’s a setup conflict, and I don’t know any more why
I needed this setup.
Could you ex
You would set DIGESTIF_TEXMF to the (list of) directory(ies) containing
the ls-R file(s).
However, I gather from Hans's comment that lmtx does not have the ls-R
files. So something lmtx-specific has to be added to Digestif.
Best,
Augusto
On Sun, Jan 3, 2021 at 11:21, Saša Janiška wrote
On Sat, Dec 26, 2020 at 10:54 AM Hans Hagen wrote:
> On 12/25/2020 9:47 PM, Christoph Reller wrote:
> > Hi,
> >
> > Consider the following MWE:
> >
> > \definefloat[combination][figure]
> > \setupcaptions[
> >number=no, %<- comment and table
On 12/25/2020 9:47 PM, Christoph Reller wrote:
Hi,
Consider the following MWE:
\definefloat[combination][figure]
\setupcaptions[
number=no, %<- comment and table appears
align=flushright]
\starttext
\startplacecombination[title=Combination]
\startfloatcombination
\startplaceta
Hi,
Consider the following MWE:
\definefloat[combination][figure]
\setupcaptions[
number=no, %<- comment and table appears
align=flushright]
\starttext
\startplacecombination[title=Combination]
\startfloatcombination
\startplacetable%[title=Table] %<- uncomment and table a
Hi,
I finally decided to start an experiment that I had on my todo list for
a while: dynamically scaling fonts. Below is an example of usage (plus
some comment). In that example some 2*200 different font sizes are used
which in mkiv demands 400 font definitions. This costs time and memory
Nice. It works again. Thank you very much!
Cordially,
Jairo
El lun., 21 de dic. de 2020 2:45 a. m., Hans Hagen
escribió:
> On 12/21/2020 4:46 AM, Jairo A. del Rio wrote:
> > While shading works with MkIV, with LMTX the following breaks:
> >
> >
> > \startMPpage
On 12/21/2020 4:46 AM, Jairo A. del Rio wrote:
While shading works with MkIV, with LMTX the following breaks:
\startMPpage
comment("two shades with named colors");
fill fullcircle scaled 5cm
withshademethod "circular"
withshadecolors ((1,0,0),(0,0,1,0))
;
fill f
While shading works with MkIV, with LMTX the following breaks:
\startMPpage
comment("two shades with named colors");
fill fullcircle scaled 5cm
withshademethod "circular"
withshadecolors ((1,0,0),(0,0,1,0))
;
fill fullcircle scaled 5cm shifted (6cm,0)
withshademethod &
nest, no one ever came up with a project that had
> any real demands on the engine that could not be met (the fact that
> tex is a good solution for rendering doesn't mean that there is
> demand for it ... it is seldom on the radar of those who deal with
> that, who then often prefer s
201 - 300 of 2237 matches
Mail list logo
