Created attachment 442 [details]
Screen shot of corrupted font

Created attachment 443 [details]
Graphics font

Created attachment 444 [details]
Tagged MP3

Have solved this via a workaround. However, need to find a long-term solution.
Bidirectional display is solved by a Bidi CPAN module.
Display of appropriate ASCII font from the font bmp is changed by making the 
following change in Slim::Display::string
From:
if ($ord > 255) {
    $ord = 63;
}
to 
if ($ord > 255) {
   }  if ($ord >=1488 && $ord <= 1514) {
          $ord = $ord -1264;
   } else {
    $ord = 63;
}
However, this workaround is specific for Hebrew characters 1488-1514 range and 
the appropriate 224-250 ASCII range.
As each of the international chars will be mapped to the same ASCII range, we 
need to be able to identify what the offset is. Perhaps a configuraiton file, 
or imbedd the offset in the specific font file?

With the new Unicode fonts, is this still an issue?

Nope - this is fixed.