{"action":"created","issue":{"url":"https://api.github.com/repos/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/14","repository_url":"https://api.github.com/repos/kshawkin/Best-Practices-for-TEI-in-Libraries","labels_url":"https://api.github.com/repos/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/14/labels{/name}","comments_url":"https://api.github.com/repos/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/14/comments","events_url":"https://api.github.com/repos/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/14/events","html_url":"https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/14","id":103980124,"number":14,"title":"how to record non-ASCII characters","user":{"login":"kshawkin","id":538464,"avatar_url":"https://avatars.githubusercontent.com/u/538464?v=3","gravatar_id":"","url":"https://api.github.com/users/kshawkin","html_url":"https://github.com/kshawkin","followers_url":"https://api.github.com/users/kshawkin/followers","following_url":"https://api.github.com/users/kshawkin/following{/other_user}","gists_url":"https://api.github.com/users/kshawkin/gists{/gist_id}","starred_url":"https://api.github.com/users/kshawkin/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/kshawkin/subscriptions","organizations_url":"https://api.github.com/users/kshawkin/orgs","repos_url":"https://api.github.com/users/kshawkin/repos","events_url":"https://api.github.com/users/kshawkin/events{/privacy}","received_events_url":"https://api.github.com/users/kshawkin/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2015-08-31T03:49:25Z","updated_at":"2016-06-11T15:22:08Z","closed_at":null,"body":"People often want to know what to do with non-ASCII characters. There are generally four options:\r\n* insert them as they are (and assume the files will be manipulated by Unicode-aware software and that people can distinguish these from similar characters)\r\n* insert decimal entity references\r\n* insert hexadecimal entity references\r\n* insert mneumonic entity references (which need to be declared)\r\n\r\nWe should give advice on this."},"comment":{"url":"https://api.github.com/repos/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/comments/225369520","html_url":"https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/14#issuecomment-225369520","issue_url":"https://api.github.com/repos/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/14","id":225369520,"user":{"login":"kshawkin","id":538464,"avatar_url":"https://avatars.githubusercontent.com/u/538464?v=3","gravatar_id":"","url":"https://api.github.com/users/kshawkin","html_url":"https://github.com/kshawkin","followers_url":"https://api.github.com/users/kshawkin/followers","following_url":"https://api.github.com/users/kshawkin/following{/other_user}","gists_url":"https://api.github.com/users/kshawkin/gists{/gist_id}","starred_url":"https://api.github.com/users/kshawkin/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/kshawkin/subscriptions","organizations_url":"https://api.github.com/users/kshawkin/orgs","repos_url":"https://api.github.com/users/kshawkin/repos","events_url":"https://api.github.com/users/kshawkin/events{/privacy}","received_events_url":"https://api.github.com/users/kshawkin/received_events","type":"User","site_admin":false},"created_at":"2016-06-11T15:22:08Z","updated_at":"2016-06-11T15:22:08Z","body":"Right, it might good to give different recommendations for (a) glyphs that are available as precomposed Unicode characters, (b) glyphs that can only be constructed using combining characters, and (c) glyphs not in Unicode.  For the last one, it's true that I left `<g>` off the list.  Though I wasn't explicit about it when creating the issue, I was only talking about characters that are in Unicode—that is, (a) and (b).  The BPTL doesn't address the need to encode non-Unicode characters, though perhaps it should.\r\n\r\nThe BPTL, like P5, avoids recommendations that are software dependent, but we sometimes do it when the recommendation seems applicable to many programs and to broader digital library architectures (like what we say about always putting `<pb>`s and other milestone elements inside text divisions).  While it has long seemed that editing tools would soon improve their display of combining characters, maybe that won't really happen anytime soon, and therefore we should include the recommendation to use NCRs for combining characters.\r\n\r\nI believe that XML software is required by the XML specification to handle NCRs, though people may end up editing files with software that doesn't implement the specification.  Aside the predefined mnemonic entity references (`&quot;`, `&lt;`, etc.), all other mnemonic entity references these have to be defined properly to be used, and I think you're right that they are more likely to not be processed properly.  While we don't currently discuss these in the BPTL, we could be explicit in recommending against their use."}}
{"actor":{"display_login":"kshawkin"}}