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

Fix issues in the Feb update #410

Merged
merged 93 commits into from
Feb 25, 2021
Merged

Fix issues in the Feb update #410

merged 93 commits into from
Feb 25, 2021

Conversation

aaronbell
Copy link
Collaborator

@aaronbell aaronbell commented Feb 13, 2021

Summary of the Pull Request

A small set of fixes that resolves a couple of new bugs introduced in the latest version, plus other fixes I have been working on.

PR Checklist

Detailed Description of the Pull Request / Additional comments

Full changelist:

  • Repositioned tilde in related ligatures. Previously it was higher than the standard one.
  • Added missing vietnamese anchors on acute and grave (futureproofing).
  • Corrected / made consistent greater & less positioning in </> and <$> related ligatures.
  • Otherwise reviewed hinting

aaronbell and others added 30 commits June 29, 2020 17:15
Decreased Bold weight, added anchors to lowercase Greek, updated GDEF feature builder. Added font linking to STAT.
Reduced weight of bold extreme for better alignment with Regular. Resolved some introduced bugs in hinting and glyph widths.
This reverts commit 25dc61a.
Updating code for the build process and adding in a separate hinting file for the PL glyphs.
Updates build script to include madig's modifications, plus adds static TTF export and autohinting using ttfautohint (if available). Also updated / renamed the Nerdfonts PL file.
- Adjusted box drawing characters for better alignment to the letters
- Added anchors to all alphabetic characters (also brevecomb-cy which was missing them)
- added a fi and fl ligature (and decompose them so they never show up :) )
- improved weight of horncomb (lowercase) in bold
Changing contour order for Extralight to resolve interpolation error
1) Added support for Salishan language groups
2) Remastered mark positioning for glyphs with 2 diacritics (needed for Salishan)
3) Rebuild Build Script to simplify code
4) Fixed minor other hinting issues
5) Fixed RVRN substitutions for heavy weight
Also it wants to update the hyphen glyph, but I don't see any specific changes.
Re-adding the static folder
- updates macronbelow design
- increases overlap on middle positions for infinite arrows
- remove iacute_j ligated forms, added jacute forms
- removed Catalan locl substitutions
- updated a couple of hints
@aaronbell
Copy link
Collaborator Author

Adding a few more updates :)

@DHowett
Copy link
Member

DHowett commented Feb 24, 2021

@aaronbell this good for release soon? I'm happy to review/sign off and tag it 2102.23 if so :)

@aaronbell
Copy link
Collaborator Author

@DHowett the only other thing that might be worth doing is the postscript name issue I emailed you about a little while ago. Did you have thoughts on that?

Forgot to set this back to 1200! Oops ❌
- reverted nameID 4 modification
- disabled underline variation as MVAR not properly supported.
@aaronbell
Copy link
Collaborator Author

aaronbell commented Feb 24, 2021

@DHowett I've submitted another couple of small fixes to resolve the postscript issue and prevent MVAR table generation. Should be good to go.

@DHowett
Copy link
Member

DHowett commented Feb 25, 2021

Thanks! I'll build this into the next version of Terminal. Unfortunately, I missed the boat for this one by just a hair, so I'll hold back just a little while to avoid breaking people.

I have GOT to get Cascadia out of our package. Good lord.

@aaronbell
Copy link
Collaborator Author

@DHowett It'd probably be good—I think you can set up the packages such that the Windows Terminal one will automatically download a "Cascadia Code" one.

That way we could also put the PL fonts in too, no? Then folks wouldn't have to download them separately!

Ben Kiel mentioned that there are edge cases in Dutch where one would not want to have a jacute following an iacute, and that safer behavior is to only swap in cases where the j is followed by an acutecomb—a use case already covered by ccmp.

I will likely add back a accented form of the ij and IJ glyphs, but that can be at a later date :)
@DHowett DHowett changed the title Fixes FIx issues in the Feb update Feb 25, 2021
@DHowett DHowett changed the title FIx issues in the Feb update Fix issues in the Feb update Feb 25, 2021
@DHowett DHowett merged commit f91a925 into microsoft:main Feb 25, 2021
@DHowett
Copy link
Member

DHowett commented Feb 25, 2021

@aaronbell whoops, ufolint got real mad about this. I also fixed the PR trigger so it would fail future PRs for linting errors.

2021-02-25T20:00:28.8261060Z Test result that led to failure:
2021-02-25T20:00:28.8365140Z [FAIL] sources/CascadiaCode-Bold.ufo/glyphs.public.background contains rogue files not listed in contents.plist: gheupturn-cy.glif, asciitilde_equal.liga.glif, less_less_equal_start.seq.glif, quotedblbase.glif, g.glif, less_less_equal_middle.seq.glif, parenleft_asterisk.liga.glif, ka-cy.glif, kaiS_ymbol.glif, A_lpha-latin.glif, idotless.glif, dcaron.alt.glif, G_stroke.glif, N_hookleft.glif, greater_greater_hyphen_middle.seq.glif, kappa.glif, numbersign_underscore_parenleft.liga.glif, greater_greater_equal_start.seq.glif, quoteright.glif, nine.glif, quotesinglbase.glif, d.glif, greater_greater_equal_middle.seq.glif, quoteleft.glif, p.glif, greater.center.glif, numbersign_middle.seq.glif, less_less_hyphen_middle.seq.glif, rho.glif, less_less_hyphen_start.seq.glif, greater_greater_hyphen_end.seq.glif, six.glif, onehalf.glif, K_aiS_ymbol.glif, nhookleft.glif, asterisk_parenright.liga.glif, greater_greater_equal_end.seq.glif, less_less_hyphen_end.seq.glif, greater.alt.glif, less_less_equal_end.seq.glif, notedbl-musical.glif, kadescender-cy.glif, degree.glif, dashdownA_rrow.glif, integraltp.glif, integralbt.glif

This seems like a very much not good thing? Are these dead old files that got moved and replaced? I noticed some things got moved out of background into public but didn't know enough to ask.

@DHowett
Copy link
Member

DHowett commented Feb 25, 2021

I suspect that the files in the background/ directory are outdated and should have been deleted because in the previous update you moved them into the non-background one?

@aaronbell
Copy link
Collaborator Author

Yeah, all those files (and the folders themselves I think) can just be deleted. No background files necessary!

@DHowett
Copy link
Member

DHowett commented Feb 25, 2021

Whoa, none? The background contents file still refers to one thing: macronbelowcomb.

@aaronbell
Copy link
Collaborator Author

The background files have no impact on the font output. They're just there as extra cruft from my development work. I should really just delete them all on conversion to UFO.

@DHowett
Copy link
Member

DHowett commented Feb 25, 2021

Mind doing that in a PR? I'm strapped into meetings almost all day ☹️

@aaronbell
Copy link
Collaborator Author

Oh... I merged the fix in :)

@DHowett
Copy link
Member

DHowett commented Feb 25, 2021

huh, it notified me that your PR was closed (without merging)

@aaronbell
Copy link
Collaborator Author

Oh yeah, I PR'd the wrong thing, so closed it. Ended up just merging in an update directly. :x

@aaronbell
Copy link
Collaborator Author

(d4fac8b)

@DHowett
Copy link
Member

DHowett commented Feb 25, 2021

☹️

2021-02-25T20:23:08.8372820Z ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2021-02-25T20:23:08.8418550Z sources/CascadiaCode-Bold.ufo
2021-02-25T20:23:08.8519700Z ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2021-02-25T20:23:08.8621680Z  
2021-02-25T20:23:08.8723270Z [UFO directory] ....... 
2021-02-25T20:23:08.8819450Z    Found UFO v3
2021-02-25T20:23:08.8841710Z    Detected glyphs directories: 
2021-02-25T20:23:08.8843730Z      -- glyphs . 
2021-02-25T20:23:08.8845470Z      -- glyphs.public.background F
2021-02-25T20:23:08.8846400Z 
2021-02-25T20:23:08.8847740Z =============================================================================
2021-02-25T20:23:08.8849980Z sources/CascadiaCode-Bold.ufo failed ufolint testing! Exit with status code 1
2021-02-25T20:23:08.8851490Z =============================================================================
2021-02-25T20:23:08.8952800Z  
2021-02-25T20:23:08.9017690Z Test result that led to failure:
2021-02-25T20:23:08.9119990Z [FAIL] Unable to find the UFO directory 'glyphs.public.background' defined in layercontents.plist
2021-02-25T20:23:08.9219570Z  

@aaronbell
Copy link
Collaborator Author

Well that serves me right.

@aaronbell
Copy link
Collaborator Author

OK. updated again. Double-checked that it builds. :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment