Comment 23 for bug 14709

Message-id: <email address hidden>
Date: Mon, 25 Apr 2005 10:43:42 +0300 (EEST)
From: Harri Kiiskinen <email address hidden>
To: <email address hidden>, <email address hidden>
Cc: <email address hidden>, Debian BTS <email address hidden>,
 Harri Kiiskinen <email address hidden>
Subject: Re: Bug#302160: openoffice.org: crashes when trying to read a
 non-ascii character from afm file

Hello,

and sorry for not answering the last mail; I simply forgot it.

On Sat, 23 Apr 2005 <email address hidden> wrote:

> Thank for you tracking the issue about the openoffice crash in:
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=302160
>
> Other users have encountered the same crash and broken or corrupted fonts
> are not so rare.
>
> Could you give more information about the font so that the font
> librairy maintainer can check why it is not ignored (and send to
> the application leading to a crash).
>
> Was it a font corrupted in some random way by a disk problem ?

I cannot provide you with the details about the font nor the afm-file
any more, because when I fixed the corrupted afm-file, the problem went
away, and at the time of the last mail, I didn't remember any more which
font it actually was.

However, the details are almost clear in my mind: there were two 8-bit
characters in the corrupted afm-file: in the first case, a character
with the decimal code >230 had replaced (in emacs it looked like \238)
the return-char at the end of the line; in the second case, a character
in the name of a glyph in kerning tables had been replaced by a
charcter with the decimal code >230.

The cause was most probably a disk corruption, probably as a result of
running out of batteries on my laptop.

Greetings,

Harri Kiiskinen