User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; MyIE2; .NET CLR 1.1.4322) Build Identifier: template/en/default/list/table.html.tmpl have field 'maxlength' It is BYTE count. Need character count. Because UTF-8 is multibyte string Reproducible: Always Steps to Reproduce: 1.Make bug have summary contents no latin characters 2.Look this sammary in buglist. Actual Results: Field 'short summary'in buglist have bad last character. Count of character is < 60.

It also happens with the component field. If the component name is "Suivi Déclaration", the 8-bytes truncated string will be "Suivi d&#65533;"

*** Bug 332190 has been marked as a duplicate of this bug. ***

Confirming. It's what we should do as soon as possible. What's up if you happen to be bitten by bug 331583? Do we need to fix such databases here, or in bug 304550, or not at all?

There has a patch been proposed on bug 332190 for this. I asked to move it here.

This is patch from bug #332190. This patch is only for illustration. String must be decoded not in inner functions of Bugzilla, but just when it comes from outside.

Bug 332190, of which this is marked as a duplicate, is actually more general than this one. In our bugzilla installation we mainly use Greek, and I consider bad wrapping in the description and comments much more annoying than the bad truncation of the summary.

Sorry; of course I meant that bug 332190 is marked a duplicate of this, not vice-versa.

I made these changes for my purposes

This bug is retargetted to Bugzilla 3.2 for one of the following reasons: - it has no assignee (except the default one) - we don't expect someone to fix it in the next two weeks (i.e. before we freeze the trunk to prepare Bugzilla 3.0 RC1) - it's not a blocker If you are working on this bug and you think you will be able to submit a patch in the next two weeks, retarget this bug to 3.0. If this bug is something you would like to see implemented in 3.0 but you are not a developer or you don't think you will be able to fix this bug yourself in the next two weeks, please *do not* retarget this bug. If you think this bug should absolutely be fixed before we release 3.0, either ask on IRC or use the "blocking3.0 flag".