Thomas A. Schmitz wrote:
> On May 17, 2008, at 9:06 PM, Hans Hagen wrote:
>
>> in node-ini ... you can play with this change ...
>>
>>
>> function nodes.process_characters(head)
>> --~ if status.output_active then
>> if false then
>> return head, false -- true
>>
On May 17, 2008, at 9:06 PM, Hans Hagen wrote:
> in node-ini ... you can play with this change ...
>
>
> function nodes.process_characters(head)
> --~ if status.output_active then
> if false then
> return head, false -- true
> else
>
Great! Yes, this seems
Thomas A. Schmitz wrote:
> On May 17, 2008, at 6:58 PM, Hans Hagen wrote:
>
>>> Another interesting feature is that numbers in the typing
>>> environmnet come
>>> out in oldstyle (they look nice, BTW). This is expected, and can be
>>> avoided by using a complete typescript and loading tt fonts w
On May 17, 2008, at 6:58 PM, Hans Hagen wrote:
>>
>> Another interesting feature is that numbers in the typing
>> environmnet come
>> out in oldstyle (they look nice, BTW). This is expected, and can be
>> avoided by using a complete typescript and loading tt fonts with
>> fefault
>> features,
Aditya Mahajan wrote:
> Hi,
>
> While using oldstyle features with mkiv, -- in a typing environment comes
> out as a endash. I would consider this a bug.
>
> For example:
>
> \setfontfeature{oldstyle}
> \starttext
> \starttyping
> -- A comment 123
> \stoptyping
>
> \stoptext
>
> Another inte
Hi,
While using oldstyle features with mkiv, -- in a typing environment comes
out as a endash. I would consider this a bug.
For example:
\setfontfeature{oldstyle}
\starttext
\starttyping
-- A comment 123
\stoptyping
\stoptext
Another interesting feature is that numbers in the typing environm
