[prev in list] [next in list] [prev in thread] [next in thread] 

List:       koffice
Subject:    Re: Negative review of koffice..
From:       Marko Samastur <markos () elite ! org>
Date:       2000-04-20 15:45:38
[Download RAW message or body]

Rudiger Koch wrote:
> 
> Am Mit, 19 Apr 2000 schrieb Marko Samastur:
> >
> > The other problem is that right now, it doesn't work. Or at least in SO
> > it doesn't. If I use an iso-8895-2 font for typing (which is the right
> > one for slovenians like me), I get non-latin1 letters on the screen, but
> > not on the paper.
> 
> iso-8895-2 might not be the right choice if your font is encoded using another
> scheme such as microsoft-symbol, apple-roman, microsoft-unicode... Ghostscript
> seemingly figures the right encoding to use by itself. So try using another
> encoding (Any)

No. iso-8859-2 is the only right one. No other encoding contains all the
necessary characters, except microsofts 1250, which isn't used in Linux
anyway.

> Why does the user need to take care of this, anyway? It seems highly redundant
> and a constant source of error for unexperienced users of non Roman scripts.
> Using "AnyCharSet" works fine for me in Thailand for _all font encodings that
> occur for Thai fonts.

I have no idea how this works in 2.0, but in 1.1.2 choosing Anycharset
will get me latin1 or something which doesn't include latin2 set. Funny
result is that you install distribution with KDE and choose Slovenian as
language, but when you first start KDE, you get menus with the wrong
charsets, which you then must manualy set in Contro center.
 
It seems silly in 1.1.2 that choosing language doesn't select correct
fonts and even when you select them, some applications like Konsole just
don't care.

Marko

[prev in list] [next in list] [prev in thread] [next in thread]