Chris Carlen wrote:
Akar wrote:
If he wanted to do as I thought which is an English KDE but with the
ability to write and view Thai, then I think my earlier post was
correct, he should set the desktop,filemanager, general AND qtconfig
general font to arial or something and choose his thai font as the
backup where thai glyphs aren't available. If his thai font has western
character set as well then he can do just that font by itself.
That is exactly what I want to do, yes. The Tahoma font has Western as
well as Thai and a few other character sets.
If he wants all his kde apps and menus in Thai, then yes he certainly
needs to get the i18n kit for thai as well as thai fonts.As you say the
encoding is set automatically but you must have fonts with the glyphs
available. No matter what language you choose in KDE you should still be
able to display other glyphs in the same window.
Yes, I have installed the i18n package, which makes it possible to make
KDE be in Thai. But as you have ascertained above, that is not the goal
here. Rather we only want to be able to type Thai sometimes, by
switching the keyboard (which is working fine).
The remaining problem at this point, as I mentioned in another post, is
that Thai filenames are not displaying correctly in Konqueror.
In fact, here is the current way things happen:
I set my font to Tahoma for all KDE fonts except fixed width, and in
Konqueror. Next I "create new text file" in Konqueror. When the dialog
appears to type in the file name, I switch to Thai keyboard. Ok so far.
I type in a filename. The characters are Thai! (That is good.)
Now I hit enter to make the file, and konqueror shows the filename as
"???????????????" What's even stranger is I can right click it and
select "Properties" and the question marks appear in the Properties dialog.
At this point I can type Thai Ok in most input fields within KDE.
Now here's another interesting observation that I think confirms what I
am suspecting to be the problem here:
I created a text file in kwrite. I set the Tahoma font for kwrite. I
can type in Thai! Then I saved the file. Then I opened the file in
kwrite. What happens next is predictable:
The characters show up all as "?????????????????????????"
Qt has no way of knowing what encoding to use for this text. Thus the
removal of the ability for the user to select the encoding to use for a
font, and to remove a nice GUI selection box for this, is quite a silly
thing to have been done. It is Windows like. "We will decide what you
need, we know better than you..."
Actually, UniCode is supposed to take care of this issue since Unicode
includes ALL of the IS)-8859 pages as well as other stuff and
ideographic fonts.
Ok, I need to go over to the other thread I started in the devel forum,
and respond to the replies over there for a while.
I think that what you are now describing is a bug. :-(
So, all I can suggest is that you submit a bug report.
As I understand what others on the devel list have said, Qt-3.x is now
supposed to work with UniCode -- even for fonts not encoded as UniCode
-- so there isn't any need to set encoding (for languages using 255 or
less characters at least) since UniCode should take care of this.
But, as you report, this isn't working properly yet. That *IS* a
problem and it needs fixing.
It ia remotely possible that this would work better with an actual
UniCode font, but I don't know for sure.
--
JRT
___________________________________________________
This message is from the kde-linux mailing list.
Account management:
http://mail.kde.org/mailman/listinfo/kde-linux.
Archives:
http://lists.kde.org/.
More info:
http://www.kde.org/faq.html.
