First I apologize for not replying earlier and thank you for the comments. The document is automatically generated with XSLT and the result has some problems, but I believe they can be fixed. I will bring up the point on GIF 89a/87a with the group in this week's call. You are suggesting that we either specify GIF 87a only, or specify 89a and allow for transparency? Thanks, Sean On 8/1/06, Frank Ellermann <nobody@xyzzy.claranet.de> wrote: > > Hi, could you please "downgrade" this document to be visible > with "any" browser ? Some internal links apparently have no > anchors, or their anchors have no name=, I didn't check the > source. I'd also appreciate it if you replace the three used > non-ASCII characters by NCRs or symbolic references ( in > the table of contents). > > In section 3.7 (default delivery context) you allow JPEG and > GIF 89a (non-interlaced, non-transparent, non-animated). The > latter would be almost the same as GIF 87a adding text chunks. > What is a mobile device supposed to do with text in GIF 89a ? > Or in other words, what's wrong with the transparency concept > in GIF 89a ? > > Bye, Frank > > >Received on Wednesday, 16 August 2006 14:50:04 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:10:34 GMT