Add Hyle Deco

[mbaliga]

https://github.com/mbaliga/HyleDeco-gf

Font family name: Hyle Deco
Designer: Madhav Baliga
License: SIL Open Font License 1.1
Upstream repository: https://github.com/mbaliga/HyleDeco-gf
Styles: Regular, Italic (static, hairline design)
Glyph coverage: GF Latin Core, 319 of 319 verified

Hyle Deco is a hairline deco display face built on a constant 44 unit stroke, drawn from hand made vector letterforms. Fontbakery googlefonts profile passes with zero failures on both styles; the report is included in the repository QA folder.

Disclosure: a niche academic Greek typeface named "Hyle 2.0" exists elsewhere. It is not on Google Fonts, is unrelated in design and origin, and the names are distinct. Raising it proactively to save reviewer time.

By opening this issue, I confirm the project meets the following requirements:

• The entire font project is available in a Github repository (repo) and licensed under the OFL
• The source files are available in the repo
• I am the sole copyright author of the entire project, or all other copyright authors have licensed their work to me under the OFL, and I commit to clearly disclosing if AI tools were used in the creation of this project.
• There are no "Reserved Font Names" in the OFL license information, or in the project documentation of any known upstream projects. If there are RFNs, they are not used in whole or in part in this family name, or, I want to discuss how Google can work with my use of them.
• The family name is unique according to namecheck.fontdata.com
• The name of the font family expected to appear on app menus must be very clearly communicated and definitive. It should not include any copyright holder's full names or acronyms.
• The font supports at least the Google Fonts 'Latin Core' glyphset from github.com/googlefonts/glyphsets (direct link)
• The repo has the Google Fonts preferred upstream repo structure
• I have read, agree with, and comply with, the full Google Fonts contributing requirements
• I will maintain the repository and participate in the onboarding process (addressing, solving, and responding to issues, merging pull requests, etc)

[kenmcd]

Claude may need to go back to learning mode.

One source - a Regular UFO with TT curves.
Italic is simply slanted Regular

These images are from the Regular UFO source.

Lots of precision in the outlines - many nodes. (fonts are the same)

Think my favorite is the 7 figure with 862 nodes.

The diacritics may need some work.

Some characters have interesting designs.

Repo says Claude is a contributor - which explains a lot.

[mbaliga]

Claude may need to go back to learning mode.

One source - a Regular UFO with TT curves. Italic is simply slanted Regular

These images are from the Regular UFO source.

Lots of precision in the outlines - many nodes. (fonts are the same)

Think my favorite is the 7 figure with 862 nodes.

The diacritics may need some work.

Some characters have interesting designs.

Repo says Claude is a contributor - which explains a lot.

Thanks for the sarcastic reply. Not knowledgeable about fonts, I drew the alphabets in Figma and asked Claude to convert them into into a font.

Since you did precious little to educate me, allow me some time to figure out how to fix these issues :)

[kenmcd]

Note: I have no relationship to Google Fonts (GF).
I am just another user.

Google Fonts Guide
https://simoncozens.github.io/gf-docs/

FontForge (the free font editor) also has a user manual and design guide.
https://fontforge.org/en-US/
Design With FontForge - http://designwithfontforge.com/

Someone from GF will eventually respond (they are very busy).
While they can be very helpful, they do not have time to educate you.

[bghryct]

@mbaliga you might take a look at https://ohnotype.co/blog/drawing-vectors for an idea of what "well drawn" outlines look like. There are ways to automate path cleanup and Claude may be helpful in that direction as well.

[mbaliga]

Note: I have no relationship to Google Fonts (GF). I am just another user.

Google Fonts Guide https://simoncozens.github.io/gf-docs/

FontForge (the free font editor) also has a user manual and design guide. https://fontforge.org/en-US/ Design With FontForge - http://designwithfontforge.com/

Someone from GF will eventually respond (they are very busy). While they can be very helpful, they do not have time to educate you.

I appreciate you taking the time to educate me. Your previous reply was helpul as well, wry though it may have been. Due to reasons I should not explain and lf my own making, I am constrained at present to only my Android, iPad and Steam deck. Kindly exuse me for my reply.

I apologise for my oversight. I assumed if the glyphs were shaped right I would be in a good place to have Claude to the rest of the plumbing. I have fixed most of the issues you pointed out and I will spend some more time to make sure I have missed abything yet again.

Have a good day!

[kenmcd]

Not sure how you can clean-up these outlines, and fix diacritics, etc. without some sort of font editor.
The outlines are really a mess.

This is the O uppercase cleaned-up and converted to PS curves.

This is the current O uppercase with TT curves, and too many nodes, and outline issues (errors).

The "Short Segment" error is actually a little jog in what should be a straight line.
Here it is zoomed way in...

The collinear lines also needed fixing (causes problems in rasterizers).
This is one character, and they are all like this.

The 7 above with 862 nodes should have only seven nodes (at the corners).

And then GF would have to even be interested in this design.
Kinda doubtful.
But they have surprised me in the past on what they have accepted.

You have a long way to go on the technical issues before it would even be possible.

[mbaliga]

@kenmcd

Figma is a vector editor so I never had the issue with the line segments, i was suprised myself when I saw the screenshots your shared. Here is what I am seeing in Figma, neither the O nor the 7 are as messed up as they ended up.

What happened is I gave Claude PNGs as i was not able to view or attach the SVGs on my phone, and it rasterized the images, breaking them in this manner.