[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [bug #35614] mobile-phone friendly HTML output
|
From: |
Patrice Dumas |
|
Subject: |
Re: [bug #35614] mobile-phone friendly HTML output |
|
Date: |
Sat, 25 Feb 2012 14:02:04 +0100 |
|
User-agent: |
Mutt/1.4.2.2i |
On Fri, Feb 24, 2012 at 03:12:04PM -0800, Karl Berry wrote:
> it will be grateful if there is a way to insert custom <meta>.
>
> Indeed. I kind of think there is already, in the development makeinfo
> -- Patrice?
In fact, in the CVS version of makeinfo there are customization variables
for all the cases exposed here. In meta, it is EXTRA_HEAD, after <body> it
is AFTER_BODY_OPEN, before body close it is PRE_BODY_CLOSE.
> Not hardcoded, but I surmise we should make a configuration variable to
> output such recommended boilerplate stuff, since presumably it will
> change over time.
<meta name="HandheldFriendly" content="True">
<meta name="MobileOptimized" content="320">
<meta name="viewport" content="width=device-width">
<meta http-equiv="cleartype" content="on">
Looks quite wrong to me. There is no information pertaining to the
document generated here, it is information on the reading device. That is
not the way HTML should be used in my opinion. Maybe the
<meta name="HandheldFriendly" content="True">
could be used everytime if the document generated is indeed HandheldFriendly
but the other look wrong. Is there a page describing the norm behind
names such as HandheldFriendly, or http-equiv="cleartype"? I have found
something on http://www.w3.org/TR/mwabp/ on viewport, but that still looks so
wrong to me.
What seems correct to me is to assume that the HTML generated follows
http://www.w3.org/TR/mobile-bp/#d0e630
which we follow except for avoiding using tables. I'll have a look at that.
If you know about a standalone mobileOk validator, I could use that too
to check that we produce mobileok html, and, if not we could add a
customization variable to produce mobileok HTML.
> 2. "Reader" feature in Safari 5.x.
> [...]
> Replace every occurrence of "<body>" and "</body>" in html.c,
> makeinfo.c, and node.c into "<body><article>" and "</article><body>".
>
> Well, it would seem that could be done with @html, then. Anyway, since
> the iphone is so ridiculously nonfree, I don't think we should insert
> any support for it into the distribution.
More to the point, we should only output conformant HTML. Now if there
is a preferably open format which is HTML except has an article tag, we can
output that too.
--
Pat