google/fonts
1
0
Fork 0
mirror of https://github.com/google/fonts.git synced 2024-12-01 03:06:03 +03:00
Code Issues Projects Releases Wiki Activity

Fix cross links. (#5232)

Browse Source
This commit is contained in:
Andrew John 2022-09-13 17:59:02 -07:00 committed by GitHub
parent fd32eafcd4
commit 8a0bcb2e6f
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
4 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
cc-by-sa/knowledge/glossary/terms/placeholder_text/content.md
View File

@ -9,4 +9,4 @@ The term can also mean display of placeholder text that is rendered as gray bars
</figure>
The purpose of any placeholder text, including lorem ipsum, is to indicate that the text is not there to be read, which is why it’s used in design mockups, where the viewer should be focussing on the overall design, and in type specimens, where the reader should be focussing on the [characters](/glossary/character)’s personality and design, and overall [typographic color](color).
The purpose of any placeholder text, including lorem ipsum, is to indicate that the text is not there to be read, which is why it’s used in design mockups, where the viewer should be focussing on the overall design, and in type specimens, where the reader should be focussing on the [characters](/glossary/character)’s personality and design, and overall [typographic color](/glossary/color).

2
cc-by-sa/knowledge/glossary/terms/superscript_subscript/content.md
View File

@ -17,4 +17,4 @@ Superscript and subscript can be easily applied to text with controls in most us
</figure>
Although it’s possible for software to synthesize the smaller sizes, it’s best to use the correct superscript and subscript [glyphs](/glossary/glyph) in a [font](/glossary/font) file, if they exist—much like [avoiding faux small caps](/lesson/choosing_type/choosing_reliable_typefaces).
Although it’s possible for software to synthesize the smaller sizes, it’s best to use the correct superscript and subscript [glyphs](/glossary/glyph) in a [font](/glossary/font) file, if they exist—much like [avoiding faux small caps](/lesson/choosing_reliable_typefaces).

2
cc-by-sa/knowledge/modules/choosing_type/lessons/a_checklist_for_choosing_type/content.md
View File

@ -113,7 +113,7 @@ The default characters we see in a typeface aren’t necessarily the only option
While sometimes these are available as separate sibling families, such as [Montserrat](https://fonts.google.com/specimen/Montserrat) and [Montserrat Alternates](https://fonts.google.com/specimen/Montserrat+Alternates), they’re typically made available to us as [OpenType](/glossary/open_type) features within a single font file.
There’s so much typographic power to unlock via OpenType if the features exist within the font: From [swash glyphs](swash_glyph) that add flourish to your [display](/glossary/display) type, to [fractions](/glossary/fractions) that enable legible recipe ingredients; from proper [small caps](small_caps) that prevent abbreviations from appearing to shout at the reader, to intentional control over [the different flavors of numerals](/glossary/numerals_figures); an understanding of OpenType is arguably one of the greatest tools a designer can have.
There’s so much typographic power to unlock via OpenType if the features exist within the font: From [swash glyphs](/glossary/swash_glyph) that add flourish to your [display](/glossary/display) type, to [fractions](/glossary/fractions) that enable legible recipe ingredients; from proper [small caps](/glossary/small_caps) that prevent abbreviations from appearing to shout at the reader, to intentional control over [the different flavors of numerals](/glossary/numerals_figures); an understanding of OpenType is arguably one of the greatest tools a designer can have.
<figure>

2
cc-by-sa/knowledge/modules/using_type/lessons/avoiding_widows_orphans/content.md
View File

@ -10,7 +10,7 @@ Because they occur frequently when setting long-form text, it’s useful to know
</figure>
Like so many things in [typography](/glossary/typography), avoiding widows and orphans means [breaking the rules](/lesson/using_type/breaking_the_rules) a little. For instance, while it might be technically correct to have just one word at the end of a line, it creates an undesirable amount of whitespace to the right of that word (in left-aligned text). It's more pleasing to the eye if we push one more word from the penultimate line down to the last.
Like so many things in [typography](/glossary/typography), avoiding widows and orphans means [breaking the rules](/lesson/breaking_the_rules) a little. For instance, while it might be technically correct to have just one word at the end of a line, it creates an undesirable amount of whitespace to the right of that word (in left-aligned text). It's more pleasing to the eye if we push one more word from the penultimate line down to the last.
Beware, though: Creating a line break like this inserts a break character permanently, meaning it will come along for the ride if a user copies and pastes our text. So we need to choose between a hard line break or a non-breaking space. We’ll use a hard line break if we intend the line to break at that very point in all circumstances, or a non-breaking space if we intend the last two words in a paragraph to stay together.