Skip to content
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

aim for standard FlyingSaucer library #41

Open
plutext opened this issue Jan 27, 2018 · 2 comments
Open

aim for standard FlyingSaucer library #41

plutext opened this issue Jan 27, 2018 · 2 comments

Comments

@plutext
Copy link
Owner

plutext commented Jan 27, 2018

FlyingSaucer is reinvigorated over recent years.

It would be good to get the benefit of its improvements, and potentially, to include toDocx in FS itself, so that a patched FS is no longer required.

See also https://www.docx4java.org/forums/xhtml-import-f28/library-question-t2249.html

@plutext
Copy link
Owner Author

plutext commented Jan 28, 2018

A version of FlyingSaucer current against upstream (ie to Jan 2018), but with docx code is at https://github.com/plutext/flyingsaucer/tree/FS2018-YellowfinBI/flying-saucer-docx

A version of docx4j-ImportXHTML which uses this, may be found at https://github.com/plutext/docx4j-ImportXHTML/tree/FS2018

I would like to release a new docx4j-ImportXHTML v3.4.0 based on the FS2018 branch.

But to do that the changes in plutext/flyingsaucer/tree/FS2018-YellowfinBI need to be accepted upstream, and pushed to Maven Central as a new version (which we can use as our dependency).

So next step is to make a pull request.

@plutext
Copy link
Owner Author

plutext commented Jan 30, 2018

See now flyingsaucerproject/flyingsaucer#138

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant