On 9/18/2023 3:58 PM, Michael Loescher wrote:
There seems to be something wrong with the \type command.
MWE:
\starttext
\type{hello}
\stoptext
gives an error:
tex error > tex error on line 2 in file Z:/test.tex: Control
sequence expected instead of undefined
what platform?
looks l
There seems to be something wrong with the \type command.
MWE:
\starttext
\type{hello}
\stoptext
gives an error:
tex error > tex error on line 2 in file Z:/test.tex: Control sequence
expected instead of undefined
\buff_verbatim_type_normal
#1->\buff_verbatim_initialize_ty
:\crlfit looks like \type{\rotate[]{}} kills the definition of boxtitlecolor.Changing the names of the titlecolor/framecolor definitions makes no difference.\crlfWhy is this? ConTeXt error?\blank\boxfigure{test}{norotation: title color is blue}\blank\boxfigurerotate{test}{rotation: title color should
for ebgaramonditalic
but not for ebgaramondregular.
How do I fix it?
I'm using ConTeXt version: 2023.08.27 13:48
\startluacode
fonts.handlers.otf.addfeature {
name = "kernit",
type = "kern",
nocheck = true,
data = {
[0x27E8]
Dear List
In the MWE below, the kerning feature works OK for ebgaramonditalic
but not for ebgaramondregular.
How do I fix it?
I'm using ConTeXt version: 2023.08.27 13:48
\startluacode
fonts.handlers.otf.addfeature {
name = "kernit",
type = "kern",
ion (page 31):
> \xmlfilter{#1}{./node[@type=="cleanup"]}
> It should select among the 's those with .
> However, this node is not selected in the call to \xmlfilter.
> Where am I wrong?
>
> MWE follows
>
>
> % failure to typeset attribute selected.
> \set
This line of code comes from the xml documentation (page 31):
\xmlfilter{#1}{./node[@type=="cleanup"]}
It should select among the 's those with .
However, this node is not selected in the call to \xmlfilter.
Where am I wrong?
MWE follows
% failure to typeset attribute selected.
\setu
Mathias' minion.lfg (and associated
type-imp-minion) until just now, had to figure it all out from scratch from
demo.lfg and lm.lfg templates -)
(OTOH, had previously seen yours and Mikael's sophisticated minion-math.lfg)
I think that my version is/will be more complete - except for mathemat
heading. With this type of formatting any "continued" marks
would look weird.
--
Regards,
Alexey Kryukov
Moscow State University
Faculty of History
___
If your question is of interest to others as well,
(not figures.getinfo2)
figures.getinfo2 = function(name, page) -- [ [NTG-context] Pdf info with
Lua/Ctx API ]
if type(name) == "string" then
name = { name = name, page = page }
end
if name.name then
local data = figures.push(name)
local info = figures.identify()
iption = "test",
manipulators = {
base = squeeze,
node = squeeze,
}
}
fonts.handlers.otf.features.register(specification)
fonts.handlers.otf.addfeature {
name = "stest",
type = "substitution",
data = {
a = "X",
of the
\everyinitializeverbatim register because it is used for
inline and display verbatim. A better place to add the option is
\buff_verbatim_initialize_typing_two for \starttyping
and \buff_verbatim_initialize_type_two for \type.
ok
e 12pt roman
%D bodyfont.
-)
> well, in type-imp-latinmodern.mkiv i can find 'designsize' ... you're
> not relying on some gpt driven search machine are you?
No just the search files feature in Notepad++ -)
Ok, looking at type-imp-latinmodern.mkiv, under latin-modern-designsize, I see
the design size typescript
Ok, where is that design size typescript? A search for, e.g., lmroman8-regular
etc. in
texmf-context/tex/context/base/mkiv
yields no results, so it must be defined at some higher level of abstraction..
well, in type-imp-latinmodern.mkiv i can find 'designsize
objectcompresslevel 3
mkiv lua stats > positions: 311 collected, 0 deltas, 307 shared partials, 133
partial entries
mkiv lua stats > cross referencing: 713 identified, 269 unknown
mkiv lua stats > used platform: linux-64, type: unix, binary subtree:
texmf-linux-64
mkiv lua stats >
الْأَسْمَرُ السَّرِيعُ يَقْفِزُ فَوْقَ الْكَلْبِ الْكَسُولِ!
The quick brown fox jumps over the lazy dog!
\stoplines
\stopbuffer
{\tfxx \type{\tfxx} \getbuffer}
{\tfx \type{\tfx} \getbuffer}
\type{\tf} \getbuffer
{\tfa \type{\tfa} \getbuffer}
{\tfb \type{\tfb} \getbuffer}
{\tfc \type{\tfc} \getbuffer
oesn't scale the
\symbol, although \tfa and higher do work.
I guess fixing \tfx-symbol interaction will be part of your conversation with
Wolfgang -)
> well, you wented symbols so
Ultimately I just want to be able to type the Unicode symbols for 02BE and 02BF
-- ʾ and ʿ -- and get prope
-ade.nl | www.pragma-pod.nl
-
\unprotect \pushoverloadmode
\appendtoks
\frozen\instance\protected\edefcsname\e!type\currentbuffer\endcsname
{\buff_verbatim_type_defined_buffer[\currentbuffer][\currentdefinedbuffer
Am 29.07.23 um 22:49 schrieb Max Chernoff:
I'm on mobile now so I can't type out a complete solution, but I think that
what you're looking for is in this file:
https://github.com/gucci-on-fleek/unnamed-emoji/blob/master/documentation/unemoji-manual.mkxl
It doesn't exactly do what you
I'm on mobile now so I can't type out a complete solution, but I think that
what you're looking for is in this file:
https://github.com/gucci-on-fleek/unnamed-emoji/blob/master/documentation/unemoji-manual.mkxl
It doesn't exactly do what you specifically asked for, but I think that it's
reference (save it as main.tex):
\starttext
\dorecurse{15}
{\chapter[chap\recurselevel]{Chapter}}
\stoptext
You have the file that reads the references from main.tuc and generates
the inter-document links:
\setupinteraction[state=start]
\starttext
Links to each chapter using
}
\dorecurse{4}{\samplefile{tufte}\par}
}
\stoptext
\stopbuffer
\startplacefigure[location=here,reference=fig:vz-1,title={Cheating with
vertical expansion: \type {[vz=no]}.}]
\startcombination[4*1]
{\typesetbuffer[vz-1][width=\combinationwidth,page=1,frame=on]} {}
{\typesetbuffer[vz-1
; > > [file:LucidaBrightDemiBold]
> > > > > > \definefontsynonym[LucidaBrightDemiItalic]
> > > > > > [file:LucidaBrightDemiItalic]
> > > > > > \stoptypescript
> > > > > Hm, isn't that this lucida rip off again? Ma
; > > \stoptypescript
> > > > Hm, isn't that this lucida rip off again? Maybe bad metricks then but
> > > > I'm
> > > > not going to look into that as the official TUG lucida opentype fonts
> > > > perform okay.
> > > >
> > >
ynonym[LucidaBrightDemiItalic]
> > > > [file:LucidaBrightDemiItalic]
> > > > \stoptypescript
> > > Hm, isn't that this lucida rip off again? Maybe bad metricks then but I'm
> > > not going to look into that as the official TUG lucida opentype fonts
&
. And a guess. Bad metrics is not the
culprit
if it were true, the same problem would be under lualatex, correct?
well, who knows what (me)tricks those fonts have embedded .. are these
the official TUG lucida open type fonts? if so,
\setupbodyfont[lucida]
should just work (btw, you also don't set up
0
530329
0
system > ptr 50218 10054 50201
565577 0 0 0 0 0 0
7 0 0 7
system > top 50219806398 131074 14831
573482156 36
rowfill
like:
\frozen \instance \def \rightarrowfill \mathfiller {8594}
It depends on what you expect. First of all, your assumption that the arrow
fill is the same as in plain tex is wrong.
Why would it be wrong?
because context is not plain
When I type
\hbox to 3cm{\rightarrowfill} witho
ed. No trick involved. But as it
> uses a specific mechanism in an hbox you need to trigger that (unless you
> want to add overhead that will kake tex crawl).
>
> > Like a magician… now all of a sudden evetything works, but unlike TeX's
>
> Not sure what this refers to. Muc
interesting article:
https://futuress.org/stories/arabic-typography/amp/
HR
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl /
substitution
does in open type). That might eventually in the engine lead to mapping
glyphs or snippets but the resulting node lists is what the engine then
carries on.
Bottom line is that the production-ready part is an obvious byproduct
of its short lifespan, but one cannot be making the
it nor number of copies
limit as far as I can see - just one eBook licence per title.
Maybe there will be VAT etc added when you get to checkout - I didn't go that
far.
Yes, but it smells a bit like some clone. I have an official optima nova
cd (in type one format, i can't afford the opentype rig
om: Aditya Mahajan
To: Aditya Mahajan via ntg-context
Subject: Re: [NTG-context] TiKz with LMTX
Message-ID:
Content-Type: text/plain; charset="iso-8859-15"
On Mon, 5 Jun 2023, Aditya Mahajan via ntg-context wrote:
> On Sun, 4 Jun 2023, Jig? via ntg-context wrote:
>
>
>
kiv lua stats > loaded patterns: en::1, load time: 0.000
mkiv lua stats > loaded fonts: 2 files: latinmodern-math.otf,
lmroman10-regular.otf
mkiv lua stats > font engine: otf 3.133, afm 1.513, tfm 1.000, 7
instances, 3 shared in backend, 3 common vectors, 0 common hashes, load
with ConTeXt
are great), but I was used to printing books with an old Type-1 Minion
(www.ctan.org/pkg/w-a-schmidt) and find it hard to accept that this
should not be possible with the
modern flavours of TeX.
My system:
This is LuaTeX, Version 1.16.0 (TeX Live 2023/Arch Linux)
open source > le
to printing books with an old Type-1 Minion
(www.ctan.org/pkg/w-a-schmidt) and find it hard to accept that this
should not be possible with the
modern flavours of TeX.
My system:
This is LuaTeX, Version 1.16.0 (TeX Live 2023/Arch Linux)
open source > level 1, order 1, name
'/usr/share/texmf-d
age breaking changes. The
caption must stay within the type area – that works so far.
But it shouldn’t be necessary to define left/right manually, and that’s
my question: if these \doifs work correctly within a float
but ConTeXt gives the following error:
fonts > otf loading > loading 'Noto-COLRv1.ttf', hash
'noto-colrv1'
otf reader > table version 1 of 'colr' is partially supported for font
Noto-COLRv1.ttf
otf reader > unsupported colr type 2 paint format 0
ing > loading 'Noto-COLRv1.ttf', hash 'noto-colrv1'
otf reader > table version 1 of 'colr' is partially supported for font
Noto-COLRv1.ttf
otf reader > unsupported colr type 2 paint format 0
otf reader > unsupported colr type 2 paint format %i
otf reader
made their money by shoving down acroread all over. It's no secret
> Normally context will fall bakc on latin modern but when you explicitly load
> a font setup and that one doesn't have math fonts it will not be set up
I checked the type-imp-* file. Unicode-math from latex had no issues on
e are not than
> > manyu math fonts) one always has to match them properly with serif and sans
> > fonts (relative scaling etc).
> >
> > When someone wants support for some commercial font, they have to buy us a
> > few copies with no constraints. (Normally in a project we
nt, they have to buy us a
> few copies with no constraints. (Normally in a project we just get them
> anyway.) There are plenty of examples in the type-imp-* files that show the
> way.
>
> Hans
Thanks for the info Hans. I'll check it out again. About a month or
so ago I went over th
scaling etc).
When someone wants support for some commercial font, they have to buy us
a few copies with no constraints. (Normally in a project we just get
them anyway.) There are plenty of examples in the type-imp-* files that
show the way.
Hans
+0200
> From: Mikael Sundqvist
> To: mailing list for ConTeXt users
> Subject: Re: [NTG-context] This is rmally done by loading special math
> fonts into the math family slots.
> Message-ID:
> <
> cahy-ll9-tprwsutrnjh2qx5_pxdhgmgfvz+ckrfqv9eh88a...@mail.
context.tex'
setup > error in line 12, namespace 'fontinstanceready',
instance 'D', key 'no,'
open source > level 5, order 15, name
'/home/vm/context/tex/texmf-context/tex/context/fonts/mkiv/type-imp-plex.mkiv'
open source > level 6, order 16, name
'/home/vm/context/te
Hi Lynx,
> * How can I be sure that the standalone version is the one being
> implemented?
It depends on what your $PATH is set to. On Linux/macOS, you can run
$ type -ap context
to list all the ConTeXts in your $PTAH. The first one in that list is
the one that will
ugh then we can as well stick to 32K or
> 16K (for some even less). There's always Lua for unlimited storage of
> quantities.
>
> So,
>
> \newfloat\fooA
>
> \scratchdimen=123.456pt\relax[\type{dim:}
> \the\scratchdimen==123.456pt]\par
> \fooA=123.
umber of registers (currently 64K per
> category) because after all, if 64K is not enough then we can as well
> stick to 32K or 16K (for some even less). There's always Lua for
> unlimited storage of quantities.
>
> So,
>
> \newfloat\fooA
>
> \scratchdimen=123.456pt\rela
considering lowering the number of registers (currently 64K per
category) because after all, if 64K is not enough then we can as well
stick to 32K or 16K (for some even less). There's always Lua for
unlimited storage of quantities.
So,
\newfloat\fooA
\scratchdimen=123.456pt\relax[\type{dim
\currentitemnumber{}, the last one.
\setcounter[mynumber][\currentitemnumber]
\stopitemize
The \type{\getnumber[mynumber]} value is \getnumber[mynumber].
\incrementcounter[mynumber]
And now the big finish, start at \getnumber[mynumber]:
\startitemize[n][start=\getnumber[mynumber]] % WHY DOES THIS FAIL?
\item
[mynumber][]
\startitemize[n]
\item The first item.
\item The second item
\item Item number \currentitemnumber{}, the last one.
\setcounter[mynumber][\currentitemnumber]
\stopitemize
The \type{\getnumber[mynumber]} value is \getnumber[mynumber].
\incrementcounter[mynumber]
And now the big finish
later.
The idea behind it is to collect templates and examples that are
scattered all over the web or in the list threads. The first example
that comes to my mind is the type definition for a Roboto font I needed
and other type scripts that can be useful for the community
I've found the following Github repository with the typscripts definitions:
https://github.com/r3n4ud/roboto-context
When I use this type-imp-roboto.mkiv file fonts are used and embedded
when using Roboto in thes \setupbodyfont[].
When I use ebgaramond as the body font but use
Dear Hraban,
No, it does not. I am attaching hte type file and the short test document.
Here are the links where one can download the fonts:
https://github.com/googlefonts/roboto/releases
https://fonts.google.com/specimen/Roboto+Slab
I am wondering if 'hinted' or 'unhinted' release
files to the recommended directory
structure under: texmf-local/fonts/truetype.
** I've created a type-imp-roboto.mkiv file and saved it in the
recommended location under: texmf-local/tex/.../mkiv/.
Using: \usetypescript or \usetypescriptfile or \usebodyfont [roboto]
with setuphead does not work
files to the recommended directory
structure under: texmf-local/fonts/truetype.
** I've created a type-imp-roboto.mkiv file and saved it in the
recommended location under: texmf-local/tex/.../mkiv/.
Using: \usetypescript or \usetypescriptfile or \usebodyfont [roboto]
with setuphead does not work
texmf-local/fonts/truetype.
** I've created a type-imp-roboto.mkiv file and saved it in the recommended
location under: texmf-local/tex/.../mkiv/.
Using: \usetypescript or \usetypescriptfile or \usebodyfont [roboto] with
setuphead does not work.
I use the following simplest setup command:
\setuphead[c
will be to create a proper working
type-imp-roboto-flex.mkiv and type-imp-roboto.mkiv for the non-variable
font edtion to be more portable. Roboto is a very good font and is
recommended as a body font for presentations or headings, which made me
use in the first place.
I must admit that I am
One
> >> \stopitemize
>
> >> This paragraph should be indented - due to the blank line after
> >> \type{\stopitemize}.
>
> >> \startitemize
> >> \item Two
> >> \stopitemize
> >> This paragraph should not be indente
:
%
\setupindenting[medium,yes]
\setupitemize[indentnext=auto]
\startitemize
\item One
\stopitemize
This paragraph should be indented - due to the blank line after
\type{\stopitemize}.
\startitemize
im via ntg-context wrote:
> >>
> >>> %
> >>>
> >>> \setupindenting[medium,yes]
> >>> \setupitemize[indentnext=auto]
> >>>
> >>>\startitemize
> >>> \item One
> >&g
[indentnext=auto]
\startitemize
\item One
\stopitemize
This paragraph should be indented - due to the blank line after
\type{\stopitemize}.
\startitemize
\item Two
\stopitemize
This paragraph should not be indented
auto]
> >
> > \startitemize
> > \item One
> > \stopitemize
> >
> > This paragraph should be indented - due to the blank line after
> > \type{\stopitemize}.
> >
> > \startitem
llowing example:
>> %
>> \setupindenting[medium,yes]
>> \setupitemize[indentnext=auto]
>> \startitemize
>> \item One
>> \stopitemize
>> This paragraph should be indented - due to the blank line after
>> \type{\stopitemize}.
>> \sta
emize[indentnext=auto]
>
> \startitemize
> \item One
> \stopitemize
>
> This paragraph should be indented - due to the blank line after
> \type{\stopitemize}.
>
> \startitemize
> \item Two
>
llowing example:
>> %
>> \setupindenting[medium,yes]
>> \setupitemize[indentnext=auto]
>> \startitemize
>> \item One
>> \stopitemize
>> This paragraph should be indented - due to the blank line after
>> \type{\stopi
s]
> \setupitemize[indentnext=auto]
>
> \startitemize
> \item One
> \stopitemize
>
> This paragraph should be indented - due to the blank line after
> \type{\stopitemize}.
>
> \startitemize
> \item Two
>
be indented - due to the blank line after
\type{\stopitemize}.
\startitemize
\item Two
\stopitemize
This paragraph should not be indented.
%
Tragically, the paragraph which claims it should be indented
All the other wiki pages are outdated.
This is just a wild guess, so I may be very wrong here.
If this doesn't work, then what do you get when you run
type -ap context
type -ap luatex
type -ap texlua
type -ap luametatex
/full/path/to/texlive/2023/context --version
/full/path/to/co
tps://www.pragma-ade.nl / http://context.aanhet.net
> archive : https://bitbucket.org/phg/context-mirror/commits/
> wiki : https://contextgarden.net
>
> ___
ing did the trick , which I found it convenient really.
But I don't use math mode, although someone else might, it's intuitive, and
does the job
\startmidaligned
$\tfc a + \overbracket{b + c} + \underbracket{d + e} + \doublebracket{f + g} +
h$
\stopmidaligned
\startformula
\int_{\infty
to work, but does not adapt to \quotation{normal}
\type{\footnote} style/format customizations
\footnote[e]{E E E E}%
\high{\tx{,}}
\note[a]
\stoptext
It would be great if there were a command that treated a (some command like)
\note as a \footnote-equivalent command for typesetting purposes
tachments/20230401/1f8c6cc9/attachment-0001.pdf.
According to type-imp-concrete.mkiv, text has the feature boldened-10
applied to it.
Even with a variable font (which might not be the case in the link
above), extending the font fakes the bold, such as in:
\definefontfamily
[mainface]
If you talk about the math font, I do not see what you mean. Daniel
> > has worked a lot on his fonts, and they now work well.
> >
> >
> > indeed the body font is not concrete opentype math but it looks very
> > similar at first sight
>
> Hi Luigi,
>
&g
nd they now work well.
>
>
> indeed the body font is not concrete opentype math but it looks very
> similar at first sight
Hi Luigi,
according to type-imp-concrete.mkiv, Concrete-Math.otf seems to be only
used for the math font.
> here evince & mupdf are quite ok (evince somewhat bo
matism is to just start with
initex and implement from scratch.
In the above case: just add \type {foo} and you might see another font
you didn't ask for / set up.
I was actually thinking to ask you about that, and by falling back to cmr math
font that perhaps would expedite loading time along t
>
> \startitem
> After playing with math support for more than a year, we have
> come to the
> conclusion that it is time to move on. We have already discarded
> italic correction and now are replacing rules with extensibles. Much
> was already in
>
have come to the
>conclusion that it is time to move on. We have already discarded italic
>correction and now are replacing rules with extensibles. Much was already
> in
>place (and applied) but experiences with type one antykwas made us review
>some \OPENTYPE\ fonts.
eady discarded italic
correction and now are replacing rules with extensibles. Much was
already in
place (and applied) but experiences with type one antykwas made us
review
some \OPENTYPE\ fonts. Not using rules makes some of them look
better. The
effect is subtle and probably not
et it…» part the first thing I thought was: yeah, I'll
> > proceed by removing that file altogether and you'll forget it for sure .
>
> that message is part of 'reference tex the program' for over 40 years so if
> chatgpt would come up with it, it would do so by having parsed plenty of tex
it comes to answering
tex related questions chargpt is pretty unreliable, but that's another
topic)
But instaed I looked at it and though to myself «how much has changed?!» In
plain TeX (I have forgotten it a bit) but I can still type
> \par
> $test$
>
with the file specification as in:
> >
> >
> > \starttypescript [mylucidaserif] % or mylucidasans
> >\definefontsynonym[LucidaBrightRegular][file:LucidaBrightRegular]
> >\definefontsynonym[LucidaBrightItalic] [file:LucidaBrightItalic]
> >\defi
lic] [file:LucidaBrightItalic]
\definefontsynonym[LucidaBrightBold] [file:LucidaBrightDemiBold]
\stoptypescript
and \setups[font:fallback:serif:sans] wouldn't be needed either
you'd end up with
in mkxl (lmtx)
\setupbodyfont[lucida]
will load open type definitions
mkiv lua stats >
y days)
>
> what does
>
> mtxrun --generate --verbose
>
> report (whre does it fail)
>
> > 57 \starttext
> > 58
> > 59 \usetypescriptfile[type-lucida]
> > 60 \usetypescript[Lucida][texnansi]
> > 61 >> \setupbodyfont[MyLucida, 10p
y days)
>
> what does
>
> mtxrun --generate --verbose
>
> report (whre does it fail)
>
> > 57 \starttext
> > 58
> > 59 \usetypescriptfile[type-lucida]
> > 60 \usetypescript[Lucida][texnansi]
> > 61 >> \setupbodyfont[MyLucida, 10p
;:bq"
replace: |
\startblockquote
$|$
\stopblockquote
And this means all I have to do is type :bq and as you can sense from
the example above, I have the \start and \stop and intervening space all
ready to work with.
Hope it helps!
Julian
On 26
gt; \setupcaption[table][location=right,orientation=90]
>> \startplacetable
>> [location=middle,
>> reference=tab:papierformaten,
>> title={Standaardformaten}]
>> \rotate[rotation=90]{\externalfigure[Table1][type=buffer]}
>> \stopplacetable
fallback modern rm 12pt' is loaded
open source > level 2, order 3, name
'/usr/local/texlive/2023/texmf-dist/tex/context/fonts/mkiv/type-imp-lucida.mkiv'
close source> level 2, order 3, name
'/usr/local/texlive/2023/texmf-dist/tex/context/fonts/mkiv/type-imp-lucida.mkiv
and place it on
the right side?
My attempt:
\setupcaption[table][location=right,orientation=90]
\startplacetable
[location=middle,
reference=tab:papierformaten,
title={Standaardformaten}]
\rotate[rotation=90]{\externalfigure[Table1][type=buffer
ce1d1/trees/929f6dbc83f6d3b65dab91f1efa4aacb.lud'
stripped
resolvers | caching | 'files' compiled to
'/home/ce/.texlive2023/texmf-var/luametatex-cache/context/78ac5e3684a91334606faa581c7ce1d1/trees/929f6dbc83f6d3b65dab91f1efa4aacb.lud'
mtxrun |
mtxrun | elapsed lua time: 4.32
Description: Adobe PDF document
\setupcaption[table][location=right,orientation=90]
\startplacetable
[location=middle,
reference=tab:papierformaten,
title={Standaardformaten}]
\rotate[rotation=90]{\externalfigure[Table1][type=buffer]}
\stopplacetable
Thank you
by both mtxrun --generate and
luatools --generate right after.
there i no need to use luatools (it's something old from the early days)
what does
mtxrun --generate --verbose
report (whre does it fail)
57 \starttext
58
59 \usetypescriptfile[type-lucida]
60 \usetypescript[Lucida
t][encoding=texnansi]
54 \stoptypescript
55
56
57 \starttext
58
59 \usetypescriptfile[type-lucida]
60 \usetypescript[Lucida][texnansi]
61 >> \setupbodyfont[MyLucida, 10pt]
62
63 \input zapf
64
65 \input tufte
66
67
68 \stoptext
6
lation can be
Building from source is the production of executables from source code
files, using the appropriate tools for the chosen type of source code,
e.g. compilers, linkers, and other build tools like GNU autotools,
make, cmake, or other build mechanisms. With regard to complete
softwa
Hi,
When I reinstall LMTX on my linux 64 system, the first executing
install.sh gives the error message:
tex error > tex error on line 34 in file
/home/garfileo/public/context/tex/texmf-context/tex/context/base/mkiv/type-set.mkiv:
! I can't find file `type-imp-latinmodern.mkiv'.
so I h
fter a decade it is time
to remove the \type
15 %D {\pdf*} ones completely. For the moment I keep them commented
but even that will
16 %D go away.
17
18 \writestatus{loading}{ConTeXt Backend Macros / PDF}
19
20 \registerctxluafile{lpdf-ini}{optimize}
21 >> \registerctxlua
in the directory I've chosen:
charlie@Air-di-Tommaso ~ % which luametatex
/Users/charlie/Documents/ConTeXt/ConTeXt-LMTX/tex/texmf-osx-arm64/bin/luametatex
charlie@Air-di-Tommaso ~ % type luametatex
luametatex is
/Users/charlie/Documents/ConTeXt/ConTeXt-LMTX/tex/texmf-osx-arm64/bin/luametatex
charlie
of what's in the Lucida typescript
file that comes with the distribution. There must be some easy way to monkey
patch the existing type script file.
Mattias
--- Original Message ---
On Monday, January 30th, 2023 at 1:20 PM, Pablo Rodriguez via ntg-context
wrote:
>
>
>
> O
Hi,
I'm trying to access Lucida Casual. I see in type-imp-lucida-typeone.mkiv that
there is, indeed, a typescript for it, but I can't figure out how to switch to
it. That is, I want to make some text be Lucida Casual.
I gather from a previous thread that I should be using \definefontstyle
do at the end of each year, I upgraded my ConTeXt installation.
> I noticed a change in \vec behavior which doesn't extend the arrow anymore.
> Here is my example:
>
> \starttext
> Engine: \texenginename\ \texengineversion
>
> \ConTeXt: \contextversionnumber
>
> \typ
101 - 200 of 6736 matches
Mail list logo
