Kyle Barrow wrote:
> There is a property for a browsers PNG support. i-mode supports this - I
> thought they only handles GIFs?
>
i-mode handsets can only display GIFs. J-Phone handsets display PNG and JPG.
r e n
>
> I have tried to add as much information as I can squeeze out of DoCoMo which
> will all be available through BrowserHawk. cyScape is even creating new
> characters per line and number of lines properties for i-mode. I would like
> to see character/line values for non-i-mode phones but am not sure where to
> start looking.
>
> Kyle
>
> -----Original Message-----
> From: keitai-l-bounce@appelsiini.net
> [mailto:keitai-l-bounce@appelsiini.net]On Behalf Of Jon Baer
> Sent: Thursday, September 28, 2000 9:40 PM
> To: keitai-l@appelsiini.net
> Subject: (keitai-l) Re: How to identify a mobile device with a redirect
> script
>
> Cool,
>
> Are they going to have specifics on PNG support, Gif89a support, etc?
> Unfortunatley no header to differentiate between graphics themselves it
> seems.
> The UserAgent should be sufficient but they should also keep a track (or
> map) of
> maybe what the phones themselves support in house, is this what you are
> doing?
>
> Like if you can tell the model, should be able to get some definitions from
> the
> model.
>
> [ excessive quoting removed ]
--
ascii: r e n f i e l d
octal: \162 \145 \156 \146 \151 \145 \154 \144
hex: \x72 \x65 \x6e \x66 \x69 \x65 \x6c \x64
morgan stanley dean witter japan
e-business technologies | engineering and strategy
-- Binary/unsupported file stripped by Listar --
-- Type: application/x-pkcs7-signature
-- File: smime.p7s
-- Desc: S/MIME Cryptographic Signature
Received on Fri Sep 29 02:31:05 2000