289396 - new filter "url_quote_utf8"

Status: RESOLVED WONTFIX

(Bugzilla :: Bugzilla-General, enhancement)

Description

[Mario Ivankovits]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041109 Firefox/1.0
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041109 Firefox/1.0

I place urls to directly call a legacy application with bugzilla informations on
some the bugzilla pages.
Now the legacy application has converted to utf-8 and thus I was forced to
encode those links with utf-8
The attached patch installs a new Filter (url_quote_utf8) to handle this case.

Maybe you might find it usefull.

Reproducible: Always

Comment 1

[Mario Ivankovits]

Attachment: filter url_qoute_utf8

Comment 2

[Stephen Lee]

Isn't this covered as part of the main UTF-8 bug - bug 126266?

Comment 3

[Mario Ivankovits]

If bugzilla goes utf-8 at all, then my filter might be useless - sure.

Due to the lenght of the bug I think this might not happen that fast.

My filter do not change anything how bugzilla handles the encoding at all, it
just gives the possibility to create a utf-8 encoded url-link.

As I wrote I need this to pass data to our legacy application and I dont know if
this is of any need for the bugzilla standard, but as it is a very small patch
(~10 lines of code) and do not change any current bugzilla behaviour, but
introduces a NEW function I thought I leave the decision if it should be added
to the bugzilla team.

Comment 4

[:glob ✱]

once bug 126266 is fixed (this will happen for the 2.20 release -- soon),
technically bugzilla won't be using utf-8 internally.  by this i mean it won't
use perl's native utf8 support when managing strings.  it will treat utf strings
as binary data.  the only thing that will change is the character encoding sent
on web pages and in emails to allow the browser/mail client to correctly decode
the binary data as utf8 strings.

Comment 5

[Mario Ivankovits]

I wonder how you will store such "binary-strings" into the database (in a way it
is readable with any client) and how we can use the search-facility e.g. using
wildcards (regexp).
But I havent followed the discussion and maybe you found solutions for this -
thus we could change this bug to WONTFIX.