~thosgood
Sorry I forgot to follow up on this. In your example macro, part of hte problem is that
\startverb\tag{\x}\stopverb
is just going to produce the string\tag{\x}
(i.e. where\x
is not interpreted at all). The proper thing would be\startverb\tag\stopverb{\x}
. But there is another issue with the math renering that is causing this to come out as( x )
instead of(x)
. I'm working on it now.
Comment by ~thosgood on ~jonsterling/forester
This works perfectly, thank you so much!
~thosgood We don't yet have description lists, but I think that description lists aren't the solution to this problem. Having a glance at the documentation (https://developer.mozilla.org/en-US/docs/Web/HTML/Element/dl) and it looks like this is not an appropriate structure.
Let me spend a little time experimenting to see if I can come up with a reasonable approach.
Comment by ~thosgood on ~jonsterling/forester
Just changing the automatic numbering can be done by setting
list-style-type
(e.g. tolower-alpha
) in the CSS. As for manual numbering, I think that the best way to do this might be via a description list, if that sounds "semantically sensible"? It would need some CSS tweaking to make it look like an ordered list.Does Forester already support description lists?
~thosgood, thanks very much for these concrete proposals! Something like what you describe might be better than what we are doing right now. I have to think about it a little bit, because I also need to have a good answer for what the "auto-titled" links should be (e.g. those you write as
[[xxx-NNNN]]
).
Comment by ~thosgood on ~jonsterling/forester
Ah, I see. Here's my first suggestion for how the title could render, though I'm not sure it's definitely good. At the moment, if I'm not mistaken, the rendering is of the form
[self.taxon] [self.number] ... > [parent.parent.title] > [parent.title] > [self.title]
I think what could make sense, for both untitled and titled trees (with parents), is to have
... > [parent.parent.title] > [parent.title] [self.taxon] [self.number] [self.title]
This way, both of the links that I posted (I.5.5 and I.5.6) would have "SGA 1: Étale covers and the fundamental group › Étale morphisms › Fundamental property of étale morphisms" as their titles, followed by Theorem I.5.5/Corollary I.5.6, and with the latter then being followed by its title ("Extensions of liftings").
But yeah, this would be the desirable rendering for me, but I have no idea how it would affect everybody else!
Comment by ~thosgood on ~jonsterling/forester
amazing, thanks!
Comment by ~thosgood on ~jonsterling/forester
This seems like a sensible solution, but it would be convenient to have a macro at least that allows one to simply write the emitted-tree "inline", e.g.
\p{Blach blah blah.\footnote[xxx-NNNN]{This is the content of the footnote}}
where, as for subtrees, the
[xxx-NNNN]
is optional.
Ticket created by ~thosgood on ~jonsterling/forester
Some trees that transclude a lot of other trees will have very long "Backlinks"/"Related" sections at the end, to the point where they become a bit less useful (e.g. SGA 1 has a lot of backlinks that come from just sections pointing to themselves). It would be nice to be able to set these to not appear on a per-tree basis if possible.