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

Redo LibreOffice support using UNO #47

Closed
benzea opened this issue Jul 30, 2014 · 5 comments
Closed

Redo LibreOffice support using UNO #47

benzea opened this issue Jul 30, 2014 · 5 comments
Milestone

Comments

@benzea
Copy link
Member

benzea commented Jul 30, 2014

The current LibreOffice support is not very nice for a couple of reasons:

  • it requires parsing both ODT and PDF files. Because of this:
    • prone to break if PDF export changes
    • no support for right to left languages
    • no support for multicolumn layouts
  • Style based system is hard to use

The idea is to move over to use python-uno (either as a macro, or launching libreoffice externally). Using a macro would have the advantage that one might be able to extend the LibreOffice UI to simplify questionnaire creation.

@benzea
Copy link
Member Author

benzea commented Aug 8, 2014

After some trail and error, which did not work out ...

It appears that the API required to do this might not even be available. So, instead we might need to retrieve the information from an XML layout dump. This might work by exporting twice (embedding metainformation in hidden text) and then retrieving first metadata, and later layout information from the XML files.

We might be able to embed all the metadata using hidden text to begin with. That way we don't need styles at all. Though I do not know how to nicely switch between having the text visible/hidden and such.

@benzea benzea removed the python 3 label Aug 13, 2014
@benzea benzea added this to the python 3 milestone Aug 13, 2014
@reviczky
Copy link

https://github.com/mstamy2/PyPDF2

  • Support for Python 3

That should do it!

@reviczky
Copy link

@benzea
Copy link
Member Author

benzea commented Jan 16, 2018

Quite likely, I am going to drop support for ODT for SDAPS 2.x for a start. Don't want this to become a roadblock in the whole project, and moving to Python 3 would make sense at the same time.

@benzea benzea modified the milestones: python 3, 2.0 Jan 16, 2018
@benzea benzea mentioned this issue Jan 16, 2018
@benzea
Copy link
Member Author

benzea commented Apr 2, 2018

Support has been removed now.

@benzea benzea closed this as completed Apr 2, 2018
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

2 participants