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

Fencing doesn’t behave consistently #51

Open
sannorozco opened this issue Jun 21, 2024 · 3 comments
Open

Fencing doesn’t behave consistently #51

sannorozco opened this issue Jun 21, 2024 · 3 comments
Assignees

Comments

@sannorozco
Copy link
Collaborator

sannorozco commented Jun 21, 2024

Hallo,

I found an issue that’s preventing me to fence the extremes on this project. Fencing doesn’t behave consistently.

As we did it back in February, for each fence we need to add two sets of mappings for them to work, one pin and one with the value we want to fence an axis. They work like this for opsz 14 and opsz8.

But for opsz144 this does not work even though the geometry looks good in the Fencer app.

In this example, 144 100 1000, the YOPQ value of this is 228, so I try to fence it to 230 with this mapping, but it goes beyond, both in Fontra and the compiled ttf.

What is strange is that this structure worked good for all previous fences on the designspace. @Lorp Do you have any idea of what’s needed to fence this one?

Also, I tried saving the font from the fencer app and it does not generate the full designspace of the font, blended axis doesn’t work and neither the axis, it just moves weird on the current axis combination you had selected while slicking on the “Save font” button.

Any help will be apprecieted, thanks!

Screenshot 2024-06-21 at 14 00 46 Screenshot 2024-06-21 at 14 47 24 Screenshot 2024-06-21 at 14 57 21
@davelab6
Copy link
Member

davelab6 commented Jul 8, 2024

I'm just getting back from 2 weeks vacation and seeing this now, I set up time to chat with @Lorp tomorrow 1:1 and see what we can figure out :)

@Lorp
Copy link
Collaborator

Lorp commented Jul 8, 2024

Apologies for neglecting this. Hopefully we can get it sorted tomorrow.

@sannorozco
Copy link
Collaborator Author

Hallo @Lorp!

Here is the sequence to replicate this issue, inside the .zip are the XMLs, with the mappings separated by opsz.

  1. Start with this designspace, that has no fencing mappings.
  2. Add mappings fences-opsz14.xml.
  3. Add mappings fences-opsz8.xml.
  4. Add mappings fences-opsz144.xml.
  5. Add mappings fences-opsz144-wdth100-wght100-YOPQmax.xml. ERROR.
  6. Now, when trying to fence YOPQmax for 144 100 1000, it goes beyond and back, this last fence doesn’t work. At this location, the YOPQmax blended value is 228, so I’m trying to fend it to 230 so the tiny contours doesn't disappear overlapping.

Fencer Issues

  • When I load the latest VF into fencer, then download font from it, it breaks opsz, weight, width, & slnt that were working on the font that I dropped.
  • Also, after adding all the mappings, when I download it again with all added mappings it breaks all parametric axis.
  • The resulting VF from Fencer is different from fontmaker & Fontra.

Let me know if you have any questions,

Thanks!

fencer-with-all-mappings-added

fencer-issue.zip

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