移动设备

的演示文稿，因此服务器提供浏览器告诉你的内容 支持。您可以使用Apache的常见来源，使用 mod_negotiation来确定要提供的内容，并将mod_publisher转换为 将您的标记转换为适当的格式。 - Nick KewUsers anywhere in Europe have a choice of devices. Many of them willmake that choice without knowing what "xhtml" or "wml" are, let aloneunderstanding the implications of their device supporting them.If you want to support such devices, offer a content-negotiated setof presentations, so the server serves what the browser tells you itsupports. You can do that from a common source with Apache, usingmod_negotiation to determine what to serve, and mod_publisher totransform your markup to the appropriate format.--Nick Kew 在西欧，我想在中欧也是如此，WAP 1 （WML）得到广泛支持。 几年以来是越来越多的支持WAP 2的gsm设备 （xhtml）。一些运营商也销售iMode访问（cHTML）......最后， 几部手机嵌入了真正的网络浏览器。 所有你需要知道的是您想要定位的受众群体，您要发布的内容类型等等。In western Europe, and I guess it''s the same in central Europe, WAP 1(WML) is widely supported.Since a few years there are more and more gsm devices that support WAP 2(xhtml). Some operators also sells iMode access(cHTML)... And at last,few phones embed a real web browser.All you need to know is what audience you want to target, what types ofcontent you want to publish, etc. In助手。 我做的最后一项工作是使用PartnerML - 沃达丰的（实际上是Bango'） 技术允许两个单平台创作几代 设备。您将服务器中的内容作为PartnerML提供，然后Voda的 堆栈根据需要将其转码为特定于手机的内容。 有点粗糙，标准较少比它应该稳定， 但它避免了对传统WML支持的需求。 就个人而言，对于网络工作，我不小心使用XHTML 1.0和良好的 基于CSS的流体设计，在可访问性方面付出了一些努力 方面。通过在网络堆栈中调整一点图像大小，这可以在类似PDA的设备上获得好的结果。 电话仍然无法浏览纸幅QUOT; - 他们只是没有屏幕 空间允许它。如果你正在构建一个应用程序（门票，比萨饼，出租车） 和你的_target_市场是手机，那么你仍然需要 使用非 - 主流非香草HTML技术来做到这一点。这是一个混乱的局面，你必须和网络提供商交谈才能知道'b $ b'真正支持的是什么。 如果您的用户是美国人，那么他们的神灵;帮助你 - 一如既往，他们的电话网络是一场噩梦。 WAP / WML还没有死，但谢天谢地，这已经足够了奄奄一息 和转码器包裹，很少有人在内容 创作中工作水平还是要担心它。 - Smert''spamionamIn flux.Last work I did was in PartnerML - Vodafone''s (actually Bango''s)technology to allow single-platform authoring for two generations ofdevices. You serve content from your server as PartnerML, then Voda''sstack transcodes it into phone-specific content, as required.Somewhat lumpy, and the standard is less stable than it ought to be,but it avoids the need for legacy WML support.Personally, for web work, I''m not careful to use XHTML 1.0 and goodCSS-based fluid design, with some effort placed on the accessibilityaspects. With a little image resizing in the network stack, this givesgood results on PDA-like devices.Phones still can''t "browse the web" - they just don''t have the screenspace to allow it. If you''re building an app (tickets, pizzas, taxis)and your _target_ market is phones, then you''re still going to have touse non-mainstream non-vanilla HTML techniques to do it. This is amess and you have to talk to the network provider to know what''sreally supported.And if your users are American, &deity; help you - as always, theirphone networks are a nightmare.WAP / WML isn''t dead yet, but thankfully it''s sufficiently moribundand transcoder-wrapped that few people working at the "contentauthoring" level still have to worry about it.--Smert'' spamionam 这篇关于移动设备的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！ 上岸，阿里云！