March 2016 - ntg-context - NTG Mailing Lists

Why does 0.0001pt make such a big difference?
by Peter Münster 24 Mar '16

24 Mar '16

Hi, Please compare \setupwhitespace[0.0001pt plus 2ex] with \setupwhitespace[0pt plus 2ex] here: \showframe \setuphead[section][style={\switchtobodyfont[72pt]}] \setupalign[height] \setupwhitespace[0.0001pt plus 2ex] % desired result %\setupwhitespace[0pt plus 2ex] % "plus 2ex" is unused \starttext \dorecurse{5}{\dorecurse{150}{bla }\par} \section{test} bla \stoptext Why is there such a difference please? TIA, -- Peter

2 1

Re: [NTG-context] Length range control of the last line of paragraph
by Hans Hagen 24 Mar '16

24 Mar '16

On 3/21/2016 8:14 PM, Jan Tosovsky wrote: > Dear All, > > when paragraphs are separated by indenting the first line (instead of an > empty line), these rules should be followed: a next beta will provide a bit more control over last words \usemodule[art-01] \setupbodyfont[10pt] \definehyphenationfeatures [words-1] [rightwords=3, lefthyphenmin=4, righthyphenmin=4] \definehyphenationfeatures [words-2] [rightwords=3, rightchars=word, lefthyphenmin=4, righthyphenmin=4] \definehyphenationfeatures [words-3] [rightwords=3, rightchars=8, lefthyphenmin=4, righthyphenmin=4] \enabletrackers[hyphenator.visualize] \setupalign[verytolerant,stretch] \dontcomplain \setuphyphenation [method=traditional] \edef\tufte{\cldloadfile{tufte}} \starttext \dorecurse{100}{ \hsize\dimexpr\textwidth-#1mm\relax \start \sethyphenationfeatures[words-1] \tufte \par \hsize\dimexpr\textwidth-#1mm\relax \start \sethyphenationfeatures[words-2] \tufte \par \hsize\dimexpr\textwidth-#1mm\relax \start \sethyphenationfeatures[words-3] \tufte \par \page } \stoptext not uploaded yet ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------

3 5

Re: [NTG-context] Length range control of the last line of paragraph
by Hans Hagen 24 Mar '16

24 Mar '16

On 3/23/2016 8:14 PM, Jan Tosovsky wrote: > On 2016-03-22 Hans Hagen wrote: >> On 3/21/2016 8:14 PM, Jan Tosovsky wrote: >>> >>> when paragraphs are separated by indenting the first line >>> (instead of an empty line), these rules should be followed: >> >> a next beta will provide a bit more control over last words >> >> \usemodule[art-01] \setupbodyfont[10pt] >> >> \definehyphenationfeatures >> [words-1] >> [rightwords=3, >> lefthyphenmin=4, >> righthyphenmin=4]> >> >> ... >> >> not uploaded yet > > I am impressed by your passion. Thanks for your continuous tweaking and inventing various approaches to fulfil my needs! i added only a few lines ... the rightwords is already there for a while (but the rightchars is new) ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------

1 0

Re: [NTG-context] Length range control of the last line of paragraph
by Hans Hagen 23 Mar '16

23 Mar '16

On 3/22/2016 9:57 PM, Jan Tosovsky wrote: > On 2016-03-22 Hans Hagen wrote: >> On 3/21/2016 8:14 PM, Jan Tosovsky wrote: >>> Dear All, >>> >>> when paragraphs are separated by indenting the first line (instead of >> an >>> empty line), these rules should be followed: >>> >>> (1) the last line lenght is greater than the left indent >>> xxxxxxxxxxxxxxxx >>> xxxx >>> xxxxxxxxxxxxxx >>> xxxxxxxxxxxxxxxx >>> >>> (2) the last line is shorter than block width >>> xxxxxxxxxxxxxxxx >>> xxxxxxxxxxxxxx >>> xxxxxxxxxxxxxx >>> xxxxxxxxxxxxxxxx >>> >> >> you need to keep in mind that what would work out well for one specific >> case will not look nice in general as the last line filling is just one >> of the aspects ... so, your last line + following first line might look >> okay (according to whatever rules and criteria) but then, as you also >> need to increase the tolerance and enable stretch to permit that >> solution to be found, the rest might look like crap > > I (naively) thought the last line can be somehow isolated in the engine so the parfillskip settings doesn't influence the rest (too much). well, in order to determine what the last line is tex has to construct the paragraph so x x xxxxxxxx becoming x x xxxxxxxx would be real bad > I understand your point. > >>> (ad 2) This can be done using \parfillskip XXpt plus 1fil (where >>> XX is required gap) >> >> setting the XXpt is tricky as it might lead to underful or overful >> cases when that amount start interfering with an optimal solution (as it's >> seen as acceptable overflow in some direction) >> > > underful or overful where? in previous lines? I am quite lost here :-) \starttext \setupalign[tolerant,stretch] \dorecurse{100}{ \hsize\dimexpr\textwidth-#1pt\relax \parfillskip -4em plus 1 fill \input tufte \page } \stoptext page 43 >> it's hard to envision an interface, maybe some extra key in setupalign >> >> \setupindenting[big] \indenting[yes] >> >> \edef\ward{\cldloadfile{ward}} >> >> \setupalign[verytolerant,stretch] >> >> \dorecurse{100}{ >> \hsize\dimexpr\textwidth-#1mm\relax >> \parfillskip \zeropoint plus 1fil\relax >> \ward \par >> \parfillskip \zeropoint plus \dimexpr\availablehsize- >> 3\parindent\relax >> \ward \par >> \startnarrower[left] >> \parfillskip \zeropoint plus 1fil\relax >> \ward \par >> \stopnarrower >> \startnarrower[left] >> \parfillskip \zeropoint plus >> \dimexpr\availablehsize-3\parindent\relax >> \ward \par >> \stopnarrower >> \page >> } > > Wow, this is cool visualization! > > When \zeropoint is replaced by e.g. 2em, I have what wanted originally. > > Could anybody explain drawbacks of such approach? I mean especially that overful magic above. I'd like to summarize this topic on Wiki. > > Jan > > ___________________________________________________________________________________ > If your question is of interest to others as well, please add an entry to the Wiki! > > maillist : ntg-context(a)ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context > webpage : http://www.pragma-ade.nl / http://tex.aanhet.net > archive : http://foundry.supelec.fr/projects/contextrev/ > wiki : http://contextgarden.net > ___________________________________________________________________________________ > -- ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------

2 1

Re: [NTG-context] Tagging and startitemize[columns]
by Christoph Reller 23 Mar '16

23 Mar '16

On Tue, 22 Mar 2016 14:53:05 +0100, Hans Hagen <pragma(a)wxs.nl> wrote: > > On 3/22/2016 9:19 AM, Christoph Reller wrote: > > \setuptagging[state=start] > > \starttext > > > > \startsectionlevel[title=Chapter] > > Text. > > \startitemize[columns] > > \item A > > \item B > > \stopitemize > > > > \startitemize > > \item A > > \item B > > \stopitemize > > More Text. > > \stopsectionlevel > > \stoptext > > > > and what if you remove the % in line 847 in strc-itm.mkvi and remake the > format? > > \strc_itemgroups_tag_start_group > Indeed this solves the current problem. Thank you Hans! I hope that you can uncomment this line in the next beta, or do you expect any bad side effects from doing so? Also I hope that it is okay if I report any further issues regarding tagging here. Thanks, Christoph

1 0

Re: [NTG-context] Length range control of the last line of paragraph
by Hans Hagen 22 Mar '16

22 Mar '16

On 3/21/2016 8:14 PM, Jan Tosovsky wrote: > Dear All, > > when paragraphs are separated by indenting the first line (instead of an > empty line), these rules should be followed: > > (1) the last line lenght is greater than the left indent > xxxxxxxxxxxxxxxx > xxxx > xxxxxxxxxxxxxx > xxxxxxxxxxxxxxxx > > (2) the last line is shorter than block width > xxxxxxxxxxxxxxxx > xxxxxxxxxxxxxx > xxxxxxxxxxxxxx > xxxxxxxxxxxxxxxx > you need to keep in mind that what would work out well for one specific case will not look nice in general as the last line filling is just one of the aspects ... so, your last line + following first line might look okay (according to whatever rules and criteria) but then, as you also need to increase the tolerance and enable stretch to permit that solution to be found, the rest might look like crap it's the same for successive hyphenation and club/widow: any whole document setting that is done to get rid of one or two odd cases will often make the rest of the text look bad this is a side effect of focusing on a specific typographical aspect whereby ignoring the rest combined with fully automated typesetting of course one can have extensive discussions about how things should look right but one cannot ignore the text itself then: adding a few words or rephrasing is often a better way out (the same applies to fonts: one can stress the virtues of some advanced kerning between two glyphs but at the same time be blind for the cases where it doesn't happen) > (ad 1) Some suggestions can be found in > http://tex.stackexchange.com/questions/28357/ensure-minimal-length-of-last-l > ine - but to be honest, it is not very clear to me how to apply it and even > combine with (2) > > (ad 2) This can be done using \parfillskip XXpt plus 1fil (where XX is > required gap) setting the XXpt is tricky as it might lead to underful or overful cases when that amount start interfering with an optimal solution (as it's seen as acceptable overflow in some direction) > I'd be grateful for any command which would set this globally for all > paragraphs. Partly requested here http://tracker.luatex.org/view.php?id=885 > > One could set > (a) minimum length - default=2*indent > (b) minimum gap - default=indent > (c) minimum block width where (a) and (b) are still to be applied - > default=2*a+b any heuristic that works for one case will make another worse (when applied to a whole document) > (ad c) if there are narrower blocks within the document (e.g. blockquotes), > we should still have some room for typesetting the last line content. If the > area width is insufficient, the last line would be typeset without these > (a+b) restrictions. > > In meantime, any suggestion how to combine a+b manually are welcome. it's hard to envision an interface, maybe some extra key in setupalign \setupindenting[big] \indenting[yes] \edef\ward{\cldloadfile{ward}} \setupalign[verytolerant,stretch] \dorecurse{100}{ \hsize\dimexpr\textwidth-#1mm\relax \parfillskip \zeropoint plus 1fil\relax \ward \par \parfillskip \zeropoint plus \dimexpr\availablehsize-3\parindent\relax \ward \par \startnarrower[left] \parfillskip \zeropoint plus 1fil\relax \ward \par \stopnarrower \startnarrower[left] \parfillskip \zeropoint plus \dimexpr\availablehsize-3\parindent\relax \ward \par \stopnarrower \page } The 2*indent is not enough in most cases. Actually, in context another mechanism can help: \definehyphenationfeatures [words] [rightwords=3, lefthyphenmin=4, righthyphenmin=4] \enabletrackers[hyphenator.visualize] \setupalign[verytolerant,stretch] \dontcomplain \sethyphenationfeatures [words] \setuphyphenation [method=traditional] \dorecurse{100}{\hsize\dimexpr\textwidth-#1mm\relax \input tufte \page} \stoptext currently this doesn't discourage breaks between the last words but i'll add an option for that (chars or words in that case, that is the question) ... the reason for this mechanism is not so much the length but more the fact that one doesn't want an (even long) last word hyphenated. Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------

2 1

Re: [NTG-context] Length range control of the last line of paragraph
by Hans Hagen 22 Mar '16

22 Mar '16

On 3/22/2016 9:29 PM, Jan Tosovsky wrote: > Hi Michael, > > On 2016-03-22 Rogers, Michael K wrote: >> >> Perhaps this? (I'm still better at Plain TeX than ConTeXt.) >> >> %%%%%%%%%%%%%%%% >> \starttext >> \setupindenting[yes,40pt] >> \dimen0=\hsize >> \advance\dimen0 by -\parindent >> \advance\dimen0 by -2em >> \parfillskip=2em plus \dimen0 >> \tolerance=0 % strictly enforces glue dimensions/stretching - may >> have unwanted side effects >> >> \dorecurse{41}{wxyz }\par >> \dorecurse{42}{wxyz }\par >> \dorecurse{26}{wxyz } >> > > thanks, if I understand correctly, this follows my original idea to dynamically get the actual block width, simply substract indentation and use the variable for defining \parfillskip i just added some variant to an existing setting, nothing too fancy, just a delta of local width and some indent > I modified it slightly, but it doesn't seem to have desired effect. The last line of third paragraph is still too short: because there is more involved, like hyphenation, badness of other lines, etc ... after all it is stretch, not absolute i'm not going to waste time too much on figuring out some heuristic that works in one case but not in the other > \starttext > \hsize 15.37cm > \input tufte > > \parfillskip30pt plus 1fil > \input tufte > > \dimen0\hsize > \advance\dimen0 by -60pt > \parfillskip=30pt plus \dimen0 > %\tolerance=0 % strictly enforces glue dimensions/stretching - may have unwanted side effects well, no stretch or tolerance means that the solution space becomes pretty small (so you might get your desired last line but a terrible n lines before that) and hsize is not always the best choice (normally all these par values also depends on the global body font, spacing, margins, etc. so it's more dynamic) > \input tufte > > \parfillskip0pt plus 1fil > > \input tufte > > hsize is \the\hsize{}\par > dimen0 is \the\dimen0{} > > \stoptext > > I disabled that tolerance as it caused overflowing the text to the margin. Was that the key for the functionality? what key? try to add a minus or negative plus ... the outcome differes per case Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------

1 0

Re: [NTG-context] Length range control of the last line of paragraph
by Rogers, Michael K 22 Mar '16

22 Mar '16

Perhaps this? (I'm still better at Plain TeX than ConTeXt.) %%%%%%%%%%%%%%%% \starttext \setupindenting[yes,40pt] \dimen0=\hsize \advance\dimen0 by -\parindent \advance\dimen0 by -2em \parfillskip=2em plus \dimen0 \tolerance=0 % strictly enforces glue dimensions/stretching - may have unwanted side effects \dorecurse{41}{wxyz }\par \dorecurse{42}{wxyz }\par \dorecurse{26}{wxyz } \blank \hrule \blank % compare \parfillskip=0ptplus1fill \dorecurse{35}{wxy x } xy.\par \dorecurse{42}{wxyz }\par \dorecurse{26}{wxyz } \stoptext %%%%%%%%%%%%%%%% - Michael > On Mar 21, 2016, at 3:14 PM, Jan Tosovsky <j.tosovsky(a)email.cz> wrote: > > Dear All, > > when paragraphs are separated by indenting the first line (instead of an > empty line), these rules should be followed: > > (1) the last line lenght is greater than the left indent > xxxxxxxxxxxxxxxx > xxxx > xxxxxxxxxxxxxx > xxxxxxxxxxxxxxxx > > (2) the last line is shorter than block width > xxxxxxxxxxxxxxxx > xxxxxxxxxxxxxx > xxxxxxxxxxxxxx > xxxxxxxxxxxxxxxx > > > (ad 1) Some suggestions can be found in > http://tex.stackexchange.com/questions/28357/ensure-minimal-length-of-last-l > ine - but to be honest, it is not very clear to me how to apply it and even > combine with (2) > > (ad 2) This can be done using \parfillskip XXpt plus 1fil (where XX is > required gap) > > I'd be grateful for any command which would set this globally for all > paragraphs. Partly requested here http://tracker.luatex.org/view.php?id=885 > > One could set > (a) minimum length - default=2*indent > (b) minimum gap - default=indent > (c) minimum block width where (a) and (b) are still to be applied - > default=2*a+b > > (ad c) if there are narrower blocks within the document (e.g. blockquotes), > we should still have some room for typesetting the last line content. If the > area width is insufficient, the last line would be typeset without these > (a+b) restrictions. > > In meantime, any suggestion how to combine a+b manually are welcome. > > Thanks, Jan > > ___________________________________________________________________________________ > If your question is of interest to others as well, please add an entry to the Wiki! > > maillist : ntg-context(a)ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context > webpage : http://www.pragma-ade.nl / http://tex.aanhet.net > archive : http://foundry.supelec.fr/projects/contextrev/ > wiki : http://contextgarden.net > ___________________________________________________________________________________ ________________________________ This e-mail message (including any attachments) is for the sole use of the intended recipient(s) and may contain confidential and privileged information. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this message (including any attachments) is strictly prohibited. If you have received this message in error, please contact the sender by reply e-mail message and destroy all copies of the original message (including attachments).

2 1

Poster template
by MANUEL GONZALEZ SUAREZ 22 Mar '16

22 Mar '16

Hello friends I would like to know if there is a template to make posters in ConTeXt, as there are in LaTeX (beamerposter, a0poster, etc.) Thanks very much

2 2

Tagging and startitemize[columns]
by Christoph Reller 22 Mar '16

22 Mar '16

Hi, Stil ConTeXt is the only TeX-based typesetting system that can produce tagged PDF - this is a unique feature, thank you Hans! I have, however, found that the following MWE produces wrongly nested tagging information. Specifically: - The itemization with columns (\startitemize[columns]) is not contained in an "itemgroup" - The second itemization (without columns) is tagged outside of the "sectioncontent" (Maybe the second issue is a consequence of the first.) I am afraid but this might be a bug. Thank you for any feedback. Cheers, Christoph MWE: \setuptagging[state=start] \starttext \startsectionlevel[title=Chapter] Text. \startitemize[columns] \item A \item B \stopitemize \startitemize \item A \item B \stopitemize More Text. \stopsectionlevel \stoptext

2 1