I'm creating versions of a web application for the Japanese wireless
market. I have successfully created the IMode version, and have a
XHTML version working for WAP 2.0 devices. I have been having problems
however, figuring out what exactly is needed for the J-SKY/Vodaphone
users. I don't read Japanese and have been unable to find any English
documentation on the subject.  From what I understand...there are
different browser versions 2.0, 3.0, 4.x, and 5.0 .  The 4.x and 5.0
browsers seem to be able to dispaly the cHTML and the XHTML versions
of my application....but the 3.0 and lower versions can't. I thought
maybe they were expecting WML content but they weren't able to read my
WML version of the Application either.
I would like to get some more info (in English) on the
J-SKY/J-PHONE/Vodaphone service. Particularly how to develop
applications for the different versions of the browser.

---

Clarification of Question by adrock64-ga on 07 Mar 2005 07:32 PST

I am not sure why I have not received any kind of response to this
question.  Is it priced too low?  Is it waiting to be assigned?

All recent Vodafone handsets support XHTML Basic (+ some proprietary extensions).
Older J-Phone handsets have support for MML or Mobile Markup Language,
an HTML derivate similar to DoCoMo's cHTML (but, as usual, a bit
different).
More info on Vodafone's XHTML Basic support on
http://www.dp.j-phone.com/dp/tool_dl/download.php?docid=135 (document
is in Japanese, but also contains a lot of understandable code samples
and references).
As for MML, I can't come up with relevant documentation -most of it
seems to have disappeared when J-Phone became Vodafone KK-, but the
"J-sky editor" software can still be downloaded from
http://www2.j-phone-west.com/funtoj/download/down.html
To be honest, I wouldn't develop several mobile versions of one site;
recent DoCoMo/Vodafone/AU handsets all support XHTML Basic (and even
XHTML-MP), so it should be possible to create one version that works
on all recent handsets - older phones may have some display problems,
but then again, the number of consumers stuck with a +3 years old
phone is rather limited. Forward compatibility is the way to go, in my
opinion.