Version: (using KDE KDE 3.4.92) Installed from: Compiled From Sources Compiler: gcc 3.4 OS: Linux When translating the status strings in the PO file, I found one strange thing. Translating some of "Offline", "Online", "Away", "Invisbile","Connecting" (commonly used string, not protocol specific) causes the select-status-in-some-protocol menu displays wrong translated strings. Some are replaced by "Offline", and some are replaced by "Away." But if I leave these common strings untranslated, the status strings in protocols are correct. To simplify the complexity, I make an experiment : I downloaded a new POT file from SVN, made necesarry changes, and only translated the five strings. It yields: Original Displayed String String (I type them in English here) ========== ============= (Yahoo) 01 Online => Online 12 Invisible => Online 13 Offline => Online (MSN) 07 Invisible => untranslated Online 08 Offline => untranslated Online (Jabber) 02 Online => Online 03 Away => Online 07 Invisible => Online 08 Offline => Online (IRC) 01 Online => Online 02 Away => Online 03 Offline => Online (ICQ) 03 Away => Online 07 Offline => Online (AIM) 01 Online => Online 02 Away => Away 03 Offline => Offline How do I solve this, thanks ^^
Created attachment 13288 [details] PO file, only the five strings translated
You forgot to specify in what language. from the po file, i see this is Traditional Chinese
Bugs to zh_TW should be assigned to KDE I18N maintainers, because the default assignee has left F/OSS community several YEARS ago, and doesn't answer any report since then.
WRT comment #3: I've seen Jing-Jong Shyue contributing lately some translations, so he seems to be active again - and maybe could do something on that, too...
Please reassign this bug to me. I have been the coordinator of the zh_TW translation team since August 2006. However I did not understand this bug very clearly. The kopete's po file had been fully translated and updated. Hope this problem has already solved. If not, please give me a mail (you can use Chinese :D) describing the problem again, and I'll see what I can do.
So, if you do not see same phenomenon anymore, as described in the bug report, and reporter won't confirm either fixing or persisting, you may probably safely close the bug (after all, it's over 1,5 year old...)
I think that this bug should have been fixed, but it seems that I don't have permissions to close this bug. Maybe someone could help us with this.
Then closing as fixed...