Document how to access all of Voces

[stefanocoretta]

The characters from the latin-ext subset of Voces are not rendered as Voces font on Safari nor Chrome on iOS 10.2 nor 9.3.5. The default typeface is displayed instead. The subset latin-ext works fine on Safari and Chrome on MacOS Sierra.

You can see an example here (jsbin backup)

This is what I see on MacOS Safari, which is correct.

[jungshik]

The example page does not work either on Chrome on Linux.

Chrome's DOM inspector has the following.

LocalFontFoo—Local file(4 glyphs)
Voces—Network resource(2 glyphs)
LocalFontBar—Local file(1 glyph)

Note that only 2 glyphs out of 7 come from Voces.
It looks like Voces covers only two characters in the sample text above.

[laerm0]

Entering the demo text into the specimen page works fine; same goes for testing the font in-browser on impallari.com. The test page @jungshik provides does not work, nor does a jsbin of the font. So something about how the file is delivered via GFonts is off. I wasn't able to get a better result by specifying unicode-range, either.

Thoughts from @rsheeter, maybe?

[davelab6]

Basically the latin-ext subset doesn't include all the IPA characters, even though they are in the font, you can't access them that way. Eg

https://jsbin.com/vosekod/edit?html,output

However, the text subset API feature will enable you to get served fonts with those characters, if they are in the font:

https://jsbin.com/feberir/edit?html,output

latin-ext doesn't have everything, from languages (#1215) to the lowly trademark (#78)

The resolution to this issue will be to update that glyph set definition :) I'm tracking that separately in #135

GF could also do a better job of explaining this in documentation somewhere.

[stefanocoretta]

Thanks for the clarification and sorry for the very delayed reply. Shall I close the issue or leave it open? (I reckon you changed the title so you might want to close it yourself or not).

[davelab6]

Yeah I'll keep this open until we provide documentation on this properly