t's the reason behind this double feature?
> see thread of a few days ago
sure, just overlooked it (or rather my search didn't match).
___
If your question is of interest to others as well, please add an entry to the
On 6/6/2021 3:34 PM, Steffen Wolfrum wrote:
This minimal I ran with «ConTeXt ver: 2021.06.04 17:28 MKI» and got two PDF
files:
One «test.pdf» as expected and one called «test-pdf-keep.pdf».
What's the reason behind this double feature?
see thread of a few days ago
This minimal I ran with «ConTeXt ver: 2021.06.04 17:28 MKI» and got two PDF
files:
One «test.pdf» as expected and one called «test-pdf-keep.pdf».
What's the reason behind this double feature?
Steffen
> Am 05.06.2021 um 10:14 schrieb Wolfgang Schuster
> :
>
> denis.ma...
e named "mwe.tex", I get
>> an extra "mwe-pdf-keep.pdf", either with or without invoking the option
>> "--purgeall".
>> [...]
>> I’m afraid that this might be a bug.
>
> more an incomplete feature (should normally not be done) [...]
> no f
ext
I’m afraid that this might be a bug.
more an incomplete feature (should normally not be done) ... there is an
% keeppdf
(first line) feature for something Aditya and I are trying
no fix-upload today (not for a o
also be using
>> \definefontfamily [praise][serif][junicode]
>> but, the above min via behavior I couldn't get to work at live.contextgarden
>
> You need proper quotation mark (as shown in my example below) sand not
> ". Another option is to use the \quotation command and en
marks but your system has
no easy way to input them you can check if your text editor has smart
quotes feature which replaces " with the proper quotes.
\definefontfeature
[default]
[default]
[protrusion=quality,expansion=quality]
\setupquotation
[method=font]
\setupalign[hz,ha
case of a
missing publisher, it is not simply left blank because the APA style
explicitly tells us to put "Author" when there is no defined publisher,
so this is a feature, not a bug.
Alan
The APA does not attempt to define bibliographies. It defines reference
lists (and
t standard definitions that one could modify
as needed without breaking the entire system.
And then there are clearly bugs that can be fixed. In the case of a
missing publisher, it is not simply left blank because the APA style
explicitly tells us to put "Author" when there is no define
enable this feature in a permanent way?
I mean, how can we avoid that an update disables it?
Not ... because we define some inserts (e.g for footnotes) we need to
decide what storage model to choose ... technically we can use the
runtime 'experiment' feature but i expect to switch rather soon
On 5/25/21 6:20 PM, Hans Hagen wrote:
> [...] but for those willing to check the alternative, in
> page-ins.mkxl one can uncomment
>
> % \insertmode\plustwo
Many thanks for the new upload, Hans.
I’m extremely interested in testing this.
How can we enable this feature in a perma
gt;
> > On 5/22/2021 11:34 PM, Jairo A. del Rio wrote:
> > > Hi. Is \thewithproperty documented elsewhere? Is this a new
> > primitive?
> > > It looks interesting.
> > In the case of the \sin trick particular case \let\computer\the would
> >
primitive?
> It looks interesting.
In the case of the \sin trick particular case \let\computer\the would
also work; i added the \thewithproperty feature just because i
expect that users can come up with variants (like \drawme\sin ...)
which
then would adapt behaviour (via \dow
case \let\computer\the would
> also work; i added the \thewithproperty feature just because i
> expect that users can come up with variants (like \drawme\sin ...) which
> then would adapt behaviour (via \dowithproperty2).
>
Having flags for computing and drawing would be awesome.
On 5/22/2021 11:34 PM, Jairo A. del Rio wrote:
Hi. Is \thewithproperty documented elsewhere? Is this a new primitive?
It looks interesting.
In the case of the \sin trick particular case \let\computer\the would
also work; i added the \thewithproperty feature just because i
expect that users can
3 or four
decimal digits, that approach is not very handy.
So I will use the new feature and I’ll put it on the wiki once I have a few
interesting examples.
By the way, what does
\complexexpr{123 + new(456,789)}
complex numbers, so (re=123,im=0) + (re=456,im=789)
this uses the xcomplex
is not very handy.
So I will use the new feature and I’ll put it on the wiki once I have a few
interesting examples.
By the way, what does
\complexexpr{123 + new(456,789)}
mean?
Best regards: Otared
> On 21 May 2021, at 17:06, Hans Hagen wrote:
>
> On 5/21/2021 4:37 PM, Adity
tdate,
%D copyright={Aditya Mahajan}]
%D This metapost module is inspired by a TeX.SE question:
%D http://tex.stackexchange.com/q/39296/323
%D
%D I thought that it would be fun to implement a similar feature in MetaPost.
%D
%D To use this package in MetaPost:
%D
%D \starttyping
%Dinput mp-s
ugh the latest greatest lmtx should
perform some 2.5 times better when profiling).
There's also a new (yet unofficial) feature:
\starttext
\setupfonts
[serif=dejavuserif*default,
sans=dejavusans,
mono=dejavusansmono]
{AAA\char1234 AAA}
{\ss BBB\char1234 BBB}\par
{AA}
{
only
> works when in the component file)
>
>
> Can you make a simple example, it's possible there is a reset somewhere
> which disables the feature at the end of the environment or the start of
> the component file.
>
> Wolfgang
>
>
> __
][setups=test] is in the
component file.
Is this expected behavior?
(Before I just \setcharacterspacing[test] in the env file but now it
only works when in the component file)
Can you make a simple example, it's possible there is a reset somewhere
which disables the feature at the end
\definedfont[file:NotoColorEmoji.ttf*color]
\emoji{handshake}
\char"1F91D
\stoptext
two handhakes ... (you need to use the color feature, this font doesn't
have non colored ones btw)
-
module is inspired by a TeX.SE question:
%D http://tex.stackexchange.com/q/39296/323
%D
%D I thought that it would be fun to implement a similar feature in MetaPost.
%D
%D To use this package in MetaPost:
%D
%D \starttyping
%Dinput mp-sketch;
%D
%Dbeginfig(1)
%D sketchypaths; % Ma
n: TeX document
%D \module
%D [ file=mp-sketch.mp
%Dversion=2021.05.13
%D title=\CONTEXT\ \METAPOST\ graphics,
%D subtitle=Sketch drawing,
%D author=Aditya Mahajan,
%D date=\currentdate,
%D copyright={Aditya Mahajan}]
%D This metapost module is insp
Hi,
testing the new language goodies feature for ligature prevention, I found that
hard line breaks seem to interfere somehow with the ligature prevention
mechanism:
==
\setuplanguage[de][ goodies={lang-de.llg}]
\startlanguageoptions[de]
auf|jubeln
\stoplanguageoptions
the nothyphenated option or insert
\nohyphencollapsing into the \chapter command.
Is there another way to prevent collapsing hyphens with a single setting
that applies to the entire document?
The hyphens did not collapse in the previous version.
they did when a font had the tlig feature enabled
32-bit x86 Alpine Linux distribution on the iPad. One feature of the
> app is that it can import and mount several "file systems". One way to
> create such a file system is to export a Docker container.
>
> So, what one can do is create a Docker container in some other devic
t; You're not going to be able to get the Docker container to run on the
> iPad if that's what you were ultimately hoping.
Sorry, my explanation of what I am trying to achieve was a bit too
terse.
There is a little wonderful app on the App Store, called iSH
(https://github.com/ish-app/ish), which
ly the !! elements of TEXMF, so that mktexlsr does not
% create ls-R files in the non-!! elements -- because if an ls-R is
% present, it will be used, and the disk will not (usually) be searched,
% regardless of !!. Although in principle a directory listed here need
% not contain an ls-R fi
On 4/29/2021 11:08 PM, Otared Kavian wrote:
Hi Massi,
Thank you and Hans for this nice feature: is it going to be included in the
built-in sidebar ?
At some point yes.
Hans
-
Hans
Hi Massi,
Thank you and Hans for this nice feature: is it going to be included in the
built-in sidebar ?
Best regards: Otared
> On 29 Apr 2021, at 11:52, mf wrote:
>
> Il 28/04/21 17:53, Hans Hagen ha scritto:
>> On 4/28/2021 5:27 PM, mf wrote:
>>> Hello,
>>>
feature. In days when often
texts is imported from elsewhere and editors can show these dashes we
need to adapt
Not sure I understand your explanation.
I have been using UTF-8 as charset for my documents since 2002
(otherwise polytonic Greek was unreadable for me).
It was also more readable to use
On 4/27/21 8:57 AM, Hans Hagen wrote:
> [...]
> as mentioned in an earlier mail, after decades of utf in tex we should
> use the normal symbols instead ... you can disable collapsing with
>
> \nohyphencollapsing
>
> but then you need to enable the tlig font feature. In da
.. you can disable collapsing with
\nohyphencollapsing
but then you need to enable the tlig font feature. In days when often
texts is imported from elsewhere and editors can show these dashes we
need to ad
ee
that I have been using "\tfc $+$" in some of my tikz code for about 4 years.
So, it appears to be a old feature. I am thinking of changing the wiki from:
These quick font switches are meant for changing the font style, alternative,
or size of a few words: they do not change the bod
uot; in some of my tikz code for
about 4 years. So, it appears to be a old feature. I am thinking of changing
the wiki from:
These quick font switches are meant for changing the font style, alternative,
or size of a few words: they do not change the bodyfont, so they don't affect
interline spa
On 4/26/21 12:37 PM, denis.ma...@ub.unibe.ch wrote:
> Hi again,
>
> should I change the wiki or is the current behaviour a bug (that will
> eventually be corrected)?
Hi Denis,
sorry for the delayed reply.
I don’t think it’s a bug, but a feature.
>
> the wiki (https://wiki
* unicode character
* html entitity (in fact an ugly output of HTML editor)
HTML is preprocessed with ctx preprocessor (great feature!) and
substituted for unicode char nbsp or tilde.
MWE shows unichar spaces are non-breakable (see end of the first lines),
however they are not stretc
> Used XML input has two types of non-breakable space:
> unicode character
> html entitity (in fact an ugly output of HTML editor)
> HTML is preprocessed with ctx preprocessor (great feature!) and substituted
> for unicode char nbsp or tilde.
>
> MWE shows unichar spaces
Dear list,
first episode of series on nbsp of XML in lmtx.
Unfortunately, not that catchy as Netflix.
Used XML input has two types of non-breakable space:
- unicode character
- html entitity (in fact an ugly output of HTML editor)
HTML is preprocessed with ctx preprocessor (great feature
Hi,
The *next* upload will have the following change.
For a long time in mkiv and also lmtx, the tex habit of turning -- and
--- into endash and emdash has been handled at the font level by a
injecting a font feature. This works okay.
This tlig feature is currently part of the defaults
at the
left and right edges. All is under low level (engine) option controls
(compatibility and such) but currently I enable all. With a bit of
definitions one can for the 002D and 2010 cases deal with pre/post
variants .. the question is do we need that for more, if so, then I need
to add some mo
> On 16 Apr 2021, at 10:36, Thomas A. Schmitz
> wrote:
>
> On 4/16/21 10:26 AM, Hans Åberg wrote:
>>> That it doesn’t update in the background is more a feature than a bug,
>>> otherwise it would complain about broken/unavailable files during the TeX
>>&
On 4/16/21 10:26 AM, Hans Åberg wrote:
That it doesn’t update in the background is more a feature than a bug,
otherwise it would complain about broken/unavailable files during the TeX runs.
It is likely a bug: It has worked in some past versions.
It still works for me (I'm on the latest
e versions of
Preview, one get an extra copy so that they must eventually be all closed by
hand.
> That it doesn’t update in the background is more a feature than a bug,
> otherwise it would complain about broken/unavailable files during the
is not updated unless switching to the Preview
>> application.
>>
>> It something wrong here? Is it not functional in MacOS? Am I missing some
>> clue?
>
> Apple’s Preview updates only on activation, and not reliably (for me, it
> often crashes).
>
> That it does
nd not reliably (for me, it often
crashes).
That it doesn’t update in the background is more a feature than a bug,
otherwise it would complain about broken/unavailable files during the TeX runs.
Hraban
___
If your question
> unknown library 'modern-designsize'
fonts > 'fallback modern-designsize mm 12pt' is loaded
fonts > preloading modern-designsize (mono)
fonts > 'fallback modern-designsize tt 12pt' is loaded
fonts
Hi,
I uploaded a new version. However, because of some new feature there can
be (unwanted) side effects wrt hyphenation (should not be but who knows).
As a follow up on Denis mails about ligature prevention, we now have a
mechanism called language 'goodies' analogue to 'font goodies
IIRC, there’s currently no support for this.
--result= can be used to rename the output file, but it can not be used to
create the file in a specific directory, nor to move it there.
Such a feature would be quite useful though, I think.
Maybe two options?
--result=foo.pdf => rename out
.
Can be used for words with multiple wrong ligatures (Auflaufform).
Does not take derived forms into account (e.g., replacements for Auflage and
Auflagen must both be defined).
2. \blockligatures
Works as a font feature to block certain ligatures
Works also for derived forms of a given word (e.g
Ah, I've now realized that the \blockligatures needs to be activated as a font
feature... So forget about this point.
But, it still looks like ligature prevention with \replaceword is not working
with lmtx, but it works with --luatex
n Sat, 20 Mar 2021, Christoph Reller wrote:
> > >> Of course we can do this in lua:
> > >>
> > >> if tex.modes["A"] and not tex.modes{"B"] then
> > >> ...
> > >> end
> > >
> >
Mar 2021, Christoph Reller wrote:
>> Of course we can do this in lua:
>>
>> if tex.modes["A"] and not tex.modes{"B"] then
>> ...
>> end
>
> ... which means that you can use that at the context end as well
n Sat, 20 Mar 2021, Christoph Reller wrote:
> > >> Of course we can do this in lua:
> > >>
> > >> if tex.modes["A"] and not tex.modes{"B"] then
> > >> ...
> > >> end
> > >
> > >
gt;
>> if tex.modes["A"] and not tex.modes{"B"] then
>> ...
>> end
>
> ... which means that you can use that at the context end as well
(old feature).
> Save the following as test.mkix (or add &quo
n
> >> ...
> >> end
> >
> > ... which means that you can use that at the context end as well (old
> feature).
> > Save the following as test.mkix (or add "% macros=mkix" as the first
> line):
> >
> > ```
> > \starttext
> &
On 3/20/2021 8:24 AM, Aditya Mahajan wrote:
On Sat, 20 Mar 2021, Christoph Reller wrote:
Of course we can do this in lua:
if tex.modes["A"] and not tex.modes{"B"] then
...
end
... which means that you can use that at the context end as well (old feature).
Save the fo
On Sat, 20 Mar 2021, Christoph Reller wrote:
> Of course we can do this in lua:
>
> if tex.modes["A"] and not tex.modes{"B"] then
> ...
> end
... which means that you can use that at the context end as well (old feature).
Save the following as test.mkix (or ad
On 3/19/2021 10:47 PM, Pablo Rodriguez wrote:
On 3/19/21 10:11 PM, Joseph wrote:
Dear list,
Following MWE aims to reproduce the issue,
Hi Joseph,
I’m afraid that kerning current latest from 2021.03.17 17:46 isn’t able
to deal with the OpenType kern feature (which is enabled by default
On 3/19/21 10:11 PM, Joseph wrote:
> Dear list,
>
> Following MWE aims to reproduce the issue,
Hi Joseph,
I’m afraid that kerning current latest from 2021.03.17 17:46 isn’t able
to deal with the OpenType kern feature (which is enabled by default):
\showfontkerns
\starttext
\sta
> 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
s that use this feature to get
rid of upcoming spaces (picking up two optional arguments where one is
needed). So, no matter what solution is chosen: push back a space or
not, it has some unpredictable character.
This is why I always am explicit, as in \date[d=3]\ bla because no
matter what happe
On 3/13/2021 2:01 AM, Mohammad Hossein Bateni wrote:
Umm... the fallbacks are correct. My conclusion is that tlig does not
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
On 3/13/2021 1:13 AM, Mohammad Hossein Bateni wrote:
Any idea why the ligature {U+647 and U+654 => U+6C0} does not kick in?
because it's not defined as ligature
-
Hans Hagen | PRAGMA ADE
Umm... the fallbacks are correct. My conclusion is that tlig does not 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
for this other Farsi font
>> > (
>> https://github.com/aminabedi68/Mikhak/blob/master/Font/ttf/Mikhak-Medium.ttf
>> > <
>> https://github.com/aminabedi68/Mikhak/blob/master/Font/ttf/Mikhak-Medium.ttf>).
>>
>> > Perhaps this is because the last
is is because the last font is not standard, but
> > TrueType/OpenType standard is sometimes up for interpretation.
> >
> > I see two strange symptoms here:
> >
> > \showotfcomposition displays the tlig feature differently for the last
> > font. It appears
ype standard is sometimes up for interpretation.
I see two strange symptoms here:
\showotfcomposition displays the tlig feature differently for the last
font. It appears in the "extra" list, not in "basic". Why is that?
What does this mean anyway?
The font doesn't have endas
.
The problem, you see, is that \startalignment only offers a few key words like
flushleft, middle etc. and not what I need this time, which is a precise
indentation feature like .5cm. I suppose my real problem is not being
sufficiently au fait with how definitions work. I just can't seem to get
offers a few key
words like flushleft, middle etc. and not what I need this time, which
is a precise indentation feature like .5cm. I suppose my real problem is
not being sufficiently au fait with how definitions work. I just can't
seem to get a definition that gives me a result like
Chapter
The problem, you see, is that \startalignment only offers a few key words
> like flushleft, middle etc. and not what I need this time, which is a precise
> indentation feature like .5cm. I suppose my real problem is not being
> sufficiently au fait with how definitions work. I just can't seem to get
flushleft, middle etc. and not what I need this time, which
is a precise indentation feature like .5cm. I suppose my real problem is
not being sufficiently au fait with how definitions work. I just can't
seem to get a definition that gives me a result like
Chapter title
author
this is because the last font is not standard, but
TrueType/OpenType standard is sometimes up for interpretation.
I see two strange symptoms here:
\showotfcomposition displays the tlig feature differently for the last
font. It appears in the "extra" list, not in "basic". Why is that?
>> Since this is just for fun, the additional space and compile time is just a
>> bit annoying and doesn’t affect others, but I like to streamline my
>> workflows...
>
> This is a relatively simple feature to add. I have pushed a new branch with
>
split the files with some external tool
> afterwards.
> >
> > I could also treat them as two individual books, but then I'd have to get
> > the
> last page number of volume 1 in volume 2.
> In the early days of context (more than 2 decades ago) we had a printer
> where w
treat them as two individual books, but then I'd have to get the
last page number of volume 1 in volume 2.
In the early days of context (more than 2 decades ago) we had a printer
where we could inject from different trays and that is why we have a
feature in context to mark pages (so
some previous ones. Rather trivial but we need to be able to say that we
'added a new feature' occasionally. I couldn't yet think of more than
'cycle' and 'repeat' but who knows what users want ... (like some
autofit loop).
Hans
---
. The cycle and repeat
methods do that (using abit diufferent tricks than the 20 year old one
but not that different); these methods are independent of the parshape's
repeat option itself, which is an engine feature.
Messing with left/right 'align' will also bring left/rightskip into the
game
but that will be fixed in the next upload
Many thanks for your new upload, Hans.
Another minor detail:
\starttext
\startTEXpage
\startMPcode{doublefun}
draw lmt_followtext [
text = "\feature[+][smallcaps]\bf\samplefile{zapf} ",
path = ((0,0)..(3,3)..(9,-3)..(12,0)..(9
the next upload
Many thanks for your new upload, Hans.
Another minor detail:
\starttext
\startTEXpage
\startMPcode{doublefun}
draw lmt_followtext [
text = "\feature[+][smallcaps]\bf\samplefile{zapf} ",
path = ((0,0)..(3,3)..(9,-3)..(12,0)..(9,3)..(3,-3)..cy
Dear list,
I have the fowllowing sample:
\starttext
\startmakeup[page][align=middle]
\startMPcode{doublefun}
draw lmt_followtext [
text = "\feature[+][smallcaps]\bf\samplefile{zapf} ",
path = ((0,0)..(3,3.25)..(9,-3.25)..(12,0)..(9,3.25)..(3,-3.25)..(0,0)),
autoscal
sting hacks but maybe not needed because
never asked for", but on the other hand, sometimes availability creates
retrospective demand. (I also did \newlocalread and added some extra
random access hackery to \read, so who knows what users will abuse that
feature fo
left,empty,right,
left,empty,right,
left,empty,right]
\stoptext
pretty old feature ... there are more options
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061
Pond can create single-system PDFs, I leave page breaking to ConTeXt.
> Anyway, reading midi is probably straightforward, but it really sounds like a
> too limited feature unless one could use video/audio output or music
> typesetting (which is hard enough and outside of scope of ConTeXt, I w
essed in the video output ;)
Anyway, reading midi is probably straightforward, but it really sounds like
a too limited feature unless one could use video/audio output or music
typesetting (which is hard enough and outside of scope of ConTeXt, I would
say).
Mojca
__
Hi,
In the perspective of fancyfying context I made an alternative rendering
for missing glyphs (and in the process also made the visualization
italic and bold aware which is of course feature creepifying).
\replacemissingcharacters
\startbuffer
\startlines[before=,after
he file name, all booklets would use the same note PDFs. Now, the temp
> directory contains literally thousands of files.
> Since this is just for fun, the additional space and compile time is just a
> bit annoying and doesn’t affect others, but I like to streamline my
> workflows
more. and i'd rather not mangle the distribution tree as that's
out-of-sight/out-of-mind and likely to get replaced sometime after i've
forgotten that i mangled it
- does that mean that the usepath/usesubpath feature or environment scoping
is now different?
=> if so, where do i find the n
d sometime after i've
forgotten that i mangled it
- does that mean that the usepath/usesubpath feature or environment scoping
is now different?
=> if so, where do i find the new rules/syntax so i can regenerate my path
code/environment file?
=> is there a hook to generate
ontent-Type: text/plain; charset=utf-8; format=flowed
>
> Hi,
>
> I uploaded a new lmtx. I'm still playing a bit with metafonts so there
> are two new files
>
> context --global meta-imp-demo.mkxl
> context --global meta-imp-clock.mkxl
>
> Both show a bit. The que
defined symbols that
are proper characters and efficiently used.
Hans
PS. The clock one has a hidden cut'n'paste feature that only works on
acrobat which of course then makes it a kind of useless feature (plenty
of them by now) because when, e.g. a mupdf bases viewer doesn't support
ths, kerns etc)
> and we do so for at least the 'f' which also has a strange left offset
> ... i now adapted that to also serve the new (compact context font)
> model and also make sure that the smaller sizes for mkiv are handled; we
> can add more in those files, but that's also a (mat
aller sizes for mkiv are handled; we
can add more in those files, but that's also a (math) 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 d
gt; > http://www.ntg.nl/mailman/listinfo/ntg-context
> > webpage : http://www.pragma-ade.nl / http://context.aanhet.net
> > archive : https://bitbucket.org/phg/context-mirror/commits/
> > wiki : http://contextgarden.net
> >
> __
OK makes sense. I’ll see if I can remove this \feature macro.Yes 2nd case was only for reference for working case.Thanks De : Hans HagenEnvoyé le :vendredi 8 janvier 2021 16:32À : mailing list for ConTeXt users; JosephObjet :Re: [NTG-context] Missing kern when using \feature On 1/8/2021 2:45 PM
][default][kern=yes]
\definefontfamily[mainfont][serif][EBGaramond]
\setupbodyfont[mainfont, 9pt]
\showfontkerns
\starttext
Chapitre {\feature[-][xvicentury]v}. % no kerning between v and .
indeed there should be no kerning because there are two different font
setups (lmtx is a bit better
][serif][EBGaramond]\setupbodyfont[mainfont, 9pt]\showfontkerns \starttextChapitre {\feature[-][xvicentury]v}. % no kerning between v and . Chapitre v.\stoptext
___
If your question is of interest to others as well
]
\setupbodyfont
[mainface]
\starttext
\feature[+][onumsmcp]\tfb ab12αβ
\stoptext
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 langu
this is either a switch you turn on in ConTeXt, or something
that would still need to be implemented as a feature.
Best,
Augusto
On Mon, Jan 4, 2021 at 12:00 AM Henning Hraban Ramm
wrote:
> Am 03.01.2021 um 22:24 schrieb Hans Hagen :
>
> On 1/3/2021 10:02 PM, BPJ wrote:
>&g
401 - 500 of 4827 matches
Mail list logo
