The worst is that they are expecting complex formats to “just open” and using those complex formats. It’s the EU, such a thing as a modern office format should be standardized the hell through, there should be a format specifically designed for all such places, MSO just shouldn’t be a factor. Yet when MS kickbacks are involved, it’s fine to use something unfit for the task and call a couple of blank pages (at page breaks, I assume) a fatal flaw. Anyway, text formats are complex, but not that complex, MSO’s OOXML is just intentionally left open and with variety of interpretations and with implementation’s data structures not important for anything written into the standard and in general it’s a scam device and MS should have been fined like 50 billion for publishing it and daring to propose it to official entities and as a standard.
What I don’t understand is why can’t we use something like XHTML with <tex> and <ps> and <csv> tags and a WYSIWIG editor.
I mean, OK, I’ve spent a few months playing with prototyping a document format with edits history and comments and it’s not as easy as it seems, but applying what worked for me to a content format like described above with links to blobs by hashes, blobs stored in the same zipfile, one could get something usable for many office tasks.
Not even talking about org-mode, you know, existing, with just a bit of extension that could fill the role of many office applications.
I mean, no need to even talk about “fit for the task” and efficiency. 90s’ WordPerfect was good enough for the same uses. The complexity of formats is a deliberate way to limit competition by MS and a deliberate excuse to keep getting kickbacks for the organizations in question.
There’s just one thing that can be done - to make it mandatory to use software developed by government contract for this specific purpose for all governmental stuff, and make it FOSS, and with a FOSS format, and with specifications simple enough for a student to write an editor.
The worst is that they are expecting complex formats to “just open” and using those complex formats. It’s the EU, such a thing as a modern office format should be standardized the hell through, there should be a format specifically designed for all such places, MSO just shouldn’t be a factor. Yet when MS kickbacks are involved, it’s fine to use something unfit for the task and call a couple of blank pages (at page breaks, I assume) a fatal flaw. Anyway, text formats are complex, but not that complex, MSO’s OOXML is just intentionally left open and with variety of interpretations and with implementation’s data structures not important for anything written into the standard and in general it’s a scam device and MS should have been fined like 50 billion for publishing it and daring to propose it to official entities and as a standard.
What I don’t understand is why can’t we use something like XHTML with <tex> and <ps> and <csv> tags and a WYSIWIG editor.
I mean, OK, I’ve spent a few months playing with prototyping a document format with edits history and comments and it’s not as easy as it seems, but applying what worked for me to a content format like described above with links to blobs by hashes, blobs stored in the same zipfile, one could get something usable for many office tasks.
Not even talking about org-mode, you know, existing, with just a bit of extension that could fill the role of many office applications.
I mean, no need to even talk about “fit for the task” and efficiency. 90s’ WordPerfect was good enough for the same uses. The complexity of formats is a deliberate way to limit competition by MS and a deliberate excuse to keep getting kickbacks for the organizations in question.
There’s just one thing that can be done - to make it mandatory to use software developed by government contract for this specific purpose for all governmental stuff, and make it FOSS, and with a FOSS format, and with specifications simple enough for a student to write an editor.
Anyway. This is all dreams.