pretty mailman listinfo pages?

Mon Apr 21 10:41:15 UTC 2014

Le 2014-04-21 05:52, Felix Miata a écrit :
> On 2014-04-20 19:04 (GMT-0400) Ahmed Fathy Hussein composed:
> 
>> I'd like to help with this if possible. I've made a KDE themed HTML 
>> page of
>> kde-www listinfo page here
>> http://dl.dropboxusercontent.com/u/143005469/list.html
> 
>> Is that close to what you were expecting?
> 

[snipped]

> 
> The fix is conceptually rather simple: do not size text using px.

Units like px and pt are absolute units: they render inconsistently 
across devices; they depend on the pixel density of the display device. 
They create rigid, "frozen" text sizes in all versions of IE (that 
include IE9, IE10 and IE11). Font-size declarations with absolute unit 
do not scale with and do not match the users' preferred font size for 
normal body text.

One quote on this:

"
Top Ten Web Design Mistakes of 2005

For this year's list of worst design mistakes, I decided to try 
something new: I asked readers of my newsletter to nominate the 
usability problems they found the most irritating.
(...)
1. Legibility Problems
Bad fonts won the vote by a landslide, getting almost twice as many 
votes as the #2 mistake. About two-thirds of the voters complained about 
small font sizes or frozen font sizes;
"
https://web.archive.org/web/20051018031846/http://www.useit.com/alertbox/designmistakes.html

> Simply deleting lines 190 and 612 containing those font-size rules
> that set a px size on body and p at least in theory should be all
> that's required to fix it, though because of the enormous weight of
> that stylesheet there are surely some other font-size rules that need
> adjusting, at least for whatever pages use those rules. Deleting those
> two lines means body text and p text will render at the optimum size
> personalized as the user's browser default, which you can see
> simulated in the Firefox portion of the image.

More reading on that precise issue:

Adapatability is Accessibility by John Allsop
http://web.archive.org/web/20010124093700/http://www.alistapart.com/stories/dao/dao_3.html

http://alistapart.com/article/dao#section6

"
So what is the minimum point size we should use? None. Don't use points. 
This allows readers to choose the font size which suits them. The same 
goes even for pixels. Because of logical resolution differences, a pixel 
on one platform is not a pixel on another.
(...)
If you don't set a size for the text in the BODY, then the text of the 
BODY will be the size that the reader has chosen as their default size. 
Already we are aiding adaptability of our page, simply by doing nothing!
"

-------------

"
Avoid FONT SIZE settings for your normal body text. By definition, the 
browser's normal font size is supposed to be the most readable size for 
normal text. That's why browsers have a configuration setting to let the 
user choose a font size for normal text, so that they can choose one 
that is good for them.
"
Dan's Web Tips: Characters and Fonts (This page was first created 20 Jul 
1997)
http://webtips.dan.info/char.html

-------------

"
Browsers allow the user to set a default font size which will be applied 
to any font that is not given an explicit size by the displayed page. It 
is easy for the user to change this size after a page is displayed. Page 
designers can scale their fonts relative to this default size.
(...)
If you do not specify any font size at all (as on the pages you are 
reading), text will appear in the default size that was selected by the 
user.
"
Truth & Consequences of web site design
Font size
http://web.archive.org/web/20090529000800/http://pages.prodigy.net/chris_beall/TC/Font%20size.html

-------------

Getting started with practical web accessibility, section 1 Twelve 
simple rules:
Rule 10: Adjustable font size
http://www.cs.tut.fi/~jkorpela/acc/1.11.html

"
 From the accessibility point of view, the basic alternatives are, 
starting from the best:

1.  Do not set the font size at all (i.e., leave it to the browser and 
the user). This is in practice equivalent to setting body { font-size: 
100%; }.
"

and that is what that very website is doing too:

BODY    { background : #fbfffe;
           color : #000;
           font-size: 100%;
           margin: 0 0 0 0.0;
           padding: 0.4em 0.4em 0.4em 0.6em; }
at line 211 of
http://www.cs.tut.fi/~jkorpela/basic.css

-------------

comp.infosystems.www.authoring.stylesheets
Font-size : best format to use
Nick Theodorakis On Sun, 24 Nov 2002 20:50:20 -0000
"
For the main body text, specify no size and then the user will read at
his chosen default size.
"
Nick Theodorakis

comp.infosystems.www.authoring.stylesheets
Font-size : best format to use
Eric Jarvis On Sun, 24 Nov 2002 21:16:26 GMT
"
"leave it to the user's defaults and go with the flow"...the great
thing is that you NEVER need to check if it's readable for the 
user...they
already did that for you
"

> i'm not so sure...how many users actually know how to set their default
> fonts and sizes?  how many actually do it?  Perhaps not as many as you
> think...

But how many people _have to_? If browser default is good, why would I
change it (it wasn't so I changed it).

One thing's for sure: you don't know what default text size the reader
finds best[1], better than the reader knows for themself.

I don't think it really matters how many people have changed there font
size. What really matters is that those who have, have done so for a
reason.

https://groups.google.com/forum/#!topic/comp.infosystems.www.authoring.stylesheets/bDdenuFNaFQ/discussion

Gérard

> For more detail and overview of web page font sizing generally please 
> visit:
> https://web.archive.org/web/20080501114209/http://tobyinkster.co.uk/article/web-fonts/
> http://wm4.wilsonminer.com/posts/2008/oct/20/relative-readability/
> http://ia.net/blog/100e2r/?v=4
> http://www.w3.org/2003/07/30-font-size
> http://fm.no-ip.com/Auth/rudeweb.html

-- 
Konqueror Implementation Report of CSS 2.1 test suite (RC6): 9418 
testcases
http://www.gtalbot.org/BrowserBugsSection/Konqueror4Bugs/Konq-IR-CSS21TestSuite.html
53 Bugs in Konqueror 4.13.0
http://www.gtalbot.org/BrowserBugsSection/Konqueror4Bugs/
Contributions to the CSS 2.1 test suite
http://www.gtalbot.org/BrowserBugsSection/css21testsuite/
CSS 2.1 Test suite RC6, March 23rd 2011
http://test.csswg.org/suites/css2.1/20110323/html4/toc.html