I will certainly add it but could you explain what difference it
makes? Does this fix the "font boosting" issue?
It should help (as noted), yes. The practical result is that mobile
devices skip the step of laying out the page with a large size and then
shrinking it, but just render it
I am no expert, but yes, I think it does. I added that to some other
website and the fonts were consistently sized. (I've since changed the site
to do something different, but it definitely helped.)
I'll test it out soon.
On Fri, Mar 27, 2020 at 4:08 AM Gavin Smith
wrote:
> On Thu, Mar 26,
On Fri, Mar 27, 2020 at 11:07 AM Gavin Smith wrote:
> I will certainly add it but could you explain what difference it
> makes? Does this fix the "font boosting" issue?
> (https://lists.gnu.org/archive/html/bug-texinfo/2019-06/msg0.html)
Done in commit 2509d615c.
On Thu, Mar 26, 2020 at 10:56 PM Karl Berry wrote:
>
> Gavin - I suggest adding
>
> to the standard HTML ... block. This will make the result
> noticeably better on mobile/pads and is, so far as I have seen, harmless
> on larger screens.
>
> It looks like this would be in
Gavin - I suggest adding
to the standard HTML ... block. This will make the result
noticeably better on mobile/pads and is, so far as I have seen, harmless
on larger screens.
It looks like this would be in tp/Texinfo/Convert/HTML.pm,
where the charset http-equiv is output. FWIW ... --best, karl.