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 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, and other with oldstyle features. Nevertheless, I find it to be an interesting side effect. Aditya
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 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, and other with oldstyle features. Nevertheless, I find it to be an interesting side effect.
\def\mkinitializeverbatim {\ctxlua{buffers.visualizers.reset()}% \def\obs{\obeyedspace}% \verbatimfont \resetfontfeature \obeycharacters} ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
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, and other with oldstyle features. Nevertheless, I find it to be an interesting side effect.
\def\mkinitializeverbatim {\ctxlua{buffers.visualizers.reset()}% \def\obs{\obeyedspace}% \verbatimfont \resetfontfeature \obeycharacters}
Since we're speaking about oldstyle numbers, here's an interesting little bug in mkiv that has bugged me (no pun intended) for quite some time now. Is there a solution to this one too? Best Thomas \definefontfeature [mytest] [mode =node,script=latn,language=dflt,kern=yes,tlig=yes,trep=yes,onum=yes] \starttypescript [serif] [test] \definefontsynonym [Serif] [name:TeXGyrePagella-Regular] [features=mytest] \stoptypescript \starttypescript [Test] \definetypeface [Test] [rm] [serif] [test] [default] \stoptypescript \usetypescript[Test] \setupbodyfont[Test,12pt] \setupfootertexts[-- \pagenumber\ --] \starttext -- 123456789 -- \stoptext
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 with fefault features, and other with oldstyle features. Nevertheless, I find it to be an interesting side effect. \def\mkinitializeverbatim {\ctxlua{buffers.visualizers.reset()}% \def\obs{\obeyedspace}% \verbatimfont \resetfontfeature \obeycharacters}
Since we're speaking about oldstyle numbers, here's an interesting little bug in mkiv that has bugged me (no pun intended) for quite some time now. Is there a solution to this one too?
Best
Thomas
\definefontfeature [mytest]
[mode =node,script=latn,language=dflt,kern=yes,tlig=yes,trep=yes,onum=yes]
\starttypescript [serif] [test] \definefontsynonym [Serif] [name:TeXGyrePagella-Regular] [features=mytest] \stoptypescript
\starttypescript [Test] \definetypeface [Test] [rm] [serif] [test] [default] \stoptypescript
\usetypescript[Test] \setupbodyfont[Test,12pt]
\setupfootertexts[-- \pagenumber\ --]
\starttext -- 123456789 -- \stoptext
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 ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
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 to take care of the problem; thanks a lot, Hans! Best Thomas
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 else
Great! Yes, this seems to take care of the problem; thanks a lot, Hans!
we need to make sure that node lists are only processed once, i.e. when the box is being built and this is a left over from previous luatex versions where we could not be sure (in the otr the boxes pass by again) but i think that by now we have that bit of luatex rather stable Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
participants (3)
-
Aditya Mahajan -
Hans Hagen -
Thomas A. Schmitz