Nostr Web Client

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

Reply to this note

Please Login to reply.

Discussion

Niel Liesmons 6mo ago

No.

Use nostrified #asciidoc.

Also, it overflows on mobile in this app.

elsat 6mo ago

Can you add comment here on the question: https://github.com/nostrability/nostrability/issues/146

And also a screenshot of what you are seeing?

‎לופֿטמענטש 6mo ago

That's LaTeX

Niel Liesmons 6mo ago

My points have already been said in April I see.

elsat 6mo ago

🤝

Silberengel 6mo ago

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.

Silberengel 6mo ago

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.

Silberengel 6mo ago

Yakihonne at least puts it into inline-code backticks, so that you can find it.

Textstr.org is rendering stuff like this:

https://njump.me/naddr1qvzqqqr4gupzqwe6gtf5eu9pgqk334fke8f2ct43ccqe4y2nhetssnypvhge9ce9qqxnzde4xgcrxdfj8qmnvwfc69lg5m

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.

Niel Liesmons 6mo ago

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.

Silberengel 6mo ago

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.

MichaelJ 6mo ago

We're working on the plugins already, might as well share them with the world.

REDKAZ⚡️| YakiHonne 6mo ago

Latex is already supported within nostr:npub1yzvxlwp7wawed5vgefwfmugvumtp8c8t0etk3g8sky4n0ndvyxesnxrf8q However it has nothing to do with the NIP-23 we just support the preview and Latex syntax

REDKAZ⚡️| YakiHonne 6mo ago

From mobile pov

YakiHonne 6mo ago

On the list.

hzrd149 6mo ago

It wouldn't hurt for apps to support LatEx syntax in markdown, but I don't think it should be required. markdown has hundreds of extensions and it gets more complex the more you use

Silberengel 6mo ago

It's already the case that the #NostrMarkup LaTeX implementations for 30023s don't match. Stuff looks different, depending upon the client.

elsat 6mo ago

nostr:npub1yzvxlwp7wawed5vgefwfmugvumtp8c8t0etk3g8sky4n0ndvyxesnxrf8q nostr:npub14ya7n7czu3kyq3m2sn6kjawmtq6ll6kerrlm90gz9yzfjmflmsxq8dsn39 nostr:npub18vay956v7zs5qtgc65mvn54v96cuvqv6j9fmu4cgfjqkt5vjuvjsc47nzf did yall converge on LaTex rendering?

Victor Stabile 6mo ago

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.

REDKAZ⚡️| YakiHonne 6mo ago

you can test it out on yakihonne if you want, there isa github discussion about this also if u want to join it

elsat 6mo ago

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?

Victor Stabile 6mo ago

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.

Silberengel 6mo ago

Obsidian does full LaTeX typesetting, but 30023s use Markdown for that. I'm sticking to `latex` format, and only rendering MathJax formulas, not entire LaTeX documents.

Victor Stabile 6mo ago

I usually write my articles using markdown with embedded latex in obsidian

REDKAZ⚡️| YakiHonne 6mo ago

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.