Aharon Schkolnik wrote:
> gbiff (http://gbiff.sourceforge.net/) claims to support "any ISO-8859
> encoding".
>
> I am using it with a pop-3 account on our Exchange server here at
> work.
>
> I have chosen the font:
>
> -DEC-David-Medium-R-Normal--24-240-75-75-P-124-ISO8859-8
>
> However, the headers displayed by gbiff still look like:
>
> =?WINDOWS-1255?Q?=E0=E4=F8
>
> Does anyone know why this is, and if there is anything I can do about
> it ?
I have no specific experience with gbiff, so a full solution may be
provided from one of gbiff users.
However, I can explain you what happened:
The header you quoted, is encoded in a BASE64 MIME format.
If it is not decoded, it means that the application you use (gbiff in
this specific case) doesn't know how to decode BASE64. Or that it is
not configured to do it.
Fonts have nothing to do with it.
The only connection of fonts to this issue, is that AFTER the text was
decoded, without Hebrew font it may be displayed as "Chinese" (a.k.a.
"Gibberish").
Look at the font that you mentioned (using "xfd"), and compare to the
glyphs that are used with the header you mentioned
("=?WINDOWS-1255?Q?=E0=E4=F8"); If the glyphs are the same, it means
that the font worked perfectly.
--
Eli Marmor
[EMAIL PROTECTED]
CTO, Founder
Netmask (El-Mar) Internet Technologies Ltd.
__________________________________________________________
Tel.: +972-9-766-1020 8 Yad-Harutzim St.
Fax.: +972-9-766-1314 P.O.B. 7004
Mobile: +972-50-23-7338 Kfar-Saba 44641, Israel
=================================================================
To unsubscribe, send mail to [EMAIL PROTECTED] with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]
