search

AlessioLaiso / aleo

Aleo font family
SIL Open Font License 1.1
33 stars 5 forks source link

Weight Axis variable font Version #2

Open davelab6 opened 5 years ago

davelab6 commented 5 years ago

I'd love to see a variable fonts version of this, with a weight axis. At Google Fonts, I've commissioned the folks at @TypeNetwork to work on upgrading a number of font projects to be variable fonts with a weight axis, and this would be a great candidate! Would you accept a pull request with this change done for you in the next week or so? :)

kevinconroy commented 5 years ago

I certainly would, but also defer to @AlessioLaiso as the creative genius behind Aleo

AlessioLaiso commented 5 years ago

Hi @davelab6, I'd be more than happy to see a variable font version of Aleo! I look forward to accepting the pull request soon.

davelab6 commented 5 years ago

Thanks both! They will be getting a handle on all issues very soon :))

pichotta commented 5 years ago

Using git repo Issues to document information and exchanges as per project guidelines.

On Wed, Oct 2, 2019 at 3:52 PM Jill Pichotta pichotta@typenetwork.com wrote: Hi Alessio,

We are happy to be working with you and the Google fonts team to make a variable version of Aleo. Our goal is to make a one weight axis variable font for each slope, roman and italic.

In order to achieve the highest quality and most efficient long term results we will be converting the source data from Glyphs to UFO. The new source data will be generated in the RoboFont environment using fontmake and ttfautohint.

During the process we will be looking to improve any errors while preserving how the font appears and renders on different platforms. for e.g. there might be a fix the /gcommaaccent in the Light, or /Ccedilla in the Regular but, in general, the transition for the user should be as seamless as possible.

We have started by making a fork off the existing git repository. When the proposed final font is approved we will initiate a pull request.

I see that there are recent UFOs added to the repo. I would like to confirm, are the Glyph sources and generated TTFs and OTFs are still the most current data? We may instead choose to work from those and comparing them to what is currently being served at fonts.google.com

We hope this answers some of your questions about the process. Please let us know if you have any additional comments.

Best Regards,

Jill Pichotta Vice President Type Network pichotta@typenetwork.com

On Wed, Oct 2, 2019, 5:49 PM Alessio Laiso hello@alessiolaiso.com wrote: Hi Jill,

Thank you for the details, that sounds great!

Answering your question: the most current data are the Glyphs sources and the UFO files, not the generated TTFs and OTFs.

I'll be happy to answer any additional questions that may come up during the process, so feel free to write.

Best, Alessio

pichotta commented 5 years ago

Hi Alessio,

A couple questions about the source data: Were the Glyph sources compatible at one time? i.e. Is there are reason that the curves in the Bold have considerably more points? and, is there a reason that the Light has serif components but not the other styles?

Do you know if the generated TTFs and OTFs are the same as what is currently being served on fonts.google.com?

Thank in advance for any information : )

AlessioLaiso commented 5 years ago

Hi Jill,

Unfortunately the Glyphs sources were never compatible - this was the problem I had highlighted in my very first email. When I first designed Aleo each style was in an individual file in FontForge, so compatibility was not a concern back then, and honestly I'm not really able to tell you why some styles have way more points than others (I should have to ask my inexperienced self 7 years ago).

The Light has serif components because it was a first attempt at cleaning up the masters, carried on together with the guys at Prezi, but it was not finished for all the styles.

Yes, as far as I know, the TTFs and OTFs are the same as what's served on Google Fonts.

You're very welcome!

Edit: since Aleo is based on Lato, many of the incompatible letters could be recovered from Lato and that should fix the issues for the paths with too many points.

pichotta commented 5 years ago

Hi Alessio,

Thank you for the information on Aleo, and its reference Lato. The Aleo family is still on the list but given the amount of point incompatibility we will be returning to it again in month or two. We will post another notification here when we resume. Thank you for your patience.

Best,

Jill

AlessioLaiso commented 5 years ago

Thank you very much, Jill. I look forward to getting an update from you soon!