https://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.
jerf 47 minutes ago [-]
Over 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.
PaulDavisThe1st 6 minutes ago [-]
I added DVI support to NCSA Mosaic back in 1993-94, believing it to be a better format for "rich" documents than HTML or PDF.
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.
jerf 30 minutes ago [-]
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".
joshjob42 2 days ago [-]
Add 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.
stschaef 32 minutes ago [-]
I 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
psc007 3 days ago [-]
Why is there no npm registry package?
hulitu 21 hours ago [-]
> 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.
lizhang 20 minutes ago [-]
[dead]
Rendered at 18:16:27 GMT+0000 (Coordinated Universal Time) with Vercel.
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.
Nobody else seemed convinced :(
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.
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".
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
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.