LLTI Archives

October 2001, Week 4

LLTI@LISTSERV.DARTMOUTH.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
LLTI-Editor <[log in to unmask]>
Reply To:
Language Learning and Technology International Information Forum <[log in to unmask]>
Date:
Tue, 23 Oct 2001 17:06:50 EDT
Content-Type:
text/plain
Parts/Attachments:
text/plain (86 lines)
--- Forwarded Message from Derek Roff <[log in to unmask]> ---

>Date: Mon, 22 Oct 2001 12:36:57 -0600
>From: Derek Roff <[log in to unmask]>
>To: [log in to unmask], LLTI-Editor <[log in to unmask]>
>Subject: Re: #67345 Hebrew font question

I've worked alot with fonts and keyboards on the Mac, but not much
with Language Kits.  Perhaps my speculations on the latter may be of
some use.

I don't think this is a simple font problem.  For single byte fonts,
a font relates a specific graphic to a character code number, and
nothing more.   If you enter a character code number in a document,
you will see the associated character for the chosen font.  The
problem is linking the more than 200 characters in a font to our
101-key keyboards.  Keyboard files  (sometimes working with a
language script) define the relationship between the keys that we
press on the keyboard, and the character code that is placed in the
document.

It sounds like this is where the problem lies.  I think you have a
version of the Hebrew keyboard file that is not fully compatible with
this version of your Hebrew fonts.  The keyboard file is translating
option+0 into a character code number, which doesn't match the
desired character in the font.  When you get little squares in your
text, it usually means that the chosen font doesn't have a special
graphic for that code number.  Fonts and keyboards have been evolving
rapidly under OS 9, as Apple moves toward Unicode and OS X.
Therefore, all the pieces have to be right, for things to work.  It
may be that this computer has a Hebrew font from 9.0 and a keyboard
file from 9.1.  Or it may be that Apple didn't get all the bugs out
of that iteration of the Hebrew Language Kit.

The are programs that will show you all the characters in a font, and
their keyboard equivalents.  I use Key Finder, which I bought years
ago.  VersionTracker.com doesn't list Key Finder, but it does show a
program called  Font Finder 1.2.1, which is a $10 shareware program,
listing similar properties.  Fontographer is another program which
will allow you to see every character in a font, and how to type it.
One of these programs will let you verify that all the needed
characters exist in Arial Hebrew and Cordova Hebrew.  I bet that they
do.

If this is the case, then you can type the needed characters, using
the key combinations that Font Finder will reveal.  That may be a
satisfactory solution for limited use.  However, the key combinations
may be chaotic and illogical for anyone used to a Hebrew typing
system, such as an older version of the Hebrew Language Kit.  Given
that the fonts are complete, I would try reinstalling the Language
Kit, making sure that all the parts and OS numbers match.  If things
still don't work properly, then Apple should be aware of this
problem.  If they can't direct you to a solution, it is possible to
modify keyboard files, using ResEdit, which is a freeware resource
editing program created by Apple (available through
VersionTracker.com).

For someone familiar with ResEdit, it is fairly easy to modify a
keyboard file, and get whatever key combinations you want for
specific characters.  If you have never worked with ResEdit, it has a
significant learning curve.  I hope someone using the Hebrew Language
Kit will be able to offer a simpler solution.

Derek Roff

>> From: [log in to unmask]
>> Date: Fri, 19 Oct 2001 20:03:23 -0400

> I am trying to solve a problem with the Hebrew Language Kit that
> comes with Mac OS 9.x.  It comes with 2 fonts, mainly Arial Hebrew
> and Cordova Hebrew.  Both are nice fonts however they do not display
> characters properly when "accented".  In each font, it is a
> different subset that does not display.
>
> For example, with Cordova Hebrew, typing "u" then option+0 produces
> a nice box, while any other letter then option+0 produces the
> correct output.
>
> Is there a (set of) font(s) suitable for word processing that are
> known to render all characters correctly?

Derek Roff
Language Learning Center, Ortega Hall Rm 129, University of New Mexico
Albuquerque, NM 87131  505/277-7368 fax 505/277-3885
Internet: [log in to unmask]

ATOM RSS1 RSS2