On Wed, Mar 12, 2003 at 11:00:28AM +0200, Ira Abramov wrote:
> Quoting Shaul Karl, from the post of Tue, 11 Mar:
> > $ cd licq-1.2.3
> > ./configure --help|grep hebrew
> > --enable-hebrew include support for hebrew reverse string
>
> I don't think it needs it in QT3, which supports Hebrew out of the box.
> however the GTk GUI plugin of licq doesn't support Hebrew. could that
> switch be GTk specific? or maybe for the console version of licq? the
> program comes with three different interfaces (I mean different features
> on each as well, QT seems the most advanced), so I'd imagine that switch
> relates only to one of the three (I bet on the text mode)
>
I don't know. I guess that now we need someone who can understand the
source. GTk 2 support Hebrew much like QT3, doesn't it? What will happen
when the package gets compiled against GTk 2?
In general, can I write software which will be compiled against QT3
so that it will be able to use the QT3 bidi features even in text mode
(be it on the console, xterm, ...)? What about GTk?
Isn't there a bidi library which is independent of whether the program
is running in textual or graphical environment? Can QT3 or GTk bidi
features turned off so that such a library can always do its work? Does
the use of unicode or utf8 eliminate the problem all together by avoiding
it in the first place? I do feel that I am using most of the relevant
buzz words that I am familiar with but in effect I am totally clueless.
--
Shaul Karl, [EMAIL PROTECTED] e t
=================================================================
To unsubscribe, send mail to [EMAIL PROTECTED] with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]
