Ahoi, there were a few strange changes in ConTeXt rendering since about since mid-August, probably all related to box handling. I recognized \framed inserts some additional space when I re-typeset some sheets of labels that suddenly didn’t fit the labels any more. Today my editor in chief asked me where the pagination of our magazine went to – I guess its footer box became too small, couldn’t investigate yet. He didn’t see that the type on the back is askew, probably also from the additional space around a \framed Such sudden changes are really frustrating and might cost me a lot of money (the magazine is already printed and distributed). I’ll try to come up with a MWE. Greetlings, Hraban --- https://www.fiee.net http://wiki.contextgarden.net https://www.dreiviertelhaus.de GPG Key ID 1C9B22FD
If I just typeset frames, they get 1pt of space inbetween:
\starttext
\dorecurse{20}{%
%\vskip-1pt% to avoid space
\framed[width=10cm,height=1cm]{\ConTeXt}%
}
\stoptext
I’m not quite sure if that shows the real problem and if that really was tight before.
With my tiny labels I had to \vskip-2.365mm to make them fit again.
There the font size was set to 7.5pt and the baselineskip to 2ex.
But these settings didn’t change the 1pt between frames.
The difference it probably due to the labels consisting of nested \frameds with images.
Greetlings, Hraban
---
https://www.fiee.net
http://wiki.contextgarden.net
https://www.dreiviertelhaus.de
GPG Key ID 1C9B22FD
Am 2018-10-28 um 20:01 schrieb Henning Hraban Ramm
Ahoi,
there were a few strange changes in ConTeXt rendering since about since mid-August, probably all related to box handling.
I recognized \framed inserts some additional space when I re-typeset some sheets of labels that suddenly didn’t fit the labels any more.
Today my editor in chief asked me where the pagination of our magazine went to – I guess its footer box became too small, couldn’t investigate yet. He didn’t see that the type on the back is askew, probably also from the additional space around a \framed
Such sudden changes are really frustrating and might cost me a lot of money (the magazine is already printed and distributed).
I’ll try to come up with a MWE.
Greetlings, Hraban --- https://www.fiee.net http://wiki.contextgarden.net https://www.dreiviertelhaus.de GPG Key ID 1C9B22FD
___________________________________________________________________________________ If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___________________________________________________________________________________
Am 28.10.18 um 20:37 schrieb Henning Hraban Ramm:
If I just typeset frames, they get 1pt of space inbetween:
\starttext
\offinterlineskip
\dorecurse{20}{% %\vskip-1pt% to avoid space \framed[width=10cm,height=1cm]{\ConTeXt}% } \stoptext
Herbert
I’m not quite sure if that shows the real problem and if that really was tight before.
With my tiny labels I had to \vskip-2.365mm to make them fit again. There the font size was set to 7.5pt and the baselineskip to 2ex. But these settings didn’t change the 1pt between frames. The difference it probably due to the labels consisting of nested \frameds with images.
Greetlings, Hraban --- https://www.fiee.net http://wiki.contextgarden.net https://www.dreiviertelhaus.de GPG Key ID 1C9B22FD
Am 2018-10-28 um 20:01 schrieb Henning Hraban Ramm
: Ahoi,
there were a few strange changes in ConTeXt rendering since about since mid-August, probably all related to box handling.
I recognized \framed inserts some additional space when I re-typeset some sheets of labels that suddenly didn’t fit the labels any more.
Today my editor in chief asked me where the pagination of our magazine went to – I guess its footer box became too small, couldn’t investigate yet. He didn’t see that the type on the back is askew, probably also from the additional space around a \framed
Such sudden changes are really frustrating and might cost me a lot of money (the magazine is already printed and distributed).
I’ll try to come up with a MWE.
Greetlings, Hraban --- https://www.fiee.net http://wiki.contextgarden.net https://www.dreiviertelhaus.de GPG Key ID 1C9B22FD
___________________________________________________________________________________ If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___________________________________________________________________________________
___________________________________________________________________________________ If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___________________________________________________________________________________
Am 2018-10-28 um 20:49 schrieb Herbert Voss
Am 28.10.18 um 20:37 schrieb Henning Hraban Ramm:
If I just typeset frames, they get 1pt of space inbetween: \starttext
\offinterlineskip
\dorecurse{20}{% %\vskip-1pt% to avoid space \framed[width=10cm,height=1cm]{\ConTeXt}% } \stoptext
Herbert
Thank you, that works in this case. But it doesn’t help with my labels. And why did it work without \offinterlineskip before? See attachment - it’s right if the labels fit one page. At the moment I need a negative vskip of 5pt. Greetlings, Hraban --- https://www.fiee.net http://wiki.contextgarden.net https://www.dreiviertelhaus.de GPG Key ID 1C9B22FD
Am 29.10.18 um 16:13 schrieb Henning Hraban Ramm:
But it doesn’t help with my labels.
you have a \setupinterlinespace[2ex] so \offinterlinespace has no real meaning here. Try it without and \setupinterlinespace[0.1pt]
And why did it work without \offinterlineskip before?
No idea ... Herbert, hope that I understand your problem well
Am 2018-10-29 um 16:47 schrieb Herbert Voss
Am 29.10.18 um 16:13 schrieb Henning Hraban Ramm:
But it doesn’t help with my labels.
you have a
\setupinterlinespace[2ex]
so \offinterlinespace has no real meaning here. Try it without and
\setupinterlinespace[0.1pt]
And why did it work without \offinterlineskip before?
No idea ...
Herbert, hope that I understand your problem well
So, \offinterlineskip disables the interline skip completely? Then I can’t use it where there’s text involved. I already tried without \setupinterlinespace, no change. Greetlings, Hraban --- https://www.fiee.net http://wiki.contextgarden.net https://www.dreiviertelhaus.de GPG Key ID 1C9B22FD
So, \offinterlineskip disables the interline skip completely?
Indeed, it is just plain TeX. In order to inhibit the interline glue in front of the next line only, use \nointerlineskip. dr. Hans van der Meer
On 30 Oct 2018, at 14:08, Henning Hraban Ramm
wrote: Am 2018-10-29 um 16:47 schrieb Herbert Voss
: Am 29.10.18 um 16:13 schrieb Henning Hraban Ramm:
But it doesn’t help with my labels.
you have a
\setupinterlinespace[2ex]
so \offinterlinespace has no real meaning here. Try it without and
\setupinterlinespace[0.1pt]
And why did it work without \offinterlineskip before?
No idea ...
Herbert, hope that I understand your problem well
I already tried without \setupinterlinespace, no change.
Greetlings, Hraban --- https://www.fiee.net http://wiki.contextgarden.net https://www.dreiviertelhaus.de GPG Key ID 1C9B22FD
___________________________________________________________________________________ If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___________________________________________________________________________________
In the last days I recognized that some of my ConTeXt projects behave differently WRT spacing, not only with \framed, but also with heads - everywhere there’s more space induced than before. The attached screenshot shows an example of before and after. The headings are set up like \setuphead[section,subject][page=no, before={\testpage[7]\blank},after=, previousnumber=no, sectionsegments=section] \setuphead[subsection,subsubject][style={\bf}, before={\testpage[7]\blank[small]},after=, sectionsegments=section:subsection] "1 Aufnahme" is a section, "1.1" is a subsection; I always use the start/stop version. To get back to the old behaviour, I need to replace the \blank commands with a negative vskip of font size! And then there’s still space inserted if the heading starts at the top of a column. I tried to come up with a MWE – headingspacetest.tex shows at least that there’s always space inserted before section headers. It might be related to some font handling, since the spacing changes affect different "things" in different projects – frames with my label stickers and on my magazine covers, headings like here. Or maybe the changes are unrelated. This change happened between ConTeXt versions 2018.07.27 and 2018.09.01. I didn’t change my code. Unfortunately there are no older versions of ConTeXt to go back to any more. Greetlings, Hraban --- https://www.fiee.net http://wiki.contextgarden.net https://www.dreiviertelhaus.de GPG Key ID 1C9B22FD
The columns environment uses now the newer mixedcolumns mechanism which is the reason for the differences in your document. To use the older columns mechanism add \usemodule[old-multicolumns] to your document. Wolfgang Henning Hraban Ramm schrieb am 07.11.18 um 22:53:
In the last days I recognized that some of my ConTeXt projects behave differently WRT spacing, not only with \framed, but also with heads - everywhere there’s more space induced than before. The attached screenshot shows an example of before and after.
The headings are set up like
\setuphead[section,subject][page=no, before={\testpage[7]\blank},after=, previousnumber=no, sectionsegments=section] \setuphead[subsection,subsubject][style={\bf}, before={\testpage[7]\blank[small]},after=, sectionsegments=section:subsection]
"1 Aufnahme" is a section, "1.1" is a subsection; I always use the start/stop version.
To get back to the old behaviour, I need to replace the \blank commands with a negative vskip of font size! And then there’s still space inserted if the heading starts at the top of a column.
I tried to come up with a MWE – headingspacetest.tex shows at least that there’s always space inserted before section headers.
It might be related to some font handling, since the spacing changes affect different "things" in different projects – frames with my label stickers and on my magazine covers, headings like here. Or maybe the changes are unrelated.
This change happened between ConTeXt versions 2018.07.27 and 2018.09.01. I didn’t change my code.
Unfortunately there are no older versions of ConTeXt to go back to any more.
Greetlings, Hraban --- https://www.fiee.net http://wiki.contextgarden.net https://www.dreiviertelhaus.de GPG Key ID 1C9B22FD
___________________________________________________________________________________ If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___________________________________________________________________________________
Thank you, I only tried \usemodule[old-columnsets] before.
It’s really annoying if ConTeXt proves unreliable time and again.
I’m trying to replace InDesign in my workflows as often as possible, but if I need to check and rework my environments with every other beta, it’s no fun and costs a lot of time.
Greetlings, Hraban
---
https://www.fiee.net
http://wiki.contextgarden.net
https://www.dreiviertelhaus.de
GPG Key ID 1C9B22FD
Am 2018-11-08 um 18:32 schrieb Wolfgang Schuster
The columns environment uses now the newer mixedcolumns mechanism which is the reason for the differences in your document.
To use the older columns mechanism add \usemodule[old-multicolumns] to your document.
Wolfgang
Henning Hraban Ramm schrieb am 07.11.18 um 22:53:
In the last days I recognized that some of my ConTeXt projects behave differently WRT spacing, not only with \framed, but also with heads - everywhere there’s more space induced than before. The attached screenshot shows an example of before and after.
The headings are set up like
\setuphead[section,subject][page=no, before={\testpage[7]\blank},after=, previousnumber=no, sectionsegments=section] \setuphead[subsection,subsubject][style={\bf}, before={\testpage[7]\blank[small]},after=, sectionsegments=section:subsection]
"1 Aufnahme" is a section, "1.1" is a subsection; I always use the start/stop version.
To get back to the old behaviour, I need to replace the \blank commands with a negative vskip of font size! And then there’s still space inserted if the heading starts at the top of a column.
I tried to come up with a MWE – headingspacetest.tex shows at least that there’s always space inserted before section headers.
It might be related to some font handling, since the spacing changes affect different "things" in different projects – frames with my label stickers and on my magazine covers, headings like here. Or maybe the changes are unrelated.
This change happened between ConTeXt versions 2018.07.27 and 2018.09.01. I didn’t change my code.
Unfortunately there are no older versions of ConTeXt to go back to any more.
On 9/11/18 11:41 AM, Henning Hraban Ramm wrote:
Thank you, I only tried \usemodule[old-columnsets] before.
It’s really annoying if ConTeXt proves unreliable time and again. I’m trying to replace InDesign in my workflows as often as possible, but if I need to check and rework my environments with every other beta, it’s no fun and costs a lot of time.
Clearly you haven't understood the meaning of “beta”. If you don't want your documents to break, don't update.
Greetlings, Hraban --- https://www.fiee.net http://wiki.contextgarden.net https://www.dreiviertelhaus.de GPG Key ID 1C9B22FD
Am 2018-11-08 um 18:32 schrieb Wolfgang Schuster
: The columns environment uses now the newer mixedcolumns mechanism which is the reason for the differences in your document.
To use the older columns mechanism add \usemodule[old-multicolumns] to your document.
Wolfgang
Henning Hraban Ramm schrieb am 07.11.18 um 22:53:
In the last days I recognized that some of my ConTeXt projects behave differently WRT spacing, not only with \framed, but also with heads - everywhere there’s more space induced than before. The attached screenshot shows an example of before and after.
The headings are set up like
\setuphead[section,subject][page=no, before={\testpage[7]\blank},after=, previousnumber=no, sectionsegments=section] \setuphead[subsection,subsubject][style={\bf}, before={\testpage[7]\blank[small]},after=, sectionsegments=section:subsection]
"1 Aufnahme" is a section, "1.1" is a subsection; I always use the start/stop version.
To get back to the old behaviour, I need to replace the \blank commands with a negative vskip of font size! And then there’s still space inserted if the heading starts at the top of a column.
I tried to come up with a MWE – headingspacetest.tex shows at least that there’s always space inserted before section headers.
It might be related to some font handling, since the spacing changes affect different "things" in different projects – frames with my label stickers and on my magazine covers, headings like here. Or maybe the changes are unrelated.
This change happened between ConTeXt versions 2018.07.27 and 2018.09.01. I didn’t change my code.
Unfortunately there are no older versions of ConTeXt to go back to any more.
___________________________________________________________________________________ If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___________________________________________________________________________________
On 11/9/2018 1:50 PM, Clyde Johnston wrote:
Clearly you haven't understood the meaning of “beta”. If you don't want your documents to break, don't update.
Does ConTeXt have an LTS (long-term stable) release?
just save your tree (or multiple) Hans -- ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl -----------------------------------------------------------------
Am 2018-11-08 um 23:51 schrieb Henri Menke
Clearly you haven't understood the meaning of “beta”.
Thank you for educating me.
If you don't want your documents to break, don't update.
Since when? I started using ConTeXt in 1999 and don’t expect my MkII code to work any more. I’m still kind of an evangelist for ConTeXt, but that doesn’t protect me from getting very frustrated at times. It seems to me that the replacement of the column layout code was premature, when it breaks heading setup, frame handling and can’t handle columns that don’t start at the top of a page. Greetlings, Hraban --- https://www.fiee.net http://wiki.contextgarden.net https://www.dreiviertelhaus.de GPG Key ID 1C9B22FD
Hi,
I solve the same problem for ages... I decided for fixed time points related
with new edition of TeXlive.
Advantages:
TeXlive versions (from my point of view) are most stable.
You really can compile your files repeatedly getting the same result.
Disadvantages:
You have to store all TeXlive editions.
All TeXlive editions are space demanding.
You have make notes on your files/projects which version was used.
You cannot use new features if you are going to refresh the project.
This is my way but maybe there is something better.
[I work ConTeXt since 2010 and only with MkIV.]
Best wishes,
Tomas
Fri, Nov 09, 2018 ve 02:40:30PM +0100 Henning Hraban Ramm napsal(a):
# Am 2018-11-08 um 23:51 schrieb Henri Menke
On Fri, 9 Nov 2018 15:05:59 +0100
Tomas Hala
I solve the same problem for ages... I decided for fixed time points
If it may be useful: I keep a very short-term backup so that when things "break" or change, I can easily backtrack to a working copy. I update using the following shell script: #!/bin/sh CONTEXTHOME=${HOME}/context if [ ! -d ${CONTEXTHOME}/beta ] ; then mkdir -p ${CONTEXTHOME}/beta fi if [ ! -d ${CONTEXTHOME}/previous ] ; then mkdir -p ${CONTEXTHOME}/previous fi cd ${CONTEXTHOME}/beta echo "*** move current to previous ***" rsync -av --delete --progress . ../previous echo "*** update beta ***" rsync -ptv --progress rsync://contextgarden.net/minimals/setup/first-setup.sh . 2>&1 | tee first-setup.log ./first-setup.sh --modules=all --fonts=all --engine=luatex 2>&1 | tee -a first-setup.log This will not help against any undetected changes that may go unnoticed for a while between different projects, but does protect me against immediate "bugs". Hans has suggested keeping a ConTeXt standalone copy in each separate project file, as it is small enough that such duplication does not take up too much space. (As we strip-down the distribution and as storage space becomes bigger and bigger, this should not be a problem.) The advantage of having a copy associated with a project is that one can come back, years later even, and produce *exactly* the same output. Alan
Hello Henning,
I go similar way as Alan does - I'm updating ConTeXt (usually) once a week while keeping backups of the previous versions.
My experience is that cca once a year I'm forced to get back to a previous Ctx copy as something stops working (IIRC, there some issues with switching to Lua 5.2 and now to Lua 5.3, an issue with Lua sorting alg which probably added a sortaity check at a point, a TickZ issue - all has been passed successfully over time (.dll rebuild with upper Lua releases, my fault in sorting alg, ...)), but some time later I "boarded" back to the "train-of-ConTeXt-beta-releases".
I'm working on Windows (W7 and WX) - so for the case you were interested, I'm attaching some batches to save & update ConTeXt beta (call ReNew.bat from your Ctx installation direcory (d:\Ctx-Beta in my case); and also you need to have 7z installed which is used to zip the latest ConTeXt installation before update; .ba_ to be renamed to .bat).
Best regards,
Lukas
On Fri, 09 Nov 2018 16:23:55 +0100, Alan Braslau
On Fri, 9 Nov 2018 15:05:59 +0100 Tomas Hala
wrote: I solve the same problem for ages... I decided for fixed time points
If it may be useful: I keep a very short-term backup so that when things "break" or change, I can easily backtrack to a working copy. I update using the following shell script:
#!/bin/sh CONTEXTHOME=${HOME}/context if [ ! -d ${CONTEXTHOME}/beta ] ; then mkdir -p ${CONTEXTHOME}/beta fi if [ ! -d ${CONTEXTHOME}/previous ] ; then mkdir -p ${CONTEXTHOME}/previous fi cd ${CONTEXTHOME}/beta echo "*** move current to previous ***" rsync -av --delete --progress . ../previous echo "*** update beta ***" rsync -ptv --progress rsync://contextgarden.net/minimals/setup/first-setup.sh . 2>&1 | tee first-setup.log
./first-setup.sh --modules=all --fonts=all --engine=luatex 2>&1 | tee -a first-setup.log
This will not help against any undetected changes that may go unnoticed for a while between different projects, but does protect me against immediate "bugs".
Hans has suggested keeping a ConTeXt standalone copy in each separate project file, as it is small enough that such duplication does not take up too much space. (As we strip-down the distribution and as storage space becomes bigger and bigger, this should not be a problem.) The advantage of having a copy associated with a project is that one can come back, years later even, and produce *exactly* the same output.
Alan
-- Ing. Lukáš Procházka | mailto:LPr@pontex.cz Pontex s. r. o. | mailto:pontex@pontex.cz | http://www.pontex.cz | IDDS:nrpt3sn Bezová 1658 147 14 Praha 4 Mob.: +420 702 033 396
On 11/9/2018 2:40 PM, Henning Hraban Ramm wrote: > Am 2018-11-08 um 23:51 schrieb Henri Menke: > >> Clearly you haven't understood the meaning of “beta”. > > Thank you for educating me. > >> If you don't want your documents to break, don't update. > > Since when? > I started using ConTeXt in 1999 and don’t expect my MkII code to work any more. > I’m still kind of an evangelist for ConTeXt, but that doesn’t protect me from getting very frustrated at times. > > It seems to me that the replacement of the column layout code was premature, when it breaks heading setup, frame handling and can’t handle columns that don’t start at the top of a page. - the new columnset code has been around for a while now and has become default ... the old code is a module - the new mixed column code has been around for even longer (and always was default on my machine) btu the old code is available as module both old mechanism were only partially adapted to mkiv and i bet that there were side effects - the new page columns mode is the way to go for columns with floats etc so we have three mkiv column models and two old ones available as modules (i expect them to keep working more or less ok but nothing will be changed in them) Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl -----------------------------------------------------------------
Hans Hagen schrieb am 09.11.18 um 17:01:
- the new mixed column code has been around for even longer (and always was default on my machine) btu the old code is available as module
A big difference between the old columns environment and the new mixed columns code is that the new environment uses grid snapping by default which can result in blank lines in the output. Below is a simplified version of Henning problems which produces an blank line when you use bold text. \showboxes \starttext \startcolumns[balance=no] \snaptogrid[]\hbox{\setstrut\begstrut Ward\endstrut} \samplefile{ward} \snaptogrid[]\hbox{\bf\setstrut\begstrut Ward\endstrut} \samplefile{ward} \stopcolumns \stoptext Two simple ways to get rid of the blank line are 1. to disable the strut for the section or 2. to disable the grid snapping for the section. \showboxes \setuphead[section][before=,after=] \setuphead[section][style=bold] \define[1]\Sample {\begingroup \setuphead[section][#1] \section{Ward \doifsomething{#1}{\tttf [#1]}} \samplefile{ward}\par \endgroup} \starttext \startcolumns[balance=no] \Sample{} \Sample{style=} \Sample{strut=no} \Sample{grid=no} \stopcolumns \stoptext Wolfgang
participants (10)
-
Alan Braslau
-
Clyde Johnston
-
Hans Hagen
-
Hans van der Meer
-
Henning Hraban Ramm
-
Henri Menke
-
Herbert Voss
-
Procházka Lukáš Ing.
-
Tomas Hala
-
Wolfgang Schuster