Basic support is already there - all that's needed is a style sheet. Someone would still have to do it - remember that this is an open-source project developed in great part by volunteers. -- F.

Hi, Making a website "magically" work on all mobile phones is certainly not as easy as "flicking a switch". Despite the widespread belief among developers that have not actually worked with mobile browsers, even serving a scaled-down XHTML-MP version of the markup would not solve the problem fully. There is still huge fragmentation among device manufacturers, browser software developers, and network operators, which means there is a wide variety of support (or lack of) for markup standards. This means a developer has to adapt her markup to various subsets of cHTML, WML, and XHTML-MP based on the User-Agent accessing the site. If someone were to undertake such a project for mediawiki, I'd suggest using libraries such as WURFL (wurfl.sf.net), a project which attempts to document devices' capability trees in a structured fashion, and WALL-4-PHP (wall.laacz.lv), a project which uses the WURFL to adapt the output markup based on the client's User-Agent. This would require building a skin that uses WALL-4-PHP's tag markup exclusively. Another approach is to use an existing transcoder that makes a best-effort to convert web pages into markup that will render on the phone. Two examples are Skweezer (commercial) and Phonifier (open source): -- Skweezer: http://www.skweezer.net/ http://www.skweezer.net/s.aspx/-/en~wikipedia~org/wiki/Tropical_Storm_Allis… -- Phonifier: http://www.phonifier.com/ http://www.phonifier.com/phonify.php?i=1&m=1&u=http%3A%2F%2Fen.wiki… Because mediawiki's output markup is well structured, both transcoders do a very good job of transcoding the markup. Anyway, those are my $0.02. I've dealt extensively with mobile browser incompatibility and the headaches of multiserving N-markups for mobile content, and I don't think this problem is as simple as people are making it out to be. Best, Garth On Dec 19, 2007 10:24 AM, Joseph Hagerty <revjoe(a)revjoe.com> wrote:

On Thu, 2007-12-20 at 20:23 +1100, Angela wrote: Because it shows up as #4 in the SERP for "wap wikipedia", while en.wap.wikipedia.org shows up #69, well below the fold. -- David A. Desrosiers desrod(a)gnu-designs.com Skype...: 860-967-3820

Angela wrote: Probably because they don't know that it exists. It isn't linked from www.wikipedia.org or en.wikipedia.org ; I haven't noticed any news release about the subdomain; there isn't even anything on Meta but http://meta.wikimedia.org/wiki/Mobile_subdomain and from it it couldn't even be seen that the proposal is actually implemented. Links on main pages and perhaps <link rel="handheld"> links on every MediaWiki page would help.