[NTG-context] [Bug] Two-column text: Larger top spacing in inline images
Dear Hans and ConTeXt developers,
When you compile the following code with ConTeXt ver: 2021.10.28 10:19, you
will see that:
* in 1-column text the top spacing of the circle is normal,
* in 2-column text, the top spacing of the circle is too large.
Here is the link to the output PDF:
https://live.contextgarden.net/cgi-bin/result.cgi?id=7K5tLW
\def\example{%
Lorem ipsum. Lorem ipsum. Lorem ipsum.
Lorem ipsum. Lorem ipsum. Lorem ipsum.
Lorem ipsum. Lorem ipsum. Lorem ipsum.
Lorem ipsum. Lorem ipsum. Lorem ipsum.
Lorem ipsum. Lorem ipsum. Lorem ipsum.
Lorem ipsum. Lorem ipsum. Lorem ipsum.
\startMPcode draw fullcircle scaled 1cm; \stopMPcode\
Lorem ipsum. Lorem ipsum. Lorem ipsum.}
\starttext
\example
\startcolumns
\example
\stopcolumns
\stoptext
Best regards,
Marcin Ciura
___
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
___
Re: [NTG-context] not working "mtxrun --scripts cache --erase"
I’m afraid that I have just found out that "mtxrun --scripts cache --erase" doesn’t delete a single file from the cache. Could anyone confirm the issue? I can confirm that the same thing happens here. If I change line 81 of texmf-context/scripts/context/lua/mtx-cache.lua from if find(filename,"luatex%-cache") then to if find(filename,"luametatex%-cache") then the problem appears to be fixed. -- Max ___ 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 ___
Re: [NTG-context] Count (and limit) glyphs per line?
On 2022-06-26 9:59 a.m., Benjamin Buchmuller wrote:
Hi Max,
Thank you so much for your help and pointing me to the documents; always a lot
of things to learn in TeX!
No problem :)
I'm afraid that including the hyphen width doesn't solve the issue yet. It
seems to move the problem to other parts of the text.
Ah, too bad. My next step would have been to insert \penalty1's
(prevent breaks) at the potential breaks before/after the "selected"
break, but Hans provided a _much_ better solution that you should use
instead.
My guess is that one could equivalently have said "local max_length = 111",
right?
Not really; the hyphen is added to the accumulated width, not the
accumulated character count.
I made the following MWE (reproducible also online) to illustrate what I see:
My code assumes that each line has _roughly_ "max_length" characters
before it runs. These lines each only have ~60 characters, so I'm not
entirely surprised that there are issues. Just use Hans's solution,
which is much less of a total hack than this is :)
* Running with hsize only makes the problem worse in itemizations, so I think localhsize
is the way to go. My guess, localhsize is the width of the "text" part of a
paragraph, for example, excluding the symbols in the itemization.
I forgot about \leftskip. Replace "tex.hsize" with "tex.hsize -
tex.leftskip.width" and everything should work properly. Using
localhsize would also work, whenever it's non-zero.
I'm wondering if I do understand the second while loop correctly:
So how it works is the outer loop goes through each "node" in the
paragraph. If it is a glyph or glue, then we increment the character
counter by one and the width by the node's width.
If we have exceeded the maximum character count or maximum width, then
we switch directions and start going backwards through each node,
starting at the character that was too long. If one of the previous 5
characters is glue, then force a break there; otherwise, we force a
break at the nearest glue or hyphen.
Now we reset the width and character counters and return to the outer
loop, which continues until the end of the paragraph.
for disc we add hyphen.width, do we?)
Once we're trying to make a break, it's too late to add anything to the
width. Instead, I'm just adding the width of a hyphen unconditionally at
the very beginning. (Of course, this code actually has a bug: I add the
hyphen width at the very beginning, but then I reset the total width to
zero each loop. That's probably why this wasn't working before).
* The other cases still seem a bit obscure to me, and I tried to trace where
each of them might be triggered:
if n.id == glue_id then
local penalty = node.new "penalty"
penalty.penalty = -1
node.insertbefore(head, n, penalty)
context.inrightmargin("glue")
break
end
When going backwards, if we find any glue, break there, since breaking
at a space is always preferred to breaking at a hyphen.
if not end_disc and n.id == disc_id then
context.inrightmargin("disc")
end_disc = n
end
Save the location of the potential hyphen closest to the maximum length,
just in case we need it later.
if end_disc and back_chars >= 5 then
context.inrightmargin("end")
end_disc.penalty = -1
break
end
We've already went back 5 characters from the maximum length and we
haven't found any spaces to break at; if we have already found a
potential hyphen, let's force break there.
if n.id == glyph_id then
context.inrightmargin("glyph")
back_chars = back_chars + 1
end
Count how many characters we've went backwards by.
(Oh, and be really careful when using "context()" inside Lua engine
callbacks. If you had done something like "context.vbox('some text')",
you would have triggered the paragraph builder while inside the
paragraph builder, which could lead to an infinite loop)
I'm maybe doing this wrong, but I see these conditions triggered more often
than probably expected for a 25 line document?
Without running this code below, I'd guess that either "glue" or "end"
should trigger for every line, "disc" should come before whenever "end"
is triggered", and "glyph" is probably triggered about 3 times per line.
Many thanks again!
(self-promotion warning) If these Lua callbacks interest you, I use
quite a few of them in my "lua-widow-control"
Re: [NTG-context] Count (and limit) glyphs per line?
I completely agree, Hans, that such specifications are often made without a second thought on them. And Max is probably right that they originated from the typewriter area. In a sense these "challenges" can be at least somewhat educational. I've learnt---also thanks to Max's suggestions---a fair amount on LMTX. So, I'm looking forward to see how the "crappyspec" parbuilder will finally look like. Thank you very much for the demo, looks very impressive! Best Benjamin ___ 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 ___
Re: [NTG-context] Count (and limit) glyphs per line?
On 6/25/2022 10:25 PM, Benjamin Buchmuller via ntg-context wrote:
Dear list,
A brief follow-up for (1) itemizations [resolved; but question on ConTeXt hsize
defaults] and (2) hyphenation [troubles].
(1) To deal with itemizations and other situation where texts are indented such
as:
\setuppapersize[landscape,letter]
\showframe
\starttext
\samplefile{knuth}
\ctxlua{context(tex.dimen["textwidth"])} % 37213340
\ctxlua{context(tex.dimen["localhsize"])} % 0
\startitemize[width=5em]
\item \samplefile{knuth}
\ctxlua{context(tex.dimen["textwidth"])} % 37213340
\ctxlua{context(tex.dimen["localhsize"])} % 33283340
\stopitemize
\stoptext
The problem with these thing is that there is more involved than just
counting, like font features, hyphenation, current paragrph properties,
etc. and you don't want interference with other features. You also want
the paragraphs to look somewhat ok. Folks who enforce such demands on
authors never wonder where the tools do do that come from (publishers
and probably most designers are not interested in that anyway: thinking
probably stops at the number '120').
Attached a proof of concept that gives an idea. No upload as first we
need to do some wrapping up of math. Not that we needed something in the
engine other than the linebreak helper to accept direct modes (no need
to go back and forth then and i only want write this crap once). Could
be a module although it's only some 70 lines of code in the end. Maybe
it makes a nice (lmtx) demo for the ctx meeting too.
Here we work per paragraph not per line which looks better on the
average. One could mess with parshapes but why bother.
(The todo in the name refers to the fact that it might do into a th elow
level paragraph manual.)
(No more time now but we can add later; remind me if I forget.)
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
-
todo-paragraphs.pdf
Description: Adobe PDF document
___
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
___
[NTG-context] "mtxrun --scripts cache --erase" not working?
Dear list, as reported some months ago (https://mailman.ntg.nl/pipermail/ntg-context/2022/105420.html), "mtxrun --scripts cache --erase" doesn’t erase the cache at all. Could anyone confirm this issue (which I experience on both Linux64 and Win64)? Many thanks for your help, Pablo ___ 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 ___
Re: [NTG-context] Count (and limit) glyphs per line?
Hi Max,
Thank you so much for your help and pointing me to the documents; always a lot
of things to learn in TeX!
I'm afraid that including the hyphen width doesn't solve the issue yet. It
seems to move the problem to other parts of the text. My guess is that one
could equivalently have said "local max_length = 111", right?
I made the following MWE (reproducible also online) to illustrate what I see:
* Here, instead of a breaking point, the trouble is caused by not being able to
break it. This causes the next line to be underfull. (I get a lot of these, but
also some with hyphenated breakpoints, in my own document. Maybe the insertion
point of the penalty/breaking bonus needs to move up?)
* Running with hsize only makes the problem worse in itemizations, so I think
localhsize is the way to go. My guess, localhsize is the width of the "text"
part of a paragraph, for example, excluding the symbols in the itemization.
(More thoughts below)
\startluacode
local max_length = 112
local glyph_id = node.id "glyph"
local disc_id = node.id "disc"
local glue_id = node.id "glue"
function userdata.limiter(head)
head = language.hyphenate(head)
local hyphen = node.new "glyph"
hyphen.char = language.prehyphenchar(0)
hyphen.font = font.current()
local width = hyphen.width
node.free(hyphen)
local chars = 0
local n = head
while n do
if n.id == glyph_id or n.id == glue_id then
chars = chars + 1
width = width + n.width - (n.shrink or 0)
end
local localhsize = tex.dimen["textwidth"]
if tex.dimen["localhsize"] > 0 then
localhsize = tex.dimen["localhsize"]
end
if chars >= max_length or width > localhsize then
local back_chars = 0
local end_disc = nil
while n do
if n.id == glue_id then
local penalty = node.new "penalty"
penalty.penalty = -1
node.insertbefore(head, n, penalty)
break
end
if not end_disc and n.id == disc_id then
end_disc = n
end
if end_disc and back_chars >= 5 then
end_disc.penalty = -1
break
end
if n.id == glyph_id then
back_chars = back_chars + 1
end
n = n.prev
end
width = 0
chars = 0
end
n = n.next
end
return head
end
nodes.tasks.appendaction(
"processors",
"before",
"userdata.limiter"
)
\stopluacode
\setuppapersize[A5]
\showframe
\starttext
This is text width:
\ctxlua{context(tex.dimen["textwidth"])}
This is hsize:
\ctxlua{context(tex.dimen["hsize"])}
This is localhsize:
\ctxlua{context(tex.dimen["localhsize"])}
\startitemize[width=5em]
\item Thus, I came to the conclusion that the \hbox{designer} of a
new system must not only be the implementer and first large--scale user; the
de signer should also write the first user manual.
\item \samplefile{knuth}
This is text width:
\ctxlua{context(tex.dimen["textwidth"])}
This is hsize:
\ctxlua{context(tex.dimen["hsize"])}
This is localhsize:
\ctxlua{context(tex.dimen["localhsize"])}
\stopitemize
\stoptext
I'm wondering if I do understand the second while loop correctly:
* Once we find the node that exceeds either the character limit or the
(local-)hsize (glyphs and glues summed, for disc we add hyphen.width, do we?),
then we insert an incredibly good breaking point for a new line. And exit the
loop.
* The other cases still seem a bit obscure to me, and I tried to trace where
each of them might be triggered:
if n.id == glue_id then
local penalty = node.new "penalty"
penalty.penalty = -1
node.insertbefore(head, n, penalty)
context.inrightmargin("glue")
break
end
if not end_disc and n.id == disc_id then
Re: [NTG-context] Count (and limit) glyphs per line?
On 6/25/2022 5:38 PM, Benjamin Buchmuller via ntg-context wrote: Wow, that works like a charm! Thank you, Max! It's also a very insightful example of how to use and inject Lua code in the TeX output routine. Do you mind if I add it to the wiki? (Probably under "Wrapping".) I didn't check it but it's not the output routine one kicks code in, but likely some other spot. Be aware that messing around with node lists - can have a performance hit - can have interferences with other mechanisms - use the user callback hooks (before/after), not the system ones so: - i ignore complains about performance - i won't spent time on issues related to it so, when do do such thingsm best work with a 'frozen' install and check your stuff after an update: - play safe 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 - ___ 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 ___
