{"action":"closed","issue":{"url":"https://api.github.com/repos/spencermountain/nlp_compromise/issues/47","labels_url":"https://api.github.com/repos/spencermountain/nlp_compromise/issues/47/labels{/name}","comments_url":"https://api.github.com/repos/spencermountain/nlp_compromise/issues/47/comments","events_url":"https://api.github.com/repos/spencermountain/nlp_compromise/issues/47/events","html_url":"https://github.com/spencermountain/nlp_compromise/issues/47","id":84474805,"number":47,"title":"Circa, or c.","user":{"login":"franciscop","id":2801252,"avatar_url":"https://avatars.githubusercontent.com/u/2801252?v=3","gravatar_id":"","url":"https://api.github.com/users/franciscop","html_url":"https://github.com/franciscop","followers_url":"https://api.github.com/users/franciscop/followers","following_url":"https://api.github.com/users/franciscop/following{/other_user}","gists_url":"https://api.github.com/users/franciscop/gists{/gist_id}","starred_url":"https://api.github.com/users/franciscop/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/franciscop/subscriptions","organizations_url":"https://api.github.com/users/franciscop/orgs","repos_url":"https://api.github.com/users/franciscop/repos","events_url":"https://api.github.com/users/franciscop/events{/privacy}","received_events_url":"https://api.github.com/users/franciscop/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":7,"created_at":"2015-06-03T10:04:05Z","updated_at":"2015-07-26T19:54:38Z","closed_at":"2015-07-26T19:54:38Z","body":"Is it possible to add an exception for the following regex?\r\n\r\n    /c\\.(\\ ?[0-9]+)/\r\n\r\nRight now I'm using a small script to pre-process the text that I want to analyze with nlp_compromise. The current solution that I am using looks like this:\r\n\r\n    raw = raw.replace(/c\\.(\\ ?[0-9]+)/g, 'circa $1');\r\n\r\nBasically, any `c. YEAR` will be replaced by `circa YEAR` so nlp doesn't mess up with that `c.`. While only `c.` might not be good enough to be added to [abbreviations](https://github.com/spencermountain/nlp_compromise/blob/master/src/data/lexicon/abbreviations.js) since it's not significant enough, this expression matches `c. NUMBER`, which I think it's unambiguous enough. What do you think? Is there a way to add this or other similar, case-specific abbreviations?\r\n\r\n(I am not proposing to change c. for circa, this is just my solution, I am proposing to add, if possible, an exception for `c. YEAR` and not break sentences in that period)."}}