SOURCES: X11-glibc-charset.patch (NEW) - patch to use

[Andrzej Krzysztofowicz]

=?iso-8859-2?Q?Pawe=B3?= Sakowski wrote:
> 
> On Mon, 2004-09-27 at 18:56 +0200, Andrzej Krzysztofowicz wrote:
> > > The behavior I'd expect is to be able to display any exotic text, even
> > > in pl_PL.ISO-8859-2, as long as I have the correct fonts installed. Had
               ^^^^^^^^^^
> > > I wanted to spare memory, I wouldn't have installed Cyrillic or Tibetan
> > > fonts.
> > 
> > Even if you use a powerful fontserver containing all possible fonts for any
> > case ? And fon some reason you cannot drop this xfs from your FontPath ?
> 
> If well coded, vast font availability on the xfs server needn't result
> in a major increase of memory usage on the client end. But I'm well
> aware this is an if(0) statement.
> 
> A problem is that limiting font availability based on locale is
> extremely inflexible. If you have a Hebrew user learning Japanese, they

But if you declare, that ISO-8859-2 is used for local encoding, what byte
sequences are used for Hebrew/Japanese characters?

I agree with you according to UTF.

> won't be able to set up their system so that they can use fonts for both
> scripts. So, given the choice I (for my desktop) would prefer to have
> available all the fonts[1], accepting the resulting bloat.
> 
> [1] No, I don't speak either Hebrew nor Japanese :)

/me neither writes in these languages ;P

-- 
=======================================================================
  Andrzej M. Krzysztofowicz               ankry at mif.pg.gda.pl
  phone (48)(58) 347 14 61
Faculty of Applied Phys. & Math.,   Gdansk University of Technology