se \placenotes to display a table
of the actual URLs for any readers that want to type them in.
I want the "link 1" bit to be normal text rather than superscript so
it's more visible. Using the \setupnote[textstyle=...] command I can
change the style of the number but not the supe
de the URL in-line in the text or as a (distracting) footnote. So when the author writes "See my video at
" I will print "See my video at link 1". At the back of the book, in an
appendix somewhere, I then use \placenotes to display a table of the actual URLs for any readers that
n
include the URL in-line in the text or as a (distracting) footnote. So when the author writes "See my video at
" I will print "See my video at link 1". At the back of the book, in an
appendix somewhere, I then use \placenotes to display a table of the actual URLs for any readers
e. So when the author writes
"See my video at " I will print "See my video at link 1". At
the back of the book, in an appendix somewhere, I then use \placenotes to
display a table of the actual URLs for any readers that want to type them in.
I want the "link 1" bit to b
(they are not in
open type but we sort of assume they are); the options that we had to
control how the engine deals with fonts are now driving the process
(without them being set not much is applied) and we basically assume
open type fonts (where one can enable engine options for those kind of
fonts but also
properties of atoms and molecules which means that we now have: pre
super/subscripts, post super/subscripts and primes; this permits nicer
anchoring under parameter control
= there are more font parameters to control matters (they are not in
open type but we sort of assume they are); the options
On 3/10/2022 4:59 PM, mf via ntg-context wrote:
Hello,
I'm trying to add new templates (xmlsetups) from the XML document itself.
See the attached MWE.
- the XML document is a simple XHTML file
- in the "head" element there's a "script" element with the "type
Hello,
I'm trying to add new templates (xmlsetups) from the XML document itself.
See the attached MWE.
- the XML document is a simple XHTML file
- in the "head" element there's a "script" element with the "type"
attribute set to "text/vnd.conte
Hans,
Thank you for your suggestion. I tried disabling all otf features except
besub, but it didn't work. I presume that prepend should be added like this:
\startluacode
fonts.handlers.otf.addfeature {
name = "besub",
type = "substitution",
prepend = true,
data = {
["uni
. I opened the font file in Font Forge and looked up the glyph info.
Here is what I tried and what failed:
\startluacode
fonts.handlers.otf.addfeature {
name = "besub",
type = "substitution",
data = {
["uni0431"] = "uni0431.SRB.alt"
}
}
\stopluacode
\defin
as a ‘bbl’ type file I get a list of publications but the entries are uncomplete. enclosed files: publist-test.tex, test-literaturliste.bbl, publist-test.pdf2. When I use a buffer for testing, I do not get \cite reference nor a publication list: publist-buffer-test,texCan someone advise?Kind regardsWilli
. Here is
what I tried and what failed:
\startluacode
fonts.handlers.otf.addfeature {
name = "besub",
type = "substitution",
data = {
["uni0431"] = "uni0431.SRB.alt"
}
}
\stopluacode
\definefontfeature[default]
[mode=node,kern=yes,
liga=yes,dlig=yes,
Sat, 22 Jan 2022 22:20:36 +0100
> From: Willi Egger
> To: mailing list for ConTeXt users
> Subject: Re: [NTG-context] \installpagearrangement doublesided
> stickers
> Message-ID: <6a631259-75dc-4b7f-be10-a0584908b...@boede.nl>
> Content-Type: text/plain; charset=utf-8
eeded at all (from what I can see, the XML
does not embed any type definition for dc:title, for example).
--
Karl Pettersson
Uppsala, Sweden
https://static-dust.klpn.se/
___
If your question is of interest to ot
/ui/#iso:std:iso:19005:-1:ed-1:v2:cor:1:v1:en
> and
> https://www.iso.org/obp/ui/#iso:std:iso:19005:-1:ed-1:v2:cor:2:v1:en:tab:1
> suggest that dc:description and dc:title are of the same type,
> which is coherent with
> XMPSpecificationPart1.pdf
> as in
> https://gi
ui/#iso:std:iso:19005:-1:ed-1:v2:cor:2:v1:en:tab:1
suggest that dc:description and dc:title are of the same type,
which is coherent with
XMPSpecificationPart1.pdf
as in
https://github.com/adobe/XMP-Toolkit-SDK/tree/main/docs
I.e. these are correct -- but Subject must a
> On 2/4/2022 7:29 PM, Karl Pettersson via ntg-context wrote:
> > > > Hi
> > > >
> > > > PDF/A files generated using ConTeXt fail validation with veraPDF, and
> > > > the reason seems to be that the dc:description metadata is defined with
> >
; PDF/A files generated using ConTeXt fail validation with veraPDF, and
> > > the reason seems to be that the dc:description metadata is defined with
> > > the wrong type in the embedded XMP extension schema.
> > >
> > >
> https://tex.stackexchange.com/qu
ription metadata is defined with
> > the wrong type in the embedded XMP extension schema.
> >
> > https://tex.stackexchange.com/questions/632380/generate-pdf-a-with-context
> >
> > https://github.com/veraPDF/veraPDF-library/issues/1224
> >
>
that the dc:description metadata is defined with
> > the wrong type in the embedded XMP extension schema.
> >
> >
> https://tex.stackexchange.com/questions/632380/generate-pdf-a-with-context
> >
> > https://github.com/veraPDF/veraPDF-library/issues/1224
> &
On 2/4/2022 7:29 PM, Karl Pettersson via ntg-context wrote:
Hi
PDF/A files generated using ConTeXt fail validation with veraPDF, and
the reason seems to be that the dc:description metadata is defined with
the wrong type in the embedded XMP extension schema.
https://tex.stackexchange.com
Hi
PDF/A files generated using ConTeXt fail validation with veraPDF, and
the reason seems to be that the dc:description metadata is defined with
the wrong type in the embedded XMP extension schema.
https://tex.stackexchange.com/questions/632380/generate-pdf-a-with-context
https://github.com
class, and we are currently
discussing the correct way for the user to type it. If you have
suggestions, please let us hear!
Some further suggestions by Hans are (see below for two more)
13 imaginary
14 differential
15 exponential
16 function
Q1: Do you have any further suggestions on new classes
for the user to type it. If you have
suggestions, please let us hear!
Some further suggestions by Hans are (see below for two more)
13 imaginary
14 differential
15 exponential
16 function
Q1: Do you have any further suggestions on new classes (or comments on
these)? It might be good to think about
that way
I don’t think that farmers (in Germany) still use them, but “Morgen”
(morning) and “Tagwerk” (a day’s work) were usual measures for areas,
depending on the region and the type of work (farming, viniculture,
fresco painting...)
a 'bunder' land is one still used and a 'mud' potatoes
, but “Morgen”
(morning) and “Tagwerk” (a day’s work) were usual measures for areas,
depending on the region and the type of work (farming, viniculture,
fresco painting...)
According to https://de.wikipedia.org/wiki/Tagewerk, only the kingdom of
Bavaria had a proper definition:
1 Tagwerk
On Tue, 25 Jan 2022, Joel via ntg-context wrote:
> I have about several different types of list that reoccur multiple times in
> my documents. Though I tried to keep things simple, by just defining the type
> when it appears, strange glitches appear. For instance, I have one
I have about several different types of list that reoccur multiple times in my
documents. Though I tried to keep things simple, by just defining the type when
it appears, strange glitches appear. For instance, I have one that uses the ☞
(pointing hand) logo, and sometimes that randomly appears
(it is a bit of a pity that support for indic scripts is such a
weird mix of font technology and
engine dependent reshuffling ... probably also driven by limitations
of open type at that time)>
When using these fonts regularly, one notices very erratic formatting
phenomena that must h
ling ... probably
also driven by limitations of open type at that time)
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038
] {\mfunctionlabeltext{ArgMin}}
\definemathcommand [liminfbar] [limop] {\underline{\mfunctionlabeltext{lim}}}
\definemathcommand [limsupbar] [limop] {\overline{\mfunctionlabeltext{lim}}}
\starttext
The built-in commands \type{\liminf}, yielding $\liminf$, and \type{\limsup},
yielding $\limsup$ do not work
ans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-\startluacode
fonts.handlers.otf.addfeature {
name = "iast&
simpler method
because a special cell type exists here, e.g.
\bTH ... \eTH
creates bold text.
3. Simple markup
For natural tables with short texts in each cell there exists a simple
mode which uses \starttable inspired markup with the short \NC and \NR
commands to mark the start
un véritable casse-tête. \type{LaTeX} et
\type{ConTeXt} offrent des outils d'automatisation encore assez mal
connus dans la communauté des éditeurs, notamment dans l'édition
savante, pour la collation et la comparaison de textes médiévaux}.\par
\stoplanguage
\startlinenumbering
\dorecurse{6
item itself.
one aspect is how ligatures are made: some fonts have single shapes,
others use replacements and kerning of (then) multiple shapes
I think you wrote about this somewhere else and it got me interested in
physical type from my period: it looks like some printers did some of
the same
thus now can in the historical
>> item itself.
>
> one aspect is how ligatures are made: some fonts have single shapes,
> others use replacements and kerning of (then) multiple shapes
I think you wrote about this somewhere else and it got me interested in
physical type from my per
manually put in a ligature when the physical type was
a ligatured one, as best I can tell. Not every shop had the same founts
and not every compositor used every available ligature in the same shop.
in that case you can best access the shapes by name (which is possible
in context), assuming
s and only manually put in a ligature when the physical type was
a ligatured one, as best I can tell. Not every shop had the same founts
and not every compositor used every available ligature in the same shop.
My bigger technical problem is that I need to combine paragraphs of
normally typeset pros
a fi ligature but not as feature so you need to add it:
\startluacode
fonts.handlers.otf.addfeature {
name = "xlig",
type = "ligature",
data = {
[64257] = { "f", "i" },
}
}
\stopluacode
\definefontfea
indique à ConTeXt que l'on veut ici du texte en français (ou 'en' pour l'anglais).
{\em Définir un apparat critique et le mettre en page avec un traitement de texte courant est un véritable casse-tête. \type{LaTeX} et \type{ConTeXt} offrent des outils d'automatisation encore assez mal c
tricks to make footnotes
invisible (I use folding in
emacs). The following would be a single example verse (32 syllables,
same size as the one quoted
above), encoded in ekdosis and with lots of manuscripts:
\begin{tlg}[hp16][]
\tl{
\app{\lem[wit={ceteri}]{manthāna}
\rdg[type=stemmaerror,wi
required us to identify an lemma with \edtext and then write the
> variant directly into
> the text. This may not matter in the case of few variants, but with many
> variants the text is
> quickly rendered unreadable -- even with all tricks to make footnotes
> invisible (I use
p{\lem[wit={ceteri}]{manthāna}
\rdg[type=stemmaerror,wit={B2}]{\unm śrīmanthāna} % stemma error
\rdg[wit={C4,L1,N5}]{manthāra}
\rdg[wit={N13,Tü,V1,V22,Vu}]{manthāno\skp{-}}
\rdg[wit={J2}]{mandāra}}%
\app{\lem[wit={ceteri}]{bhairavo}
\rdg[wit={N20}]{mairavo}
\rd
On 1/1/2022 11:14 AM, Ajith R wrote:
Don't know how. Can you point towards a documentation?
\type-imp-*
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt
context \frules with leaders as in:
test \leaders \frule height 6mm depth 3mm radius 1mm\hfill test
\startuseMPgraphic{demoleader}
fill
unitcircle xysized (RuleWidth,RuleHeight+RuleDepth)
withcolor RuleColor ;
\stopuseMPgraphic
test {\red \leaders \frule
height 6mm
depth 3mm
be missing something, because I can't get it to work.
> >
> > Here is a minimal —non working—example :-)
> > (The attempted removal (“f_i” → “fi” only before “o”) is of course
> > irrelevant. I chose it just for the sole purpose of this test, to
> > provide a simple example
of this test, to provide a simple example.
What I am trying to achieve is more complex, with other ligatures.)
fonts.handlers.otf.addfeature{
name = "unfio",
type = "chainsubstitution",
lookups = {
{ type = "multiple",
of this test, to provide a simple example.
What I am trying to achieve is more complex, with other ligatures.)
fonts.handlers.otf.addfeature{
name = "unfio",
type = "chainsubstitution",
lookups = {
{ type = "multiple",
this test, to provide a
> simple example. What I am trying to achieve is more complex, with other
> ligatures.)
>
> fonts.handlers.otf.addfeature{
> name = "unfio",
> type = "chainsubstitution",
> lookups
.)
fonts.handlers.otf.addfeature{
name = "unfio",
type = "chainsubstitution",
lookups = {
{ type = "multiple",
data = { [ "f_i" ] = { "f", "i" } }
}
}
rules = {
{ after = { { "
ther aspect of additional files is that I like to keep my system
uncluttered so e.g when I install fonts we just need the open type files
that I then install in texmf-fonts/fonts/data//* instead of
bothering about forther structure (in fact it doesn't really m
>>
>> Today's Topics:
>>
>> 1. Re: how to setup path of ConTeXtLMTX for MacVim?
>> (Jan-Erik Hägglöf)
>> 2. Re: circuitikz module seems broken (Hans Hagen)
>> 3. Re: TeXWorks and synctex SOLVED (Bruce Horrocks)
>>
>>
>> --
>
> Message: 1
> Date: Tue, 14 Dec 2021 00:48:25 +0100
> From: Jan-Erik Hägglöf
> To: mailing list for ConTeXt users
> Subject: Re: [NTG-context] how to setup path of ConTeXtLMTX for
> MacVim?
> Message-ID: <32566c08-2359-48df-
source > level 2, order 68, name
'/opt/luametatex/texmf-context/tex/context/fonts/mkiv/type-imp-euler.mkiv'
open source > level 3, order 69, name
'/opt/luametatex/texmf-context/tex/context/fonts/mkiv/type-imp-texgyre.mkiv'
close source> level 3, order 69, name
'/opt/luametatex/te
d in publ-ini.lua and publ-ini.mkiv.
> Related to the previous entry, the ability to remove existing entry tags from
> the "collected" or "tobesaved" lists defined in publ-ini.lua. This would
> allow us to override the usual list registry rules of \cite based on the
> valu
d" or "tobesaved" lists defined in publ-ini.lua.
This would allow us to override the usual list registry rules of \cite
based on the values of, say, an entry's category, "type" field or "options"
field.
- General support for the useauthor, useeditor, u
On 12/7/2021 9:55 AM, Mikael Sundqvist via ntg-context wrote:
Hi,
We changed so that newcomputermodern-book (which is bolder than
newcomputermodern) uses the same lfg file as lm, which works. I attach
an updated version of the type-imp-newcomputermodern.mkiv, which also
adds the lfg file
g file as lm, which works. I attach
> an updated version of the type-imp-newcomputermodern.mkiv, which also
> adds the lfg file to newcomputermodern.
>
> /Mikael
>
> PS If one wants to play with modernlatin, is there a simple way to
> play with the boldness (for example make it just
Hi,
We changed so that newcomputermodern-book (which is bolder than
newcomputermodern) uses the same lfg file as lm, which works. I attach
an updated version of the type-imp-newcomputermodern.mkiv, which also
adds the lfg file to newcomputermodern.
/Mikael
PS If one wants to play
Note the presence of double-spaced blank lines in the following document
and in the attached source file:
\setuptyping[numbering=line]
\starttext
\startbuffer[javacode]
try {
final var num = stack.pop();
if( num != null ) {
stack.push( blah );
}
return true;
}
\stopbuffer
\type
On Tue, 30 Nov 2021 14:05:23 +0100
Henning Hraban Ramm via ntg-context wrote:
> Maybe you could define your own float type for the cases without
> caption?
I've done that for other options, too, I guess no-caption-floats get
a dedicated float type as well now. It's more robust than r
v 2021, at 12:06, Denis Maier via ntg-context >> cont...@ntg.nl> wrote:
> >>>
> >>> Hi,
> >>>
> >>> for a current project I’ll need different variants of underbars.
> >>>
> >>> - A normal underbar
> >>>
;>> On 30 Nov 2021, at 12:06, Denis Maier via ntg-context > cont...@ntg.nl> wrote:
>>>
>>> Hi,
>>>
>>> for a current project I’ll need different variants of underbars.
>>>
>>> - A normal underbar
>>> - A dotted underbar
>
Am 30.11.21 um 14:19 schrieb Taco Hoekwater via ntg-context:
I would like to have this type of “complete” bar nesting as well.
YES, #metoo
As it stands, you can nest \underbars inside \underbars and \overstrikes inside
\overstrikes and \overbars inside \overbars, but no other combinations
’ll need different variants of underbars.
> >
> > - A normal underbar
> > - A dotted underbar
> > - A combination of both
> >
> > Is there a way to combine them? I was hoping to have the dotted variant
> above the normal bar.
>
> I would like to have
hem? I was hoping to have the dotted variant above
> the normal bar.
I would like to have this type of “complete” bar nesting as well.
As it stands, you can nest \underbars inside \underbars and \overstrikes inside
\overstrikes and \overbars inside \overbars, but no other combinations work.
) knows a way to disable the caption without
influencing the placement, I'm all ears.
Now I understand your problem, and unfortunately I can’t help you.
Maybe you could define your own float type for the cases without caption?
Hraban
that this change in default will mean that
almost everyone needs to add tlig in their documents. We may perhaps need a
'sensible-defaults' module :-)
Nothing against such a module, but I think it’s wrong to expect
automatical text replacements. If I type ' or " or -- I don’t want that
replaced,
load time 0.151 seconds
mkiv lua stats > font embedding time: 0.002 seconds, 1 fonts
mkiv lua stats > result saved in file: mfe-quote.pdf, compresslevel 1,
objectcompresslevel 3
mkiv lua stats > positions: 4 collected, 0 deltas, 0 shared partials, 0
partial entries
mkiv lua stats > used platf
lt saved in file: mfe-quote.pdf, compresslevel 1,
objectcompresslevel 3
mkiv lua stats > positions: 4 collected, 0 deltas, 0 shared partials, 0
partial entries
mkiv lua stats > used platform: osx-64, type: unix, binary subtree:
texmf-osx-64
mkiv lua stats > used engine: luametatex version:
ors, 0 common hashes, load time 0.151 seconds
mkiv lua stats > font embedding time: 0.002 seconds, 1 fonts
mkiv lua stats > result saved in file: mfe-quote.pdf, compresslevel 1,
objectcompresslevel 3
mkiv lua stats > positions: 4 collected, 0 deltas, 0 shared partials, 0
partial
even if for
other properties cmr fundamentally differs from open type math fonts.
Anyway, in the traditional tex approach to primes, the prime symbol is
taken from the script variant, where is has a different size (or not),
different boundingbox (or not) and/or is already raised (or not). Also
; > \setlayer[mwe] { \switchtobodyfont[chancery,8pt] \hskip 5mm Chancery
> > Font Here }
> > \setupbackgrounds[page][background=mwe]
> >
> > \starttext
> > Normal font text goes here. \blank[4*big]
> > { \switchtobodyfo
in different fonts, and that there was not simple
one-fits-all solution). We have not touched eulernova yet.
In any case, if you replace euler-math.lfg and type-imp-euler.mkiv in
ConTeXt-lmtx/tex/texmf-context/tex/context/fonts/mkiv/ with the
attached files, I think at least the primes should look
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
-español]
\placeRussian
\stoptitle
\stoptitle
\stoptext
Reading the manuals, I find that the publication mechanism for
bibliography kinda fits my needs (using ConTeXt to sort and type data
generated via external software) but, unlike registers, it doesn't seem
to include options for alphabetical
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
for bibliography
kinda fits my needs (using ConTeXt to sort and type data generated via
external software) but, unlike registers, it doesn't seem to include
options for alphabetical headers. Is it fine to keep using registers in
this case? Is there a better mechanism for this task in ConTeXt? Thank
On Thu, 2021-11-18 at 18:57 +0100, Hans Hagen wrote:
> Are you talking type 1 fonts? These should just work, assuming that you
> have the afm files installed. You need to define them with the right
> features enabled (just like opentype fonts).
Ok, yes this works (for kerning and the
On 11/18/2021 5:36 PM, Gérard Milmeister via ntg-context wrote:
Using old fonts
Around 2000 I acquired a collection of fonts, mostly Type 1
and some TrueType. As it appears they are not fully usable
in ConTeXt. The two main issues are:
1. Kerning and ligatures
These features can be only
Using old fonts
Around 2000 I acquired a collection of fonts, mostly Type 1
and some TrueType. As it appears they are not fully usable
in ConTeXt. The two main issues are:
1. Kerning and ligatures
These features can be only be used, if the GPOS and GSUB
tables are present and adequately filled
{then} \quad \liminf_{n \geq 0}x_{n} = -1, \quad
\limsup_{n\geq 0} x_{n}= +1.
\stopformula
The commands defined above, \type{\liminfbar} and \type{\limsupbar}, behave
correctly in all fonts I tested:
\startformula
x_{n} := (-1)^n, \quad\mbox{then} \quad \liminfbar_{n \geq 0}x_{n} = -1, \quad
{then} \quad \liminf_{n \geq 0}x_{n} = -1, \quad
\limsup_{n\geq 0} x_{n}= +1.
\stopformula
The commands defined above, \type{\liminfbar} and \type{\limsupbar}, behave
correctly in all fonts I tested:
\startformula
x_{n} := (-1)^n, \quad\mbox{then} \quad \liminfbar_{n \geq 0}x_{n} = -1, \quad
On 11/16/2021 10:53 AM, Henning Hraban Ramm via ntg-context wrote:
Hi,
\starttext
\quotation{\type{\CONTEXT\ }}
\stoptext
gives
“\CONTEXT \”
i.e. the space moved. Why? Bug?
no, side effect of catcodes ... when you use \type it will change
catcodes (sort of) and when tex serializes a \cs
Hi,
\starttext
\quotation{\type{\CONTEXT\ }}
\stoptext
gives
“\CONTEXT \”
i.e. the space moved. Why? Bug?
Hraban
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist
2021 12:26 AM, skyhorse--- via ntg-context wrote:
> > Here is the minium not-working example which I took from the
> > Wikigarden a few minutes ago.
> >
> > \def\T#1{%
> >\startitemize[#1,joinedup]
> > \item This is a bullet of type #1.
> >\s
This is a bullet of type #1.
\stopitemize
}
\starttext
\dorecurse{9}{\T\recurselevel}
\stoptext
Compiling this into a pdf file with context produces an error.
I've pasted the complete context typesetting run to show the error, in hopes
that it will shed some light on what's wrong with my setup
Hans Hagen via ntg-context wrote:
> On 11/14/2021 12:26 AM, skyhorse--- via ntg-context wrote:
> > Here is the minium example which I took from the
> > Wikigarden a few minutes ago.
> >
> > \def\T#1{%
> >\startitemize[#1,joinedup]
> >
On 11/14/2021 12:26 AM, skyhorse--- via ntg-context wrote:
Here is the minium not-working example which I took from the Wikigarden a few
minutes ago.
\def\T#1{%
\startitemize[#1,joinedup]
\item This is a bullet of type #1.
\stopitemize
}
\starttext
\dorecurse{9}{\T
Here is the minium not-working example which I took from the Wikigarden a few
minutes ago.
\def\T#1{%
\startitemize[#1,joinedup]
\item This is a bullet of type #1.
\stopitemize
}
\starttext
\dorecurse{9}{\T\recurselevel}
\stoptext
Compiling this into a pdf file with context
rings,
after checking that with:
\startluacode
function document.transfer_metadata(name)
local main_doc = lpdf.epdf.load(name)
context(type(main_doc.Info.ModDate))
context(type(main_doc.Info.Title))
end
\stopluacode
Would it be possible that LMTX can deal with these object
tem > ConTeXt ver: 2020.03.10 14:44 MKIV beta fmt: 2020.6.8 int:
> english/english
>
> fonts > otf loading > loading
> 'MYPATH/texmf/fonts/truetype/google/Vollkorn-Regular.ttf', hash
> 'vollkorn-regular'
> fonts > otf loading > loading fail
etadata(name)
local main_doc = lpdf.epdf.load(name)
context(type(main_doc.Info.ModDate))
context(type(main_doc.Info.Title))
end
\stopluacode
Would it be possible that LMTX can deal with these objects and import
them as strings?
Many thanks for your
/truetype/google/Vollkorn-Regular.ttf', hash
'vollkorn-regular'
fonts > otf loading > loading failed due to read error
fonts > defining > forced type 'ttf' of 'Vollkorn-Regular' not found
fonts > defining > font with asked name 'Vollkorn-Regular' is no
t;>> Yesterday, Roblox announced - Luau - https://luau-lang.org/why
> >>> <https://luau-lang.org/why> - mainly adding linting and
> >>> type-checking features.
> >>>
> >>> Being compatible with Lua 5.1 is probably a bummer but nonetheless
>
inting and
type-checking features.
Being compatible with Lua 5.1 is probably a bummer but nonetheless
would be interesting to hear about this from this community.
for sure i need more than an email to give a real answer (and some can
be read between the lines of the history documents / articles t
On Fri Nov 5, 2021 at 9:14 PM CET, Hans Hagen via ntg-context wrote:
> On 11/5/2021 6:23 PM, Ramkumar KB via ntg-context wrote:
> > Hello,
> >
> > Yesterday, Roblox announced - Luau - https://luau-lang.org/why
> > <https://luau-lang.org/why> - mainly adding linti
On 11/5/2021 6:23 PM, Ramkumar KB via ntg-context wrote:
Hello,
Yesterday, Roblox announced - Luau - https://luau-lang.org/why
<https://luau-lang.org/why> - mainly adding linting and type-checking
features.
Being compatible with Lua 5.1 is probably a bummer but nonetheless
Hello,
Yesterday, Roblox announced - Luau - https://luau-lang.org/why - mainly
adding linting and type-checking features.
Being compatible with Lua 5.1 is probably a bummer but nonetheless would be
interesting to hear about this from this community.
Thank you.
best regards,
Ramkumar
to test if everything works as expected.
Wolfgang
%D \module
%D [ file=type-imp-kurier,
%Dversion=2021.10.24,
%D title=\CONTEXT\ Typescript Macros,
%D subtitle=Kurier,
%D author=Hans Hagen,
%D date=\currentdate,
%D copyright={PRAGMA ADE
401 - 500 of 6767 matches
Mail list logo
