OS if that helps
current version of ConTeXt: 2021.03.05 19:11
looks like you combine some mkii examples (xtx is a mkii xetex file, and
there is no gyr) with mkiv
Here is a simple way:
\definefontfeature[default] [boldened-30]
\definefontfeature[mathextra][boldened-20]
\setupbodyfont[pagella]
\start
name = "consola",
version = "1.00",
comment = "",
author = "",
copyright = "",
remapping = {
tounicode = true,
unicodes = {
hyphen = 0x002D,
},
},
}
--- 8< --
e can add to this.
> >
> > Denis
> >
> >
> > %\setupfontprotrusion [quality] [left=0] % no protrusion on the left
> margin
> > \setupfontprotrusion [quality] [left=1] % default
> > %\setupfontprotrusion [quality] [left=1.5] % more protru
default
> %\setupfontprotrusion [quality] [left=1.5] % more protrustion
> %\setupfontprotrusion [quality] [left=2] % even more protrustion
> %\setupfontprotrusion [quality] [left=2.5] % too much protrusion
>
> \definefontfeature
> [default]
> [default]
> [protrusion=qua
] % no protrusion on the left margin
\setupfontprotrusion [quality] [left=1] % default
%\setupfontprotrusion [quality] [left=1.5] % more protrustion
%\setupfontprotrusion [quality] [left=2] % even more protrustion
%\setupfontprotrusion [quality] [left=2.5] % too much protrusion
\definefontfeature
tprotrusion [quality] [left=1.5] % more protrustion
%\setupfontprotrusion [quality] [left=2] % even more protrustion
%\setupfontprotrusion [quality] [left=2.5] % too much protrusion
\definefontfeature
[default]
[default]
[protrusion=quality,
expansion=quality]
\setupquotation
[method=fo
partially but this is normal with
the quality setting).
I attached the example to ensure nothing was added when I send it.
Wolfgang
\definefontfeature
[default]
[default]
[protrusion=quality,
expansion=quality]
\setupquotation
[method=font]
\setupalign
[hz,hanging]
\showframe
ut in the left margin?
>>
>> For example in the following text, I want the "y" in "you are so" to be
>> aligned with the "oh" in "oh hi there" and the "here" in "here here".
>>
>> \definefontfeature
>>[default]
Sandra Snan schrieb am 04.06.2021 um 08:44:
Hi♥
How do I get the quotes to potrude out in the left margin?
For example in the following text, I want the "y" in "you are so" to be
aligned with the "oh" in "oh hi there" and the "here" in "h
Hi♥
How do I get the quotes to potrude out in the left margin?
For example in the following text, I want the "y" in "you are so" to be
aligned with the "oh" in "oh hi there" and the "here" in "here here".
\definefontfeature
[
mment = "",
author = "",
copyright = "",
remapping = {
tounicode = true,
unicodes = {
hyphen = 0x002D,
},
},
}
--- 8< --
\definefontfeature[consola][mode=base, goodies=consola, unicod
ures=default]
% \stoptypescript
% \definefontfeature
% [hz] [default]
% [protrusion=quality, expansion=quality, mode=node, script=latn]
% \starttypescript[DollyPro]
% \definetypeface [DollyPro] [rm] [serif] [DollyPro] [default] [features=hz]
% \stoptypescript
\usetypescriptfile[type-DollyPro]
\s
On 5/22/2021 11:28 AM, Pablo Rodriguez wrote:
Hi Hans,
I have the following sample:
\definefontfeature
[default]
[default]
[expansion=quality]
\setupalign
[hz]
\setuppapersize[A6]
\setupbodyfont[pagella]
\setupbackend [space=yes]
\starttext
\input
Hi Hans,
I have the following sample:
\definefontfeature
[default]
[default]
[expansion=quality]
\setupalign
[hz]
\setuppapersize[A6]
\setupbodyfont[pagella]
\setupbackend [space=yes]
\starttext
\input zapf
\stoptext
Using SumatraPDF-3.1.2 and current latest
Hi, With beta 2021-05-19 I notice that some kerns (usually before ‘v’ letter) are no longer present, not sure if that’s intented change behaviour or not.Following MWE reproduces the case. \definefontfeature[default][default][kern=yes]\definefontfamily[mainfont][serif][EBGaramond]\setupbodyfont
experiment and if that works,
I'll make a small package for that.
Did you try to use the regular variant:
\starttext
\definefontfeature[materialicons][default][rlig=yes]
\definedfont[file:materialiconsregular.ttf*materialicons]
baby_changing_station % selects symbol as ligature
\stoptext
relates to the
> > ConTeXt fontloader. Take the following ConTeXt example:
> >
> > \starttext
> > \definefontfeature [default:bold] [default] [axis={weight=500}]
> > \definedfont[file:NotoSansCJKsc-VF.otf*default:bold @ 10pt]
> > U+5E2E 帮
MkIV is to blame in this case.
> > In case you understand how does ConTeXt handle with bitmap fonts,
> > relevant files are under
> >
> /home/coragyps/lmtx/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/fonts/
> >
> > \definefontfeature[Emoji][default][
s/lmtx/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/fonts/
\definefontfeature[Emoji][default][sbix=yes]
\starttext
\framed[background=color,background=black]{\definedfont[file:NotoColorEmoji.ttf*Emoji]\char"1F91D}
took me quite a while
On 5/14/2021 1:49 AM, Jairo A. del Rio wrote:
In ConTeXt LMTX this works just fine (try mtxrun --generate and context
--make first):
\definefontfeature[Emoji][default][sbix=yes]
\starttext
\definedfont[file:NotoColorEmoji.ttf*Emoji]\char"1F91D
\stoptext
However, when one tries to co
e0dde776fb1556f32e/fonts/
> \definefontfeature[Emoji][default][sbix=yes]
>
> \starttext
>
>
> \framed[background=color,background=black]{\definedfont[file:NotoColorEmoji.ttf*Emoji]\char"1F91D}
>
> \stoptext
>
>
> In Hans' example for applecoloremoji there is no white backgro
Thanks Jairo,
That indeed works, should've read that it is bitmap only.
I do get a white background though (MKIV), is that how the bitmap is stored?
\definefontfeature[Emoji][default][sbix=yes]
\starttext
\framed[background=color,background=black]{\definedfont[file:NotoColorEmoji.ttf*Emoji
In ConTeXt LMTX this works just fine (try mtxrun --generate and context
--make first):
\definefontfeature[Emoji][default][sbix=yes]
\starttext
\definedfont[file:NotoColorEmoji.ttf*Emoji]\char"1F91D
\stoptext
However, when one tries to convert it with ImageMagick the following
ha
\definefontfeature [default:bold] [default] [axis={weight=500}]
\definedfont[file:NotoSansCJKsc-VF.otf*default:bold @ 10pt]
U+5E2E 帮
\stoptext
The font is available at
https://github.com/googlefonts/noto-cjk/raw/main/Sans/Variable/OTF/NotoSansCJKsc-VF.otf.
This compiles
\definefontfeature [default:bold] [default] [axis={weight=500}]
\definedfont[file:NotoSansCJKsc-VF.otf*default:bold @ 10pt]
U+5E2E 帮
\stoptext
The font is available at
https://github.com/googlefonts/noto-cjk/raw/main/Sans/Variable/OTF/NotoSansCJKsc-VF.otf.
This compiles
ry to use the regular variant:
\starttext
\definefontfeature[materialicons][default][rlig=yes]
\definedfont[file:materialiconsregular.ttf*materialicons]
baby_changing_station % selects symbol as ligature
\stoptext
(in latex equivalent) .. keep in mind that 'web' fonts are often more
mini
Hi,
recently we got an interesting bug report in luaotfload (the original report
is at https://github.com/latex3/luaotfload/issues/184) which relates to the
ConTeXt fontloader. Take the following ConTeXt example:
\starttext
\definefontfeature [default:bold] [default] [axis={weight=500
rialdesignicons.com/
>>>> <https://materialdesignicons.com/>
>>>> \starttext
>>>> \definedfont[file:materialdesignicons-webfont.ttf]\char"F1372\relax
>>>> \stoptext
>>> You need to employ a sense of humour for that font:
>>&g
\mainlanguage[de]
\definefontfeature[default][default][dlig=yes,liga=yes]
\definefontfamily[times][rm][Times New Roman]
\setupbodyfont[times]
\starttext
aufjubeln
aufjubeln\\
auffliegen
auffliegen\\
begrifflich
begrifflich\\
\stoptext
==
Best,
Denis
Hi,
I just ran into an issue with the \blockligatures mechanism. For some reason,
the following examples replaces ffi with f|fi and ffl with f|fl although I have
not specified them in \blockligatures:
==
\definefontfeature[default][default][dlig=yes
font.ttf]\char"F1372\relax
> >> \stoptext
> > You need to employ a sense of humour for that font:
> >
> > \starttext
> >\definefontfeature[materialicons][default][rlig=yes]
> >\definedfont[file:materialiconsregular.ttf*materialicons]
> >baby_ch
xample:
%Font available here: https://materialdesignicons.com/
<https://materialdesignicons.com/>
\starttext
\definedfont[file:materialdesignicons-webfont.ttf]\char"F1372\relax
\stoptext
You need to employ a sense of humour for that font:
\starttext
\definefontfeature[materialico
A bug? Minimal (non-)working example:
>> %Font available here: https://materialdesignicons.com/
>> <https://materialdesignicons.com/>
>> \starttext
>> \definedfont[file:materialdesignicons-webfont.ttf]\char"F1372\relax
>> \stoptext
> You need to employ
icons.com/>
\starttext
\definedfont[file:materialdesignicons-webfont.ttf]\char"F1372\relax
\stoptext
You need to employ a sense of humour for that font:
\starttext
\definefontfeature[materialicons][default][rlig=yes]
\definedfont[file:materialiconsregular.
= table.setmetatableindex({ }, function(t,k)
return shared
end)
languages.hyphenators.traditional.installmethod("sha",
function(dictionary,word,n)
return all
end)
\stopluacode
\definehyphenationfeatures
[sha]
[characters=all,
alternative=sha
On 5/10/21 9:36 AM, Hans Hagen wrote:
> [...]
> but at the cost of runtime you can try \setupbackend [space=yes]
It works perfectly fine, but not with font expansion:
\definefontfeature
[default]
[default]
[expansion=quality]
\setupalign
[hz]
\setuppapers
On 5/3/2021 8:07 PM, Alan Bowen wrote:
I am trying to set text in the Syriac font Estrangelo Edessa.
Right now, I have the following (taken for the wiki):
\definefontfeature[semitic-complete]
[mode=node,analyze=yes,language=dflt,ccmp=yes,
autoscript=position,autolanguage=position,
init=yes
I am trying to set text in the Syriac font Estrangelo Edessa.
Right now, I have the following (taken for the wiki):
\definefontfeature[semitic-complete]
[mode=node,analyze=yes,language=dflt,ccmp=yes,
autoscript=position,autolanguage=position,
init=yes,medi=yes,fina=yes,isol=yes,
mark=yes,mkmk
On 4/26/2021 12:37 PM, Hans van der Meer wrote:
I get the following message in the log (latest beta):
fonts > !
fonts > ! check count_components with mkiv !
fonts > !
These are my font settings:
\definefontfeature [default] [default] [itlc=yes]
\setu
I get the following message in the log (latest beta):
fonts > !
fonts > ! check count_components with mkiv !
fonts > !
These are my font settings:
\definefontfeature [default] [default] [itlc=yes]
\setupbodyfont[schola,10pt]
\setupitaliccorrection [text]
but that will
change. If you want to retain that, you can add this to a cont-loc.mkxl
file
\definefontfeature
[default]
[default]
[tlig=yes,
trep=yes]
but it should not be needed (and only introduces overhead). When it's a
font feature it kicks in after hyphenation but because we're
['ff'] = { "f", "f" },
['fi'] = { "f", "i" },
['fl'] = { "f", "l" },
}
}
\stopluacode
\blockligatures[begrif:fl:ich]
\definefontfeature[default][default][dlig=yes,liga=yes,moreligature
; ['fi'] = { "f", "i" },
> ['fl'] = { "f", "l" },
> }
> }
> \stopluacode
>
>
> \blockligatures[begrif:fl:ich]
> \definefontfeature[default][default][dlig=yes,liga=yes,moreligatures=yes]
>
;, "l" },
}
}
\stopluacode
\blockligatures[begrif:fl:ich]
\definefontfeature[default][default][dlig=yes,liga=yes,moreligatures=yes]
\definefontfamily[times][rm][Times New Roman]
\definefontfamily[termes[rm][TeX Gyre Termes]
\definefontfeature[default:block][default][block
Hi,
I just ran into something strange with ligature blocking:
---
\blockligatures[begrif:fl:ich]
\definefontfeature[default][default][dlig=yes,liga=yes,]
\definefontfeature[default:block][default][blockligatures
.
% these don't prevent ligatures
\replaceword[eka][auffasse][au{ff}asse]
\replaceword[eka][auffasst][au{ff}asst]
\replaceword[eka][auffasste][au{ff}asste]
\replaceword[eka][asdf][jklö] % this works though
% block as a font feature
\blockligatures[ff]
\definefontfeature
ear list,> > Following MWE aims to reproduce the issue,> > \definefontfeature[default][default][kern=yes]> > \definefontfamily[mainfont][serif][EBGaramond]> > \setupbodyfont[mainfont]> > \showfontkerns> > \starttext> > Chapitre v.> > \stoptextah, went
On 3/19/2021 10:11 PM, Joseph wrote:
Dear list,
Following MWE aims to reproduce the issue,
\definefontfeature[default][default][kern=yes]
\definefontfamily[mainfont][serif][EBGaramond]
\setupbodyfont[mainfont]
\showfontkerns
\starttext
Chapitre v.
\stoptext
ah, went unnoticed because i
Dear list, Following MWE aims to reproduce the issue, \definefontfeature[default][default][kern=yes]\definefontfamily[mainfont][serif][EBGaramond]\setupbodyfont[mainfont]\showfontkerns \starttextChapitre v.\stoptext ThanksBest regards Joseph
17:00:
> On 3/18/2021 4:12 PM, denis.ma...@ub.unibe.ch wrote:
>> Ok. But where are they coming from in Word? I'm on Windows.
>
> i don't see them in word when i enter 'effe' and select times, but i
> admit that my knowledge of word is zero so
\definefontfeature [default] [
Hans Hagen schrieb am 18.03.2021 um 17:00:
On 3/18/2021 4:12 PM, denis.ma...@ub.unibe.ch wrote:
Ok. But where are they coming from in
Word? I'm on Windows.
i don't see them in word when i enter 'effe' and select times, but i
admit that my knowledge of word is zero so
\definefontfeature
> work when the character is not in the font itself. Is that the case?
> > Is this a bug or a feature?
> >
> > \starttext
> >
> >
> \definefontfallback[fall][dejavusansmono][0-0xf][check=yes,force=no]
> > \definefontsynonym[Test][file:Mikhak-Medium.ttf][f
][check=yes,force=no]
\definefontsynonym[Test][file:Mikhak-Medium.ttf][fallbacks=fall]
\definefontfeature[tf][arabic][tlig=yes]
\definedfont[Test*tf]
foo--bar
[\char"2013]
[\char"2014]
\stoptext
... or a misunderdstanding:
\starttext
\definefo
-Medium.ttf][fallbacks=fall]
\definefontfeature[tf][arabic][tlig=yes]
\definedfont[Test*tf]
foo--bar
[\char"2013]
[\char"2014]
\stoptext
On Fri, Mar 12, 2021 at 7:13 PM Mohammad Hossein Bateni
wrote:
> Any idea why the ligature {U+647 and U+654 => U+6C
ile, I run into fonts
>> > where this does not work.
>> >
>> > See the attached tex/pdf files. I basically load the font as follows:
>> >
>> > \definefontfeature[tf][arabic][tlig=yes]
>> > \definedfont[dejavusansmono*tf]
>> >
>> >
tandard tex ligatures built in, I tend
> > to add them when I load the fonts. Once in a while, I run into fonts
> > where this does not work.
> >
> > See the attached tex/pdf files. I basically load the font as follows:
> >
> > \definefontfeature
as follows:
\definefontfeature[tf][arabic][tlig=yes]
\definedfont[dejavusansmono*tf]
This works fine for DejaVuSansMono and for one Farsi font I use
(https://github.com/rastikerdar/vazir-font/blob/master/dist/Vazir-Regular.ttf
<https://github.com/rastikerdar/vazir-font/blob/master/dist/Va
Hi,
Since most fonts do not have the standard tex ligatures built in, I tend to
add them when I load the fonts. Once in a while, I run into fonts where
this does not work.
See the attached tex/pdf files. I basically load the font as follows:
\definefontfeature[tf][arabic][tlig=yes
nction
<...mtx/tex/texmf-context/tex/context/base/mkiv/luat-run.lua:54>
Jairo
El vie, 5 de feb. de 2021 a la(s) 17:02, Hans Hagen (j.ha...@xs4all.nl)
escribió:
> On 2/5/2021 6:29 PM, Jairo A. del Rio wrote:
> > The following examples doesn't work as expected:
> >
> >
On 2/5/2021 6:29 PM, Jairo A. del Rio wrote:
The following examples doesn't work as expected:
\definefontfeature[emojis][default,color:svg][script=latn,language=dflt]
\definefont[gilbert][file:Gilbert-ColorBoldPreview5*emojis @ 13bp]
\starttext
{\gilbert abcdefghijklmnpqrstuvwxyz
The following examples doesn't work as expected:
\definefontfeature[emojis][default,color:svg][script=latn,language=dflt]
\definefont[gilbert][file:Gilbert-ColorBoldPreview5*emojis @ 13bp]
\starttext
{\gilbert abcdefghijklmnpqrstuvwxyz}
\stoptext
Letters are displayed correctly
category {demo} unicode 105 \relax % rather low level
for now
\registerboxglyph category {demo} unicode 106 \relax % rather low level
for now
\definefontfeature[whatever][box=demo]
\definedfont[Serif*whatever]
% \enabletrackers[fonts.collecting]
\startTEXpage%[offset=0pt]
%\hbox{g
h) user effort
>
> to be decided is of we use the feature setting "mathkerns=yes" (this was
> a directive but i made it just a feature)
>
> Now, ideally:
>
> \enableexperiments[fonts.compact] % for the definitions
>
> should give nearly similar results
efinitions
should give nearly similar results (but less mem usage, less fonts
loaded and possibly some performance gain)
I also updated some test features:
\definefontfeature[mathextra][staircase=yes,boundingbox=frame]
as part of the general lmtx upgrading process. Only cambria (and lucida)
have
, Joseph wrote:> Dear list,> > Still spot a minor difference with previous LMTX versions. MWE > reproduces it (in previous beta we had twice as kerning, now it’s no > kerning at all).> > Thanks a lot as usual.> > \definefontfeature[xvicentury][mode=node]> > \definefontf
On 1/8/2021 2:45 PM, Joseph wrote:
Dear list,
Still spot a minor difference with previous LMTX versions. MWE
reproduces it (in previous beta we had twice as kerning, now it’s no
kerning at all).
Thanks a lot as usual.
\definefontfeature[xvicentury][mode=node]
\definefontfeature[default
Dear list, Still spot a minor difference with previous LMTX versions. MWE reproduces it (in previous beta we had twice as kerning, now it’s no kerning at all).Thanks a lot as usual. \definefontfeature[xvicentury][mode=node]\definefontfeature[default][default][kern=yes]\definefontfamily[mainfont
On 1/7/2021 11:05 PM, Joseph wrote:
\definefontfeature[default][default][liga=yes, dlig=yes, hlig=yes]
\definefontfamily[mainfont][serif][EBGaramond]
\setupbodyfont[mainfont, 9pt]
\starttext
start active justice
\stoptext
fixed in next upload
Yes but I am afraid I still see some cases where ligatures are missing. MWE below (in 2 last words between c t and s t): \definefontfeature[default][default][liga=yes, dlig=yes, hlig=yes]\definefontfamily[mainfont][serif][EBGaramond]\setupbodyfont[mainfont, 9pt] \starttext start active justice
;> Hi everyone. The following example works fine with MkIV, but fails with
>> latest LMTX.
>>
>> To be specific, the lam-alif ligature isn't working. Compile with both to
>> see differences.
>>
>> Majalla is a Windows font, so I guess it's available fo
fic, the lam-alif ligature isn't working. Compile with both to see
> differences.
>
> Majalla is a Windows font, so I guess it's available for testing:
>
>
> \mainlanguage[arabic]
>
> \definefontfeature
>
> [arabic]
>
> [mode=node,language=dflt,script=arab,
>
>
with latest
LMTX.
To be specific, the lam-alif ligature isn't working. Compile with both to see
differences.
Majalla is a Windows font, so I guess it's available for testing:
\mainlanguage[arabic]
\definefontfeature
[arabic]
[mode=node,language=dflt,script=arab,
init=yes,medi=yes
On 1/6/21 1:41 PM, Hans Hagen wrote:
> On 1/5/2021 6:53 PM, Pablo Rodriguez wrote:
>> [...]
>> GFS Heraklit
>> (https://greekfontsociety-gfs.gr/_assets/fonts/GFS_Heraklit.zip [direct
>> link].) defines Greek c2sc and smcp for grek{dflt} (as displayed by
>> FontForge [which I read as: default
nTeXt is misbehaving:
\definefontfeature
[onumsmcp]
[script=latn,
onum=yes,
smcp=yes,
c2sc=yes]
\definefallbackfamily
[mainface]
[rm]
[GFS Heraklit]
[preset=range:greek,
force=yes]
\definefontfamily
[mainface]
[rm]
[TeX Gyre Pagella
t, I think that "script=auto" may
>> be safer than "script=latn". Or am I taking too much for granted?
> well, ytou get what you ask for ... if you don't set the script you get
> default (dflt) which also gives small caps
I have another sample that makes me wonder wh
On 1/5/2021 4:46 PM, Pablo Rodriguez wrote:
Hans,
this sample shows an issue with script:
\definefontfeature
[default]
[default]
[script=latn]
\definefontfeature
[onumsmcp]
[onum=yes,
smcp=yes,
c2sc=yes]
\setupbodyfont
[pagella
Hans,
this sample shows an issue with script:
\definefontfeature
[default]
[default]
[script=latn]
\definefontfeature
[onumsmcp]
[onum=yes,
smcp=yes,
c2sc=yes]
\setupbodyfont
[pagella]
\starttext
\feature[+][onumsmcp]\tfb abc123ABC
\stoptext
I could reproduce this occasionally occuring unexpected output in following MWE.Seems linked to calt=yes feature being set and ordn=yes being set and letter ‘f’ (some other letters such as ‘b’ work fine). Thanks as always for help. \definefontfeature[noteref][mode=node, ordn=yes
Dear list, Rare cases only but I thought it’d worth reporting this difference I could not understand.Could reproduce this problem with a simple MWE below. Kerning between ‘v’ and dot is doubled if \feature macro is used. Thanks \definefontfeature[xvicentury][mode=node]\definefontfeature[default
hanging punctuation, less severe style
\definefontfeature
[default]
[default]
[protrusion=punctuation,expansion=quality]
\setupalign[hz,hanging]
% Provide protrusion for quotations.
\setupquotation[method=font] % Toggle this line to see the effect.
\setupquote[method=font]
\starttext
Following MWE allows to reproduce the problem. Text right margin looks>> completely misaligned.> > Hi Hans,> > I was about to report the same issue, when I found the report by Joseph.> > Another MWE, just in case it might help:> > \showframe\showgrid> \definefontfea
in case it might help:
\showframe\showgrid
\definefontfeature
[default][default]
[expansion=quality]
\setupalign[hz]
\starttext
\input zapf
\stoptext
Many thanks for your help,
hm, so what was the last version that it still worked ok
ame\showgrid
\definefontfeature
[default][default]
[expansion=quality]
\setupalign[hz]
\starttext
\input zapf
\stoptext
Many thanks for your help,
Pablo
--
http://www.ousia.tk
___
If your question is
Dear list, Following MWE allows to reproduce the problem. Text right margin looks completely misaligned.Thanks \definefontfeature[myfeature][mode=node, kern=yes, protrusion=quality, expansion=quality]\definefontfamily[mainfont][serif][EBGaramond][features=myfeature]\setupbodyfont[mainfont, 9pt
Pablo Rodriguez schrieb am 26.12.2020 um 12:58:
Dear list,
I have the following sample:
\definefontfeature
[standarddigits]
[lnum=yes,
tlig=no]
\definefontfamily
[anothermpface]
[rm]
[Gabriola]
[features={default}]
\definefontfamily
Dear list,
I have the following sample:
\definefontfeature
[standarddigits]
[lnum=yes,
tlig=no]
\definefontfamily
[anothermpface]
[rm]
[Gabriola]
[features={default}]
\definefontfamily
[anothermpface]
[ss]
[Gabriola]
[features
ypeset with 2 kerns (a
and v + v and o).
Thanks
\definefontfeature[myfeature][mode=node, kern=yes]
\definefontfamily[mainfont][serif][EBGaramond][features=myfeature]
\setupbodyfont[mainfont, 9pt]
\showfontkerns
\starttext
Scavoir
\stoptext
fixed in next upload (left over from experiment r
Dear list, With MWE below, I notice there is no font kern between ‘v’ and ‘o’ in word typeset. Not sure that’s expected or not, but using older versions including ConTeXt live (contextgarden.net) , the word is typeset with 2 kerns (a and v + v and o).Thanks \definefontfeature[myfeature][mode=node
[features={default, dlig=no}]
> \setupbodyfont[english,10pt]
> \starttext
>
> Variant 1:
> Does this look like EBGaramond?
>
> fi fl ffi ffl ct st
> \stoptext
>
>
> However, it turns of *all* the ligatures.
>
> Here is an example that works as expected, Variant 2:
>
>
is the original? Which one are we supposed to support / configure?
\definefontfeature[whatever][default][rlig=yes]
% \definefontfeature[whatever][default][rlig=yes,dlig=yes] % those st
and ct ligs
\definefontfamily [english] [rm] [EB Garamond] [features=whatever]
\definefontfamily [englis
?
fi fl ffi ffl ct st
\stoptext
However, it turns of *all* the ligatures.
Here is an example that works as expected, Variant 2:
\definefontfeature[english][dlig=no]
\definefontfamily[ebgaramond] [rm] [EB Garamond]
[features={default,english}]
\setupbodyfont[ebgaramond,10pt
lig=no}]
Pass only named features sets (create with \definefontfeature) as
argument to the features key.
Even though "dlig=no" works at the moment this is not officially
supported and can disap
What commands should I use to turn them off?
>
> Hi Kurt,
>
> here you have the sample that should work:
>
> %~ \definefontfamily[ebgaramond] [rm] [ebgaramond]
>
> %~ [features={default,dlig=no}]
>
> \definefontfeature[english][dlig=no]
>
> \definefontf
* the ligatures.
Here is an example that works as expected, Variant 2:
\definefontfeature[english][dlig=no]
\definefontfamily[ebgaramond] [rm] [EB Garamond]
[features={default,english}]
\setupbodyfont[ebgaramond,10pt]
\starttext
Variant 2:
Does this look like EBGaramond?
fi fl ffi ffl ct st
to support / configure?
\definefontfeature[whatever][default][rlig=yes]
% \definefontfeature[whatever][default][rlig=yes,dlig=yes] % those st
and ct ligs
\definefontfamily [english] [rm] [EB Garamond] [features=whatever]
\definefontfamily [english] [mm] [Stix Two Math]
\setupbodyfont[engli
[ebgaramond]
%~ [features={default,dlig=no}]
\definefontfeature[english][dlig=no]
\definefontfamily[ebgaramond] [rm] [EB Garamond]
[features={default,english}]
\setupbodyfont[ebgaramond,10pt]
\starttext
ct st
\stoptext
BTW, on my system the default doesn’t get discretiona
h MkIV, but fails
>> with
>> > latest LMTX.
>> > |
>> >
>> > |To be specific, the lam-alif ligature isn't working. Compile with both
>> > to see differences.
>> > |
>> >
>> > |Majalla is a Windows font, so I guess it's avai
owing example works fine with MkIV, but fails with
> > latest LMTX.
> > |
> >
> > |To be specific, the lam-alif ligature isn't working. Compile with both
> > to see differences.
> > |
> >
> > |Majalla is a Windows font, so I guess it's available for te
Hi everyone. The following example works fine with MkIV, but fails
with latest LMTX.
To be specific, the lam-alif ligature isn't working. Compile with both
to see differences.
Majalla is a Windows font, so I guess it's available for testing:
\mainlanguage[arabic]\definefontfeature
[arabic
owgrid> > \setuplayout[grid=both]> > \definefontfeature[base][mode=node]> > \definefontfamily[mainfont][serif][EBGaramond][features=base]> > \setupbodyfont[mainfont, 9pt]> > \starttext> > \blank[line, samepage]Fin des psalmes.> > \blank[line, samepage]Fin des
201 - 300 of 1591 matches
Mail list logo
