No.
Use nostrified #asciidoc.
Also, it overflows on mobile in this app.
Should LatEx be added to NIP-23? Texstr.org looking very sexytime
https://github.com/nostrability/nostrability/issues/146#issuecomment-3053102700
cc nostr:npub1l5sga6xg72phsz5422ykujprejwud075ggrr3z2hwyrfgr7eylqstegx9z nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 nostr:npub1yzvxlwp7wawed5vgefwfmugvumtp8c8t0etk3g8sky4n0ndvyxesnxrf8q nostr:npub18vay956v7zs5qtgc65mvn54v96cuvqv6j9fmu4cgfjqkt5vjuvjsc47nzf nostr:npub1zga04e73s7ard4kaektaha9vckdwll3y8auztyhl3uj764ua7vrqc7ppvc nostr:npub1ye5ptcxfyyxl5vjvdjar2ua3f0hynkjzpx552mu5snj3qmx5pzjscpknpr nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft
#devstr
Discussion
Can you add comment here on the question: https://github.com/nostrability/nostrability/issues/146
And also a screenshot of what you are seeing?
I was like woooowww, but then I noticed that it often garbles the text and sentences from the original event content are just missing.
He's got markdown sort of smeared all over the place, with a really aggressive parser, and it just chews everything up.
Agree that Asciidoc is the best place for this.
I render it on everything, as I implemented it for Asciidoc, so why not, but it's usually like 80% hit. Push it much over that, and you start transforming stuff that isn't LaTeX because the parser has to start guessing.
Yakihonne at least puts it into inline-code backticks, so that you can find it.
Textstr.org is rendering stuff like this:
Which I find outrageous. I tried to render that and the parsing is a nightmare. I'll do it the way Yakihonne does, as that's not insane.
It comes down to having a clear, easy-to-parse, syntax, without a gazillion flavours.
#asciidoc is a good fresh start. Just have to mindful that Nostr-stuff has to added in a clear way most peeps ca agree on + all new WYSIWYG editors etc... have to built.
nostr:npub1wqfzz2p880wq0tumuae9lfwyhs8uz35xd0kr34zrvrwyh3kvrzuskcqsyn was thinking we could build a plugin for Asciidoctor, to set a Nostr standard for the implementation. Then custom implementations could refer to that.
Could maybe get Asciidoctor to take it up on their own list.
We're working on the plugins already, might as well share them with the world.