Hi, ConTeXt initializes the \belowdisplayshortskip to zero point. I believe this is wrong, it should be equal to \belowdisplayskip: the fact that the line above the display is short shouldnt affect the typesetting that follows the display. For the moment, I've fixed it by: \everydisplay {\belowdisplayshortskip=\belowdisplayskip } Taco
Taco Hoekwater wrote:
Hi,
ConTeXt initializes the \belowdisplayshortskip to zero point. I believe this is wrong, it should be equal to \belowdisplayskip: the fact that the line above the display is short shouldnt affect the typesetting that follows the display.
For the moment, I've fixed it by:
\everydisplay {\belowdisplayshortskip=\belowdisplayskip }
hm, dangerous fix since \startformula ... \stopformula work together with snapping and blanks Hans
Hans Hagen wrote:
Taco Hoekwater wrote:
Hi,
ConTeXt initializes the \belowdisplayshortskip to zero point. I believe this is wrong, it should be equal to \belowdisplayskip: the fact that the line above the display is short shouldnt affect the typesetting that follows the display.
For the moment, I've fixed it by:
\everydisplay {\belowdisplayshortskip=\belowdisplayskip }
hm, dangerous fix since \startformula ... \stopformula work together with snapping and blanks
I know it is dangerous, but my document uses $$ .. $$ and it really needs to have a reliable value in \belowdisplayshortskip. If it cannot be fixed in core, than we have to write something in the wiki. Taco
Taco Hoekwater wrote:
Hans Hagen wrote:
Taco Hoekwater wrote:
Hi,
ConTeXt initializes the \belowdisplayshortskip to zero point. I believe this is wrong, it should be equal to \belowdisplayskip: the fact that the line above the display is short shouldnt affect the typesetting that follows the display.
For the moment, I've fixed it by:
\everydisplay {\belowdisplayshortskip=\belowdisplayskip }
hm, dangerous fix since \startformula ... \stopformula work together with snapping and blanks
I know it is dangerous, but my document uses $$ .. $$ and it really needs to have a reliable value in \belowdisplayshortskip. If it cannot be fixed in core, than we have to write something in the wiki.
an option is to limit the settings to the start..stop only btw, can you hack a proper 'lastlinewidth' in pdftex? one that is available always (not only when a display is entered inside a par) Hans
Hans Hagen wrote:
Taco Hoekwater wrote:
an option is to limit the settings to the start..stop only
btw, can you hack a proper 'lastlinewidth' in pdftex? one that is available always (not only when a display is entered inside a par)
Ok, It is not too hard, the trick is in (mostly) getting the pascal web mechanics right. End of this week, ok? Taco
Taco Hoekwater wrote:
Hans Hagen wrote:
Taco Hoekwater wrote:
an option is to limit the settings to the start..stop only
btw, can you hack a proper 'lastlinewidth' in pdftex? one that is available always (not only when a display is entered inside a par)
Ok, It is not too hard, the trick is in (mostly) getting the pascal web mechanics right. End of this week, ok?
sure, Hans
participants (2)
-
Hans Hagen -
Taco Hoekwater