Hey folks,

My project uses a custom font glyph file for displaying Hebrew text. The
glyphs are for old 160x160 devices.
On 320x320 devices it looks also fine, since it's just doubled.

We're now starting to use StyleTap (great product BTW, not that I'm
affiliated) to be able to sell our product for Windows Mobile devices.
However the displays are different, and now I need to be able to use
one-and-a-half and triple density, otherwise the display becomes distorted.

I did some research and found out that I need to use PILRC's FONTFAMILY
statement in my RCP file, as such:

FONTFAMILY ID FontShShNorm FONTID 128 LOCALE "heIL"
BEGIN
    FONT "sh_std.pfn" DENSITY 72
    FONT "heb_HD.pfn" DENSITY 108
END

72 is for single density and 108 is for one-and-a-half.
But how am I supposed to write the glyphs? My existing project uses glyphs
with 11 as its height, as such:

------
------
------
-##---
---#--
---#--
---#--
---#--
-####-
------
------

This is the second letter in the Hebrew alphabet.
So, if 11 rows is needed for single density, how many rows do I need for
one-and-a-half density? 16.5 is the mathematically correct answer, but it's
impossible to hold 16.5 rows. I tried using 16 rows but then PILRC gave me
these warnings during compilation:

.
.
.
Sivan.rcp:27: warning: Widths of '?' (168) glyphs not in proportion across
different densities
Sivan.rcp:27: warning: Widths of '?' (169) glyphs not in proportion across
different densities
Sivan.rcp:27: warning: Widths of '?' (170) glyphs not in proportion across
different densities
Sivan.rcp:27: warning: Widths of '?' (171) glyphs not in proportion across
different densities
Sivan.rcp:27: warning: Widths of '?' (172) glyphs not in proportion across
different densities
.
.
.

It's the same warning for all glyphs.

If I try to run the output anyway on the Pocket PC (using StyleTap), I get
"gibrish" letters instead of the desired hebrew ones. The display is perfect
and not distorted, but I am unable to display the glyphs I want.

PILRC's documentation on the matter isn't very helpful...

Cheers

-- 
For information on using the ACCESS Developer Forums, or to unsubscribe, please 
see http://www.access-company.com/developers/forums/

Reply via email to