Inconsistent naming between Google Fonts and Noto website

[engelfrost]

The subset that Google Fonts calls Noto Sans JP is not the same sunset that the Noto website calls Noto Sans JP. See garris/BackstopJS#981 (comment)

[davelab6]

Do you have any solution proposals? :)

[engelfrost]

The best solution would of course be if the names were consistent across Google Fonts and the Noto documentation. But I guess it's a little late to change the name of Noto Sans JP on Google Fonts since it's already published, so I guess there is no perfect solution.

At least mentioning that the Google Font names are not consistent with the Noto documentation would be helpful.

An appropriate place to mention is would be under the bullet point "For use in web content" on https://www.google.com/get/noto/help/guidelines/, since this already references Google Fonts.

Another second place could be the examples section, it seems to me that you'll actually want to use the name "Noto Sans JP" when loading Noto Sans CJK JP from Google Fonts.

Another solution would be to change to example to a font that does not have the same naming inconsistencies, and add a separate section about Noto Sans CJK JP and any other fonts that might be differently named on Google Fonts.