May 2010 - ntg-context - NTG Mailing Lists

unicode no-break spaces
by Peter Münster 05 Jul '10

05 Jul '10

Hello, This used to work with MKIV, but with today's version, it does not: \starttext X X THIN SPACE (U+2009)\blank X X NARROW NO-BREAK SPACE (U+202F)\blank X X NO-BREAK SPACE (U+00A0)\blank \stoptext Should this work, or should we rather use "~" and "\," as in the past? Cheers, Peter -- Contact information: http://pmrb.free.fr/contact/

5 10

Re: [NTG-context] minimal example of some problems
by Michael Saunders 04 Jul '10

04 Jul '10

>>>> 1. Leftward protrusion doesn't work. >>>> 2. I don't think hz is working in footnotes. >>> >>>> The font I'm using is Adobe Garamond Premiere Pro. If you think there >>>> might be a problem with the typescript, I can show you that too. >>> >>> These two are related to font. Either show that something is wrong with >>> default typescripts (lmodern, times, palatino, etc) else it means that >>> tosmething is wrong with your typescript. But first you have to narrow >>> down the problem >> >> I take your word for it that it works for the default typescripts; >> therefore, the problem must be somewhere in my typescript, but I have >> no idea where. It is as follows: > >I don't have the font, so I cannot test it. I should not have been so fast to take your word for it. If I use the default LM fonts, I get the same problems---no leftward protrusion and no hz in the footnotes. >You can prevent notes from splitting across pages by > >\setupenumerations[footnote] > [before=\vbox\bgroup, after=\egroup] > >The footnote may still appear on a different page. If you want to prevent >that add > >\setupfootnotes[split=verystrict] This doesn't work. I'm still getting footnotes appearing on the wrong page. >>> 4. Notice the overprinting near the top of p.2 c.1. That is a >>> marginal note that should go into the right margin. >> >> \starttext >> \startcolumns >> >> \input knuth >> \input tufte >> \column >> \input tufte >> \inmargin{This is in wrong margin} >> \input knuth >> \stopcolumns >> \stoptext >> >> The marin note in 2nd column is displayed in the 1st column. This is >> artifact of the way in which TeX constructs columns: first creating a >> long and narrow page and then splitting it into two. I don't know at >> what stage of the OTR are margin notes inserted, and if there is a >> workaround. Maybe others can help. > >this is the first time someone needs it so indeed there is no mechamism > >it's not that complex to deal with it (but i'd only do it in mkiv) gien >time and motivation ... you can put a feature request in the tracker so >that i can look at it when i'm reworking marging notes the mkiv way >(first come floats) Where is the tracker I should put this in? I have found another problem which is probably related. In the same sort of arrangement, two columns with margins on either side, I would like to place floats like this: 1. If they appear on the left side, they should end at the right edge of the left column. 2. If they appear on the right side, they should begin at the left edge of the right column. Using \placetable[inmargin] (my best guess), this works fine for case (2), but case (1) begins at the left edge of the left column and can overprint the right column.

7 18

PDF Meta Tags
by Bart C. Wise 28 Jun '10

28 Jun '10

I received the following message from a publisher: [The PDF generator] you used flattens the file such that is has no meta tags whatsoever. We need the tags that give page separations, page count, header info, etc. How do I get those meta tags enabled? Would setting \interaction[state=start] do what's needed? Running minimals-beta. Thanks, Bart

6 17

Page numbering in Adobe Reader
by Zhichu Chen 28 Jun '10

28 Jun '10

Hi Hans and Taco, Some guy think it's cool to use romannumeral numbers in the preface and so is in the Adobe Reader. I searched the source but apparently it is not provided. I made a very dirty test file so could you make a switch in the \setupinteraction officially? My test file is like: ============================================== \pdfcompresslevel 0 \setupinteraction [state=start, focus=width, page=yes, openaction=firstpage, click＝no, title=TEST, author=Neals, subtitle=Test, keyword={test}] \setupcolors [state=start] \newcount\FrontPageNumbers \setupsubpagenumber[way=bytext,state=start] \setuppagenumbering[location=] \startsectionblockenvironment[frontpart] \setupfootertexts[pagenumber] \setuppagenumbering[conversion=romannumerals] \stopsectionblockenvironment \startsectionblockenvironment[bodypart] \global\FrontPageNumbers=\pagenumber \global\advance\FrontPageNumbers\minusone \setuppagenumber[number=1] \resetsubpagenumber % \setupfootertexts[\the\FrontPageNumbers] \setupfootertexts[pagenumber] \stopsectionblockenvironment \startsectionblockenvironment[backpart] \resetsubpagenumber \stopsectionblockenvironment \def\PageLabels{\pdfcatalog{/PageLabels << /Nums [ 0 << /S /r >> \the\FrontPageNumbers << /S /D >> ] >> >>}} \prependtoks \PageLabels \to \everystoptext \starttext \startfrontmatter % \chapter{Table of Contents} \completecontent[interaction=all] \chapter{Preface} \dorecurse{10}{\input zapf\par} % \chapter{Preface} % \dorecurse{10}{\input zapf\par} % \chapter{Preface} % \dorecurse{10}{\input zapf\par} \stopfrontmatter \startbodymatter \chapter{Test} \dorecurse{15}{\input tufte\par} \chapter{TestAgain} \dorecurse{15}{\input ward\par} \stopbodymatter \startbackmatter Index maybe. \stopbackmatter \stoptext ============================================== A lot of the code to setup the main layout is stolen from Wolfgang :) -- 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 4

referenceformat MkIV
by Yury G. Kudryashov 07 Jun '10

07 Jun '10

Hi! I try the following: \definereferenceformat[ineq][left=(,right=),text=Equation] \starttext \placeformula[first] \startformula 2=2 \stopformula In \in[first] ineq \ineq[first] in \in[first]. \stoptext The result is: 2 = 2 (1) In 1 ineq (1) in (1). It seems that \ineq doesn't clear some variables, and the next \in uses the previous format.

2 4

Re: [NTG-context] Multiple pleas for help (long)
by Scott Steele 02 Jun '10

02 Jun '10

If anyone has any insight on how to keep the footnotes from having their numbers in the margin and from having line-breaks after each one, that is the only issue from the original email that is still unsolved, I think. ——— In Latex, \fancybreak was part of a package called, I believe, fancyheader or fancypage. It produced a break frequently seen in published prose (I'm currently reading {\em Bluebeard} where Kurt Vonnegut uses it liberally) with significant vertical space between two paragraphs and, centered both in that vertical space as well as horizontally, a number of well-spaced marks. There are usually 3 marks, and they are frequently asterisks or traditional dingbats/fleurons. This sort of break is generally used when the author wishes to indicate a break more significant than a change in paragraph but short of an outright new chapter. \def\FancyBreak{\par\blank\hfill* * *\hfill\hfill\par\blank} \starttext \input tufte \FancyBreak \input tufte \stoptext I don't understand why I need the two consecutive \hfill's at the end for the marks to be centered, but the definition works well for me. ——— Thanks, Wolfgang, for your help with the emoticons—they work now. \useexternalfigure[frowny][Frowny][factor=8,type=pdf] \def\Frowny{\dontleavehmode\smash[h]{\externalfigure[frowny]}} Also, thanks for the \simplealignedbox, which works very well in my table of contents (although I have to put a \par at the end of it or it stays on one line and goes off the page). I don't understand why, but Tex didn't like having a \par inside the type of definition you used, but it allowed the following: \def\SectionListEntry#1#2#3% { \noindent \simplealignedbox{left}{2cm}{#2}% \simplealignedbox{middle}{5mm}{·}% \simplealignedbox{right}{3cm}{#3}% \par } (I have a few issues with my table of contents, but these are now less specific to \placelist, so I'm including them in a different posting.) Thanks again for all the help, Scott ----- This is a work of ﬁction. Names, characters, places, and incidents either are the product of the writer's imagination or are used ﬁctitiously, and any resemblance to actual persons, living or dead, businesses, companies, events, or locales is entirely coïncidental.

2 2

Strange expansion behavior in XML/luatex
by Martin Kolařík 01 Jun '10

01 Jun '10

Hello, I had a problem with some my documents; I extracted it to as small code as possible. What is happening -- if any of xml flushing function (I tried xmlflush, xmlfilter and xmlall) is expanded to a macro (so the content of xml becomes a text of the macro), and the xml contains other hooked xml tags, the \edef (and its counterparts \xdef or \expandedaction) inside the inner tag is "skipped" by the log. Then macros relying on the expansion fail (I detected it in \doif and \processaction). Macros are normally expanded, only \edef fails (maybe some other TeX commands fail too, but I did not test it). In my example below, content of "il" is flushed to a macro, "inline" is the inner tag and "\processaction" is the example of macro using "\edef". Do not look for sense, it is an example. XML: <?xml version="1.0" encoding="utf-8"?> <il> Text <inline what="something" /> text. </il> TeX: \startxmlsetups doc:inline \processaction [\xmlatt{#1}{what}] [something=>A thing, nothing=>Hic sunt leones] \stopxmlsetups \startxmlsetups doc:il \edef\content{\xmlflush{#1}}% \stopxmlsetups \xmlregistersetup{xml:doc} \startxmlsetups xml:doc \xmlsetsetup{\xmldocument}{inline|il}{doc:*} \stopxmlsetups I do not know, if it is a bug or a feature :-); but notwithstanding the fact, similar code I used in MkII worked very well. Thanks for hints, Martin -- Martin Kolařík martin.kolarik(a)email.cz martin.kolarik(a)jabber.cz +420603535593

2 5

Title page layout
by Scott Steele 01 Jun '10

01 Jun '10

I'm trying to anchor a table or box containing my title and subtitle to the bottom right corner of the textblock (on a title page). The following comes very close to doing what I want, but there is still some vertical space between the bottom of the text of the subtitle and the last major horizontal gridline. How can I have the subtitle text be (above and) flush with the last major horizontal gridline in the same way that it is flush with the rightmost vertical gridline? NOTE: Small adjustments to the example I provide might not be helpful for me since, in actuality, I'm using Adobe Jenson, which makes both the metrics and the expression of the problem slightly different. Also, are there max/min functions for dealing with dimexpr's? %\definetypeface[jenson][rm][Xserif][Adobe Jenson Pro] %\setupbodyfont[jenson, 11pt] \definepapersize[pocket][width=4.25in, height=6.875in] \setuppapersize[pocket][pocket] \setuplayout[location=middle, width=0.815\paperwidth, rightmargindistance=0in, leftmargindistance=0in, height=middle, margin=0.08\paperwidth, backspace=0.115\paperwidth, marking=off, grid=yes, topspace=0.018889\paperheight, header=0.044444\paperheight, footer=0.044444\paperheight, bottomspace=0.038889\paperheight] \setuppagenumbering[alternative=doublesided, location={footer,marginedge}] \def\givewidthof#1\to#2% { \bgroup \setbox\scratchbox\hbox{#1}% \expanded{\egroup\def\noexpand#2{\the\wd\scratchbox}} } % From a response by Hans to a mailing list question. It was originally \setwidthof#1\to#2, which—in English at least—sounds somewhat ambiguous with regard to which variable is providing a width. \def\TitlePage#1#2% { \givewidthof{\scc #2}\to\SubtitleWidth \newdimen\TitlePageVar \TitlePageVar=\dimexpr(\textwidth-\SubtitleWidth) \dontleavehmode\vfill \starttable[s(0pt)|lw(\TitlePageVar)|cw(\SubtitleWidth)|] \NC\NC{\scd #1}\AR \NC\NC{\scc #2} \stoptable \page } \showgrid \startfrontmatter \TitlePage{Title}{Longer Subtitle} \stopfrontmatter Thanks, Scott ----- This is a work of ﬁction. Names, characters, places, and incidents either are the product of the writer's imagination or are used ﬁctitiously, and any resemblance to actual persons, living or dead, businesses, companies, events, or locales is entirely coïncidental.

2 1

Frontmatter page numbers and using ifodd / pageno
by Scott Steele 31 May '10

31 May '10

With the page layout setups I'm using, the first table of contents entry on each page (except for the first page) is formatted as if it were on the preceding page. I assume that the page number is not advancing until some number of objects are placed on the page. When I compiled the example included below, it was the first three entries on each page (after the first page) that were formatted as if they were on the previous page. Related to this, I need "invisible" page numbers on the table of contents pages to enable different formatting by odd/even page number (which I accomplish now by using \phantom as a style command for page numbering), but I'd like for the page numbering of the body matter to start at 1. Also, how can I number the front matter backward? Like: xi, x, ix, viii, vii, vi, v, iv, iii, ii, i. \def\SectionListEntry#1#2#3% { \noindent \noexpand{\ifodd\pageno \simplealignedbox{left}{.63667\textwidth}{#2} \simplealignedbox{middle}{.06\textwidth}{·} \simplealignedbox{right}{.30333\textwidth}{#3} \else \simplealignedbox{left}{.30333\textwidth}{#3} \simplealignedbox{middle}{.06\textwidth}{·} \simplealignedbox{right}{.63667\textwidth}{#2} \fi} \par\blank } \setuplist[section] [alternative=command, command=\SectionListEntry] \def\TableOfContents% { \page[empty] \page[odd] \setuppagenumbering[style=command, command=\phantom] \setuppagenumber[state=start] \placelist[section] \setuppagenumber[state=stop] \page[empty] \page[odd] } \startfrontmatter \TableOfContents \stopfrontmatter \startbodymatter \setuppagenumber[state=start] \dorecurse{45}{\section{Section title}\input tufte} \stopbodymatter Thanks, Scott ----- This is a work of ﬁction. Names, characters, places, and incidents either are the product of the writer's imagination or are used ﬁctitiously, and any resemblance to actual persons, living or dead, businesses, companies, events, or locales is entirely coïncidental.

1 0

Difference in whitespace around section head from mkII to mkIV
by Adam Fuller 31 May '10

31 May '10

hi all, i'm experiencing some unwanted whitespace related to a section head. the whitespace is present when using lua (texexec --lua funk.tex) and absent when using mkII (texexec funk.tex). i've confirmed the correct mkII behaviour on the garden's live tool, and my own minimals installation: This is LuaTeX, Version beta-0.60.1-2010050621 (rev 3678) \write18 enabled. (funk.tex ConTeXt ver: 2010.05.13 12:15 MKIV fmt: 2010.5.21 int: english/english if you run the document below on mkII, you'll see that the first text on each slide is right up against the top of the text area. this is good. if you use my version of luatex, a line is skipped. why the difference? i'm not actually using anything lua (i've just started using Context in the past weeks, and i've got a conference presentation due in 3 days, so i've got weird habits. i'm just now getting my head around the copious amounts of documentation for the system, and all the differences between context, luatex, pdftex, mkII, mkIV, and all the other new terms), so i'll probably just "texexec funk.tex" as a workaround. /however/, when i get some free time, i'll be playing with lua, and i'd like it to work right. i've been a latex user since my undergrad a couple of years ago, and i just found metapost maybe one month ago. what an eye opener! i love programming and i love making dorky little vector images... it's the perfect marriage! maybe somebody bright can shed some light on this? thanks everybody, adam % author: adam fuller % date: 24/5/2010 % description: why does placehead=no,page=yes in \definehead push % the first line of a slide down by one? when a slide is too long % and breaks to another page, that page starts right up at the top, % without the annoying extra whitespace. trying to unravel it. \setupheadertexts[myslide][] \setupheader[state=start] \setuppagenumbering[state=stop] \definehead[myslide][subsubsection] \setuphead[myslide][style=slanted,placehead=no,page=yes] \definestartstop[slide][ before={\page\startalignment[right,nothyphenated,hanging]\tf}, after={\stopalignment}] \starttext \showframe[text]% \showframe[header]% \myslide{}% \midaligned\framed[location=middle,align=center,offset=none,frame=off]{ %\blank[2*big,force] {\bfa Adam Fuller} \blank[1*big,force] {\em from} \blank[1*big,force] {\bfa U. Canterbury} \blank[1*big,force] {\em talks about} \blank[1*big,force] {\bfa Adapting simplified propeller turbines to higher specific speeds: CFD studies} \blank[1*big,force] {\em at} \blank[1*big,force] {\bfa Hidroenergia 2010} } \page% \myslide{Where I start from}% My Ph.D. research has been to increase the specific speed ($N_S$), starting with an existing range, while maintaining a turbine efficiency of 70\%. By \em{adapting}, I mean taking an existing design \em{philosophy} to a new design \em{point}. This \em{philosophy} is just a list of rules that reflect the turbines' intended use: \startitemize \item no guide vanes \item run at 1500~rev/min only \item use flat blades \stopitemize \myslide{New design point, new challenges} The paper discusses how increasing the specific speed may impact on the design of such a turbine's three main components. The adapted version of each component brings its own challenges. At higher $N_S$ \startitemize \item draft tube performance is increasingly important. How sensitive is its performance to the inputs in this particular case? \item velocity triangles at the runner's leading and trailing edge become less forgiving to uncertainty (dimensional and fluid dynamical) \item the volute's priority changes from \quote{provide swirl $x$} to \quote{provide uniform axial flow at mimimum loss}. How must the design change? \stopitemize \myslide{For this presentation} To illuminate these three points, I worked up a CFD study related to each component. To summarize the studies: \startitemize \item Draft tube: $C_p = f({\rm swirl}, \theta)$. What is $f$? I'll try to put my result in the context of the literature. \item Runner: from the desktop-design stage, the ratios \startformula \omega r:V_a:\Delta V_t\approx 8:4:1, \stopformula are expected to cause problems with sensitivity of output and efficiency to speed. I'll talk about how my CFD results suprised me. \item Volute: Trying to reconcile the need for predictable axial runner inlet flow, low loss, and no flow-spanning vanes or struts has led to an adaptation of previous Giddens volutes. I'll talk about the changes that were made, and show that the new volute looks to meet the requirements. \stopitemize \stoptext

1 0