* \autoinsertnextspace regression / discrepancy, mkiv to lmtx
@ 2022-10-25 23:52 Rik Kabel via ntg-context
2022-10-26 11:43 ` Hans Hagen via ntg-context
0 siblings, 1 reply; 4+ messages in thread
From: Rik Kabel via ntg-context @ 2022-10-25 23:52 UTC (permalink / raw)
To: ntg-context; +Cc: Rik Kabel
[-- Attachment #1.1: Type: text/plain, Size: 393 bytes --]
The following example produces different results when processed by LMTX
and MkIV. In particular, a space between the X and Y is not
auto-inserted by LMTX, while it is by MkIV.
\starttexdefinition TEST #1
#1\autoinsertnextspace
\stoptexdefinition
\tt
\starttext
\TEST{X} \emph{Y}
\stoptext
The MkIV result is the correct result (in my opinion).
--
Rik
[-- Attachment #1.2: Type: text/html, Size: 685 bytes --]
[-- Attachment #2: Type: text/plain, Size: 496 bytes --]
___________________________________________________________________________________
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
___________________________________________________________________________________
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: \autoinsertnextspace regression / discrepancy, mkiv to lmtx
2022-10-25 23:52 \autoinsertnextspace regression / discrepancy, mkiv to lmtx Rik Kabel via ntg-context
@ 2022-10-26 11:43 ` Hans Hagen via ntg-context
2022-10-26 13:35 ` Rik Kabel via ntg-context
0 siblings, 1 reply; 4+ messages in thread
From: Hans Hagen via ntg-context @ 2022-10-26 11:43 UTC (permalink / raw)
To: ntg-context; +Cc: Hans Hagen
On 10/26/2022 1:52 AM, Rik Kabel via ntg-context wrote:
> The following example produces different results when processed by LMTX
> and MkIV. In particular, a space between the X and Y is not
> auto-inserted by LMTX, while it is by MkIV.
>
> \starttexdefinition TEST #1
> #1\autoinsertnextspace
> \stoptexdefinition
> \tt
> \starttext
> \TEST{X} \emph{Y}
> \stoptext
>
> The MkIV result is the correct result (in my opinion).
more a side effect ... we lookahead and \emph is not some character
I made a variants that does abetter job on that
\starttexdefinition TEST #1
#1%
\autoinsertedspace % subtle name change
\stoptexdefinition
but you have to wait till we update,
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
___________________________________________________________________________________
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: \autoinsertnextspace regression / discrepancy, mkiv to lmtx
2022-10-26 11:43 ` Hans Hagen via ntg-context
@ 2022-10-26 13:35 ` Rik Kabel via ntg-context
2022-10-27 7:54 ` Hans Hagen via ntg-context
0 siblings, 1 reply; 4+ messages in thread
From: Rik Kabel via ntg-context @ 2022-10-26 13:35 UTC (permalink / raw)
To: ntg-context; +Cc: Rik Kabel
On 2022-10-26 07:43, Hans Hagen via ntg-context wrote:
> On 10/26/2022 1:52 AM, Rik Kabel via ntg-context wrote:
>> The following example produces different results when processed by
>> LMTX and MkIV. In particular, a space between the X and Y is not
>> auto-inserted by LMTX, while it is by MkIV.
>>
>> \starttexdefinition TEST #1
>> #1\autoinsertnextspace
>> \stoptexdefinition
>> \tt
>> \starttext
>> \TEST{X} \emph{Y}
>> \stoptext
>>
>> The MkIV result is the correct result (in my opinion).
> more a side effect ... we lookahead and \emph is not some character
>
> I made a variants that does abetter job on that
>
> \starttexdefinition TEST #1
> #1%
> \autoinsertedspace % subtle name change
> \stoptexdefinition
>
> but you have to wait till we update,
>
> Hans
>
>
Thank you in advance for the upcoming fix.
Can you tell us (me) why you chose to create a new macro,
\autoinsertedspace, instead of changing the code for
\autoinsertnextspace in LMTX? Do you see a circumstance under which the
current LMTX behavior of \autoinsertnextspace is desirable or required?
Will the new macro be available under MkIV?
--
Rik
___________________________________________________________________________________
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
___________________________________________________________________________________
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: \autoinsertnextspace regression / discrepancy, mkiv to lmtx
2022-10-26 13:35 ` Rik Kabel via ntg-context
@ 2022-10-27 7:54 ` Hans Hagen via ntg-context
0 siblings, 0 replies; 4+ messages in thread
From: Hans Hagen via ntg-context @ 2022-10-27 7:54 UTC (permalink / raw)
To: ntg-context; +Cc: Hans Hagen
On 10/26/2022 3:35 PM, Rik Kabel via ntg-context wrote:
>
> On 2022-10-26 07:43, Hans Hagen via ntg-context wrote:
>> On 10/26/2022 1:52 AM, Rik Kabel via ntg-context wrote:
>>> The following example produces different results when processed by
>>> LMTX and MkIV. In particular, a space between the X and Y is not
>>> auto-inserted by LMTX, while it is by MkIV.
>>>
>>> \starttexdefinition TEST #1
>>> #1\autoinsertnextspace
>>> \stoptexdefinition
>>> \tt
>>> \starttext
>>> \TEST{X} \emph{Y}
>>> \stoptext
>>>
>>> The MkIV result is the correct result (in my opinion).
>> more a side effect ... we lookahead and \emph is not some character
>>
>> I made a variants that does abetter job on that
>>
>> \starttexdefinition TEST #1
>> #1%
>> \autoinsertedspace % subtle name change
>> \stoptexdefinition
>>
>> but you have to wait till we update,
>>
>> Hans
>>
>>
> Thank you in advance for the upcoming fix.
>
> Can you tell us (me) why you chose to create a new macro,
> \autoinsertedspace, instead of changing the code for
> \autoinsertnextspace in LMTX? Do you see a circumstance under which the
> current LMTX behavior of \autoinsertnextspace is desirable or required?
compatibility .. it also uses a different mechanism for which that name
suits better
> Will the new macro be available under MkIV?
I suppose I can do that if needed,
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
___________________________________________________________________________________
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2022-10-27 7:54 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-10-25 23:52 \autoinsertnextspace regression / discrepancy, mkiv to lmtx Rik Kabel via ntg-context
2022-10-26 11:43 ` Hans Hagen via ntg-context
2022-10-26 13:35 ` Rik Kabel via ntg-context
2022-10-27 7:54 ` Hans Hagen via ntg-context
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).