Manoj Srivastava <sriva...@acm.org> writes: > I am writing the sources of this in a mode that I can turn into > text as well as html, and I was planning on just adding it to the html > files produced by the policy package, as well as a set of .txt files in > /usr/share/doc. Once we have released that, and the html files are live > on the web, we can turn the wiki pages into pointers to them.
Sounds great to me. Using lynx -dump or something similar to generate the text files from the HTML files, or some other format that generates both output formats? It might be nice sorting out a nice hyperlinkable format for upgrading-checklist too while we're at it, since there's been a frequent request for things like the PTS to be able to link to the upgrading-checklist data for a particular release and for the section references in the document to be links to the relevant bits of Policy. It's currently theoretically in HTML, but all the content is a giant <pre> block so that's only theoretical. > I would be happy to maintain these documents in the package > itself, and we can decide on the css (my current css received a number > of negative reviews about fonts and colors, but I am sure there are > plenty of people who can who can show me the error of my ways here). Sounds good to me. I know enough CSS to do something simple like my personal web pages, so I may be able to help. My style definitely tends towards the minimal. -- Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
