:
Dear gang,
For \addfeature and the like, a virtual font feature defined in terms of a CLD
local function behaves differently from other font features. MWE:
==
\startluacode
local function squeeze(tfmdata)
for k, v in next, tfmdata.characters do
v.width = 1.75 * (v.height or 0)
v.depth
On 8/20/2023 5:33 PM, Hamid,Idris wrote:
Dear gang,
For \addfeature and the like, a virtual font feature defined in terms of a CLD
local function behaves differently from other font features. MWE:
==
\startluacode
local function squeeze(tfmdata)
for k, v in next
Dear gang,
For \addfeature and the like, a virtual font feature defined in terms of a CLD
local function behaves differently from other font features. MWE:
==
\startluacode
local function squeeze(tfmdata)
for k, v in next, tfmdata.characters do
v.width = 1.75 * (v.height
data = {
[ '¿' ] = { 0, 400 },
[ '¡' ] = { 0, 400 },
}
}
\stopluacode
\definefontfeature[ktest][gpos_test=yes]
\starttext
\startTEXpage[offset=1em]
\ruledhbox{¿? xx ¡!}
\addfeature{ktest}
\rule
bfe781ce0dde776fb1556f32e/fonts/otl/stixtwotext-regular.tmd'
>>> stripped
>>> fonts > otf loading > loading, optimizing, packing and caching
>>> time 0.002
>>> lua error > lua error on line 1 in file ./Untitled.tex:
>>>
>>
.-64/tex/texmf-context/tex/context/base/mkiv/font-otc.lua:325: attempt to
index a nil value (upvalue 'descriptions')
stack traceback:
...-64/tex/texmf-context/tex/context/base/mkiv/font-otc.lua:325: in
local 'prepare_ligature'
...-64/tex/texmf-context/tex/context/base/mkiv/font-otc.lua
] [AntykwaTorunska] [features=f:onum]
\definefontfamily [test] [sans] [Myriad Pro]
\definefontfamily [test] [mono] [DejaVu Sans Mono]
\definefontfamily [test] [math] [Xits Math]
\setupbodyfont[test,12pt]
\starttext
Mozarts erster Satz ist ein
{\subtractfeature[f:test]\addfeature[f:frac]4/4}-Takt
[test] [sans] [Myriad Pro]
\definefontfamily [test] [mono] [DejaVu Sans Mono]
\definefontfamily [test] [math] [Xits Math]
\setupbodyfont[test,12pt]
\starttext
Mozarts erster Satz ist ein
{\subtractfeature[f:test]\addfeature[f:frac]4/4}-Takt, Beethoven wählt
einen Dreiertakt, Mozarts Romanze
gt; > \definefontfeature[f:oldstyle][onum=yes]
> >
> > \setupbodyfont[mainface, 18pt]
> > \addfeature{f:oldstyle}
> >
> > \starttext
> > 123456789
> > \blank[big]
> > $\sqrt{2} + 1234$
> > \stoptext
> >
> > Any pointers will
o Text][] %onum=yes does not seem to
> work
> \definefontfamily[mainface][mm][STIX Two Math][]
> \definefontfeature[f:oldstyle][onum=yes]
>
> \setupbodyfont[mainface, 18pt]
> \addfeature{f:oldstyle}
>
> \starttext
> 123456789
> \blank[big]
> $\sqrt{2} + 1234$
> \sto
][]
\definefontfeature[f:oldstyle][onum=yes]
\setupbodyfont[mainface, 18pt]
\addfeature{f:oldstyle}
\starttext
123456789
\blank[big]
$\sqrt{2} + 1234$
\stoptext
Any pointers will be greatly appreciated.
Alan
___
If your
On 12/9/2018 1:34 PM, Pablo Rodriguez wrote:
On 12/7/18 11:25 PM, Hans Hagen wrote:
On 12/7/2018 9:14 PM, Pablo Rodriguez wrote:
[...]
The issue is that, although opbd values are used, that results from opbd
and from single placement in addfeature are different (although LuaTeX
reports
On 12/7/18 11:25 PM, Hans Hagen wrote:
> On 12/7/2018 9:14 PM, Pablo Rodriguez wrote:
>> [...]
>> The issue is that, although opbd values are used, that results from opbd
>> and from single placement in addfeature are different (although LuaTeX
>> reports the same val
the font myself and the Greek script is required and selected
(with the Latin script, that OT opbd property doesn’t work at all).
The issue is that, although opbd values are used, that results from opbd
and from single placement in addfeature are different (although LuaTeX
reports the same values
he Greek script is required and selected
(with the Latin script, that OT opbd property doesn’t work at all).
The issue is that, although opbd values are used, that results from opbd
and from single placement in addfeature are different (although LuaTeX
reports the same values for lfbd).
Just in case i
function 'splitter'
...ext/tex/texmf-context/tex/context/base/mkiv/font-otc.lua:159: in
function 'addfeature'
...ext/tex/texmf-context/tex/context/base/mkiv/font-otc.lua:730: in
function 'enhancer'
...ext/tex/texmf-context/tex/context/base/mkiv/font-con.lua:1269: in
function 'enhance'
...ext/tex/texmf-c
v/font-otc.lua:159: in
function 'addfeature'
...ext/tex/texmf-context/tex/context/base/mkiv/font-otc.lua:730: in
function 'enhancer'
...ext/tex/texmf-context/tex/context/base/mkiv/font-con.lua:1269: in
function 'enhance'
...ext/tex/texmf-context/tex/context/base/mkiv/font-con.lua:1291: in
function 'apply
> [C]: in function '__div'
> ...ntext/tex/texmf-context/tex/context/base/mkiv/l-lpeg.lua:290: in
> function 'splitter'
> ...ext/tex/texmf-context/tex/context/base/mkiv/font-otc.lua:159: in
> function 'addfeature'
> ...ext/tex/texmf-context/tex/context/base/mkiv/font-otc.lua:
ontext/tex/context/base/mkiv/l-lpeg.lua:290: in
function 'splitter'
...ext/tex/texmf-context/tex/context/base/mkiv/font-otc.lua:159: in
function 'addfeature'
...ext/tex/texmf-context/tex/context/base/mkiv/font-otc.lua:730: in
function 'enhancer'
...ext/tex/texmf-context/tex/context/base/mkiv/font-c
On 4/29/2016 9:51 AM, Ulrike Fischer wrote:
I was playing with the addfeature handler mentioned here
https://mailman.ntg.nl/pipermail/ntg-context/2016/083952.html and
run into a problem with ttc-fonts:
\starttext
\directlua{
fonts.handlers.otf.addfeature {
name = "
On 4/29/2016 9:51 AM, Ulrike Fischer wrote:
I was playing with the addfeature handler mentioned here
https://mailman.ntg.nl/pipermail/ntg-context/2016/083952.html and
run into a problem with ttc-fonts:
\starttext
\directlua{
fonts.handlers.otf.addfeature {
name = "
I was playing with the addfeature handler mentioned here
https://mailman.ntg.nl/pipermail/ntg-context/2016/083952.html and
run into a problem with ttc-fonts:
\starttext
\directlua{
fonts.handlers.otf.addfeature {
name = "oneb",
{
type = &qu
Hello Wolfgang,
indeed if one uses pagella it is true what you say.
If I use Seravek, which has oldstuyle figures also, then it does not work in
the same way.
I tested with \addfeature[oldstyle] which is defined as
\definefontfeature[oldstyle][default][sript=latn,onum=yes]
With this feature
s,lnum=no,pnum=no,tnum=yes]
\definefontfeature [lnum+pnum] [onum=no,lnum=yes,pnum=yes,tnum=no]
\definefontfeature [lnum+tnum] [onum=no,lnum=yes,pnum=no,tnum=yes]
\setupbodyfont[pagella]
\starttext
\starttabulate[|f{\addfeature{onum+pnum}}r|f{\addfeature{onum+tnum}}r|f{\addfeature{lnum+pnu
>>> If I am correct then one should be able to enable the font feature tnum for
>>> the page-numbers with “pagecommand=“.
>>>
>>> I have
>>>
>>> \setuphead
>>> [section]
>>> [aftersection=\page, textstyle=\bfd, numberstyle=\bfd
>>
>> If I am correct then one should be able to enable the font feature tnum for
>> the page-numbers with “pagecommand=“.
>>
>> I have
>>
>> \setuphead
>> [section]
>> [aftersection=\page, textstyle=\bfd, numberstyle=\bfd, align=middle,
>
e=\bfd, align=middle,
after={\godown[-1\lineheight]}, number=no]
\setuplist[section][pagecommand={\addfeature[tnum]#1\subtractfeature[tnum]}]
However if I do this then I get the pagenumber prefixed with ‘section’
e.g.
bbb bar buch bühne section3
What am I doing in the wrong way?
\setuplist[c
]}, number=no]
\setuplist[section][pagecommand={\addfeature[tnum]#1\subtractfeature[tnum]}]
However if I do this then I get the pagenumber prefixed with ‘section’ e.g.
bbb bar buch bühne section3
What am I doing in the wrong way?
Kind regards
Willi
that this sample doesn’t work with latest beta either:
\usemodule[newotf]
\definefontfeature[noliga][liga=no]
\starttext
\startTEXpage[offset=1em]
fiflff no--liga:
\addfeature[noliga]fiflff
--- em--dash
\stopTEXpage
\stoptext
I may be wrong, but I
=no]
\starttext
\startTEXpage[offset=1em]
fiflff no--liga:
\addfeature[noliga]fiflff
--- em--dash
\stopTEXpage
\stoptext
I may be wrong, but I think that the non-deactivated OpenType feature is
related to the non-activated em- and en-dashes.
To the list members: could you test
:
\usemodule[newotf]
\definefontfeature[noliga][liga=no]
\starttext
\startTEXpage[offset=1em]
fiflff no--liga:
\addfeature[noliga]fiflff
--- em--dash
\stopTEXpage
\stoptext
I may be wrong, but I think that the non-deactivated OpenType feature is
related
]
\definefontfeature[noliga][liga=no]
\starttext
\startTEXpage[offset=1em]
fiflff no--liga:
\addfeature[noliga]fiflff
--- em--dash
\stopTEXpage
\stoptext
I may be wrong, but I think that the non-deactivated OpenType feature is
related to the non-activated em
beta either:
\usemodule[newotf]
\definefontfeature[noliga][liga=no]
\starttext
\startTEXpage[offset=1em]
fiflff no--liga:
\addfeature[noliga]fiflff
--- em--dash
\stopTEXpage
\stoptext
I may be wrong, but I think that the non-deactivated OpenType
no--liga: \addfeature[noliga]fiflff --- em--dash \stopTEXpage \stoptextI may be wrong, but I think that the non-deactivated OpenType feature isrelated to the non-activated em- and en-dashes.To the list members: could you test the sample above and tell em- anden-dashes work and if no-liga disables
Dear list,
I’m afraid that features don’t work with newotf:
\usemodule[newotf]
\definefontfeature[noliga][liga=no]
\starttext
\startTEXpage[offset=1em]
fiflff
\addfeature[noliga]fiflff
\stopTEXpage
\stoptext
Is this a bug or am I missing something?
Many
]
\setupbodyfont[latinmodern, 12pt]
\definefontfeature[oldstyle][lnum=no, onum=yes]
\starttext
Regular figures: 0123456789
{\addfeature[oldstyle] Local oldstyle figures: 0123456789}
\stoptext
This way, lining figures are enabled by default, and you can change to
oldstyle figures locally. if you wna
] [onum=no, extend=2, slant=0.25]
\definefontfamily [mainfamily] [serif] [Latin Modern Roman]
[features={mainfeature}]
\setupbodyfont [mainfamily, 50pt]
\starttext
1236
\addfeature [testfeature]
1236
\stoptext
Kind regards,
Joshua Krämer
.
\definefontfeature [mainfeature] [default] [onum=yes]
\definefontfeature [testfeature] [onum=no, extend=2, slant=0.25]
\definefontfamily [mainfamily] [serif] [Latin Modern Roman]
[features={mainfeature}]
\setupbodyfont [mainfamily, 50pt]
\starttext
1236
\addfeature [testfeature]
1236
Dear list,
I have noticed that ConTeXt (beta from 2014.02.14 17:07) has a problem
with Palatino Linotype.
Here the sample:
\definefontfeature[capstosc][c2sc=yes]
\definefontfamily[mainface][serif][Palatino Linotype]
\setupbodyfont[mainface]
\starttext
{\addfeature[capstosc] AEIOU}
\sc aeiou
{\addfeature[capstosc] AEIOU}
\sc aeiou
\stoptext
All vowels are fine, but the i is a dotted small cap i. The regular
small cap i is defined as i.sc (and the dotted small cap i is defined
as i.sc too). But FontForge applies both c2sc and smcp substitutions
fine.
It seems to be a regression
Am 21.10.2013 um 00:55 schrieb Hans Hagen pra...@wxs.nl:
On 10/21/2013 7:44 AM, Peter Münster wrote:
Hi,
aligncharacter=yes does not work with \addfeature[with-tnum]:
--8---cut here---start-8---
\definefontfeature[with-tnum][default][tnum=yes
Hi,
aligncharacter=yes does not work with \addfeature[with-tnum]:
--8---cut here---start-8---
\definefontfeature[with-tnum][default][tnum=yes]
\definefontfamily[mainface][sans][Alwyn New]
\setupbodyfont[mainface]
\setupTABLE[alignmentcharacter
On 10/21/2013 7:44 AM, Peter Münster wrote:
Hi,
aligncharacter=yes does not work with \addfeature[with-tnum]:
--8---cut here---start-8---
\definefontfeature[with-tnum][default][tnum=yes]
\definefontfamily[mainface][sans][Alwyn New]
\setupbodyfont[mainface
On 10/21/2013 8:04 AM, Wolfgang Schuster wrote:
Am 21.10.2013 um 00:55 schrieb Hans Hagen pra...@wxs.nl:
On 10/21/2013 7:44 AM, Peter Münster wrote:
Hi,
aligncharacter=yes does not work with \addfeature[with-tnum]:
--8---cut here---start-8
I missing?
The version you are using? The `\feature[+][...]` syntax has been
around only since about March 2013; before that you had to use
`\addfeature[...]`. Does that explain the error you're getting?
Cheers,
Sietse
][file:EBGaramond12-Regular.otf]
\definefontfeature[ss20][ss20=yes]
\definefontfeature[iota1][cv81=1]
\definefontfeature[iota2][cv81=2]
\definefontfeature[altcirc][cv80=1]
\define\test{Tì αᾟα\par}
\starttext
\definedfont[ebg*default at 12pt]\test
\addfeature{ss20}\test
\addfeature{iota1}\test
at 12pt]\test
\addfeature{ss20}\test
\addfeature{iota1}\test
\addfeature{iota2}\test
\addfeature{altcirc}\test
\stoptext
The font is at
http://www.georgduffner.at/ebgaramond/fonts/EBGaramond12-Regular.otf
The corresponding lookups in the kern.fea roughly contain
pos T' 145 i.dotless
[altcirc][cv80=1]
\define\test{Tì αᾟα\par}
\starttext
\definedfont[ebg*default at 12pt]\test
\addfeature{ss20}\test
\addfeature{iota1}\test
\addfeature{iota2}\test
\addfeature{altcirc}\test
\stoptext
The font is at
http://www.georgduffner.at/ebgaramond/fonts/EBGaramond12-Regular.otf
] \SAMPLE \blank
\feature[more][f:thinimacron] \SAMPLE \blank
\addfeature[f:upsidedown] \SAMPLE \blank
\feature[+][f:smallcaps]\SAMPLE \blank
\addfeature[f:wideimacron] \SAMPLE \blank
\feature[-][f:upsidedown] \SAMPLE \blank
[f:newstylesmallcaps] [smcp=yes,onum=no]
\startTEXpage[offset=10pt]
\define\SAMPLE{123 Idrīs ?` !` VA fi}
\SAMPLE\blank
\feature[+][f:oldstyle] \SAMPLE \blank
\feature[more][f:thinimacron] \SAMPLE \blank
\addfeature[f:upsidedown] \SAMPLE \blank
\feature
Hi,
After some experimenting, I settled on the next interface for dynamic
features:
The is also a generic command \type {\feature} that takes two arguments.
Below we show all calls, with long and short variants:
\starttyping
\addfeature[f:mine] \feature [more][f:mine] \feature
{[+nc]}\feature{f:nocaps}
fijn fietsen 123
\stop
\par
\start
fijn fietsen 123
\type{[+os]}\addfeature{f:oldstyle}
fijn fietsen 123
\type{[+sc]}\addfeature{f:smallcaps}
fijn fietsen 123
\type{[-os]}\subtractfeature{f:oldstyle
On Fri, 15 Mar 2013 05:07:02 -0600, Hans Hagen pra...@wxs.nl wrote:
\start
fijn fietsen 123
\type{[+os]}\addfeature{f:oldstyle}
fijn fietsen 123
\type{[+sc]}\addfeature{f:smallcaps}
fijn fietsen 123
\type{[=os]}\replacefeature{f:oldstyle
On 3/15/2013 7:11 PM, Idris Samawi Hamid ادريس سماوي حامد wrote:
On Fri, 15 Mar 2013 05:07:02 -0600, Hans Hagen pra...@wxs.nl wrote:
\start
fijn fietsen 123
\type{[+os]}\addfeature{f:oldstyle}
fijn fietsen 123
\type{[+sc]}\addfeature{f:smallcaps
also allow, e.g.,
\feature{add=bar,remove=baz}
I'd like to avoid parsing as much as possible here as these are state
changers. So, I made:
\addfeature [f:mine] \feature[more][f:mine] \feature[+] [f:mine]
\subtractfeature[f:mine] \feature[less][f:mine] \feature[-] [f:mine
On 3/15/2013 7:11 PM, Idris Samawi Hamid ادريس سماوي حامد wrote:
So I hope I have this right:
\addfeature adds a set of features {feature1,feature2,...featureN}
to the currently defined/enabled stack of OT features
\subtractfeature subtracts a set of features from the currently
defined
56 matches
Mail list logo
