Re(2): Re(3): Re(2): Re(2): [Keitaidata-devel] licence/xml/format

[Nick M. <ni...@ky...>]

to...@no... writes:
>As Curt said earlier, once this stuff is in the system
>we don't have to edit it much anyway so we don't exactly have to worry
>about typing.

true enough.  I do keep forgetting....
>
>
>What do you mostly want though when serving to handsets... I'm thinking
>that most peoples requirements are simple, if its i-mode, they probably
>know the basic tags it supports, they want to know screen resolution
>and number of characters across.

There is explicit and implit knowledge here....

If we DO know it is a Japanese imode phone, we might need to know the
following....

text-width
text-height
horizontal_res
vertical_res
colour_level   / 4056/256/8/2
colour_type  /* colour, greyscale, BW */
sound
cachesize
animatedgif support
number_of_form_entities.  /* 31 or 42 */
multiple_form_entities_selectable?
uin_support /* but this is in the header I guess */
foma
markup_level (imode-html1,2,3) /*optional*/
+ java capabilities
+ bugs...


/*if we don't know it is a Japanese imode phone, 
   we would also need to know the following. It is "implicit knowledge",
as such.... */

markup_type     /* is it imode or jphone or au */
gif support
built_in_back_button_support = yes
autoimagesizereduction=yes
encoding=shift_jis
postsupport=yes
getsupport="yes"
wrapsupport=no
jpgsupport
png support
pngdepth /* 8bit, 24 bit */
server_side_forwarding_support.  /* can I forward it transparently to a
different url */



I don't use "sound" but everything else I would "want to know"



How much "implicit knowledge" do we need to code in? For example, I know
that all imode phones support gif, but not jpeg. Should this be specified?
I suspect it should as I WOULD want it specified if it was a German Imode
phone (for example).

Nick