From: BobF on
some dude wrote:
> I tried Qt the other day. QString AString = L"string"; was an error.

wxWidgets?
From: Goran on
On Feb 5, 1:28 pm, some dude <n...(a)no.com> wrote:
> I tried Qt the other day.  QString AString = L"string"; was an error.

So use a ctor with QChar. Did you try to suggest that Qt doesn't
support Unicode? Naaah... ( Docs were tl;dr, huh? ;-) )

Goran.
From: Giovanni Dicanio on
"Goran" <goran.pusic(a)gmail.com> ha scritto nel messaggio
news:2e448c96-8106-49e4-8772-427d42e24d5e(a)c4g2000yqa.googlegroups.com...

> So use a ctor with QChar.

It seems there is no simple ctor taking just one 'const QChar*'.

Giovanni


From: Tom Serface on
Yeah, that's sort of like saying, "if you want a million $, just get a
million $".

Tom

"Goran" <goran.pusic(a)gmail.com> wrote in message
news:aac00d90-0642-4da3-8f10-b1c4b3958bbb(a)j31g2000yqa.googlegroups.com...
> On Feb 5, 1:38 am, some dude <n...(a)no.com> wrote:
>> Pretty slick, can it be made portable?
>
> What, to port to e.g. Unix clone? Haha, good one. No, not with MFC^.
> Try Qt.
>
> ^ Technically, it _is_ possible - just ;-) port relevant MFC parts to
> another window manager (or make one for your target platform.
>
> Goran.

From: Tom Serface on
I absolutely agree about putting string resources in the resource file
(especially in 2010 where it will be Unicode by default). I even put format
strings in the resources now. I've been hit by the phrase, "Oh yeah we
forgot to tell you, it also need to run in Japanese" too many times. My
opinon:

1. Always use Unicode
2. Always use resource string table for any strings

Tom

"Giovanni Dicanio" <giovanniDOTdicanio(a)REMOVEMEgmail.com> wrote in message
news:e9m$xEmpKHA.3792(a)TK2MSFTNGP06.phx.gbl...
>> http://doc.trolltech.com/4.6/qstring.html
>>
>> it seems to me that QString offers a constructor which takes a const char
>> *, but not a wchar_t*...
>
> Or to be more accurate, the QChar * (i.e. Unicode version) constructor
> takes an additional size parameter:
>
> http://doc.trolltech.com/4.6/qstring.html#QString-2
>
> BTW: As Mihai several times wrote here, the best thing to do for
> internationalization is to put string literals in resources instead of
> embedding them in source code.
>
> Giovanni
>
>