Re: [armedbear-devel] [armedbear-cvs] r13338 - trunk/abcl/doc/manual
On 17 June 2011 10:01, <mevenson@common-lisp.net> wrote:
Separate content/presentation rules via LaTeX include directives. Properly use the as yet unwritten \code{} markup.
The listings-package might be useful for source code listings. At any rate, writing a macro for it manually would be just wrong. :) There are existing packages for that, let's use them, ok? On the choice of LaTeX, +1 high praise, I love it, although I've never used it much to generate html with proper links/frames and all. The little dabbling I've done seemed non-problematic, though, and the output on non-html in TeX has always been superior to anything I've tried.
On 6/18/11 5:57 AM, Ville Voutilainen wrote:
On 17 June 2011 10:01,<mevenson@common-lisp.net> wrote:
Separate content/presentation rules via LaTeX include directives. Properly use the as yet unwritten \code{} markup.
The listings-package might be useful for source code listings. At any rate, writing a macro for it manually would be just wrong. :) There are existing packages for that, let's use them, ok?
I fully intend to use/adapt existing macros over doing things manually. As I noted in the comments to the commits, I am sort of "walking forward, randomly" to figure out the minimally intrusive markup in actually writing the manual while worrying about how to implement things in the future. For the \code[]{} markup here, I am distinguishing between Java and Lisp source so that I can thunk through the appropriate style for online presentation. -- "A screaming comes across the sky. It has happened before, but there is nothing to compare to it now."
participants (2)
-
Mark Evenson -
Ville Voutilainen