Perhaps the work KDE does could later be more generalized but I think they need to include others in these ideas right now.

It would be useful to have a KDElib for this but it would be even more useful to have a more generic lib or at least standard for this. I hope that they make sure to involve others outside of KDE on this, such as Apache,, GNOME, Apple, Corel, and OpenOffice.

The “decompilation” of ODF is relatively easy, so documents created in ODF format (and following a certain specification) could be re-imported to another application. “The same content as an ODF table would be trivially to process, one could even transport cell types, e.g. While this listing solution is okay for small amounts of data, it can get extremely complicated for more data, especially if data fields are “encapsulated”, meaning they contain another dataset, such as “X220180:,:F32.1”. “CSV files are a mess: one needs to know (through user input or preprocssing/autodetection) which character is used as the delimiter, has to be carefull about quotation or escaping of the delimiter, there is no hint on the content encoding, …” While ODF can be processed everywhere, you can even not use KOffice and use OpenOffice for editing instead, if you want. you have client data from one of your patients and want to create a medical report, so the basic data (name, date of birth, insurance number, registration code, diagnosis, test results) is already in the document (which already contains your company head, address, phone etc., along with the date) when KOffice starts for you to enter the report text. It could be used to create documents which are prepared to get edited in KOffice, e. The idea of using a library instead of re-inventing a ODF file creator is a great idea. “I especially like the idea to get ODF libs available for developers outside the KOffice project.”

Apache openoffice for windows 10 x64