[NTG-context] Re: weird \inlinetypebuffer interaction

[Wolfgang Schuster <wolfgang.schuster.lists@gmail.com>]

Pablo Rodriguez via ntg-context schrieb am 08.05.2024 um 18:05:
> On 5/7/24 22:37, Wolfgang Schuster wrote:
>> [...]
>> \typebuffer disables automatic \endash and \emdash with the
>> \nohyphencollapsing command
>> but the command isn't used for \typeinlinebuffer.
> Many thanks for your explanation, Wolfgang.
> 
> Since \type doesn’t collapse hyphens, wouldn’t it be possible to add
> \nohyphencollapsing to \typeinlinebuffer just for the sake of output
> consistency?

You can make \typeinlinebuffer behave like \type by adding a second 
initializer which besides other things prevents hyphen collapsing.


buff-ver.mkxl:

\protected\def\buff_verbatim_type_buffer_indeed_inline#1#2%
   {\cdef\currenttype{#1}%
    \buff_verbatim_initialize_type_one
+  \buff_verbatim_initialize_type_two
    \dostarttaggedchained\t!verbatim\currenttype\??type
    \clf_typebuffer
      name   {#2}%
      strip  {\v!yes}%
      regime {\currentregime}%
      method {\p_buff_option}%
      nature {inline}% is default anyway
    \relax
    \dostoptagged}

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

maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage  : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive  : https://github.com/contextgarden/context
wiki     : https://wiki.contextgarden.net
___________________________________________________________________________________