{"action":"created","issue":{"url":"https://api.github.com/repos/TypeNetwork/Amstelvar/issues/74","repository_url":"https://api.github.com/repos/TypeNetwork/Amstelvar","labels_url":"https://api.github.com/repos/TypeNetwork/Amstelvar/issues/74/labels{/name}","comments_url":"https://api.github.com/repos/TypeNetwork/Amstelvar/issues/74/comments","events_url":"https://api.github.com/repos/TypeNetwork/Amstelvar/issues/74/events","html_url":"https://github.com/TypeNetwork/Amstelvar/issues/74","id":318890486,"node_id":"MDU6SXNzdWUzMTg4OTA0ODY=","number":74,"title":"Glyph Sharing vs file size","user":{"login":"dberlow","id":1956494,"node_id":"MDQ6VXNlcjE5NTY0OTQ=","avatar_url":"https://avatars2.githubusercontent.com/u/1956494?v=4","gravatar_id":"","url":"https://api.github.com/users/dberlow","html_url":"https://github.com/dberlow","followers_url":"https://api.github.com/users/dberlow/followers","following_url":"https://api.github.com/users/dberlow/following{/other_user}","gists_url":"https://api.github.com/users/dberlow/gists{/gist_id}","starred_url":"https://api.github.com/users/dberlow/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dberlow/subscriptions","organizations_url":"https://api.github.com/users/dberlow/orgs","repos_url":"https://api.github.com/users/dberlow/repos","events_url":"https://api.github.com/users/dberlow/events{/privacy}","received_events_url":"https://api.github.com/users/dberlow/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":6,"created_at":"2018-04-30T13:30:37Z","updated_at":"2018-06-01T20:18:11Z","closed_at":null,"author_association":"COLLABORATOR","body":"Glyph Sharing vs Glyph Expansion\r\n\r\nExecutive Summary:\r\n\r\nThis is a questing essay about two classes of sharing in the defininition of the Amstelvar glyphs repertoire. \r\n\r\nThe first class of sharing are glyphs that currently need to be defined, even though they share contour congruency with an existing glyph in the design space, like uppercase A and Small Cap A, or uppercase Won and Small Cap Won. \r\n\r\nThe second class of sharing are glyphs within the repertoire that are expected to be shared by different glyph groups, like A+B=C, a+b=c and 1+2=3, where the + and = are used with both cases and figures. \r\n\r\nfirst issue: When Amstemvar has small caps defined, all the glyphs highlighted in red and yellow below will also need to have small cap glyphs defined, along with A-Z and 0-9. So, as things stand now all of those glyphs will be instantiated as seperate contours with their own gvars, hints and kerning. \r\n\r\nsee \"Amstelvar Glyphork?\"\r\n<img width=\"1081\" alt=\"amstelvar glyphork\" src=\"https://user-images.githubusercontent.com/1956494/39429442-eb6a15ec-4c58-11e8-834f-41e1b20c2032.png\">\r\n\r\nContour congruency, however, exists within the design space already, where those small cap A and Won contours, are already there with gvars, hinting and kerning, elsewhere in the design space. \r\n\r\nsee Amstelvar EI Small caps\r\n<img width=\"1142\" alt=\"amstelvar ei small caps\" src=\"https://user-images.githubusercontent.com/1956494/39429502-0cdd6170-4c59-11e8-99de-dfd22a375c30.png\">\r\n\r\nsecond issue:, Glyph sharing between cases is a more entrenched and insidious issue. \r\n<img width=\"362\" alt=\"plus puss\" src=\"https://user-images.githubusercontent.com/1956494/39429516-14afe8c8-4c59-11e8-9c02-9d157b61d668.png\">\r\n\r\nThe gist of these sharing issues, and I've spoke with Dave about it with regards to the accents over, under and stacked with upper small caps and lowercase, is that, (because we cannot reference (composites?) from the glyphs of the whole design space, (that are outside of the current instance), we are going to have to produce multiple versions of all the glyphs above, one math glyph e.g. for each y-transparency axis. In some instances these glyphs can be compostited from a master-per-instance to a different alignment. In other cases that’s not possible and a different glyph will be gsubbed. The bottom line is that adding all there required contours, composited, gsub, gvar, hinting, kerning and probably more, will have the effect of doubling the size of this variable font. \r\n"},"comment":{"url":"https://api.github.com/repos/TypeNetwork/Amstelvar/issues/comments/393997723","html_url":"https://github.com/TypeNetwork/Amstelvar/issues/74#issuecomment-393997723","issue_url":"https://api.github.com/repos/TypeNetwork/Amstelvar/issues/74","id":393997723,"node_id":"MDEyOklzc3VlQ29tbWVudDM5Mzk5NzcyMw==","user":{"login":"davelab6","id":261579,"node_id":"MDQ6VXNlcjI2MTU3OQ==","avatar_url":"https://avatars0.githubusercontent.com/u/261579?v=4","gravatar_id":"","url":"https://api.github.com/users/davelab6","html_url":"https://github.com/davelab6","followers_url":"https://api.github.com/users/davelab6/followers","following_url":"https://api.github.com/users/davelab6/following{/other_user}","gists_url":"https://api.github.com/users/davelab6/gists{/gist_id}","starred_url":"https://api.github.com/users/davelab6/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/davelab6/subscriptions","organizations_url":"https://api.github.com/users/davelab6/orgs","repos_url":"https://api.github.com/users/davelab6/repos","events_url":"https://api.github.com/users/davelab6/events{/privacy}","received_events_url":"https://api.github.com/users/davelab6/received_events","type":"User","site_admin":false},"created_at":"2018-06-01T20:18:11Z","updated_at":"2018-06-01T20:18:11Z","author_association":"COLLABORATOR","body":"Sounds good to me!\n"}}
{"actor":{"display_login":"davelab6"}}