tation would make them even longer.
I real IDE-like support for ConTeXt would be nice: setup-en.pdf is
always open when I write environments as I cannot remember all commands
and options. If my editor would give me a list of possible commands when
I just type some letters and then give possible op
dentation style, so forcing one on the user is not a good idea.
That said, if you have a list of desiderata, I may consider adding an
option to enable them. You may open an issue here for further
discussion:
https://github.com/lifepillar/vim-context-metapost
If you need to reflow paragraphs, t
arlesdoherty/Library/TeXShop/Engines/ARM.engine:3: bad CPU type in
executable: /Users/charlesdoherty/context-osx-arm64/tex/texmf-osx-64/bin/mtxrun
I have tried various options to no avail but I would really appreciate some
help on this (longhand rather than cryptic would be really helpfu
his engine I get:
/Users/charlesdoherty/Library/TeXShop/Engines/ARM.engine:3: bad CPU
type in executable:
/Users/charlesdoherty/context-osx-arm64/tex/texmf-osx-64/bin/mtxrun
I have tried various options to no avail but I would really
appreciate some help on this (longhand rather than cryptic woul
-arm64/tex/texmf-osx-64/bin/mtxrun --autogenerate
--script context --directives="system.showerror" --autopdf "$1" --purgeall
I made it executable.
When I typeset a file in TeXShop using this engine I get:
/Users/charlesdoherty/Library/TeXShop/Engines/ARM.engine:3: bad CP
secondpart\blank
firstpart\char"2010 secondpart\blank
firstpart\char"2013 secondpart\blank
firstpart\char"2014 secondpart
\type{firstpart---secondpart}
all work as I expect (both words get hyphenated).
The trep feature was already stripped to only ' replacment but in th
s
a format file which contains the content of the source files (which is a
lot faster).
When you make a change in one of the source files you have to create a new
format with includes these changes, to create such a format files type
context --make
:03:54 +
From: mailto:denis.ma...@ub.unibe.ch>>
To: mailto:j.ha...@xs4all.nl>>,
mailto:ntg-context@ntg.nl>>
Subject: Re: [NTG-context] Ligature suppression word list
Message-ID:
<41e6530172b54bffb7a82febff0a6...@ub.unibe.ch<mailto:41e6530172b54bffb7a82febff0a6...@ub.un
t; resolvers > resolving > file 'type-imp-loc.mkxl' is not
readable
> resolvers > resolving > file './type-imp-loc.mkxl' is not
readable
> resolvers > resolving > file 'type-imp-loc.mkxl' is not
readable
> resolvers
Hello Hans,
more specific resolver now:
\enabletrackers[resolvers.details]
\starttext
Readable?
\stoptext
On Sat, Apr 10, 2021 at 3:29 PM Hans Hagen wrote:
> On 4/10/2021 3:10 PM, Jano Kula wrote:
>
> > resolvers > resolving > file 'type-imp-loc.mkxl' is not read
On 4/10/2021 3:10 PM, Jano Kula wrote:
Hello,
updated lmtx (ver: 2021.04.09 19:59 LMTX), paths updated, etc.
\enabletrackers[resolvers.*]
\starttext
Readable?
\stoptext
shows in log some file are "not readable":
resolvers > resolving > file 'type-imp-loc.mkxl' is not re
Hello,
updated lmtx (ver: 2021.04.09 19:59 LMTX), paths updated, etc.
\enabletrackers[resolvers.*]
\starttext
Readable?
\stoptext
shows in log some file are "not readable":
resolvers > resolving > file 'type-imp-loc.mkxl' is not readable
resolvers > resolving
I have a lengthy text in English which occasionally uses Arabic place
names in brackets, e.g.
Khàbab ( خبب )is a Syrian town 50 km south of Damascus
The text is copy-pasted from a Word file, so I do not have to type the
Arabic as such, and would not know how to do that anyway.
Since I never
bffb7a82febff0a6...@ub.unibe.ch
> <mailto:41e6530172b54bffb7a82febff0a6...@ub.unibe.ch>>
> Content-Type: text/plain; charset="iso-8859-1"
>
>> -Ursprüngliche Nachricht-
>> Von: Hans Hagen mailto:j.ha...@xs4all.nl>>
>> Gesendet: Samstag, 3. April
'bug' is not a good one
the font just has no ligatures defined which you can remedy (in this
cae) with because it does have the glyphs
\startluacode
fonts.handlers.otf.addfeature {
name = "moreligatures",
type = "ligature",
data = {
s
> cae) with because it does have the glyphs
>
> \startluacode
> fonts.handlers.otf.addfeature {
> name = "moreligatures",
> type = "ligature",
> data = {
> ['ff'] = { "f", "f" },
>
\startluacode
fonts.handlers.otf.addfeature {
name = "moreligatures",
type = "ligature",
data = {
['ff'] = { "f", "f" },
['fi'] = { "f", "i" },
['fl'] = { "f"
gt; \definetyping[T]
> \definemode[mode][yes]
> \starttext
> \startmode[mode]
> \startT
> Bla
> \stopT
> \stopmode
> \stoptext
>
> Or use buffers (to avoid catcode all together):
>
> \definetyping[T]
> \definemode[mode][yes]
> \starttext
> \s
finemode[mode][yes]
\starttext
\startbuffer[code]
\startT
Bla
\stopT
\stopbuffer
\doifmode{mode}{\getbuffer[code]}
\stoptext
or (note type**T**buffer so that the output is formatting according to the
options of \definetyping[T])
\definetyping[T]
\definemode[mode][yes]
\starttext
\startbuffer[
The Lua code to generate start/stop environments with Pandoc is
described in Part 8 of my Typesetting Markdown series.
https://dave.autonoma.ca/blog/2020/04/28/typesetting-markdown-part-8/#annotations
The XML-MKIV documentation shows how to map a specific setup to a
particular attribute:
\xmlsets
seconds loading
mkiv lua stats > callbacks: internal: 55815, file: 82, direct: 3, late: 0,
function 6072, total: 61972 (632 per page)
mkiv lua stats > randomizer: resumed with value 0.30966186523438
mkiv lua stats > v-node processing time: 0.366 seconds
mkiv lua stats > result saved in fi
= "middle",
style = "type",
background = "DiagonalRule",
}
local letters_1 = { "A", "B", "C", "D", "E", "F", "G", "H" }
local pattern_1 = {
".XXX..XX",
"X...
\NC\NR
# \stoptabulate
#}
#\starttext
#\startluacode
# local background_one = {
# align = "middle",
# style = "type",
# background = "DiagonalRule",
# }
#
# local letters_1 = { "A", "B", "C
\NC \bf #1 \NC\NC\NR
\stoptabulate
}
\starttext
\startluacode
local background_one = {
align = "middle",
style = "type",
background = "DiagonalRule",
}
local letters_1 = { "A", "B", "C", "D", "E
Peter Münster schrieb am 12.02.2021 um 13:31:
Hi,
When I want to type an "i" in the position-command, there is some
vertical offset:
\starttext
\startpositioning
\position(1, 1){i} \position(2, 1){x}
\position(1, 2){x} \position(2, 2){i}
\position(1, 3){a} \position(2, 3){x}
\positi
Hi,
When I want to type an "i" in the position-command, there is some
vertical offset:
\starttext
\startpositioning
\position(1, 1){i} \position(2, 1){x}
\position(1, 2){x} \position(2, 2){i}
\position(1, 3){a} \position(2, 3){x}
\position(1, 4){x} \position(2, 4){a}
\stoppositioning
ould
> say).
It usually makes no sense to typeset music directly from a MIDI file, there’s
too much information missing (e.g. time, measures, repeats) or subject to
individual interpretation.
There’s midi2ly.py included with LilyPond, bu
>> tex.print(table.serialize(current.luadata))
>> -- to show that the key doesn’t contain weird invisible characters, I’ll
>> type it here:
>> tex.print(table.serialize(current.luadata.angerer2016))
>> tex.print('\\stoptyping')
>> \stopluacode
>>
>>
with finalizers. One should
also think of hyphenation and l2r/r2l direction, so in the end the usual
approach might be the best way.
You might use other approaches, how to deal with suspects of this type.
Below the MWE for font fallbacks with distribution fonts.
Not critical, just looking
be the other approach (also visible in print).
I think, the color could be achieved with finalizers. One should also think
of hyphenation and l2r/r2l direction, so in the end the usual approach
might be the best way.
You might use other approaches, how to deal with suspects of this type.
Below the MWE
>
> Message: 1
> Date: Thu, 21 Jan 2021 14:30:59 -0500
> From: Andres Conrado Montoya
> To: mailing list for ConTeXt users
> Subject: [NTG-context] Missing images in Wiki?
> Message-ID:
> z7sh-ng53xaxs6lr
Hello,
On Tue, 19 Jan 2021 at 12:11, Hans Hagen wrote:
> On 1/19/2021 11:57 AM, Floris van Manen wrote:
> >
> >
> > On 18/01/2021 19:20, Hans Hagen wrote:
> >> You can run
> >>
> >>meta-imp-punk.mkxl
> >>
> >> to get a
On 1/19/2021 11:57 AM, Floris van Manen wrote:
On 18/01/2021 19:20, Hans Hagen wrote:
You can run
meta-imp-punk.mkxl
to get an idea. There's also a typescript:
type-imp-punk.mkxl
How to run these?
Normally with:
context --global
On 18/01/2021 19:20, Hans Hagen wrote:
You can run
meta-imp-punk.mkxl
to get an idea. There's also a typescript:
type-imp-punk.mkxl
How to run these?
.F
___
If your question is of interest to others
Pagella font (I do not know if the same issue
> >> occurs with other fonts as I haven't tested them).
> >>
> >> If I compile with LMTX, the spacing between letters becomes very small
> >> so that when I type "|f|", for example, the second "|"
also a typescript:
type-imp-punk.mkxl
one can create different versions and play with random variants and
such. The question is: do we need more metapost font magic and
infrastructure?
For "pdf features that browsers implement fuzzy or not at all" lovers
there is
test
\star
error message with a more
> complex macro. It made me figure out where my problems came from.
>
> So here are my two questions:
> - Why shouldn't we tell metafun if expr is a path, a pair or so on?
You were (attempting to) redefine the macro’s arguments, but they are read-only.
with LMTX, the spacing between letters becomes very small
so that when I type "|f|", for example, the second "|" intersects the
f and looks rather ugly. However, compiling with the --luatex switch
fixes these issues and the math looks nice again.
Can anybody else replicate this iss
very small
so that when I type "|f|", for example, the second "|" intersects the f
and looks rather ugly. However, compiling with the --luatex switch fixes
these issues and the math looks nice again.
Can anybody else replicate this issue, and does anybody know
aven't tested them).If I compile with LMTX, the spacing between letters becomes very
small so that when I type "|f|", for example, the second "|"
intersects the f and looks rather ugly. However, compiling with
the --luatex switch fixes these issues and the math
Hi,
I've been having some trouble with ConTeXt not typesetting math
correctly when using the Pagella font (I do not know if the same issue
occurs with other fonts as I haven't tested them).
If I compile with LMTX, the spacing between letters becomes very small
so that when I type &qu
e=3]{a}
\stopformula
\switchtobodyfont[lucidaot]
If we switch to lucida, the \type{size=1} and \type{size=2} are the same:
\startformula
\Set[size=0]{a}\quad
\Set[size=1]{a}\quad
\Set[size=2]{a}\quad
\Set[size=3]{a}
\sto
wrote the following ==\usemodule[graph]\starttext\startMPcode{graph}draw begingraph(150mm, 100mm); gdraw "test-mpgraph.txt"; endgraph;\stopMPcode\stoptext==which fails with "error: Improper type" (see attache
he bug, just try accessing it:
>
> \startluacode
> local current = publications.datasets.default
> tex.print('\\starttyping')
> tex.print(table.serialize(current.luadata))
> -- to show that the key doesn’t contain weird invisible characters, I’ll
> type it here:
contain weird invisible characters, I’ll
type it here:
tex.print(table.serialize(current.luadata.angerer2016))
tex.print('\\stoptyping')
\stopluacode
will display:
t={
["angerer2016"]={
["author"]="Angerer...",
["category"]="artic
tats > font engine: otf 3.112, afm 1.513, tfm 1.000, 7 instances, 3
shared in backend, 3 common vectors, 0 common hashes, load time 0.156 seconds
mkiv lua stats > publications load time: 0.004 seconds, 1396 bytes, 1
definitions, 0 shortcuts
mkiv lua stats > font embedding time: 0.006 s
2, afm 1.513, tfm 1.000, 7
instances, 3 shared in backend, 3 common vectors, 0 common hashes, load
time 0.156 seconds
*mkiv lua stats > publications load time: 0.004 seconds, 1396 bytes, 1
definitions, 0 shortcuts*
mkiv lua stats > font embedding time: 0.006 seconds, 1 fonts
mkiv lua stats
[packed]},
after={\egroup},
]
\definereferenceformat [cite] [type=title,left={},right={}]
\definereferenceformat [bibpage] [type=page]
starttext
Now \cite[test 2020] on page
\page
\startbibitem[test 2020]
\input ward
\stopbibitem
\stoptext
Instead of “Now test 2020 on page”, I get “Now 248
.
Wait, you traverse global tablers so their entries are *not* global.
\starttext
\startluacode
context.starttabulate { "|T|T|" }
for k, v in table.sortedhash(_G) do
context.NC() context(type(v)) context.NC() context(k)
context.NC() context.NR()
end
context.st
ntitled.tex: ! Undefined control sequence
>>>
>>> \pgfplots@environment@polaraxis@ [#1]->\begin
>>> {axis}[#1,data cs=polar,axis
>>> type=polar]
>>> l.18\startpolaraxis[]
>>>
&
{axis}[#1,data cs=polar,axis
> > type=polar]
> > l.18\startpolaraxis[]
> >
> > 16 \startsection[title={Polar Plot}]
> > 17 \starttikzpicture % tikz code
> > 18 >> \st
n file
> /Users/Gavin/Documents/Computer/ConTeXt/Polar Plot Experiments/Untitled.tex:
> ! Undefined control sequence
>
> \pgfplots@environment@polaraxis@ [#1]->\begin
> {axis}[#1,data cs=polar,axis
> type=polar]
> l.18
Richard Mahoney schrieb am 20.12.2020 um 03:42:
In the recent versions of LMTX I've been having trouble with finding
my own typescriptfile -- type-sourceserifpro.tex (attached)
This file lives in the working directory of all of the other project
files,
and is also here:
~/lmtx-20201218/tex
In the recent versions of LMTX I've been having trouble with finding
my own typescriptfile -- type-sourceserifpro.tex (attached)
This file lives in the working directory of all of the other project
files,
and is also here:
~/lmtx-20201218/tex/texmf-fonts/tex/context/user/type-
sourceserifpro.tex
height=1em,option=printable,frame=on,offset=0.5mm,frameoffset=1mm,type=radio,color=black]
> \definefield[test][check][cbox][yes][no]
>
> \starttext
> \field[test] \space Do you see the word »yes«?
> \stoptext
>
> Unfortunately in Firefox and some other PDF Viewer there is th
> Am 04.12.2020 um 10:04 schrieb Hans Hagen :
>
> On 12/4/2020 8:02 AM, Axel Kielhorn wrote:
>>> Am 01.12.2020 um 18:23 schrieb Wolfgang Schuster
>>> :
>>>
>>> The following example shows the output of all commands:
>>>
>>&g
On 12/4/2020 8:02 AM, Axel Kielhorn wrote:
Am 01.12.2020 um 18:23 schrieb Wolfgang Schuster
:
The following example shows the output of all commands:
\starttext
\starttabulate [|T|T|]
\NC \type{\jobname} \NC \jobname \NC\NR
\NC \type{\jobfilename} \NC \jobfilename
> Am 01.12.2020 um 18:23 schrieb Wolfgang Schuster
> :
>
> The following example shows the output of all commands:
>
> \starttext
> \starttabulate [|T|T|]
> \NC \type{\jobname} \NC \jobname \NC\NR
> \NC \type{\jobfilename} \NC \jobfilena
environment file for the style and processing settings.
>
> context --environment=myxmlstyle myfile.xml
>
> The following example shows the output of all commands:
>
> \starttext
> \starttabulate [|T|T|]
> \NC \type{\jobname} \NC \jobname \NC\NR
> \NC \type{\jo
settings.
context --environment=myxmlstyle myfile.xml
The following example shows the output of all commands:
\starttext
\starttabulate [|T|T|]
\NC \type{\jobname} \NC \jobname \NC\NR
\NC \type{\jobfilename} \NC \jobfilename \NC\NR
\NC \type{\jobfilesuffix
rint("okay")}
bold
\stopbuffer
\usemodule[scite]
\startxmlsetups xml:initialize
\xmlsetsetup{#1}{doc|pre}{xml:*}
\stopxmlsetups
\xmlregistersetup{xml:initialize}
\startxmlsetups xml:doc
\xmlflush{#1}
\stopxmlsetups
\startxmlsetups xml:pre
\blank
\xmlprettyprint{#1}{\xml
hey are far from perfect
> but suit my needs. A few days ago, Hans warned not to use \noalign in LMTX,
> so I used the trick he gave to the list even if I don't really understand it.
>
> === LMTX version
> %D \macros{HR, VR}
> %D \type{\HR} draws a horizontal rule b
%D \macros{HR, VR}
%D \type{\HR} draws a horizontal rule between two rows of a matrix
%D \type{\VR} is used in place of \type{\NC} to draw a vertical rule between
two columns of a matrix
%D each macro takes an optional parameter giving the rule dimensions
%D Example
%D \type{\startmatrix \NC
,0)ctx.par()
ctx("TeX Getvar: ") ctx.getvariable("Test", "Height")ctx.par()
var = tokens.getters.macro(tokens.getters.macro("??variables") ..
"Test:Height")
ctx("Lua Type: ") ctx(type(var))ctx.par()
ctx("L
Dear list, Following MWE outputs only ‘m’ characters (with latest upload).Thanks \startluacode function roman_num(n) assert(type(n) == 'number') context(tex.romannumeral(n))end \stopluacode \define[1]\RM{\ctxlua{roman_num(#1)}} \starttext\RM{1}\RM{7}\RM{10}\RM{70}\RM{100}\stoptext
tx.getvariable("Test", "Height")ctx.par()
var = tokens.getters.macro(tokens.getters.macro("??variables") ..
"Test:Height")
ctx("Lua Type: ") ctx(type(var))ctx.par()
ctx("Lua Value: ") ctx(var)ctx.par()
end
\stopluac
,frame=on,offset=0.5mm,frameoffset=1mm,type=radio,color=black]
\definefield[test][check][cbox][yes][no]
\starttext
\field[test] \space Do you see the word »yes«?
\stoptext
Unfortunately in Firefox and some other PDF Viewer there is the word
"yes" written in the checkbox.
This make
1 0 R
/MaxLen 1024
/Q 0
/Subtype /Widget
/T
/V
>>
endobj
4 0 obj
<<
/Type /Annot
/DA (/rmtf 11.9552 Tf 1.1955 Ts 0 0 0 rg 0 0 0 RG)
/F 4
/Parent 2 0 R
/Q 0
/Subtype /Widget
/Rect [ 14.033054 14.033054 70.40415 25.08072 ]
>>
orecurse, such that \dorecurse{10}{\type{ab c}}
> > does not squash the spaces?
>
> Verbatim in arguments of other commands is tricky because in case with
> \dorecurse the loop reads the content before it is passed to type, as a
> result of this process all spaces are collapsed.
Sylvain Hubert schrieb am 08.11.2020 um 17:56:
Hi Wolfgang,
I'm sorry that the question was not clear enough. Let me ask in this way:
how to define a \dorecurse, such that \dorecurse{10}{\type{a b c}}
does not squash the spaces?
Verbatim in arguments of other commands is tricky because
Hi Wolfgang,
I'm sorry that the question was not clear enough. Let me ask in this way:
how to define a \dorecurse, such that \dorecurse{10}{\type{ab c}} does
not squash the spaces?
Sylvain
On Sun, 8 Nov 2020 at 15:03, Wolfgang Schuster <
wolfgang.schuster.li...@gmail.com> wrote:
>
Sylvain Hubert schrieb am 08.11.2020 um 14:47:
Dear List,
I would like to ask how to define a command, \same, such that
\same{\type{a b c}}
produces the same result as its argument does
\type{a b c}
The naive way doesn't work because it makes all the spaces collapse
Dear List,
I would like to ask how to define a command, \same, such that
\same{\type{a b c}}
produces the same result as its argument does
\type{a b c}
The naive way doesn't work because it makes all the spaces collapse:
\define[1]\same{#1}
I would also like to ask whether
If you happen to use ibus on a linux, there's a emoji/unicode picker
<https://mike-fabian.github.io/ibus-typing-booster/documentation.html#emoji-predictions>,
where you can type `elem` and pick one from the
candidates “∈∉∊⋲⋳⋴⋵⋶⋷⋸⋹⟒⫙” .
On Thu, 5 Nov 2020 at 21:25, wrote:
> A quick
Thank you for your extremely thorough and helpful response, Hans! I'm still
fairly new to ConTeXt, but I'm learning, and I have been helped greatly by all
the support that is generously provided on this email list.
With thanks,
Sciurus
-Original Message-
From: Hans Hagen
Sent:
for "is an element of" a set).
…
> This is a very common character in mathematics, so I wanted to ask: what is
> the recommended way to type this character? (I'm hoping to avoid having to
> cut and paste the character into the document every time I want to use it.
> And I don't have
how to read this information, but if I read it
> correctly, perhaps this character should be gotten with \in. Also, the Basic
> Math page of the Wiki (https://wiki.contextgarden.net/Math/basic) states
> that you should be able to type this character with "\in". But that doesn'
like an epsilon, and
> which is the mathematical symbol for "is an element of" a set).
…
> This is a very common character in mathematics, so I wanted to ask: what is
> the recommended way to type this character? (I'm hoping to avoid having to
> cut and paste the character into
completely sure how to read this information, but if I read it
correctly, perhaps this character should be gotten with \in. Also, the Basic
Math page of the Wiki (https://wiki.contextgarden.net/Math/basic) states
that you should be able to type this character with "\in". But that doesn
correctly, perhaps this character should be gotten with \in. Also, the Basic
Math page of the Wiki (https://wiki.contextgarden.net/Math/basic) states
that you should be able to type this character with "\in". But that doesn't
work (even inside a formula), since \in is used for r
r context.delayed as it is another table (metatable
trickery to allow nesting, I guess). Try:
\starttext
\startluacode
context(type(context.delayed))
\stopluacode
\stoptext
Long story short: context.cmda(context.delayed.cmdb(something)) will
(possibly) work; context.cmdc({key=context.de
Thank you, Wolfgang, for your prompt and helpful solution!
Although I didn't make it clear in the minimal working example, I am using this
for ordinary dialog. For the record (and for anyone searching the mailing list
in the future), to get that to work right, I had to put in one more thing
I'm trying to get quotation marks at the beginning of each new paragraph in
quotations (in ConTeXt Mk IV), as is the convention in English. Here's a
minimal working example of what I have tried:
\setupdelimitedtext[quotation][repeat=yes, middle="]
\starttext
\quotation{\input knuth
}
\stoptext
> (PS: I would say that adding support for transliteration of the text
> from one script to the other would be a really nice feature. Then you
> could type your text for a book once and have it typeset in both
> versions without any extra effort :)
There is Philipp Gesang's transliter
nsliteration of the text
from one script to the other would be a really nice feature. Then you
could type your text for a book once and have it typeset in both
versions without any extra effort :)
As for transliteration, cyrillic to latin is one-to-one, straightforward
with no exceptions.
A simple
ay that adding support for transliteration of the text
> from one script to the other would be a really nice feature. Then you
> could type your text for a book once and have it typeset in both
> versions without any extra effort :)
As for transliteration, cyrillic to latin is one-to-on
soi1:1][width=.25\makeupwidth]
> \setupcolumnset[soi1:2][width=.30\makeupwidth]
> \setupcolumnset[soi1:3][width=.45\makeupwidth]
>
> Any tips, help or pointers would be greatly appreciated. If not for
> columnset, is there any other way to get this type of layout?
>
> Thank you,
>
some new stuff (in the middle of fit)
(PS: I would say that adding support for transliteration of the text
from one script to the other would be a really nice feature. Then you
could type your text for a book once and have it typeset in both
versions without any extra effort :)
just gimme the specs
ly.
Thank you,
Mojca
(PS: I would say that adding support for transliteration of the text
from one script to the other would be a really nice feature. Then you
could type your text for a book once and have it typeset in both
versions without any extra effort :)
__
]
\setupcolumnset[soi1:2][width=.30\makeupwidth]
\setupcolumnset[soi1:3][width=.45\makeupwidth]
Any tips, help or pointers would be greatly appreciated. If not for
columnset, is there any other way to get this type of layout?
Thank you
ments given (main font,
scripts, serif & sans, fallbacks fonts to other scripts)?
For example IBM Plex <https://www.ibm.com/plex/languages/> will cover
most of what you need (except cjk for now) and there is a font
definition file type-imp-plex.mkiv in the distribution (
llbacks fonts to other scripts)?
For example IBM Plex <https://www.ibm.com/plex/languages/> will cover most
of what you need (except cjk for now) and there is a font definition file
type-imp-plex.mkiv in the distribution (not all fallbacks d
Hi all,
Just wanted to put the word out that I have posted two new pages to the
Wiki, both aimed at new users of ConTeXt:
https://wiki.contextgarden.net/Introduction
https://wiki.contextgarden.net/Some_Basic_Commands
The first is an introduction to the general principles of writing documents
in
font files so they could be compiled via Metapost. If you go for 2),
> the following would work as a poor's man solution for any symbol you need.
>
> \starttext
> \startuseMPgraphic{Flag}
> %From ifsym.gen
> draw (3pt,0pt)--(3pt,10pt);
> fill (3pt,10pt)--(0pt,8pt)--(3pt,6pt)--cyc
,8pt)--(3pt,6pt)--cycle;
\stopuseMPgraphic
This is a poor's man \type{ifsym's \Flag}: \useMPgraphic{Flag}.
\stoptext
There's a more advanced way to register glyphs explained in Luametafun (
http://www.pragma-ade.com/general/manuals/luametafun.pdf), in case you're
interested.
Regards,
Jairo :)
El
ks.json
> {
> "name" : "context",
> "tasks" : [
>{
>"label": "ConTeXt LuaMetaTeX",
>"type": "shell",
>"command": "export
> PATH=$HOME/ConTeXt-lmtx/tex/texmf-
here, I think):
%%% Begin of file $HOME/.config/Code/User/tasks.json
{
"name" : "context",
"tasks" : [
{
"label": "ConTeXt LuaMetaTeX",
"type": "shell",
"command": "export
PATH=$H
;
>
> --
>
> Message: 1
> Date: Mon, 21 Sep 2020 12:21:37 +0200
> From: Denis Maier
> To: ntg-context@ntg.nl
> Subject: [NTG-context] Parallel text support
> Message-ID: <780fe43c-f2c3-6ea1-04
Denis Maier schrieb am 21.09.2020 um 16:38:
Hi,
I'm a bit confused, but this here won't compile:
=
\startbuffer[test]
Test
\stopbuffer
\startxmlsetups xml:test
\xmlsetsetup{#1}{*}{-}
\xmlsetsetup{#1}{article}{xml:*}
\xmlsetsetup{#1}{table[@content-type
Re: ZapfDingbats Unicode differences MKIV vs LMTX (Hans Hagen)
>> 5. Math fonts for Nimbus fonts (Otared Kavian)
>> 6. Re: 2020 Meeting recordings? (Taco Hoekwater)
>>
>>
>> --
>>
>&
601 - 700 of 6767 matches
Mail list logo
