Subject: Re: makewrapper.sh patch
From: Vlad Harchev (hvv@hippo.ru)
Date: Wed Jan 03 2001 - 10:10:46 CST
On Sun, 31 Dec 2000, Kevin Vajk wrote:
>
> On Sat, 30 Dec 2000, Vlad Harchev wrote:
>
> > You seem to be forgetting that unix is multiuser system, and can be used by a
> > lot of users simulatenously. Consider a server at the university with a lot of
> > foreign students, and that computers are all diskless and run AW via NFS from
> > the server. If AW will behave as you suggest, every user will get ALL fonts
> > installed in their comboboxes - and it that case (provided a lot of
> > locale-specific subdirs are present) EACH user will get a dozen of Helvetica
> > in their font combobox. Please think admin-wise, not user-wise. We are not MS
> > or Corel to be so stupid.
>
> Isn't that already the case for all the other applications which
> know how to use system-wide fonts? And the fonts ought to have
> names like "Helvitica", "Helvitica (thai)", "Helvitica (Lao)", etc,
> right?
In fact I'm not sure what's the correct way. I think it's better to use X
fontsets and provide only the one item "Helvetica".
As for CJK support now, CJK font names don't have latin letters in their
name, and they contain latin glyphs too.
But also don't forget about different ecodings. For example, there are 3
rather widely spread encodings for X Windows for Russian language (i.e. given
glyph has different codes in various encodings). In this case, user should see
only the font with encoding that is relevant to his locale - so just loading
all fonts in all subdirectories won't work.
> > You'll just have to set $LANG to something corresponding to Thai, and set
> > $LC_MESSAGES to "en", and of course configure your X server to accept Thai
> > character. Please don't invent the wheel.
>
> I still don't understand. If I want to write a document containing
> English, Thai, and Lao, how is this going to work?
I think there are two solutions - either you invent new locale that includes
characters of English, Thai and Lao (providing locale description to glibc),
or you use some unicode locale (most probably utf8). In the former case,
(and if your X server was setup appropriately) you would be able to type any
"character" of any lagnuage that has a unicode value assigned, provided
you have unicode font installed.
> > But I think we can solve all our problems by prefixing all font names we ship
> > with Abi - i.e. instead of
> > -AbiSource-Arial-regular-r-normal--0-0-0-0-p-0-iso8859-1
> > we call them
> > -AbiSource-AbiArial-regular-r-normal--0-0-0-0-p-0-iso8859-1
> > So those stupid Qt-based apps won't use our scalable fonts, and AW, when
> > reading the list of fonts, will just strip "Abi" prefix, getting "normal" font
> > names ("Arial" in this case).
>
> Having abiword step on KDE applications isn't good. Nobody's
> objected to re-naming our fonts this way yet, have they?
I'll ask this question in a serparate message.
> - Kevin Vajk
> <kvajk@ricochet.net>
>
>
I'm sorry for so late reply.
Best regards,
-Vlad
This archive was generated by hypermail 2b25 : Wed Jan 03 2001 - 11:25:10 CST