-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jason Grout wrote:
> Alex Ghitza wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Hi,
>>
>> This comes up in the pdf versions of the various documentation files:
>> the tutorial, the reference manual, the programming manual, the
>> constructions file.
>>
>> When you have a long-ish line in a verbatim environment, and it exceeds
>> the width of the page, it gets cut off.  For an example (there are
>> many), search for "capped relative precision" in tut.pdf or tut.tex.
>>
>> To solve this, it might be easiest to use a latex package for source
>> code environments like Listings, see
>> http://www.ctan.org/tex-archive/macros/latex/contrib/listings/
>> It does line-breaking, and it has a whole lot of other fancy cool
features.
>>
>> One problem is that it is released under the Latex Project Public
>> License, which is more restrictive than (and hence incompatible with)
>> GPL, see
>> http://www.gnu.org/philosophy/license-list.html
>> but maybe the maintainer of Listings can be persuaded to relicense it?
>>
>> Another possibility would be to make our own customized verbatim
>> environment...
>>
>> Thoughts?
>>
>
> Do we need to include the listings package in Sage?  I have the listings
> package in my system tex distribution already (texlive on ubuntu, but I
> think I have the optional tex packages installed).
>
Very good point.  I also have it in my tex distribution on gentoo
by default.

Alex
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHoTm6dZTaNFFPILgRArEpAJ9Bkg7M44Zpj6DTeKxtWFNXhH5T+wCeLPDE
FfLaOgnoaXj0wnv4CDK9fCY=
=FATK
-----END PGP SIGNATURE-----


--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---

Reply via email to