Mailinglist Archive: opensuse-packaging (129 mails)

< Previous Next >
Re: [opensuse-packaging] release-notes-openSUSE requires google-opensans-fonts
Rick Salevsky composed on 2015-04-10 11:27 (UTC+0200):

On Fri, 2015-04-10 at 10:36 +0200, Richard Brown wrote:

Johannes Meixner wrote:

what is the reason that release-notes-openSUSE requires
google-opensans-fonts and dejavu-fonts?

There are zero comments in release-notes-openSUSE.spec or
release-notes-openSUSE.changes that could tell something
about why this requirement exists.

The use of Open Sans Fonts would be consistent with the openSUSE
branding guidelines... http://opensuse.github.io/branding-guidelines/

Absent heroic countermeasures, that particular page is useless except as a
demonstration how not to style a web page that anyone needs to be able to
read anything more than the largest headings on. Whatever A11Y & U7Y may be
there is well disguised.

Maybe the html version of the release notes is going in that direction?

Right, the HTML version needs the font. BTW, all openSUSE documentations
needs this font. So removing it is a bad Idea. ;)

There is no such thing is HTML needing any particular font. CSS may declare
the stylist's preference for some particular font, but HTML ultimately is
there for the reader, who may choose to have as little as one font available
for any purpose, and is the ultimate authority[1] whether a page's CSS should
have any effect at all. Wanting to not see any particular font otherwise
unncecessary is not justification for preventing installation of release notes.

IOW, suggests or recommends for Google's Opensans is OK, but not requires.

[1] http://www.w3.org/TR/CSS2/cascade.html#important-rules
--
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata *** http://fm.no-ip.com/
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-packaging+owner@xxxxxxxxxxxx

< Previous Next >