- ntg-context - Mailing Lists

\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

Appendix label in TOC (Table of Contents) : APPENDIX instead of CHAPTER
by Mathieu DUPONT 23 May '11

23 May '11

Hi, The following code : \setuplabeltext[chapter=CHAPTER~]\setuplabeltext[appendix=APPENDIX~]\setuplist [chapter] [label=yes,style={\blank[0cm]}] \starttext \completecontent \chapter{Title of a chapter} \startappendices\chapter{Title of an appendix}\stopappendices \stoptext results in : Contents CHAPTER 1 Title of a chapter CHAPTER A Title of an appendix Instead, I would like to get the following result : Contents CHAPTER 1 Title of a chapter APPENDIX A Title of an appendix In other words, this command :\setuplist [chapter] [label=yes]seems not to take this one :\setuplabeltext[appendix=APPENDIX~]into account. Am I forgetting to add another important command in my header ?Any help would be greatly appreciated. Thanks in advance, Mathieu

2 1

how to change current directory ?
by 정진기 23 May '11

23 May '11

2 1

[OT] Street-Fighting Mathematics
by luigi scarso 22 May '11

22 May '11

Street-Fighting Mathematics The Art of Educated Guessing and Opportunistic Problem Solving Sanjoy Mahajan Foreword by Carver A. Mead The book is made with ConTeXt mkii (so it's not a 100% off-topic, because we know that Sanjoy uses ConTeXt) -- luigi

5 4

Feature request: setuppapersize
by Aditya Mahajan 22 May '11

22 May '11

Hans, Since we have some leverage with backward compatibility in MkIV, can we make \setuppapersize (slightly) more intuitive. Normally, one would expect \setuppapersize[A5] to be equivalent to \setuppapersize[A5][A5] but currently it is equivalent to \setuppapersize[A5][A4] This is a bit confusing, and means that we always have to specify the printpaper size; even if it is equal to paper size. Can we modify the definition of \dodefinepapersize to change this behavior? \def\dodefinepapersize[#1][#2][#3]% {\ifsecondargument \doifsomething{#1} % to be sure {\doifassignmentelse{#2} {\getparameters [\??pp#1] % geen \c!scale, scheelt hash ruimte [\c!width=\@@ppwidth,\c!height=\@@ppheight,\c!offset=\@@ppoffset,#2]% %AM: Added these two lines \setvalue{\??pp:1:#1}{#1}% \setvalue{\??pp:2:#1}{#1}}% {\setvalue{\??pp:1:#1}{#2}% \setvalue{\??pp:2:#1}{#3}}}% (*) see below \else \getparameters[\??pp][#1]% \setuppapersize % hm. this will freeze ! \fi} Perhaps, in line (*), we should also check if #3 is something, otherwise set ??p:2:#1 to #2: \doifsomethingelse{#3} {\setvalue\??pp:2:#1}{#3}} {\setvalue\??pp:2:#1}{#2}} What do you think? Aditya

7 20

Using text as a clip path for Metafun & free shape paragraphs
by Otso Helenius 22 May '11

22 May '11

Thanks to Wolfgang for the instructions on changing fonts, \switchtobodyfont works as expected. I still have to dig up the exact definitions of both \switchtobodyfont and \switchtotypeface, as the latter command seems to work in Hans' examples (for example showfont.pdf) but not with my installation. Now, I've been trying to use metapost for achieving magazine type layout with ConTeXt, and have a question about the following features: 1) Is it possible to use TeX typeset text as a clipping path for MP graphics? What I would like to achieve is a similar cut mask as seen in this picture: https://modernpost.files.wordpress.com/2009/10/rockstar11091.jpg i.e. the text outline cuts a hole in the brown filled rectangle revealing the bitmap below. I can cut pictures easily with paths in MP like so: \startMPcode fill unitsquare xysized (100mm,100mm) withcolor green; picture cur; cur := currentpicture; currentpicture := nullpicture; fill unitsquare xysized (100mm,100mm) withcolor blue; path mask; mask := unitsquare xysized (100mm,100mm) -- reverse unitsquare xysized (100mm,10mm) shifted (0mm,45mm) -- cycle; clip cur to mask; draw cur; \stopMPcode But I can't cut pictures with pictures (only with masks), nor have I found a way in any of the manuals (mmakempy.pdf, metafun-p.pdf, metapostmanual.pdf) to output text outline as paths which could be used for cutting a hole in the mask picture. Is this possible? 2) MP gives an easy way to format free flowing paragraph shapes similar to this image: http://www.davidlcade.com/images/gropius/g2.png . I have followed the instructions on pages 435-444. The problem with this approach is that the text which will be placed in a freely shaped paragraph will be a separate block which won't flow freely with other text in the document body if the contents on earlier pages change. I guess this drops in the category of big feature requests, but it would be nice to be able to define the shapes and positions of ConTeXt columns/paragraphs with MP graphics. In InDesign columns of any shape anywhere on the page can be connected without having to separate one block of text from the rest. With this feature one could define for example a 2-page spread for a magazine (with free shape graphics and columns) in between two ordinarily defined pages and would not have to manually disrupt the body text flow through the document. Best regards, Otso Helenius

2 1

request for a quick & dirty hack: shift accents in compose=yes
by Mojca Miklavec 22 May '11

22 May '11

Hello, I'm using a feature "compose=yes" \definefontfeature [default] [liga=yes,kern=yes,tlig=yes,compose=yes] in a handwritten font to get ccarons (font SnellRoundhandLTStd-Scr.otf). However the carons are placed way off to the right due to the nature of handwritten font. Is there any simple, very-quick-and-dirty way to fix ConTeXt sources (I need it very soon), so that carons would be placed a bit more to the left? (I don't mind to do it just for this single document and then forget about it?) Thanks a lot, Mojca

4 4

Font selection problem in MKIV
by Otso Helenius 22 May '11

22 May '11

> Try > > \switchtotypeface[LeagueScript][12pt] > \switchtobodyfont[LeageScript] Is \switchtobodyfont the recommended way of changing the typeface temporarily anywhere in a document (for example when making cover page graphics)? Its name implies only document body. Nevertheless, \switchtobodyfont works (at least in the document body, haven't tested yet elsewhere) without setting \setupbodyfont. > \definetypeface[LeagueScript][ss][specsans][League Script Thin] > \definetypeface[Pompadour][ss][specsans][Pompadour] This seems to work for most fonts, with others like Pompadour it fails (pompadour has SubFamily string of "Black" [Mac] and "Regular" [Windows] in the .otf), and spec fails to find pompadour-normal-normal which it is looking for). Pompadour is a serif font, so i tried also with arguments [rm][specserif]. I have looked into co-typography.pdf for help, and while it is very extensive in some parts, in others it is (too) technical and lacks expanations for some parameters. As soon as I get these issues sorted out I'll try if I can make the MKIV font pages in the Wiki a bit more beginner friendly. Best regads, Otso Helenius

2 5