I will only respond to two parts of your dialogue, since I just don't agree with you. All noble initiatives aside, this is a lost cause in my opinion. To each its own I guess...
Quote:
Originally Posted by skreutzer
That's exactly what I'm looking for! Maybe it won't be used by most people (with the consequences they have to pay according to this decision), but it will at least for myself and the people I'm working with. But I can't find *SCADS* of tools that do semantic markup, Doitsu mentioned AbiWord, I mentioned LyX. Any other?
|
There are more, like yWriter and Scrivener. They free to use, but not open source. Then again, they would not work for you anyway, since they have either been compiled for Mac and/or Windows. They can run on Linux (or at least yWriter can) via WINE.
Quote:
Originally Posted by skreutzer
In fact, it is a very good thing to provide conversions from secret formats and proprietary software to open formats. Hopefully this doesn't lead to a situation where people start to build workflows around your add-on (and therefore around the proprietary software), which would contradict the problem you want to solve initially. But I guess, you have no control over that...
|
As I have said multiple times, the DOCX format is not secretative or proprietary. It is a well documented open format. It is the OOXML (Office Open XML) and been accepted as an open standard in 2006 by ECMA and in 2008 by ISO.
The old format was a closed proprietary format. The new one isn't and can be used by anyone if they want, regardless of the OS.
The reason I created this, is that I want another type of output not suited for a wordprocessor. Actually, a lot of information very relevant to a wordprocessor is thrown out the window since it has no use in an e-book. So, that is not a good output for a wordprocessor.
Without a doubt someone can come up with a document that my add-in chokes upon. I am always looking for documents that can actually that, since it helps me to improve the process. Still, the add-in was initially created to help my own process and for some others. That grew to support more, but in the end I still make the decisions. I can say that if I do not longer support the add-in, it will be open-source. Untill then, I keep it closed source for various reasons.