'Re: Bug#12036: non-latin1 chars displayed as ? in most KDE apps'

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

List:       kde-devel
Subject:    Re: Bug#12036: non-latin1 chars displayed as ? in most KDE apps
From:       Vadim Plessky <lucy-ples () mtu-net ! ru>
Date:       2000-09-29 19:05:23
[Download RAW message or body]

On Fri, 29 Sep 2000, David Faure wrote:
|  On Fri, 29 Sep 2000, Vadim Plessky wrote :
|  >On Fri, 29 Sep 2000, Tinkl Lukб№ wrote:
|  >|  > -----Original Message-----
|  >|  > From: David Faure [mailto:david@mandrakesoft.com]
|  >|  >
|  >|  > >It should be noted that this [class of] bug makes it hardly
|  >|  > > possible to use KDE2 in non-English environment -- I don't speak
|  >|  > > about i18n here but about actually typing in non-latin1 strings.
|  >|  >
|  >|  > Many of those problems have been fixed recently.
|  >|  > (Among other things, after I met Lukas Tinkl, who is Czech
|  >|  > too, and we looked at
|  >|  > many of those problems and  fixed them).
|  >
|  >When it was fixed?
|  >I downloaded today build 0927mdk.
|
|  I'd hardly call that today. :)
The latest which were on Mandrake Cooker (:-|
|
|  Outgoing mails have been fixed (at least they have been tested to work for
| latin2).
If I forward/reply, then place in Outbox - I can view them in Russian.
But, if just Forward and want to add something - no way.
For some reason, it's not possible to change font in Kmail for Quoted text - 
fist level, Second level, Thirs level.
I reported it as bug, but still not fixed. Only default Helvetica, which has 
iso-8859-1 coding. 

|
|  The keyboard switcher depends on X finding the key maps, not always the
| case. In any case, you need to change the charset in KControl - an
| automatic binding from the keyboard to the charset is at the moment just a
| vague and recent idea....
well, Cyrillic characters are located in second half of 256 character map.
Keyboard has only 104 keys. 28 are Latin letters. I don't know how to put +33 
characters of Russian alphabet on these keys.
And, then, what is wonderful US/RU flags doing on panel? It's even possible 
to switch them :-), but nothing happens.
I belive keyboard switcher was implemeted in MS Windows from 1995. Works 
through key combination (usally Alt+Shift or Ctrl+Shift) anf flag on panel as 
well.
|
|  > Konqi has problem - if  "Character-encoding=windows-1251" is specified
|  > in META tag, it doesn't display page in Russian. If there is no tag -
|  > displays correctly. Tested several times.
|
|  I fixed support for charset-specification in the HTTP header
| (Content-Type), but I don't know about the meta-tags in the HTML itself. I
| thought they were handled though.
ohh, eyahh. build 927 now handles it. Thanks!
Here is standard Meta tag for 1251 charset:
<HTML><HEAD><TITLE>Графическая Оболочка КДЕ</TITLE>
<META content="text/html; charset=windows-1251" http-equiv=Content-Type>

|
|  About working with 2 languages, well, the GUI has to appear in one only,
| not in two... Working with 2 languages with different charsets would
GUI - of course, in one language. Input from keyboard - in any number of 
languages.

| require some work in the apps (like koffice apps), which isn't done yet,
| but planned.

I believe keyboard switcher(handler) handles it.
When I press F key with US-English or UK-English layout, handler provides F 
to program.
When I press same key with Russian layout, same key gives "A" (well, not 
English A, but letter which looks like the same as English A, code is 192, if 
I remeber. Russian alahabet is located in last 64 bytes of 256 char. set, one 
letter , 33rd, is misplaced)
Same way for of handling - for all other keys.

Hope this helps.

-- 
Vadim Plessky

>> Visit http://master.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

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