LaTeX.wasm: LaTeX Engines in Browsers
swiftlatex.com
LaTeX.wasm: LaTeX Engines in Browsers
1–10 of 42 posts
Re: LaTeX.wasm: LaTeX Engines in Browsers
#2Why is there no npm registry package?
Re: LaTeX.wasm: LaTeX Engines in Browsers
#3Add LuaLaTeX and you're cookin' with gas. For real would be fantastic if we could get more or less the full LaTeX ecosystem readily and rapidly available online and in a huge variety of desktop applications.
Re: LaTeX.wasm: LaTeX Engines in Browsers
#4> LaTeX Engines in Browsers
This is hillarious. Browsers lost the ability to print some 10 years ago. Today, printing a web page is an exercise in masochism.
I am very curious how the output will look like.
Re: LaTeX.wasm: LaTeX Engines in Browsers
#5Over the years many people have hypothesized that once WASM was really mature, it would become practical to fix the issues with web browser layout by sending down custom layout machines to users.
I would find it hilarious if LaTeX turned into a leader in that space. I doubt it could hold on to that. There's a lot of things that something designed from the beginning for web-like uses could probably improve on that would be capable of overcoming LaTeX. But I could see a world where it carves out a niche and holds on to that niche for a long period of time.
Re: LaTeX.wasm: LaTeX Engines in Browsers
#6Over the years many people have hypothesized that once WASM was really mature, it would become practical to fix the issues with web browser layout by sending down custom layout machines to users. I would find it hilarious if LaTeX turned into a leader in that space. I doubt it could hold on to that. There's a lot of things that something designed from the beginning for web-like uses could probably improve on that wou…
Running layout in WASM is already practical. A good demo is https://www.nicbarker.com/clay
The things you can't do are things like expose an accessibility tree (without a dummy DOM), interact with the system IME, and access system fonts.
Re: LaTeX.wasm: LaTeX Engines in Browsers
#7I immediately received the following error :|
This is pdfTeX, Version 3.14159265-2.6-1.40.21 (SwiftLaTeX PDFTeX 0.3.0) (preloaded format=swiftlatexpdftex) I can't find the format file `swiftlatexpdftex.fmt'!
Likewise for XeTeX
Re: LaTeX.wasm: LaTeX Engines in Browsers
#8Over the years many people have hypothesized that once WASM was really mature, it would become practical to fix the issues with web browser layout by sending down custom layout machines to users. I would find it hilarious if LaTeX turned into a leader in that space. I doubt it could hold on to that. There's a lot of things that something designed from the beginning for web-like uses could probably improve on that wou…
Running layout in WASM is already practical. A good demo is https://www.nicbarker.com/clay The things you can't do are things like expose an accessibility tree (without a dummy DOM), interact with the system IME, and access system fonts.
I feel like it's fair to say that you have not "fixed the issues with browser layout" if you lose accessibility and input. System fonts I can live without, we can push our own, but those two things are a big deal.
Even input you might be able to hack around but accessibility is a big deal and the "hack" at that point is nearly to both lay it out in the browser and the supposed "fixed" layout system, and while that may work in some sense I again have lots of questions about whether that is really "fixed".
Re: LaTeX.wasm: LaTeX Engines in Browsers
#9https://www.swiftlatex.com/editor.html for the wysiwyg editor says "We are working hard to fix the editor." It has said this for many years. I think I tried it once when it was live and it was pretty cool. My guess is people observed it could corrupt documents, so it was taken down.
Re: LaTeX.wasm: LaTeX Engines in Browsers
#10[dead]