Re: *.abw files across platforms ..

Robert G. Werner (
Mon, 21 Jun 1999 18:47:47 -0700 (PDT)

On systems running X it is even worse. The same font can have different names
and atributes depending on the distribution.
However, this isn't a unique problem and the WWW people have handled it by
establishing a hierarchy of font descriptions that vary from the general
(serif, sans serif), through the very specific (Helvetic at 6 points, bold,
italic, and outlined). The browser trys to match the fonts available to those
the document requests. It seems to me that establishing some basic fall
through policies would be the eaisest way to guarantie Abiword does something
reasonable when a document wants a font the host platform doesn't provide.

Robert G. Werner
Impeach Conggress!!

Now I lay me down to sleep
I pray the double lock will keep;
May no brick through the window break,
And, no one rob me till I awake.

On Mon, 21 Jun 1999, Thomas Fletcher wrote:

> On Sat, 19 Jun 1999, Robert G. Werner wrote:
> > Sorry if this a silly question.
> > Have we established that an *.abw file created on BeOS, say, is easily
> > viewable on Linux or that one created under Win32 can be used on the MacOS?
> > Of course the OS has to be able to read the media that the file resides on but
> > once that is accoplished are there any problems with cariage return's, etc.?
> >
> There shouldn't be ... the biggest obstacle will be
> mapping fonts across since font names tend to
> differ on BeOS from other platforms (don't ask
> why .. I don't know it is just that way).
> Thomas
> -------------------------------------------------------------
> Thomas (toe-mah) Fletcher QNX Software Systems
> Neutrino Development Group
> (613)-591-0931

This archive was generated by hypermail 1.03b2.