- ntg-context - NTG Mailing Lists

\startuseMPgraphic
by Jeong Dal 11 Apr '16

11 Apr '16

Dear Hans van der Meer, Thank you for your sample code. I learned how to pass the value of the variables. BTW, if I change “orange” to “red” or “green”, it is working fine. I think that “orange” is not the predefined color. There is no color “orange” in the MetaFun manual either. Thank you. Best regards, Dalyoung > \starttext > \startuseMPgraphic{myname1}{color} > pickup pencircle scaled 1mm; > draw unitsquare scaled 1cm withcolor \MPvar{color}; > \stopuseMPgraphic > > \startuseMPgraphic{myname2}{color=red} > pickup pencircle scaled 1mm; > draw unitsquare scaled 1cm withcolor \MPvar{color}; > \stopuseMPgraphic > > \useMPgraphic{myname1}{color=blue} > \useMPgraphic{myname2}{color=orange} > > \stoptext > > Hans van der Meer >

7 9

Re: [NTG-context] Ligature color is not reliable
by Hans Hagen 11 Apr '16

11 Apr '16

On 4/11/2016 9:06 PM, Jan Tosovsky wrote: > On 2016-04-09 Jan Tosovsky wrote: >> >> for an illustration I wanted to colorize all ligatures, but the >> following method is not reliable for three character ligatures >> - which ends up black. >> >> While tested with Palatino, it can be simulated even with >> a default font (however there are missing ffi and ffl ligatures). >> >> \definefontfamily[palatino][rm][Palatino Linotype] >> [features={default, quality}] >> \setupbodyfont[palatino] >> >> \starttext >> Je{\red ff}, the o{\red ffi}ce on the {\red fi}rst {\red fl}oor >> is o{\red ffl}ine. >> \stoptext >> >> What is happening here? >> > > Any idea how to properly colorize those ligatures? update ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------

2 1

framedtext
by Meer, Hans van der 11 Apr '16

11 Apr '16

I am getting an unexpected results with framedtexts.Why is the second "centered" not centered? \starttext \startframedtext[left][frame=on,offset=0pt,width=broad] left\hfill \stopframedtext \startframedtext[middle][frame=on,offset=0pt,width=broad] \hfil centered\hfil \stopframedtext \startframedtext[middle][frame=on,offset=0pt,width=broad] \hfill centered\hfill \stopframedtext \startframedtext[right][frame=on,offset=0pt,width=broad] \hfill right \stopframedtext \startframedtext[none][frame=on,offset=0pt,width=broad] none \stopframedtext \stoptext This is LuaTeX, Version beta-0.90.0 (TeX Live 2016) ConTeXt ver: 2016.04.01 13:01 MKIV beta fmt: 2016.4.5 int: english/english Hans van der Meer

5 7

Re: [NTG-context] Ligature color is not reliable
by Jan Tosovsky 11 Apr '16

11 Apr '16

On 2016-04-09 Jan Tosovsky wrote: > > for an illustration I wanted to colorize all ligatures, but the > following method is not reliable for three character ligatures > - which ends up black. > > While tested with Palatino, it can be simulated even with > a default font (however there are missing ffi and ffl ligatures). > > \definefontfamily[palatino][rm][Palatino Linotype] > [features={default, quality}] > \setupbodyfont[palatino] > > \starttext > Je{\red ff}, the o{\red ffi}ce on the {\red fi}rst {\red fl}oor > is o{\red ffl}ine. > \stoptext > > What is happening here? > Any idea how to properly colorize those ligatures? Thanks, Jan

1 0

Re: [NTG-context] Weird background colors in autogenerated index
by Pablo Rodriguez 11 Apr '16

11 Apr '16

On 04/10/2016 11:00 PM, Jan Tosovsky wrote: > On 2016-04-10 Hans Hagen wrote: >> On 4/9/2016 11:22 PM, Jan Tosovsky wrote: >>> >>> since LuaTeXt 0.81 my back-of-the-book index (register) is >>> with generated strange background colors. The index title >>> is typeset in yellowish background and the left column of >>> the last index page has a blue background, see the attachment. >>> >>> ... It was fine in the version 0.80. >> >> no example > > I've published both the ConTeXt source and the final PDF here: > http://drifted.in/other/context/ Jan, here you have the minimal sample: \showgrid \starttext a\index{b} \completeindex \stoptext Comment the first line and colors background colors will disappear. Don’t know whether it is a bug or not, but this is only related to \showgrid. I hope it helps, Pablo -- http://www.ousia.tk

3 2

Interactionmenu not creating a button for the final page
by Brian Ballsun-Stanton 11 Apr '16

11 Apr '16

Given the following code: \enableregime [utf] > \mainlanguage [en] > \definepapersize[sheet][width=1280px, height=960px] > \setuppapersize[sheet][sheet] > \setupexternalfigures[directory={img, > /home/ubuntu/EGU2016-Presentation, > /home/ubuntu/ConTeXt/img}] > \usemodule[simplefonts] > \setmainfont[Adventor][expansion=quality,protrusion=quality] > \setupcolors[state=start] > \definecolor[faimsblue][h=1B3E93] > \definecolor[faimsorange][h=F68E1E] > \setuphead[section][placehead=yes, page=yes, number=no, align=middle, > style={\setupbodyfont[40pt]}] > > \setuplayout[ > backspace=.01\pagewidth, > header=0pt, > footer=.02\pageheight, > topspace=.185\pageheight, > cutspace-.1\pagewidth, > width=.87\pagewidth, > height=.798\pageheight, > bottomspace=.8cm, > bottom=12pt > ] > \setuppagenumbering[location=] > \setupinteraction > [page=yes, > color=faimsblue, > contrastcolor=faimsorange, > menu=on, > state=start] > \setupsubpagenumber > [way=bytext, > state=start] > \startinteractionmenu[bottom] > {\interactionbar[alternative=f,width=\makeupwidth,height=2ex]} > \stopinteractionmenu > \starttext > \input knuth > \section{section 1} > \input knuth > > \section{section 2} > \input knuth > > > \section{section 3} > \input knuth > > > \section{section 4} > \input knuth > \stoptext (used in a real presentation: http://context.fedarch.org/Context/presentation.pdf with environment at https://github.com/FAIMS/EGU2016-Presentation/blob/master/envpresentation.t… ) it seems that the interactionmenu doesn't have a button for the final page. I'm assuming I did something wrong, but I'm not quite sure what it is.

2 1

\startuseMPgraphic
by Meer, Hans van der 11 Apr '16

11 Apr '16

I seem to remember the following variations in \startuseMPgraphic. (1) \startuseMPgraphic{name}{comma separated list of variables} (2) \startuseMPgraphic{name}{comma separated list of key=value pairs} In the second case one is able to set a default value to that variable, possibly to be overridden with \useMPgraphic{name}{key=value}. I very much would like to specify default values on the \startuseMPgraphic definition of the graphic. However, I cannot get option (2) working. Do I have a bad memory (possible of course ;-), Has it to be done otherwise? In the example below the graphic myname1 is ok, but myname2 gives the following error: metapost > error: >> orange ! Improper type. <to be read again> ; <*> ...raw unitsquare scaled 1cm withcolor orange; minimal example: \starttext \startuseMPgraphic{myname1}{color} pickup pencircle scaled 1mm; draw unitsquare scaled 1cm withcolor \MPvar{color}; \stopuseMPgraphic \startuseMPgraphic{myname2}{color=red} pickup pencircle scaled 1mm; draw unitsquare scaled 1cm withcolor \MPvar{color}; \stopuseMPgraphic \useMPgraphic{myname1}{color=blue} \useMPgraphic{myname2}{color=orange} \stoptext Hans van der Meer

2 3

Re: [NTG-context] Weird background colors in autogenerated index
by Hans Hagen 10 Apr '16

10 Apr '16

On 4/9/2016 11:22 PM, Jan Tosovsky wrote: > Dear All, > > since LuaTeXt 0.81 my back-of-the-book index (register) is generated with > strange background colors. The index title is typeset in yellowish > background and the left column of the last index page has a blue background, > see the attachment. > > I've thought I reported it, but it is still there even in 0.95. It was fine > in the version 0.80. > > Could this be somehow eliminated? no example ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------

2 1

Re: [NTG-context] Protrusion cancellation by index term
by Hans Hagen 10 Apr '16

10 Apr '16

On 4/10/2016 12:53 PM, Jan Tosovsky wrote: > On 2016-04-03 Hans Hagen wrote: >> On 4/1/2016 9:59 PM, Jan Tosovsky wrote: >>> On 2016-04-01 Hans Hagen wrote: >>>> On 3/31/2016 10:47 PM, Wolfgang Schuster wrote: >>>>>> On 2016-03-31 Jan Tosovsky wrote: >>>>>> >>>>>> I couldn't find any details for that \leftboundary >>>>> >>>>> spac-ver.mkiv: >>>>> >>>>> \unexpanded\def\leftboundary {\boundary\plusone} >>>>> \unexpanded\def\rightboundary {\boundary\plustwo} >>>> >>>> it will instruct the protrusion checker to skip the next or >>>> previous node (e.g. a char or hbox or ...) when looking for >>>> an edge >>> >>> Thanks for details. So if that worked with plain \hbox should be >> taken rather as coincidence? >> >> a hbox becomes one node so that one node is ignored >> > > I found a nasty drawback of this method. If that hbox is used, the first paragraph is not evaluated correctly and considered as the second one. When indentation is enabled, the first paragraph after the title is not usually indented, but now it is. Additionaly, even if indenting is disabled, there is a bigger distance between title and the following para. > > \setupindenting[yes, 2em] > > \starttext > > \section{The first section}\index{the first section} > > The first para.\par > The second para. > > \section{The second section}\leftboundary\hbox{\index{the second section}} > > The first para.\par > The second para. > > \stoptext > > > I could eventually avoid inserting that 'index' tweak into titles, but this is another exception which an end-user should keep in mind ..and.. I hate exceptions ;-) > > Any idea? everything protrusion is an exception \unexpanded\def\myindex#1% {\dontleavehmode \ifcase\normalprotrudechars\else\leftboundary\hbox\fi {\index{#1}}} might work (untested) given that protrusion is off in the title Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------

1 0

Re: [NTG-context] Protrusion cancellation by index term
by Hans Hagen 10 Apr '16

10 Apr '16

On 4/1/2016 9:59 PM, Jan Tosovsky wrote: > On 2016-04-01 Hans Hagen wrote: >> On 3/31/2016 10:47 PM, Wolfgang Schuster wrote: >>>> On 2016-03-31 Jan Tosovsky wrote: >>>> >>>> I couldn't find any details for that \leftboundary >>> >>> spac-ver.mkiv: >>> >>> \unexpanded\def\leftboundary {\boundary\plusone} >>> \unexpanded\def\rightboundary {\boundary\plustwo} >> >> it will instruct the protrusion checker to skip the next or >> previous node (e.g. a char or hbox or ...) when looking for >> an edge > > Thanks for details. So if that worked with plain \hbox should be taken rather as coincidence? a hbox becomes one node so that one node is ignored > I prefer motto the fewer commands, the better :-) > > Jan > > > ___________________________________________________________________________________ > If your question is of interest to others as well, please add an entry to the Wiki! > > maillist : ntg-context(a)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 > ___________________________________________________________________________________ > -- ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------

2 1