{"action":"opened","issue":{"url":"https://api.github.com/repos/OpenSourceFieldlinguistics/FieldDB/issues/1941","labels_url":"https://api.github.com/repos/OpenSourceFieldlinguistics/FieldDB/issues/1941/labels{/name}","comments_url":"https://api.github.com/repos/OpenSourceFieldlinguistics/FieldDB/issues/1941/comments","events_url":"https://api.github.com/repos/OpenSourceFieldlinguistics/FieldDB/issues/1941/events","html_url":"https://github.com/OpenSourceFieldlinguistics/FieldDB/issues/1941","id":66953078,"number":1941,"title":"UCB suggestion: think about how to deal with code-switching","user":{"login":"jrwdunham","id":2504271,"avatar_url":"https://avatars.githubusercontent.com/u/2504271?v=3","gravatar_id":"","url":"https://api.github.com/users/jrwdunham","html_url":"https://github.com/jrwdunham","followers_url":"https://api.github.com/users/jrwdunham/followers","following_url":"https://api.github.com/users/jrwdunham/following{/other_user}","gists_url":"https://api.github.com/users/jrwdunham/gists{/gist_id}","starred_url":"https://api.github.com/users/jrwdunham/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jrwdunham/subscriptions","organizations_url":"https://api.github.com/users/jrwdunham/orgs","repos_url":"https://api.github.com/users/jrwdunham/repos","events_url":"https://api.github.com/users/jrwdunham/events{/privacy}","received_events_url":"https://api.github.com/users/jrwdunham/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-04-07T17:57:52Z","updated_at":"2015-04-07T17:57:52Z","closed_at":null,"body":"The ability to deal with code-switching. For example, when a speaker uses a different language (or multiple different languages/dialects) within a string of object/target language utterance. We want to be able to find (or exclude) such code-switch-containing forms from our searches. We also want to not be obliged to enter lexical entries for each code-switching morpheme/word. Understanding exactly what users want in this type of situation will require more in-depth exploration of this issue."}}