Bug 88747 - mrtg has problems with i18n?
Summary: mrtg has problems with i18n?
Status: CLOSED DUPLICATE of bug 75913
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: mrtg
Version: 8.0
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Miloslav Trmač
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2003-04-13 00:15 UTC by Bruno Lopes F. Cabral
Modified: 2007-04-18 16:53 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2006-02-21 18:52:39 UTC

Attachments (Terms of Use)

Description Bruno Lopes F. Cabral 2003-04-13 00:15:01 UTC
Description of problem:

	mrtg do not to behave well with LANG environment var being set
	to pt_BR-UTF-8 (chosen during a clean install of RH8)

Version-Release number of selected component (if applicable):

	# rpm -q mrtg

How reproducible:


Steps to Reproduce:

	the following command will give lots of error on a DEFAULT install
	of RH8.0 with LANG=pt_BR.UTF-8 (choosen during install)

	# mrtg /etc/mrtg/mrtg.cfg

	if you do # LANG="" mrtg /etc/mrtg/mrtg.cfg
	or # LANG="pt_BR" mrtg /etc/mrtg/mrtg.cfg
	it will succeed
Actual results:

Malformed UTF-8 character (unexpected non-continuation byte 0x20, immediately
after start byte 0xf2) at /usr/bin/../lib/mrtg2/locales_mrtg.pm line 2404.
Malformed UTF-8 character (unexpected continuation byte 0xb3, with no preceding
start byte) at /usr/bin/../lib/mrtg2/locales_mrtg.pm line 3107.
Malformed UTF-8 character (unexpected non-continuation byte 0x20, immediately
after start byte 0xe2) at /usr/bin/../lib/mrtg2/locales_mrtg.pm line 3107.

Expected results:

	No error message from UTF-8

Additional info:


Comment 1 Zach Gorman 2003-04-18 18:14:02 UTC
I think this is the same as bug #75913

Comment 2 Miloslav Trmač 2004-08-16 21:04:07 UTC

*** This bug has been marked as a duplicate of 75913 ***

Comment 3 Red Hat Bugzilla 2006-02-21 18:52:39 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

Note You need to log in before you can comment on or make changes to this bug.