This is the mail archive of the
mailing list for the Cygwin project.
Re: Printable Copy Of The Cygwin Users Guide]
- From: Igor Pechtchanski <pechtcha at cs dot nyu dot edu>
- To: cygwin at cygwin dot com
- Cc: Joshua Daniel Franklin <joshuadfranklin at yahoo dot com>
- Date: Sat, 10 May 2003 14:33:09 -0400 (EDT)
- Subject: Re: Printable Copy Of The Cygwin Users Guide]
- Reply-to: cygwin at cygwin dot com
On Fri, 9 May 2003, Igor Pechtchanski wrote:
> On Fri, 9 May 2003, Joshua Daniel Franklin wrote:
> > On Fri, May 09, 2003 at 11:06:33AM -0400, Igor Pechtchanski wrote:
> > [snip]
> > > > > The only problem I can see is that your courier-fonted stuff (mostly code)
> > > > > does not wrap correctly. In my Adobe 5.05 Reader, the
> > > > > courier stuff went off page. What Reader are you using?
> > > >
> > > > Yes, the code listings are not supposed to wrap. I suppose I really should
> > > > figure out how to mess with the margins in the TeX files, though that defeats
> > > > the purpose of DocBook. (It's not just the reader, xpdf does the same thing.)
> > > > Luckily there aren't very many code listings with >70 columns.
> > >
> > > I'm not too keen on pure TeX, hopefully someone will correct me if I'm
> > > wrong. LaTeX, for example, uses the \textwidth and \textheight dimensions
> > > for the text size on the page, and \topmargin and \@themargin for the
> > > offsets from the top left corner of the page...
> > >
> > > I'll try to come up with a way to change those margins only for code
> > > listings (in a few weeks, though). It would help if you send me
> > > (privately) the .tex file(s) used as input to pdfjadetex...
> > I can do that, though like I said hand-editing the TeX source doesn't
> > scale.
> Oh, I wasn't planning to edit the TeX source; I was hoping to see what
> commands were used to typeset the code listings and maybe send in a chunk
> of the preamble that redefines them...
> I was also thinking about an environment that would wrap the code lines
> automatically, but that would probably take some more hacking...
Hmm, the source that Joshua sent me specifies explicit values for the
margins at the level of the TeX source, so my guess is that the XML schema
used to generate the TeX source would be the thing to change. As I know
next to nothing about the XML schemas used by docbook/jade, either someone
else will have to do it, or it'll have to wait until I have the time to
learn the stuff (not soon). I thought there would be some low-hanging
fruit there -- should have known better. Sorry...
|\ _,,,---,,_ firstname.lastname@example.org
ZZZzz /,`.-'`' -. ;-;;,_ email@example.com
|,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski
'---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow!
Knowledge is an unending adventure at the edge of uncertainty.
-- Leto II
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html