Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Commit aaf0b0a

Browse filesBrowse files
committed
Reword sentences to be more formal
1 parent 6ffc56e commit aaf0b0a
Copy full SHA for aaf0b0a

File tree

Expand file treeCollapse file tree

1 file changed

+8
-7
lines changed
Filter options
Expand file treeCollapse file tree

1 file changed

+8
-7
lines changed

‎doc/users/fonts.rst

Copy file name to clipboardExpand all lines: doc/users/fonts.rst
+8-7Lines changed: 8 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -134,7 +134,7 @@ Are we reinventing the wheel?
134134
Internally, a feasible response to the question of 'reinventing the
135135
wheel would be, well, Yes *and No*. The font-matching algorithm used
136136
by Matplotlib has been *inspired* by web browsers, more specifically,
137-
`CSS Specifications <http://www.w3.org/TR/1998/REC-CSS2-19980512/>`_!
137+
`CSS Specifications <http://www.w3.org/TR/1998/REC-CSS2-19980512/>`_.
138138

139139
Currently, the simplest way (and the only way) to tell Matplotlib what fonts
140140
you want it to use for your document is via the **font.family** rcParam,
@@ -144,7 +144,7 @@ This is similar to how one tells a browser to use multiple font families
144144
(specified in their order of preference) for their HTML webpages. By using
145145
**font-family** in their stylesheet, users can essentially trigger a very
146146
useful feature provided by browers, known as Font-Fallback. For example, the
147-
following snippet in an HTMl markup would:
147+
following snippet in an HTML markup would:
148148

149149
.. code-block:: html
150150

@@ -163,14 +163,15 @@ following snippet in an HTMl markup would:
163163
For every character/glyph in *"some text"*, the browser will iterate through
164164
the whole list of font-families, and check whether that character/glyph is
165165
available in that font-family. As soon as a font is found which has the
166-
required glyph(s), the browser moves on to the next character.
166+
required glyph(s), the browser uses that font to render that character, and
167+
subsequently moves on to the next character.
167168

168169
How does Matplotlib achieve this?
169170
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
170-
Well, Matplotlib doesn't achieve this, *yet*. It was initially only designed to
171-
use a **single font** throughout the document, i.e., no matter how many
172-
families you pass to **font.family** rcParam, Matplotlib would use the very
173-
first font it's able to find on your system, and try to render all your
171+
Currently, Matplotlib can't render a multi-font document. It was initially
172+
only designed to use a **single font** throughout the document, i.e., no matter
173+
how many families you pass to **font.family** rcParam, Matplotlib would use the
174+
very first font it's able to find on your system, and try to render all your
174175
characters/glyphs from that *and only that* font.
175176

176177
.. note::

0 commit comments

Comments
0 (0)
Morty Proxy This is a proxified and sanitized view of the page, visit original site.