>> if the user doesn't have the Symbol font
>But Symbol is a standard OS font.
But the way the symbol hack works is by assuming that e.g., greek
alpha=latin a, greek beta =latin b, etc. for a one-to-one decimal order
equivalence. This means that whatever text is displayed is actually a
Latin-based language (English, etc.) and not really Greek in any
application other than the browser window. With the lack of tonos and
diaeresis, the supposèd Greek text becomes rather a fragile illusion -- and
especially so when the Symbol font has been removed, for whatever reason.
The few remaining Math symbols are probably too few for the purposes
>> Asking them to download a font is going
>> to cut your audience significantly.
>Doesn't IE allow you to do that stuff in the background now?
>Ans WEFT embedding is a good option too.
Hmm. We've been around the encoding problems with TrueDoc and I think WEFT
before: wherein, the fonts from one platform are opaque to the browser's
need to properly display characters on another platform (win --> mac)
especially in the 128+ ranges. This could be a disaster with Unicode, I
suspect; but, I have not experimented with that aspect.
As much as I dislike reading pdf in a browser, it does seem the better
response to the problem. If horizontal, at least scaled to the intersection
of A4 and USLetter -- International Intersection, as it were -- to allow
for offline printing. I do prefer, though, a narrow & tall browser window.
[log in to unmask]
"It's alive!" The TDC conference on type on-screen