Monda: Version 2.200 added

[emmamarichal]

Taken from the upstream repo https://github.com/googlefonts/mondaFont at commit googlefonts/mondaFont@13ca3d8.

PR Checklist:

• Family categorization tags collected from the type design team with the Categories Form
• Minisite_url definition in the METADATA.pb file for commissioned projects
• Primary_script definition in the METADATA.pb file for all projects that have a primary non-Latin based language support target
• Fontbakery checks are reviewed and failing checks are resolved in collaboration with the upstream font development team
• Diffenator2 regression checks for revisions on all projects that are currently in production
• Designers bio info have to be present in the designer catalog (at least an issue should be opened for tracking this, if they are not)
• Check designers order in metadata.pb, since the first one of the list appears as “principal designer”
• Social media formatted visual assets for all new commissioned projects in the Drive directory, communicate with the repository Maintainer so that they can push this content to the Social Media tracker spreadsheet
• Social media content draft for all new commissioned projects in the Drive directory and Social Media tracker spreadsheet, communicate with the repository Maintainer so that they can push this content to the Social Media tracker spreadsheet

[vv-monsalve]

@emmamarichal It seems the is a conflict between the static and VF fonts. See build

[emmamarichal]

@vv-monsalve I have the feeling it's a conflict with the old versions, since it's a VF replacement. Maybe it's something related to the new packager? But I see it packages the right file though.
I don't have any issues locally, here you can find the QA I exported. We can talk about this in the next pipeline meeting if Simon is here!

Monda_QA.zip

[vv-monsalve]

I have the feeling it's a conflict with the old versions, since it's a VF replacement. Maybe it's something related to the new packager?

From our last tool meeting I think so. Perhaps given you updated the path to the VF on the metadata file before running it (AFAIR).

But I see it packages the right file though.

I re-download the qa from the CI run and this is what happens with it

As discussed on the meeting today, we better wait to review the reported error from the CI build with Marc next week.

Alternatively you could try to update the PR from packager (e.g. from a release with clean new paths to fonts)

[emmamarichal]

Ah, I maybe have a more precise idea. This was a case a bit special, since it's a VF replacement. I edited the metadata.pb that already exists, to change the path to /variable/monda[wght] instead of /ttf/monda-regular.ttf etc.

But I forgot to change the fonts infos in metadata. There are still on bold and regular.
Even if the metadata.pb has been solve by the packager, maybe the conflict is here. I'll try to solve it today.

[emmamarichal]

@vv-monsalve, I can't unblock the PR because of the "changes requested" :/

I worked on the request and it's solved now