Skip to content
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

Greek - Phi Φ - spacing feel loose generally in all roman weights #403

Open
EbenSorkin opened this issue Jan 18, 2024 · 4 comments
Open
Assignees

Comments

@EbenSorkin
Copy link
Collaborator

Greek - Phi Φ - spacing feel loose generally in all roman weights

image Note the 6th style which I am using to compare is ( lower right ) is Commisioner by Kostas Bartsokas
@dberlow
Copy link
Contributor

dberlow commented Jan 19, 2024

Eben,

We do not have sources for opsz0 and do not know what the "Hard-Wrap" axes does. This is important when posting an issue comparing a font with no optical size defined to a mystery location in our font.

I also see from another issue, that the spacing you show is not identified for design space and is not accurate to the sources we provided.

Can you point to the branch where this font, and these styles are being made?

What is the design space of Commisioner? and where is the specimen you are showing in that design space?

@EbenSorkin
Copy link
Collaborator Author

EbenSorkin commented Jan 19, 2024 via email

@davelab6
Copy link
Member

We do not have sources for opsz0

Right, but the way CSS works, when you specify an axis value beyond the axis range, it will clamp to the nearest value that the axis does have. So opsz 0 is a short hand to get opsz min.

and do not know what the "Hard-Wrap" axes does.

This is a possible UX improvement for the https://github.com/vikagrabowska/Octopus web app, but this (iirc) is not an axis setting, but a setting for how many characters to wrap at.

This is important when posting an issue comparing a font with no optical size defined to a mystery location in our font.

I agree that the full instance location should be specified in all issues. The image shows 2 other axes locations, weight 770 and width 100. I was going to ask, Eben, were any other axes set? but you already replied to say only weight.

So there's a UX improvement for Octopus to suggest too, the Show > Parameters feature of https://typetools.typenetwork.com/ :)

I also see from another issue, that the spacing you show is not identified for design space and is not accurate to the sources we provided.

I'm curious how you see this? Seems default spacing for opsz 8 wght 770 to me from a quick look :)

Can you point to the branch where this font, and these styles are being made?

I used the latest build from Marc which was about a week old at the time

Eben, please be very specific; I think its important to use the latest file in this repo (from https://github.com/googlefonts/roboto-flex/tree/main/fonts) not some random version on you HD.

What is the design space of Commisioner? and where is the specimen you are showing in that design space?

https://github.com/kosbarts/Commissioner README tells the design space; I agree knowing its instance location and any other settings is pertinent.

@dberlow
Copy link
Contributor

dberlow commented Jan 19, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants