Sansita swashed: version 1.003 added #2658

RosaWagner · 2020-08-31T13:24:10Z

Taken in upstream repo https://github.com/Omnibus-Type/Sansita-Swashed at commit https://github.com/Omnibus-Type/Sansita-Swashed/tree/4b18bac65511ce185c1dc687472a8c77bdc6cc4d

ExtraBold and SemiBold name id 1+2 > 31 characters, but name ID 4 is still < 27 characters.
To be sure I tested the statics with Word in Windows 10 and it works with no issue. Tell me if it's problematic and I will condensed the style names.
This PR is following his one: Sansita Swashed 1.002 #2584 which I gonna close now.

gf-bot · 2020-08-31T13:37:24Z

Fontbakery report

Fontbakery version: 0.7.29

[1] Family checks

⚠ WARN: Is the command `ftxvalidator` (Apple Font Tool Suite) available?

com.google.fonts/check/ftxvalidator_is_available

--- Rationale ---

There's no reasonable (and legal) way to run the command `ftxvalidator` of the
Apple Font Tool Suite on a non-macOS machine. I.e. on GNU+Linux or Windows etc.

If Font Bakery is not running on an OSX machine, the machine running Font
Bakery could access `ftxvalidator` on OSX, e.g. via ssh or a remote procedure
call (rpc).

There's an ssh example implementation at:
https://github.com/googlefonts/fontbakery/blob/master/prebuilt/workarounds
/ftxvalidator/ssh-implementation/ftxvalidator

⚠ WARN Could not find ftxvalidator.

[4] SansitaSwashed[wght].ttf

⚠ WARN: METADATA.pb: Fontfamily is listed on Google Fonts API?

com.google.fonts/check/metadata/listed_on_gfonts
⚠ WARN Family not found via Google Fonts API. [code: not-found]

⚠ WARN: Are there caret positions declared for every ligature?

com.google.fonts/check/ligature_carets

--- Rationale ---

All ligatures in a font must have corresponding caret (text cursor) positions
defined in the GDEF table, otherwhise, users may experience issues with caret
rendering.

If using GlyphsApp, ligature carets can be set directly on canvas by accessing
the `Glyph -> Set Anchors` menu option or by pressing the `Cmd+U` keyboard
shortcut.

⚠ WARN This font lacks caret position values for ligature glyphs on its GDEF table. [code: lacks-caret-pos]

⚠ WARN: Is there kerning info for non-ligated sequences?

com.google.fonts/check/kerning_for_non_ligated_sequences

--- Rationale ---

Fonts with ligatures should have kerning on the corresponding non-ligated
sequences for text where ligatures aren't used (eg
https://github.com/impallari/Raleway/issues/14).

⚠ WARN GPOS table lacks kerning info for the following non-ligated sequences:
- f + f
- f + i
- i + f
- f + l
- l + f
- i + l
[code: lacks-kern-info]

⚠ WARN: Combined length of family and style must not exceed 27 characters.

com.google.fonts/check/name/family_and_style_max_length

--- Rationale ---

According to a GlyphsApp tutorial [1], in order to make sure all versions of
Windows recognize it as a valid font file, we must make sure that the
concatenated length of the familyname (NameID.FONT_FAMILY_NAME) and style
(NameID.FONT_SUBFAMILY_NAME) strings in the name table do not exceed 20
characters.

After discussing the problem in more detail at `FontBakery issue #2179 [2] we
decided that allowing up to 27 chars would still be on the safe side, though.

[1]
https://glyphsapp.com/tutorials/multiple-masters-part-3-setting-up-instances
[2] https://github.com/googlefonts/fontbakery/issues/2179

⚠ WARN The combined length of family and style exceeds 27 chars in the following 'WINDOWS' entries:
FONT_FAMILY_NAME = 'Sansita Swashed Light' / SUBFAMILY_NAME = 'Regular'

Please take a look at the conversation at fonttools/fontbakery#2179 in order to understand the reasoning behind these name table records max-length criteria. [code: too-long]

Summary

💔 ERROR	🔥 FAIL	⚠ WARN	💤 SKIP	ℹ INFO	🍞 PASS	🔎 DEBUG
0	0	5	36	9	127	0
0%	0%	3%	20%	5%	72%	0%

Note: The following loglevels were omitted in this report:

SKIP
INFO
PASS
DEBUG

Diff images: qa.zip

m4rc1e · 2020-09-04T13:44:19Z

Fontbakery report

Fontbakery version: 0.7.29

[1] Family checks

⚠ WARN: Is the command `ftxvalidator` (Apple Font Tool Suite) available?

com.google.fonts/check/ftxvalidator_is_available

--- Rationale ---

There's no reasonable (and legal) way to run the command `ftxvalidator` of the
Apple Font Tool Suite on a non-macOS machine. I.e. on GNU+Linux or Windows etc.

If Font Bakery is not running on an OSX machine, the machine running Font
Bakery could access `ftxvalidator` on OSX, e.g. via ssh or a remote procedure
call (rpc).

There's an ssh example implementation at:
https://github.com/googlefonts/fontbakery/blob/master/prebuilt/workarounds
/ftxvalidator/ssh-implementation/ftxvalidator

⚠ WARN Could not find ftxvalidator.

[4] SansitaSwashed[wght].ttf

⚠ WARN: METADATA.pb: Fontfamily is listed on Google Fonts API?

com.google.fonts/check/metadata/listed_on_gfonts
⚠ WARN Family not found via Google Fonts API. [code: not-found]

⚠ WARN: Are there caret positions declared for every ligature?

com.google.fonts/check/ligature_carets

--- Rationale ---

All ligatures in a font must have corresponding caret (text cursor) positions
defined in the GDEF table, otherwhise, users may experience issues with caret
rendering.

If using GlyphsApp, ligature carets can be set directly on canvas by accessing
the `Glyph -> Set Anchors` menu option or by pressing the `Cmd+U` keyboard
shortcut.

⚠ WARN This font lacks caret position values for ligature glyphs on its GDEF table. [code: lacks-caret-pos]

⚠ WARN: Is there kerning info for non-ligated sequences?

com.google.fonts/check/kerning_for_non_ligated_sequences

--- Rationale ---

Fonts with ligatures should have kerning on the corresponding non-ligated
sequences for text where ligatures aren't used (eg
https://github.com/impallari/Raleway/issues/14).

⚠ WARN GPOS table lacks kerning info for the following non-ligated sequences:
- f + f
- f + i
- i + f
- f + l
- l + f
- i + l
[code: lacks-kern-info]

⚠ WARN: Combined length of family and style must not exceed 27 characters.

com.google.fonts/check/name/family_and_style_max_length

--- Rationale ---

According to a GlyphsApp tutorial [1], in order to make sure all versions of
Windows recognize it as a valid font file, we must make sure that the
concatenated length of the familyname (NameID.FONT_FAMILY_NAME) and style
(NameID.FONT_SUBFAMILY_NAME) strings in the name table do not exceed 20
characters.

After discussing the problem in more detail at `FontBakery issue #2179 [2] we
decided that allowing up to 27 chars would still be on the safe side, though.

[1]
https://glyphsapp.com/tutorials/multiple-masters-part-3-setting-up-instances
[2] https://github.com/googlefonts/fontbakery/issues/2179

⚠ WARN The combined length of family and style exceeds 27 chars in the following 'WINDOWS' entries:
FONT_FAMILY_NAME = 'Sansita Swashed Light' / SUBFAMILY_NAME = 'Regular'

Please take a look at the conversation at fonttools/fontbakery#2179 in order to understand the reasoning behind these name table records max-length criteria. [code: too-long]

Summary

💔 ERROR	🔥 FAIL	⚠ WARN	💤 SKIP	ℹ INFO	🍞 PASS	🔎 DEBUG
0	0	5	36	9	127	0
0%	0%	3%	20%	5%	72%	0%

Note: The following loglevels were omitted in this report:

SKIP
INFO
PASS
DEBUG

Diff images: sansita_swashed.zip

gf-bot · 2020-09-04T13:46:00Z

Fontbakery report

Fontbakery version: 0.7.29

[1] Family checks

⚠ WARN: Is the command `ftxvalidator` (Apple Font Tool Suite) available?

com.google.fonts/check/ftxvalidator_is_available

--- Rationale ---

There's no reasonable (and legal) way to run the command `ftxvalidator` of the
Apple Font Tool Suite on a non-macOS machine. I.e. on GNU+Linux or Windows etc.

If Font Bakery is not running on an OSX machine, the machine running Font
Bakery could access `ftxvalidator` on OSX, e.g. via ssh or a remote procedure
call (rpc).

There's an ssh example implementation at:
https://github.com/googlefonts/fontbakery/blob/master/prebuilt/workarounds
/ftxvalidator/ssh-implementation/ftxvalidator

⚠ WARN Could not find ftxvalidator.

[4] SansitaSwashed[wght].ttf

⚠ WARN: METADATA.pb: Fontfamily is listed on Google Fonts API?

com.google.fonts/check/metadata/listed_on_gfonts
⚠ WARN Family not found via Google Fonts API. [code: not-found]

⚠ WARN: Are there caret positions declared for every ligature?

com.google.fonts/check/ligature_carets

--- Rationale ---

All ligatures in a font must have corresponding caret (text cursor) positions
defined in the GDEF table, otherwhise, users may experience issues with caret
rendering.

If using GlyphsApp, ligature carets can be set directly on canvas by accessing
the `Glyph -> Set Anchors` menu option or by pressing the `Cmd+U` keyboard
shortcut.

⚠ WARN This font lacks caret position values for ligature glyphs on its GDEF table. [code: lacks-caret-pos]

⚠ WARN: Is there kerning info for non-ligated sequences?

com.google.fonts/check/kerning_for_non_ligated_sequences

--- Rationale ---

Fonts with ligatures should have kerning on the corresponding non-ligated
sequences for text where ligatures aren't used (eg
https://github.com/impallari/Raleway/issues/14).

⚠ WARN GPOS table lacks kerning info for the following non-ligated sequences:
- f + f
- f + i
- i + f
- f + l
- l + f
- i + l
[code: lacks-kern-info]

⚠ WARN: Combined length of family and style must not exceed 27 characters.

com.google.fonts/check/name/family_and_style_max_length

--- Rationale ---

According to a GlyphsApp tutorial [1], in order to make sure all versions of
Windows recognize it as a valid font file, we must make sure that the
concatenated length of the familyname (NameID.FONT_FAMILY_NAME) and style
(NameID.FONT_SUBFAMILY_NAME) strings in the name table do not exceed 20
characters.

After discussing the problem in more detail at `FontBakery issue #2179 [2] we
decided that allowing up to 27 chars would still be on the safe side, though.

[1]
https://glyphsapp.com/tutorials/multiple-masters-part-3-setting-up-instances
[2] https://github.com/googlefonts/fontbakery/issues/2179

⚠ WARN The combined length of family and style exceeds 27 chars in the following 'WINDOWS' entries:
FONT_FAMILY_NAME = 'Sansita Swashed Light' / SUBFAMILY_NAME = 'Regular'

Please take a look at the conversation at fonttools/fontbakery#2179 in order to understand the reasoning behind these name table records max-length criteria. [code: too-long]

Summary

💔 ERROR	🔥 FAIL	⚠ WARN	💤 SKIP	ℹ INFO	🍞 PASS	🔎 DEBUG
0	0	5	36	9	127	0
0%	0%	3%	20%	5%	72%	0%

Note: The following loglevels were omitted in this report:

SKIP
INFO
PASS
DEBUG

Diff images: qa.zip

Jost #2627, Rubik #2664, Sansita Swashed #2658, Piazzolla #2653, Baskervville Epilogue Grandstander #2648, Merriweather #2632, Syne #2644

Piazzolla metadata #2678 Sansita Swashed added #2658 (ofl/sansitaswashed is already in sandbox, but I forgot designers/omnibus-type)

* Sansita Swashes: version 1.003 added * Updated designers info for Omnibus-Type * Update DESCRIPTION.en_us.html Co-authored-by: Marc Foley <m.foley.88@gmail.com>

Jost #2627, Rubik #2664, Sansita Swashed #2658, Piazzolla #2653, Baskervville Epilogue Grandstander #2648, Merriweather #2632, Syne #2644

Piazzolla metadata #2678 Sansita Swashed added #2658 (ofl/sansitaswashed is already in sandbox, but I forgot designers/omnibus-type)

Rosalie Wagner added 2 commits August 31, 2020 15:15

Sansita Swashes: version 1.003 added

4b42c4c

Updated designers info for Omnibus-Type

155165c

RosaWagner added the Check Font Files label Aug 31, 2020

RosaWagner mentioned this pull request Aug 31, 2020

Sansita Swashed 1.002 #2584

Closed

RosaWagner added Ready to push and removed Check Font Files labels Aug 31, 2020

Update DESCRIPTION.en_us.html

19a0770

m4rc1e merged commit e24965e into master Sep 4, 2020

m4rc1e deleted the sansita-swashed branch September 4, 2020 13:40

davelab6 added a commit that referenced this pull request Sep 9, 2020

Update to_sandbox.txt

3b371af

Jost #2627, Rubik #2664, Sansita Swashed #2658, Piazzolla #2653, Baskervville Epilogue Grandstander #2648, Merriweather #2632, Syne #2644

RosaWagner added to_sandbox and removed Ready to push labels Sep 9, 2020

RosaWagner added a commit that referenced this pull request Sep 11, 2020

Update to_sandbox.txt

4860d8e

Piazzolla metadata #2678 Sansita Swashed added #2658 (ofl/sansitaswashed is already in sandbox, but I forgot designers/omnibus-type)

RosaWagner added to_production --- Live Font is visible on API and removed in_sandbox labels Sep 23, 2020

davelab6 pushed a commit that referenced this pull request Dec 10, 2020

Sansita swashed: version 1.003 added (#2658)

1c4860f

* Sansita Swashes: version 1.003 added * Updated designers info for Omnibus-Type * Update DESCRIPTION.en_us.html Co-authored-by: Marc Foley <m.foley.88@gmail.com>

davelab6 added a commit that referenced this pull request Dec 10, 2020

Update to_sandbox.txt

e3b33c2

Jost #2627, Rubik #2664, Sansita Swashed #2658, Piazzolla #2653, Baskervville Epilogue Grandstander #2648, Merriweather #2632, Syne #2644

davelab6 pushed a commit that referenced this pull request Dec 10, 2020

Update to_sandbox.txt

d3c847e

Piazzolla metadata #2678 Sansita Swashed added #2658 (ofl/sansitaswashed is already in sandbox, but I forgot designers/omnibus-type)

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Sansita swashed: version 1.003 added #2658

Sansita swashed: version 1.003 added #2658

RosaWagner commented Aug 31, 2020

gf-bot commented Aug 31, 2020

m4rc1e commented Sep 4, 2020

gf-bot commented Sep 4, 2020

Sansita swashed: version 1.003 added #2658

Sansita swashed: version 1.003 added #2658

Conversation

RosaWagner commented Aug 31, 2020

gf-bot commented Aug 31, 2020

Fontbakery report

Summary

Diff images: qa.zip

m4rc1e commented Sep 4, 2020

Fontbakery report

Summary

Diff images: sansita_swashed.zip

gf-bot commented Sep 4, 2020

Fontbakery report

Summary

Diff images: qa.zip