oever

52 ms·

571.
WebODF meets ownCloud to fix what’s wrong with Google Docs(themukt.com)
3 points by oever 12y ago|0 comments
572.
WebODF: finally a text editor based on web standards (adityabhatt.wordpress.com)
10 points by oever 12y ago|0 comments
573.
Top KDE meeting asks for your financial help.(kde.org)
1 points by oever 12y ago|0 comments
574.
by oever 13y ago
How could you forget processing instructions and stylesheets?
575.
by oever 13y ago
They could save quite some money and gain security by switching to a mix of WebODF, and OpenOffice/LibreOffice.
576.
by oever 13y ago
Support for general XML is something that is very feasible. There is already an experimental branch (xml) on github for this. This branch has XML Schema support. XML Schemas can be read and the UI adapts to the schema. With CSS the document
577.
by oever 13y ago
Everyone is free to fork WebODF and at this moment there are 19 forks of it on github. So there is no single gatekeeper. We welcome everyone that contributes and we give active contributors favorable license costs for their closed commercia
578.
by oever 13y ago
Thanks for the observation. I'm part of the WebODF team. We certainly do not mean to spread FUD. Of course one can build a commercial product around WebODF without needing a license as long as the commercial product respects the AGPL l
579.
Bringing OpenDocument to the web, collaboratively(aditya.bhatts.org)
2 points by oever 13y ago|0 comments
580.
OwnCloud 6 will have document editing powered by WebODF(webodf.org)
1 points by oever 13y ago|0 comments