Bug 59325

Summary: l10n problem in title of 'Modify View:' dialog...
Product: [Unmaintained] kab3 Reporter: Andrey Cherepanov <sibskull>
Component: generalAssignee: Tobias Koenig <tokoe>
Status: RESOLVED UNMAINTAINED    
Severity: normal    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Compiled Sources   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: Here is the patch for replacing non i18n char * in view names

Description Andrey Cherepanov 2003-06-04 13:11:50 UTC 
Version:           3.1 (using KDE 3.1.2)
Installed from:    compiled sources
Compiler:          gcc version 2.96 20000731 (Red Hat Linux 7.1 2.96-98)
OS:          Linux (i686) release 2.4.7-10

Hi! Russian user talk me about wrong title of modify view dialog. Name of the view on Russian are shown as ??????????. There is correct view name in menu, but in this dialog is incorrect. In ConfigureViewDialog constructor property 'viewName' set incorrect already.
Comment 1 Andrey Cherepanov 2003-06-05 06:42:27 UTC 
I guess, that's happen because view name is stored in KToggleAction in const char * instead 
QString. Quick vay to change it is use QString::local8Bit() instead QString::latin1(), but it's no 
right way of i18n. 
Can I make patch for complete correct this bug?
Comment 2 Andrey Cherepanov 2003-06-05 11:08:57 UTC 
Created attachment 1720 [details]
Here is the patch for replacing non i18n char * in view names

I test - it works fine.
Please, recheck it and put to CVS.
Comment 3 Tobias Koenig 2003-06-05 15:57:15 UTC 
Hi Andrey, 
 
i've modified your patch a bit, to make it compile with CVS HEAD. 
Furthermore I moved the setCaption() call outside the ctor, so we don't 
have to pass the viewName parameter all the time. 
 
Could you test CVS HEAD, if it still works for you? 
 
Ciao, 
Tobias
Comment 4 Tobias Koenig 2009-08-05 15:56:44 UTC 
The development of the old KAddressBook will be discontinued for KDE 4.4.
Since the new application has the same name, but a completly new code base we close all bug reports against the old version and ask the submitters to resend there reports against the new product.