惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

WordPress大学
WordPress大学
Security Latest
Security Latest
C
Cisco Blogs
P
Palo Alto Networks Blog
Know Your Adversary
Know Your Adversary
Project Zero
Project Zero
C
Cyber Attacks, Cyber Crime and Cyber Security
NISL@THU
NISL@THU
Exploit-DB.com RSS Feed
Exploit-DB.com RSS Feed
S
Secure Thoughts
P
Privacy International News Feed
V
Vulnerabilities – Threatpost
D
Docker
Google Online Security Blog
Google Online Security Blog
K
KPMG report finds enterprise disconnect between AI and its ROI | CIO
Recent Announcements
Recent Announcements
T
The Exploit Database - CXSecurity.com
G
Google Developers Blog
Schneier on Security
Schneier on Security
小众软件
小众软件
爱范儿
爱范儿
GbyAI
GbyAI
J
Java Code Geeks
T
Tailwind CSS Blog
Cisco Talos Blog
Cisco Talos Blog
The Hacker News
The Hacker News
D
DataBreaches.Net
Blog — PlanetScale
Blog — PlanetScale
TaoSecurity Blog
TaoSecurity Blog
MyScale Blog
MyScale Blog
B
Blog RSS Feed
Cyberwarzone
Cyberwarzone
有赞技术团队
有赞技术团队
Martin Fowler
Martin Fowler
C
CXSECURITY Database RSS Feed - CXSecurity.com
S
Securelist
L
Lohrmann on Cybersecurity
cs.CL updates on arXiv.org
cs.CL updates on arXiv.org
Y
Y Combinator Blog
S
Schneier on Security
Latest news
Latest news
Apple Machine Learning Research
Apple Machine Learning Research
博客园 - 叶小钗
F
Fortinet All Blogs
M
MIT News - Artificial intelligence
PCI Perspectives
PCI Perspectives
V
V2EX
V2EX - 技术
V2EX - 技术
O
OpenAI News
W
WeLiveSecurity

fantasai: Weblog

Change of Affiliation Thoughts on the W3C’s May 2020 Advisory Board Election fantasai 69: Process 2020 Revision Thoughts on the W3C’s May 2019 Advisory Board Election Running for the W3C Advisory Board Designing CSS Thoughts on the May 2018 W3C Advisory Board Election Environmental Sustainability Recommendations for Mountain View Buildings fantasai 63: The Way of Music fantasai 62: How To Wash Dishes Open Letter on the Iran Nuclear Deal Recipe for a Minimum Viable Kitchen Creating a Paid Contributor Agreement for Mozilla On Brendan Eich and the Separation of Concerns fantasai 57: 2012 TAG Election Endorsements fantasai 56: Approaching UTR50 Evolution of CSS Layout Job Description of a Standards Engineer fantasai 52: about:csswg fantasai 53: W3C Process Holes fantasai 51: about:fantasai fantasai 50: Hiatus E Pluribus Unum Towards a Unified Ruby Model Creating the Future of CSS Testing (2011 Edition) Creating the Future of CSS Testing (2009 Edition) CSS2.1 and the Case for Collaborative Testing Introducing Brad Kemper, CSSWG Invited Expert fantasai 44: Layout Is Expensive CSS Working Group Charter 2008 fantasai 42: Riddle of the Universe Pulling Back the Curtain: Opening Up the CSS Working Group What is the CSS Working Group doing? The True Story of mpt and fantasai fantasai 38: Long Vacation fantasai 37: CSS3 Text Evolutions fantasai 36: What is Mozilla? fantasai 34: Empty fantasai 33: When to use PDF fantasai 32: Revised CSS3 Text fantasai 31: The Art of Semantics fantasai 30: Travel Notes fantasai 29: Filibuster Frist fantasai 28: UTN 22 fantasai 27: SSSS fantasai 26: CSS and Multi-Script Text fantasai 25: Free As in Freedom fantasai 24: The Law of Hospitality fantasai 23: Organizing the Documentation Effort fantasai 22: Yom Kippur fantasai 21: Firefox and Switching Styles Link Types for RSS and Atom Feeds fantasai 19: An Absence of Aesthetics Sitting on the Outside, Looking Up fantasai 17: A Touch of Class fantasai 16: Task Force fantasai 15: W3 fantasai 13: A Stitch in Time fantasai 11: What Is Love Content and Hype (English Composition for Marketers) fantasai 10: Reviewer at Small fantasai 09: Losing it fantasai 08: Personality Type fantasai 07: Happiness fantasai 06: Moving fantasai 05: Black Tuesday fantasai 03: Words of Wisdom fantasai 01: Why validate your pages? fantasai 00: Experiment
fantasai 02: Big and Small
2003-03-30 · via fantasai: Weblog

2003-03-29

In HTML, <big> and <small> were designed as presentational elements, and for the most part, that's how they are used--to alter font size. It's better to use semantic elements such as headers, emphasis, and classes, combined with style sheets for stylistic control. Therefore, using <big> and <small> is discouraged. But what should I do if I want something to really be big? I don't want it stressed or emphasized, I want it Big! *throws hands apart in the gesture that originated *. They're not the same -- if you've ever played in an orchestra you know what I mean. When the conductor says "Make it big!" s/he doesn't mean "Put some emphasis on it." >This< *jabs air* is emphasis. It's not big. Forte is big. This is sharp. It's like the little v-shaped 'hat' accent. –This– *moves tensed hands slightly forward and out* is stress. It's not big. It's pushed in and stretched full, like the horizontal-angle accent.

My argument isn't completely irrelevant, btw. I'm thinking of how one should mark up something like the two phrases at the end of http://www.mozilla.org/docs/refList/i18n/. (Read it. It's interesting.) Of course I could assign an ID to each of them and associate "big" CSS with them that way, but that's little better than using a style attribute. They're not specially styled because they're "one-codebase" and "another-language". They're not styled because they're "catchy-phrase"s. They're styled large and blue because the author wanted them "big". (There! Notice the color; it's not just a font size change.) The bigness makes a difference. Compare

The End.

to

The End.

It has a different, and not entirely media dependent, effect.

Probably the best one could do is <strong class="big">, since "strong" comes close, even though "emphasis" doesn't cut it. (This won't work for <small>, though.)

Why do I insist on size, which technically is physical, rather than accent or importance? Size has a different connotation, as I've pointed out above. Those phrases are not meant to stand up and shout for your attention like the self-important warning at the top of http://www.mozilla.org/bugs/ (which should be marked up as "important"). They're a loud and forceful and memorable conclusion to the text. If I styled them in italics or otherwise simply <em>phasized them they wouldn't be so loud. They'd just be a few dinky phrases at the end of an essay, and I wouldn't have remembered them for months and months.


So, what's an excuse for <small>?

I wish you'd update more often.. Even though I never update myself. *hides*

It's actually a pattern I encounter more often than "big". The pattern, I said, not the text! *runs away*

1.2.1 Read the text before designing it.

The typographer's one essential task is to interpret and communicate the text. It's tone, its tempo, its logical structure, its physical size, all determine the possibilities of its typographic form. The typographer is to the text as the theatrical director to the script, or the musician to the score.

Robert Bringhurst, The Elements of Typographic Style