-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update Sora #5827
Comments
Hi @tarmovannas! I'm Emma and I work with the GoogleFonts team as font engineer. |
Thanks @emmamarichal. That would be great, but we should slightly fix the italics first. Also we planned to create Cyrillics. So we need a type designer / font engineer to help with this. Let me tag @WRRicht3r here, and he can explain further. |
No rush, just let me know here when it's ready :) |
Hi @emmamarichal , this is William from the SORA team, unfortunately, we were in the process of working on this implementation but got ghosted by the type designer who was going to help us, therefore we are unable to make these updates at the moment. |
Hi @WRRicht3r Unfortunately I'm not sure I have the skills to develop Cyrillic. But we can release the italic first, and take care of the cyrillic when it's done, that gives you time to find someone else to work on it. What do you think? cc @davelab6 |
Hello @emmamarichal help with the italics would be great! Please let us know how we can proceed with this. cc @tarmovannas |
For the italic, my job is to fix the possible errors detected through our QA (so that the fonts follow the Google Fonts specs), this is rather engineering. For the design, you'll have to provide me with a "finished" file, that follows the GF glyphset. I couldn't open the Glyphs italic file, -I don't know why- but the italic seemed to be already well advanced, no? |
Hello @emmamarichal at the moment, the version of italics we have are available here and here cc @tarmovannas |
Hi @WRRicht3r, I just run a fontbakery on the exported fonts. It looks good, I can solve the fails quickly. The only thing is I can't access to the file. Do you think you can solve that? Fontbakery reportFontbakery version: 0.8.10 [2] Family checksℹ INFO: Check axis ordering on the STAT table. (com.google.fonts/check/STAT/axis_order)
⚠ WARN: Make sure all font files have the same version value. (com.google.fonts/check/family/equal_font_versions)
[27] Sora-Italic[wght].ttf🔥 FAIL: Checking file is named canonically. (com.google.fonts/check/canonical_filename)
🔥 FAIL: Checking OS/2 fsType does not impose restrictions. (com.google.fonts/check/fstype)
No such DRM restrictions can be enabled on the Google Fonts collection, so the fsType field must be set to zero (Installable Embedding) instead. [code: drm] 🔥 FAIL: Check Google Fonts glyph coverage. (com.google.fonts/check/glyph_coverage)
🔥 FAIL: Is the Grid-fitting and Scan-conversion Procedure ('gasp') table set to optimize rendering? (com.google.fonts/check/gasp)
🔥 FAIL: Check glyphs do not have components which are themselves components. (com.google.fonts/check/glyf_nested_components)
Use -F or --full-lists to disable shortening of long lists. [code: found-nested-components] 🔥 FAIL: Font enables smart dropout control in "prep" table instructions? (com.google.fonts/check/smart_dropout)
🔥 FAIL: Check a font's STAT table contains compulsory Axis Values. (com.google.fonts/check/STAT)
🔥 FAIL: Check variable font instances (com.google.fonts/check/fvar_instances)
🔥 FAIL: Ensure component transforms do not perform scaling or rotation. (com.google.fonts/check/transformed_components)
🔥 FAIL: Validates that when an instance record is included for the default instance, its subfamilyNameID value is set to either 2 or 17 (or something with the same value as 2), and its postScriptNameID value is set to 6 (or something with the same value as 6). (com.adobe.fonts/check/varfont/valid_default_instance_nameids)
🔥 FAIL: STAT table has Axis Value tables? (com.adobe.fonts/check/stat_has_axis_value_tables)
⚠ WARN: Checking OS/2 achVendID. (com.google.fonts/check/vendor_id)
⚠ WARN: Are there caret positions declared for every ligature? (com.google.fonts/check/ligature_carets)
⚠ WARN: Is there kerning info for non-ligated sequences? (com.google.fonts/check/kerning_for_non_ligated_sequences)
Use -F or --full-lists to disable shortening of long lists. [code: lacks-kern-info] ⚠ WARN: Ensure variable fonts include an avar table. (com.google.fonts/check/mandatory_avar_table)
⚠ WARN: Ensure Stylistic Sets have description. (com.google.fonts/check/stylisticset_description)
⚠ WARN: Ensure fonts have ScriptLangTags declared on the 'meta' table. (com.google.fonts/check/meta/script_lang_tags)
⚠ WARN: Checking with ots-sanitize. (com.google.fonts/check/ots)
WARNING: maxp: Bad maxZones: 0 ⚠ WARN: Check font contains no unreachable glyphs (com.google.fonts/check/unreachable_glyphs)
⚠ WARN: Does the font have a DSIG table? (com.google.fonts/check/dsig)
⚠ WARN: Are there any misaligned on-curve points? (com.google.fonts/check/outline_alignment_miss)
Use -F or --full-lists to disable shortening of long lists. [code: found-misalignments] ℹ INFO: Show hinting filesize impact. (com.google.fonts/check/hinting_impact)
ℹ INFO: Font has old ttfautohint applied? (com.google.fonts/check/old_ttfautohint)
ℹ INFO: EPAR table present in font? (com.google.fonts/check/epar)
ℹ INFO: Check for font-v versioning. (com.google.fonts/check/fontv)
ℹ INFO: Font contains all required tables? (com.google.fonts/check/required_tables)
ℹ INFO: List all superfamily filepaths (com.google.fonts/check/superfamily/list)
[21] Sora[wght].ttf🔥 FAIL: Check Google Fonts glyph coverage. (com.google.fonts/check/glyph_coverage)
🔥 FAIL: Check glyphs do not have components which are themselves components. (com.google.fonts/check/glyf_nested_components)
Use -F or --full-lists to disable shortening of long lists. [code: found-nested-components] 🔥 FAIL: Check a font's STAT table contains compulsory Axis Values. (com.google.fonts/check/STAT)
🔥 FAIL: Check variable font instances (com.google.fonts/check/fvar_instances)
🔥 FAIL: Ensure component transforms do not perform scaling or rotation. (com.google.fonts/check/transformed_components)
⚠ WARN: Checking OS/2 achVendID. (com.google.fonts/check/vendor_id)
⚠ WARN: Is there kerning info for non-ligated sequences? (com.google.fonts/check/kerning_for_non_ligated_sequences)
Use -F or --full-lists to disable shortening of long lists. [code: lacks-kern-info] ⚠ WARN: Ensure variable fonts include an avar table. (com.google.fonts/check/mandatory_avar_table)
⚠ WARN: Ensure Stylistic Sets have description. (com.google.fonts/check/stylisticset_description)
⚠ WARN: Ensure fonts have ScriptLangTags declared on the 'meta' table. (com.google.fonts/check/meta/script_lang_tags)
⚠ WARN: Check font contains no unreachable glyphs (com.google.fonts/check/unreachable_glyphs)
⚠ WARN: Ensure dotted circle glyph is present and can attach marks. (com.google.fonts/check/dotted_circle)
⚠ WARN: Does the font have a DSIG table? (com.google.fonts/check/dsig)
⚠ WARN: Are there any misaligned on-curve points? (com.google.fonts/check/outline_alignment_miss)
Use -F or --full-lists to disable shortening of long lists. [code: found-misalignments] ℹ INFO: Show hinting filesize impact. (com.google.fonts/check/hinting_impact)
ℹ INFO: Font has old ttfautohint applied? (com.google.fonts/check/old_ttfautohint)
ℹ INFO: EPAR table present in font? (com.google.fonts/check/epar)
ℹ INFO: Is the Grid-fitting and Scan-conversion Procedure ('gasp') table set to optimize rendering? (com.google.fonts/check/gasp)
PPM <= 65535: ℹ INFO: Check for font-v versioning. (com.google.fonts/check/fontv)
ℹ INFO: Font contains all required tables? (com.google.fonts/check/required_tables)
ℹ INFO: List all superfamily filepaths (com.google.fonts/check/superfamily/list)
Note: The following loglevels were omitted in this report:
|
Hey @emmamarichal are you able to access this ? |
no, not this one either |
Hi @WRRicht3r, what is the status of the project here? :) |
Hi @WRRicht3r |
Hello Emma,
Apologies for the delays with the response. We have been reaching out to
the typeform designer who supported us with the initial implementation, but
have yet to receive a response, therefore we have been unable to
provide the missing assets.
We hope he will get back to us soon so we can close this issue.
Thanks and regards,
William Richter
Head of Ecosystem Growth
…On Wed, Dec 13, 2023 at 4:03 PM Emma Marichal ***@***.***> wrote:
Hi @WRRicht3r <https://github.com/WRRicht3r>
Do you still want we onboard this upgrade, with italics? I just need you
update the repo with the more recent sources :)
—
Reply to this email directly, view it on GitHub
<#5827 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AVCODG5YBUPNASIMHENQ42DYJG7V3AVCNFSM6AAAAAAUGM6MT2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJUGA4DGOBYGQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Too bad this wasn't resolved.. I really like the font, and planned on using it.. only to find out there's no italics. Not sure why it would be posted like this, not very useful? |
Font Project Git Repo URL:
https://github.com/sora-xor/sora-font
Current version:
Version 2.000 https://fonts.google.com/specimen/Sora?query=sora
New available version:
Version number not updated on the repo
Super short description of the upgrade:
Bugs reported in this repo which this upgrade would fix:
sora-xor/sora-font#21
sora-xor/sora-font#20
sora-xor/sora-font#19
sora-xor/sora-font#17
sora-xor/sora-font#16
sora-xor/sora-font#14
this issue isn't really solved: #4898
The text was updated successfully, but these errors were encountered: