-
Notifications
You must be signed in to change notification settings - Fork 65
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
Is this project alive #100
Comments
I wrote this code in 2006 as a thin abstraction layer on top on the XML DOM. At the time the intent was to have something until a more powerful library would be available from e.g. the Document Foundation. The organisation I work for doesn't use this library any longer, so no, there is no proactive maintenance happening. |
But do you plan to merge Pull Requests? E.g. if somebody finds errors/issues and provides a solution? Or do you suggest a fork? I didn't have the impression that a more powerful library is available for Python for ODF manipulation. E.g. I find the decision to have many interfaces to expect Element subclasses, while at the same time Text nodes are not Element subclasses to be problematic: E.g. OpenOffice, depending how you type your text, puts text in text:span elements, or directly into higher elements like text:p, now solve with the existing code the simple exercise: "spit out all text in an ODF" Only possible my recursively walking doc.topnode. Remove all children from a node? Oops, better have no children that happen to be Text, because it will raise an assert in remove_from_caches (that insists that it can only remove elements from the cache, right, and Text is not a subclass of Element), ... |
Would be great if all of you could join the "discussion" in #123. |
Please see my comment about that. |
Am about to start using this code, my only worry is that it does not seem to be actively maintained.
The text was updated successfully, but these errors were encountered: