- ntg-context - NTG Mailing Lists

chart module \connection[cc]
by Alan BRASLAU 11 Nov '12

11 Nov '12

Hello, Once again, let me say that the chart module is great! In the following example 3 columns x 2 rows, I connect the cell {3,2} with the cell {2,1}. In the absence of the cell {2,2}, the arrow nicely goes through the center of this blank space. \usemodule [chart] \setupFLOWcharts [nx=3,ny=2, dx=2\bodyfontsize,dy=2\bodyfontsize, width=7\bodyfontsize,height=7\bodyfontsize, maxwidth=\textwidth] \starttext \startFLOWchart [minimal] \startFLOWcell \name {11} \location {1,1} \text {1,1} \connection [rl] {21} \stopFLOWcell \startFLOWcell \name {21} \location {2,1} \text {2,1} \connection [rl] {31} \stopFLOWcell \startFLOWcell \name {31} \location {3,1} \text {3,1} \connection [bt] {32} \stopFLOWcell % \startFLOWcell % \name {22} % \location {2,2} % \text {2,2} % \stopFLOWcell \startFLOWcell \name {32} \location {3,2} \text {3,2} \connection [lb] {21} \stopFLOWcell \stopFLOWchart \FLOWchart [minimal] \stoptext Question (or perhaps feature request), it would be nice to be able to connect the cells {3,2} and {2,1} using a diagonal arrow, running directly from the center of one cell to the center of the other, of course ending at the intersections with the cell shapes outlines. Is this possible? A decent syntax could be \connection [cc] {21} This syntax could also nicely work for the other connections, without having to specify "l" or "r" or "t" or "b". Thus, \connection [rl] {21} for the cell {1,1} could be replaced by \connection [cc] {21} yielding the same result. I can figure out how to do this in metapost, but I have not looked into the chart module code. Alan

1 0

Clubpenalty / Windowspenalty
by "H. Özoguz" 11 Nov '12

11 Nov '12

Hi there, is there some equivalent to clubpenalty and windowpenalty? (Respecting grid=yes) Huseyin

2 1

Annotation module broken
by Marco Patzer 11 Nov '12

11 Nov '12

Hi Wolfgang, the annotation module broke within the last few betas. \usemodule [annotation] \starttext \startannotation {Foo} Bar \stopannotation \stoptext Marco

2 1

\chapter{} vs \startchapter..\stopchapter
by Bill Meahan 10 Nov '12

10 Nov '12

I note there are two different ways of handling a chapter: The traditional \chapter{mytitle} \startchapter[title=mytitle, ownnumber=N ..] blah \stopchapter Is there any difference or advantage/disadvatage to using one method or the other? Other than the source code, is there anything that lists the keys for \startchapter somewhere? It's not documented in even the most recent command reference. Many thanks! -- Bill Meahan Westland, Michigan USA

6 9

Presets in collectors
by Marco Patzer 10 Nov '12

10 Nov '12

Hi! Is there a reason that presets don't work with collectors? Collectors are based on layers and that's what presets are made for, right? Bug or feature? \definecollector [mycollector] [width=\textwidth] \setcollector [mycollector] {\framed[width=5cm,height=2cm]{Foo}} \setcollector [mycollector] [preset=rightbottom] %% not recognized %% [corner={right, bottom}, %% works %% location={left, top}] {\framed{Bar}} \flushcollector [mycollector] \starttext\null\stoptext Marco

2 2

Preventing page break in register between reference and page number
by "H. Özoguz" 10 Nov '12

10 Nov '12

Hello there, I am relatively new to ConTeXt, now typing a small book in it. I have a problem with the register (index). This is an example: |\definepapersize[MyBook][A6] \setuppapersize[MyBook][A6] % Prints on paper the size of MyBook \starttext \index{A} blub \index{B} blub \index{C} blub \index{D} blub \index{E} blub \index{F} blub \index{G} blub \index{H} blub \index{I} blub \index{J} blub \index{K} blub \index{Long Long Long} blub \index{M} blub \index{N} blub \completeindex \stoptext |The page numer of the reference "Long Long Long" is set to the next page. How to prevent this? Maybe the reference "Long Long Long" could break into two lnes or a rule like that?

4 5

Highlight current chapter in list
by Marco Patzer 09 Nov '12

09 Nov '12

Hi! How do I highlight the current chapter in the table of contents? The TOC is displayed on each page. For illustration I misused the interaction colour, which of course only works for the first page of a chapter. \setupheadertexts [\setups{headlist}] \startsetups [headlist] \framed[align=normal, frame=off] {\placelist [chapter] [alternative=f, criterium=all]} \stopsetups \setupinteraction [state=start, color=lightgray, contrastcolor=darkgreen] \starttext \startchapter [title=alpha] \stopchapter \startchapter [title=beta] \page\input knuth \stopchapter \startchapter [title=gamma] \stopchapter \stoptext Marco

5 15

[***SPAM***] Fonts problems with ConTeXt MKIV (LuaTeX)
by Patrick 09 Nov '12

09 Nov '12

Dear all, I have to use a special font (DIN) for my document. This font have a really limited number of caracters. Previously I was using ConTeXt MKII with no problems. After migrating to ConTeXt MKiV the math formula and list doesn’t work due to the font. It's like the charset used for the formula and the list bullet are not available. I have not this issue with the same font with ConTeXt MKII. The code used to load the font is not the same for the two version. With MKIV I use the simplefonts module, with MKII I use typescript. Both code are available below. Do you have any idea how could I use DIN font with MKIV without breaking math formula ? Thanks in advance for any hint Patrick This is the code I use with MKIV: \usemodule[simplefonts] \definefontfeature[fakeitalic][default][slant=.25] \setsansfont[din] This is the code I use with MKII: % Load the DIN font and set the typescript \loadmapfile [texnansi-s-din.map] \starttypescript [map] [gentium] [ec,texnansi,8r,t5,t2a,t2b,qx] \loadmapfile [\typescriptthree-s-din.map] \stoptypescript \starttypescript [serif] [DIN] [texnansi] \definefontsynonym[DIN-Black][texnansi-DIN-Black0][encoding=texnansi] \definefontsynonym[DIN-Bold][texnansi-DIN-Bold0][encoding=texnansi] \definefontsynonym[DIN-Light][texnansi-DIN-Light0][encoding=texnansi] \definefontsynonym[DIN-Medium][texnansi-DIN-Medium0][encoding=texnansi] \definefontsynonym[DIN-Regular][texnansi-DIN-Regular0][encoding=texnansi] \stoptypescript \starttypescript [serif] [DIN] [name] \usetypescript[serif][fallback] \definefontsynonym [Serif] [DIN-Regular] \definefontsynonym [SerifItalic] [DIN-Light] \definefontsynonym [SerifSlanted] [DIN-Light] \definefontsynonym [SerifBold] [DIN-Bold] \stoptypescript \starttypescript [DIN] \definetypeface [MyDIN] [rm] [serif] [DIN] [default] [encoding=texnansi] \definetypeface [MyDIN] [ss] [sans] [default] [default] [encoding=texnansi] \definetypeface [MyDIN] [tt] [mono] [default] [default] [encoding=texnansi] \definetypeface [MyDIN] [mm] [math] [default] [default] [encoding=texnansi] \stoptypescript \usetypescript[DIN]

3 11

[OT] Spacing research
by Nicola 08 Nov '12

08 Nov '12

Hi, people in this list may be interested in reading this: http://aldusleaf.org/rhea.php Nicola

3 2

RFC: path relative to current file.
by Andre Caldas 08 Nov '12

08 Nov '12

Hello, list! A while ago, I raised a question about how to, in a tex, specify a file with a path relative to the currently being processed file. http://www.ntg.nl/pipermail/ntg-context/2012/069132.html http://www.ntg.nl/pipermail/ntg-context/2012/068902.html Even though the issue did not get much attention, I do believe it is the right thing to do. I wrote a module to implement a macro I called "\pathrelativetome". My code is still a lot ugly. I don't know how to do many things in Lua, LuaTeX and ConTeXt. It can be found here: https://bitbucket.org/andrecaldas/math-video-classes/src/bade74046a6b/lib It would be REALLY NICE if the functionality of "pathrelativetome" was provided by ConTeXt. call it using, for example: context --usemodule=lib/relativetome src/products/assorted.tex Ugly things remaining: 1. pathstack should be initialized with the path of the first tex script. I.e.: src/products/, instead of pathstack[1] = 'src/products' 2. Functions pop and push should be local. (relativetome.lua) 3. Call function "pop" automatically, just like the "push" function is called automatically. 4. Avoid having to define "\xproject", "\xproduct", "\xcomponent" and "\xenvironment". http://www.ntg.nl/pipermail/ntg-context/2012/069305.html Any suggestions/improvements are very welcome! Cheers, André Caldas.

5 18