{"action":"created","issue":{"url":"https://api.github.com/repos/adobe-type-tools/afdko/issues/95","labels_url":"https://api.github.com/repos/adobe-type-tools/afdko/issues/95/labels{/name}","comments_url":"https://api.github.com/repos/adobe-type-tools/afdko/issues/95/comments","events_url":"https://api.github.com/repos/adobe-type-tools/afdko/issues/95/events","html_url":"https://github.com/adobe-type-tools/afdko/issues/95","id":125431624,"number":95,"title":"[spec] Allow both LigatureCaretByPos and LigatureCaretByIndex on the same glyph?","user":{"login":"brawer","id":1527880,"avatar_url":"https://avatars.githubusercontent.com/u/1527880?v=3","gravatar_id":"","url":"https://api.github.com/users/brawer","html_url":"https://github.com/brawer","followers_url":"https://api.github.com/users/brawer/followers","following_url":"https://api.github.com/users/brawer/following{/other_user}","gists_url":"https://api.github.com/users/brawer/gists{/gist_id}","starred_url":"https://api.github.com/users/brawer/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/brawer/subscriptions","organizations_url":"https://api.github.com/users/brawer/orgs","repos_url":"https://api.github.com/users/brawer/repos","events_url":"https://api.github.com/users/brawer/events{/privacy}","received_events_url":"https://api.github.com/users/brawer/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":6,"created_at":"2016-01-07T16:42:17Z","updated_at":"2016-01-08T00:14:38Z","closed_at":null,"body":"Currently, [section 9.b](http://www.adobe.com/devnet/opentype/afdko/topic_feature_file_syntax.html#9.b) of the OpenType Feature File specification does not make it clear whether the same glyph can have both LigatureCaretByPos and LigatureCaretByIndex statements. Should this be allowed? Might be good to clarify the spec.\r\n\r\nExample:\r\n```\r\ntable GDEF {\r\n     LigatureCaretByPos [c_t c_s]  500;\r\n     LigatureCaretByIndex c_t 5;\r\n} GDEF;\r\n```\r\n"},"comment":{"url":"https://api.github.com/repos/adobe-type-tools/afdko/issues/comments/169847165","html_url":"https://github.com/adobe-type-tools/afdko/issues/95#issuecomment-169847165","issue_url":"https://api.github.com/repos/adobe-type-tools/afdko/issues/95","id":169847165,"user":{"login":"behdad","id":142891,"avatar_url":"https://avatars.githubusercontent.com/u/142891?v=3","gravatar_id":"","url":"https://api.github.com/users/behdad","html_url":"https://github.com/behdad","followers_url":"https://api.github.com/users/behdad/followers","following_url":"https://api.github.com/users/behdad/following{/other_user}","gists_url":"https://api.github.com/users/behdad/gists{/gist_id}","starred_url":"https://api.github.com/users/behdad/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/behdad/subscriptions","organizations_url":"https://api.github.com/users/behdad/orgs","repos_url":"https://api.github.com/users/behdad/repos","events_url":"https://api.github.com/users/behdad/events{/privacy}","received_events_url":"https://api.github.com/users/behdad/received_events","type":"User","site_admin":false},"created_at":"2016-01-08T00:14:38Z","updated_at":"2016-01-08T00:14:38Z","body":"I suggest disallowing multiple declarations for the same glyph.  Warn and only accept the last one, or first one.\r\n\r\n> Since the order can change at runtime anyway (because hinting affects caret values in format 2), there probably is not much point in mandating any particular sorting order.\r\n\r\nSorting order *is* important.  That's what specifies which ligature component a particular point reflects."}}