About metric compatibility

[NightFurySL2001]

According to many sources, Caladea was introduced into Croscore fonts of Google Chrome OS as a substitute for Cambria, but the version provided here is not metrically compatible with current Cambria.

https://en.wikipedia.org/wiki/Croscore_fonts#Crosextra_fonts
https://wiki.archlinux.org/index.php/Metric-compatible_fonts

[bkmgit]

The file https://github.com/huertatipografica/Caladea/blob/master/sources/ufo/Caladea-Regular.ufo/fontinfo.plist has metrics that are the same as the fonts available at http://gsdview.appspot.com/chromeos-localmirror/distfiles/crosextrafonts-20130214.tar.gz :
Ascent: 778
Descent: -222
Em Size: 1000
Underline position: -89
Height: 57

but in https://fonts.google.com/download?family=Caladea and at https://github.com/huertatipografica/Caladea/tree/bea9e4996451fb18e0bdb5cbd177c8a263c0343d/fonts/ttf the metrics:
Ascent: 800
Descent: 200
Em Size: 1000
Underline position: -100
Height: 50

are used. A related issue is #3

Perhaps the fonts should be regenerated?

[CaroGiovagnoli]

@vv-monsalve

[bkmgit]

@CaroGiovagnoli @vv-monsalve Thanks.

[davelab6]

I reviewed this with @vv-monsalve and @NightFurySL2001 you are right, so I've ask Viviana to rebuild the project with the compatible metrics and update it in Google Fonts

[vv-monsalve]

The original vertical metrics of fonts at commit 095c699 v1.001 UFO sources were:

Metrics	Values
typoAscender	778
typoDescender	-222
typoLineGap	172
hheaAscender	950
hheaDescender	-222
hheaLineGap	0
winAscent	950
winDescent	222

@andrestelex, @CaroGiovagnoli, I'll restore the fonts to those values, taking them as the compatible metrics with the reference font. Please confirm these are the intended values.

[vv-monsalve]

@andrestelex, @CaroGiovagnoli

[fabiangreffrath]

@vv-monsalve Maybe provide a PR that upstream could just merge?

[ethanc8]

@vv-monsalve is the metrics-copy branch on your repo the most recent version with correct metrics?

[vv-monsalve]

@ethanc8 I initiated the metrics rollback job in that particular branch. However, due to the recent clarification on the font's expected compatibility with Cambria, changes must be made to both the vertical and horizontal metrics. Unfortunately, I haven't had the chance to address the horizontal metrics yet, so that task is still pending.

[ethanc8]

@ethanc8 I initiated the metrics rollback job in that particular branch. However, due to the recent clarification on the font's expected compatibility with Cambria, changes must be made to both the vertical and horizontal metrics. Unfortunately, I haven't had the chance to address the horizontal metrics yet, so that task is still pending.

Does this mean that the vertical metrics are correct but the horizontal metrics aren't correct in that branch?

[vv-monsalve]

After a quick inspection of the current source files, yes, these are the current rolled-back vertical metrics: