Minor bug report: templates/BlueGrey/styles.css

Found in 2.0beta7 rev 445:

templates/BlueGrey/styles.css

line 69 should read:
   background-color: #ff8888;

not->
  ackground-color: #ff8888;


Minor typo.  No biggie, but it wiped out the diff
highlighting for 
deleted lines.




------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribewebsvn.tigris.org
For additional commands, e-mail: dev-helpwebsvn.tigris.org

If you guys are thinking about dumping enscript and going
with an "all 
PHP" solution for pretty-printing, may I also request
that we be able to 
select ".pdf" as an output option?  Not only for
individual files, but 
perhaps entire directories of source code? 

Another idea, maybe even print a "contact sheet"
of thumbnails for 
graphics formats that PHP understands. 

IIRC, PHP has some innate PDF ability, so this might not be
*completely* 
heinous.

Not that I'm volunteering to code it...  




------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribewebsvn.tigris.org
For additional commands, e-mail: dev-helpwebsvn.tigris.org

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

Christopher A. Shamis wrote:
> If you guys are thinking about dumping enscript and
going with an "all
> PHP" solution for pretty-printing, may I also
request that we be able to
> select ".pdf" as an output option?  Not
only for individual files, but
> perhaps entire directories of source code?
> Another idea, maybe even print a "contact
sheet" of thumbnails for
> graphics formats that PHP understands.
> IIRC, PHP has some innate PDF ability, so this might
not be *completely*
> heinous.
> 
> Not that I'm volunteering to code it...  
> 
> 
> 
> 
>
------------------------------------------------------------
---------
> To unsubscribe, e-mail: dev-unsubscribewebsvn.tigris.org
> For additional commands, e-mail: dev-helpwebsvn.tigris.org
> 
> 
I myself plan on doing something sometime later to
abstractify the output
of source code enough so that something like this is easily
possible.
Thanks for the idea of another output method. 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)

iD8DBQFENyFp5tcAKF5t41MRAmciAJ4veW0k3j5G0Lq8XPtNxpEZLjylcgCg
hFqk
j39o7y9g5wL42CM5PSGe06E=
=OHJE
-----END PGP SIGNATURE-----

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribewebsvn.tigris.org
For additional commands, e-mail: dev-helpwebsvn.tigris.org

Yeah, I work in a all-windows shop, and you would not
BELIEVE what 
Microsoft coders qualify as a source-code printout.  Think:
Notepad 
File->Print.  They don't have line-numbers or
syntax-highlighting; heck, 
half the time they don't even have the filename in the top
of the 
page-header. 

/This/ is what passes for "innovation" on the M$
platform.  What a 
joke.  It's a sad state of affairs when the worlds leading
software 
company's premier development IDE doesn't even have a
decent "code 
print" function that comes even close to what has
existed in the FREE 
arena for over 15 years. 

Anyway, all the more reason to implement it in Websvn.  At
least then 
those poor fools stuck coding in VS.NET might be able to get
nice, 
clean, pretty-printed source.  ---Although once all those
Win32 
programmers realize the joys of a proper hard copy, it will,
of course, 
spell the doom of many trees... 

>I myself plan on doing something sometime later to
abstractify the output
>of source code enough so that something like this is
easily possible.
>Thanks for the idea of another output method. 
>
>  
>

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribewebsvn.tigris.org
For additional commands, e-mail: dev-helpwebsvn.tigris.org