----- Douglas Torrance <dtorra...@monmouthcollege.edu> a écrit : > Hi everyone, > > Currently, the FAQ distributed with the source is much less up-to-date > than the FAQ on the webpage, which itself is also very out-of-date. > > I'm interested in working to remedy this, but I'd like to get some input > so I have a better feel of what direction to take.
Hi, My personal point of view is to support you completely on that idea. > There are lots of questions in the FAQ that likely wouldn't be > frequently asked in 2014, e.g., "How do I get Window Maker to use more > than 16 colors on my SGI Indy Workstation?" Should these kind of > questions be removed entirely, or kept for historical purposes? My gut > feeling is to get rid of them. If people want to read the old > questions, there's git and archive.org. I am a bit undecided here too. My feeling is that WMaker has the advantage that it still runs on old hardware, so collectors of these would be interested... I would be in favour of keeping them in a section dedicated to special hardware. On the other hand: are there still people in that case? because if not, it's would be a bit sad to make you spend time on useless thing. Time for the spring clean-up? > Also, it would be nice if the source and webpage FAQs were the same. > One option that could work would be to use something like texinfo, where > the main FAQ is written in some format that can be exported to plaintext > for the source and html for the webpage. Maybe there's an even better > solution? There are plenty of solution... - the current hype is probably Markdown syntax, which has the advantage that the text remains directly readable (for the FAQ distributed in plain as part of the package), but it requires contributors to install the appropriate tools to check it will convert ok to HTML; - there's also txt2html, which is probably an ancestor of markdown (with the same constraints); - there's stuff like docbook, but I personally would not recommend it (stuff to install, no more plain text directly available, too verbose markup); - the texinfo is probably not a bad solution (still some stuff to install, but directly readable text file); - groff (used for man pages), but the syntax is not so great, the file is not really directly readable; - custom sed-based shell script to generate HTML from current text format (no added dependency then, but probably not worth the effort...) So I guess texinfo would probably be a decent choice? > And of course, maybe there's some more questions/answers we could add to > the FAQ. > > I'd appreciate any thoughts. Thanks! > Doug -- To unsubscribe, send mail to wmaker-dev-unsubscr...@lists.windowmaker.org.
