Hi Jacob, * Jacob Block <jacob.bl...@gmail.com> [04.01.2013 10:19]: > I've been looking at documentation toolchains and so far Sphinx seems to be > an excellent choice. I am not interested in the python side, I'm working on > creating engineering notes/texts in Latex. So my first step was just > finding out what I can get rid of and simplify down. > > I tried changing the documentclass from howto/manual to article, report, > etc. and it was always looking for sphinx+documentclass. Found that > hard-coded in line 173 of sphinx/writers/latex.py. > > 'wrapperclass': 'sphinx' + document.settings.docclass, > > Dropping that now accepts the different default Latex document classes > which seems like a good start. Also didn't need to include the sphinx > package which I saw from year + older threads seemed to be necessary. I'm > interested in expanding this separation but would like to keep things > working normal and would appreciate some feedback.
your idea sounds very interesting. I completely agree with you that Sphinx is one of the finest tools -- perhaps *the* finest tool :) -- to publish scientific papers in a web-based and printable form. For my part, I still use some simple workarounds to create my homepage (main topic: physics, language: german): http://www.grund-wissen.de Some of these workarounds I noted down here: http://www.grund-wissen.de/notizen/tools/sphinx/anpassungen.html I'm quite happy with the results Sphinx creates in that way. Since I'm not enough with Sphinx details, I probably can't give you further help on your development idea. In my opinion, different LaTeX document classes nevertheless would be a nice feature, for example to create presentations or to support different papersize formats (like ``scrbook`` and so on do for European page formats). Greetings and good luck, Bernhard
signature.asc
Description: Digital signature
