November 2011 - ntg-context - NTG Mailing Lists

Re: [NTG-context] Problems with linespacing
by Jan Heinen 04 Nov '11

04 Nov '11

Wolfgang, thanx for your fast response. The typescript does not find my allerlight. I have tried "name:allerlight" ... without success. But I am happy with \definefont[name:.......] and \setupinterlinespace Now I still need a possibility to have a bigger linespacing after a paragraph and why does (3) runs to the right end of the page? > http://www.imagebanana.com/view/bipcpje7/Linespacing.png Regards Jannis

2 1

Problems with linespacing
by Jan Heinen 04 Nov '11

04 Nov '11

I can't find what I am doing wrong in my tex-file. 1. I have little problems with the linespacing when I use big fontsizes. The text looks uneasy. Here you can see the problem ... (1) and (2) on the image http://www.imagebanana.com/view/bipcpje7/Linespacing.png And why does (3) runs to the right end of the page? ... and here my tex-file: \definefont[Gross] [name:allerlight at 36pt] \starttext \Gross Ich bin Blindtext. Von Geburt an. Es hat lange gedauert, bis ich begriffen habe, was es bedeutet, ein blinder Text zu wer wer wer wer wer wer wer wer wer wer wer keinen Sinn. Man wirkt hier und da aus dem Zusammenhang gerissen. Oft wird man gar nicht erst gelesen. Aber bin ich deshalb ein schlechter Text? Ich weiss, dass ich nie die Chance haben werde, im Stern zu erscheinen. \stoptext 2. And using a very small fontsize, eg. 8pt the linespacing looks to be the same in every line but it is to big. 3. What is to do to have only a small linespacing in a paragraph and a bigger linespacing after a break and then again a small linespacing in the next paragraph, and so on. And I don't want to put \blank after a paragraph. --------- ------- --------- -- -------- --------- ---------- --------- ------- ----- ------- -- Regards Jannis

2 1

Odd column break - how to avoid?
by Alasdair McAndrew 03 Nov '11

03 Nov '11

Hello, In a two column document I'm preparing, I have a column break in a very odd place. The column just stops, and the document material just begins in the next column, leaving a lot of white space. I've no idea what's causing this, and I've tried to avoid it, but nothing I do seems to work. Is there any way of forcing a column not to break? Thanks, Alasdair

1 0

Re: [NTG-context] Hello world title not flush left - beginner question?
by Wolfgang Schuster 03 Nov '11

03 Nov '11

Am 03.11.2011 um 15:15 schrieb Alan Braslau: > On Thu, Nov 03, 2011 at 02:36:06PM +0100, Wolfgang Schuster wrote: >> >> \def\startdictum >> {\dostartbuffer[dictum][startdictum][stopdictum]} >> >> \setuphead >> [title] >> [insidesection=\texsetup{dictum}] >> >> \startsetups dictum >> >> \doifelsebuffer{dictum} >> {\startframedtext[right][frame=off,offset=none,width=.5\ >> textwidth,foregroundstyle=\itx] >> \getbuffer [dictum] >> \resetbuffer[dictum] >> \stopframedtext} >> {\donothing} >> >> \stopsetups >> >> \starttext >> >> \startdictum >> \input ward >> \stopdictum >> >> \starttitle[title=This is a heading with a epgigraph below] >> >> \input knuth >> >> \stoptitle >> >> \stoptext > > Wolfgang, > > Looking at your message above, > I do not really understand why it is best to set a buffer > for a one-time use: to be typeset after the title and then reset. This was just a example to demonstrate the “insidesection” key to add something after the heading. When you want to use it only one time the above is overkill but it’s useful when you want a epigraph for each chapter. With \doifelsebuffer I can check if there the user set a epigraph and only when there is one i want the framedtext but I have to reset the buffer for the next chapter. > Would it not be better (or more logical, in fact) to simply use: > > \setupframedtext [frame=off,offset=none,width=.5\textwidth, > foregroundstyle=\itx] > % I did not check, but I imagine that this works... > > \starttitle [title=This is a heading with an epigraph below] > > \startframedtext [right] > \input ward > \stopframedtext > > > Of course, one could (and probably should) define a special sort > of framed text? > I don't remember the proper syntax for this, though. How is a framedtext more logical than a dictum or epigraph environment, with my solution you can also change the definition of the code to place the epigraph format without any change in the text while your framed text is always a framedtext (I know you can avoid this with a named framedtext) and changes to the layout require more work. > I am interested, as in one of my documents, I do something like this > (without any special typesetting, for the moment) stupidly as: > > \def\sectionbis#1{{\it #1}\blank} > > \startsection [title=Section title] > > \sectionbis{\input ward} > > \input tufte \definestartstop[sectionbis][style=italic,inbetween=\blank] Wolfgang

2 2

wiki.contexgarden.net/Main_Page
by Alan Braslau 03 Nov '11

03 Nov '11

Dear context garden administrators (and users): It would be a good idea to have a wiki.contextgarden.net/News page containing an archive of past and present news. Clicking on the "News" label on the Main_Page could go there. Examples of items to include could be: July 2011: TeX Live 2011 released, including current ConTeXt September 2011: First general assembly of the ConTeXt user's group (in Bassenge, Belgium during the 5th International ConTeXt User Meeting) November 2011: Deadline for contributions to the proceedings of the 5th International ConTeXt User Meeting, to appear in the first issue of the ConTeXt User Journal. November 2011: Migration of contextgarden.net to new servers. etc. Should this new page be generally editable, or should it be administered? Alan

2 2

lua and brackets
by Martin Fechner 03 Nov '11

03 Nov '11

Hi all, I try to call a lua-function, but it seems that it doesn't work if the parameter contains squared brackets. Here is a short example: \starttext sometext \reference[myref]{} is \ctxlua{tex.print(\atpage[myref])} \stoptext Is there a way to mask the brackets? Best regards, Martin

2 4

Hello world title not flush left - beginner question?
by Grant William (ST-CO/ENG3.11) 03 Nov '11

03 Nov '11

Hi all, I am a novice user of latex and have always wanted to have more control over how things look and are set up. Context is perfect! But now I am stuck on a frustrating bug I can't seem to figure out. Maybe this is not a bug at all... Nontheless, in the Hello World http://wiki.contextgarden.net/Hello_world example page, upon building my own version and looking closely, the title text is not lined up to the left edge of the text area, whereas the following line for the A. U. Thor is flushed over correctly. The example pdf on the page is like this as well, but when I turn on \showframe and look at in on my computer, the offset is just screaming at me! I can't seem to figure out what portion of the \setuphead[title] code is causing this. Is this a bug or what is going on here? Thanks. William Grant

2 1

\unit problem
by Romain Diss 03 Nov '11

03 Nov '11

Hello all, It seems that some unit combinations don't work very well with the \unit macro. I have some problems with the m- (milli-) prefix but some tests reveal other strange errors. Here is a not so minimal example. The first 33 entries come from "phys- dim.mkiv" and work well. In the entries 100 to 115 which I added, the 102, 107, 108, 109, 110, 111, 112 and 115 cause problem : \starttext \startbuffer 01: $10\unit{km/h}$ 02: $\unit{10 km/h}$ 03: \unit{km/h} 04: \unit{10 km/h} 05: \unit{10 km/h} 06: \unit{~1 km/h} 07: 10\unit{km/h} 08: 10 \unit{km/h} 09: $10 \unit{km/h}$ 10: 10 \unit{KiloMeter/Hour} 11: 10 \unit{kilometer/hour} 12: 10 \unit{km/h} 13: 10 \unit{kilometer per hour} 14: 10 \unit{km / h} 15: 10 \unit{ km / h } 16: 10 \unit{km/ms2} 17: 10 \unit{meter per second} 18: 10 \unit{cubic meter} 19: 10 \unit{cubic meter per second} 21: 10 \unit{cubic meter / second} 22: $10 \unit{cubic meter / second}$ 23: 30 \unit{kilo pascal } 24: 30 \unit{kilo pascal square meter / second} 25: 30 \unit{kilo pascal square meter / kelvin second} 26: \unit{30 kilo pascal square meter / kelvin second} 27: $30 \unit{kilo pascal square meter / kelvin second }$ 28: 30 \unit{crap} 29: 30 \unit{AC} 30: $\frac{10 \unit{m/s}}{20 \unit{m/s}} $ 31: {\ss 30 \unit{kilo pascal square meter / second kelvin}} 32: \unit{123.22^-3 km/s} 33: \unit{123.22e-3 km/s} 100: \unit{10 mm} 101: \unit{10 km} 102: \unit{10,2 mA} 103: \unit{123 kA} 104: \unit{0,001 MA} 105: \unit{1 dal} 106: \unit{2.21 GW} 107: \unit{345 mW} 108: \unit{152.20 mHz} 109: \unit{55.5 mmol} 110: \unit{6.7 mol/l} 111: \unit{125 g/l} 112: \unit{125 g / l} 113: \unit{125 km/s} 114: \unit{125 m/s} 115: \unit{125 mA/s} \stopbuffer \typebuffer Result: \startlines \getbuffer \stoplines \stoptext Thank you for your help. -- Romain Diss <romain.diss(a)yahoo.fr>

1 0

beta
by Hans Hagen 03 Nov '11

03 Nov '11

Hi, I uploaded a new beta. The biggest new thing is that there is yet another table mechanism: extreme tables. There is a manual too: http://www.pragma-ade.com/general/manuals/xtables-mkiv.pdf It says in the introduction: >> This is a short introduction to yet another table mechanism built in \CONTEXT. It is a variant of the so called natural tables but it has a different configuration. Also, the implementation is completely different. The reason for writing it is that in one of our projects we had to write styles for documents that had tables spanning 30 or more pages and apart from memory constraints this is quite a challenge for the other mechanisms, if only because splitting them into successive floats is not possible due to limitations of \TEX. The extreme table mechanism can handle pretty large tables and split them too. As each cell is basically a \type {\framed} and as we need to do two passes over the table, this mechanism is not the fastest but it is some two times faster than the natural tables mechanism, and in most cases can be used instead. << There will probably a few additions but it's already pretty complete. Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------

5 5

OT LCD 498 pixels-per-inch
by luigi scarso 03 Nov '11

03 Nov '11

http://www.tmdisplay.com/english/news/2011/2011_1020.htm -- luigi

2 2