-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am 27.03.2010 21:55, schrieb jfine: > On Mar 27, 2:17 pm, jfine <[email protected]> wrote: >> Hi >> >> I'd like to use Sphinx to create an improved TeX/CTAN catalogue. You >> can see the current version at >> http://texcatalogue.sarovar.org/
Very interesting! As you probably guessed, I love TeX :) I'm getting the catalogue data right now, to try out your work. > Just to say that I've made a start > http://bitbucket.org/jfine/sphinx-ctan-catalogue/ > > The file that is of most interest is > > http://bitbucket.org/jfine/sphinx-ctan-catalogue/src/64ca79292bc1/py/doit.py > > I guess I need to map as best I can the catalogue XML to the Sphinx > constructs, perhaps using extensions to add constructs. Yes, I'd suggest that as well. > As the search facility uses the (for me) intermediate rst files I > guess I can't avoid them, so one way or another I'll be writing rst > files. Not necessarily, only if you want to see the matching text for search results. But anyway, currently Sphinx does assume that there is a source file for every document. While I don't think it would be difficult to conditionalize that assumption where necessary, personally I would always go with such a two-step process. Writing out rst is not hard using standard tools such as textwrap and basic regexes, and it's much more convenient to check the output in the form of a file. cheers, Georg -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (GNU/Linux) iEYEARECAAYFAku7mm4ACgkQN9GcIYhpnLBFeACeL0iObNwAROK3Nhm+o+XSg9f0 sjoAnRzRJwzhia8/zRn+ASftlVmHQIny =WIds -----END PGP SIGNATURE----- -- You received this message because you are subscribed to the Google Groups "sphinx-dev" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/sphinx-dev?hl=en.
