Philip Oakley <[email protected]> wrote: > I'd expect 'git help --pdf git' to simply feed the path of git.pdf > (probably in the same directory as the .html versions) to the web > browser and let it determine the users prefered reader. Yes, this is what I would do as well. Unfortunately I don’t really know C, so I can’t implement this. But for someone who is familiar with C, it should be easy---just call `xdg-open` (X11), `open` (OS X) or `start` (Windows) and thus the user’s preferred PDF reader, and maybe some common programs (evince, okular, …) as fallback.
Junio C Hamano <[email protected]> wrote: > I didn't see (and I still do not quite see) why people would want to > have separate pdf files for all the subcommands (instead of say an > .epub or .pdf that binds all the man pages and perhaps user-manual, > just like we do for .texi/.info). Because it’s a good start :-) I see your point, and I agree that a combined PDF/EPUB/etc would make more sense. This should be not too difficult with the AsciiDoc-DocBook-Toolchain (or maybe even without DocBook), I just need to dig into it a bit further. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
