It's already the case that the #NostrMarkup LaTeX implementations for 30023s don't match. Stuff looks different, depending upon the client.
Discussion
nostr:npub1yzvxlwp7wawed5vgefwfmugvumtp8c8t0etk3g8sky4n0ndvyxesnxrf8q nostr:npub14ya7n7czu3kyq3m2sn6kjawmtq6ll6kerrlm90gz9yzfjmflmsxq8dsn39 nostr:npub18vay956v7zs5qtgc65mvn54v96cuvqv6j9fmu4cgfjqkt5vjuvjsc47nzf did yall converge on LaTex rendering?
I just implemented naively what I was using on Obsidian. I would change it to a sane standard if there was one, but I am not advocating for one.
you can test it out on yakihonne if you want, there isa github discussion about this also if u want to join it
Check out yakihonne approach on github nostr:npub18vay956v7zs5qtgc65mvn54v96cuvqv6j9fmu4cgfjqkt5vjuvjsc47nzf https://github.com/nostrability/nostrability/issues/146#issuecomment-3054965472
If you don’t object, can you consider yakihonne’s approach, so that two known apps rendering LaTex have identical rendering?
Right now I am too busy to dive into it, not to mention to reimplement a new standard. Also, I write all my articles on Obsidian which renders LaTeX the same way as TeXstr, if I change, I would need to either write them without proper rendering or rewrite every formula before publishing to Nostr. We would need at least a decent editor that renders the same format as Nostr clients for it to be usable in practice.
We are rendering Latex from long time ago due to some researchers needs, however not sure how the standard should go perhaps the best idea is to keep it under the ‘’ encoding to avoid conflict.