-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DLLify the main parsing stuff #2
Comments
@konsumer hopefully you made progress here. Perhaps you could try to make it so that it is still compatible in linux world? That is where I see the main motivation to use this util. Cheers! |
Totally. I just mean it as a general concept. I use a Mac, so it's .so for both of us. I'm not super-strong with C, so it goes very slow. I'd be happy to do the wrappers and emscripten compilation, but maybe it would make more sense for a C-person to do the other stuff, if there's interest. I'll keep working on it, though, if no one else wants to do it. |
The original author has a git repository here: http://www.wagner.pp.ru/git/oss/catdoc.git he has updated this and I think the code in this branch is out of date. you may want to see if he can move his code into github or just do a merge for him. Anyways, this doesn't really answer your question, but good luck on your quest. |
Thanks! |
I'm working on the beginnings of a pure-javascript catdoc, based on this project. As I look at this code (which is totally excellent, by the way) I keep thinking that if it were a DLL with everything but the CLI options parser & file-reader, it would be easier to integrate into lots of languages. I could use emscripten to compile it to client-side javascript (like sweet client-side doc upload widgets), and write thin ffi wrappers for other languages (like nodejs, python, lua, ruby, etc.)
The text was updated successfully, but these errors were encountered: