You are not logged in.

Dear visitor, welcome to KDE-Forum.org. If this is your first visit here, please read the Help. It explains in detail how this page works. To use all features of this page, you should consider registering. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.

KitKat

Beginner

  • "KitKat" started this thread

Posts: 18

Location: Germany

  • Send private message

1

Sunday, September 17th 2006, 12:41pm

[kopete] error in metacontact view

Hi everyone,

when I mouse-hover over a metacontact with mulitple protocols, its info panel pops up and it looks like this:

When I do the same for a metacontact with only one protocol, I don't get these all-caps lines.

I'm running kopete 0.12.2. but this error occured suddenly (no changes from me, IIRC) when I was still running a 0.10.x version.

Is there any setting that I have missed? Is this a bug?
No trees were killed in the creation of this message. However, many electrons were terribly inconvenienced.

This post has been edited 1 times, last edit by "KitKat" (Sep 17th 2006, 12:44pm)


2

Sunday, September 17th 2006, 1:29pm

You probably need the correct i18n package for your distribution and KDE version. I had the same problem after I updated my KDE installation and missed the i18n package. After installing the updated i18n package, the problem was gone.

KitKat

Beginner

  • "KitKat" started this thread

Posts: 18

Location: Germany

  • Send private message

3

Sunday, September 17th 2006, 1:36pm

As per yast (I'm using Suse 10.0), kde3-i18n-de is istalled. How do I update it?
No trees were killed in the creation of this message. However, many electrons were terribly inconvenienced.

This post has been edited 1 times, last edit by "KitKat" (Sep 17th 2006, 1:39pm)


4

Sunday, September 17th 2006, 2:50pm

In fact, you only need to update the i18n-file for kopete, which is located in /opt/kde3/share/locale/de/LC_MESSAGES/kopete.mo

download http://websvn.kde.org/*checkout*/branche…twork/kopete.po and the use the following command to build your kopete.mo-file:

Source code

1
msgfmt kopete.po -o kopete.mo

Place the resulting file in opt/kde3/share/locale/de/LC_MESSAGES/ and be sure to back up the existing file (if there is an existing file).

KitKat

Beginner

  • "KitKat" started this thread

Posts: 18

Location: Germany

  • Send private message

5

Sunday, September 17th 2006, 3:21pm

Sorry, if this seems stupid, but download how (copy, paste as text file?) and where to? I can't get that command to work.
No trees were killed in the creation of this message. However, many electrons were terribly inconvenienced.

6

Sunday, September 17th 2006, 3:33pm

Simply issue the following command on Konsole:

Source code

1
wget http://websvn.kde.org/*checkout*/branches/stable/l10n/de/messages/kdenetwork/kopete.po

The next step is compiling the file

Source code

1
msgfmt kopete.po -o kopete.mo
You need to install the package "gettext" in order to have "msgfmt" available.

Then copy the resulting file to the mentioned location.

KitKat

Beginner

  • "KitKat" started this thread

Posts: 18

Location: Germany

  • Send private message

7

Sunday, September 17th 2006, 3:52pm

Thanks, that worked!

Do I need to keep the kopete.po and the kopete.mo I created in my home folder or can I delete those?
No trees were killed in the creation of this message. However, many electrons were terribly inconvenienced.

This post has been edited 1 times, last edit by "KitKat" (Sep 17th 2006, 3:53pm)


8

Sunday, September 17th 2006, 4:03pm

Well, you do not really need them anymore, but I would a least keep kopete.po, just in case I need to compile it once again.

Is the metacontact-info now formatted correctly?

KitKat

Beginner

  • "KitKat" started this thread

Posts: 18

Location: Germany

  • Send private message

9

Sunday, September 17th 2006, 4:05pm

OK, I'll keep that.

Yep, the formatting now shows without those all-caps lines and is now much clearer and easier to read.

Thanks again.
No trees were killed in the creation of this message. However, many electrons were terribly inconvenienced.