John, you said:
but if you read what I wrote, you'll see that I'm NOT receptive to his suggestion.I made the same suggestion Dan did (just with some illustrative code) which you seemed to be very receptive to when coming from him (I am sorry I don't have a banner next to my name but perhaps someday I will be so endowed) -
In my target audience, the split is about 50-50. About half of our target audience have the latest and greatest... cell phones, blackberries, pda's that will wipe your butt for you. These will render html just fine. The other half have dash mounted systems (cars, boats, rv's, etc) or handheld systems or custom mapping devices. They render wml.With mobile user agents, it will really depend on what your target audience is.
If the people you expect to be using your mobile site have the latest and greatest in technology, and can actualy support HTML/CSS, then go for it. If instead they're using old clunkers that need a lot of hand-holding, go with the WAP/WML route.
This is not a design issue. It's not a content issue.
My problem is how to accurately detect which device wants which language.