GNOME Bugzilla – Bug 332640
cmd_me show no action string but nick
Last modified: 2006-10-11 19:53:49 UTC
/me blah just show my nick. /me action from other people do the same. But if blah include my nick, highlight works and red colored string shows up. A little dig into source code but found nothing in doubt.
Have you the same issue with xchat2 (gtk) ?
No, xchat and xchat2 have always show them all.
And with a fresh user ?
It seems this bug is reproductible : https://launchpad.net/distros/ubuntu/+source/xchat-gnome/+bug/35878
Every single change of nick does not make things better. Options of color nick and timestamp do nothing either. All sort of nicks (include from others) (and include multibyte characters) are nothing different.
What OS are you on?
I confirm this on 0.11 / mandriva 2006 (seerofsouls.com backport) Could it be related to translated strings somehow? Some clueless dweeb on Rosetta completely borked the Dutch translation... (Please make translations managed via regular GNOME cvs! But that's offtopic for this bug.)
Hmm, very possibly. Why should we use gnome cvs for translations when we don't use gnome cvs for anything else?
David, please read this article: http://www.mdke.org/blog/Ubuntu_Translation___Quality_Assurance.html There is (some) quality control on the translations produced in the GTP, where there is none at all on Rosetta, and this is just another example. I tried to fix some of the errors on Rosetta after the 0.10 release btw, but it looks like the errors are still there in 0.11.
I cannot reproduce the bug with LANGUAGE=C.
Where were you "fixing some of the errors"? Only the translations in the trunk branch on rosetta get merged back into upstream.
I don't recall having seen multiple branches on Rosetta, I just tried to fix some of the most glaring errors.
(In reply to comment #9) > David, please read this article: > http://www.mdke.org/blog/Ubuntu_Translation___Quality_Assurance.html > > There is (some) quality control on the translations produced in the GTP, where > there is none at all on Rosetta, and this is just another example. I tried to > fix some of the errors on Rosetta after the 0.10 release btw, but it looks like > the errors are still there in 0.11. > xchat-gnome is not an official GNOME module and so i don't think that would change something. Official translators mainly translate GNOME applications.
Being one of these "official" translators, I can say with confidence that there are a lot of non-official GNOME modules in "extras" that we are happily translating.
Any changes you make on https://launchpad.net/products/xchat-gnome/trunk/+pots/xchat-gnome will make it into HEAD. There are translation branches in rosetta for each of the versions in ubuntu, but I've yet to figure out how to easily merge those upstream. If there's a really compelling reason to stop using rosetta, I will, but at the moment, there's not a whole lot of translation activity happening on either side of the fence.
I just replaced the translations in svn with those in the dapper branch of rosetta. Assuming it was fixed there, it should be fixed in svn head too.
*** Bug 347548 has been marked as a duplicate of this bug. ***
After some investigations on IRC (thanks to Vinicius!) it seems this bug still occurs in 0.12. This bug happened with LANG=pt_BR.UTF-8 but not with C locales so that's clearly a translation issue. I reopen the bug until someone using this local test with HEAD version.
I didn't sync from the other branch of rosetta until after 0.12 was cut, so it's unsurprising that this bug is in it. HEAD (and soon 0.13) should work if the translations were fixed.
This should be fixed in 0.13, please reopen if not.
This bug is still present in the 0.13 de_DE.UTF-8. See https://launchpad.net/distros/ubuntu/+source/xchat-gnome/+bug/35878
German translations should be fixed in Ubuntu: https://launchpad.net/products/xchat-gnome/+bug/60527
Fixed in the development version. The fix will be available in the next major release. Thank you for your bug report.