nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqjd874v63430gng67kpw5m597f34dr9vr0yhkp8dkmnma8208raysyd6kk0 (nprofile…6kk0) I guess it depends on what an archival format is for. If the archival format is for making sure that what you publish will be able to be read *in some way* in the future, then HTML makes sense. If the archival format is for making sure that what you publish will be able to be read *in a way adapted to future standards* then I feel like there is an argument for XML, because XSLT allows it to be flexibly processed.
I do actually think that XML output is one of the killer features of forester, because it allows the LaTeX output to be endlessly customized once you understand a bit of XSLT.
Also, you should check out Xee: https://blog.startifact.com/posts/xee/, which is a modern XSLT implementation. If this ends up being what you want to use, I can help to bundle a statically compiled version alongside forester.
Owen Lynch
npub1cj…fxs07
2025-03-28 10:28:12 UTC
in reply to nevent1q…pd7k
Author Public Key
npub1cjyyl7y66997ewku92pzvvhkyec43k7cde44rhgayxdwwl63axdqafxs07Seen on
wss://relay.ditto.pubPublished at
2025-03-28 10:28:12 UTCEvent JSON
{
"id": "3f68d3852f50e0fbe3a56147015b64697bb58a2cc27eb9693930db67bf10d072",
"pubkey": "c4884ff89ad14becbadc2a822632f6267158dbd86e6b51dd1d219ae77f51e99a",
"created_at": 1743157692,
"kind": 1,
"tags": [
[
"p",
"934feab351ac5e89a35eb05d4dd0be4c6ad19583792f609db6dcf7d3a9e71f49",
"wss://relay.mostr.pub"
],
[
"p",
"ba51d3bb7fc92891016b5873c0b4f7c6a0550c964ec565ece24b6fc2dcf93301",
"wss://relay.mostr.pub"
],
[
"e",
"c8dd6325619379dd37e24b9b18860b4587f19a8a49f126a03040ccb3fb520a84",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://mathstodon.xyz/users/olynch/statuses/114239582527073376",
"activitypub"
]
],
"content": "nostr:nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqjd874v63430gng67kpw5m597f34dr9vr0yhkp8dkmnma8208raysyd6kk0 I guess it depends on what an archival format is for. If the archival format is for making sure that what you publish will be able to be read *in some way* in the future, then HTML makes sense. If the archival format is for making sure that what you publish will be able to be read *in a way adapted to future standards* then I feel like there is an argument for XML, because XSLT allows it to be flexibly processed.\n\nI do actually think that XML output is one of the killer features of forester, because it allows the LaTeX output to be endlessly customized once you understand a bit of XSLT.\n\nAlso, you should check out Xee: https://blog.startifact.com/posts/xee/, which is a modern XSLT implementation. If this ends up being what you want to use, I can help to bundle a statically compiled version alongside forester.",
"sig": "52d0bc3bc79e88bf9ac231dfc7855399ea6df44a09e6871d3a4d0a9369976b8c6f21c67219d2d17078bbe03edb3ef49f3eccfaecbf84d463d31db89cd691eb1b"
}