Bug 291161 - Existing bugzilla entries containing non-ascii are corrupt äöü
Summary: Existing bugzilla entries containing non-ascii are corrupt äöü
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Bugzilla
Classification: Community
Component: Bugzilla General
Version: devel
Hardware: All
OS: Linux
medium
low
Target Milestone: ---
Assignee: PnT DevOps Devs
QA Contact:
URL:
Whiteboard:
: 441032 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-09-14 16:00 UTC by Need Real Name
Modified: 2013-06-24 02:46 UTC (History)
0 users

Fixed In Version: 2.18
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-04-05 20:49:52 UTC
Embargoed:

Attachments (Terms of Use)

Description Need Real Name 2007-09-14 16:00:23 UTC 
Bugzilla entries containing non-ascii are either corrupt or the pages have the
wrong charset.

äöü
Comment 1 Need Real Name 2007-09-14 16:01:35 UTC 
Only applies to existing bugzilla entries, e.g. see bug 291041 (assigned to's name)
Comment 2 Noura El hawary 2007-09-17 01:28:21 UTC 
Yes, you are right ,, Thanks for reporting it.. It is a UTF-8 issue and we are
currently working on solving it.

Thanks,
Noura
Comment 3 Need Real Name 2007-11-01 19:17:38 UTC 
Can we keep this open until the bug is fixed?
Comment 4 David Lawrence 2007-11-07 04:09:29 UTC 
The assigned to name in bug 291041 is now displaying properly which is why I
closed this bug. Is there something that is still not displaying properly for you?
Comment 5 Need Real Name 2007-11-07 07:10:04 UTC 
The title, initial bug description and summary for this bug all still contain
corrupt characters.
Comment 6 Need Real Name 2008-04-05 11:25:05 UTC 
*** Bug 441032 has been marked as a duplicate of this bug. ***
Comment 7 Need Real Name 2008-04-05 11:27:29 UTC 
New bugs are okay but existing bugs are still broken.

Mark as WONTFIX, since this bug is not being given any time?
Comment 8 David Lawrence 2008-04-05 20:49:52 UTC 
We did some code work that should fix new reports coming in but not much has
been done on bugs that were already in the database before the fixes. We are
focusing all of our resources currently on updating to newer 3.2 version which
has much better support for handling utf8. So we can close this as NEXTRELEASE.
Note You need to log in before you can comment on or make changes to this bug.