WPIntell

Source evidence

Accessing Google Early Access Fonts

Google Web Fonts Customizer (GWFC) · support · 2014-08-08T08:28:00+00:00

complaintsentiment
mediumseverity
0.81relevance
0replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

6 / 31 rows with source links

19.4% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

25 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
keysuck unresolved
Hello. I have made a feature request regarding this issue but decided to pursue it myself by modifying the fonts.json. I followed the preexisting format to link Google Early Access Fonts by adding the following lines (based on the information found in CSS of the target font) starting at line 4: { "kind": "webfonts#webfont", "family": "Nanum Gothic", "variants": [ "400", "700", "800" ], "subsets": [ "latin", "korean" ], "version": "v4", "lastModified": "2014-01-07", "files": { "400": "http://themes.googleusercontent.com/static/fonts/earlyaccess/nanumgothic/v4/NanumGothic-Regular.eot", "700": "http://themes.googleusercontent.com/static/fonts/earlyaccess/nanumgothic/v4/NanumGothic-Bold.eot", "800": "http://themes.googleusercontent.com/static/fonts/earlyaccess/nanumgothic/v4/NanumGothic-ExtraBold.eot" } }, Now, this works flawlessly, showing the assigned font as the very first font on the drop list of the font customizer screen. However, when I tried to add the next font, just below the new custome font and above ABeeZee as follows, the font name is visible but cannot be applied: { "kind": "webfonts#webfont", "family": "Nanum Myeongjo", "variants": [ "400", "700", "800" ], "subsets": [ "latin" ], "version": "v3", "lastModified": "2014-01-07", "files": { "400": "http://themes.googleusercontent.com/static/fonts/earlyaccess/nanummyeongjo/v3/NanumMyeongjo-Regular.eot", "700": "http://themes.googleusercontent.com/static/fonts/earlyaccess/nanummyeongjo/v3/NanumMyeongjo-Bold.eot", "800": "http://themes.googleusercontent.com/static/fonts/earlyaccess/nanummyeongjo/v3/NanumMyeongjo-ExtraBold.eot" } }, I know I am not a programmer and I accidentally came across this in an attempt to apply Korean font not available in Google Fonts, but I don’t understand why the first one works while the successive one fails. Can you see the flaws? https://wordpress.org/plugins/google-web-fonts-customizer-gwfc/

Comments

0 shown

No comments were stored for this source.