i18n and QStrings

[Thiago Macieira]

Andras Mantia wrote:
>Hi,
>
> As today I hit the problem that my QString got damaged after a i18n call
> (it contained unicode chars - eg.  ű = udoubleacute - and it was replaced
> by ?) because i18n() expects const char *, I think it would be a good idea
> to add a QString i18n(const QString& text) which would call simply be:
>
>QString i18n(const QString& text)
>{
>   return i18n(text.utf8());
>}
>
>Is it a bad idea? Yeah, I don't really know which one will be picked up in
>case of i18n("foo")...

i18n expects an 8-bit encoded text, not a Unicode text. Why do you need to 
translate something that is already Unicode?

-- 
  Thiago Macieira  -  Registered Linux user #65028
   thiagom at mail.com           
    ICQ UIN: 1967141   PGP/GPG: 0x6EF45358; fingerprint:
    E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: signature
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20031129/14321c44/attachment.sig>