ASPN ActiveState Programmer Network
ActiveState
/ Home / Perl / PHP / Python / Tcl / XSLT /
/ Safari / My ASPN /
Cookbooks | Documentation | Mailing Lists | Modules | News Feeds | Products | User Groups


Recent Messages
List Archives
About the List
List Leaders
Subscription Options

View Subscriptions
Help

View by Topic
ActiveState
.NET Framework
Open Source
Perl
PHP
Python
Tcl
Web Services
XML & XSLT

View by Category
Database
General
SOAP
System Administration
Tools
User Interfaces
Web Programming
XML Programming


MyASPN >> Mail Archive >> image-sig
image-sig
[Image-SIG] Problems with XpmImagePlugin.py
by Richard Oudkerk other posts by this author
Jul 7 2004 4:08PM messages near this date
[Image-SIG] Re: gimp-2.0 palette | [Image-SIG] Problems with XpmImagePlugin.py
Douglas Bagnall wrote:
 >  >
 >  > (6) ImageColor.colormap misspells 'lightgray' as 'lightgrey'.  (I
 >  > assume this is a misspelling since it contains 'gray', 'dimgray',
 >  > 'slategray',... but not 'grey', 'dimgrey', 'slategrey',...)
 >  >
 > 
 >  AFAIK, this spelling mixture is very old and has snuck into many realms.
 >   Netscape borrowed XPM colours for html extensions, whence, for a
 >  while, they entered the CSS standard.  The w3c now accepts either
 >  spelling for any shade of grey, but I think X may be more conservative.

But ImageColor.colormap should either stick to one spelling or include both. 
(The patched version of XpmImagePlugin.py can cope with both spellings.)


BTW, I have noticed that the transparency problem goes away if instead of writing

     im.save("file.png")

I do

     im.save("file.png", **im.info)

Shouldn't .save() use the information in im.info by default, or is this intentional?

Richard
_______________________________________________
Image-SIG maillist  -  Image-SIG@[...].org
http://mail.python.org/mailman/listinfo/image-sig

Privacy Policy | Email Opt-out | Feedback | Syndication
© 2004 ActiveState, a division of Sophos All rights reserved