Closed Bug 160096 Opened 22 years ago Closed 19 years ago

Msg "A legal component ..." due to use of international chars in component name

Categories

(Bugzilla :: Creating/Changing Bugs, defect, P2)

2.16
defect

Tracking

()

RESOLVED FIXED
Bugzilla 2.22

People

(Reporter: jan.vlcinsky, Assigned: glob)

References

Details

Steps to reproduce
==================
Create a product
Create a component - use some international characters like "Pøihlašování 
uživatelù"
Create a bug for the product and component (I had this done in previous version 
2.14 already, the problem may apeare here probably)
Edit the bug (add some comments) and submit. Keep the component as is

Ezpected
========
All international characters will appeare correctly
Submit will succeed.

Observed
========
Some international characters were shown incorrectly
Submit failed with message "A legal component must be selected"

Reason
======
All HTML pages miss encoding information, and when browser selects some 
default, it is sometime incorrect.

Solution
========
Edit header.html.tmpl and add line into HTML header with encoding (I used 
windows-1250)
 <meta content="text/html; charset=windows-1250" http-equiv="Content-Type">

Remaining topics to solve
=========================
It would be advisable to have parameter for Bugzilla to specify, what encoding 
is to be used.
I will create a bug (enhancment) for sending e-mails.
Hmm. This may be fixed by bug 126266, but its a slightly different problem.

How is this data stored in the versioncache, for example? What charset is used?
Depends on: bz-charset
Priority: -- → P2
Target Milestone: --- → Bugzilla 2.18
Unloved bugs targetted for 2.18 but untouched since 9-15-2003 are being
retargeted to 2.20
If you plan to act on one immediately, go ahead and pull it back to 2.18.
Target Milestone: Bugzilla 2.18 → Bugzilla 2.20
This bug has not been touched by its owner in over six months, even though it is
targeted to 2.20, for which the freeze is 10 days away. Unsetting the target
milestone, on the assumption that nobody is actually working on it or has any
plans to soon.

If you are the owner, and you plan to work on the bug, please give it a real
target milestone. If you are the owner, and you do *not* plan to work on it,
please reassign it to nobody@bugzilla.org or a .bugs component owner. If you are
*anybody*, and you get this comment, and *you* plan to work on the bug, please
reassign it to yourself if you have the ability.
Target Milestone: Bugzilla 2.20 → ---
This works for me on a post-126266 install with utf8 switched on... Please reopen if I'm too shortsighted ;)
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
OS: Windows NT → All
Hardware: PC → All
Target Milestone: --- → Bugzilla 2.22
Assignee: myk → bugzilla
QA Contact: matty_is_a_geek → default-qa
You need to log in before you can comment on or make changes to this bug.