[NTG-context] Re: zint 2.12.0 barcode generator

[Bruce Horrocks]

On 20 Aug 2023, at 17:28, Keith McKay  wrote:
> 
> Hi all,
> 
> I've updated the zint barcode generator on my mac mini to 2.12.0 and now no 
> barcode is produced. I have this vague recollection that it is only the 
> 2.10.0 version of zint which works in ConTeXt. If I am correct, is ConTeXt 
> likely to be updated so that 2.12.0 works?  I originally installed zint with 
> Homebrew. There is a very complicated thread on stackoverflow on how to 
> downgrade to previous versions of a formula in homebrew, but it is far too 
> complicated for my wee brain.

zint 2.12.0 works for me on an x64 Mac mini using ConTeXt ver: 2023.08.10 02:59

Following the instructions here 

1) I had to create the path $TEXROOT/tex/texmf-osx-64/bin/lib/luametatex/zint
2) I symbolic linked directly to the homebrew created libzint library

   $ cd $TEXROOT/tex/texmf-osx-64/bin/lib/luametatex/zint
   $ ln -s /usr/local/Cellar/zint/2.12.0/lib/libzint.dylib libzint.so

3) Then
   $ cd ~
   $ mtxrun --generate

4) and the sample file

   \usemodule[zint]
   \starttext
   \barcode[alternative=isbnx, text=9783865419026, width=4cm]
   \stoptext

   produced a barcode.

—
Bruce Horrocks
Hampshire, UK

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

maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___

[NTG-context] Re: Inconsistent behavior: \addfontfeature and CLD local function

[Hamid,Idris]

Ok, understood. Thank you for the explanation.

Best wishes
Idris

--
Professor Idris Samawi Hamid
Department of Philosophy
Colorado State University
Fort Collins, CO 80523
On Aug 20, 2023, 9:45 AM -0600, Hans Hagen , wrote:
** Caution: EXTERNAL Sender **

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, tfmdata.characters do
v.width = 1.75 * (v.height or 0)
v.depth = 1.75 * (v.depth or 0)
end
end

local specification = {
name = "sqtfm",
description = "test",
manipulators = {
base = squeeze,
node = squeeze,
}
}
because much more has to be done to satisfy the backend (liek advance
with and such) .. you cannot just change dimensions on the fly for
characters that could potentially be shared just as you can't change
glyph dimension mid document

Hans

-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | 
https://nam10.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.pragma-ade.nl%2F&data=05%7C01%7CIdris.Hamid%40colostate.edu%7C2e50b62ee65c41cb704308dba1947214%7Cafb58802ff7a4bb1ab21367ff2ecfc8b%7C0%7C0%7C638281431156972904%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=SE09abKBexjImz73ucHLxz4Wv6reS75qYg88LrdNOrg%3D&reserved=0
 | 
https://nam10.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.pragma-pod.nl%2F&data=05%7C01%7CIdris.Hamid%40colostate.edu%7C2e50b62ee65c41cb704308dba1947214%7Cafb58802ff7a4bb1ab21367ff2ecfc8b%7C0%7C0%7C638281431156972904%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=HDd8xwSOEAqmBG04WkLwG2NBE8JXlAeGWKVI9iqIU1A%3D&reserved=0
-

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

maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___

[NTG-context] Re: zint 2.12.0 barcode generator

[Keith McKay]

Thanks Michal!
I'll give this a try over the next few days and report back.
Best wishes
Keith

On Sun, 20 Aug 2023, 18:38 Michal Vlasák,  wrote:

> On Sun Aug 20, 2023 at 6:28 PM CEST, Keith McKay wrote:
> > Hi all,
> >
> > I've updated the zint barcode generator on my mac mini to 2.12.0 and now
> > no barcode is produced. I have this vague recollection that it is only
> > the 2.10.0 version of zint which works in ConTeXt. If I am correct, is
> > ConTeXt likely to be updated so that 2.12.0 works?  I originally
> > installed zint with Homebrew. There is a very complicated thread on
> > stackoverflow on how to downgrade to previous versions of a formula in
> > homebrew, but it is far too complicated for my wee brain.
>
> Hans updated ConTeXt to account for 2.12.0 already in April, so it
> should work, but maybe there is some subtle error (like there was when
> we upgraded to 2.11).
>
> Unfortunately I am unable to take a closer look until the end of the
> month. In the meantime can you please try to compile the library
> yourself? Here are the instructions:
>
> https://github.com/contextgarden/luametatex-optional-libraries
>
> I.e. on Linux (please adjust for macOS):
>
> git clone --recursive
> https://github.com/contextgarden/luametatex-optional-libraries.git
> cd luametatex-optional-libraries
> cmake -S . -B build -DCMAKE_BUILD_TYPE=Release
> cmake --build build -j4
> cp build/libzint.so
> /path/to/context/tex/texmf-linux-64/bin/lib/luametatex/libs/libzint.so
>
> The repository is still based on zint 2.11, I will update it to 2.12
> after I confirm that it works.
>
> Michal
>
> ___
> If your question is of interest to others as well, please add an entry to
> the Wiki!
>
> maillist : ntg-context@ntg.nl /
> https://www.ntg.nl/mailman/listinfo/ntg-context
> webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
> archive  : https://bitbucket.org/phg/context-mirror/commits/
> wiki : https://contextgarden.net
>
> ___
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___

[NTG-context] Re: zint 2.12.0 barcode generator

[Michal Vlasák]

On Sun Aug 20, 2023 at 6:28 PM CEST, Keith McKay wrote:
> Hi all,
>
> I've updated the zint barcode generator on my mac mini to 2.12.0 and now 
> no barcode is produced. I have this vague recollection that it is only 
> the 2.10.0 version of zint which works in ConTeXt. If I am correct, is 
> ConTeXt likely to be updated so that 2.12.0 works?  I originally 
> installed zint with Homebrew. There is a very complicated thread on 
> stackoverflow on how to downgrade to previous versions of a formula in 
> homebrew, but it is far too complicated for my wee brain.

Hans updated ConTeXt to account for 2.12.0 already in April, so it
should work, but maybe there is some subtle error (like there was when
we upgraded to 2.11).

Unfortunately I am unable to take a closer look until the end of the
month. In the meantime can you please try to compile the library
yourself? Here are the instructions:

https://github.com/contextgarden/luametatex-optional-libraries

I.e. on Linux (please adjust for macOS):

git clone --recursive 
https://github.com/contextgarden/luametatex-optional-libraries.git
cd luametatex-optional-libraries
cmake -S . -B build -DCMAKE_BUILD_TYPE=Release
cmake --build build -j4
cp build/libzint.so 
/path/to/context/tex/texmf-linux-64/bin/lib/luametatex/libs/libzint.so

The repository is still based on zint 2.11, I will update it to 2.12
after I confirm that it works.

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

maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___

[NTG-context] Re: redefine space to be the same as \␣ similar to knuthian approach

[Hans Hagen via ntg-context]

Carlos,

> On 8/20/2023 6:41 PM, Wolfgang Schuster wrote:


And now it gets even worse, see 
https://meeting.contextgarden.net/2021/talks/2021-09-21/starttext.pdf 
why \starttext is necessar
And watch how \startTEXpage is defined. It clearly explains why that 
works without.


Also watch how \TEX\ comes our without the space between T and E that 
occurs at yoru end.


And finally, appreciate the nice layout / setup of that presentation, 
which contradicts your (implcit and/or explicit) claims that lmtx is 
unusable.


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 / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___

[NTG-context] Re: redefine space to be the same as \␣ similar to knuthian approach

[Hans Hagen]

On 8/20/2023 5:51 PM, Carlos wrote:

On Sun, Aug 20, 2023 at 03:38:15PM +0200, Wolfgang Schuster wrote:

Carlos schrieb am 19.08.2023 um 15:32:

On Fri, Aug 18, 2023 at 08:58:58PM +0200, Wolfgang Schuster wrote:

Hi,

1. Learn to two provide a working minimal example which shows the problem.


Did the minimal example I provided earlier wasn't enough for you?

Besides, You know perfectly well that \stoptext is not even necessary,
superflous; it's not required to compile any context flavor file for
ages now.

So I suggest you to save those keystrokes for other tasks. Not those,
petty petty betty. I know it's hard to teach an ol' dog new tricks,
but… it's worth to try! right?


Please explain why this example (which is a valid ConTeXt document) works


Opening a group with \starttext makes no sense because there is nothing after 
\stoptext.

The possibility to nest \starttext is necessary when you \startproduct etc. 
where components can be be documents on its own and this means \startcomponent 
includes \starttext in its
definition.


 begin example
\starttext

\starttext

\stoptext

\stoptext
 end example

but this doesn't.

 begin example
\starttext

\starttext
 end example

Wolfgang


Take a look at the command line when you process a file and you should see 
something like this:

As you can see the luatex engine processes the file cont-yes.mkiv and not your 
document which put as argument to context. Your document is just read by 
cont-yes.mkiv and at the end of the document ConTeXt inserts an extra \stoptext 
which is ignored when your document
is valid (equal number of \starttext and \stoptext).


The bonus \starttext is just there so that we can use \startTEXpage etc 
without wrapper and a second bonus is that it catches sloppy coding and 
if a user want to take a shortcut and save a handful of keystrokes it's 
fine for me but support converges to zero (unless one pays top money for 
the incovenience). There is only so much you can expect from volunteers.



Wolfgang. I do appreciate your emphasis and your input on all of this.
I do. I really do. But we can't go over this, over and over again. Do
you know who said the above? Not me. You. Do you know whose remarks
are those? Not mine.  Yours.

Replace cont-yes.mkiv with the newer equivalent. And you're right though. 
\starttext is not even needed most of the times.
Wolfgang tries to educate you ... starttext is the anchor for checking 
if a bodyfont has been defined and if not it kicks in some default.


Now with that said:

When Wolfgang asks / tells something because there is nothing in context 
that he doesn't know. And you can bet then he knowa more than you do 
about the internals, objectives and implementation. So, let me put it a 
bit stronger: if Wolfgang gives you an answer that you don't like, you 
should be very careful in your answering because there is very little 
change that he's wrong. To stress his position here: if he sends me a 
patch I can merge it in without testing it which (believe me) is a 
rather unique positin. From this you might conclude that I don't like 
your tone.


And with that out if the way:

When Mikael wonders if there might be something with your installation 
you should indeed sit down and wonder a bit if that could be the case 
because he is a pretty good tester who had been around for quite a 
while. So you can be sure that he tested it well and that he has a 
proper setup. Personally I'd be worried if someone doubts my installation.


Did you install from the garden, using the lmtx installer? Because that 
is the reference. Everything installed otherwise is the users problem.


Which brings me to this file read only thing you mention. If your font 
cache is not writable you migth end up with bad metrics indeed just 
because there are no font resources but that's not up to context to deal 
with.


Also, \␣ is a fixed space and has no glue so i keep wondering what  this 
brings to the picture,


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 / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___

[NTG-context] Re: redefine space to be the same as \␣ similar to knuthian approach

[Wolfgang Schuster]

Carlos schrieb am 20.08.2023 um 17:51:

On Sun, Aug 20, 2023 at 03:38:15PM +0200, Wolfgang Schuster wrote:

Carlos schrieb am 19.08.2023 um 15:32:

On Fri, Aug 18, 2023 at 08:58:58PM +0200, Wolfgang Schuster wrote:

Hi,

1. Learn to two provide a working minimal example which shows the problem.


Did the minimal example I provided earlier wasn't enough for you?

Besides, You know perfectly well that \stoptext is not even necessary,
superflous; it's not required to compile any context flavor file for
ages now.

So I suggest you to save those keystrokes for other tasks. Not those,
petty petty betty. I know it's hard to teach an ol' dog new tricks,
but… it's worth to try! right?

Please explain why this example (which is a valid ConTeXt document) works


Opening a group with \starttext makes no sense because there is nothing after 
\stoptext.

The possibility to nest \starttext is necessary when you \startproduct etc. 
where components can be be documents on its own and this means \startcomponent 
includes \starttext in its
definition.


 begin example
\starttext

\starttext

\stoptext

\stoptext
 end example

but this doesn't.

 begin example
\starttext

\starttext
 end example

Wolfgang

Take a look at the command line when you process a file and you should see 
something like this:

As you can see the luatex engine processes the file cont-yes.mkiv and not your 
document which put as argument to context. Your document is just read by 
cont-yes.mkiv and at the end of the document ConTeXt inserts an extra \stoptext 
which is ignored when your document
is valid (equal number of \starttext and \stoptext).

Wolfgang. I do appreciate your emphasis and your input on all of this.
I do. I really do. But we can't go over this, over and over again. Do
you know who said the above? Not me. You. Do you know whose remarks
are those? Not mine.  Yours.


Just because ConTeXt fixes your mistake doesn't mean you should abuse it 
and *no* user should learn from your example.


Each ConTeXt document should contain a starttext/stoptext  pair or 
equivalent commands (e.g. startdocument/stopdocument or 
startproduct/stopproduct).



Replace cont-yes.mkiv with the newer equivalent. And you're right though. 
\starttext is not even needed most of the times.


And now it gets even worse, see 
https://meeting.contextgarden.net/2021/talks/2021-09-21/starttext.pdf 
why \starttext is necessary.


Wolfgang

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

maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___

[NTG-context] zint 2.12.0 barcode generator

[Keith McKay]

Hi all,

I've updated the zint barcode generator on my mac mini to 2.12.0 and now 
no barcode is produced. I have this vague recollection that it is only 
the 2.10.0 version of zint which works in ConTeXt. If I am correct, is 
ConTeXt likely to be updated so that 2.12.0 works?  I originally 
installed zint with Homebrew. There is a very complicated thread on 
stackoverflow on how to downgrade to previous versions of a formula in 
homebrew, but it is far too complicated for my wee brain.


Thanks

Keith McKay

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

maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___

[NTG-context] Re: redefine space to be the same as \␣ similar to knuthian approach

[Carlos]

On Sun, Aug 20, 2023 at 03:38:15PM +0200, Wolfgang Schuster wrote:
> Carlos schrieb am 19.08.2023 um 15:32:
> > On Fri, Aug 18, 2023 at 08:58:58PM +0200, Wolfgang Schuster wrote:
> > > Hi,
> > > 
> > > 1. Learn to two provide a working minimal example which shows the problem.
> > > 
> > Did the minimal example I provided earlier wasn't enough for you?
> > 
> > Besides, You know perfectly well that \stoptext is not even necessary,
> > superflous; it's not required to compile any context flavor file for
> > ages now.
> > 
> > So I suggest you to save those keystrokes for other tasks. Not those,
> > petty petty betty. I know it's hard to teach an ol' dog new tricks,
> > but… it's worth to try! right?
> 
> Please explain why this example (which is a valid ConTeXt document) works
> 

Opening a group with \starttext makes no sense because there is nothing after 
\stoptext.

The possibility to nest \starttext is necessary when you \startproduct etc. 
where components can be be documents on its own and this means \startcomponent 
includes \starttext in its
definition.

>  begin example
> \starttext
> 
> \starttext
> 
> \stoptext
> 
> \stoptext
>  end example
> 
> but this doesn't.
> 
>  begin example
> \starttext
> 
> \starttext
>  end example
> 
> Wolfgang

Take a look at the command line when you process a file and you should see 
something like this:

As you can see the luatex engine processes the file cont-yes.mkiv and not your 
document which put as argument to context. Your document is just read by 
cont-yes.mkiv and at the end of the document ConTeXt inserts an extra \stoptext 
which is ignored when your document
is valid (equal number of \starttext and \stoptext).

Wolfgang. I do appreciate your emphasis and your input on all of this.
I do. I really do. But we can't go over this, over and over again. Do
you know who said the above? Not me. You. Do you know whose remarks
are those? Not mine.  Yours.

Replace cont-yes.mkiv with the newer equivalent. And you're right though. 
\starttext is not even needed most of the times. 

> 
> ___
> If your question is of interest to others as well, please add an entry to the 
> Wiki!
> 
> maillist : ntg-context@ntg.nl / 
> https://www.ntg.nl/mailman/listinfo/ntg-context
> webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
> archive  : https://bitbucket.org/phg/context-mirror/commits/
> wiki : https://contextgarden.net
> ___

-- 
Real Users never use the Help key.

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

maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___

[NTG-context] Re: Inconsistent behavior: \addfontfeature and CLD local function

[Hans Hagen]

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, tfmdata.characters do
 v.width = 1.75 * (v.height or 0)
 v.depth  = 1.75 * (v.depth  or 0)
 end
end

local specification = {
 name= "sqtfm",
 description = "test",
 manipulators = {
 base = squeeze,
 node = squeeze,
 }
}
because much more has to be done to satisfy the backend (liek advance 
with and such) .. you cannot just change dimensions on the fly for 
characters that could potentially be shared just as you can't change 
glyph dimension mid document


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 / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___

[NTG-context] Inconsistent behavior: \addfontfeature and CLD local function

[Hamid,Idris]

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  = 1.75 * (v.depth  or 0)
end
end

local specification = {
name= "sqtfm",
description = "test",
manipulators = {
base = squeeze,
node = squeeze,
}
}

fonts.handlers.otf.features.register(specification)
\stopluacode

\definefontfeature[forceno]
  [mode=node,
   script=latn]


\definefontfeature[forceyes]
  [mode=node,
   script=latn,
   smcp=force,
   sqtfm=force]
   % smcp=yes,
   % sqtfm=yes]

\showglyphs

\startTEXpage[offset=1em]
\definedfont[texgyretermes-regular*forceyes]
% \definedfont[texgyretermes-regular*forceno]
% \addfeature{forceyes}

abcdefg
\stopTEXpage
==
 You may toggle these lines:

\definedfont[texgyretermes-regular*forceyes]
% \definedfont[texgyretermes-regular*forceno]
% \addfeature{forceyes}

With
\definedfont[texgyretermes-regular*forceyes]
active we get the expected result: small caps plus some negative squeeze (= 
spread in this case).

With
\definedfont[texgyretermes-regular*forceno]
\addfeature{forceyes}
active we get an *unexpected* result: small caps but no negative squeeze.

(Similar results occur if we toggle the "=force" lines with the "=yes" lines, 
but the larger project of which this is the MWE uses the force key.)

Clue: A CLD with a feature defined via fonts.handlers.otf.addfeature doesn't 
seem to have this problem:

==

\startluacode
local function squeeze(tfmdata)
for k, v in next, tfmdata.characters do
v.width = 1.75 * (v.height or 0)
v.depth  = 1.75 * (v.depth  or 0)
end
end

local specification = {
name= "sqtfm",
description = "test",
manipulators = {
base = squeeze,
node = squeeze,
}
}

fonts.handlers.otf.features.register(specification)

fonts.handlers.otf.addfeature {
name = "stest",
type = "substitution",
data = {
a = "X",
b = "P",
}
}
\stopluacode

\definefontfeature[forceno]
  [mode=node,
   script=latn]


\definefontfeature[forceyes]
  [mode=node,
   script=latn,
   % % smcp=force,
   sqtfm=force,
   stest=force]
   % % smcp=yes,
   % sqtfm=yes,
   % stest=yes]

\showglyphs

\startTEXpage[offset=1em]
\definedfont[texgyretermes-regular*forceyes]
% \definedfont[texgyretermes-regular*forceno]
% \addfeature{forceyes}

abcdefg
\stopTEXpage
==

So only the local-function feature appears to exhibit this inconsistency.

What is the explanation for this inconsistent behavior?
Is there a way to get the expected result for \addfeature etc.?

Thank you in advance.

Best wishes
Idris

--
Professor Idris Samawi Hamid
Department of Philosophy
Colorado State University
Fort Collins, CO 80523
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___

[NTG-context] Re: redefine space to be the same as \␣ similar to knuthian approach

[Wolfgang Schuster]

Carlos schrieb am 19.08.2023 um 15:32:

On Fri, Aug 18, 2023 at 08:58:58PM +0200, Wolfgang Schuster wrote:

Hi,

1. Learn to two provide a working minimal example which shows the problem.


Did the minimal example I provided earlier wasn't enough for you?

Besides, You know perfectly well that \stoptext is not even necessary,
superflous; it's not required to compile any context flavor file for
ages now.

So I suggest you to save those keystrokes for other tasks. Not those,
petty petty betty. I know it's hard to teach an ol' dog new tricks,
but… it's worth to try! right?


Please explain why this example (which is a valid ConTeXt document) works

 begin example
\starttext

\starttext

\stoptext

\stoptext
 end example

but this doesn't.

 begin example
\starttext

\starttext
 end example

Wolfgang

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

maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___

[NTG-context] backend not forcing 1000 width units on fonts; em size must be applied or else fails

[Carlos]

Mikael, Wolfgang: 

This is in reference to the prior 

Re: redefine space to be the same as \␣ similar to knuthian approach

> Maybe your system is broken?
> 
> >
> > > 2. The example below results in a correct output for \TEX.
> > >
> >
> > Not in my end with any font other than latin modern
> 
> Here
> 
> \setupbodyfont[stixtwo]
> 
> 
> \setuplayout[width=16cm]
> \showmakeup
> 
> \starttext
> 
> Thus, I came to the conclusion that the designer of a new
> system must not only be the implementer and first
> large||scale user; the designer should also write the first
> user manual.
> \setupbodyfont[12.895pt]
> 
> {\ss The separation of any of these four components would have
> hurt \TeX\ significantly. If I had not participated fully in
> all these activities, literally hundreds of improvements
> would never have been made, because I would never have
> thought of them or perceived why they were important.\par}

After long hours of meditation I was going to ask you, Mikael, what
exactly did you mean by «maybe your system is broken» but I chose to
have chatgpt to provide me all the answers instead; just kidding :) 

But It seems as if any other font without the correct width units causes
kerning to be thrown off most noticeably  on control sequences such as
\TeX\ and presumably, this, in turn, rightly so, also causes
those extra spaces all over

When I read the log it said that the backend > fonts > width units are
being forced to be 1000, but in reality this never happened. If it had
happened, I wouldnt' have had this issue with sizes say at 10pt and 11pt

The permissions for these font files are 644 or read permissions only
and I wrongly assumed this would be taken care of by the backend,
but by the looks of it, it didn't.

Anyhow. Thank you for your time Mikael, Wolfgang. you too Hans.  


-- 
Seems a computer engineer, a systems analyst, and a programmer were
driving down a mountain when the brakes gave out.  They screamed down the
mountain, gaining speed, but finally managed to grind to a halt, more by
luck than anything else, just inches from a thousand foot drop to jagged
rocks.  They all got out of the car:
The computer engineer said, "I think I can fix it."
The systems analyst said, "No, no, I think we should take it
into town and have a specialist look at it."
The programmer said, "OK, but first I think we should get back
in and see if it does it again."

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

maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___