1
0
mirror of https://github.com/google/fonts.git synced 2024-12-19 06:41:31 +03:00
fonts/cc-by-sa/knowledge/glossary/terms/all_caps/content.md
2022-03-28 12:02:37 -07:00

12 lines
1.2 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

When [text](/glossary/text_copy) is set in only [uppercase](/glossary/uppercase_lowercase) letters, its commonly abbreviated as all-caps. All-caps text can be hard to read unless that text is very short, so its best to keep it brief, such as for titles or emphasis. Dont use it for [body](/glossary/body) text. At any but the larger sizes, we often add additional [tracking/letter-spacing](/glossary/tracking_letter_spacing) to all-caps type thats longer than two or three characters—this helps improve overall readability.
<figure>
![The phrase “QUIET is the new LOUD”. The all-caps word “QUIET" set in large type requires no tracking. The all-caps word “LOUD"—set much smaller—has additional tracking to aid readability. Lines highlight this setting.](images/thumbnail.svg)
<figcaption>The all-caps word “QUIET" set in large type requires no tracking. The all-caps word “LOUD"—set much smaller—has additional tracking to aid readability.</figcaption>
</figure>
If you have to use uppercase text within body text, consider using [small caps](/glossary/small_caps). Small caps are designed to feel more at home with the rest of the lowercase type and won't “shout” so much at the reader.