Moved from another thread:
i would just suggest joining the higher standard in writing excellence of the (pretty) older user manual (.odt) with the accessibility and top-notch friendliness of the (not so)newer quick start guide and user manual (.epub), as much as humanly possible ;)
Yes, looking at the both of them, I can see what you mean. I would be happy to do some grunt work in this regard, but I'm not highly skilled in document format conversions etc... I'm not opposed to learning, though. The sourceforge wiki uses markdown, so if we were to use that as a base, we could build web and print documents from that. I think the important thing is to have a good web version of the docs, personally. Epub is basically html, so that might also be a good base format if not trying to get it all on the wiki.
@planar2 - I didn't have any trouble with the wiki using firefox, as long as cookies are enabled, etc.
Moved from another thread:
i would just suggest joining the higher standard in writing excellence of the (pretty) older user manual (.odt) with the accessibility and top-notch friendliness of the (not so)newer quick start guide and user manual (.epub), as much as humanly possible ;)
Yes, looking at the both of them, I can see what you mean. I would be happy to do some grunt work in this regard, but I'm not highly skilled in document format conversions etc... I'm not opposed to learning, though. The sourceforge wiki uses markdown, so if we were to use that as a base, we could build web and print documents from that. I think the important thing is to have a good web version of the docs, personally. Epub is basically html, so that might also be a good base format if not trying to get it all on the wiki.
@planar2 - I didn't have any trouble with the wiki using firefox, as long as cookies are enabled, etc.