Non ASCII characters

[andrey-bm52]

in j.jason and in q.json files.
In words "Jekyll and Hyde", "qabbālāh".
"Jekyll and Hyde": {
"word": "Jekyll and Hyde",
"wordset_id": "a4a55a6b0d",
"meanings": [
{
"id": "75b8309869",
"def": "a person who unpredictably displays two distinct and morally opposed personality traits",
"example": "The way they scream at me one minute and apologize the next�—it's like they're Jekyll and Hyde!",
"speech_part": "noun"
}
],

and

"qabbālāh": {
    "word": "qabbālāh",
    "wordset_id": "2805a6b224",
    "meanings": [
        {
            "id": "efb0ebd478",
            "def": "an esoteric or occult matter resembling the mystical Jewish teachings, based on esoteric writings, that is traditionally secret",
            "example": "Our human resources manual is a bit of a kabala.",
            "speech_part": "noun"
        }
    ],

[gardners]

There are a couple of others as well. Check the changes in my pull-request #3.

[HamptonMakes]

Hey people! We had no idea anyone was using this... 4 years ago @malrase and I spent a year of our life on this and never thought it'd get used... but someone is using it! WE ARE SO HAPPY!

Officially, the dictionary is encoded in UTF-8 and not ASCII. This is That being said, we likely should have ASCII representations of all of the words and definitions since in English that's typically enough. But, I agree that for now these types of very obscure characters in English can just be layered into their ASCII representation.