I think the status info is Ajax-ed in... If so, it’s a separate HTTP request and process to display it, so being “different” should come as no surprise.
So it may not be output by the server as UTF-8, or the Ajax routines to parse/display the output may be maniuplating it as if it’s ASCII... You could probably do some digging in LiveHeaders in FireFox to narrow down the issue a bit... You may even be able to solve it :-) On 5/7/10 1:08 AM, "Kumar, Ashish" <xml.de...@gmail.com> wrote: > Hello, > > We are currently using Nagios 3.0.6 on RHEL 5. > > I have checked Nagios archives already but there is something I found strange, > so I am posting it here. > > I was testing UTF-8 support in Nagios with following are the results: > > 1. Created 3 filesystems /Индия, /भारत, /インド (thank you Google translate) > Results: > All of them appear as it is in "Service section" in Nagios UI > > 2. Defined a NSCA service and sent messages in different languages with > different severity level > Result: > E-mails are sent with UTF-8 characters perfectly fine > The message appears with junk characters in "Status Information" section of > Nagios UI > > It's pretty interesting that UTF-8 characters appear perfectly fine in > "Service" section but not in "Status Information" that too in same UI. Is > there a way to fix this? > > Thank you. > > > ------------------------------------------------------------------------------ > > > _______________________________________________ > Nagios-users mailing list > Nagios-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/nagios-users > ::: Please include Nagios version, plugin version (-v) and OS when reporting > any issue. > ::: Messages without supporting info will risk being sent to /dev/null
------------------------------------------------------------------------------
_______________________________________________ Nagios-users mailing list Nagios-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null
