wion

From [Phil a while back](https://github.com/textpattern/textpattern/issues/308#issuecomment-315812385): >I’d like to see how this matures first though. The whole thing seemed a bit clunky as a direct comments replacement - having to jump...

I guess that's it. Not having a web form limits the communication to only those playing along with the standard, but that's good in my opinion. We live in different...

I just stack them.`[1][2][3]` Then use CSS to give a little room between them. Works fine. But to deal with the lack of comma, I style the `sup > a`...

Don’t know what the state of callbacks is these days but a more dynamic Handling of ToCs would be sweet, so it wasn’t so tedious to edit a static one...

Just remembered there's the **soo_toc** plugin for Txp, and it works perfectly with only minor extra fuss to ensure id selectors are in headers. I'm happy.

Btw, I've been choosing to use notes only up to now and combine full biblio graphic references with any note comment per notes item, [for example](https://fullpoint.wion.com/desiderata#enotes), but I'm finding there...

I guess the first thing to ask is whether it's really necessary to use a list on a bibliography at all. Not needing to would make this moot for me...

If that’s possible, it would work nicely. In the case of a biblio, always the last section, the closing `p.` might not be an issue anyway. I don’t know if...

Yes, the presentation is easy, as my example given earlier (second post) might suggest. What I’m referring to here, and admittedly wasn’t clear about, is spacing used in the editor...

Bloke, thanks for the clarification. Seems like a good situation no matter how you slice it.