On Воскресенье 15 Декабрь 2002 14:57, Juergen Spitzmueller wrote:
> Vitaly Lipatov wrote:
> > Please pay attention for incorrect letters in discussed
> > screenshot. I underlined such letters in attached file.
>
> Vitaly,
> can you dig a bit further if and which characters are
> displayed wrong? Pe
Vitaly Lipatov wrote:
> Please pay attention for incorrect letters in discussed
> screenshot. I underlined such letters in attached file.
Vitaly,
can you dig a bit further if and which characters are displayed wrong? Perhaps
this is only a font problem at my end (and, as I said, I really don't us
On Четверг 12 Декабрь 2002 23:42, Juergen Spitzmueller wrote:
> Kornel Benko wrote:
> > Yes I knew this. I am regularly testing with both frontends.
> > I was answering to Johns: "...and qt shows '?'"
> > which in my case is not valid.
>
> I have similar experiences. In xforms, ru_intro is displaye
On Четверг 12 Декабрь 2002 23:42, Juergen Spitzmueller wrote:
> Kornel Benko wrote:
> > Yes I knew this. I am regularly testing with both frontends.
> > I was answering to Johns: "...and qt shows '?'"
> > which in my case is not valid.
>
> I have similar experiences. In xforms, ru_intro is displaye
On Thu, Dec 12, 2002 at 10:23:21PM +0100, Kornel Benko wrote:
> How does QT know that a char shoud be displayed as registered (0xae) and not as
>Zcaron? (0x1ae)
> Do we supply full unicode for displaying?
because we convert the text using encoding->ucs (that Dekel added)
see QLPainter.C
regard
-BEGIN PGP SIGNED MESSAGE-
On Donnerstag, 12. Dezember 2002 21:41, John Levon wrote:
> I suppose Xlib will just display what we ask for. Whereas Qt has the
> unicode and knows it can't be shown in the given font.
>
> I guess that would explain that
How does QT know that a char shoud be di
-BEGIN PGP SIGNED MESSAGE-
On Donnerstag, 12. Dezember 2002 21:41, John Levon wrote:
> because you, like me, haven't got latin2 fonts I suppose ?
That may be. I am installing the 8859-2 fonts as soon as possible.
# xlsfonts | grep 8859-2 | wc
543 831 33632
On Thu, Dec 12, 2002 at 09:53:48PM +0100, Juergen Spitzmueller wrote:
> XFLD: -adobe-times-medium-r-normal--34-240-100-100-p-170-iso10646-1
iso10646 - I do not have these fonts. (I have only a couple iso10646
fonts)
http://www.nada.kth.se/i18n/ucs/unicode-iso10646-oview.html
So I think this ex
Am Donnerstag, 12. Dezember 2002 21:48 schrieb John Levon:
> On Thu, Dec 12, 2002 at 09:42:11PM +0100, Juergen Spitzmueller wrote:
> > I have similar experiences. In xforms, ru_intro is displayed with weird
> > characters, in qt, it looks like correct russian (not that I can read it;
> > see screen
-BEGIN PGP SIGNED MESSAGE-
On Donnerstag, 12. Dezember 2002 21:42, Juergen Spitzmueller wrote:
> I have similar experiences. In xforms, ru_intro is displayed with weird
> characters, in qt, it looks like correct russian (not that I can read it;
> see screenshot).
> This is qt 3.0.5
I can
On Thu, Dec 12, 2002 at 09:51:38PM +0100, Kornel Benko wrote:
> > and indeed, apart from the u, I get '?'
> >
> > xforms shows it correctly
>
> This is weird. Then _my_ xforms is broken ? ( 1.0 btw)
I mean "correctly but wrongly". I know that doesn't make much sense :)
I see copyright etc. in
-BEGIN PGP SIGNED MESSAGE-
On Donnerstag, 12. Dezember 2002 21:37, John Levon wrote:
> and indeed, apart from the u, I get '?'
>
> xforms shows it correctly
This is weird. Then _my_ xforms is broken ? ( 1.0 btw)
> since we do the ucs stuff in QLPainter.C, I don't understand why
Maybe,
On Thu, Dec 12, 2002 at 09:42:11PM +0100, Juergen Spitzmueller wrote:
> I have similar experiences. In xforms, ru_intro is displayed with weird
> characters, in qt, it looks like correct russian (not that I can read it; see
> screenshot).
> This is qt 3.0.5
Hmm, interesting. What fonts do you h
Kornel Benko wrote:
> Yes I knew this. I am regularly testing with both frontends.
> I was answering to Johns: "...and qt shows '?'"
> which in my case is not valid.
I have similar experiences. In xforms, ru_intro is displayed with weird
characters, in qt, it looks like correct russian (not that
On Thu, Dec 12, 2002 at 08:10:10PM +, Angus Leeming wrote:
> The xforms frontend certainly displays this incorrectly. Attached.
because you, like me, haven't got latin2 fonts I suppose ?
I just don't understand why there's a difference. Hmm actually
I suppose Xlib will just display what we
On Thu, Dec 12, 2002 at 08:57:55PM +0100, Kornel Benko wrote:
> On Donnerstag, 12. Dezember 2002 20:36, John Levon wrote:
> > but I don't know why xforms just shows wrong fonts, and qt shows '?'
> > everywhere.
>
> Why should qt do that?
> See attached
and indeed, apart from the u, I get '?'
xf
-BEGIN PGP SIGNED MESSAGE-
On Donnerstag, 12. Dezember 2002 21:10, Angus Leeming wrote:
...
> The xforms frontend certainly displays this incorrectly. Attached.
> Angus
Yes I knew this. I am regularly testing with both frontends.
I was answering to Johns: "...and qt shows '?'"
which in my
On Thursday 12 December 2002 7:57 pm, Kornel Benko wrote:
> -BEGIN PGP SIGNED MESSAGE-
>
> On Donnerstag, 12. Dezember 2002 20:36, John Levon wrote:
> > but I don't know why xforms just shows wrong fonts, and qt shows '?'
> > everywhere.
>
> Why should qt do that?
> See attached
The xforms
-BEGIN PGP SIGNED MESSAGE-
On Donnerstag, 12. Dezember 2002 20:36, John Levon wrote:
> but I don't know why xforms just shows wrong fonts, and qt shows '?'
> everywhere.
Why should qt do that?
See attached
Kornel
- --
Kornel Benko
[EMAIL PROTECTED]
-BEGIN PGP SIGNATURE-
On Thu, Dec 12, 2002 at 07:51:12PM +0100, Kornel Benko wrote:
> > Is there some Qt user who could test this ? Is there somebody who would
> > be willing to test a QLyXKeySym that tries to iterate through all codecs
> > with canEncode() to find a codec that can convert to getISOEncoded ?
>
> What
On Thu, Dec 12, 2002 at 08:04:24PM +0100, Juergen Spitzmueller wrote:
> It is a new function of qt 3.1:
> http://www.trolltech.com/developer/changes/3.1.html
darn. Alternatively I wonder if we could pass every string through a
fucntion before passing it to Qt, that converted it to a QString via
Q
Kornel Benko wrote:
> > void QTextCodec::setCodecForCStrings ( QTextCodec * c ) [static]
> I did not find this function in qt3 ...
It is a new function of qt 3.1:
http://www.trolltech.com/developer/changes/3.1.html
Jürgen.
-BEGIN PGP SIGNED MESSAGE-
On Donnerstag, 12. Dezember 2002 19:10, John Levon wrote:
> AIUI the problem is that the char * strings are encoded in non-latin1,
> so we cannot make QStrings with the right text from them. However, there
> is this function :
>
> void QTextCodec::setCodecForCStr
23 matches
Mail list logo
