Am 08.09.2011 um 09:55 schrieb Aditya Mahajan:
> On Wed, 7 Sep 2011, Thomas Friedrich wrote:
>
>> Hi,
>>
>> I am having problems typing ">>" when typesetting code within a
>> \definetyping environment.
>>
>> I hope someone might be able to give me a hint. My code looks as
>> follows:
>>
>> \definetyping
>> [Haskell]
>> [ option=commands,
>> before={\startframedtext[width=\makeupwidth,
>> frame=off,bottomframe=on,topframe=on,
>> background=screen,backgroundscreen=.90]},
>> after={\stopframedtext},
>> bodyfont=9pt,
>> margin=1.5em]
>>
>> \startHaskell
>> main = foo >>= bar
>> \stopHaskell
>>
>> Whenever ConTeXt comes across >> anywhere in the text, it just doesn't
>> typeset anything. So in the above case, I get the output:
>>
>> main = foo = bar
>
> Confirmed. >> are eaten in MkII but everything works fine with MkIV. My guess
> is because of automatic ligatures for >>. My usual trick for disabling such
> ligatures in MkII is
>
> \usetypescript [modern] [texnansi]
> \setupbodyfont [modern]
>
> but that does not work in this case. There were some discussions in the past
> about disabling ligatures in typewriter font, but I don't remember the exact
> solution.
No, the culprit is “option=commands" which gobbles “>>”.
Wolfgang
___________________________________________________________________________________
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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
