May 2011 - ntg-context - NTG Mailing Lists

Re: [NTG-context] Appendix label in TOC (Table of Contents) : APPENDIX instead of CHAPTER
by Mathieu DUPONT 23 May '11

23 May '11

Effectively, now that I've installed MkIV, I get the output I expected. Thank you very much, Wolfgang ! Mathieu

1 0

Table of contents
by Oliver Buerschaper 23 May '11

23 May '11

Dear all, is it possible to have entries in the table of contents not indented at all whenever they stem from unnumbered headings? For example: --- \starttext \startfrontmatter \completecontent \chapter{Preface} \stopfrontmatter \startbodymatter \part{Test} \chapter{Tufte} \chapter{Bryson} \part{Test} \chapter{Tufte} \chapter{Bryson} \stopbodymatter \startbackmatter \chapter{Acknowledgements} \stopbackmatter \stoptext --- Many thanks, Oliver

2 1

MPdefinitions
by Vedran Miletić 23 May '11

23 May '11

Hi, compiling example with quadriliterals and \startMPdefinitions{solvers} \stopMPdefinitions from MetaFun manual, regardless of the code that is commented out inside MPdefintions environment, gives: ! You can't use `\relax' after \the. system > tex > error on line 30 in file solvers.tex: You can't use ` ... 20 % z1=0.5[z11,z13] ; z2=0.5[z21,z23] ; 21 % z3=0.5[z31,z33] ; z4=0.5[z41,z43] ; 22 % draw z1--z3 dashed evenly ; draw z2--z4 dashed evenly ; 23 % z0=whatever[z1,z3]=whatever[z2,z4] ; 24 % mark_rt_angle (z1,z0,z2); 25 % if show_labels>0: 26 % draw_problem_labels ; 27 % fi; 28 % endgroup ; 29 % enddef ; 30 >> \stopMPdefinitions 31 32 \starttext 33 %a 34 \stoptext <recently read> \@MPF@::solvers \dostartMPdefinitions ...er {\the \MPinstancetoks #2} l.30 \stopMPdefinitions Is this a bug? Vedran

2 4

Re: [NTG-context] Hyphenating compound words in MKIV & microtypographyy
by Hans Hagen 23 May '11

23 May '11

On 23-5-2011 5:54, Otso Helenius wrote: >> it produces larger files, take more runtime and in most cases does >> not look better at all; for instance one can argue that protrusion >> gives more width but at the same time it introduces the boundary >> condition that some characters have to hang; or take hz (expansion) >> ... when applied so much that it gets visible, it will also lead to >> similar shapes in successive lines to look different >> >> so, just enabling these features assuming that the output looks >> better is debatable (sometimes adding or removing a word is more >> effective) > > I agree, in many cases automatic layout of content can look horrific because the algorithms > aren't able to solve each possible case in a near optimal way (while we as humans are). > And also, there is no question about it, *every* setting should be possible to turn on and off > depending on the situation. > > Just as with WYSIWYG tools such as InDesign, manual adjustment of layout is needed to achieve > optimal results. But my actual complaint is this: the example I pasted was a very trivial > and simple typesetting task. Even the current versions MS Office can automatically achieve > acceptable paragraph look with the given input. In such case there should not be any need > to manually adjust spacing and expansion of words nor forcing the column into a ragged one. > > The output of this MKIV source: > > \mainlanguage[fi] > \language[fi] > \definefontfeature[default][default][protrusion=quality, expansion=quality] > \setupalign[hz, hanging, spacing] > \starttext > \startcolumns[n=2] > \dorecurse{10}{kolmivaihekilowattituntimittari ympäristöliiketoiminta epäjärjestelmällisyydellistyttymättömyydellänsäkään järjestelmällisentelentelemättömyydellänsäkään hääyöaie kolmivaihekilowattituntimittari ympäristöliiketoiminta epäjärjestelmällisyydellistyttymättömyydellänsäkään järjestelmällisentelentelemättömyydellänsäkään hääyöaie} > \stopcolumns > \stoptext > > can be downloaded here: https://pi-xi.net/share/context_hyphen.pdf > > I also wrote a "close as possible" equivalent of the code above in LaTeX and > compiled it with pdfTeX (TL 2011): > > \documentclass[12pt, twocolumn, a4paper, finnish]{article} > \usepackage[utf8]{inputenc} > \usepackage[finnish]{babel} > \usepackage{ae} > \usepackage[auto=true, spacing=true, kerning=true, tracking=true, protrusion=true, expansion=true]{microtype} > \usepackage{pgffor} > \setlength{\parindent}{0mm} > \newcommand{\Repeat}[2]{\foreach \n in {1,...,#1}{#2}} > \begin{document} > \foreach \n in {1,...,10}{kolmivaihekilowattituntimittari ympäristöliiketoiminta epäjärjestelmällisyydellistyttymättömyydellänsäkään järjestelmällisentelentelemättömyydellänsäkään hääyöaie kolmivaihekilowattituntimittari ympäristöliiketoiminta epäjärjestelmällisyydellistyttymättömyydellänsäkään järjestelmällisentelentelemättömyydellänsäkään hääyöaie} > \end{document} > > The LaTeX example can be downloaded here: https://pi-xi.net/share/latex_hyphen.pdf > > As can be seen, the neither versions have any specific adjustments done by hand: both > only have the microtypographic features turned on. There is no comparison, the pdfTeX > version looks superior: there are no rivers, all lines are justified to equal length, > and the expansion and spacing are both acceptable. (1) The 'spacing' options does not work and even gives an error in mkiv) so remove that one. What version of context are you running? I've already fotgotten about it but I think it was an experimental pdftesx feature with side effects. In pdftex hz and protrusion is also somewhat tricky as it can bleed from one font instance to another (due to traditional tex's internal font sharing), although context takes some precautions. (2) But, more important: add \setuplayout[width=middle] to give context a more similar opportunity to produce something acceptable. You're now giving context a disadvantage of narrower columns. (3) You can remove the \language as you already set \mainlanguage. (4) In context protrusion and expansion is a font property and applying it globally to all fonts (with some flag) will not happen. Actually, in some situations you need to turn it on explicitly (imaging hanging happening when you're doing a table). I don't know what latex's default layout setup is but if you want to do an experiment, you need to make sure that you use the same widths of columns. 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 -----------------------------------------------------------------

1 0

query about referring to pdf attachments
by Jesse Alama 23 May '11

23 May '11

Can one refer to PDF attachments as though they were local files? I'd like to treat the PDF as a kind of rudimentary filesystem. Whatever is attached to the PDF can be found under the "root directory" of the PDF. One could then place hyperlinks to these files which, when followed, cause an attachment to be opened (say, a music player, a web browser, etc.). Ideally, one would be able to do something like this: \useattachment[my-video][my-video.mpg] \attachment[my-video] \useURL[my-video-url][file:///my-video.mpg][][Awesome Video] \starttext Follow the link to \from[my-video-url]! \stoptext The "file:///my-video.mpg" URI is a guess; the idea is to somehow refer to a file placed in the PDF's "filesystem". Jesse

1 0

\startquotation and citations
by Oliver Buerschaper 23 May '11

23 May '11

Dear all, I'm struggling with quotation blocks and proper placing of citations… In an ideal world I'd be striving for something like this: \startquotation[source=…] \input tufte \stopquotation where … could be either of: 1. a simple string: {Edward Tufte}, 2. a citation command: \cite[Tuf:yyyy] 3. a footnote: \footnote{See \cite[Tuf:yyyy]} This should be typeset immediately after the closing delimiter and well before \stopnarrower. In the real world (and with a deadline approaching rapidly) I've tried two approaches so far: 1. A hack dating back three years which bypasses the delimitedtext mechanism. --- \long\def\startextendedquotation[#1]#2\stopextendedquotation {\bgroup\par \blank[halfline] \startnarrower[4em] \symbol[leftquotation]% #2\removeunwantedspaces \symbol[rightquotation]#1 \stopnarrower \blank[halfline] \par\egroup} \starttext \input tufte \startextendedquotation[\footnote{See Tufte…}] \input tufte \stopextendedquotation \input tufte \stoptext --- Here the footnote actually appears, however, the beginning of the quotation looks weird (and setting up margins etc. is a bit messy). 2. Another hack which employs delimitedtext but abuses its closing delimiter option: --- \setupdelimitedtext [quotation] [leftmargin=4em, rightmargin=4em, spacebefore=halfline, spaceafter=halfline] \starttext \input tufte \bgroup \setupdelimitedtext [quotation] [right={\symbol[rightquotation]\footnote{See Tufte…}}] \startquotation \input tufte \stopquotation \egroup \input tufte \stoptext --- This approach places the opening delimiter nicely in the margin of the quotation block but sadly swallows the footnote (ordinary strings seem fine though). How to combine the looks of 2 with the footnotes of 1? Many thanks, Oliver

2 1

pdf attachments broken in latest minimal?
by Jesse Alama 23 May '11

23 May '11

It seems that PDF attachments aren't working in the latest minimals: $ context --version mtx-context | main context file: /Users/alama/context/tex/texmf-context/tex/context/base/context.mkiv mtx-context | current version: 2011.05.18 22:26 ======================================== \useattachment[busted][hi.txt] \starttext attachment here: \attachment[busted] \stoptext ======================================== Prepending \setupinteraction[state=start] to the document, and the compiling with, say, xetex, results in a PDF that has the attachment. But not with mkiv. -- Jesse Alama http://centria.di.fct.unl.pt/~alama/

2 3

\type and linebreak (again)
by Andreas Schneider 23 May '11

23 May '11

Hi, I stumbled across the same problem that was discussed earlier this month: \type doesn't break, even if there are opportunities. I tried to follow the suggestions given in that thread, but with no success: \setuppapersize[A4][A4] \starttext \setuptype[space=stretch] %\setupalign[stretch] %\setuptolerance[stretch] \type{cp $SOMEVAR/some/very/very/very/long/directory/WITHFILE $SOMEVAR/other/long/directory} \startitemize \item \type{cp $SOMEVAR/some/very/very/very/long/directory/WITHFILE $SOMEVAR/other/long/directory} \stopitemize \stoptext I tried with and without the \setupalign/\setuptolerance commands, without success; both lines exceed the margins. (Tested with ConTeXt ver: 2011.05.18 22:26 MKIV fmt: 2011.5.23) Is there anything else I can do/setup to get such long verbatim lines broken? I would also like an option for character-based line wraps; i.e. it should (optionally; not in this particular case for example) break a word even in the middle if necessary, and without hyphenation mark. Especially in similar cases where I have a very very long directory name, I wouldn't care if it gets broken "the hard way". Thanks in advance! -- Best Regards, Andreas

2 3

Hyphenating compound words in MKIV & microtypography
by Otso Helenius 23 May '11

23 May '11

Hi, MKIV seems to have a problem in hyphenating long finnish compound words in MKIV (2011.05.18 22:26). Here is a minimalist example (columns added to exaggerate the problem): \mainlanguage[fi] \language[fi] \starttext \startcolumns[n=3] kolmivaihekilowattituntimittari ympäristöliiketoiminta epäjärjestelmällisyydellistyttymättömyydellänsäkään järjestelmällisentelentelemättömyydellänsäkään \stopcolumns \stoptext Similarly with en-hyphenation and \input knuth, some of the lines stretch out in an ugly fashion. What am I doing wrong? I don't have these problems in LaTeX. P.S. The punctuation characters should be partially hung out in a justified paragraph (similar to what microtype package does on LaTeX). Wikipedia says ConTeXt has "interfaces for handling microtypography" but they don't seem as apparent and as easy as using microtype on LaTeX. The wiki article Protrusion#MkIV presents \definefontfeature but I find it counterintuitive that one has to use \definefontfeature[default][default][protrusion=quality,expansion=quality] \setupalign[hz,hanging] to enable the features. It is unclear if these lines switch the features on globally for all loaded fonts (for example ttf/otf ones defined with \starttypescript). IMHO these features should be enabled by default because they produce better typographic quality by default (which should be the preference), and could be switched off anyway if wanted. The less setup lines one has to add before \starttext to get high quality results the better. Otso Helenius

2 1

Roman numbers for chapters in chapter lines but not in section lines
by Mathieu DUPONT 23 May '11

23 May '11

Hi, I am trying to obtain the following result : CHAPITRE I Title of chapter1.1 Title of section1.1.1 Title of subsection In other words, I need my chapter numbers to be in roman number, but not in the numbers of the sections and subsections (1.1.1 and not I.1.1). Here is the base code : \setuplist [chapter] [label=yes,style={\blank[0cm]}]\setupsection[section-2][conversion=Romannumerals]\setuplabeltext[chapter=CHAPITRE~] \starttext \placecontent \chapter{Title of chapter}\section{Title of section}\subsection{Title of subsection} \stoptext which results in : CHAPITRE I Title of chapterI.1 Title of sectionI.1.1 Title of subsection Any idea ?All help is greatly appreciated. Thanks a bunch, Mathieu

2 1