Bug 102091

Summary:	Non-Latin characters fails in description
Product:	[Community] Bugzilla	Reporter:	Yue Shi Lai <ylai>
Component:	Bugzilla General	Assignee:	PnT DevOps Devs <hss-ied-bugs>
Status:	CLOSED WORKSFORME	QA Contact:	David Lawrence <dkl>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.2
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
URL:	http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=102090
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-10-28 20:44:23 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Yue Shi Lai 2003-08-11 03:56:31 UTC

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030225

Description of problem:
Posting non-Latin characters (like Chinese, in this case) fails, and the
characters are displayed as HTML-sequences, whereas non-Latin follow-ups
succeeds. It is rather a problem comment on Chinese translation if you cannot
post the characters itself.

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


How reproducible:
Always

Steps to Reproduce:
1. Open a new bug
2. Write some Chinese characters into the bug description
3. Write some Chinese characters as a follow-up subsequently

Actual Results:  Characters in the description field are displayed as
HTML-sequences.

Expected Results:  Characters posted as Chinese (like in UTF-8) should be
displayed as such.

Additional info:

Comment 1 David Lawrence 2006-04-08 17:42:50 UTC

Red Hat's current Bugzilla version is 2.18. I am moving all older open bugs to
this version. Any bugs against the older versions will need to be verified that
they are still bugs. This will help me also to sort them better.

Comment 2 David Lawrence 2008-09-16 16:50:11 UTC

Red Hat Bugzilla is now using version 3.2 of the Bugzilla codebase and therefore this bug will need to be re-verified against the new release. With the updated code this bug may no longer be relevant or may have been fixed in the new code.
Updating bug version to 3.2.