description lists and URLs

19 views
Skip to first unread message

kcri...@gmail.com

unread,
Mar 2, 2023, 4:49:45 PM3/2/23
to PreTeXt support
Hi:  I note with some interest (and some trepidation) the new-ish behavior of putting footnotes for every web link in PTX.  Here is a question about that which arose from a PTX demo I gave today.

While demonstrating a live compilation (using "pretext build print" for the first time in front of other people, hooray!) of a pdf from a sample document, I noticed that in description lists, the footnotes appear directly under the non-title portion of the description list item.  This is not the case for URLs from <url> elements in unordered lists (and hence, I presume, for ordered lists, though I didn't try that).

Is that intended behavior?  Or not?  I honestly could imagine either way.  I see in pretext-latex that "\NewDocumentEnvironment{dlimedium}" uses a tcolorbox, and somewhere the documentation says that certain LaTeX environments are the reason certain environments postpone their footnotes until they are done, possibly several pages later, so it seems quite likely that is related.  But I don't know if it's *intended*, so I thought I'd ask.

Rob Beezer

unread,
Mar 3, 2023, 12:21:02 PM3/3/23
to pretext...@googlegroups.com
(Sent yesterday, but never made it out.)

On 3/2/23 13:49, kcri...@gmail.com wrote:
> Hi:  I note with some interest (and some trepidation) the new-ish behavior of
> putting footnotes for every web link in PTX.

I don't think that is accurate. First, this happens only with a "url" element
where you have provided content (text for the clickable). How does the
(printed) PDF reader even know there is a link, and where does it go? Second,
if you say @visual="foo.html" then you can get a less-ugly URL in the footnote.
Third, if you say @visual="" there will not be a footnote.

That should all be documented (I haven't checked). If it needs improvement,
then a PR would be most welcome. Try searching on "visual", maybe?

> While demonstrating a live compilation (using "pretext build print" for the
> first time in front of other people, hooray!) of a pdf from a sample document, I
> noticed that in description lists, the footnotes appear directly under the
> non-title portion of the description list item.  This is not the case for URLs
> from <url> elements in unordered lists (and hence, I presume, for ordered lists,
> though I didn't try that).

That does sound like an oversight with the use of a "tcolorbox".

Rob

Rob Beezer

unread,
Mar 3, 2023, 12:30:14 PM3/3/23
to pretext...@googlegroups.com
Thanks, KDC. That was a bad one. I'd seen these scroll by in the PDF of the
Guide, but I was always doing something else. There were 8 of them there. :-(
Very unprofessional. I suspect they popped up with the automatic "url"
footnotes, just like for you.

Anyway, all fixed now. Updating the Guide on the website just now - don't want
that hanging around in its prior state!

Rob


On 3/2/23 13:49, kcri...@gmail.com wrote:
> --
> You received this message because you are subscribed to the Google Groups
> "PreTeXt support" group.
> To unsubscribe from this group and stop receiving emails from it, send an email
> to pretext-suppo...@googlegroups.com
> <mailto:pretext-suppo...@googlegroups.com>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/pretext-support/606f74ce-ba1a-4933-87c9-3a7ea668de99n%40googlegroups.com <https://groups.google.com/d/msgid/pretext-support/606f74ce-ba1a-4933-87c9-3a7ea668de99n%40googlegroups.com?utm_medium=email&utm_source=footer>.

kcri...@gmail.com

unread,
Mar 4, 2023, 11:41:00 AM3/4/23
to PreTeXt support
> Hi:  I note with some interest (and some trepidation) the new-ish behavior of
> putting footnotes for every web link in PTX.

I don't think that is accurate. First, this happens only with a "url" element
where you have provided content (text for the clickable).

That makes sense; I've never tried doing it without providing content!  Yes, the rest is documented, the only issue was having the footnote versus not having it.

That does sound like an oversight with the use of a "tcolorbox".

Glad it wasn't too hard to fix!   If the people who were at the presentation follow up, I can emphasize that great open source development flow :) though in this case I was mainly talking about capabilities.
Reply all
Reply to author
Forward
0 new messages