added all 915 google fonts available from their API

[MI53RE]

Added all the width maps for google font (915 at that time)

This has been realized through Firefox, on windows 10

Did it on Chrome but results were different and using existing mapped font as reference width were off by -10px for andale mono

Did make sure existing font will stay untouched

Enjoy =) !!

[adambisek]

Why do you need all those fonts?

[MI53RE]

I am currently working on a pdf parser that need to detect exact position of specific flags in it so I can later add data in that same position.

Due to the varieties of software able to generate pdf, and their implementation, we have, neither us or our client, no control over the font nor the structure that can be used to produce the documents so if more fonts are covered the better.

Why ? because in some (quite frequent) case the position of those flags are not reacheable directly and in those cases, I need to calculate the position based on the text width that take precedence of those flags, hence your tools is doing an awesome job to complete this task.

[coveralls]

Coverage remained the same at 100.0% when pulling fe9acde on MI53RE:feature-google-font into 8bf5e90 on adambisek:master.

[iliakan]

Why is this not merged? Any reason not to want more fonts? :)

[iliakan]

Maybe it should be made more modular? To load only needed fonts, so that there's no extra parsing and loading from JS side.

[MI53RE]

Maybe it should be made more modular? To load only needed fonts, so that there's no extra parsing and loading from JS side.

At which level do you think the modularity should be applied ? :) That's actually quite an interesting suggestion (maybe a conf file allowing to select the needed font only when importing the library in project )?

[iliakan]

Per-font modularity seems legit.

[DharanBro]

Can we have an API exposed? so that consumers will pass the JSON(font size config) and the library shall make use of it. maybe like. .useFont(fontConfig)

[Evgenus]

@MI53RE 523,724 lines added? now big is the package after this? I see that a joke about black hole is lighter than node_modules is not a joke at all.

[kamronbatman]

There should be a script that generates this instead on a per font used basis. That could take the form of a rollup/webpack plugin or similar. Nobody needs/uses all 915 fonts. And I am not convinced this file can be treeshaken either.

[MI53RE]

@Evgenus true now as I see it after all this time I agree this was quite big ^^'
@kamronbatman in the "niche" market my company was at that time, it was actually necessary to cover as many font type as possible, and this PR is more specific to such projects indeed. Now the data in this PR might still be usefull to someone if sampled (save the time to do the job on his/her side) but then again might overload the size of the whole module if accepted. A treebased or API based aproache to get only the needed font would be more welcome indeed