[NTG-context] Weekdays and others as numbers

[Jairo A. del Rio]

ConTeXt has some inbuilt functions for dates. I see that the following

\mainlanguage[spanish]
\starttext

\dayoftheweek{4}{5}{1992}

\stoptext


gives "lunes" (Monday). How to get a weekday number (2 in this case)
instead?

Sincerely,

Jairo
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / 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
___

[NTG-context] RE : Missing kern when using \feature

[Joseph]

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, 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][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 in these dynamic features: more strict testing at the cost of a bit more runtimen but optimized so not noticeable) > Chapitre v. i see a kern here > \stoptext> > > ___> If your question is of interest to others as well, please add an entry to the Wiki!> > maillist : ntg-context@ntg.nl / 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> ___>   --  -   Hans Hagen | PRAGMA ADE   Ridderstraat 27 | 8061 GH Hasselt | The Netherlands    tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl- 
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / 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
___

Re: [NTG-context] Missing kern when using \feature

[Hans Hagen]

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][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 in these dynamic features: more strict 
testing at the cost of a bit more runtimen but optimized so not noticeable)



Chapitre v.


i see a kern here


\stoptext


___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / 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
___




--

-
  Hans Hagen | PRAGMA ADE
  Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
   tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / 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
___

[NTG-context] space after \date[]

[Peter Münster]

Hi,

There is no more space after \date[] with the latest version.
Is this wanted, or a bug?

Example:

\starttext
\date[d=1] X % no space before "X"
\stoptext

Kind regards,
-- 
   Peter
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / 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
___

Re: [NTG-context] LuaTeX and PDF.js

[Vedran Miletić]

08. 01. 2021. u 05:41, Aditya Mahajan piše:

On Fri, 8 Jan 2021, Hans Hagen wrote:


On 1/8/2021 12:39 AM, Vedran Miletić wrote:


It's whatever ConTeXt standalone has. I don't have any extra Lua installed:


--credits should mention the lua version


Should I see it on non-HiDPI as well? Because it seems it's there.


depends on what you consider (non) hdpi ... the positioning of glyphs
depends on font scale, rounding of stems and such (hints in fonts but
these get less relevant with high res displays), caching, inter glyph
corrections (that pdftex/luatex/...) put in the text stream to resync
within certain tolerances, etc ... (often a print is a better reference
as displays are seldom 600+ dpi) .. it's also why often expansion looks
bad on screen because even a sub percentage difference can give such
effects


Another way to see it is just zoom in on the PDF. If the artifacts go away on 
zooming in, then they are due to anti-aliasing.

Aditya

Thanks to both of you for the detailed explanations. Printed page shows 
no artifacts and neither does PDF.js when the text is zoomed. So it is 
an issue with anti-aliasing after all.


I'll report it to PDF.js and see what they tell me.

Regards,
Vedran

--
Vedran Miletić
vedran.miletic.net
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / 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
___

[NTG-context] Missing kern when using \feature

[Joseph]

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][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, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / 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
___

[NTG-context] tikz-module not up to date (synchronisation problem with contextgarden?)

[Christian Prim]

Hi

It's been a long time, since a solution for the 'module wrapping error' in
tikz has been proposed here in the list:
https://mailman.ntg.nl/pipermail/ntg-context/2017/090404.html

Since July a fix has been published:
https://github.com/pgf-tikz/pgf/commit/9b24e5cdb8246b1075d02c02c75ff8bcac642c16

A few days ago the release containing the fix was released. On
contextgarden the manual under modules/t-tikz/doc/generic/pgf shows the
current version 3.1.8b, but the source doesn't include the fix. I compared
the source on context-garden (rsync://
contextgarden.net/minimals/current/modules/) with the zip (
https://github.com/pgf-tikz/pgf/archive/3.1.8b.zip). In the zip file the
fix is included, so I'm puzzled...

Is there a synchronisation-problem?

Just wanted to mention it. It's not crucial.

Thanks
Christian
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / 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
___

Re: [NTG-context] A not so short introduction to ConTeXt Mark IV

[Robert Zydenbos]

Thank you, Joaquin, for this wonderfully systematic bit of work. I wish I had 
had this three or four years ago.

There has been a bit of a discussion here about whether ConTeXt manuals should 
start from the assumption that the reader already is familiar with LaTeX or 
not. If I may cast a vote here: I recommend that authors *SHOULD NOT* assume 
such familiarity, because

(1) Knowledge of LaTeX is not just irrelevant, but can actually confuse.

(2) ConTeXt is a complete system in itself that is built up in a more 
consistent way than LaTeX. It does not depend on LaTeX in any way, and authors 
should not risk creating the impression that it does.

Of course there’s nothing wrong if someone were to write parallel materials for 
LaTeX users (‘ConTeXt for LaTeX Users’, or something of the sort). But 
basically LaTeX ought to be ignored completely. I, for one, do not want to have 
anything to do with LaTeX any more, now that ConTeXt is there.

Now that this new manual exists, I can more confidently recommend ConTeXt to 
colleagues.

Thanks once again!

Robert

On 03.01.21 10:45, Joaquín Ataz López wrote:

Hello to all:

Two months ago I informed to the list […]


___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / 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
___

[NTG-context] Size problems in fencing

[Mikael Sundqvist]

Hi,

I have written about these problems some months(year?) ago, but since I
noticed today that the problem persists, I write again. The first problem
is with sizes of nested fences, the second one with the size of lucida
fences. The test file is pasted below.

Let me also take the opportunity to thank for the nice card that arrived in
the mail. Last year's card was still on the refrigerator, and its message
is kind of funny/scary in retrospect. I wish you all a good 2021!

/Mikael

\definemathfence[Set][left="007B,right="007D,command=yes]
\definemathfence[Paren][left="0028,right="0029,command=yes]


\starttext

When using nested fences, if one set the size of the outer one, it applies
also to the inner one, with the same size:
\startformula
\Paren[size=2]{\int_0^1 \Paren{f_1(x)+f_2(x)}\,dx}
\stopformula
If one is not specifying the size of the outer fence, it seems to work
correctly:
\startformula
\Paren{\int_0^1 \Paren{f_1(x)+f_2(x)}\,dx}
\stopformula

\startformula
\Paren{\int_0^1 \Paren[size=1]{f_1(x)+f_2(x)}\,dx}
\stopformula

With most fonts, the sizing works well:

\startformula
\Set[size=0]{a}\quad
\Set[size=1]{a}\quad
\Set[size=2]{a}\quad
\Set[size=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}
\stopformula


\stoptext
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / 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
___

[NTG-context] squeezed

[Hans Hagen]

Hi,

Another example:

\definetweakedfont[squeezed] [xscale=0.90]

\bTABLE
\bTR \bTD foo \eTD \bTD[style=\squeezed] $x = 1$ \eTD \eTR
\bTR \bTD oof \eTD \bTD[style=\squeezed] $x = 2$ \eTD \eTR
\eTABLE

\bTABLE[style=squeezed]
\bTR \bTD $x = 1$ \eTD \bTD  $x = 3$ \eTD \eTR
\bTR \bTD $x = 2$ \eTD \bTD  $x = 4$ \eTD \eTR
\eTABLE

\bTABLE[style=\squeezed\squeezed\squeezed]
\bTR \bTD $x = 1$ \eTD \bTD  $x = 3$ \eTD \eTR
\bTR \bTD $x = 2$ \eTD \bTD  $x = 4$ \eTD \eTR
\eTABLE


-
  Hans Hagen | PRAGMA ADE
  Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
   tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / 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
___

[NTG-context] new upload

[Hans Hagen]

Hi,

A new upload ... I'm playing abit with font tweaks ...

\enableexperiments[fonts.compact] % for the definitions

\starttext

\definefont[FooA][Serif*default @ 12pt 1800 500]
\definefont[FooB][Serif*default @ 12pt 0.85 0.50]
\definefont[FooC][Serif*default @ 12pt]

\definetweakedfont[runwider] [xscale=1.5]
\definetweakedfont[runtaller][yscale=2.5,xscale=.8,yoffset=-.2ex]

{\FooA test test \runwider test test \runtaller test test}\par
{\FooB test test \runwider test test \runtaller test test}\par
{\FooC test test \runwider test test \runtaller test test}\par

\blank {\input tufte }

\blank {\glyphxscale 1070 \input tufte }

\definetweakedfont[squeezed] [xscale=0.9]

\blank $a = mb^2 + \sqrt{123}$
\blank {\squeezed $a = mb^2 + \sqrt{123}$}

\stoptext

Just run these examplex in lmtx to get an idea. It might come in handy 
for special cases, like making sure something fits in some area or make 
for instance last lines look a bit better (posters or so).


For the moment I decided for two additional (optional) scale directives 
in the font definition (hopefully i didn't mess up the ctx parser for 
that). Scales are either fractions or integers (the traditional tex 
scaling in permilles).


Hans

(also, odd in mp and ligs in some cases fixed)


-
  Hans Hagen | PRAGMA ADE
  Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
   tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / 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
___

Re: [NTG-context] RE : Some ligatures don't work in latest LMTX

[Hans Hagen]

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

-
  Hans Hagen | PRAGMA ADE
  Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
   tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / 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
___

[NTG-context] RE : Some ligatures don't work in latest LMTX

[Joseph]

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 \stoptext ThanksBest Joseph De : Jairo A. del RioEnvoyé le :jeudi 7 janvier 2021 17:15À : Hans HagenCc : mailing list for ConTeXt usersObjet :Re: [NTG-context] Some ligatures don't work in latest LMTX Oh, yeah. It works again. Thank you very much :) Jairo El jue., 7 de ene. de 2021 10:20 a. m., Hans Hagen  escribió:On 1/7/2021 3:04 PM, Jairo A. del Rio wrote:> Hmm, it works for Persian because this uses less diacritics than Arabic. > The following fails with LMTX:> > \definefontfamily[main][serif][notonaskharabic][features=arabic]> > \setupdirections[bidi=global,method=one]> > \setupbodyfont[main]> > \starttext> > \obeylines> > %https://www.letsstartthinking.org/Islam/quran-short-phrases-and-verses.php > > > بِسْمِ اللَّـهِ الرَّحْمَـٰنِ الرَّحِيمِ> > \stoptext> > Hi, Hans. Could you please check this out? It works for MKIV, but in > LMTX vowels are misplaced. Thank you in advance.It works here but i have different code in the meantime. We're in a transition to an lmtx version of the font handler. In lmtx we need to do a bit more checking when we are in in compact font mode so it might be that there is temporary loss of some functionality. In principle mkiv and lmtx should do the same as there is no real change in logic.)I'll push an update later today,Hans-                                           Hans Hagen | PRAGMA ADE               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands        tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl- 
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / 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
___