Erik's notes on Writing for the Sony Ericsson cHTML web browser
Practice and examples of pages
Why XHTML? Why not WAP or WML?
Even if you study the standards of XHTML and CSS, as well as my pages on this site, it is still a frustrating work to adopt your web documents to the Sony Ericsson cHTML browser. Of course, it has the side effect that your web documents obtain a pure XHTML skeleton which prepares them to be accessed by the handheld WWW browsers of tomorrow. You might switch to WML but I believe that WML as well as WAP are ephemeral phaenomena that will not endure the development of handheld internet devices such as the high-end SonyEricsson cellular telephones (viewed in 2005).
Reasons
Nokia, the world leader in mobile telephony, was very fast to embrace the XHTML 1.0 Basic recommendations of the World Wide Web Consortium
The available bandwidth - even for handheld devices - doubles every 2 or 3 years.
The available memory in new mobile phones is likely to double every 6-8 months, which allows for ever more advanced browsers with better image rendering, internet caches etc.
Special treatment of mobile phones of the less-requiring WML and WAP kind will become unnecessary. Everything will merge into XHTML. This is why I shall deal only with XHTML.
When setting up your site for the use of T610 cellular phones and its relatives, you must keep in mind that
the connection speed of the cellphone (models produced in 2004-2005) is quite low;
the memory of the cellphone is 4-10 MB, of which most is occupied by the user's SMS's, games, addresses, system software;
the cache file(s) of the cHTML browser accepts a maximum of one thep back
You will then have the choices:
To adopt your site to interoperability with handheld devices by upgrading to XHTML 1.1 and CSS 2.1 and using all kinds of tricks within your stylesheets and/or server-side scripting to ensure legibility in the cHTML browser and the screen media (typically desktop and laptop computers).
To start all over by writing pages targetting only the handheld devices.
I have tried both solutions. The first choice works sometimes, and sometimes it does not. In fact, most of the pages on this site cannot be accessed by the T610 mobile phone browser for reasons not yet understood (I even followed my own advice!).
Part of a politician's campaign for the Danish parliament Folketinget. No member of his party was elected on the general elections February 8, 2005. In Danish.
I did not write any of this. It is a good example of the surprising amount of old HTML 4.01 Transitional code that the cHTML browser still accepts. Ignore the option of screen resolution.
thomas : køhler
In the case of thomas : køhler, I trick the browser world by using the frameset page (www.thomaskohler.nu is based on frames). Screen based browsers processing HTML 2+ use this page only for drawing up the other frames. The default text is most often Sorry, your browser doesn't accept frames. Upgrade!. Since Sony Ericsson's browsers have a frames handicap and read this page, I use it for navigation purposes. The best impression will, though, be obtained at the start page for handheld devices, t : K - Start. (http://www.thomaskohler.nu/handheld/startside.html).
The above example is overloaded with meta tags to get a high score in the search engines. The next example is located just one level below the start page, and meta tagging is minimised to keep the file size low.
The number of meta tags has been kept low to minimize file size.
Comprising only 252 bytes (as of 2004-01-12), this stylesheet the one of the smallest files I have ever produced.