🏠Activity stream

• so.nwalsh.com, 15 Dec 2025 at 09:33:33

  Sneak peek. I’ve put up a preview of what I’m thinking about for a rebooted exproc.org website. https://so.nwalsh.com/2025/12/15-exproc

• docbook/xslTNG #680 created, 11 Dec 2025 at 22:37:42

  Formatting article titles in bibliography?

  I'm attempting to tag and generate a bibliography in which article titles are enclosed in quotation marks and not italicized. I'd prefer not to have to customize the XSLT, but customizing the CSS (with a user-supplied stylesheet that I can address from the appropriate parameter) feels more portable (among other things, because I'm already using such a stylesheet for other purposes).

  Raw markup doesn't seem up to the task. With cooked markup I can enter the quotation marks (or use a <quote> element) myself, so that part of the issue has a fix of sorts. But if I tag the article title as <citetitle>, with or without a @pubwork value of "article", it always comes out in italics. When I look at the generated HTML I see <cite class="citetitle"> for both the article title and the title of the journal (also tagged as <citetitle>), which is to say that it looks to me as if anything tagged as <citetitle> will be italicized and there isn't a convenient hook into @pubwork or anything else for formatting article titles and journal titles differently.

  I can work around the problem by not tagging the article title at all, but since it is semantically a cited title, that feels wrong. Should I hold my nose and leave it untagged anyway? Or should xslTNG be adjusted to format <citetitle> in a way that is sensitive to the value of @pubwork?

• docbook/xslTNG #679 created, 11 Dec 2025 at 22:04:08

  Best practices and suggested usage of mathphrase

  mathphrase is officially described as intended for simple math expressions, though the config option for supporting mathphrase, and some discussions I have seen, may suggest using mathphrase for involved expressions.

  Please consider documenting suggested usage for authors of documents containing complex math expressions, such as those found in a typical formal research article.

• docbook/xslTNG #678 created, 10 Dec 2025 at 10:06:48

  Role on bridgehead doesn't copy the value to the HTML class

• so.nwalsh.com, 8 Dec 2025 at 19:30:10

  Follow up to pictures of pints post, a new-to-me flavo(u)rs of crisps post: Masala Chicken. Spicy, tasty, maybe a little generic.

  
• xmlresolver/xmlresolver #266 closed, 8 Dec 2025 at 17:02:52

  Simplify how logging is configured?

• xmlresolver/xmlresolver #267 merged, 8 Dec 2025 at 17:02:51

  Large refactor of logging to simplify it

• xmlresolver/xmlresolver #267 created, 8 Dec 2025 at 16:47:57

  Large refactor of logging to simplify it

  Fix #266

  The notion of a default level and different levels for different categories of output has all been discarded. There’s just a log level. Warning and error messages are the same. All of the other categorized messages are now just debug level.

  There’s an intertwingled fix here to avoid outputing error messages when attempting to parse catalogs in zip files.

• so.nwalsh.com, 8 Dec 2025 at 10:20:43

  More accurate locations. When it all goes wrong, can I tell you where? https://so.nwalsh.com/2025/12/08-locations

• so.nwalsh.com, 7 Dec 2025 at 16:33:22

  Arkell’s Ale. It’s been a while since I did a #picturesofpints post. This one from last week is a Swindon local, I believe.

  
• xmlresolver/xmlresolver #266 created, 5 Dec 2025 at 16:39:03

  Simplify how logging is configured?

  At the moment, there's a notion of a default logging level, to control what messages are output from the logger (for example, when you're using the default logger and not relying on java.util.logging.Logger to do the presentation).

  Behind the scenes there's some (poorly or perhaps incorrectly) documented attempts to allow for finer grained choices: "config" messages at this level, "request" messages at that level, "response" messages at some other level.

  No doubt, I thought this was useful once. But now it looks like a whole lot of extra complexity for a barely measurable amount of value.

• xmlresolver/xmlresolver #260 closed, 5 Dec 2025 at 14:35:52

  Reopening an issue #174

• xmlresolver/xmlresolver #265 merged, 5 Dec 2025 at 14:35:51

  Flesh out the adapter unit tests

• xmlresolver/xmlresolver #241 closed, 5 Dec 2025 at 14:34:24

  ResolverConstants are unnecessarily divergent

• xmlresolver/xmlresolver #265 created, 5 Dec 2025 at 14:30:35

  Flesh out the adapter unit tests

  Fix #260

• photos.nwalsh.com, 5 Dec 2025 at 12:10:21
  

  Masala chicken crisps
• xmlresolver/xmlresolver #261 closed, 3 Dec 2025 at 10:49:21

  Add test templates for SAX adapters

• xmlresolver/xmlresolver #264 merged, 3 Dec 2025 at 10:49:20

  Added SAX adapter tests

• xmlresolver/xmlresolver #264 created, 3 Dec 2025 at 10:46:49

  Added SAX adapter tests

  Close #261

  These were submitted by @jarl-dk (thank you!), but I’ve adapted them slightly.

• xmlresolver/xmlresolver #262 closed, 3 Dec 2025 at 10:43:24

  Is classpath only resources supported?

And 1252 more items…