- ntg-context - Mailing Lists

Occasional words sticking out from flush-right
by James Fisher 03 Mar '10

03 Mar '10

Hi, I'm experiencing an issue where, when the width of a block of text is small, the occasional word sticks out from the otherwise flush right. I've previously seen an example of this in an image on the contextgarden wiki, but now can't find it. To reproduce what I mean, compile this with Mark IV: \mainlanguage[en] \usetypescript[palatino] \setupbodyfont[palatino,11pt] \setuppapersize[A4][A4] \setuphead[title][header=empty] \starttext \title{Personal statement} \startcolumns[n=2] This heavily-hyphenated jauntily-formatted flush-left flush-right justified-text paragraph set in a two-column layout and subtly-quirky-but-never-offensive Palatino shouldn't produce out-of-flush sticking-out-like-a-sore-thumb words from the flush-right. \stopcolumns \stoptext In this example, the string 'sticking-out-like-a-sore-thumb' sticks out to approx 3mm from the right edge of the paper. In this situation, I would much prefer that that string is hyphenated, using one of the hyphens already in the string. Based on one other test (in which my text was far less hyphenated than the above), it seems that the hyphenation algorithm refuses to hyphenate strings of words that are already hyphenated. Is this true? If so, is it deliberate? And how do I turn it off? (And do other people agree with me that it's awfully ugly?) Best James Fisher

3 5

Using XeTeX results in: ! Undefined control sequence. \PDFversion ->1.\the \pdfminorversion
by James Fisher 03 Mar '10

03 Mar '10

Somewhere in my twists and turns to get Mark IV working today, it appears XeTeX has been broken. Running `texexec --xtx' on any ConTeXt file results in: ! Undefined control sequence. \PDFversion ->1.\the \pdfminorversion All I've been able to find out is that these macros are something to do with PDFTeX. I really don't know where to turn now. I'm running: XeTeX 3.1415926-2.2-0.9995.2 (Web2C 7.5.6) TeXExec | version 6.2.1 - 1997-2009 - PRAGMA ADE/POD MTXrun | current version: 2010.03.02 12:34

1 0

no protrusion for hyphen ??
by Steffen Wolfrum 03 Mar '10

03 Mar '10

Hi, I have read there were troubles with |-| in MkIV last year. I found another one: the hyphen set by |-| doesn't get protruded. See example below, please: \startluacode fonts.protrusions.vectors['stpure'] = { [0x002D] = { 0, 0.50 }, -- hyphen } fonts.protrusions.classes['stwpure'] = { vector = 'stpure', factor = 1 } \stopluacode \definefontfeature[default][default] [mode=node,protrusion=stwpure,script=latn]% extend=2,slant=.2, \usetypescript[postscript] \definetypeface[postscript][rm][serif][times][default] \setupbodyfont[postscript,18pt] \setupalign[line,block,hanging] \showframe \starttext \dorecurse{13}{test } test|-|text test \dorecurse{13}{test } test- text test \stoptext Steffen

2 4

doifnumberelse
by Hans van der Meer 03 Mar '10

03 Mar '10

The macro \doifnumberelse is not behaving as I would have expected from the description in Taco Hoekwater's article "Context System Macros: part 1: General macros". There I read: The next macro executesa command depending of the outcome of a test on numerals. \doifnumberelse {string} {then ...} {else ...} This text suggest that the the test is on whether "string" as a whole is a number (taken as having digits 0123456789 only, I presume) of contains nondigits and thus isn't a number. However, it seems the macro tests on the first character only. Below follows a minimal example, the context version is: ConTeXt ver: 2010.02.18 14:48 MKIV fmt: 2010.2.20 int: english/ english % test result of \doifnumberelse \def\test#1{#1 is \doifnumberelse{#1}{a number}{not a number}\crlf} \starttext \test{1} % result: 1 is a number \test{a} % result: a is not a number \test{1a} % result: 1a is a number \test{a1} % result: a1 is not a number \stoptext Hans van der Meer

2 1

Blank page at end of chapter
by Tom 02 Mar '10

02 Mar '10

I can't figure out how to turn off running headers on the blank pages that are inserted into a document to make the first page of the next chapter start on a right page. I'm probably overlooking something. Tom Benjey 717-258-9733 voice 717-243-0074 fax Twitter: @TomBenjey

2 1

METAPOST's superellipse with superness<0.5 does not give a superellipse
by James Fisher 02 Mar '10

02 Mar '10

Hi again, Another METAPOST problem. For the sake of curiosity, I've been looking at and playing with the superellipse() function in plain METAPOST. This is all fine and dandy until I try values of 'superness' less than 0.5, in which case it generates shapes that are seemingly not superellipses. At s=0.5, the function generates a diamond shape -- which, AFAIK, is correct. However, s<0.5, the points of the diamond immediately turn to curves. (My knowledge of superellipses here is just from http://en.wikipedia.org/wiki/Superellipse -- try the image at http://en.wikipedia.org/wiki/File:Lame_anima.gif to see how I expect the shape to change with varying values of superness). Some code follows -- perhaps someone could run it and tell me if, for starters, they get the same as me. (See http://i49.tinypic.com/2ijqatl.jpgfor superellipse() with s=0.3). Best, James % The following is a superellipse function at < http://lists.foundry.supelec.fr/pipermail/metapost-commits/2008-June/000340… >; % I think it's the superellipse function in my copy of METAPOST; it at least has the same behaviour. % It seems to calculate the vertices correctly, but not the way they join (try changing all ... to --). % %def superellipse(expr r,t,l,b,s)= % r ... (s[xpart t,xpart r],s[ypart r,ypart t]){t-r} ... % t ... (s[xpart t,xpart l],s[ypart l,ypart t]){l-t} ... % l ... (s[xpart b,xpart l],s[ypart l,ypart b]){b-l} ... % b ... (s[xpart b,xpart r],s[ypart r,ypart b]){r-b} ... cycle %enddef; def supertest expr s = superellipse( ( 100, 50 ), ( 50, 100 ), ( 0, 50 ), ( 50, 0 ), s ); enddef; % These >0 supernesses are fine, I think ... beginfig(0); draw supertest 2; endfig; beginfig(1); draw supertest 1.01; endfig; % The following, 0.5>=superness<=1, % are from visual reference definitely right beginfig(2); draw supertest 1; endfig; beginfig(3); draw supertest 0.99; endfig; beginfig(4); draw supertest 0.7; endfig; beginfig(5); draw supertest 0.51; endfig; beginfig(6); draw supertest 0.5; endfig; % Now, for <0.5, % things get problematic -- % the points in the shape generated by s=0.5 % should stay 'pointy' beginfig(7); draw supertest 0.49; endfig; beginfig(8); draw supertest 0.3; endfig; beginfig(9); draw supertest 0.01; endfig; beginfig(10); draw supertest 0; endfig; end;

2 5

Math integral symbols (cambria) , MK-IV
by gummybears 02 Mar '10

02 Mar '10

Hi, When using font Cambria, the integral symbols \iint and \iiint look funny compared to \int. The contour, surface and volume integrals look fine. Version ConText version 2010.02.25 19:46. LuaTeX version 50,0 Test file \usetypescript[cambria] \setupbodyfont[cambria] \starttext \startformula \startalign[n=2] \NC \text{integral} \NC \int_{a}^{b} \NR \NC \text{double integral} \NC \iint_{a}^{b} \NR \NC \text{triple integral} \NC \iiint_{a}^{b} \NR \NC \text{contour integral} \NC \oint_{a}^{b} \NR \NC \text{surface integral} \NC \oiint_{a}^{b} \NR \NC \text{volume integral} \NC \oiiint_{a}^{b} \NR \stopalign \stopformula \stoptext

2 1

Re: [NTG-context] Math in MKIV - HOWTO
by Zhichu Chen 02 Mar '10

02 Mar '10

Hi, I got some time today and checked some symbols of hlcra.tfm (LucidaNewMath-Arrows), and got this table: ==================================================== fonts.enc.math["lucida-ma"] = { [0x025CB] = 0x00, -- circle [0x025CF] = 0x01, -- blackcircle [0x025A1] = 0x02, -- square [0x025A0] = 0x03, -- blacksquare [0x025B3] = 0x04, -- triangleup [0x025B2] = 0x05, -- blacktriangleup [0x025BD] = 0x06, -- triangledown [0x025BC] = 0x07, -- blacktriangledown [0x02B28] = 0x08, -- lozenge [0x02B27] = 0x09, -- blacklozenge [0x02B29] = 0x0A, -- blackdiamond [0x02571] = 0x0B, -- upright [0x02572] = 0x0C, -- downright [0x022E4] = 0x0D, -- squareimageofnoteq [0x022E5] = 0x0E, -- squareoriginalofnoteq [0x02A4F] = 0x0F, -- dblsquareunion [0x02A4E] = 0x10, -- dblsquareintersection [0x02A64] = 0x11, -- zdomainantirestriction [0x02A65] = 0x12, -- zrangeantirestriction [0x022EE] = 0x13, -- verticalellipsis [0x022EF] = 0x14, -- ellipsis [0x022F0] = 0x15, -- uprightellipsis [0x022F1] = 0x16, -- downrightellipsis [0x022D5] = 0x17, -- equalparallel [0x0225B] = 0x1A, -- stareq [0x00127] = 0x1B, -- hbar [0x022F6] = 0x1C, -- barelementof [0x02209] = 0x1D, -- notelementof [0x022FD] = 0x1E, -- barcontains [0x0220C] = 0x1F, -- notcontain [0x02204] = 0x20, -- nexists [0x02194] = 0x21, -- leftrightarrow [0x02195] = 0x22, -- updownarrow [0x0219E] = 0x23, -- leftleftarrow [0x0219F] = 0x24, -- upuparrow [0x021A0] = 0x25, -- rightrightarrow --~ [0x00026] = 0x26, -- amperand [0x021A1] = 0x27, -- downdownarrow [0x021A2] = 0x28, -- leftarrowtail [0x021A3] = 0x29, -- rightarrowtail [0x021A4] = 0x2A, -- leftarrowbar [0x021A6] = 0x2B, -- rightarrowbar [0x021A5] = 0x2C, -- uparrowbar --~ [0x02212] = 0x2D, -- minus --~ [0x0002D] = 0x2D, -- minus [0x021A7] = 0x2E, -- downarrowbar [0x021E4] = 0x2F, -- barleftarrow [0x021E5] = 0x30, -- barrightarrow [0x021E0] = 0x38, -- dashleftarrow [0x021E1] = 0x39, -- dashuparrow [0x021E2] = 0x3A, -- dashrightarrow [0x021E3] = 0x3B, -- dashdownarrow [0x021A9] = 0x3C, -- hookleftarrow --~ [0x0003D] = 0x3D, -- equalto [0x021AA] = 0x3E, -- hookrightarrow [0x021AB] = 0x3F, -- looparrowleft [0x021AC] = 0x40, -- looparrowright [0x1D538] = 0x41, -- A (blackboard A) [0x1D539] = 0x42, -- B [0x02102] = 0x43, -- C [0x1D53B] = 0x44, -- D [0x1D53C] = 0x45, -- E [0x1D53D] = 0x46, -- F [0x1D53E] = 0x47, -- G [0x0210D] = 0x48, -- H [0x1D540] = 0x49, -- I [0x1D541] = 0x4A, -- J [0x1D542] = 0x4B, -- K [0x1D543] = 0x4C, -- L [0x1D544] = 0x4D, -- M [0x02115] = 0x4E, -- N [0x1D546] = 0x4F, -- O [0x02119] = 0x50, -- P [0x0211A] = 0x51, -- Q [0x0211D] = 0x52, -- R [0x1D54A] = 0x53, -- S [0x1D54B] = 0x54, -- T [0x1D54C] = 0x55, -- U [0x1D54D] = 0x56, -- V [0x1D54E] = 0x57, -- W [0x1D54F] = 0x58, -- X [0x1D550] = 0x59, -- Y [0x02124] = 0x5A, -- Z (blackboard Z) [0x0231C] = 0x5B, -- ulcorner [0x0231D] = 0x5C, -- urcorner [0x0231E] = 0x5D, -- llcorner [0x0231F] = 0x5E, -- lrcorner [0x02225] = 0x5F, -- parallel, Vert, lVert, rVert, arrowvert [0x021D5] = 0x60, -- Updownarrow [0x021D4] = 0x61, -- Leftrightarrow [0x021D6] = 0x62, -- Upleftarrow [0x021D7] = 0x63, -- Uprightarrow [0x021D9] = 0x64, -- Downleftarrow [0x021D5] = 0x65, -- Downrightarrow [0x021CD] = 0x66, -- nLeftarrow [0x021CE] = 0x67, -- nLeftrightarrow [0x021CF] = 0x68, -- nRightarrow --~ [0x021CE] = 0x69, -- nLeftrightarrow -- what's the difference between this and 0x0067[0x021CE] [0x021DA] = 0x6A, -- Lleftarrow [0x1D55C] = 0x6B, -- k \Bbbk (blackboard k) [0x021DB] = 0x6C, -- Rrightarrow [0x021C4] = 0x6D, -- rlarrow [0x021C6] = 0x6E, -- lrarrow [0x021C5] = 0x6F, -- udarrow --~ [0x021C5] = 0x70, -- duarrow [0x021C7] = 0x71, -- llarrow [0x021C8] = 0x72, -- uuarrow [0x021C9] = 0x73, -- rrarrow [0x021CA] = 0x74, -- ddarrow [0x021BE] = 0x75, -- rupharpoon [0x021BF] = 0x76, -- lupharpoon [0x021C2] = 0x77, -- rdownharpoon [0x021C3] = 0x78, -- ldownharpoon [0x021CB] = 0x79, -- lrharpoon [0x021CC] = 0x7A, -- rlharpoon [0x021B0] = 0x7B, -- upthenleftarrow --~ [0x0] = 0x7C, -- part [0x021B1] = 0x7D, -- upthenrightarrow --~ [0x0] = 0x7E, -- part [0x02276] = 0x7F, -- ltgt [0x021B2] = 0x81, -- downthenleftarrow [0x021B3] = 0x82, -- downthenrightarrow [0x02B0E] = 0x83, -- rightthendownarrow [0x02B10] = 0x84, -- leftthendownarrow [0x02B0F] = 0x85, -- rightthenuparrow [0x02B11] = 0x86, -- leftthenuparrow [0x021B6] = 0x87, -- leftarcarrow [0x021B7] = 0x88, -- rightarcarrow [0x0293D] = 0x89, -- leftarcarrowplus [0x0293C] = 0x8A, -- rightarcarrowminus [0x021BA] = 0x8B, -- anticlockwise [0x021BB] = 0x8C, -- clockwise [0x02260] = 0x94, -- noteq [0x02262] = 0x95, -- notidentical [0x02241] = 0x96, -- nottilde [0x02244] = 0x97, -- notasymptoticallyequal [0x02249] = 0x98, -- notalmostequal [0x02247] = 0x99, -- notapproximatelyeq [0x0226E] = 0x9A, -- nless [0x0226F] = 0x9B, -- ngtr [0x02270] = 0x9C, -- nleq [0x02271] = 0x9D, -- ngeq [0x022E6] = 0x9E, -- lnsim [0x022E7] = 0x9F, -- gnsim [0x02605] = 0xAB, -- black star [0x02713] = 0xAC, -- check [0x02277] = 0xC5, -- gtlt [0x02284] = 0xC6, -- nsubsetof [0x02285] = 0xC7, -- nsupsetof [0x02288] = 0xC8, -- nsubseteq [0x02289] = 0xC9, -- nsupseteq [0x0228A] = 0xCC, -- subsetneq [0x0228B] = 0xCD, -- supsetneq --~ [0x0228A] = 0xD0, -- subsetneq --~ [0x0228B] = 0xD1, -- supsetneq [0x02270] = 0xD6, -- nleq [0x02271] = 0xD7, -- ngeq [0x02268] = 0xDC, -- lneqq [0x02269] = 0xDD, -- gneqq [0x022E6] = 0xE0, -- lnsim [0x02219] = 0xE1, -- bullet [0x022E7] = 0xE2, -- gnsim [0x02280] = 0xE5, -- nprec [0x02281] = 0xE6, -- nsucc [0x022E8] = 0xEB, -- precnsim [0x022E9] = 0xEC, -- succnsim [0x022EA] = 0xEF, -- nnormalsub [0x022EB] = 0xF0, -- ncontainnormalsub [0x022EC] = 0xF1, -- nnormalsubeq [0x022ED] = 0xF2, -- ncontainnormalsubeq [0x02226] = 0xF7, -- nparallel [0x022AC] = 0xF8, -- nvdash [0x022AE] = 0xF9, -- nVdash [0x022AD] = 0xFA, -- nvDash [0x022AF] = 0xFB, -- nVDash } ==================================================== The empty lines indicate that there're some symbols I can't find in the unicode chart, the commented lines indicate that I'm not sure about that. I don't know if you were working on that. I almost went blind after this and I hope you won't go through the same work. On Wed, Feb 24, 2010 at 8:27 PM, Mojca Miklavec <mojca.miklavec.lists(a)gmail.com> wrote: >>> The double stroke A--Z from U+1D538 -- U+02124 in hlcra.tfm(lbma.pfb) >>> from 0x41--0x5a are missing, even though I added to the lbr-ma vector >>> :( >> >> you should coordinate this with mojca > > Just go on ... I'll check once I finish a few important task (and that > most probably won't be today), but I promise to do a precise check > (whether or not the vector will be complete by then - of course it > will be much easier if Zhichu does the work :). > > Mojca > -- Best Regards Chen ---------------------------------------------------------------- Zhi-chu Chen | Shanghai Synchrotron Radiation Facility No. 2019 | Jialuo Rd. | Jiading | Shanghai | P.R. China tel: 086 21 5955 3405 | zhichu.chen.googlepages.com | www.sinap.ac.cn ----------------------------------------------------------------

3 9

Suggestions on fonts and foundries
by Tom 02 Mar '10

02 Mar '10

Some time back I recall seeing a message in which someone discussed using fonts available from foundries and recommended certain ones. Unfortunately, I can't seem to find that message. I will probably need one serif font for the text of the book, a plain sans serif font to use for entries in a table, a fancier sans serif font for chapter titles and, possibly a different not-too-plain sans serif font for page headers. Also, I can't figure out how to tell ConTeXt which font to use for page headers. Tom Benjey 717-258-9733 voice 717-243-0074 fax Twitter: @TomBenjey

3 2

[ntg-context] ppchtex questions and maybe buglets
by Bernhard Rosensteiner 02 Mar '10

02 Mar '10

Hi all, ppchtex is really nice. after experimenting with it i found some buglets: \starttext \setupchemical[axis=off,frame=on, option=test, size=medium, scale=medium, right=2000, left=3000, height=6000,textsize=medium]%textsize and option=test has no effect - why? \startchemical \chemical[SIX,SB135,DB246,SR6,Z,CRZ6][N,C,N,C,C,C,{\LC{\color[green]{NH}}}]%here color works \color[green]{\chemical[ADJ3,Five,SB235,DB4,Z345,SR3,CRZ3][N,C,H,H]}%color does not work here, manual says it should -why? \bottext{\offset[y=-\baselineskip]{Adenin}} \stopchemical \stoptext maybe someone can also explain how the OFF key works. the behaviour is strange in my opinion. i found nothing precise in the manual. onhttp://chneukirchen.org/blog/archive/2004/05/ppchtex.html i found following explanation: 18OFF1: do 18 small steps in direction 1 (right) but this don´t work - even with the example on the homepage. best regards Bernhard

2 1