W3C home > Mailing lists > Public > public-bpwg-comments@w3.org > July to September 2006

RE: CR-mobile-bp-20060627

From: Jo Rabin <jo@linguafranca.org>
Date: Fri, 8 Sep 2006 16:08:16 +0100
To: "'Frank Ellermann'" <nobody@xyzzy.claranet.de>
Cc: <public-bpwg-comments@w3.org>
Message-ID: <011501c6d358$9dc84b50$8100a8c0@Linguafrancam2>

Hello Frank

The Best Practices Working Group has decided to change the document to refer
to GIF 89a, without limitations, in the light of your comments.

I found one broken internal reference, but you refer to several. It would be
very helpful if you were able to supply any further information.

On the subject of troublesome characters, again it would be very helpful if
you were able to provide more detailed information about the problem you
describe and perhaps you could let us know what browser/version you are
using.

Thanks again for your comments. 
Jo 
> -----Original Message-----
> From: public-bpwg-comments-request@w3.org [mailto:public-bpwg-comments-
> request@w3.org] On Behalf Of Sean Owen
> Sent: 16 August 2006 15:50
> To: Frank Ellermann
> Cc: public-bpwg-comments@w3.org
> Subject: Re: CR-mobile-bp-20060627
> 
> 
> 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 (&nbsp; 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 Friday, 8 September 2006 15:08:57 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 15 June 2012 12:13:30 GMT