Couldn't they also only serve up the fix to affected chrome browsers by checking the user agent string in the request header? That way they give the most effective format based on the browser and os requesting it.
That's what I meant. The Google Fonts CSS is already based on the user agent string (it doesn't contain media-queries or similar tricks), so they just need to treat Chrome+Win differently and tell it to load the SVG version.
