Noto Sans & Serif 2.0 & others: MS Code Pages not selected

[ghost]

Noto Sans & Serif 2.0 & others: MS Code Pages not selected

Thus not recognised by, and not properly showing in, Word 2016.

Issue

Font

NotoSans-Regular.ttf
NotoSans-Italic.ttf
NotoSans-Condensed.ttf
NotoSans-Medium.ttf
NotoSerif-Regular.ttf
etc. and many many others.

Where the font came from, and when

Site: https://noto-website-2.storage.googleapis.com/pkgs/Noto-hinted.zip
Date: 2017-11-29

Font Version

2.00

OS name and version

Windows 8 Pro

Application name and version

Office Word 2016, Version 1609 (Build 7369.2127)

[codeman38]

Duplicate of #316. This should probably be fixed up manually in post-production, if it can't be fixed in the tool chain, now that the alpha fonts have been promoted to the main repo.

[anthrotype]

The toolchain already supports compiling the codepage bits if they are specified in the glyphs or ufo source using the respective fields. For Noto sources which uses Glyphs.app, the codePageRanges custom parameter should be set accordingly. UFO has the equivalent openTypeOS2CodePageRanges in fontinfo.plist

[nizarsq]

@librarhyme could you check if this issue still reproducible in the latest build in these directories:
https://github.com/googlefonts/noto-fonts/tree/master/phaseIII_only/hinted/ttf/NotoSansMono
https://github.com/googlefonts/noto-fonts/tree/master/phaseIII_only/hinted/ttf/NotoSans
https://github.com/googlefonts/noto-fonts/tree/master/phaseIII_only/hinted/ttf/NotoSerif

[moyogo]

Duplicate of #316.

The code page ranges were fixed in Noto Sans 2.001 (4b9da60ee), Noto Sans Mono 2.002 (4b9da60ee), Noto Serif 2.001 (449470a4d) when the fonts were build with fontmake after googlefonts/fontmake#304 was merged.