Google Fonts Improvement Project [Work log]

[Thomas Jockin]

For the last week I've been working on improving fonts Lobster and Bangers.

I made Github Repos for each project.

Lobster: https://github.com/ThomasJockin/The-Lobster-Font

Banger: https://github.com/googlefonts/bangers

Main focus of improvement was character set expansion.

Here were my steps for both:

Run Glyphs > Update Glyph Info, and manually rename glyph names to GlyphsApp names

Run delete stray nodes script

Delete duplicate paths

report nodes with acute angle

Correct Path direction for whole glyph set

Cleaning TTF contours

fix existing glyphs marked red with drawing issues

Add relevant glyph set, with Glyphs “Filter List” feature

build auto components

auto-align components

Use color marking to set up glyphs to be drawn

automatically adds acutecomb from acute, etc.

Added automated anchors for whole set (cmd+U) to test the component glyphs

Adjusted anchors where needed

Set Ogonek mark anchor position

Correct Lcommaaccent vs Lcaron

check anchors (eg, is lowercase ‘z’ automatic alignment working with marks)

Export OTF to check there are no error message

Review spacing in a systematic proofing system

Fix any major spacing problems

draw the glyphs that must be drawn, eg currency symbols

[Alexei Vanyashin]

Cleaning TTF contours

Wait...

Why not convert to PS outlines first? FL: Contour > Convert > to PS

Or you mean cleaning up rudiments from TTF> PS conversion?

>automatically adds acutecomb from acute, etc.

very useful stuff! Which of the scripts do you use for this? 

[Thomas Jockin]

Yes, I meant clean up.

For the acutecomb: https://github.com/mekkablue/Glyphs-Scripts/blob/master/Anchors/Combining%20Accent%20Maker.py

[Alexei Vanyashin]

Thanks!

[Dave Crossland]

On Jul 8, 2016 9:38 PM, "Thomas Jockin" <tho...@thomasjockin.com> wrote:
>
> For the last week I've been working on improving fonts Lobster and Bangers.

:)

> Run Glyphs > Update Glyph Info, and manually rename glyph names to GlyphsApp names

It would be great to note where you have done this in your daily updates, so that we can build a better autonaming script to accelerate the job :) 

> Cleaning TTF contours

I thought the Bangers and Lobster sources were with PS outlines?

> fix existing glyphs marked red with drawing issues

How are the glyphs marked red?

> Review spacing in a systematic proofing system

Please add the proof PDFs to the repo :) 

[Thomas Jockin]

Dave,

>I thought the Bangers and Lobster sources were with PS outlines?

They are. I should have removed "TTF" from my description on my step. I apologize for the confusion.

In Bangers, the outline rendering was.. interesting. 

In several cases I had to put the outline to the BG, and then redraw shapes to use for related glyphs.

>How are the glyphs marked red?

I marked them red if there was a error w/ <caution> symbol in the upper right corner. 

I would review and remove red mark after error is cleared.

> Please add the proof PDFs to the repo :) 

They are in the Bangers and Lobster repos in /documentation.

Would you like it in another repo?

[Pablo Impallari]

Thomas, you have lost most of the features for final forms, etc... in the glyphs migration.
Have a look at the original lobster liga feature, there is a lot included there beside the the basic f_i, f_l... for both Latin and Cyr

--
You received this message because you are subscribed to the Google Groups "Google Fonts Discussions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to googlefonts-dis...@googlegroups.com.
To post to this group, send email to googlefon...@googlegroups.com.
Visit this group at https://groups.google.com/group/googlefonts-discuss.
To view this discussion on the web visit https://groups.google.com/d/msgid/googlefonts-discuss/08854d71-2224-40fb-a918-3b9a9cb29ec4%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

Un Abrazo
Pablo Impallari

[Dave Crossland]

On 9 July 2016 at 15:38, Thomas Jockin <tho...@thomasjockin.com> wrote:

>I thought the Bangers and Lobster sources were with PS outlines?

They are. I should have removed "TTF" from my description on my step. I apologize for the confusion.

In Bangers, the outline rendering was.. interesting. 

In several cases I had to put the outline to the BG, and then redraw shapes to use for related glyphs.

Yeeeeaaaaappppp.... Thanks for doing this :) 

 

>How are the glyphs marked red?

I marked them red if there was a error w/ <caution> symbol in the upper right corner. 

I would review and remove red mark after error is cleared.

Great to know :) 

 

> Please add the proof PDFs to the repo :) 

They are in the Bangers and Lobster repos in /documentation.

Would you like it in another repo?

No that's perfect! :) 

[Thomas Jockin]

Hi Pablo,

To clarify, the issue is the opentype feature for final forms is absent in the version I pull requested. 

My version only had the basic f_i, f_l liga feature defined.

Do I have that correct?

To unsubscribe from this group and stop receiving emails from it, send an email to googlefonts-discuss+unsub...@googlegroups.com.

To post to this group, send email to googlefon...@googlegroups.com.
Visit this group at https://groups.google.com/group/googlefonts-discuss.

To view this discussion on the web visit https://groups.google.com/d/msgid/googlefonts-discuss/08854d71-2224-40fb-a918-3b9a9cb29ec4%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Pablo Impallari]

Yep,

Final forms, ligatures and some other stuff I don't remember... it was 6 years ago. Alexei also added more stuff for Cyr a few years later.

We included everything in "liga" so it's always on by default.

To unsubscribe from this group and stop receiving emails from it, send an email to googlefonts-dis...@googlegroups.com.

To post to this group, send email to googlefon...@googlegroups.com.
Visit this group at https://groups.google.com/group/googlefonts-discuss.

To view this discussion on the web visit https://groups.google.com/d/msgid/googlefonts-discuss/08854d71-2224-40fb-a918-3b9a9cb29ec4%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

Un Abrazo
Pablo Impallari

--

You received this message because you are subscribed to the Google Groups "Google Fonts Discussions" group.

To unsubscribe from this group and stop receiving emails from it, send an email to googlefonts-dis...@googlegroups.com.

To post to this group, send email to googlefon...@googlegroups.com.
Visit this group at https://groups.google.com/group/googlefonts-discuss.

To view this discussion on the web visit https://groups.google.com/d/msgid/googlefonts-discuss/58d51810-3436-4376-94fd-ef86249ed696%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Thomas Jockin]

Pablo,

Ok, Thank you for the alert!

Will investigate tomorrow.

-TJ 

[Alexei Vanyashin]

I had a similar problem when I ported Lobster from VBF to Glyphs.

To make all Lobster OT features work, they need to be written manually. 

(Glyphs does not automate them)

I have already done this previously, so here is a patch for Thomas:

https://github.com/ThomasJockin/The-Lobster-Font/pull/1 

My patch also includes 14 extra Cyrillic glyphs which I added in April 2016.

[Dave Crossland]

On 9 July 2016 at 18:30, Alexei Vanyashin <a...@cyreal.org> wrote:

I have already done this previously,

I think this is a good example of why I recommend and request posting daily status updates, rather than weekly ones :) 

[Thomas Jockin]

Work to do today:

• Review Alexei's link and correct Lobster liga feature issue

• Proceed with Quicksand improvement. Revising both Light and Bold Masters up to hamburgedfontstiv 

[Thomas Jockin]

Update on Today's work:

• Merged Alexei's patch for the lost liga features. Did a light review and it looked good, but I will go a more intensive review tomorrow.

• Made corrections to Quicksand project. Mainly loosing spacing in Light master + Proportion adjustments.

One of the significant changes today was to the /r. Left is the before. Middle is after. Right is overlay.

[Alexei Vanyashin]

One of the significant changes today was to the /r. Left is the before. Middle is after. Right is overlay.

Thomas: 

You fixed the clogging problem alright, 

but also introduced a new 'terminal feature' in the design.

How does this align with the rest of the charset, i.e a, e, c ..?

I'm still curious if it would be easier/faster to draw a monoline font, 

and apply the noodler filter. But you won't have the terminal feature then, 

and the result will me more mechanical than what you have. 

What are your thought on this?

 

[Thomas Jockin]

Alexei,

I see the /r as different kind of terminal than in the /e, /c, /a.

The /a in this design is a one story /a. That is related to the /d, /q.

The /c and /e terminals transition to a smooth round shape.

The /r has to deal with a joint structure similar to /n, /m. 

Contrast was introduced to the joints of the /n, and /m.

In a bold weight, that means a rapid transition of weight at the joint from the left stem to the terminal.

Thus, the rapid contrast shifting you pointed out.

Personally, I don't see this as a conflict if the tactic is an improvement in how words look and feel.

Most likely, a similar tactic will have to be done to the tail of the /R to maintain consistency.  

[Thomas Jockin]

Mid Day Update:

• Wrapping Up Corrections to both Masters in Hamburgedfontsiv Proof. 

Doing one more Round of Proof and then off to Full Alphabet + Numbers.

Will Post Proof PDF in the Quicksand Improvement Thread.

• Switching to a more intensive review of the liga feature correction in Lobster.

[Alexei Vanyashin]

Here is what I changed:

Renamed .liga glyphs to .end 

en_che-cy.liga > en_che-cy.end etc

Moved CYR ligature from dlig to liga:

script cyrl;

sub Ie-cy ze-cy by Ie_ze-cy;

Added lookups in .liga for CYR, and LAT:

lookup endings_cyr {

  sub [ha-cy ze-cy]' @todas_cyr by [ze-cy.init ha-cy.init];

  ignore sub @having_finals_cyr' @todas_cyr;

  sub @having_finals_cyr' by @finals_cyr;

} endings_cyr;

They refer to classes, which were added manually. 

[Alexei Vanyashin]

Thomas, please check my PR #2

[Thomas Jockin]

Update on Lobster:

Had discussion with Alexei this afternoon about the merged files between us. Alexei is doing a clean up of the file and getting back to me to proceed with QA'ing the liga feature.

[Dave Crossland]

Thomas posted this on dribbble too :) https://dribbble.com/shots/2831212-Google-Fonts-Improvement-Project-Quicksand-r

[Alexei Vanyashin]

On Tuesday, July 12, 2016 at 9:37:42 PM UTC-4, Thomas Jockin wrote:

Update on Lobster:

Had discussion with Alexei this afternoon about the merged files between us. Alexei is doing a clean up of the file and getting back to me to proceed with QA'ing the liga feature.

Here you go.

I checked with the previous version to make sure all features are intact. The only difference was

in the lookups, which I added. 

Some old-school stuff!

 

[Thomas Jockin]

Great! Thanks Alexei!

On my end, I continued with my raisin project, Quicksand. Didn't get to full alphabet for both masters, but should make it by tomorrow. Some of the progress today:

Original on the Left. 

Adjusted in the Middle. 

Overlay of before and after on Right. 

Introduced tapering into the /x 

bumped up x-height 

Introduced contrast in vertical strokes. 

Helped make the /c fill its space better.

[Khaled Hosny]

On Wed, Jul 13, 2016 at 12:53:26PM -0700, Alexei Vanyashin wrote:
> On Tuesday, July 12, 2016 at 9:37:42 PM UTC-4, Thomas Jockin wrote:
> >
> > Update on Lobster:
> >
> > Had discussion with Alexei this afternoon about the merged files between
> > us. Alexei is doing a clean up of the file and getting back to me to
> > proceed with QA'ing the liga feature.
> >
> >

> Here <https://github.com/ThomasJockin/The-Lobster-Font/pull/3> you go.

>
> I checked with the previous version to make sure all features are intact.
> The only difference was
> in the lookups, which I added.
>
> Some old-school stuff!

Any specific reason to use these deprecated afii names?

Regards,
Khaled

[Dave Crossland]

On 13 July 2016 at 20:37, Thomas Jockin <tho...@thomasjockin.com> wrote:

On my end, I continued with my raisin project, Quicksand. Didn't get to full alphabet for both masters, but should make it by tomorrow. Some of the progress today:

Great to see :) 

[Alexei Vanyashin]

Any specific reason to use these deprecated afii names?

Absolutely no reason!

This screenshot shows the old version that I used to cross-check 

if all the OT features in the new version are intact.

When we convert an old font source file, say from VBF to Glyphs, 

the first thing we do is Update Glyph Info, 

which renames all the glyphs to Nice names. 

On export they are converted to production names (uniXXX). 

The problem was that Lobster had ~150 various ligatures

using the afii naming scheme, so I ensured the names

were updates in all features (liga, dlig, salt, init, etc.) 

 

[Dave Crossland]

On 13 July 2016 at 21:21, Alexei Vanyashin <a...@cyreal.org> wrote:

The problem was that Lobster had ~150 various ligatures

using the afii naming scheme, so I ensured the names

were updates in all features (liga, dlig, salt, init, etc.) 

Great stuff :) Thank you Alexei!

[Khaled Hosny]

On Wed, Jul 13, 2016 at 06:21:25PM -0700, Alexei Vanyashin wrote:
>
> > Any specific reason to use these deprecated afii names?
>
> Absolutely no reason!
> This screenshot shows the old version that I used to cross-check
> if all the OT features in the new version are intact.

I see, thanks.

Regards,
Khaled

[Thomas Jockin]

Today's update:

Cleared through the rest of the alpha. 

Built out accent characters, placed accents, etc. to clear it out next week early.

Today's comparisons:

Left original.

Middle adjusted.

Right overlay.

/Q

• Filled out the curves 

• Got gunk out of joint as the tail connects to the main part

• Smoothed out the tail

/x

• Increase x-height

• introduced tapering for secondary strokes to remove gunk.

[Dave Crossland]

Nice! :) 

[Omer Ziv]

I love seeing this comparisons, thanks for posting Thomas!

On Friday, July 8, 2016 at 9:38:40 PM UTC-4, Thomas Jockin wrote:

For the last week I've been working on improving fonts Lobster and Bangers.

I made Github Repos for each project.

Lobster: https://github.com/ThomasJockin/The-Lobster-Font

Banger: https://github.com/googlefonts/bangers

Main focus of improvement was character set expansion.

Here were my steps for both:

Run Glyphs > Update Glyph Info, and manually rename glyph names to GlyphsApp names

Run delete stray nodes script

Delete duplicate paths

report nodes with acute angle

Correct Path direction for whole glyph set

Cleaning TTF contours

fix existing glyphs marked red with drawing issues

Add relevant glyph set, with Glyphs “Filter List” feature

build auto components

auto-align components

Use color marking to set up glyphs to be drawn

automatically adds acutecomb from acute, etc.

Added automated anchors for whole set (cmd+U) to test the component glyphs

Adjusted anchors where needed

Set Ogonek mark anchor position

Correct Lcommaaccent vs Lcaron

check anchors (eg, is lowercase ‘z’ automatic alignment working with marks)

Export OTF to check there are no error message

Review spacing in a systematic proofing system

Fix any major spacing problems

draw the glyphs that must be drawn, eg currency symbols

[Jacques Le Bailly]

Solid !

Op donderdag 14 juli 2016 23:09:57 UTC+2 schreef Thomas Jockin:

[Thomas Jockin]

Today's update.

Polishing the GoogleFonts LatinPro Character Set for Quicksand Light.

Today's comparison from Dribbble:

Adjusted on Left.

Original on Right.

• Legibility of the /ae gets lost with the one story form of /a. Switched it to a two story a.

• Redrew almost all of the accents. The ogonek is a good case study. 

The terminal of the ogonek should match the main letterform stroke terminal.

[Dave Crossland]

On IM Thomas mentioned the great comments on https://dribbble.com/shots/2844841-Google-Fonts-Improvement-Project-Quicksand too :)

​

[Thomas Jockin]

Today's Update:

 Original on Left. 

Adjusted in Middle. 

Overlay on the Right.

Some of today's major adjustments: 

• Redrew the /at. Gave it a more organic italic momentum. 

• Modified the /sterling. Lighten its weight + Gave it a more smooth, organic feel for its spine.

Follow along on Dribbble:

https://dribbble.com/shots/2844841-Google-Fonts-Improvement-Project-Quicksand

[Thomas Jockin]

Started the GoogleFonts LatinPro adjustment work for Quicksand Bold. Proofing is key to all.

 

[Thomas Jockin]

Today's update: Revision on Left Original in Middle Overlay on Right

 

Working on the Bold weight Ext'd Latin. Following the revision in the ogonek of the light master, now applying it to the bold weight. You can also notice the lightening of weight for both the /A and /e.

[Alexei Vanyashin]

Thomas,

The ogonek looks good, 

you have probably seen this, 

I think this link is worth posting here,

Adam Twardoch's guide on Polish Diacritics:

This has just inspired me to add Polish Kreska alternates to the Recommended glyphs for GF Latin Plus:

Cacute.loclPLN Nacute.loclPLN Oacute.loclPLN Sacute.loclPLN Zacute.loclPLN cacute.loclPLN nacute.loclPLN oacute.loclPLN sacute.loclPLN zacute.loclPLN acutecomb.loclPLN acutecomb.loclPLN.case

[Dave Crossland]

On 22 July 2016 at 11:54, Alexei Vanyashin <a...@cyreal.org> wrote:

The ogonek looks good, 

Looks awesome! 

[Thomas Jockin]

Wrapped up the GoogleLatin Plus Character set expansion for the Bold Master today.

One fun demo of adjustments that had to be tackled is the /peso.

Original on top left.

Adjusted on bottom left.

Overlay on right.

The /peso in the Bold master had to get SERIOUS tapering in the interior horizontal bars to not get too heavy. 

Fun to notice, I had to take away black from horizontal bars asymmetrically to harmonize the inner white counter to the top and bottom counters.
This is will have to be watched when interpolating the instances weight /peso, but it's the best option to maintain legibility in the Bold /peso.

 

[Alexei Vanyashin]

Thomas, 

Have you considered altering the design for Bold, 

and then using the Glyphs App bracket trick for interpolating other styles?

[Dave Crossland]

I'm not sure about how flexible the peso design is. I hope some designers in Latin America might be interested to comment; this specific issue might be worth asking on Type Drawers or elsewhere :)

[Thomas Jockin]

Hi Alexei,

Yes, that is an option.

However, that would require all the other strike through currency to follow the same method. 

The /peso is the only currency where the legibility was compromised. 

Does one change the whole system for one glyph, or adjust that one glyph to fit the system?

[Thomas Jockin]

Spent the day getting the masters to be compatible. 

 Did want to start adding the stylistic alternates for Quicksand. 

 Here's the proposed two story /a as an alternate.

[Dave Crossland]

I'm good with the optically corrected peso :) 

I guess the instances can be from 200 to 800, looking at those 2 a's, but currently on Google Fonts there are 300, 400 and 700 weights. 

I wonder if perhaps making the 300 thicker and the 700 thinner, and adding a 200 and 800, would be good; the existing weights are being totally respaced afterall. 

[Thomas Jockin]

Now building out the two interpolated weights between the Light and Bold masters. It's looking like we can squeeze out two steps between the masters.

[Dave Crossland]

On 27 July 2016 at 20:31, Thomas Jockin <tho...@thomasjockin.com> wrote:

It's looking like we can squeeze out two steps between the masters.

Great! :)

[Nhung Nguyen]

Hi Thomas!

Excellent job at improving the font. It looks really great. I've just reviewed the Vietnamese blocks, and I have some recommendation:

- abreve: the breve looks like it's not at the center of a. Maybe we can move it a bit to the right?

- hookabove: I think it should be a bit narrower the thin weight. It's a little bit too wide at the moment.

- Horn: is it your intention to design the horn to look like a swash? If not I think it's not suitable to the style of the font. And the horn in Uhorn makes me feel hard to distinguish. Maybe pull the horn up, redesign it to be simpler so it'd be easier to distinguish.

- Hookabove stacked: in ocircumflexhookabove you put the hookabove to the right of the circumflex but in others you didn't move it to the right. I think we should move all the hookabove to the right of circumflex though!

I think that's all for now. Good job again! :D

[Nhung Nguyen]

Screenshot to explain more about my points:

[Dave Crossland]

Nhung, since Thomas has moved on to new projects, please fix the Vietnamese directly :) https://github.com/ThomasJockin/QuicksandFamily/branches shows Thomas worked only in the master branch :)

[Alexei Vanyashin]

Following up on the Peso question. Here is an example from Bitter, by Argentinian-born designer Sol Matas

However, note that Argentina, Mexico and Dominican Republic use $ as a sign for their local Peso. 

Link on Philippine Peso

[Alexei Vanyashin]

If you follow my link, 'Yuki' follows similar approach as Thomas. 

[Thomas Jockin]

This week, I am working on improving Amatic SC:

https://fonts.google.com/specimen/Amatic+SC

I'm tasked with respacing the Regular and Bold weights w/ a tighter fit to match the Hebrew designed by Ben Nathan.

I started my work with the first pass on spacing yesterday:

https://www.dropbox.com/s/1c1afgirtxvffeq/amatica_fontproof-2_11_08_16.pdf?dl=0

You can follow along on my Github:

https://github.com/ThomasJockin/Amatica-sc

[Thomas Jockin]

Continued work on Amatic's spacing.

Plan on getting to Full Alphabet proof tomorrow.

https://www.dropbox.com/s/xzge5qz78dik6pb/amatica_fontproof-11_10_16.pdf?dl=0

[Thomas Jockin]

Continued expansion of Amatica SC.

First round of full alphabet proof.

https://www.dropbox.com/s/b5ubjx85g2dpxds/amatic_fontproof-11_11_16.pdf?dl=0

-TJ

[Thomas Jockin]

Started respacing the numerals yesterday.

Continued today and started to expand the character set to Google Fonts Pro.

[Dave Crossland]

Thanks Thomas! In the last page there are 4 quadrants, with the 2 weights each, but what is each quadrant?

The essence of this project is that the work done by Vernon and Ben Nathan in Amatica SC is respaced to be much closer to the version of Amatic SC that is in fonts.google.com today. 

I'd appreciate some 3-up comparisons (eg, top left, top right, bottom left - and 3 cols - and 3 lines interleaved) with the regular and bold of the Amatic SC original, Amatica SC, and your new version. 

[Thomas Jockin]

The last page contains Caps only and Mixed case usages of the Regular and Bold weight.

Sure, I'll make the 3-up comparisons tomorrow.

[Dave Crossland]

On Nov 15, 2016 9:00 PM, "Thomas Jockin" <tho...@thomasjockin.com> wrote:
>
> The last page contains Caps only and Mixed case usages of the Regular and Bold weight.

I mean which font files are which?

> Sure, I'll make the 3-up comparisons tomorrow.

Thank you :)

> On Tuesday, November 15, 2016 at 4:27:21 PM UTC-5, Dave Crossland wrote:
>>
>>
>>
>> Thanks Thomas! In the last page there are 4 quadrants, with the 2 weights each, but what is each quadrant?
>>
>>
>>

>> The essence of this project is that the work done by Vernon and Ben Nathan in Amatica SC is respaced to be much closer to the version of Amatic SC that is in fonts.google.com today. 
>>
>> I'd appreciate some 3-up comparisons (eg, top left, top right, bottom left - and 3 cols - and 3 lines interleaved) with the regular and bold of the Amatic SC original, Amatica SC, and your new version. 
>>
>>

> --
> You received this message because you are subscribed to the Google Groups "Google Fonts Discussions" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to googlefonts-dis...@googlegroups.com.
> To post to this group, send email to googlefon...@googlegroups.com.
> Visit this group at https://groups.google.com/group/googlefonts-discuss.
> To view this discussion on the web visit https://groups.google.com/d/msgid/googlefonts-discuss/8ce3f2e6-5ac2-4381-bf9c-bf5dfd13e198%40googlegroups.com.
>
> For more options, visit https://groups.google.com/d/optout.

[Thomas Jockin]

>>I mean which font files are which?

I don't follow. 

The Amatica SC file I was given to work with had Capitals and Small Caps in the file.

The proof contains only my adjusted Amatica font file.

The 3-up comparison will be presented tomorrow.

[Dave Crossland]

Im confusing myself 😆 To confirm the top left and top right are both small caps and the bottom left and right are all caps, and it's all your latest iteration that started with Amatica SC? :)

[Thomas Jockin]

On Wednesday, November 16, 2016 at 12:04:27 AM UTC-5, Dave Crossland wrote:

Im confusing myself 😆 To confirm the top left and top right are both small caps and the bottom left and right are all caps, and it's all your latest iteration that started with Amatica SC? :)

Yes. 

Here's the comparisions you've requested, Dave;

Here's Animated GIFs:

[Thomas Jockin]

Started yesterday on expanding the character set for Amatica Sc.

Working on Revisions and correcting errors today and tomorrow.

Amatica SC Bold

Amatica SC Reg 

[Jacques Le Bailly]

Hi Thomas,

going crazy on the GIFs again :)

Looking good !

[Thomas Jockin]

I'm all about those GIFs ;-)

Today's update:

Refined Google Plus Character Set Spacing

Expanding to Vietnamese accents tomorrow.

-TJ 

[Dave Crossland]

On 16 November 2016 at 08:32, Thomas Jockin <tho...@thomasjockin.com> wrote:

>

> Here's the comparisions you've requested, Dave;

Great!

I made 2 new GIFs showing the before/after from current to your latest

[Thomas Jockin]

My workstation computer died on my earlier in the week. 

Thankfully I've moved over to a temporary station for the moment to continue my work on Amatica SC.

Worked on Vietnamese Characters for the Reg.weight.

Should have everything completed by the end of the week.

[Thomas Jockin]

Completed work on Amatica SC at the end of last week.

Started working on Josefin Sans italics

Work on the Google Fonts Improvement project continues!

Circling back to Josefin Sans' italic, there's some good points about making italics.

• Round shapes like /O or /e if just skewed linearly will look smooched on some parts of their curve profile, and flat on other parts of the curve. 

Doing a transformation of 50% of the italic slant as skew, 50% of the italic slant as rotation, and them optical corrections gives a much better result.

Worked up to Hamburgedfontsiv for both Thin and Bold masters.

[Thomas Jockin]

Worked on expanding to full alphabet for both Light and Bold master.

Should have proofs up tomorrow AM.

-TJ

[Dave Crossland]

On 2 December 2016 at 09:53, Thomas Jockin <tho...@thomasjockin.com> wrote:

Completed work on Amatica SC at the end of last week.

Marc please queue this up for next week :)

[Dave Crossland]

On 6 December 2016 at 17:25, Thomas Jockin <tho...@thomasjockin.com> wrote:

Should have proofs up tomorrow AM.

Awesome!! :)

Agree with the rotate + skew technique

[Thomas Jockin]

Completed the full alphabet over the weekend.

Continued onto the GooglePlus Latin character set expansion for the Bold weight.

https://github.com/ThomasJockin/JosefinSansFont-master/blob/592bdada4c92a864069439278f45417cfc70a8d3/documentation/proofs/JosefinSans-Bold_Italic-12.12.16_B.pdf

First pass on the expansion; things need adjustment and correction.

[Dave Crossland]

Swish:)

[Thomas Jockin]

Started work on Josefin Sans Italic Light master Google Latin Plus Character set.

Didn't complete a pass today. Will have proof up tomorrow.

[Thomas Jockin]

First pass on the Josefin Sans Thin Italic Character Set Expansion.

https://github.com/ThomasJockin/JosefinSansFont-master/blob/623369165e6668d3a3da7279cd646b89688967c0/documentation/proofs/JosefinSans-Thin_Italic-12.14.16_B.pdf

Will make corrections tomorrow. 

Will do first pass of kerning on Friday.

-TJ

[Thomas Jockin]

First pass of kerning for masters and instances for Josefin Sans.

Kerning Proof

Taking another pass tomorrow.

[Dave Crossland]

Great stuff Thomas! Santiago, I wonder if you could take a look in the next day or two and provide any comments to Thomas before this wraps up 

[Thomas Jockin]

Josefin Sans Italic is ready for mastering.

[Dave Crossland]

Thank you Thomas! Marc, please queue this up at the top of the 'hotfixes' as what is in production is buggy

On 7 February 2017 at 05:21, Thomas Jockin <tho...@thomasjockin.com> wrote:

Josefin Sans Italic is ready for mastering.

--

You received this message because you are subscribed to the Google Groups "Google Fonts Discussions" group.

To unsubscribe from this group and stop receiving emails from it, send an email to googlefonts-discuss+unsub...@googlegroups.com.
To post to this group, send email to googlefonts-discuss@googlegroups.com.

Visit this group at https://groups.google.com/group/googlefonts-discuss.

To view this discussion on the web visit https://groups.google.com/d/msgid/googlefonts-discuss/89100360-9dba-4119-af8c-43d8e93b98eb%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

Cheers
Dave

[Marc Foley]

Thank you Mr Jockin,

I'll get this sorted tomorrow.

[Marc Foley]

Has Josefin Sans been pushed to git?

[Thomas Jockin]

Yes: https://github.com/ThomasJockin/JosefinSansFont-master

[Marc Foley]

Hey Tom and Dave,

We can't actually release this.

The old version had another weight, SemiBold. If we release without this weight, it will break people's sites.

I suggest we squeeze in another weight. The Bold in our new version is much darker so we can definitely accommodate a SemiBold in the range.

Cheers,

Marc

[Thomas Jockin]

Thanks for the heads up, Marc.

I added the instance in my Glyph files and synced it to my git.

-TJ