tonsky/FiraCode
1
1
Fork 0
mirror of https://github.com/tonsky/FiraCode.git synced 2024-07-07 09:26:27 +03:00
Code Issues Projects Releases Wiki Activity

Merge pull request #1366 from jsoref/spelling

Browse Source 
Spelling
This commit is contained in:
Nikita Prokopov 2022-02-07 19:33:55 +01:00 committed by GitHub
commit 383835769c
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
14 changed files with 56 additions and 56 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
CHANGELOG.md
View File

@ -21,7 +21,7 @@ Unicode:
- Added U+220E End of Proof `∎` #1115
- Added U+FFFD Replacement Character `<60>` #1137, thanks @gjvnq
- Added U+EE00..U+EE0B Progress Bar `` #1182
- Added U+2237 Propotion `∷` #1219
- Added U+2237 Proportion `∷` #1219
- Added U+21AA Rightwards Arrow with Hook `↪` #1307
Changed:
@ -265,7 +265,7 @@ Removed 44 individual arrow ligatures, replaced with four universal, combinative
#### 1.102
- Support for IntelliJ-based IDEs ([instructions](https://github.com/tonsky/FiraCode/wiki/Intellij-products-instructions))
- Support for IntelliJ-based IDEs ([instructions](https://github.com/tonsky/FiraCode/wiki/IntelliJ-products-instructions))
- Turned on autohinting
#### 1.101

16
README.md
View File

@ -78,14 +78,14 @@ Unicode coverage makes Fira Code a great choice for mathematical writing:
| Works | Doesn’t work |
|-------|----------------|
| **Abricotine** | **Arduino IDE** |
| **Android Studio** (2.3+, [instructions](https://github.com/tonsky/FiraCode/wiki/Intellij-products-instructions)) | **Adobe Dreamweaver** |
| **Android Studio** (2.3+, [instructions](https://github.com/tonsky/FiraCode/wiki/IntelliJ-products-instructions)) | **Adobe Dreamweaver** |
| **Anjuta** (unless at the EOF) | **Delphi IDE** |
| **AppCode** (2016.2+, [instructions](https://github.com/tonsky/FiraCode/wiki/Intellij-products-instructions)) | Standalone **Emacs** ([workaround](https://github.com/tonsky/FiraCode/wiki/Emacs-instructions)) |
| **AppCode** (2016.2+, [instructions](https://github.com/tonsky/FiraCode/wiki/IntelliJ-products-instructions)) | Standalone **Emacs** ([workaround](https://github.com/tonsky/FiraCode/wiki/Emacs-instructions)) |
| **Atom** 1.1 or newer ([instructions](https://github.com/tonsky/FiraCode/wiki/Atom-instructions)) | **Godot** ([issue](https://github.com/godotengine/godot/issues/9961)) |
| **BBEdit/TextWrangler** (v. 11 only, [instructions](https://github.com/tonsky/FiraCode/wiki/BBEdit-instructions)) | **IDLE** |
| **Brackets** (with [this plugin](https://github.com/polo2ro/firacode-in-brackets)) | **KDevelop 4** |
| **Chocolat** | **Monkey Studio IDE** |
| **CLion** (2016.2+, [instructions](https://github.com/tonsky/FiraCode/wiki/Intellij-products-instructions)) | **UltraEdit** |
| **CLion** (2016.2+, [instructions](https://github.com/tonsky/FiraCode/wiki/IntelliJ-products-instructions)) | **UltraEdit** |
| **Cloud9** ([instructions](https://github.com/tonsky/FiraCode/wiki/Cloud9-Instructions)) |
| **Coda 2** |
| **CodeLite** |
@ -98,7 +98,7 @@ Unicode coverage makes Fira Code a great choice for mathematical writing:
| **GNOME Builder** |
| **GoormIDE** ([instructions](https://github.com/tonsky/FiraCode/wiki/GoormIDE-Instructions)) |
| **gVim** ([Windows](https://github.com/tonsky/FiraCode/issues/462), [GTK](https://vimhelp.org/options.txt.html#%27guiligatures%27)) |
| **IntelliJ IDEA** (2016.2+, [instructions](https://github.com/tonsky/FiraCode/wiki/Intellij-products-instructions)) |
| **IntelliJ IDEA** (2016.2+, [instructions](https://github.com/tonsky/FiraCode/wiki/IntelliJ-products-instructions)) |
| **Kate, KWrite** |
| **KDevelop 5+** |
| **Komodo** |
@ -117,13 +117,13 @@ Unicode coverage makes Fira Code a great choice for mathematical writing:
| **Notepad++** (with a [workaround](https://github.com/notepad-plus-plus/notepad-plus-plus/issues/2287#issuecomment-256638098)) |
| **Notepad3** ([instructions](https://github.com/rizonesoft/Notepad3/issues/361#issuecomment-365977420))|
| **Nova** |
| **PhpStorm** (2016.2+, [instructions](https://github.com/tonsky/FiraCode/wiki/Intellij-products-instructions)) |
| **PyCharm** (2016.2+, [instructions](https://github.com/tonsky/FiraCode/wiki/Intellij-products-instructions)) |
| **PhpStorm** (2016.2+, [instructions](https://github.com/tonsky/FiraCode/wiki/IntelliJ-products-instructions)) |
| **PyCharm** (2016.2+, [instructions](https://github.com/tonsky/FiraCode/wiki/IntelliJ-products-instructions)) |
| **QOwnNotes** (21.16.6+) |
| **QtCreator** |
| **Rider** |
| **RStudio** ([instructions](https://github.com/tonsky/FiraCode/wiki/RStudio-instructions)) |
| **RubyMine** (2016.2+, [instructions](https://github.com/tonsky/FiraCode/wiki/Intellij-products-instructions)) |
| **RubyMine** (2016.2+, [instructions](https://github.com/tonsky/FiraCode/wiki/IntelliJ-products-instructions)) |
| **Scratch** |
| **Scribus** (1.5.3+) |
| **SublimeText** (3146+) |
@ -136,7 +136,7 @@ Unicode coverage makes Fira Code a great choice for mathematical writing:
| **VimR** ([instructions](https://github.com/qvacua/vimr/wiki#ligatures)) |
| **Visual Studio** (2015+, [instructions](https://github.com/tonsky/FiraCode/wiki/Visual-Studio-Instructions)) |
| **Visual Studio Code** ([instructions](https://github.com/tonsky/FiraCode/wiki/VS-Code-Instructions)) |
| **WebStorm** (2016.2+, [instructions](https://github.com/tonsky/FiraCode/wiki/Intellij-products-instructions)) |
| **WebStorm** (2016.2+, [instructions](https://github.com/tonsky/FiraCode/wiki/IntelliJ-products-instructions)) |
| **Xamarin Studio/Monodevelop** |
| **Xcode** (8.0+, otherwise [with plugin](https://github.com/robertvojta/LigatureXcodePlugin)) |
| **Xi** |

16
README_CN.md
View File

@ -75,14 +75,14 @@ Unicode 覆盖使 Fira Code 成为数学写作的绝佳选择：
| Works | Doesn’t work |
|-------|----------------|
| **Abricotine** | **Arduino IDE** |
| **Android Studio** (2.3+, [instructions](https://github.com/tonsky/FiraCode/wiki/Intellij-products-instructions)) | **Adobe Dreamweaver** |
| **Android Studio** (2.3+, [instructions](https://github.com/tonsky/FiraCode/wiki/IntelliJ-products-instructions)) | **Adobe Dreamweaver** |
| **Anjuta** (unless at the EOF) | **Delphi IDE** |
| **AppCode** (2016.2+, [instructions](https://github.com/tonsky/FiraCode/wiki/Intellij-products-instructions)) | Standalone **Emacs** ([workaround](https://github.com/tonsky/FiraCode/wiki/Emacs-instructions)) |
| **AppCode** (2016.2+, [instructions](https://github.com/tonsky/FiraCode/wiki/IntelliJ-products-instructions)) | Standalone **Emacs** ([workaround](https://github.com/tonsky/FiraCode/wiki/Emacs-instructions)) |
| **Atom** 1.1 or newer ([instructions](https://github.com/tonsky/FiraCode/wiki/Atom-instructions)) | **Godot** ([issue](https://github.com/godotengine/godot/issues/9961)) |
| **BBEdit/TextWrangler** (v. 11 only, [instructions](https://github.com/tonsky/FiraCode/wiki/BBEdit-instructions)) | **IDLE** |
| **Brackets** (with [this plugin](https://github.com/polo2ro/firacode-in-brackets)) | **KDevelop 4** |
| **Chocolat** | **Monkey Studio IDE** |
| **CLion** (2016.2+, [instructions](https://github.com/tonsky/FiraCode/wiki/Intellij-products-instructions)) | **UltraEdit** |
| **CLion** (2016.2+, [instructions](https://github.com/tonsky/FiraCode/wiki/IntelliJ-products-instructions)) | **UltraEdit** |
| **Cloud9** ([instructions](https://github.com/tonsky/FiraCode/wiki/Cloud9-Instructions)) |
| **Coda 2** |
| **CodeLite** |
@ -95,7 +95,7 @@ Unicode 覆盖使 Fira Code 成为数学写作的绝佳选择：
| **GNOME Builder** |
| **GoormIDE** ([instructions](https://github.com/tonsky/FiraCode/wiki/GoormIDE-Instructions)) |
| **gVim** ([Windows](https://github.com/tonsky/FiraCode/issues/462), [GTK](https://vimhelp.org/options.txt.html#%27guiligatures%27)) |
| **IntelliJ IDEA** (2016.2+, [instructions](https://github.com/tonsky/FiraCode/wiki/Intellij-products-instructions)) |
| **IntelliJ IDEA** (2016.2+, [instructions](https://github.com/tonsky/FiraCode/wiki/IntelliJ-products-instructions)) |
| **Kate, KWrite** |
| **KDevelop 5+** |
| **Komodo** |
@ -114,13 +114,13 @@ Unicode 覆盖使 Fira Code 成为数学写作的绝佳选择：
| **Notepad++** (with a [workaround](https://github.com/notepad-plus-plus/notepad-plus-plus/issues/2287#issuecomment-256638098)) |
| **Notepad3** ([instructions](https://github.com/rizonesoft/Notepad3/issues/361#issuecomment-365977420))|
| **Nova** |
| **PhpStorm** (2016.2+, [instructions](https://github.com/tonsky/FiraCode/wiki/Intellij-products-instructions)) |
| **PyCharm** (2016.2+, [instructions](https://github.com/tonsky/FiraCode/wiki/Intellij-products-instructions)) |
| **PhpStorm** (2016.2+, [instructions](https://github.com/tonsky/FiraCode/wiki/IntelliJ-products-instructions)) |
| **PyCharm** (2016.2+, [instructions](https://github.com/tonsky/FiraCode/wiki/IntelliJ-products-instructions)) |
| **QOwnNotes** (21.16.6+) |
| **QtCreator** |
| **Rider** |
| **RStudio** ([instructions](https://github.com/tonsky/FiraCode/wiki/RStudio-instructions)) |
| **RubyMine** (2016.2+, [instructions](https://github.com/tonsky/FiraCode/wiki/Intellij-products-instructions)) |
| **RubyMine** (2016.2+, [instructions](https://github.com/tonsky/FiraCode/wiki/IntelliJ-products-instructions)) |
| **Scratch** |
| **Scribus** (1.5.3+) |
| **SublimeText** (3146+) |
@ -132,7 +132,7 @@ Unicode 覆盖使 Fira Code 成为数学写作的绝佳选择：
| **VimR** ([instructions](https://github.com/qvacua/vimr/wiki#ligatures)) |
| **Visual Studio** (2015+, [instructions](https://github.com/tonsky/FiraCode/wiki/Visual-Studio-Instructions)) |
| **Visual Studio Code** ([instructions](https://github.com/tonsky/FiraCode/wiki/VS-Code-Instructions)) |
| **WebStorm** (2016.2+, [instructions](https://github.com/tonsky/FiraCode/wiki/Intellij-products-instructions)) |
| **WebStorm** (2016.2+, [instructions](https://github.com/tonsky/FiraCode/wiki/IntelliJ-products-instructions)) |
| **Xamarin Studio/Monodevelop** |
| **Xcode** (8.0+, otherwise [with plugin](https://github.com/robertvojta/LigatureXcodePlugin)) |
| **Xi** |

2
distr/README.txt
View File

@ -476,7 +476,7 @@ In a workspace:
font-family: 'Fira Code';
}
4. Click Aplly or OK
4. Click Apply or OK
5. Happy coding!

2
features/calt/conj_disj.fea
View File

@ -1,4 +1,4 @@
### Logical conjuntion/disjunction #738
### Logical conjunction/disjunction #738
lookup slash_backslash {
ignore sub @NotSpace slash' backslash;

10
googlefonts-qa/checks/FiraCode-Light.checks.md
View File

@ -53,7 +53,7 @@ Fontbakery version: 0.7.1
<summary>🍞 <b>PASS:</b> Check METADATA.pb parse correctly. </summary>
* [com.google.fonts/check/metadata/parses](https://github.com/googlefonts/fontbakery/search?q=com.google.fonts/check/metadata/parses)
* 🍞 **PASS** METADATA.pb parsed successfuly.
* 🍞 **PASS** METADATA.pb parsed successfully.
</details>
<details>
@ -331,7 +331,7 @@ But instead we have got: 'Copyright 2012-2015 The Fira Code Project Authors (htt
</details>
<details>
<summary>💤 <b>SKIP:</b> Glyphs are similiar to Google Fonts version?</summary>
<summary>💤 <b>SKIP:</b> Glyphs are similar to Google Fonts version?</summary>
* [com.google.fonts/check/production_glyphs_similarity](https://github.com/googlefonts/fontbakery/search?q=com.google.fonts/check/production_glyphs_similarity)
* 💤 **SKIP** Unfulfilled Conditions: api_gfonts_ttFont
@ -564,7 +564,7 @@ The version string must ideally include a git commit hash and either a 'dev' or
<summary>🍞 <b>PASS:</b> Are there non-ASCII characters in ASCII-only NAME table entries?</summary>
* [com.google.fonts/check/name/ascii_only_entries](https://github.com/googlefonts/fontbakery/search?q=com.google.fonts/check/name/ascii_only_entries)
* 🍞 **PASS** None of the ASCII-only NAME table entries contain non-ASCII characteres.
* 🍞 **PASS** None of the ASCII-only NAME table entries contain non-ASCII characters.
</details>
<details>
@ -703,7 +703,7 @@ The version string must ideally include a git commit hash and either a 'dev' or
<details>
<summary>🍞 <b>PASS:</b> METADATA.pb: Font styles are named canonically?</summary>
* [com.google.fonts/check/metatada/canonical_style_names](https://github.com/googlefonts/fontbakery/search?q=com.google.fonts/check/metatada/canonical_style_names)
* [com.google.fonts/check/metadata/canonical_style_names](https://github.com/googlefonts/fontbakery/search?q=com.google.fonts/check/metadata/canonical_style_names)
* 🍞 **PASS** Font styles are named canonically.
</details>
@ -777,7 +777,7 @@ The version string must ideally include a git commit hash and either a 'dev' or
<summary>🍞 <b>PASS:</b> Check name table: POSTSCRIPT_NAME entries. </summary>
* [com.google.fonts/check/name/postscriptname](https://github.com/googlefonts/fontbakery/search?q=com.google.fonts/check/name/postscriptname)
* 🍞 **PASS** POSTCRIPT_NAME entries are all good.
* 🍞 **PASS** POSTSCRIPT_NAME entries are all good.
</details>
<details>

12
googlefonts-qa/checks/static/FiraCode-Bold.checks.md
View File

@ -25,7 +25,7 @@ Fontbakery version: 0.7.1
<summary>🍞 <b>PASS:</b> Fonts have equal numbers of glyphs?</summary>
* [com.google.fonts/check/family/equal_numbers_of_glyphs](https://github.com/googlefonts/fontbakery/search?q=com.google.fonts/check/family/equal_numbers_of_glyphs)
* 🍞 **PASS** All font files in this family have an equal total ammount of glyphs.
* 🍞 **PASS** All font files in this family have an equal total amount of glyphs.
</details>
<details>
@ -261,7 +261,7 @@ But instead we have got: 'Copyright 2012-2015 The Fira Code Project Authors (htt
<summary>⚠ <b>WARN:</b> Check if each glyph has the recommended amount of contours.</summary>
* [com.google.fonts/check/contour_count](https://github.com/googlefonts/fontbakery/search?q=com.google.fonts/check/contour_count)
* ⚠ **WARN** This check inspects the glyph outlines and detects the total number of contours in each of them. The expected values are infered from the typical ammounts of contours observed in a large collection of reference font families. The divergences listed below may simply indicate a significantly different design on some of your glyphs. On the other hand, some of these may flag actual bugs in the font such as glyphs mapped to an incorrect codepoint. Please consider reviewing the design and codepoint assignment of these to make sure they are correct.
* ⚠ **WARN** This check inspects the glyph outlines and detects the total number of contours in each of them. The expected values are inferred from the typical amounts of contours observed in a large collection of reference font families. The divergences listed below may simply indicate a significantly different design on some of your glyphs. On the other hand, some of these may flag actual bugs in the font such as glyphs mapped to an incorrect codepoint. Please consider reviewing the design and codepoint assignment of these to make sure they are correct.
The following glyphs do not have the recommended number of contours:
@ -491,7 +491,7 @@ Glyph name: uni2158 Contours detected: 3 Expected: 4
<details>
<summary>💤 <b>SKIP:</b> METADATA.pb: Font styles are named canonically?</summary>
* [com.google.fonts/check/metatada/canonical_style_names](https://github.com/googlefonts/fontbakery/search?q=com.google.fonts/check/metatada/canonical_style_names)
* [com.google.fonts/check/metadata/canonical_style_names](https://github.com/googlefonts/fontbakery/search?q=com.google.fonts/check/metadata/canonical_style_names)
* 💤 **SKIP** Unfulfilled Conditions: font_metadata
</details>
@ -503,7 +503,7 @@ Glyph name: uni2158 Contours detected: 3 Expected: 4
</details>
<details>
<summary>💤 <b>SKIP:</b> Glyphs are similiar to Google Fonts version?</summary>
<summary>💤 <b>SKIP:</b> Glyphs are similar to Google Fonts version?</summary>
* [com.google.fonts/check/production_glyphs_similarity](https://github.com/googlefonts/fontbakery/search?q=com.google.fonts/check/production_glyphs_similarity)
* 💤 **SKIP** Unfulfilled Conditions: api_gfonts_ttFont
@ -792,7 +792,7 @@ The version string must ideally include a git commit hash and either a 'dev' or
<summary>🍞 <b>PASS:</b> Are there non-ASCII characters in ASCII-only NAME table entries?</summary>
* [com.google.fonts/check/name/ascii_only_entries](https://github.com/googlefonts/fontbakery/search?q=com.google.fonts/check/name/ascii_only_entries)
* 🍞 **PASS** None of the ASCII-only NAME table entries contain non-ASCII characteres.
* 🍞 **PASS** None of the ASCII-only NAME table entries contain non-ASCII characters.
</details>
<details>
@ -858,7 +858,7 @@ The version string must ideally include a git commit hash and either a 'dev' or
<summary>🍞 <b>PASS:</b> Check name table: POSTSCRIPT_NAME entries. </summary>
* [com.google.fonts/check/name/postscriptname](https://github.com/googlefonts/fontbakery/search?q=com.google.fonts/check/name/postscriptname)
* 🍞 **PASS** POSTCRIPT_NAME entries are all good.
* 🍞 **PASS** POSTSCRIPT_NAME entries are all good.
</details>
<details>

12
googlefonts-qa/checks/static/FiraCode-Light.checks.md
View File

@ -25,7 +25,7 @@ Fontbakery version: 0.7.1
<summary>🍞 <b>PASS:</b> Fonts have equal numbers of glyphs?</summary>
* [com.google.fonts/check/family/equal_numbers_of_glyphs](https://github.com/googlefonts/fontbakery/search?q=com.google.fonts/check/family/equal_numbers_of_glyphs)
* 🍞 **PASS** All font files in this family have an equal total ammount of glyphs.
* 🍞 **PASS** All font files in this family have an equal total amount of glyphs.
</details>
<details>
@ -261,7 +261,7 @@ But instead we have got: 'Copyright 2012-2015 The Fira Code Project Authors (htt
<summary>⚠ <b>WARN:</b> Check if each glyph has the recommended amount of contours.</summary>
* [com.google.fonts/check/contour_count](https://github.com/googlefonts/fontbakery/search?q=com.google.fonts/check/contour_count)
* ⚠ **WARN** This check inspects the glyph outlines and detects the total number of contours in each of them. The expected values are infered from the typical ammounts of contours observed in a large collection of reference font families. The divergences listed below may simply indicate a significantly different design on some of your glyphs. On the other hand, some of these may flag actual bugs in the font such as glyphs mapped to an incorrect codepoint. Please consider reviewing the design and codepoint assignment of these to make sure they are correct.
* ⚠ **WARN** This check inspects the glyph outlines and detects the total number of contours in each of them. The expected values are inferred from the typical amounts of contours observed in a large collection of reference font families. The divergences listed below may simply indicate a significantly different design on some of your glyphs. On the other hand, some of these may flag actual bugs in the font such as glyphs mapped to an incorrect codepoint. Please consider reviewing the design and codepoint assignment of these to make sure they are correct.
The following glyphs do not have the recommended number of contours:
@ -498,7 +498,7 @@ Glyph name: uni2158 Contours detected: 3 Expected: 4
<details>
<summary>💤 <b>SKIP:</b> METADATA.pb: Font styles are named canonically?</summary>
* [com.google.fonts/check/metatada/canonical_style_names](https://github.com/googlefonts/fontbakery/search?q=com.google.fonts/check/metatada/canonical_style_names)
* [com.google.fonts/check/metadata/canonical_style_names](https://github.com/googlefonts/fontbakery/search?q=com.google.fonts/check/metadata/canonical_style_names)
* 💤 **SKIP** Unfulfilled Conditions: font_metadata
</details>
@ -510,7 +510,7 @@ Glyph name: uni2158 Contours detected: 3 Expected: 4
</details>
<details>
<summary>💤 <b>SKIP:</b> Glyphs are similiar to Google Fonts version?</summary>
<summary>💤 <b>SKIP:</b> Glyphs are similar to Google Fonts version?</summary>
* [com.google.fonts/check/production_glyphs_similarity](https://github.com/googlefonts/fontbakery/search?q=com.google.fonts/check/production_glyphs_similarity)
* 💤 **SKIP** Unfulfilled Conditions: api_gfonts_ttFont
@ -799,7 +799,7 @@ The version string must ideally include a git commit hash and either a 'dev' or
<summary>🍞 <b>PASS:</b> Are there non-ASCII characters in ASCII-only NAME table entries?</summary>
* [com.google.fonts/check/name/ascii_only_entries](https://github.com/googlefonts/fontbakery/search?q=com.google.fonts/check/name/ascii_only_entries)
* 🍞 **PASS** None of the ASCII-only NAME table entries contain non-ASCII characteres.
* 🍞 **PASS** None of the ASCII-only NAME table entries contain non-ASCII characters.
</details>
<details>
@ -865,7 +865,7 @@ The version string must ideally include a git commit hash and either a 'dev' or
<summary>🍞 <b>PASS:</b> Check name table: POSTSCRIPT_NAME entries. </summary>
* [com.google.fonts/check/name/postscriptname](https://github.com/googlefonts/fontbakery/search?q=com.google.fonts/check/name/postscriptname)
* 🍞 **PASS** POSTCRIPT_NAME entries are all good.
* 🍞 **PASS** POSTSCRIPT_NAME entries are all good.
</details>
<details>

12
googlefonts-qa/checks/static/FiraCode-Medium.checks.md
View File

@ -25,7 +25,7 @@ Fontbakery version: 0.7.1
<summary>🍞 <b>PASS:</b> Fonts have equal numbers of glyphs?</summary>
* [com.google.fonts/check/family/equal_numbers_of_glyphs](https://github.com/googlefonts/fontbakery/search?q=com.google.fonts/check/family/equal_numbers_of_glyphs)
* 🍞 **PASS** All font files in this family have an equal total ammount of glyphs.
* 🍞 **PASS** All font files in this family have an equal total amount of glyphs.
</details>
<details>
@ -261,7 +261,7 @@ But instead we have got: 'Copyright 2012-2015 The Fira Code Project Authors (htt
<summary>⚠ <b>WARN:</b> Check if each glyph has the recommended amount of contours.</summary>
* [com.google.fonts/check/contour_count](https://github.com/googlefonts/fontbakery/search?q=com.google.fonts/check/contour_count)
* ⚠ **WARN** This check inspects the glyph outlines and detects the total number of contours in each of them. The expected values are infered from the typical ammounts of contours observed in a large collection of reference font families. The divergences listed below may simply indicate a significantly different design on some of your glyphs. On the other hand, some of these may flag actual bugs in the font such as glyphs mapped to an incorrect codepoint. Please consider reviewing the design and codepoint assignment of these to make sure they are correct.
* ⚠ **WARN** This check inspects the glyph outlines and detects the total number of contours in each of them. The expected values are inferred from the typical amounts of contours observed in a large collection of reference font families. The divergences listed below may simply indicate a significantly different design on some of your glyphs. On the other hand, some of these may flag actual bugs in the font such as glyphs mapped to an incorrect codepoint. Please consider reviewing the design and codepoint assignment of these to make sure they are correct.
The following glyphs do not have the recommended number of contours:
@ -506,7 +506,7 @@ This happens a lot when points are not extremes, which is usually bad. However,
<details>
<summary>💤 <b>SKIP:</b> METADATA.pb: Font styles are named canonically?</summary>
* [com.google.fonts/check/metatada/canonical_style_names](https://github.com/googlefonts/fontbakery/search?q=com.google.fonts/check/metatada/canonical_style_names)
* [com.google.fonts/check/metadata/canonical_style_names](https://github.com/googlefonts/fontbakery/search?q=com.google.fonts/check/metadata/canonical_style_names)
* 💤 **SKIP** Unfulfilled Conditions: font_metadata
</details>
@ -518,7 +518,7 @@ This happens a lot when points are not extremes, which is usually bad. However,
</details>
<details>
<summary>💤 <b>SKIP:</b> Glyphs are similiar to Google Fonts version?</summary>
<summary>💤 <b>SKIP:</b> Glyphs are similar to Google Fonts version?</summary>
* [com.google.fonts/check/production_glyphs_similarity](https://github.com/googlefonts/fontbakery/search?q=com.google.fonts/check/production_glyphs_similarity)
* 💤 **SKIP** Unfulfilled Conditions: api_gfonts_ttFont
@ -807,7 +807,7 @@ The version string must ideally include a git commit hash and either a 'dev' or
<summary>🍞 <b>PASS:</b> Are there non-ASCII characters in ASCII-only NAME table entries?</summary>
* [com.google.fonts/check/name/ascii_only_entries](https://github.com/googlefonts/fontbakery/search?q=com.google.fonts/check/name/ascii_only_entries)
* 🍞 **PASS** None of the ASCII-only NAME table entries contain non-ASCII characteres.
* 🍞 **PASS** None of the ASCII-only NAME table entries contain non-ASCII characters.
</details>
<details>
@ -873,7 +873,7 @@ The version string must ideally include a git commit hash and either a 'dev' or
<summary>🍞 <b>PASS:</b> Check name table: POSTSCRIPT_NAME entries. </summary>
* [com.google.fonts/check/name/postscriptname](https://github.com/googlefonts/fontbakery/search?q=com.google.fonts/check/name/postscriptname)
* 🍞 **PASS** POSTCRIPT_NAME entries are all good.
* 🍞 **PASS** POSTSCRIPT_NAME entries are all good.
</details>
<details>

12
googlefonts-qa/checks/static/FiraCode-Regular.checks.md
View File

@ -25,7 +25,7 @@ Fontbakery version: 0.7.1
<summary>🍞 <b>PASS:</b> Fonts have equal numbers of glyphs?</summary>
* [com.google.fonts/check/family/equal_numbers_of_glyphs](https://github.com/googlefonts/fontbakery/search?q=com.google.fonts/check/family/equal_numbers_of_glyphs)
* 🍞 **PASS** All font files in this family have an equal total ammount of glyphs.
* 🍞 **PASS** All font files in this family have an equal total amount of glyphs.
</details>
<details>
@ -261,7 +261,7 @@ But instead we have got: 'Copyright 2012-2015 The Fira Code Project Authors (htt
<summary>⚠ <b>WARN:</b> Check if each glyph has the recommended amount of contours.</summary>
* [com.google.fonts/check/contour_count](https://github.com/googlefonts/fontbakery/search?q=com.google.fonts/check/contour_count)
* ⚠ **WARN** This check inspects the glyph outlines and detects the total number of contours in each of them. The expected values are infered from the typical ammounts of contours observed in a large collection of reference font families. The divergences listed below may simply indicate a significantly different design on some of your glyphs. On the other hand, some of these may flag actual bugs in the font such as glyphs mapped to an incorrect codepoint. Please consider reviewing the design and codepoint assignment of these to make sure they are correct.
* ⚠ **WARN** This check inspects the glyph outlines and detects the total number of contours in each of them. The expected values are inferred from the typical amounts of contours observed in a large collection of reference font families. The divergences listed below may simply indicate a significantly different design on some of your glyphs. On the other hand, some of these may flag actual bugs in the font such as glyphs mapped to an incorrect codepoint. Please consider reviewing the design and codepoint assignment of these to make sure they are correct.
The following glyphs do not have the recommended number of contours:
@ -490,7 +490,7 @@ Glyph name: uni2158 Contours detected: 3 Expected: 4
<details>
<summary>💤 <b>SKIP:</b> METADATA.pb: Font styles are named canonically?</summary>
* [com.google.fonts/check/metatada/canonical_style_names](https://github.com/googlefonts/fontbakery/search?q=com.google.fonts/check/metatada/canonical_style_names)
* [com.google.fonts/check/metadata/canonical_style_names](https://github.com/googlefonts/fontbakery/search?q=com.google.fonts/check/metadata/canonical_style_names)
* 💤 **SKIP** Unfulfilled Conditions: font_metadata
</details>
@ -502,7 +502,7 @@ Glyph name: uni2158 Contours detected: 3 Expected: 4
</details>
<details>
<summary>💤 <b>SKIP:</b> Glyphs are similiar to Google Fonts version?</summary>
<summary>💤 <b>SKIP:</b> Glyphs are similar to Google Fonts version?</summary>
* [com.google.fonts/check/production_glyphs_similarity](https://github.com/googlefonts/fontbakery/search?q=com.google.fonts/check/production_glyphs_similarity)
* 💤 **SKIP** Unfulfilled Conditions: api_gfonts_ttFont
@ -791,7 +791,7 @@ The version string must ideally include a git commit hash and either a 'dev' or
<summary>🍞 <b>PASS:</b> Are there non-ASCII characters in ASCII-only NAME table entries?</summary>
* [com.google.fonts/check/name/ascii_only_entries](https://github.com/googlefonts/fontbakery/search?q=com.google.fonts/check/name/ascii_only_entries)
* 🍞 **PASS** None of the ASCII-only NAME table entries contain non-ASCII characteres.
* 🍞 **PASS** None of the ASCII-only NAME table entries contain non-ASCII characters.
</details>
<details>
@ -857,7 +857,7 @@ The version string must ideally include a git commit hash and either a 'dev' or
<summary>🍞 <b>PASS:</b> Check name table: POSTSCRIPT_NAME entries. </summary>
* [com.google.fonts/check/name/postscriptname](https://github.com/googlefonts/fontbakery/search?q=com.google.fonts/check/name/postscriptname)
* 🍞 **PASS** POSTCRIPT_NAME entries are all good.
* 🍞 **PASS** POSTSCRIPT_NAME entries are all good.
</details>
<details>

8
googlefonts-qa/checks/static/FiraCode-Retina.checks.md
View File

@ -268,7 +268,7 @@ But instead we have got: 'Copyright 2012-2015 The Fira Code Project Authors (htt
<summary>⚠ <b>WARN:</b> Check if each glyph has the recommended amount of contours.</summary>
* [com.google.fonts/check/contour_count](https://github.com/googlefonts/fontbakery/search?q=com.google.fonts/check/contour_count)
* ⚠ **WARN** This check inspects the glyph outlines and detects the total number of contours in each of them. The expected values are infered from the typical ammounts of contours observed in a large collection of reference font families. The divergences listed below may simply indicate a significantly different design on some of your glyphs. On the other hand, some of these may flag actual bugs in the font such as glyphs mapped to an incorrect codepoint. Please consider reviewing the design and codepoint assignment of these to make sure they are correct.
* ⚠ **WARN** This check inspects the glyph outlines and detects the total number of contours in each of them. The expected values are inferred from the typical amounts of contours observed in a large collection of reference font families. The divergences listed below may simply indicate a significantly different design on some of your glyphs. On the other hand, some of these may flag actual bugs in the font such as glyphs mapped to an incorrect codepoint. Please consider reviewing the design and codepoint assignment of these to make sure they are correct.
The following glyphs do not have the recommended number of contours:
@ -511,7 +511,7 @@ Glyph name: uni2158 Contours detected: 3 Expected: 4
<details>
<summary>💤 <b>SKIP:</b> METADATA.pb: Font styles are named canonically?</summary>
* [com.google.fonts/check/metatada/canonical_style_names](https://github.com/googlefonts/fontbakery/search?q=com.google.fonts/check/metatada/canonical_style_names)
* [com.google.fonts/check/metadata/canonical_style_names](https://github.com/googlefonts/fontbakery/search?q=com.google.fonts/check/metadata/canonical_style_names)
* 💤 **SKIP** Unfulfilled Conditions: font_metadata
</details>
@ -523,7 +523,7 @@ Glyph name: uni2158 Contours detected: 3 Expected: 4
</details>
<details>
<summary>💤 <b>SKIP:</b> Glyphs are similiar to Google Fonts version?</summary>
<summary>💤 <b>SKIP:</b> Glyphs are similar to Google Fonts version?</summary>
* [com.google.fonts/check/production_glyphs_similarity](https://github.com/googlefonts/fontbakery/search?q=com.google.fonts/check/production_glyphs_similarity)
* 💤 **SKIP** Unfulfilled Conditions: api_gfonts_ttFont
@ -868,7 +868,7 @@ The version string must ideally include a git commit hash and either a 'dev' or
<summary>🍞 <b>PASS:</b> Are there non-ASCII characters in ASCII-only NAME table entries?</summary>
* [com.google.fonts/check/name/ascii_only_entries](https://github.com/googlefonts/fontbakery/search?q=com.google.fonts/check/name/ascii_only_entries)
* 🍞 **PASS** None of the ASCII-only NAME table entries contain non-ASCII characteres.
* 🍞 **PASS** None of the ASCII-only NAME table entries contain non-ASCII characters.
</details>
<details>

2
googlefonts-qa/notes/QA-notes.md
View File

@ -128,7 +128,7 @@ But instead we have got: 'Copyright 2012-2015 The Mozilla Foundation, Telefonica
- [x] uncheck "Retina" instance as `is active` instance
- [x] file issue with FontBakery to ask Dave/Marc about this `450` weight "Retina" instance (https://github.com/googlefonts/fontbakery/issues/2420)-
- [x] change if you find a better approach to keep Retina without disrupting builds / Regular weight
- To set up the instance in GlyhpsApp such that it exports a font as expected: "Retina" gets a custom parameter of `weightClass: 450`, and a glyphs menu-weight of "Normal." Tested in axis-praxis, it seems to work well. All instances have a `weightClass` custom parameter.
- To set up the instance in GlyphsApp such that it exports a font as expected: "Retina" gets a custom parameter of `weightClass: 450`, and a glyphs menu-weight of "Normal." Tested in axis-praxis, it seems to work well. All instances have a `weightClass` custom parameter.
----------------------------

2
googlefonts-qa/notes/outline-checks.md
View File

@ -146,7 +146,7 @@ Straightened in Bold & Reg:
### betaSymbol
These lines are't supposed to intersect:
These lines aren't supposed to intersect:
![](assets/2019-03-28-14-20-11.png)

2
googlefonts-qa/scripts/move-check.sh
View File

@ -5,7 +5,7 @@
# USAGE:
# Install requirements with `pip install -U -r googlefonts-qa/requirements.txt`
#
# call this script from the root of your fira code repo, with the absolute path your your local google/fonts repo
# call this script from the root of your fira code repo, with the absolute path to your local google/fonts repo
# `move-check <your_username>/<path>/fonts`
set -ex