[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kmail-devel
Subject:    Re: Fwd: Re: encoding...
From:       Vadim Plessky <lucy-ples () mtu-net ! ru>
Date:       2000-08-14 5:37:47
[Download RAW message or body]



Can somebody tell me, please, when these changes are going to be implemented?
I confirm that current version of KMail can't handle Russian language - 
neither on Title bar, and incoming messages in Cyrillic come with " ??? ??? 
???" instead of letters.
I suppose this problem also affects Bulgarian and Serbian languages, which 
also use Cyrillic alphabet, but encoding for them should be different.
 
Best regards,


Vadim Plessky


On Mon, 14 Aug 2000, Don Sanders wrote:
> I have recieved a large (600 line) and valuable patch (it fixes a lot of
> charset problems for at least Russian) for KMail that contains the
> following lines:
>
> +   mEncodingMenu->insertItem(i18n("Auto"), 1);
> +   mEncodingMenu->insertSeparator();
> +   mEncodingMenu->insertItem(i18n("KOI8-R"), 3);
> +   mEncodingMenu->insertItem(i18n("WIN-1251"), 4);
> +   mEncodingMenu->insertItem(i18n("ISO-8859-5"), 5);
> +   mEncodingMenu->insertItem(i18n("IBM-866(ALT)"), 6);
> +   mEncodingMenu->insertSeparator();
> +   mEncodingMenu->insertItem(i18n("set default"), 10);
>
>
> 1) I figure I can lose the i18n around the various encodings, at least for
> KDE2.
>
> 2) What about the i18n("Auto") and i18n("set default"), are these ok if the
> strings occur in kdelibs? (How can I tell). I can probably replace "set
> default" with "Default" (which already occurs in KMail) if need be, auto is
> trickier.
>
> BFN,
> Don.

-- 
Best Regards,


Vadim Plessky

[prev in list] [next in list] [prev in thread] [next in thread]