On Sun, 03 Oct 2010 22:56:30 -0500, john skaller <skal...@users.sourceforge.net> wrote:
> Well, I'm now struggling with the usual problem: how to produce > documentation. > > Basically, I'd like to pull down the web-site and start again from > scratch without a messy content manager. That may be appropriate ifwe > had lots of users, but since there's only two of us, it would beeasier > to post documentation by using the repository and periodicallyextracting > the web-site, since that allows offline editing. > > But the big problem: what format to use for docs? > > Interscript is the current format, it produces web pages and (should) > also make LaTeX, but it has a number of quirks which would require > some work to fix (one of which is that it requires lines to change styles > and doesn't handle spaces properly on style changes). > > Raw HTML is a possibility, though it is very hard to work with. > Links aren't all that easy because one has to name all the files > and then it is a nightmare to change anything. And the markup > is <em>soooo</em> verbose it is a pain to read and write. > > LaTeX is easier to work with, and can be converted to HTML > by one of several converters. This would produce a nice stylised > layout, as well as PDF. But it lacks proper hyperlinking and other > nice stuff that can be done with web pages. Another option: reStructuredText/Sphinx (http://sphinx.pocoo.org/) -- Aleksey Gurtovoy MetaCommunications Engineering ------------------------------------------------------------------------------ Virtualization is moving to the mainstream and overtaking non-virtualized environment for deploying applications. Does it make network security easier or more difficult to achieve? Read this whitepaper to separate the two and get a better understanding. http://p.sf.net/sfu/hp-phase2-d2d _______________________________________________ Felix-language mailing list Felix-language@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/felix-language
