I ported LaTeX to Javascript

#1

Post by manuels_ » Sat, Jan 19, 2013, 1:53 PM UTC

I ported LaTeX to Javascript
manuels.github.com

Re: I ported LaTeX to Javascript

#2

Post by shocks » Sat, Jan 19, 2013, 2:06 PM UTC

Promising. I am getting some error messages though.

    lstat(/bin) failed ...
    /bin
    :
     
    No such file or directory
    warning: kpathsea: configuration file texmf.cnf not found in these directories:

Re: I ported LaTeX to Javascript

#3

Post by oulipo » Sat, Jan 19, 2013, 2:37 PM UTC

Fun demo, but I can't get the .pdf back right now!

Re: I ported LaTeX to Javascript

#4

Post by manuels_ » Sat, Jan 19, 2013, 3:16 PM UTC

shocks wrote: post #2

Promising. I am getting some error messages though. lstat(/bin) failed ... /bin : No such file or directory warning: kpathsea: configuration file texmf.cnf not found in these directories:

These errors are save to ignore. You have to wait some seconds until compiling has completed.

Note that the browser might prevent the website from opening the PDF (Pop-up blocking)

Re: I ported LaTeX to Javascript

#5

Post by manuels_ » Sat, Jan 19, 2013, 3:17 PM UTC

oulipo wrote: post #3

Fun demo, but I can't get the .pdf back right now!

Probably the browser blocks new windows from popping up (window.open() function)

Re: I ported LaTeX to Javascript

#6

Post by dunham » Sat, Jan 19, 2013, 3:37 PM UTC

manuels_ wrote: post #5

oulipo wrote: post #3

Fun demo, but I can't get the .pdf back right now!

Probably the browser blocks new windows from popping up (window.open() function)

If you want to get around this: When the PDF is ready, give the user something to click on (a button or dialog) and call the window.open() from the onClick callback.

Re: I ported LaTeX to Javascript

#7

Post by shocks » Sat, Jan 19, 2013, 3:42 PM UTC

manuels_ wrote: post #4

shocks wrote: post #2

Promising. I am getting some error messages though. lstat(/bin) failed ... /bin : No such file or directory warning: kpathsea: configuration file texmf.cnf not found in these directories:

These errors are save to ignore. You have to wait some seconds until compiling has completed. Note that the browser might prevent the website from opening the PDF (Pop-up blocking)

Aha okay. You might want to clean that up anyway. :)

Re: I ported LaTeX to Javascript

#8

Post by micheljansen » Sat, Jan 19, 2013, 3:48 PM UTC

Some background would be nice. Wasn't LaTeX notoriously hard to port – to the point that a LateX app for iPad actually ran in an emulator initially [1]. Is this port based on web2c as well?

[1] http://www.litchie.com/?p=419

Re: I ported LaTeX to Javascript

#9

Post by jmix » Sat, Jan 19, 2013, 4:00 PM UTC

Pointlessly awesome. Care to describe why it would make sense to run LaTeX on JS?

Re: I ported LaTeX to Javascript

#10

Post by montecarl » Sat, Jan 19, 2013, 4:01 PM UTC

This part of the document isn't rendered correctly in the resulting pdf:

    In printing, text is usually emphasized with an
       \emph{italic}  
    type style.

In my pdf it looks like the every other letter, starting with the first, is missing from the word italic. It looks like " t l c ". Maybe something is wrong with the fonts. I'm using the latest Chrome on OSX.