Oh, yes. You will note that the width on Chrome is different from Firefox. That is because they allocate a little different space per character. I will select a pivot font, like Arial, and compute width(Font)/width(Arial). In my first experiment that was constant across browsers. That will really slow things down, but if it gives us a browser invariant its worth it. My plan is this. Get a list of fonts from Adobe Edge Web Fonts. Run about 800 and build a distribution. We'll see how it looks. It sure would be good to get a list of these web fonts with the CSS support. Wayne On Fri, Apr 28, 2017 at 2:21 PM, Wayne Dick <wayneedick@gmail.com> wrote: > So, we are not dropping font forever. That really scarred me, a lot. > I have developed a font width program. > It is accurate to < 0.002px > http://nosetothepage.org/fontWidth.html > > It is slow to get accurate values. If is based on the following fact: > > If P is a paragraph element with text T. P is set to breaks words as soon > as it runs out of space -just break words. That means every line has the > same length. Then P has the same area no matter what the height and width > of P may be. > > That took some proving but it is true. > > Wayne > > > > > On Fri, Apr 28, 2017 at 5:37 AM, Laura Carlson < > laura.lee.carlson@gmail.com> wrote: > >> Hi Alastair and all, >> >> On 4/28/17, Alastair Campbell <acampbell@nomensa.com> wrote: >> > I think we are still bumping up against a failure to translate >> > user-requirements to content-requirements. >> >> Yes. >> >> > I’ve put these in a wiki page: >> > https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Text_adapt >> ation_user_to_content_requirements >> >> Thank you! >> >> Kindest Regards, >> Laura >> >> -- >> Laura L. Carlson >> > >
Received on Friday, 28 April 2017 21:34:40 UTC