Fixed inconsistent return value when kerning value is not found 

On line #203 the returned value is checked against "undefined" to short out, yet the subtable function can return "null", which leads to incorrect value of "null" being returned too early in table.getKerningValue
Merge pull request #83 from nktpro/patch-1

Fixed inconsistent return value when kerning value is not found